Configuration — IPv6 Routing Avaya Ethernet Routing Switch

Configuration — IPv6 RoutingAvaya Ethernet Routing Switch 8800/8600

7.1NN46205-504, 04.03

March 2011

© 2011 Avaya Inc.

All Rights Reserved.

Notice

While reasonable efforts have been made to ensure that theinformation in this document is complete and accurate at the time ofprinting, Avaya assumes no liability for any errors. Avaya reserves theright to make changes and corrections to the information in thisdocument without the obligation to notify any person or organization ofsuch changes.

Documentation disclaimer

“Documentation” means information published by Avaya in varyingmediums which may include product information, operating instructionsand performance specifications that Avaya generally makes availableto users of its products. Documentation does not include marketingmaterials. Avaya shall not be responsible for any modifications,additions, or deletions to the original published version ofdocumentation unless such modifications, additions, or deletions wereperformed by Avaya. End User agrees to indemnify and hold harmlessAvaya, 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 Websites referenced within this site or documentation provided by Avaya.Avaya is not responsible for the accuracy of any information, statementor content provided on these sites and does not necessarily endorsethe products, services, or information described or offered within them.Avaya does not guarantee that these links will work all the time and hasno control over the availability of the linked pages.

Warranty

Avaya provides a limited warranty on its Hardware and Software(“Product(s)”). Refer to your sales agreement to establish the terms ofthe limited warranty. In addition, Avaya’s standard warranty language,as well as information regarding support for this Product while underwarranty is available to Avaya customers and other parties through theAvaya Support Web site: http://support.avaya.com. Please note that ifyou acquired the Product(s) from an authorized Avaya reseller outsideof the United States and Canada, the warranty is provided to you bysaid Avaya reseller and not by Avaya.

Licenses

THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYAWEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ AREAPPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/ORINSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITHAVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESSOTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOESNOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINEDFROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR ANAVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHTTO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSEUSING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BYINSTALLING, DOWNLOADING OR USING THE SOFTWARE, ORAUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OFYOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,DOWNLOADING OR USING THE SOFTWARE (HEREINAFTERREFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”),AGREE TO THESE TERMS AND CONDITIONS AND CREATE ABINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THEAPPLICABLE AVAYA AFFILIATE ( “AVAYA”).

Copyright

Except where expressly stated otherwise, no use should be made ofmaterials on this site, the Documentation, Software, or Hardwareprovided by Avaya. All content on this site, the documentation and theProduct provided by Avaya including the selection, arrangement anddesign of the content is owned either by Avaya or its licensors and isprotected by copyright and other intellectual property laws including thesui generis rights relating to the protection of databases. You may notmodify, copy, reproduce, republish, upload, post, transmit or distributein any way any content, in whole or in part, including any code andsoftware unless expressly authorized by Avaya. Unauthorizedreproduction, transmission, dissemination, storage, and or use withoutthe express written consent of Avaya can be a criminal, as well as acivil offense under the applicable law.

Third-party components

Certain software programs or portions thereof included in the Productmay contain software distributed under third party agreements (“ThirdParty Components”), which may contain terms that expand or limitrights to use certain portions of the Product (“Third Party Terms”).Information regarding distributed Linux OS source code (for thoseProducts that have distributed the Linux OS source code), andidentifying the copyright holders of the Third Party Components and theThird Party Terms that apply to them is available on the Avaya SupportWeb site: http://support.avaya.com/Copyright.

Preventing Toll Fraud

“Toll fraud” is the unauthorized use of your telecommunications systemby an unauthorized party (for example, a person who is not a corporateemployee, agent, subcontractor, or is not working on your company'sbehalf). Be aware that there can be a risk of Toll Fraud associated withyour system and that, if Toll Fraud occurs, it can result in substantialadditional charges for your telecommunications services.

Avaya Toll Fraud Intervention

If you suspect that you are being victimized by Toll Fraud and you needtechnical assistance or support, call Technical Service Center TollFraud Intervention Hotline at +1-800-643-2353 for the United Statesand Canada. For additional support telephone numbers, see the AvayaSupport Web site: http://support.avaya.com. Suspected securityvulnerabilities with Avaya products should be reported to Avaya bysending mail to: [email protected].

Trademarks

The trademarks, logos and service marks (“Marks”) displayed in thissite, the Documentation and Product(s) provided by Avaya are theregistered or unregistered Marks of Avaya, its affiliates, or other thirdparties. Users are not permitted to use such Marks without prior writtenconsent from Avaya or such third party which may own the Mark.Nothing contained in this site, the Documentation 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 writtenpermission of Avaya or the applicable third party.

Avaya is a registered trademark of Avaya Inc.

All non-Avaya trademarks are the property of their respective owners,and “Linux” is a registered trademark of Linus Torvalds.

Downloading Documentation

For the most current versions of Documentation, see the AvayaSupport Web site: http://support.avaya.com.

Contact Avaya Support

Avaya provides a telephone number for you to use to report problemsor to ask questions about your Product. The support telephone numberis 1-800-242-2121 in the United States. For additional supporttelephone numbers, see the Avaya Web site: http://support.avaya.com.

2 Configuration — IPv6 Routing March 2011

http://support.avaya.com

http://www.avaya.com/support/LicenseInfo

http://support.avaya.com/Copyright




Contents

Chapter 1: New in this release................................................................................................11Features..........................................................................................................................................................11

Chapter 2: Introduction...........................................................................................................13

Chapter 3: IPv6 routing fundamentals...................................................................................15The IPv6 header..............................................................................................................................................16

IPv6 addresses.......................................................................................................................................16Address formats.....................................................................................................................................18IPv6 extension headers..........................................................................................................................19Comparison of IPv4 and IPv6.................................................................................................................20

ICMPv6...........................................................................................................................................................20Neighbor discovery.........................................................................................................................................21

ND messages.........................................................................................................................................22Neighbor discovery cache......................................................................................................................23Router discovery.....................................................................................................................................25

IPv6 and the Avaya Ethernet Routing Switch 8800/8600...............................................................................25Management access.......................................................................................................................................26Host autoconfiguration....................................................................................................................................27IPv6 VLANs and brouter ports........................................................................................................................28Tunneling.........................................................................................................................................................28

Manually configured tunnels...................................................................................................................28Path MTU discovery........................................................................................................................................29Routing............................................................................................................................................................29

Virtual routing between VLANs...............................................................................................................30Brouter ports...........................................................................................................................................31Static routes............................................................................................................................................31Open Shortest Path First protocol..........................................................................................................34

OSPFv3...........................................................................................................................................................45Flooding scope.......................................................................................................................................46Multiple instances per link......................................................................................................................46Link-local addresses...............................................................................................................................46Authentication.........................................................................................................................................47Packet format.........................................................................................................................................47R-bit........................................................................................................................................................47New LSAs...............................................................................................................................................48Unknown LSA types...............................................................................................................................48Stub area................................................................................................................................................48

Security...........................................................................................................................................................49SNMP version 3......................................................................................................................................49

Secure Shell....................................................................................................................................................52SSH version 2 (SSH-2)...........................................................................................................................54

Access policy extensions................................................................................................................................56Multicast link discovery...................................................................................................................................56

MLD versions 1 and 2.............................................................................................................................57QoS and IPv6 filters........................................................................................................................................57License information.........................................................................................................................................57IPv6 DHCP Relay............................................................................................................................................57

Configuration — IPv6 Routing March 2011 3

Remote ID..............................................................................................................................................58IPv6 VRRP......................................................................................................................................................58

VRRPv3 operation..................................................................................................................................59VRRP advertisements and master router failover..................................................................................61VRRP terms............................................................................................................................................61Scaling....................................................................................................................................................62Critical IP address..................................................................................................................................62Hold-down timer.....................................................................................................................................63Accept mode...........................................................................................................................................63VRRP backup master with triangular SMLT...........................................................................................63VRRP fast advertisment interval.............................................................................................................65VRRP considerations with IPv6..............................................................................................................66IPv6 VRRP and ICMP redirects..............................................................................................................66

IPv6 RSMLT....................................................................................................................................................66IPv4 IST with IPv6 RSMLT.....................................................................................................................67Enabling RSMLT for IPv4 and IPv6........................................................................................................67Example network....................................................................................................................................67Router R1 recovery................................................................................................................................69Hold-up timer..........................................................................................................................................70RSMLT or VRRP....................................................................................................................................70Coexistence with IPv4 RSMLT...............................................................................................................70RSMLT network design and configuration..............................................................................................71RSMLT-edge...........................................................................................................................................71RSMLT considerations with OSPF.........................................................................................................72

Chapter 4: IPv6 routing configuration...................................................................................73IPv6 routing configuration tasks......................................................................................................................73

Chapter 5: Basic IPv6 configuration using Enterprise Device Manager............................77Configuring the management port interface....................................................................................................78Configuring management port addresses.......................................................................................................79Configuring the CPU IPv6 route table.............................................................................................................80Configuring a virtual IPv6 address..................................................................................................................81Adding an IPv6 interface ID to a brouter port or VLAN...................................................................................81Adding an IPv6 interface ID to a VLAN...........................................................................................................83Assigning IPv6 addresses to a brouter port or VLAN......................................................................................85Assigning IPv6 addresses to a VLAN.............................................................................................................86Configuring route advertisement.....................................................................................................................87Configuring route advertisement on a VLAN...................................................................................................89Configuring the neighbor cache......................................................................................................................91Adding a static neighbor to the cache.............................................................................................................92Configuring IPv6 routing and ICMP.................................................................................................................93Configuring an IPv6 discovery prefix...............................................................................................................94Configuring an IPv6 discovery prefix for a VLAN............................................................................................95Deleting an IPv6 address................................................................................................................................97Deleting an IPv6 interface...............................................................................................................................97Deleting an IPv6 discovery prefix....................................................................................................................98Removing an entry from the neighbor cache..................................................................................................98

Chapter 6: Basic IPv6 configuration using the CLI..............................................................99Assigning an IPv6 address to the management port....................................................................................101Configuring a management route..................................................................................................................102


Configuring a management virtual IPv6 address..........................................................................................103Creating a VLAN...........................................................................................................................................103Configuring the VLAN as an IPv6 VLAN.......................................................................................................105Assigning an IPv6 address to the VLAN.......................................................................................................106Configuring the administrative status for the VLAN......................................................................................107Assigning an IPv6 address to the brouter port..............................................................................................107Setting the administrative status on a brouter port........................................................................................108Configuring IPv6 ICMP..................................................................................................................................109Configuring neighbor discovery prefixes.......................................................................................................109Configuring route advertisement....................................................................................................................111Adding static entries to the neighbor cache..................................................................................................113Deleting an IPv6 address from the Ethernet SF/CPU slot.............................................................................114Deleting an IPv6 address..............................................................................................................................115Deleting an IPv6 interface.............................................................................................................................116Modifying interface parameters.....................................................................................................................117Deleting a management route.......................................................................................................................118Deleting a neighbor discovery prefix.............................................................................................................119Removing an entry from the neighbor cache................................................................................................120

Chapter 7: Basic IPv6 configuration using the ACLI.........................................................121Assigning an IPv6 address to the management port....................................................................................123Configuring a management route..................................................................................................................124Configuring a management virtual IPv6 address..........................................................................................125Creating a VLAN...........................................................................................................................................125Configuring an interface as an IPv6 interface...............................................................................................127Configuring the VLAN as an IPv6 VLAN.......................................................................................................129Configuring IPv6 ICMP..................................................................................................................................130Configuring neighbor discovery prefixes.......................................................................................................131Configuring route advertisement...................................................................................................................133Adding static entries to the neighbor cache..................................................................................................134

Chapter 8: IPv6 routing configuration using Enterprise Device Manager.......................137Creating IPv6 static routes............................................................................................................................137Creating a static default route.......................................................................................................................139Creating a black hole static route..................................................................................................................139Enabling OSPF on a router...........................................................................................................................140Creating OSPF port interfaces......................................................................................................................143Creating OSPF VLAN interfaces...................................................................................................................146Adding NBMA neighbors...............................................................................................................................149Creating OSPF areas....................................................................................................................................151Creating a virtual link.....................................................................................................................................153Specifying ASBRs.........................................................................................................................................155Inserting OSPF area aggregate ranges........................................................................................................156Configuring route redistribution.....................................................................................................................157

Chapter 9: IPv6 routing configuration using the CLI.........................................................159Configuring IPv6 static routes.......................................................................................................................162Configuring OSPF global parameters...........................................................................................................165Configuring OSPF areas...............................................................................................................................165Configuring OSPF area ranges.....................................................................................................................167Configuring OSPF area virtual interfaces......................................................................................................168Configuring an OSPF interface.....................................................................................................................169


Configuring OSPF direct redistribution..........................................................................................................171Configuring OSPF static redistribution..........................................................................................................172Configuring port-based OSPF parameters....................................................................................................173Configuring port-based OSPF neighbor parameters.....................................................................................175Configuring OSPF parameters for a VLAN...................................................................................................176Configuring OSPF neighbor parameters for a VLAN....................................................................................178

Chapter 10: IPv6 routing configuration using the ACLI.....................................................181Configuring IPv6 static routes.......................................................................................................................183Configuring OSPF global parameters...........................................................................................................185Configuring OSPF areas...............................................................................................................................186Configuring OSPF area ranges.....................................................................................................................187Configuring OSPF area virtual interfaces......................................................................................................188Configuring an OSPF interface.....................................................................................................................190Configuring OSPF direct redistribution..........................................................................................................192Configuring OSPF static redistribution..........................................................................................................193Configuring port-based OSPF neighbor parameters.....................................................................................193Configuring OSPF parameters for a VLAN...................................................................................................194Configuring OSPF neighbor parameters for a VLAN....................................................................................197

Chapter 11: IPv6 DHCP Relay configuration using Enterprise Device Manager.............199Configuring the DHCP relay forwarding path................................................................................................199Configuring DHCP relay interface parameters..............................................................................................200Configuring DHCP relay interface parameters on a VLAN...........................................................................201Viewing DHCP Relay statistics......................................................................................................................202

Chapter 12: IPv6 DHCP Relay configuration using the CLI...............................................203Configuring an IPv6 DHCP relay interface....................................................................................................204Configuring IPv6 DHCP relay on a port or VLAN..........................................................................................206Showing IPv6 DHCP relay information.........................................................................................................207Showing IPv6 DHCP relay information for a port or VLAN...........................................................................208

Chapter 13: IPv6 DHCP Relay configuration using the ACLI............................................211Configuring IPv6 DHCP relay in Global configuration mode.........................................................................212Configuring IPv6 DHCP relay parameters on a port or VLAN.......................................................................213Showing IPv6 DHCP relay information.........................................................................................................214

Chapter 14: IPv6 VRRP configuration using Enterprise Device Manager........................215Configuring a VRRP interface.......................................................................................................................216Configuring additional addresses on the VRRP interface.............................................................................218Configuring VRRP notification control...........................................................................................................219Configuring VRRP on a port..........................................................................................................................220Configuring VRRP on a VLAN......................................................................................................................222Viewing VRRP statistics................................................................................................................................224Viewing VRRP interface statistics.................................................................................................................226

Chapter 15: IPv6 VRRP configuration using the CLI..........................................................229Configuring VRRP on a port..........................................................................................................................231Configuring VRRP on a VLAN......................................................................................................................234Configuring global VRRP settings.................................................................................................................236Showing VRRP interface information............................................................................................................236Showing VRRP information for a VLAN........................................................................................................239


Clearing IPv6 VRRP statistics.......................................................................................................................241

Chapter 16: IPv6 VRRP configuration using the ACLI.......................................................243Configuring VRRP on a port or a VLAN........................................................................................................245Showing VRRP port or VLAN information.....................................................................................................247Showing VRRP interface information............................................................................................................250Clearing VRRP statistics...............................................................................................................................253

Chapter 17: IPv6 RSMLT configuration using Enterprise Device Manager......................255Configuring RSMLT on a VLAN.....................................................................................................................255Enabling RSMLT-edge..................................................................................................................................257Viewing and editing IPv6 RSMLT local information.......................................................................................257Viewing and editing IPv6 RSMLT peer information.......................................................................................258Viewing IPv6 RSMLT-edge information.........................................................................................................260

Chapter 18: IPv6 RSMLT configuration using the CLI........................................................263Configuring RSMLT on a VLAN.....................................................................................................................264Showing IP RSMLT information....................................................................................................................265Configuring RSMLT-edge..............................................................................................................................266

Chapter 19: IPv6 RSMLT configuration using the ACLI.....................................................269Configuring RSMLT on a VLAN.....................................................................................................................270Showing IP RSMLT information....................................................................................................................271Configuring RSMLT-edge..............................................................................................................................272

Chapter 20: IPv4-to-IPv6 transition mechanism configuration using Enterprise DeviceManager..................................................................................................................................275

Configuring the local VLAN or brouter port...................................................................................................275Configuring the destination VLAN or brouter port.........................................................................................277Configuring OSPF on a tunnel......................................................................................................................278Deleting a tunnel...........................................................................................................................................279Modifying tunnel hop limits............................................................................................................................279

Chapter 21: IPv4-to-IPv6 transition mechanism configuration using the CLI.................281Configuring manual tunnels..........................................................................................................................282Configuring OSPF on a tunnel......................................................................................................................284Deleting a tunnel...........................................................................................................................................286

Chapter 22: IPv4-to-IPv6 transition mechanism configuration using the ACLI...............287Configuring manual tunnels..........................................................................................................................288Configuring OSPF on a tunnel......................................................................................................................290

Chapter 23: Multicast protocol configuration using Enterprise Device Manager...........293Configuring a multicast router.......................................................................................................................294Configuring an MLD host..............................................................................................................................295Configuring an MLD router interface.............................................................................................................295Configuring an MLD router interface on a VLAN...........................................................................................297Viewing the MLD cache.................................................................................................................................298

Chapter 24: Multicast protocol configuration using the CLI.............................................299Enabling a multicast router............................................................................................................................301Enabling a VLAN for multicast routing..........................................................................................................302Configuring MLD on a VLAN.........................................................................................................................302


Enabling multicasting on a brouter port.........................................................................................................303Configuring MLD on a brouter port................................................................................................................304

Chapter 25: Multicast protocol configuration using the ACLI..........................................307Enabling a multicast router............................................................................................................................309Enabling a VLAN for multicast routing..........................................................................................................310Configuring MLD on a VLAN.........................................................................................................................310Enabling multicasting on a brouter port.........................................................................................................312Configuring MLD on a brouter port................................................................................................................312

Chapter 26: IPv6 traffic filter configuration using Enterprise Device Manager...............315Configuring an ACT.......................................................................................................................................316Modifying ACT attributes...............................................................................................................................317Inserting a pattern in an ACT........................................................................................................................318Inserting an ACL...........................................................................................................................................319Modifying an ACL..........................................................................................................................................321Inserting ACE common entries.....................................................................................................................322Modifying ACE common entries....................................................................................................................324Configuring a list of IPv6 source IP addresses for an ACE...........................................................................324Configuring a list of IPv6 destination IP addresses for an ACE....................................................................326Configuring an IPv6 next header rule for an ACE.........................................................................................327Deleting an ACT............................................................................................................................................328Deleting an ACL............................................................................................................................................328Deleting ACE common entries......................................................................................................................328

Chapter 27: IPv6 traffic filter configuration using the CLI.................................................331Configuring ACTs..........................................................................................................................................333Creating a template for user-created patterns..............................................................................................335Applying the ACT..........................................................................................................................................337Configuring ACLs..........................................................................................................................................337Configuring global and default actions for an ACL........................................................................................338Associating VLANs for an ACL.....................................................................................................................339Associating ports for an ACL.........................................................................................................................340Adding an ACE with IPv6 header attributes..................................................................................................341

Chapter 28: IPv6 traffic filter configuration using the ACLI..............................................343Configuring ACTs..........................................................................................................................................344Creating a template for user-created patterns..............................................................................................346Applying the ACT..........................................................................................................................................348Configuring ACLs..........................................................................................................................................349Configuring global and default actions for an ACL........................................................................................350Associating VLANs for an ACL.....................................................................................................................351Associating ports for an ACL.........................................................................................................................352Adding an ACE with IPv6 header attributes..................................................................................................352

Chapter 29: Interoperability..................................................................................................355Enabling IPv6 in Windows XP.......................................................................................................................355Pinging the switch from a Windows XP system............................................................................................355Enabling IPv6 in Linux...................................................................................................................................356Pinging the Linux system from the switch.....................................................................................................357Pinging the Avaya Ethernet Routing Switch 8800/8600 from the Linux system...........................................357Assigning IPv6 addresses to the Linux system.............................................................................................358


Viewing IPv6 neighbors from the Linux system.............................................................................................358

Chapter 30: Common procedures using Enterprise Device Manager..............................361Viewing advertisements in the link-state database.......................................................................................361Viewing characteristics in the AS-scope link-state database........................................................................362Viewing characteristics in the Link-scope link-state database......................................................................363Viewing virtual links on neighboring devices.................................................................................................364Viewing OSPF neighbor information.............................................................................................................366Viewing TCP and UDP information...............................................................................................................368Viewing routes information............................................................................................................................372Viewing IPv6 attributes for an ACL................................................................................................................373

Chapter 31: Common procedures using the CLI................................................................375Pinging a device............................................................................................................................................375

Chapter 32: Common procedures using the ACLI.............................................................377Pinging a device............................................................................................................................................377

Chapter 33: IPv6 CLI configuration......................................................................................379OSPF configuration.......................................................................................................................................379

Configuring OSPFv3.............................................................................................................................380Verifying operations from ERS 8600-A.................................................................................................380Verifying operations from ERS 8600-B.................................................................................................381Verifying OSPFv3 operations from a PC..............................................................................................381

Routing both IPv4 and IPv6 traffic.................................................................................................................382Tunnel configuration between brouter ports..................................................................................................384

Creating an IPv6 VLAN with ports on the source device......................................................................385Creating an IPv4 brouter port on the source device.............................................................................385Creating an IPv6 VLAN with ports on the remote device.....................................................................385Creating an IPv4 brouter port on the destination device......................................................................386Configuring a tunnel on the source device...........................................................................................386Configuring a tunnel on the destination device.....................................................................................386

Tunnel configuration between VLANs...........................................................................................................387Configuring an IPv6 VLAN on the source device.................................................................................388Configuring an IPv4 VLAN on the source device.................................................................................388Configuring an IPv6 VLAN on the destination device...........................................................................389Configuring an IPv4 VLAN on the destination device...........................................................................389Configuring the tunnel on the source device........................................................................................390Configuring the tunnel on the destination device..................................................................................390

Chapter 34: CLI show commands........................................................................................391ACL or ACE information................................................................................................................................392ACT data.......................................................................................................................................................393ACT pattern data...........................................................................................................................................394Basic OSPF information about a port............................................................................................................395Extended OSPF information.........................................................................................................................395Interface (VLAN or brouter port) configuration output...................................................................................396IPv6 static route information..........................................................................................................................397MLD cache....................................................................................................................................................397MLD configuration for a brouter port.............................................................................................................398MLD configuration for a VLAN......................................................................................................................398Neighbor cache.............................................................................................................................................399


Neighbor discovery prefixes..........................................................................................................................400OSPF areas..................................................................................................................................................400OSPF configuration settings for a port..........................................................................................................401OSPF information..........................................................................................................................................401OSPF interface information...........................................................................................................................402OSPF interface timer settings.......................................................................................................................403OSPF link-state database table....................................................................................................................404OSPF neighbors............................................................................................................................................405OSPF parameters configured for VLANs......................................................................................................406OSPFv3 information for brouter ports...........................................................................................................407OSPFv3 information for VLANs....................................................................................................................407Tunnel information.........................................................................................................................................408Tunnel interface information..........................................................................................................................409

Chapter 35: ACLI show commands.....................................................................................411ACL or ACE information................................................................................................................................412ACT data.......................................................................................................................................................413ACT pattern data...........................................................................................................................................414Basic OSPF information about a port............................................................................................................415Extended OSPF information.........................................................................................................................415Interface (VLAN or brouter port) configuration output...................................................................................416IPv6 static route information..........................................................................................................................417MLD cache....................................................................................................................................................417MLD configuration.........................................................................................................................................418Neighbor cache.............................................................................................................................................419Neighbor discovery prefixes..........................................................................................................................420OSPF areas..................................................................................................................................................421OSPF configuration settings for a port..........................................................................................................421OSPF information..........................................................................................................................................422OSPF interface information...........................................................................................................................423OSPF interface timer settings.......................................................................................................................423OSPF link-state database table....................................................................................................................424OSPF neighbors............................................................................................................................................424OSPFv3 information for VLANs....................................................................................................................425Tunnel information.........................................................................................................................................425

Chapter 36: ICMPv6 type and code......................................................................................427

Chapter 37: RFC reference for IPv6.....................................................................................429

Chapter 38: Customer service..............................................................................................431Getting technical documentation...................................................................................................................431Getting Product training................................................................................................................................431Getting help from a distributor or reseller......................................................................................................431Getting technical support from the Avaya Web site......................................................................................432


Chapter 1: New in this release

The following sections detail what's new in Avaya Ethernet Routing Switch 8800/8600 Configuration —IPv6 Routing, NN46205-504 for Release 7.1.

Features on page 11

FeaturesThere are no updates to this document in Release 7.1.


New in this release


Chapter 2: Introduction

This guide provides instructions for using the command line interface (CLI), the Avaya Command LineInterface (ACLI) and the Enterprise Device Manager graphical user interface (GUI) to perform generalnetwork management operations on the Avaya Ethernet Routing Switch 8800/8600. For more informationabout using the interfaces, see Avaya Ethernet Routing Switch 8800/8600 User Interface Fundamentals,NN46205-308.

Navigation• IPv6 routing fundamentals on page 15

• IPv6 routing configuration on page 73

• Basic IPv6 configuration using Enterprise Device Manager on page 77

• Basic IPv6 configuration using the CLI on page 99

• Basic IPv6 configuration using the ACLI on page 121

• IPv6 routing configuration using Enterprise Device Manager on page 137

• IPv6 routing configuration using the CLI on page 159

• IPv6 routing configuration using the ACLI on page 181

• IPv4-to-IPv6 transition mechanism configuration using Enterprise Device Manager onpage 275

• IPv4-to-IPv6 transition mechanism configuration using the CLI on page 281

• IPv4-to-IPv6 transition mechanism configuration using the ACLI on page 287

• Multicast protocol configuration using Enterprise Device Manager on page 293

• Multicast protocol configuration using the CLI on page 299

• Multicast protocol configuration using the ACLI on page 307

• IPv6 traffic filter configuration using Enterprise Device Manager on page 315

• IPv6 traffic filter configuration using the CLI on page 331

• IPv6 traffic filter configuration using the ACLI on page 343

• Interoperability on page 355

• Common procedures using Enterprise Device Manager on page 361

• Common procedures using the CLI on page 375


• Common procedures using the ACLI on page 377

• IPv6 CLI configuration on page 379

• CLI show commands on page 391

• ACLI show commands on page 411

• ICMPv6 type and code on page 427

• RFC reference for IPv6 on page 429

Introduction


Chapter 3: IPv6 routing fundamentals

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

Important:IPv6 routing is not supported with Virtual Routing and Forwarding (VRF).

Navigation• The IPv6 header on page 16

• ICMPv6 on page 20

• Neighbor discovery on page 21

• IPv6 and the Avaya Ethernet Routing Switch 8800/8600 on page 25

• Management access on page 26

• Host autoconfiguration on page 27

• IPv6 VLANs and brouter ports on page 28

• Tunneling on page 28

• Path MTU discovery on page 29

• Routing on page 29

• OSPFv3 on page 45

• Security on page 49

• Access policy extensions on page 56

• Multicast link discovery on page 56

• QoS and IPv6 filters on page 57

• License information on page 57

• IPv6 DHCP Relay on page 57

• IPv6 VRRP on page 58

• IPv6 RSMLT on page 66


The IPv6 headerThe 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 (QoS)• a 16-bit unsigned integer, the length of the IPv6 payload• an 8-bit next header selector that identifies the next 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 16 illustrates the IPv6 header.

Figure 1: IPv6 header

IPv6 addressesIPv6 addresses are 128 bits in length. The address identifies a single interface or multipleinterfaces. IPv4 addresses, in comparison, are 32 bits in length. The increased number ofpossible 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 3bits indicate the type of address that follows. Figure 2: 128-bit IPv6 address format onpage 17 shows the IPv6 address format.

IPv6 routing fundamentals


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). Forstateless autoconfiguration, the ID is 64 bits in length. See Host autoconfiguration onpage 27. 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 betweenthe MAC address and the interface ID is necessary. A manually configured interface ID canbe longer or shorter than 64 bits.

Anycast Address

An IPv6 anycast address is a unicast address identifying a group of IPv6 nodes that share acommon variable-length address prefix. A packet bearing an anycast address delivers to onenode in the group. No visual way exists to distinguish an anycast address from an unicastaddress.

Multicast Address

An IPv6 multicast address identifies a group of nodes. A packet bearing a multicast addressdelivers to all members of the group. (IPv6 multicast addresses supersede the function of IPv4broadcast addresses.)

Figure 3: Multicast Address Format on page 17 shows the format of an IPv6 multicastaddress.

Figure 3: Multicast Address Format

A value of FF (11111111) in the 8 high-order bits of an IPv6 address indicates that the addressspecifies a multicast group. The 4-bit flags field indicates whether the group is permanent or

The IPv6 header


transient. The 4-bit scope field indicates the scope of the group specified in the 112-bit groupID 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

IPv6 nodes that need to inter operate with IPv4 nodes use the IPv4-compatible address, whichincludes an IPv4 address in the low-order 32 bits. The following figure shows the format of anIPv4-compatible address.

Figure 4: IPv4-Compatible Unicast Address Format

Address formatsThe format for representing an IPv6 address is

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 nonzero field must contain at least one numeral. Within a hexadecimal field; however,leading zeros are not required.

Certain classes of IPv6 addresses commonly include multiple contiguous fields containinghexadecimal 0. The following sample address includes five contiguous fields containing zeroeswith a double colon (::):

FF01::43



You can use a double colon to compress the leading zero fields in a hexadecimal address. Adouble 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 6 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 headersIPv6 extension headers describe processing options. Each extension header contains aseparate category of options. A packet can include zero or more extension headers; see Figure5: IPv6 header and extension headers on page 19.

Figure 5: IPv6 header and extension headers

IPv6 examines the destination address in the main header of each packet it receives. Thisexamination determines whether the router is the packet destination or an intermediate nodein the packet data path. If the router is the packet destination, IPv6 examines the headerextensions that contain options for destination processing. If the router is an intermediate node,IPv6 examines the header extensions that contain forwarding options.

By examining only the extension headers that apply to the operations it performs, IPv6 reducesthe 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 IPv6routers examine between the source and the destination.

• The end-to-end extension header contains optional information for the destinationnode.

• The source routing extension header contains a list of one or more intermediate nodesthat define a path for the packet to follow through the network, to the destination. Thepacket source creates this list. This function is similar to the IPv4 source routingoptions.

The IPv6 header


• The fragmentation extension header uses an IPv6 source to send packets larger than thesize specified for the path maximum transmission unit (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 IPv6Table 1: IPv4 and IPv6 differences on page 20 compares key differences between IPv4 andIPv6.

Table 1: IPv4 and IPv6 differences

Feature IPv4 IPv6Address 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 addressresolution

ARP (broadcast) Multicast NeighborDiscovery Messages

Multicast membership IGMP Multicast Listener Discovery(MLD)

Router discovery Optional Required

Uses broadcasts Yes No

Configuration Manual, DHCP Automatic, DHCP

ICMPv6Internet Control Message Protocol version 6 (ICMPv6) maintains and improves upon featuresfrom ICMP for IPv4. ICMPv6 reports the delivery of forwarding errors, such as destinationunreachable, packet too big, time exceeded, and parameter problem. ICMPv6 also deliversinformation messages such as echo request and echo reply.



Important:ICMPv6 plays an important role in IPv6 features such as neighbor discovery, MulticastListener Discovery, and path MTU discovery.

Important:The switch does not send an ICMP message when it receives IPv6 packets destined to anIPv6 multicast address with a destination header option type equal to 0x80.

Neighbor discoveryIPv6 nodes (routers and hosts) on the same link use neighbor discovery (ND) to discover linklayer addresses and to obtain and advertise various network parameters and reachabilityinformation. ND combines the services 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 neighbors attached to local links. Routers also useND to discover neighbors and link layer information. ND also updates the neighbor databasewith valid entries, invalid entries, and entries migrated to various locations.

ND protocol provides you with the following services:

• address and prefix discovery: hosts determine the set of addresses that are on-link forthe given link. Nodes determine which addresses or prefixes are locally reachable orremote with address and prefix discovery.

• router discovery: hosts discover neighboring routers with router discovery. Hosts establishneighbors as default packet-forwarding routers.

• parameter discovery: host and routers discover link parameters such as the link MTU orthe hop limit value placed in outgoing packets.

• address autoconfiguration: nodes configure an address for an interface with addressautoconfiguration. See Host autoconfiguration on page 27.

• duplicate address detection: hosts and nodes determine if an address is assigned toanother router or a host.

• address resolution: hosts determine link layer addresses (MAC for Ethernet) of the localneighbors (attached on the local network), provided the IP address is known.

• next-hop determination: hosts determine how to forward local or remote traffic with next-hop determination. The next hop can be a local or remote router.

• neighbor unreachability detection: hosts determine if the neighbor is unreachable, andaddress resolution must be performed again to update the database. For neighbors youuse as routers, hosts attempt to forward traffic through alternative default routers.

• redirect: routers inform the host of more efficient routes with redirect messages.

Neighbor discovery


Neighbor discovery uses three components:

• host-router discovery• host-host communication component• redirect

See Figure 6: neighbor discovery components on page 22 for the ND components.

Figure 6: neighbor discovery components

ND messagesTable 2: IPv6 and IPv4 neighbor comparison on page 22 shows new ICMPv6 messagetypes.

Table 2: IPv6 and IPv4 neighbor comparison

IPv4 neighbor function IPv6 neighbor function DescriptionARP Request message Neighbor solicitation

messageA node sends this message todetermine the link-layer address of aneighbor or to verify that a neighbor isstill reachable through a cached link-layer address. You can also useneighbor solicitations for duplicateaddress detection.

ARP Reply message Neighbor advertisement A node sends this message either inresponse to a received neighborsolicitation message or tocommunicate a link layer addresschange.

ARP cache Neighbor cache The neighbor cache containsinformation about neighbor types onthe network. See Neighbor discoverycache on page 23.

Gratuitous ARP Duplicate addressdetection

A host or node sends a request with itsown IP address to determine if another



IPv4 neighbor function IPv6 neighbor function Descriptionrouter or host uses the address. Thesource receives a reply from theduplicate device. Both hosts androuters use this function.

Router solicitationmessage (optional)

Router solicitation(required)

The host sends this message upondetecting a change in a networkinterface operational state. Themessage requests that routersgenerate router advertisementimmediately rather than at thescheduled time.

Router advertisementmessage (optional)

Router advertisement(required)

Routers send this message toadvertise their presence with variouslinks and Internet parameters eitherperiodically or in response to a routersolicitation message. Routeradvertisements contain prefixes thatyou use for on-link determination oraddress configuration, and asuggested hop limit value.

Redirect message Redirect message Routers send this message to informhosts of a better first hop for adestination.

Neighbor discovery cacheThe 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 23 describes neighbor cache states.

Table 3: Neighbor cache states

State DescriptionIncomplete A node sends a neighbor solicitation message to a multicast

device. The multicast device sends no neighbor advertisementmessage in response.

Reachable You receive positive confirmation within the last reachable timeperiod.

Neighbor discovery


State DescriptionStale A node receives no positive confirmation from the neighbor in

the last reachable time period.

Delay A time period longer than the reachable time period passessince the node received the last positive confirmation, and apacket was sent within the last DELAY_FIRST_PROBE_TIMEperiod. If no reachability confirmation is received withinDELAY_FIRST_PROBE_TIME period of entering the DELAYstate, neighbor solicitation is sent and the state changes toPROBE.

Probe Reachability confirmation is sought from the device everyretransmit timer period.

The following events affect the neighbor cache. The following events involve Layer 2 and Layer3 interaction during processing:

• flushing the virtual LAN (VLAN) MAC

• removing a VLAN or brouter

• performing an action on all VLANs

• removing a port from a VLAN

• removing a port from a spanning tree group (STG)

• removing a multilink trunk (MLT) group from a VLAN

• removing an MLT port from a VLAN

• removing an MLT port from an STG

• performing an action that disables a VLAN, such as removing all ports from a VLAN

• disabling a tagged port that is a member of multiple routable VLANs

Table 4: IPv4 and IPv6 neighbor discovery comparison on page 24 shows a comparison ofIPv4 and IPv6 neighbor discovery.

Table 4: IPv4 and IPv6 neighbor discovery comparison

IPv4 neighbor functions IPv6 neighbor functionsARP Request message Neighbor solicitation message

ARP Reply message Neighbor advertisement message

ARP cache Neighbor cache

Gratuitous ARP Duplicate address detection

Router solicitation message (optional) Router solicitation (required)

Router advertisement message (optional) Router advertisement (required)

Redirect message Redirect message



Router discoveryIPv6 nodes discover routers on the local link with router discovery. The IPv6 router discoveryprocess uses the following messages:

• Router advertisement on page 25• Router solicitation on page 25

Router advertisement

Configured interfaces on an IPv6 router send out router-advertisement messages. Router-advertisements are also sent in response to router-solicitation messages from IPv6 nodes onthe 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 protocolinformation, especially during the discovery phase. To receive these messages the deviceregisters the well-known multicast addresses when a particular protocol is enabled andderegisters 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 Ethernetmulticast address of 33-33-.

Multicast neighbor solicitation exists for address resolution, duplicate address detection, andmulticast router solicitation and router advertisement

IPv6 and the Avaya Ethernet Routing Switch 8800/8600IPv6 routing provides an underlying mechanism to transmit data blocks from source todestination. The source and destination are hosts, identified by fixed-length IPv6 addresses.

The Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) provide atransport facility for data transmission. TCP is a reliable mechanism. UDP is not as reliable asTCP. Routing protocols identify the shortest path from a source to a destination. The Internet

IPv6 and the Avaya Ethernet Routing Switch 8800/8600


Protocol defines a standard format primarily known as the IP header, required for successfuldelivery of datagrams.

Transport and routing protocols are not physical media dependant. The next hop pathcalculated by the routing protocol in path from the source to the destination can result in thenext hop being connected on an Ethernet interface. In this case, the next-hop router mustrequest a mapping of a next-hop IPv6 address to a 48-bit MAC address. The IPv6 NeighborDiscovery Protocol, described in RFC2461, defines a mechanism to identify existing orupcoming neighbors in the network. This mechanism combines the ARP, router discovery, andredirect information. Due to this combination of features, the mechanism supports theautoconfiguration of host entities.

IPv6 requires installed R, RS, or 8800 modules in the Avaya Ethernet Routing Switch8800/8600 chassis. IPv6 also requires at least one 8692 SF/CPU Enterprise Enhanced SF/CPU with SuperMezz or at least one 8895 SF/CPU (no SuperMezz is required on the 8895SF/CPU). IPv6 on the Avaya Ethernet Routing Switch 8800/8600 basic redistribution usesOpen Shortest Path First (OSPF) v3, local, and static routes. Nonlocal next-hop static routesare possible.

Management accessThe Avaya Ethernet Routing Switch 8800/8600 contains an Ethernet port for both master andstandby SF/CPUs. You configure these Ethernet ports differently from the regular switch ports.In IPv4, the protocol stack operating for these ports is different from the switch IP stack. TheIPv6 functionality for the SF/CPU Ethernet port is offered only when the switch operationalstate is up, and is not offered from the boot monitor level.

The management port provides two functions:

• configuring IPv6 after the system boots up in the CLI and device management throughthe configured IPv6 address

• configuring static routes reachable through the management route for connectivity

IPv6 supports multiple addresses on each interface and for multiple addresses to managementIP interface.

In addition to the management port, you can configure management routes to reach nonlocaldestinations.

The Avaya Ethernet Routing Switch 8800/8600 advertises the management port and themanagement route to the regular routing domain (OSPFv3), but does not include the prefix forthe interface in the router advertisement.



Host autoconfigurationThe Avaya Ethernet Routing Switch 8800/8600 can automatically configure a host (node), andassign addresses automatically.

Stateless autoconfiguration enables serverless basic configuration of IPv6 nodes andrenumbering from a mathematical perspective.

Stateless autoconfiguration = network prefix (router advertisement) + IPv6 InterfaceIdentifiers.

Stateless autoconfiguration uses the network prefix information in the router advertisementmessages from the node address. The Extended Unique Identifier (EUI-64) format obtains theremaining address. The IPv6 interface address is created from the 48-bit (6-byte) MAC addressas follows:

1. EUI-64 Hexadecimal digits 0xff-fe are inserted between the third and fourth bytesof the MAC address to obtain the EUI-64.

2. The universal or local bit, the second lower-order bit of the first byte of the MACaddress, is complemented.

For example, the IPv6 identifier for host A uses the MAC address 00-AA-00-3F-2A-1C. Toautomatically assign an address, the following occurs:

1. Convert to EUI-64 format

00-AA-00-FF-FE-3F-2A-1C

2. Complement the Universal/Local (U/L) bit.

The first byte in binary form is 00000000. When the seventh bit is complemented,it becomes 00000010 (0x02).

The result is 02-AA-00-FF-FE-3F-2A-1C or 2AA:FF:FE3F:2A1C.

Thus, host A with MAC address 00-AA-00-3F-2A-1C, combined with network prefix 2001::/64provided by router advertisement, uses an IPv6 address 2001::2AA:FF:FE3F:2A1C.

If no router is present, a host can generate a link-local address with the prefix FE80. The link-local address for a node with the MAC address 00-AA-00-3F-2A-1C is FE80::2AA:FF:FE3F:2A1C.

The Neighbor Discovery Protocol performs autoconfigration. See Neighbor discovery onpage 21.

Host autoconfiguration


The following are the states of autoconfiguration address:

• Tentative: the address is being verified as unique (link-local address)

• Valid: an address from which unicast traffic can be sent and received and can be in oneof two states

• Preferred: an address for which uniqueness was verified for unrestricted use

• Deprecated: an address that remains valid but is withheld for new communication

• Invalid: an address for which a node can no longer send or receive unicast traffic

A valid lifetime is the length of time of the preferred and depreciated state. The preferred lifetimeis the length of time for the tentative, preferred, and depreciated state.

IPv6 VLANs and brouter portsThe Avaya Ethernet Routing Switch 8800/8600 supports three logical types of interfaces thatparticipate in the IPv6 routing arena:

• Virtual LAN interface: Release 4.1 supports port-based VLANs and protocol-basedVLANs. VLANs can contain MLT and SMLT ports.

• Brouter port: In IPv4, the brouter port support is limited to the physical port. In Release4.1, IPv6 extends support to MLTs. This support is possible because the Layer 3 softwaretreats MLTs as logical ports. Each logical IPv6 interface can use multiple IPv6addresses.

TunnelingTunneling provides a mechanism for transferring IPv6 traffic through an IPv4 network.

Manually configured tunnelsManually configured tunnels are point-to-point. IPv6 reachability enables tunnel forwarding.

Manually configured tunnels provide communication between two isolated IPv6 domains overan IPv4 network. Create a point-to-point connection between the two isolated IPv6 devices byconfiguring the tunnel endpoints. Tunnel interfaces are logical point-to-point interfaces. Enablea routing protocol, such as the Open Shortest Path First (OSPF) protocol, on the interfaces toallow dynamic routing.

You cannot configure the maximum transmission unit (MTU) for tunnels. The default MTU valuefor tunnels is 1280. Tunnel operational status depends on the IPv4 reachability of the tunnel



endpoint. The Avaya Ethernet Routing Switch 8800/8600 attempts reachability through R, RS,or 8800 modules and updates IPv6 information with changes.

Configure IPv6 and IPv4 addresses at each end of the tunnel. The router or host at the sourceand destination of the tunnel must support both IPv4 and IPv6 protocol stacks.

Path MTU discoveryIPv6 routers do not fragment packets. The source node sends a packet equal in size to themaximum transmission unit (MTU) of the link layer. The packet travels through the network tothe source. If the packet encounters a link to a smaller MTU, the router sends the source nodean ICMP error message containing the MTU size of the next link.

The source IPv6 node then resends a packet equal to the size of the MTU included in the ICMPmessage.

The default MTU value for a regular interface is 1500.

RoutingA routing table is present on all nodes. The table stores information about IPv6 network prefixesand how to reach them. IPv6 checks the destination neighbor cache first. If the destination isnot in the destination neighbor cache, the routing table determines:

• the interface used for forwarding (the next-hop interface)• the next-hop address

The switch requires routing protocols to exchange IPv6 routing prefixes. IPv6 routes in a routingtable 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 devices by using the OSPFv3 protocol.The only dynamic protocol supported is OSPFv3.

When you configure routing on a VLAN, an IP address is assigned to the VLAN and is notassociated with any particular physical port. Brouter ports are VLANs that route IP packets andbridge nonroutable traffic in a single-port VLAN.

Note:IPv6 addresses remain in the routing table after you disable the VLAN.

Path MTU discovery


This section contains the following topics:

• Virtual routing between VLANs on page 30• Brouter ports on page 31• Static routes on page 31• Open Shortest Path First protocol on page 34

Virtual routing between VLANsThe Avaya Ethernet Routing Switch 8800/8600 supports wire-speed IP routing betweenVLANs. As shown in Figure 7: IP routing between VLANs on page 30, although VLAN 1 andVLAN 2 reside on the same switch, for traffic to flow from VLAN 1 to VLAN 2, you must routethe traffic.

When you configure routing on a VLAN, an IP address assigned to the VLAN is the virtualrouter interface address for the VLAN. The VLAN IP address is called a virtual router interfacebecause it is associated with no particular port. The VLAN IP address can be reached throughany VLAN port, and frames route from the VLAN through the gateway IP address. You canforward routed traffic to another VLAN within the switch.

Figure 7: IP routing between VLANs

When you enable Spanning Tree Protocol on a VLAN, the spanning tree convergence mustbe stable before the routing protocol becomes active. This requirement can lead to anadditional delay in IP traffic forwarding.

Because a port can belong to multiple VLANs, a one-to-one correspondence no longer existsbetween the physical port and the router interface.

As with any IP address, you can use virtual router interface addresses for device management.For the Simple Network Management Protocol (SNMP) or Telnet management, you can useany virtual router interface address to access the switch while routing is enabled on theVLAN.



Brouter portsThe Avaya Ethernet Routing Switch 8800/8600 also supports brouter ports. A brouter port isa single-port VLAN that can route IP packets and bridge all nonroutable traffic. The differencebetween a brouter port and a standard protocol-based VLAN configured for routing is that therouting interface of the brouter port is not subject to the spanning tree state of the port. A brouterport can be in the blocking state for nonroutable traffic while it routes IP traffic. This featureremoves interruptions caused by Spanning Tree Protocol recalculations in routed traffic.

A brouter port is a one-port VLAN; therefore, each brouter port decreases the number ofavailable VLANs by one and uses one VLAN ID.

Static routesStatic routes provide an alternative method for establishing route reachability. This function,with dynamic routes, provides routing information from the forwarding database to theforwarding 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 RTMcommunicates all updates to best routes to the forwarding plane.

You must provide the following options to configure a static route:

• Local or Nonlocal hop option: configure a static route either with a next hop that exists ona locally attached network or a next hop that is reachable through a dynamic route. Thestatic route is available as long as the next hop is reachable.

Important:When you configure a static route over an IPv6 tunnel, configure either the next-hopor the tunnel-id, not both at the same time. Because there is a single node at the otherend of the tunnel, it's not up to the user to specify a next hop.

• Route preference: you can specify the route preference for the static routes as follows:

- Global value for all static routes: preference is either static or dynamic routes.- Preference for each static route entry: if specified, this value overrides the global

value for the entry. This provides flexibility to change the general behavior of aspecific static route.

• Administrative status: controls when the static route is considered for forwarding.Administrative status differs from the operational status. An admin-enabled static routecan still be unreachable and cannot be used for forwarding. An admin-disabled static routeis operationally a nonexistent route.

• Multiple static routes: specify alternative paths to the same destination. Multiple staticroutes provide stability and load balancing.

To configure a default static route, supply a value of 0 for the prefix and the prefix length.

Routing


Events that affect static route operation include user-configured changes or other systemevents. The table below describes these changes.

Table 5: Static route operation changes

Action ResultChanging the administrative status of thestatic route

Makes the static route unavailable forforwarding.

Deleting the IPv6 addresses of a VLAN orbrouter port

Permanently deletes the static routes withthe corresponding local neighbors from theRTM, the forwarding database, and theconfiguration database.

Deleting a VLAN Removes static routes with a local next-hopoption from the configuration database.Static routes with a nonlocal next-hop optionbecome inactive (they are removed from theforwarding database).

Disabling forwarding on a VLAN or brouterport

Static routes reachable through the locallyattached network become inactive.

Disabling a VLAN or brouter port Makes the static routes inactive.

Disabling IPv6 forwarding globally Stops forwarding all IPv6 traffic.

Learning changes about a dynamicallylearned neighbor

When a neighbor becomes unreachable or isdeleted, the static route with the neighborbecomes inactive, and the configuration isnot affected. The static route with theneighbor becomes active in the configurationand is added to the RTM and forwardingdatabase when the neighbor becomesreachable.

Enabling a static route Adds the route to the RTM to change certainstatic routes to active.

Deleting a static route Permanently deletes a static route from theconfiguration.

Disabling a static route Stops traffic on the static route but does notremove the route from the configuration.

Changing a preference When the static route preference changes,the best routes for the entries use both staticand dynamic paths

Deleting or disabling a tunnel Deletes or disables a tunnel and removes thetunnel entry from the forwarding table.

Enabling the tunnel Enables a tunnel, activates the tunnel staticroutes and adds an entry to the forwardingtable.



The local-nexthop flag is not required for Pv6. An IPv4 device cannot learn a neighbor ARPentry unless the device uses a local route entry. In IPv6, a host can learn a neighbor entry ifthe device is physically connected to the neighbor (one hop).

The static route becomes active when the next hop is reachable by a dynamic route neighborresolution. The static route takes the forwarding information from the dynamic route. If the nexthop is reachable using a 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 makeforwarding decisions. Use the static route table to directly change static routes. Although thetables are separate, the system routing table automatically reflects the static routing tablemanager entries if the next hop address in the static route is reachable and if the static routeis enabled.

The static route table is indexed by four attributes:

• Destination Network

• Destination Mask

• Next Hop

• ifIndex

The maximum number of entries is 500. You can insert static routes by using the static routetable, and you can delete static routes by using either the static route table or the system routingtable.

Important:The system routing table stores only active static routes with the best route preference. Astatic route is active only if the route is enabled and if the next hop address is reachable (forexample, if a valid ARP entry exists for the next hop).

You can enter multiple routes (for example, multiple default routes) that use different costs andthe lowest cost route that is reachable appears in the routing table. If you enter multiple nexthops for the same route with the same cost, the switch does not replace the existing route. Ifyou 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 connectivity loss.

Static routes configured for the management port apply using the natural mask of the network.Because traffic that originates from the switch refers to these routes before checking the IProuting table, the switch management traffic can be incorrectly forwarded from themanagement port, even though a specific route exists in the routing table.

Routing


Black hole static routes

While aggregating or injecting routes to other routers, a router may not use a route to theaggregated destination, which causes a "black hole." To avoid routing loops, you can configurea black hole static-route to the destination it is advertising.

A black hole route is a route with invalid next hop, so that the switch drops data packetsdestined to this network.

When you specify a route preference, be sure that you configure the preference valueappropriately so that when the black-hole route is used, it gets elected as the best route. Beforeadding the black hole route a check is made to ensure that no other static route to that identicaldestination in an enabled state exists. If such a route exists, you cannot add the black holeroute, and the system generates an error message.

However, if an enabled-black hole route exists, you cannot add another static route to thatdestination. You must first delete or disable the black hole route before you can add a regularstatic route to that destination.

Open Shortest Path First protocolOpen Shortest Path First (OSPF) protocol is an Interior Gateway Protocol (IGP) that distributesrouting information between routers belonging to a single autonomous system (AS). OSPF isa link-state protocol intended for use in large networks.


• Overview on page 35• Benefits on page 35• Autonomous system and areas on page 35• Neighbors on page 37• OSPF routers on page 38• Router types on page 38• OSPF interfaces on page 39• OSPF and IP on page 41• OSPF packets on page 41• Link-state advertisements on page 42• AS external routes on page 43• OSPF virtual links on page 43• OSPF routing algorithm on page 44• Specifying ASBRs on page 44



Overview

In an OSPF network, each router maintains a link-state database that describes the topologyof the autonomous system (AS). The database contains the local state for each router in theAS, including usable interfaces and reachable neighbors. If the router detects changes, itshares them by flooding link-state advertisements (LSAs) throughout the AS. Routerssynchronize topological databases based on shared information from LSAs.

From the topological database, each router constructs a shortest-path tree, with itself as theroot. The shortest-path tree provides the optimal route to each destination in the AS. Routinginformation from outside the AS appears on the tree as leaves.

OSPF routes IP traffic based solely on the destination IP address and the prefix in the IP packetheader.

OSPFv3 is supported in IPv6 routing. OSPFv3 runs for each link rather than for each subnet.Multiple instances are possible on a single link. OSPFv3 does not support the OSPFv2authentication feature.

Benefits

In large networks, OSPF offers the following benefits:

• Fast convergence: during topological changes, OSPF recalculates routes quickly.

• Minimal routing protocol traffic: OSPF sends updates only when changes occur andminimizes the traffic.

• Load sharing: OSPF provides support for equal-cost multipath routing. If several equal-cost 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.

Autonomous system and areas

You can subdivide the AS into areas that group contiguous networks, routers that connect tothese networks, and attached hosts. Each area uses a topological database that is invisiblefrom outside the area. Routers within an area cannot access the topology of other areas.Subdividing the AS into areas significantly reduces routing protocol traffic compared to treatingthe entire AS as a single link-state domain.

Attach a router to more than one area to maintain a separate topological database for eachconnected area. Two routers within the same area maintain identical topological databases forthat area. Assign a unique area ID to each area. The area ID 0.0.0.0 is reserved for thebackbone area.

Packets route in the AS based on the source and destination addresses. If the source anddestination of a packet reside in the same area, intra-area routing occurs. If the source and

Routing


destination of a packet reside in different areas, inter-area routing occurs. Intra-area routingprevents the use of information obtained outside the area to protect the area from incorrectrouting information. Inter-area routing must pass through the backbone area.


• Backbone area on page 36

• Stub area on page 36

• Not so stubby area on page 36

Backbone area

The backbone area consists of the following network types:

• networks and attached routers not in any other area

• routers that belong to multiple areas

The backbone is usually contiguous, but you can configure virtual links to create anoncontiguous area.

Configure virtual links between any two backbone routers that use an interface to a commonnonbackbone area. Virtual links belong to the backbone and use intra-area routing only. For adescription of virtual links, see OSPF virtual links on page 43.

The backbone distributes routing information between areas. The backbone area topology isinvisible to other areas. Other area topologies are invisible to the backbone area.

The OSPF routing algorithm finds the paths with the lowest cost. The topology of the backbonedictates the backbone paths used between areas. The algorithm examines the routing tablesummaries for each connected area boarder router (ABR) to select inter-area paths. The OSPFbehavior is modified, according to OSPF standards so that OSPF routes are not learnedthrough an ABR unless the router connects to the backbone or through a virtual link.

Stub area

You configure stub areas at the edge of the OSPF routing domain. Stub areas use one ABR.A stub area receives no LSAs for routes outside the area, reducing the size of the link-statedatabase. The ABR examines packets destined for outside the stub area before it forwardsthe packet to the destination.

The OSPF routing algorithm treats the network behind a passive interface as a stub area thatforms no adjacencies. The OSPF routing algorithm advertises the network into the OSPF areaas an internal route.

Not so stubby area

A not so stubby area (NSSA) replaces LSAs with a default route to prevent external LSAs fromflooding the area. An NSSA can import small stub (non-OSPF) routing domains into OSPF.Like stub areas, NSSAs are at the edge of an OSPF routing domain. Non-OSPF routingdomains attach to the NSSAs to form NSSA transit areas. The NSSA border router performsmanual aggregation by accessing the addressing scheme of small stub domains.



Neighbors

In an OSPF network, any two routers with an interface to the same network are neighbors.Routers use the Hello Protocol to discover neighbors and to maintain neighbor relationships.On a broadcast or point-to-point network, the Hello Protocol dynamically discovers neighbors.On a nonbroadcast multiaccess network (NBMA), you must manually configure neighbors forthe network.

The Hello Protocol provides bidirectional communication between neighbors. Periodically,OSPF routers send hello packets over all interfaces. These hello packets include the followinginformation:

• 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 that it is listed in theneighbor router hello packet.


• Neighbors on NBMA networks on page 37

• Neighbor adjacencies on page 37

• NBMA adjacencies on page 38

Neighbors on NBMA networks

NBMA interfaces with a positive router priority and a nonzero value can become the DR forthe NBMA network and are configured with a list of all attached routers. The neighbors listincludes each neighbor IP address and router priority. You must manually configure the IPaddress, mask, and router priority of neighbors on routers that can become the DR or BDR forthe network.

Log messages indicate when an OSPF neighbor state changes. This log message indicatesthe previous state and the new state of the OSPF neighbor. The log message generated forsystem traps also indicates the previous state and the current state of the OSPF neighbor.

Neighbor adjacencies

Neighbors can form an adjacency to exchange routing information. When two routers form anadjacency, the routers perform a database exchange to synchronize the topological databases.When the routers synchronize databases, the routers are fully adjacent. Bandwidth isconserved because only routing change information passes between adjacent routers.

All routers connected by a point-to-point network or to a virtual link always form an adjacency.All routers on a broadcast or NBMA network form an adjacency with the DR and the BDR.

Routing


NBMA adjacencies

Before a DR is elected in an NBMA network, the router sends hello packets only to thoseneighbors eligible to become the DR. The NBMA DR forms adjacencies only with configuredneighbors and drops all packets from other sources. The neighbor configuration also specifiesto the router the expected hello behavior for each neighbor.

Important:If a router receives a hello packet from a neighbor with a priority different from the configuredpriority, the router automatically changes the configured priority to match the dynamicallylearned priority.

OSPF routers

To limit the amount of routing protocol traffic, the Hello Protocol elects a designated router (DR)and a backup designated router (BDR) on each multiaccess network. Instead of neighboringrouters forming adjacencies and swapping link-state information with each other (which, on alarge network, can mean a large volume of routing protocol traffic), all routers on the networkform adjacencies only with the DR and the BDR and send link-state information to the DR andBDR. The DR redistributes this information to every other adjacent router.

In backup mode, the BDR receives link-state information from all routers on the network andlistens for acknowledgements. If the DR fails, the BDR transitions quickly to the role of DRbecause routing tables are up to date.

Router types

Routers in an OSPF network can perform different roles depending on router configuration. Table 6: Router types in an OSPF network on page 38 describes the router types you canconfigure in an OSPF network.

Table 6: Router types in an OSPF network

Router Type DescriptionAS boundary router(ASBR)

A router attached at the edge of an OSPF network is called anAS boundary router (ASBR). An ASBR uses one or moreinterfaces that run an interdomain routing protocol such as theBorder Gateway Protocol (BGP). In addition, any routerdistributing static routes or Routing Information Protocol (RIP)routes into OSPF is an ASBR. The ASBR forwards externalroutes into the OSPF domain. In this way, routers inside theOSPF network learn about destinations outside their domain.

Area border router (ABR) A router attached to two or more areas inside an OSPF networkis an area border router (ABR). ABRs play an important role in



Router Type DescriptionOSPF networks by condensing the amount of OSPFinformation that is disseminated.

Internal router (IR) A router that uses interfaces only within a single area inside anOSPF network is an internal router (IR). Unlike ABRs, IRs usetopological information only about the local area.

Designated router (DR) In a broadcast or NBMA network, a single router is thedesignated router (DR) for that network. A DR ensures that allrouters on the network synchronize and advertise that networkto the remainder of the AS.

Backup designated router(BDR)

A backup designated router (BDR) is elected in addition to thedesignated router (DR) and becomes the DR if required.

OSPF interfaces

An OSPF interface, or link, is configured on an IP interface. In the Avaya Ethernet RoutingSwitch 8800/8600, an IP interface can be a single link (brouter port) or a logical interfaceconfigured on a VLAN (multiple ports). The underlying lower level protocols and the routingprotocol itself obtain the state information associated with the interface.

The Avaya Ethernet Routing Switch 8800/8600 designates OSPF interfaces as one of thefollowing types:

• broadcast (active)• nonbroadcast multiaccess (NBMA)• point-to-point• point-to-multipoint

Important:When you enable an OSPF interface, you cannot change the interface type. You must firstdisable the interface. You can then change the type and reenable the interface. For an NMBAinterface, you must also first delete the manually configured neighbors.


• Broadcast interface on page 39• Nonbroadcast multiaccess interface on page 40

Broadcast interface

Broadcast interfaces support many attached routers and can address a single physicalmessage to all attached broadcast routers (sent to AllSPFRouters and AllDRouters).

Broadcast interfaces discover neighboring routers dynamically using the OSPF Hello Protocol.Each pair of routers on a broadcast network, such as an Ethernet, communicate directly.

Routing


Nonbroadcast multiaccess interface

Nonbroadcast multiaccess (NBMA) interfaces support many routers but cannot broadcast.

In contrast to a broadcast network where some OSPF protocol packets are multicast (sent toAllSPFRouters and AllDRouters), NBMA interfaces replicate and send OSPF packets to eachneighboring router, in turn, as unicast. NBMA networks drop all OSPF packets with destinationaddresses to AllSPFRouters and AllDRouters.

Designated router parameters

OSPF treats an NBMA network like a broadcast network. Because many routers attach to thenetwork, OSPF designates a router (DR) to generate the network link-state advertisements.

Because the NBMA network does not broadcast, you must manually configure neighbors foreach router eligible to become the DR (those with a positive, nonzero router priority). You mustalso configure a PollInterval for the network.

NBMA neighbors list and priorities

NBMA interfaces with a positive, nonzero-value router priority can become the DR for theNBMA network and are configured with a list of all attached routers, or neighbors. Thisneighbors list includes the IP address and router priority for each neighbor.

The neighbors list is used during and after the DR-election process. When an interface to anonbroadcast network with a nonzero priority becomes active, and before the Hello Protocolelects a DR, the router sends hello packets only to those neighbors eligible to become the DR(or those with a positive nonzero router priority). When a DR is elected, it forms adjacenciesonly with configured neighbors and drops all packets from other sources. This neighborconfiguration communicates the expected hello behavior of each neighbor to the router.

Important:If a router that is eligible to become the DR receives a hello packet from a neighbor showinga priority different from the current configured neighbor priority, the DR changes theconfigured priority to match the dynamically learned priority.

NBMA PollInterval

A PollInterval also configures an NBMA interface. The PollInterval designates the interval atwhich OSPF sends hello packets to inactive neighboring routers. OSPF typically sends hellopackets at the HelloInterval, for example, every 10 seconds. If a neighboring router becomesinactive or receives no hello packets for the established RouterDeadInterval, the NBMAinterface sends hello packets at the specified PollInterval, for example, every 120 seconds.

Sending hello packets

You must configure a neighbors list for the DR to allow an NBMA network to send hello packets.If the router is eligible to become a DR (if the router priority is a positive nonzero value), itperiodically sends hello packets to all neighbors that are also eligible. Any two eligible routersmust always exchange hello packets for the correct DR election. Minimize the number ofeligible routers on a nonbroadcast network to minimize the number of hello packets sent onthat network.



A newly elected DR sends hello packets to all manually configured neighbors, synchronizesthe link-state databases, establishes itself as DR, and identifies the BDR.

If a router is not eligible to become the DR, it periodically sends hello packets to both the DRand the BDR. The router also sends a hello packet in reply to a hello packet received from anyeligible neighbor (other than the current DR and BDR). This process establishes an initialbidirectional relationship with any potential DR.

When hello packets are being periodically sent, the neighbor state determines the intervalbetween the packets. If the neighbor is in the down state, the neighbor sends hello packets atthe designated PollInterval, for example, every 120 seconds. Otherwise, neighbors send hellopackets at the designated HelloInterval, for example, every 10 seconds.

Forming adjacencies

In an NBMA network, as in a broadcast network, all routers become adjacent to the DR andthe BDR. The adjacencies form after the router priorities are assigned, the neighbors areconfigured, and the network DR is elected.

OSPF and IP

OSPF runs on top of IP, which means that nodes send an OSPF packet with an IP data packetheader. The protocol field value in the IP header is 89, which identifies it as OSPF anddistinguishes it from other packets that use an IP header.

An OSPF route advertisement expresses a destination as an IP address and a variable-lengthmask. The address and the mask indicate the range of destinations to which the advertisementapplies.

OSPF can specify a range of networks and can send one summary advertisement thatrepresents multiple destinations. For example, a summary advertisement for the destination128.185.0.0 with a mask of 255.255.0.0 describes a single route to destinations 128.185.0.0to 128.185.255.255.

OSPF packets

All OSPF packets start with a 24-octet header containing information about the OSPF version,the packet type and length, the ID of the router transmitting the packet, and the ID of the OSPFarea from which the packet is sent. An OSPF packet is one of the following types:

• Hello packets

Hello packets transmit between neighbors and are never forwarded. The Hello Protocolrequires routers to send hello packets to neighbors at predefined hello intervals. If therouter receives no hello packets within the specified dead interval, the neighbor routerdeclares the other router dead.

• Database description (DD) packets

Routing


OSPF exchanges DD packets when a link is first established between neighboring routersthat synchronize the link-state databases.

• Link-state request packets

Link-state request packets describe one or more link-state advertisements that a routerrequests from a neighbor. Routers send link-state requests if the information received inDD packets from a neighbor is not consistent with the router's link-state database.

• Link-state update packets

Link-state update packets contain one or more link-state advertisements and are sentfollowing a change in network conditions.

• Link-state acknowledgement packets

Link-state acknowledgement packets acknowledge receipt of link-state updatescontaining the header information from the received link-state advertisements.

Link-state advertisements

OSPF does not require each router to send the entire routing table to the neighbors. Instead,each OSPF router floods only link-state change information in the form of link-stateadvertisements (LSAs) throughout the area or AS. LSAs in OSPF are one of the following sixtypes:

• Router-links advertisement

A router originates one or more router LSAs for an area. Each router LSA containsinterface descriptions. The router LSAs for an area describe the states of all the routerinterfaces to the area. Link-state ID fields distinguish multiple router LSAs.

• Network-links advertisement

The link designated router originates a network LSA for every broadcast or NBMA linkhaving two or more attached routers. The network LSA lists all routers attached to thelink.

• Inter-area-prefix links advertisement

The inter-area-prefix links advertisement describes an external prefix that is internal tothe autonomous system.

• Inter-area-router links advertisement

The inter-area-router links advertisement describes a path to a destination external OSPFrouter (an ASBR) that is internal to the Autonomous System.

• As-external links advertisement

The as-external links advertisement describes a path to a prefix. The described path isexternal to the Autonomous System.

• link LSA



OSPFv3 includes link LSA for the following three purposes:

- to provide the router link-local address to other routers on a link

- to distribute the prefixes associated with the link to routers on the link

- to allow the router to insert option bits to the network LSA

AS external routes

With OSPF, the following routes are AS external (ASE) routes:

• a route to a destination outside the AS

• a static route

• a default route

• a directly connected network not running OSPF

OSPF virtual links

On an OSPF network, an Avaya Ethernet Routing Switch 8800/8600 that is an ABR mustconnect directly to the backbone. If no physical connection is available, you can configure avirtual link automatically or manually.

An automatic virtual link provides redundancy support for critical network connections.Automatic virtual linking creates virtual paths for vital traffic paths in your OSPF network. Thevirtual link is available to maintain connectivity if a network connection fails, such as when aninterface cable connected to the backbone (either directly or indirectly) disconnects from theswitch.

Specifying automatic virtual linking ensures that a link is created to another router. When youspecify automatic virtual linking, the feature is always ready to create a virtual link. Createmanual virtual links if automatic virtual linking uses more resources than you want to use. Withvirtual links, you can conserve resources, while having specific control over virtual linkplacement in your OSPF configuration.

Figure 8: Virtual link between ABRs through a transit area on page 44 shows how to configurea virtual link between the ABR in area 2.2.2.2 and the ABR in area 0.0.0.0.

Routing


Figure 8: Virtual link between ABRs through a transit area

To configure a virtual link between the ABRs in Area 1 and Area 3, define Area 2 as the transitarea between the two areas. Identify R2 as the neighbor router, through which R2 must sendinformation to reach the backbone through R1.

Specifying ASBRs

ASBRs advertise non-OSPF routes into OSPFdomains so that they can pass through theOSPF routing domain. A routercan function as an ASBR if one or more of the router interfacesconnectsto a non-OSPF network.

Limit the number of ASBRs in your network to conserve resources, or to specifically controlwhich routers perform as ASBRs to control traffic flow.

OSPF routing algorithm

A separate copy of the OSPF routing algorithm runs in each OSPF area. Routers that connectto multiple areas run multiple copies of the algorithm. The processes governed by the routingalgorithm are as follows:

• When a router starts, it initializes the OSPF data structures and then waits for indicationsfrom lower level protocols that the interfaces are functional.

• A router uses the Hello Protocol to discover neighbors. On point-to-point and broadcastnetworks, the router dynamically detects neighbors by sending hello packets to the



multicast address AllSPFRouters. On nonbroadcast multiaccess networks, someconfiguration information is required to discover neighbors.

• On all multiaccess networks (broadcast or nonbroadcast), the Hello Protocol elects adefault router (DR) for the network.

• The router attempts to form adjacencies with some neighbors. On multiaccess networks,the DR determines which routers become adjacent. This behavior does not occur if arouter is configured as a passive interface because passive interfaces do not formadjacencies.

• Adjacent neighbors synchronize topological databases.

• The router periodically advertises the link state and changes to the local state. LSAsinclude information about adjacencies to enable quick detection of dead routers on thenetwork.

• LSAs flood throughout the area to ensure that all routers in an area use the sametopological database.

• From the database, each router calculates a shortest-path tree, with itself as root. Thisshortest-path tree yields a routing table for the protocol.

OSPFv3This section is an overview of the differences between Open Shortest Path First (OSPF)v3protocol, developed for IPv6, and OSPFv2, used in IPv4. This information is compiled fromRFC2740.

The IPv4 terms subnet and network are replaced in IPv6 by link. An IPv6 link is acommunication medium between nodes at the link layer. You can assign multiple IP subnets(prefixes) to a link. Two IPv6 nodes with common or different prefixes can communicate overa single link.

OSPF for IPv6 operates on each link rather than each subnet as in IPv4. IPv6 makes thefollowing changes to how packets are received and to the contents of network LSAs and hellopackets:

• The OSPF packet contains no IPv6 addresses. LSA payloads carried in link state updatepackets contain IPv6 addresses.

• The following IDs remain at 32-bits and are not assigned IPv6 addresses: area IDs, LSAlink state IDs, and OSPF router IDs.

• Router IDs identify neighboring routers by an IP address on broadcast and NBMAnetworks in OSPFv2.

OSPFv3


Flooding scopeLSA flooding scope is generalized in OSPFv3 and coded in the LS type field of the LSA. Thefollowing 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 router LSAs,network LSAs, Inter-Area-Prefix-LSAs, Inter-Area-Router LSAs, and Intra-Area-Prefix-LSAs.

• AS scope: The LSA is flooded through the routing domain. AS scope is used for AS-external-LSAs.

Multiple instances per linkOSPFv3 supports multiple OSPF protocol instances on a single link. For example, you canconfigure a single link in two or more OSPF areas.

An Instance ID in the OSPF packet header and the OSPF interface structures allow multipleprotocol instances on a single link.

Link-local addressesIPv6 uses link-local addresses on a single link. Link-local addresses facilitate features suchas neighbor discovery and autoconfiguration. Datagrams with link-local sources are notforwarded. 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-localunicast address. Routers learn link-local addresses for all other nodes on links. The next-hopinformation during packet forwarding includes the learned addresses.

For OSPF protocol packets, you must use global scope or site-local IP addresses as the sourcefor packets.

Link LSA is the only OSPF LSA type that includes link-local addresses. Link-local addressesmust not be advertised in other LSA types.



AuthenticationOSPF for IPv6 requires the IP Authentication Header and the IP Encapsulating SecurityPayload for authentication and security. OSPFv3 does not support the authentication featurefrom OSPFv2.

IPv6 uses the 16-bit one's complement checksum to protect against accidental datacorruption.

Packet formatOSPFv3 runs directly over IPv6. All other addressing information is absent in OSPF packetheaders. OSPFv3 is network-protocol-independent. LSA types now contain addressinginformation.

OSPFv3 implements the following packet changes:

• The hello packet and database description packet operations fields are expanded to 24bits.

• The packet header does not include Authentication and AuType fields.

• The interface ID replaces the address information in the hello packet. The Interface IDbecomes the network LSA link state ID if the router becomes the designated router onthe link.

• R-bit and V6-bit in the options field process router LSAs during Shortest Path First (SPF)calculation. R-bits and V6-bits determine participation in topology distribution.

• The packet header includes the Instance ID, which allows multiple OSPF protocolinstances on the same link.

R-bitUnlike OSPF for IPv4, OSPFv3 for IPv6 supports the R-bit (Router bit). The R-bit indicateswhether the originating node is an active router.

If the R-bit is cleared, routes that transit the advertising node cannot be calculated.

As an example, if a multi-homed host wishes to participate in routing without forwarding non-locally addressed packets, the R-bit is cleared.

Note that this means that an IPv6-enabled switch can continue to operate as an OSPFv3neighbor even if you disable IPv6 forwarding on the switch. This behavior differs from IPv4OSPF, in which the switch drops a neighbor if IP forwarding on the neighbor is disabled.

OSPFv3


New LSAsOSPFv3 includes link LSAs and Intra-Area-Prefix LSAs.

Link LSA

Link LSA uses local-link flooding scope, not flooded beyond the associated link.

Link LSAs have three purposes:

• to provide the link-local address of the router 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 inrouter LSAs and Network LSAs.

Unknown LSA typesIn OSPFv3, unknown LSA types are either stored and flooded as though understood or givenlocal flooding scope. Specific behavior is coded in the LS type field of the header.

Stub areaOSPFv3 retains the concept of stub areas, which minimize link-state databases and routingtable sizes.

IPv6 stub areas carry only router LSAs, network LSAs, Inter-Area-Prefix-LSAs, link LSAs, andIntra-Area-Prefix-LSAs.

Unlike IPv4, IPv6 can store LSAs with unrecognized link state (LS) types or flood them asthough they are understood. Rules applied to the stub area prevent the excessive growth ofthe link-state database. An LSA with an unrecognized link state can be flooded only if the LSAuses area or link-local flooding scope, and the LSA U-bit is configured to 0.



SecurityIPv6 uses the following key security features: Simple Network Management Protocol version3 (SNMPv3) and Secure Shell (SSH). For detailed information, see Avaya Ethernet RoutingSwitch 8800/8600 Security , NN46205-601. This section contains the following topics:

• SNMP version 3 on page 49• Secure Shell on page 52

SNMP version 3SNMPv3 remotely collects management data and configures devices. An SNMP agent is asoftware process that listens on UDP port 161 for SNMP messages. Each SNMP messagesent to the agent contains a list of management objects to either retrieve or modify.

SNMPv3 is an SNMP framework that supplements SNMPv2 with the following:

• new SNMP message formats• security for messages• access control• remote configuration of SNMP parameters

The following sections describe SNMPv3 features:

• Authentication on page 49• Privacy on page 50• Security on page 50• SNMPv3 group option for access policies on page 50• Configuration on page 50• Feature specifics on page 51• User-based security model on page 51

Authentication

The message recipient uses authentication within the user-based security model (USM) toverify the message sender and whether the message is altered. USM, HMAC-MD5, andHMAC-SHA-96 support authentication protocols.

Security


Privacy

USM is an encryption protocol for privacy. USM encrypts only the data portion of a message.The header and the security parameters are not encrypted. The privacy protocol supportedusing USM is CBC-DES Symmetric Encryption Protocol.

Security

SNMPv3 security protects against the following:

• Information modification: protects against altering information in transit

• Masquerade: protects against an unauthorized entity that assumes the identity of anauthorized entity

• Message Stream Modification: protects against delaying or replaying messages

• Disclosure: protects against eavesdropping

• Discovery procedure: finds the SnmpEngineID of an SNMP entity for a transport addressor transport endpoint address

• Time synchronization procedure: facilitates authenticated communication betweenentities

SNMPv3 does not protect against the following:

• Denial of service: does not prevent exchanges between a manager and an agent

• Traffic analysis: does not verify the general pattern of traffic between managers andagents

SNMPv3 group option for access policies

The access policy feature in the Avaya Ethernet Routing Switch 8800/8600 determines theaccess level users who connect to the switch by using various services, such as the FileTransfer Protocol (FTP), Trivial FTP (TFTP), Telnet, and rlogin. The system access policyfeature is based on the access levels and the network address of the user. This feature coversservices such as TFTP, HTTP, SSH, rlogin, and SNMP. With SNMPv3, community names donot map to an access level. Only the view-based Access Control Model (VACM) determinesthe access privileges.

Configuration

The configuration feature enables access policy services to cover SNMP. Create SNMP usersand associate SNMP users with groups. Configure an access policy for each group andnetwork.



Feature specifics

When you enable SNMP service, this policy covers all users associated with the groupsconfigured under access policy. The access privileges either allow or deny access. If you selectallow, the VACM configuration determines the access level.

The SNMP service default is disabled for all access policies.

The access level configured under access-policy policy <id> does not affect SNMP service.The VACM configuration determines SNMP access rights.

User-based security model

In a user-based security model (USM) system, the security model employs a defined set ofuser identities for any authorized user on an SNMP engine. The users with authorization onone SNMP engine must have authorization on any SNMP engine with which the original SNMPengine communicates.

The USM security model provides the following levels of communication:

• NoAuthNoPriv: communication without authentication and privacy

• AuthNoPriv: communication with authentication and without privacy

• AuthPriv: communication with authentication and privacy

Figure 9: USM association with VACM on page 51 shows the relationship between USM andVACM.

Figure 9: USM association with VACM

Security


View-based Access Control Model

The VACM provides groups access, group security levels, and context based on a predefinedsubset of management information base (MIB) objects. These MIB objects define a set ofmanaged objects and instances.

VACM is the standard access control mechanism for SNMPv3 and provides:

• authorization service to control access to MIB objects at the power distribution unit (PDU)level

• alternative access control subsystems

The access is based on principal, security level, MIB context, object instance, and type ofaccess requested (read/write). VACM MIB defines the policy and permits remotemanagement.

Secure ShellSecure Shell (SSH) is a client/server protocol that specifies how to conduct securecommunications over a network.

SSH supports a variety of the available public and private key encryption schemes. Using thepublic key of the host server, the client and server negotiate to generate a session key knownonly to the client and the server. This one-time key encrypts all traffic between the client andthe server.

Figure 10: Overview of the SSH protocol on page 53 gives an overview of the SSHprotocol.



Figure 10: Overview of the SSH protocol

By using a combination of host, server, and session keys, the SSH protocol provides strongauthentication and secure communication over an unsecure network, offering protection fromthe following security risks:

• IP spoofing• IP source routing• DNS spoofing• man-in-the-middle and TCP hijacking attacks• eavesdropping and password sniffing

Even if network security is compromised, traffic cannot be played back or decrypted, and theconnection cannot be hijacked.

The secure channel of communication provided by SSH does not provide protection againstbreak-in attempts or denial-of-service (DoS) attacks.

The SSH protocol supports the following security features:

• Authentication: identifies the SSH client. During logon, the SSH client is queried for adigital proof of identity.

Supported authentications are RSA (SSH-1), DSA (SSH-2), and passwords (both SSH-1and SSH-2).

• Encryption: scrambles data rendering it unintelligible except to the receiver.

Supported encryptions are AES and 3DES.• Integrity: guarantees that the data is transmitted from the sender to the receiver without

alteration. If any third party captures and modifies the traffic, the SSH server detects thisalteration.

Secure Shell


Important:Currently, 3DES is the only supported encryption algorithm for the Avaya Ethernet RoutingSwitch 8800/8600. Proper functioning requires the 3DES encryption image.

The implementation of the SSH server on the Avaya Ethernet Routing Switch 8800/8600enables the SSH client to securely connect to the Avaya Ethernet Routing Switch 8800/8600and supports commercially available SSH clients.

Important:You must use the CLI to initially configure SSH. You can use Enterprise Device Manager tochange the SSH configuration parameters. Avaya recommends that you use the consoleport to configure the SSH parameters.

SSH version 2 (SSH-2)SSH protocol, version 2 (SSH-2) is a complete upgrade of the SSH-1 protocol. While SSH-1contains multiple functions in a single protocol, SSH-2 functions are divided among thefollowing three protocols:

• SSH transport layer (SSH-TRANS)

The SSH transport layer manages the server authentication and provides the initialconnection between the client and the server. When a connection is established, thetransport layer provides a secure, full-duplex connection between the client and theserver.

• SSH authentication protocol (SSH-AUTH)

The SSH authentication protocol runs on top of the SSH transport layer and authenticatesthe client-side user to the server. SSH-AUTH defines three authentication methods: publickey, host-based, and password. SSH-AUTH provides a single authenticated tunnel forthe SSH connection protocol.

• SSH connection protocol (SSH-CONN)

The SSH connection protocol runs on top of the SSH transport layer and authenticationprotocols. SSH-CONN provides interactive logon sessions, remote execution ofcommands, forwarded TCP/IP connections, and forwarded X11 connections. Theseservices multiplex into the single encrypted tunnel provided by the SSH transport layer.

Figure 11: SSH version 2 protocols on page 55 shows the SSH-2 protocols.



Figure 11: SSH version 2 protocols

The modular approach of SSH-2 improves on the security, performance, and portability of theSSH-1 protocol.

Important:The SSH-1 and SSH-2 protocols are not compatible. While the SSH implementation on theAvaya Ethernet Routing Switch 8800/8600 supports both versions of SSH, Avayarecommends the more secure version, the SSH-2 protocol.

Secure Shell


Access policy extensionsThe access policy feature controls the admittance of the incoming connections though variousapplications such as HTTP, SNMPv3, Telnet and SSH. The access is controlled at two levels:

• the source IP address (IPv4 or IPv6)

• the logon access level, that is, read-only (ro), read-write (rw), read-write-all (rwa), and, inthe case of SNMP, extra configuration for groups

The first check, performed at the PDU level, determines if an action is allowed based on theaccess configuration.

For SNMP, version 3 provides a group option in the access policy. See SNMP version 3 onpage 49.

Any modifications in the access policy entry can affect the existing application session.

The following modifications result in changes to established TCP-based connections:

• Disallowing connections from the host or network for the entry in the access policy table

• Deleting an entry

• Reducing the access level; that is; ro/rw/rwa.

This results in a session logoff to clear the cached entry and forces the user to log onagain. The new logon information is verified according to the configuration.

• Increasing the access level

Multicast link discoveryIPv6 routers use multicast link discovery (MLD) 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 multicastrouter learns, for each directly attached link, which multicast addresses and which sourceshave listeners on that link. The information that MLD gathers is provided to the multicast routingprotocols that the router uses. This information ensures that multicast packets arrive at all linkswhere listeners require such packets.

A multicast router can itself be a listener of one or more multicast addresses. That is, the routerperforms both the multicast router role and the multicast address listener part of the protocol.



The router collects the multicast listener information needed by the multicast routing protocoland informs itself and other neighboring multicast routers of the listening state.

MLD versions 1 and 2The purpose of the MLD protocol in the IPv6 multicast architecture is to allow an IPv6 routerto discover the presence of multicast listeners on directly attached links and to discover whichmulticast addresses are of interest to neighboring nodes. MLD is the direct IPv6 replacementfor the IGMP protocol used in IPv4. The MLD implementation described in this document isbased on the MLDv2 standard, which is a backward-compatible update to the MLDv1standard.

QoS and IPv6 filtersUse filtering to block unwanted traffic from entering a switch or to prioritize required traffic.Filtering is critical to efficient bandwidth management and network protection. You determinewhich packets receive special handling based on information in the packet headers.

Traffic filters instruct an interface to selectively handle specified traffic. Using traffic filters, youcan reduce network congestion and control access to network resources by blocking,forwarding, or prioritizing specified traffic on an interface. You can apply multiple traffic filtersto a single interface.

If you configure IPv6 attributes for an access control template (ACT), you must configure anaccess control list (ACL) of type IPv6. If you configure only Ethernet attributes for an ACT, youcan configure two ACLs: one of type IPv4 and one of type IPv6.

For additional information about QoS and IP filters, see Avaya Ethernet Routing Switch8800/8600 Configuration — QoS and IP Filtering, NN46205-507.

License informationThe IPv6 feature requires an Advanced License. For more information about licenses, seeAdministration, NN46205-605.

IPv6 DHCP RelayThe Dynamic Host Configuration Protocol (DHCP) for IPv6 (RFC 3315) enables DHCP serversto pass configuration parameters such as IPv6 network addresses to IPv6 nodes. DHCP

QoS and IPv6 filters


supports automatic allocation of reusable network addresses and of additional configurationparameters.

To request the assignment of one or more IPv6 addresses, a client first locates a DHCP serverand then requests the assignment of addresses and other configuration information from theserver. The client sends a Solicit message to the All_DHCP_Relay_Agents_and_Servers(FF02::1:2) multicast address to find available DHCP servers. Any server that can meet theclient's requirements responds with an Advertise message. The client then chooses one of theservers and sends a Request message to the server asking for confirmed assignment ofaddresses and other configuration information. The server responds with a Reply messagethat contains the confirmed addresses and configuration.

IPv6 DHCP clients use link-local addresses to send and receive DHCP messages. To allow aDHCP client to send a message to a DHCP server that is not attached to the same link, youmust configure a DHCP relay agent on the client's link to relay messages between the clientand server. The operation of the relay agent is transparent to the client.

A relay agent relays messages from clients and messages from other relay agents.

Remote IDIPv6 DHCP Relay supports the Remote ID parameter (RFC 4649). When you enable RemoteID on the switch, the relay agent adds information about the client to DHCPv6 messages beforerelaying the messages to the DHCP server. The server can use the supplied information in theprocess of assigning the addresses, delegated prefixes and configuration parameters that theclient is to receive.

The remote ID option contains two fields:

• enterprise-number• remote-id

On the Ethernet Routing Switch 8800/8600, the enterprise-number (vendor ID) used is 1584and the remote-id field is filled with the unique MAC address of the client.

IPv6 VRRPFor IPv6 hosts on a LAN to learn about one or more default routers, IPv6-enabled routers sendRouter Advertisements using the IPv6 Neighbor Discovery (ND) protocol. The routers multicastthese Router Advertisements every few minutes.

The ND protocol includes a mechanism called Neighbor Unreachability Detection to detect thefailure of a neighbor node (router or host) or the failure of the forwarding path to a neighbor.Nodes can monitor the health of a forwarding path by sending unicast ND Neighbor Solicitationmessages to the neighbor node. To reduce traffic, nodes only send Neighbor Solicitations toneighbors to which they are actively sending traffic and only after the node receives no positiveindication that the neighbors are up for a period of time. Using the default ND parameters, ittakes a host approximately 38 seconds to learn that a router is unreachable before it switches



to another default router. This delay is very noticeable to users and causes some transportprotocol implementations to timeout.

While you can decrease the ND unreachability detection period by modifying the NDparameters, the current lower limit that can be achieved is five seconds, with the addeddownside of significantly increasing ND traffic. This is especially so when there are many hostsall trying to determine the reachability of one of more routers.

To provide fast failover of a default router for IPv6 LAN hosts, the Avaya Ethernet RoutingSwitch 8800/8600 supports the Virtual Router Redundancy Protocol (VRRP v3) for IPv6(defined in draft-ietf-vrrp-ipv6-spec-08.txt).

VRRPv3 for IPv6 provides a faster switchover to an alternate default router than is possibleusing the ND protocol. With VRRPv3, a backup router can take over for a failed default routerin approximately three seconds (using VRRPv3 default parameters). This is accomplishedwithout any interaction with the hosts and with a minimum amount of VRRPv3 traffic.

The operation of Avaya's IPv6 VRRP implementation is similar to the existing IPv4 VRRPoperation, including support for hold-down timer, critical IP, fast advertisements, and backupmaster. With backup master enabled, the backup switch routes all traffic according to its routingtable. It does not Layer 2-switch the traffic to the VRRP master.

New to the IPv6 implementation of VRRP, you must specify a link-local address to associatewith the virtual router. Optionally, you can also assign global unicast IPv6 addresses toassociate with the virtual router. Network prefixes for the virtual router are derived from theglobal IPv6 addresses assigned to the virtual router.

With the current implementation of VRRP, one active master switch exists for each IPv6network prefix. All other VRRP interfaces in a network are in backup mode.

On an Avaya Ethernet Routing Switch 8800/8600, you cannot directly check or set the virtualIP address on the standby CPU module. To check or set the virtual IP address on the standbyCPU, you must configure the virtual IP address on the master CPU, save it to the config.cfgfile, and then copy that file to the standby CPU module.

VRRPv3 operationVRRP makes use of a virtual IP address (transparent to users) shared between two or morerouters connecting the common network prefix to the enterprise network. With the virtual IPaddress as the default gateway on end hosts, VRRP provides dynamic default gatewayredundancy in the event of failover.

VRRP specifies an election protocol that dynamically assigns responsibility for a virtual routerto one of the VRRP routers on a LAN. The VRRP router controlling the IP addresses associatedwith a virtual router is called the Master router. The Master router forwards packets sent to thevirtual router IP addresses. The election process provides dynamic failover in the forwardingresponsibility if the Master becomes unavailable.

In the following figure, the first three hosts install a default route to the R1 (virtual router 1) IPaddress and the other three hosts install a default route to the R2 (virtual router 2) IP address.

IPv6 VRRP


For VRID 1, R1 is the master and R2 is the backup. For VRID 2, R2 is the master and R1 isthe backup.

This configuration not only shares the load of the outgoing traffic, but it also provides fullredundancy. If either router fails, the other router assumes responsibility for both addresses.

Figure 12: Virtual Router Redundancy Protocol configuration

When a VRRP router is initialized, if it is the IP address owner, it asserts itself as the masterrouter with a priority of 255 and it sends a VRRP advertisement. The VRRP router also sendsunsolicited ND Neighbor Advertisements and ND Router Advertisements containing the virtualrouter MAC address for each IP address associated with the virtual router. The VRRP routerthen transitions to the controlling state.

In the controlling state, the VRRP router functions as the forwarding router for the IP addressesassociated with the virtual router. It responds to ND Neighbor Solicitation and ND RouterSolicitation messages for these IP addresses, forwards packets with a destination MACaddress equal to the virtual router MAC address, and accepts only packets addressed to IPaddresses associated with the virtual router if it is the IP address owner.

If the VRRP router is initialized and the priority is not 255, the router transitions to the backupstate to ensure that all Layer 2 switches in the down path relearn the new origin of the VRRPMAC addresses.

In the backup state, a VRRP router monitors the availability and state of the master router. Itdoes not respond to ND Neighbor Solicitation and ND Router Solicitation messages for virtualrouter IP addresses and discards packets with a MAC address equal to the virtual router MACaddress. It does not accept packets addressed to IP addresses associated with the virtualrouter. If a shutdown occurs, it transitions back to the initialize state. If the master router goesdown, the backup router sends the VRRP advertisement and unsolicited ND NeighborAdvertisements and ND Router Advertisements described in the preceding paragraphs andtransitions to the controlling state.



VRRP advertisements and master router failoverWhen a VRRP router is initialized, if it is the IP address owner, its priority is 255 and it sendsa VRRP advertisement. The master router then continues to send advertisement messagesat the advertisement interval period.

The other VRRP routers transition to the backup state in the following situations:

• if the priority in the received advertisement is greater than the local priority

• if the priority in the received advertisement is the same as the local priority and the primaryIP address of the sender is greater than the local primary IP address

The backup routers use the advertisements from the master router as a keepalive to monitorthe health of the master router. If the backup router does not receive an advertisement duringthe master downtime interval, calculated as 3 * advertisement interval, then the master routeris declared down.

If a shutdown occurs, the master router sends a VRRP advertisement with a priority of 0 andtransitions to the initialize state.

The priority value 0 indicates that the master router has stopped participating in VRRP. Thistriggers the backup router to transition to the master state without waiting for the current masterto time out.

VRRP termsThe following terms are specific to VRRP:

• VRRP router—a router running the VRRP protocol

•Virtual router—an abstract object acting as the default router for one or more hosts,consisting of a virtual router ID and a set of addresses

• IP address owner—the VRRP router that has virtual router IP addresses as real interfaceaddresses (the router that responds to packets sent to this IP address.)

• Primary IP address—an IP address selected from the real addresses and used as thesource address of packets sent from the router interface (The virtual router master sendsVRRP advertisements using this IP address as the source.)

• Virtual router master—the router assuming responsibility for forwarding packets sent tothe IP address associated with the virtual router and answering ARP requests for theseIP addresses

• Virtual router backup—the virtual router that becomes the master router if the currentmaster router fails

IPv6 VRRP


ScalingThe Avaya Ethernet Routing Switch 8800/8600 supports 255 VRRP interfaces for eachswitch.

Critical IP addressWithin a VRRP VLAN, one link can go down while the remaining links in the VLAN remainoperational. Because the VRRP VLAN continues to function, a virtual router associated withthat VLAN does not register a master router failure.

As a result, if the local router IP interface connecting the virtual router to the external networkfails, this does not automatically trigger a master router failover.

The critical IP address resolves this issue. If the critical IP address fails, it triggers a failover ofthe master router.

You can specify the local router IP interface uplink from the VRRP router to the network as thecritical IP address. This ensures that, if the local uplink interface fails, VRRP initiates a masterrouter failover to one of the backup routers.

In the following figure, the local network uplink interface on R1 is shown as the critical IPaddress for R1. As well, the similar network uplink is shown as the critical IP address for R2.R2 also requires a critical IP address for cases in which it assumes the role of the masterrouter.

Figure 13: VRRP with critical IP

The critical address can be any one of the global unicast IPv6 addresses assigned to any localIPv6 interfaces.



Hold-down timerThe hold-down timer is a proprietary Avaya enhancement to VRRP. When a master routertransitions to a backup router after a critical IP failure, one of the backup routers is elected asthe master router. When the critical IP of the original master router (now a backup router) isrestored, that router remains in the backup state for a period which can be specified by thehold-down timer. The hold-down timer allows the master router enough time to detect andupdate the dynamic routes. The timer delays the preemption of the master over the backup,when the master becomes available. If the hold-timer is configured to 0, it becomes the masterrouter immediately. Otherwise, it transitions to the master state only after the hold-down timertimes out.

Note that the hold-down timer is not employed during failovers caused by the VRRP routerpriority change. It is only for failovers caused by a critical IP failure.

In addition, you can manually force the preemption of the master over the backup before thedelay timer expires.

Avaya recommends that you set all of your routers to the identical number of seconds for thehold-down timer. The hold-down timer has a default value of 0 seconds.

Accept modeWith IPv6 VRRP, the accept mode controls whether a master router accepts packetsaddressed to the address owner's IPv6 address as its own if it is not the IPv6 address owner.The default value is disable.

This parameter is not applicable for VRRP over IPv4.

VRRP backup master with triangular SMLTThe standard implementation of VRRP supports only one active master switch for each IPv6network prefix. All other VRRP interfaces in a network are in backup mode.

A deficiency occurs when VRRP-enabled switches use Split MultiLink Trunking (SMLT). IfVRRP switches are aggregated into two Split MultiLink Trunk switches, the end host traffic isload-shared on all uplinks to the aggregation switches (based on the Multilink Trunk [MLT]traffic distribution algorithm).

However, VRRP usually has only one active routing interface enabled. All other VRRP routersare in backup mode. Therefore, all traffic that reaches the backup VRRP router is forwardedover the interswitch trunk (IST) link toward the master VRRP router. In this case, the IST linkpotentially does not have enough bandwidth to carry all the aggregated traffic.

IPv6 VRRP


To resolve this issue, assign the backup router as the backup master router. The backup masterrouter can actively load-share the routing traffic with a master router.

Because there is an exchange of MAC address tables between the two VRRP peer nodes, theVRRP backup master can forward traffic directly on behalf of the master router. The switch inthe backup master state routes all traffic received on the backup master IP interface accordingto its routing table. It does not Layer 2-switch the traffic to the master router.

As a result, when the backup master router is enabled with SMLT, the incoming host traffic isforwarded over the SMLT links as usual.

The following figure shows a sample VRRP configuration with SMLT. Because the backuprouter is configured as the backup master, routing traffic is load-shared between the twodevices.



Figure 14: VRRP configuration with SMLT

The backup master feature only supports the triangular SMLT topology.

Important:Do not use VRRP backup master and critical IP at the same time. Use one or the other.

VRRP fast advertisment intervalWith the current implementation of VRRP, you can set the advertisement time interval (inseconds) between sending advertisement messages. This permits faster networkconvergence with standardized VRRP failover. However, losing connections to servers formore than a second can result in missing critical failures. Customer network uptime in many

IPv6 VRRP


cases requires faster network convergence, which means network problems must be detectedwithin hundreds of milliseconds.

To meet these requirements, Avaya provides the fast advertisement interval.

The fast advertisement interval is similar to the advertisement interval parameter except forthe unit of measure and the range. The fast advertisement interval is expressed in millisecondsand the range is from 200 to 1000 milliseconds. (This unit of measure must be in multiples of200 milliseconds.)

To configure fast advertisement, you must specify a fast advertisement interval and explicitlyenable the fast advertisement feature. When the fast advertisement feature is enabled, thefast advertisement interval is used instead of the advertisement interval.

When the fast advertisement feature is enabled, VRRP can only communicate with otherEthernet Routing Switches with the same settings.

VRRP considerations with IPv6In an IPv6 VRRP network with SMLT, if you delete the VRRP peers on the aggregationswitches, the VRRP addresses on the access switch are not immediately removed from theIPv6 neighbor table. Instead, the access switch initially displays the IPv6 neighbor states asIncomplete.

In accordance with the ND RFC, neighbor addresses are aged out 30 minutes after the trafficis stopped from a neighbor. In this case, the access switch removes the virtual addresses 30minutes after the VRRP virtual routers are deleted from the two aggregation switches.

IPv6 VRRP and ICMP redirectsIn IPv6 networks, do not enable ICMP redirects on VRRP VLANs. If you enable this option(using the config ipv6 icmp redirect-msg command), VRRP cannot function. Theoption is disabled by default.

IPv6 RSMLTIn many cases, core network convergence time depends on the length of time a routing protocolrequires to successfully converge. Depending on the specific routing protocol, thisconvergence time can cause network interruptions ranging from seconds to minutes.

Avaya Routed Split MultiLink Trunking (RSMLT) permits rapid failover for core topologies byproviding an active-active router concept to core Split MultiLink Trunking (SMLT) networks. Inthe event of core router failures, RSMLT manages packet forwarding, thus minimizing droppedpackets during the routing protocol convergence.



While Avaya’s Routed Split Multilink Trunk (RSMLT) functionality originally provided sub-second failover for IPv4 forwarding only, the Avaya Ethernet Routing Switch 8800/8600extends RSMLT functionality to IPv6. The overall model for IPv6 RSMLT is essentially identicalto that of IPv4 RSMLT. In short, RSMLT peers exchange their IPv6 configuration and trackeach other’s state by means of IST messages. An RSMLT node always performs IPv6forwarding on the IPv6 packets destined to the peer’s MAC addresses. When an RSMLT nodedetects that its RSMLT peer is down, the node also begins terminating IPv6 traffic destined tothe peer's IPv6 addresses.

With RSMLT enabled, an SMLT switch performs IP forwarding on behalf of its SMLT peer –thus preventing IP traffic from being sent over the IST.

IPv6 RSMLT supports the full set of topologies and features supported by IPv4 RSMLT,including SMLT triangles, squares, and SMLT full-mesh topologies, with routing enabled onthe core VLANs.

With IPv6, you must configure the RSMLT peers using the same set of IPv6 prefixes.

Supported routing protocols include the following:

• IPv6 Static Routes• OSPFv3

IPv4 IST with IPv6 RSMLTAvaya Ethernet Routing Switch 8800/8600 does not support the configuration of an IST overIPv6. IST is supported over IPv4 only.

Enabling RSMLT for IPv4 and IPv6To enable IPv6 RSMLT, you must use the same configuration commands provided for IPv4RSMLT. As none of the RSMLT configuration parameters depend on IP-specific information,the configuration commands remain unchanged.

RSMLT configuration is a property of a VLAN. If you enable RSMLT on a VLAN and IPv4 andIPv6 are enabled on the VLAN, then the RSMLT configuration is in effect for both protocols.No additional or separate configuration parameters are available for configuring IPv6RSMLT.

It is not possible to selectively enable or disable RSMLT for IPv4 only or IPv6 only.

Example networkThe following figure shows a sample IPv6 RSMLT topology. It shows a typical redundantnetwork example with user aggregation, core, and server access layers. To minimize thecreation of many IPv6 prefixes, one VLAN (VLAN 1, IP prefix A) spans all wiring closets.

IPv6 RSMLT


RSMLT provides the loop-free topology. The aggregation layer switches are configured withrouting enabled and provide active-active default gateway functionality through RSMLT.

Figure 15: IPv6 RSMLT network example

In the VLAN 3 portion of the network shown in the preceding figure, routers R1 and R2 provideRSMLT-enabled IPv6 service to hosts H1 and H2. Router R1 can be configured as the defaultIPv6 router for H1 and R2 can be the default router for H2. R1 is configured with the link-localaddress of fe80::1, the global unicast address 2003::1, and the routing prefix of 2003::/64 (asa shorthand, the last two items are referred to as 2003::1/64). R2 is configured with fe80::2and 2003::2/64.

Host H1 sends its IPv6 traffic destined to VLAN 1 to R1’s MAC address (after resolving thedefault router address fe80::1 to R1’s MAC). H2 sends its traffic to R2’s MAC. When an IPv6packet destined to R1's MAC address is received at R2 on its SMLT links (which is the expectedMLT behavior), R2 performs IPv6 forwarding on the packet and does not bridge it over the IST.The same behavior occurs on R1.



At startup, R1 and R2 use the IST link to exchange full configuration information including MACaddress for the IPv6 interfaces residing on SMLT VLAN 3.

When R2 detects that the RSMLT in R1 transitions to the DOWN state (for example, if R1 itselfis down, or its SMLT links are down, or the IST link is down) R2 takes over IPv6 terminationand IPv6 Neighbor Discovery functionality on behalf or R1’s IPv6 SMLT interface. Specifically:

• When the above event is detected, R2 transmits an unsolicited IPv6 NeighborAdvertisement for each IPv6 address configured on R1’s SMLT link using R1’s MACaddress (fe80::1 and 2003::1 in this example).

• R2 also transmits an unsolicited Router Advertisement for each of R1’s routing prefixes(unless R1’s prefixes are configured as “not advertised”).

• R2 responds to Neighbor Solicitations and (if configuration allows) Router Advertisementson behalf of R1

• R2 terminates IPv6 traffic (such as pings) destined to R1’s SMLT IPv6 addresses

When R1’s RSMLT transitions back into the UP state and the HoldDown timer expires itresumes IPv6 forwarding and R2 ceases to terminate IPv6 traffic on R1’s behalf.

Note that IPv6 allows a rich set of configuration options for advertising IPv6 routing prefixes(equivalent to IPv4 subnets) and configuring hosts on a link. A prefix can be configured to beor not to be advertised, to carry various flags or lifetime. These parameters affect how hostscan (auto)configure their IPv6 addresses and select their default routers. Most relevant fromthe RSMLT perspective is that an RSMLT node fully impersonates its peer’s IPv6 configurationand behavior on the SMLT link – whatever its configuration happens to be. The above networkexample illustrates one of the many possible deployment schemes for IPv6 routers and hostson a VLAN.

RSMLT provides both router failover and link failover. For example, if the Split MultiLink Trunklink between R2 and R4 is broken, the traffic fails over to R1 as well.

Router R1 recoveryAfter R1 reboots after a failure, it becomes active as a VLAN bridge first. Packets destined toR1 are switched, using the bridging forwarding table, to R2. R1 operates as a VLAN bridge fora period defined by the hold-down timer.

After the hold-down time expires and the routing tables converge, R1 starts routing packetsfor itself and also for R2. Therefore, it does not matter which of the two routers is used as thenext hop from R3 and R4 to reach IPv6 prefix 2003::/64.

When an IPV6 RSMLT peer recovers, the peer installs a temporary default route in the IPv6routing table to point all the IPv6 traffic to the IST peer IP address for the hold down time. (Thisis the same behavior as in IPv4 RSMLT.)

IPv6 RSMLT


Hold-up timerWhen both RSMLT peers are active, both peers forward traffic for each other. When a routerdetects that its peer is down, it begins terminating IPv6 traffic destined to the peer's IPv6addresses (including, for example, responding to pings and router solicitations). The routercontinues to forward and terminate traffic for its peer for a duration defined by the hold-up timer.If the peer is not restored and the hold-up timer expires, the router stops forwarding andterminating traffic for the peer.

You can set the hold-up timer (in the preceding example, the amount of time R2 routes for R1in a failure) for a time period greater than the routing protocol convergence. You can also setit as infinite (that is, the members of the pair always route for each other).

Avaya recommends that you use an infinite (9999) hold-up timer value for applications thatuse RSMLT at the edge instead of VRRP.

RSMLT or VRRPFor VLAN 1, VRRP with a backup master can provide the same functionality as RSMLT, aslong as no additional router is connected to IPv6 prefix 2003::/64.

RSMLT provides superior router redundancy in core networks (IPv6 prefix B), where OSPFv3is used for the routing protocol. Routers R1 and R2 provide router backup for each other, notonly for the edge IP Prefix 2003::/64, but also for the core IPv6 prefix B. Similarly routers R3and R4 provide router redundancy for IPv6 prefix C and also for core IPv6 prefix B.

Avaya does not recommend that you both VRRP and RSMLT on the same VLAN. Use one orthe other.

Coexistence with IPv4 RSMLTThe IPv6 RSMLT feature introduces no changes to the existing IPv4 RSMLT state machineincluding RSMLT configuration, definitions of events, logic of state transitions, or timeroperations. A single instance of state and configuration parameter set controls both IPv4 andIPv6 RSMLT logic. With the introduction of this feature, RSMLT is best thought of as a propertyof the VLAN layer as opposed to the IP (v4 or v6) layer above it. RSMLT configuration andstates affect IPv4 and IPv6 operation simultaneously.



For a given SMLT VLAN RSMLT is supported for any of the following scenarios:

• IPv4 Only: IPv4 is configured on the VLAN and IPv6 is not. RSMLT operation and logicremains unchanged from the current implementation.

• IPv6 Only: IPv6 is configured on the VLAN and IPv4 is not. IPv6 RSMLT operation followsthat of IPv4 as described in this document.

• IPv4 and IPv6: Both IPv4 and IPv6 are configured on the VLAN. IPv4 RSMLT operationand logic remains unchanged from the current implementation and unaffected by IPv6.IPv6 operation follows that of IPv4 as described in this document.

RSMLT network design and configurationBecause RSMLT is based on SMLT, all SMLT configuration rules apply. In addition, RSMLT isenabled on the SMLT aggregation switches for each VLAN. The VLAN must be a member ofSMLT links and the IST trunk. For more information about configuring SMLT in a Layer 2environment, see Avaya Ethernet Routing Switch 8800/8600 Configuration – Link Aggregation,MLT and SMLT (NN46205-518).

The VLAN also must be routable (IP address configured) and an Interior Routing Protocol (IGP)such as OSPFv3 must be configured on all four routers, although it is independent of RSMLT.You can use any supported routing protocol, even static routes, with RSMLT.

RSMLT pair switches provide backup for each other. As long as one of the two routers of anIST pair is active, traffic forwarding is available for both next hops R1/R2 and R3/R4.

Important:Do not enable ICMP redirects on RSMLT VLANs. If you enable this option (using the configipv6 icmp redirect-msg command), RSMLT cannot function. The option is disabledby default.

RSMLT-edgeRSMLT-edge stores the RSMLT peer MAC/IPv6 address pair in its local configuration file andrestores the configuration if the peer does not restore after a simultaneous reboot of bothRSMLT-peer switches.

The RSMLT-edge feature simply adds an enhancement whereby the peer's MAC (for the IPon the VLAN) gets committed to the config.cfg file after a save config; that way if you poweroff both switches, and then power up only 1 of them, that single switch can still take ownershipof its peer's IP on that VLAN even if it has not yet even seen that peer switch since it booted;this is necessary as you might have configured the peer (the switch which is still down) IP asthe default gateway in end stations.

IPv6 RSMLT


If you enable RSMLT-edge, you must also ensure that the hold-up timer for RSMLT on thoseedge VLANs is set to infinity (9999). This is to ensure that if one cluster switch fails, theremaining cluster switch maintains ownership of its failed peer IPs indefinitely.

It does not matter if that VLAN is tagged over SMLT links, single attached links, or more SMLTlinks; what is possible with VRRP, you can do with RSMLT-edge.

Be sure to save the configuration after you configure RSMLT-edge. This step is required inorder the save the peer MAC address.

RSMLT considerations with OSPFIf you run OSPF with RSMLT in a square or mesh, and a node loses the IST connection to itspeer, OSPF adjacencies can be lost. In this scenario, OSPF is not guaranteed to be in aconsistent state.



Chapter 4: IPv6 routing configuration

Configure IPv6 routing to take advantage of the additional benefits over IPv4 routing such as an increasednumber of possible addresses in your network.

Prerequisites to IPv6 routing configuration• You require R, RS, or 8800 modules for hardware forwarding.

• You must run Avaya Ethernet Routing Switch 8800/8600 Release 4.1 software or later forIPv6 hardware-based forwarding.

• Assign an IPv6 address to the Ethernet SF/CPU port.

IPv6 routing configuration tasksThis work flow shows you the sequence of tasks you perform to configure IPv6 routing on theAvaya Ethernet Routing Switch 8800/8600.


Figure 16: IPv6 routing configuration tasks

IPv6 routing configuration


IPv6 routing configuration navigation• Basic IPv6 configuration using Enterprise Device Manager on page 77

• Basic IPv6 configuration using the CLI on page 99

• Basic IPv6 configuration using the ACLI on page 121

• IPv6 routing configuration using Enterprise Device Manager on page 137

• IPv6 routing configuration using the CLI on page 159

• IPv6 routing configuration using the ACLI on page 181

• IPv4-to-IPv6 transition mechanism configuration using Enterprise Device Manager onpage 275

• IPv4-to-IPv6 transition mechanism configuration using the CLI on page 281

• IPv4-to-IPv6 transition mechanism configuration using the ACLI on page 287

• Multicast protocol configuration using Enterprise Device Manager on page 293

• Multicast protocol configuration using the CLI on page 299

• Multicast protocol configuration using the ACLI on page 307

• IPv6 traffic filter configuration using Enterprise Device Manager on page 315

• IPv6 traffic filter configuration using the CLI on page 331

• IPv6 traffic filter configuration using the ACLI on page 343

IPv6 routing configuration navigation


IPv6 routing configuration


Chapter 5: Basic IPv6 configuration usingEnterprise Device Manager

This section contains procedures to enable and configure IPv6 on the Avaya Ethernet Routing Switch8800/8600.

This chapter describes Enterprise Device Manager procedures for enabling and configuring IPv6 routingfunctions on the Ethernet Routing Switch 8800/8600. For conceptual information about Layer 3 routingfunctions, see IPv6 routing fundamentals on page 15.

Prerequisites to basic IPv6 configuration• Hardware forwarding requires R, RS, or 8800 modules.

• At least one 8692 SF/CPU with SuperMezz or 8895 SF/CPU module must be installedon your Ethernet Routing Switch 8800/8600.

• Avaya Ethernet Routing Switch 8800/8600 software Release 4.1 or later is required forIPv6 hardware-based forwarding.

Basic IPv6 configuration navigation• Configuring the management port interface on page 78

• Configuring management port addresses on page 79

• Configuring the CPU IPv6 route table on page 80

• Configuring a virtual IPv6 address on page 81

• Adding an IPv6 interface ID to a brouter port or VLAN on page 81

• Assigning IPv6 addresses to a brouter port or VLAN on page 85

• Configuring route advertisement on page 87

• Configuring the neighbor cache on page 91

• Adding a static neighbor to the cache on page 92

• Configuring IPv6 routing and ICMP on page 93


• Configuring an IPv6 discovery prefix on page 94

• Deleting an IPv6 address on page 97

• Deleting an IPv6 interface on page 97

• Deleting an IPv6 discovery prefix on page 98

• Removing an entry from the neighbor cache on page 98

Configuring the management port interfaceThe management port provides switch connectivity and management. As with other ports, youcan configure the management port for routing IPv6 and you can configure a number of IPv6addresses on an interface. The switch does not advertise the management port address to theother ports.

Procedure steps

1. In the Device Physical View tab, select the management port.2. In the navigation tree, open the Configuration > Edit folders.3. Click Mgmt Port..4. Click the Mgmt Port-IPv6 Interface tab.5. Click Insert.6. Edit the fields as required.7. Click Insert.

Variable definitionsUse the data in the following table to configure the management port interface.

Variable ValueIdentifier The IPv6 address interface identifier. This is a binary string of up to

8 octets in network byte-order.

IdentifierLength The length of the interface identifier in bits. The range is 0-64.

Descr A text string containing information about the interface. The networkmanagement system configures this string.

ReasmMaxSize(MTU)

The MTU for this IPv6 interface. This value must be the same for allthe IP addresses defined on this interface. The default value is1500.

Basic IPv6 configuration using Enterprise Device Manager


Variable ValueAdminStatus The indication of whether IPv6 is enabled (true) or disabled (false)

on this interface. This object does not affect the state of the interfaceitself, only its connection to an IPv6 stack. The default is false.

ReachableTime The time (in milliseconds) a neighbor is considered reachable afterreceiving a reachability confirmation. The range is 0-3600000milliseconds.The default value is 30000.

RetransmitTime The time (in milliseconds) between retransmissions of neighborsolicitation messages to a neighbor when resolving the address orwhen probing the reachability of a neighbor. The range is 0-3600000milliseconds.The default value is 1000.

MulticastAdminStatus

The indication of whether multicasting for IPv6 is enabled (up) ordisabled (down) on this interface. The default is false.

Configuring management port addressesConfigure an IPv6 address on the port to use in IPv6 routing. The switch does not advertisethe management port address to the other ports.

Procedure steps

1. In the Device Physical View tab, select the management port.2. In the navigation tree, open the Configuration > Edit folders.3. Click Mgmt Port.4. Click the Mgmt Port-IPv6 Addresses tab.5. Click Insert.6. In the Addr box, type the required IPv6 address for the management port.7. In the AddrLen box, type the number of bits from the IPv6 address to advertise.8. Click Insert.

Variable definitionsUse the data in the following table to configure management port IPv6 addresses.

Variable ValueIfIndex The index value that uniquely identifies the interface to which this entry

applies.

Configuring management port addresses


Variable ValueAddr The IPv6 address to which this addressing pertains.

Important:If the IPv6 address exceeds 116 octets, the object identifiers (OIDS)of instances of columns in this row are more than 128 subidentifiersand you cannot use SNMPv1, SNMPv2c, or SNMPv3 to accessthem.

AddrLen The prefix length value for this address. You cannot change the addresslength after creation. You must provide this value to create an entry inthis table. The range is 0-128.

Type Unicast, the only supported type.

Type The type of address: unicast or anycast. The default is unicast.

Origin A read-only value indicating the origin of the address. The origin of theaddress is other, manual, dhcp, linklayer, or random.

Status A read-only value indicating the status of the address, describing whetherthe address is used for communication. The status is preferred (default),deprecated, invalid, inaccessible, unknown, tentative, or duplicate.

Created A read-only value indicating the value of sysUpTime at the time this entrywas created. If this entry was created prior to the last reinitialization ofthe local network management subsystem, the object contains a zerovalue.

LastChanged A read-only value indicating the value of sysUpTime at the time this entrywas last updated. If this entry was updated prior to the last reinitializationof the local network management subsystem, this object contains a zerovalue.

Configuring the CPU IPv6 route tableEdit the management port CPU route table to specify network and gateway IP addresses usedto remotely manage the device.

Procedure steps

1. In the Device Physical View tab, select the management port.2. In the navigation tree, open the Configuration > Edit folders.3. Click Mgmt Port.4. Click the CPU IPv6 Route Table tab.5. Click Insert.



6. Edit the fields as required.7. Click Insert.

Variable definitionsUse the data in the following table to configure the CPU IPv6 route table.

Variable ValueNetwork The IPv6 destination address.

PrefixLength The number of address bits to advertise. The range is 0-128.

Gateway The IPv6 address of the management port.

Configuring a virtual IPv6 addressConfigure a virtual IPv6 address to make the switch accessible in failover situations.

Procedure steps

1. In the Device Physical View tab, select the chassis.2. In the navigation tree, open the Configuration > Edit folders.3. Click Chassis.

The Chassis tab appears with the System tab selected.4. In the VirtualIPv6Addr box, type the IPv6 address to configure as the virtual IPv6

address.5. In the VirtualIPv6PrefixLength box, type the number of bits from the virtual IPv6

address to advertise.

Adding an IPv6 interface ID to a brouter port or VLANPrerequisites

• You must configure an IPv6 interface for a VLAN or brouter port before you can assignan IPv6 address to the interface.

• You must configure a VLAN before you can give the VLAN an interface identifier or anIPv6 address. The Ethernet Routing Switch 8800/8600 supports port-based, protocol-based, and MAC-source-based VLANs. For information about configuring VLANs, seeAvaya Ethernet Routing Switch 8800/8600 Configuration — VLANs and Spanning Tree,

Configuring a virtual IPv6 address


NN46205-517 and Avaya Ethernet Routing Switch 8800/8600 Configuration — LinkAggregation, MLT, and SMLT, NN46205-518.

Procedure steps

1. In the navigation tree, open the Configuration > IPv6 folders.2. Click IPv6.

Important:Enterprise Device Manager provides multiple paths to configure IPv6 interfacesand addresses. In addition to selecting Configuration > IPv6 > IPv6, you canselect Configuration > VLAN > VLANs (select a VLAN) > IPv6 > Insert , orConfiguration > Edit > Port > IPv6 > Insert.

3. Click the Interfaces tab.4. Click Insert.5. In the IfIndex box, click Port or VLAN, and select a port number or VLAN.6. You must select the AdminStatus check box before the interface takes effect.7. Edit the remaining fields.8. Click Insert.9. Click Apply.

Variable definitionsUse the data in the following table to configure IPv6 interfaces.

Variable ValueIfIndex A unique value to identify a physical interface or a logical interface

(VLAN). For the brouter port, it is the ifindex of the port, and for aVLAN it is the ifindex of the VLAN.

Identifier The IPv6 address interface identifier. This is a binary string of up to8 octets in network byte order.

IdentifierLength The length of the interface identifier in bits.

Descr A text string containing information about the interface. The networkmanagement system also configures this string.

VlanId A value that uniquely identifies the Virtual LAN associated with theentry. This value corresponds to the lower 12 bits in the IEEE 802.1QVLAN tag.

Type The type of interface.

ReasmMaxSize(MTU)

The MTU for this IPv6 interface. This value must be same for all theIP addresses defined on this interface. The default value is 1500.



Variable ValuePhysAddress The media-dependent physical address. For Ethernet, this is a MAC

address.

AdminStatus The indication of whether IPv6 is enabled (true) or disabled (false)on this interface. This object does not affect the state of the interfaceitself, only the connection to an IPv6 stack. The default is false.

OperStatus The current operational status of the interface.

ReachableTime The time (in milliseconds) a neighbor is considered reachable afterreceiving a reachability confirmation message. The default is30000.

RetransmitTime The time (in milliseconds) between retransmissions of neighborsolicitation messages to a neighbor when resolving the address orwhen probing the reachability of a neighbor. The default is 1000.



Adding an IPv6 interface ID to a VLANPrerequisites

• You must configure an IPv6 interface for a VLAN or brouter port before you can assignan IPv6 address to the interface.

• You must configure a VLAN before you can give the VLAN an interface identifier or anIPv6 address. The Ethernet Routing Switch 8800/8600 supports port-based, protocol-based, and MAC-source-based VLANs. For information about configuring VLANs, seeAvaya Ethernet Routing Switch 8800/8600 Configuration — VLANs and Spanning Tree,NN46205-517 and Avaya Ethernet Routing Switch 8800/8600 Configuration — LinkAggregation, MLT, and SMLT, NN46205-518.

Procedure steps

1. In the navigation tree, open the Configuration > VLAN folders.2. Click VLANs.3. Click the Basic tab.4. Select a VLAN to configure.5. Click IPv6.6. Click the IPv6 Interface tab.7. Click Insert.8. You must select the AdminStatus check box before the interface takes effect.9. Edit the remaining fields.

Adding an IPv6 interface ID to a VLAN


10. Click Insert.11. Click Apply.

Variable definitionsUse the data in the following table to configure IPv6 interfaces.


(VLAN). For the brouter port, it is the ifindex of the port, and for aVLAN it is the ifindex of the VLAN.

Identifier The IPv6 address interface identifier. This is a binary string of up to8 octets in network byte order.

IdentifierLength The length of the interface identifier in bits.

Descr A text string containing information about the interface. The networkmanagement system also configures this string.

VlanId A value that uniquely identifies the Virtual LAN associated with theentry. This value corresponds to the lower 12 bits in the IEEE 802.1QVLAN tag.

Type The type of interface.

ReasmMaxSize(MTU)

The MTU for this IPv6 interface. This value must be same for all theIP addresses defined on this interface. The default value is 1500.

PhysAddress The media-dependent physical address. For Ethernet, this is a MACaddress.

AdminStatus The indication of whether IPv6 is enabled (true) or disabled (false)on this interface. This object does not affect the state of the interfaceitself, only the connection to an IPv6 stack. The default is false.

OperStatus The current operational status of the interface.

ReachableTime The time (in milliseconds) a neighbor is considered reachable afterreceiving a reachability confirmation message. The default is30000.

RetransmitTime The time (in milliseconds) between retransmissions of neighborsolicitation messages to a neighbor when resolving the address orwhen probing the reachability of a neighbor. The default is 1000.



MacOffset Specifies a number by which to offset the MAC address of thebrouter port from the chassis MAC address. This ensures that eachIPv6 address has a different MAC address.



Assigning IPv6 addresses to a brouter port or VLANAssign IPv6 addresses to interfaces to configure IPv6 routing for the interface.

Procedure steps

1. In the navigation tree, open the Configuration > IPv6 folders.2. Click IPv6.3. Click the Addresses tab.4. Click Insert.5. In the IfIndex box, click Port or VLAN, and select a port number or VLAN.6. Edit the remaining fields.7. Click Insert.8. Click Apply.

Variable definitionsUse the data in the following table to configure the IPv6 addresses for a brouter port orVLAN.


applies.

Addr The IPv6 address to which this entry addressing information pertains.

Important:if the IPv6 address exceeds 116 octets, the object identifiers (OIDS)of instances of columns in this row are more than 128 subidentifiersand you cannot use SNMPv1, SNMPv2c, or SNMPv3 to accessthem.

AddrLen The prefix length value for this address. You cannot change the addresslength after you create it. You must provide this value to create an entryin this table.



Status A read-only value indicating the status of the address, describingwhether the address is used for communication. The status is preferred

Assigning IPv6 addresses to a brouter port or VLAN


Variable Value(default), deprecated, invalid, inaccessible, unknown, tentative, orduplicate.

Created A read-only value indicating the value of sysUpTime at the time thisentry was created. If this entry was created prior to the lastreinitialization of the local network management subsystem, the objectcontains a zero value.

LastChanged A read-only value indicating the value of sysUpTime at the time thisentry was last updated. If this entry was updated prior to the lastreinitialization of the local network management subsystem, this objectcontains a zero value.

Assigning IPv6 addresses to a VLANAssign IPv6 addresses to interfaces to configure IPv6 routing for the interface.

Procedure steps

1. In the navigation tree, open the Configuration > VLAN folders.2. Click VLANs.3. Click the Basic tab.4. Select a VLAN to configure.5. Click IPv6.6. Click the Addresses tab.7. Click Insert.8. Edit the fields.9. Click Insert.

10. Click Apply.

Variable definitionsUse the data in the following table to configure the IPv6 addresses for a brouter port orVLAN.


applies.

Addr The IPv6 address to which this entry addressing information pertains.



Variable Value

Important:If the IPv6 address exceeds 116 octets, the object identifiers (OIDS)of instances of columns in this row are more than 128 subidentifiersand you cannot use SNMPv1, SNMPv2c, or SNMPv3 to accessthem.

AddrLen The prefix length value for this address. You cannot change the addresslength after you create it. You must provide this value to create an entryin this table.



Status A read-only value indicating the status of the address, describingwhether the address is used for communication. The status is preferred(default), deprecated, invalid, inaccessible, unknown, tentative, orduplicate.

Created A read-only value indicating the value of sysUpTime at the time thisentry was created. If this entry was created prior to the lastreinitialization of the local network management subsystem, the objectcontains a zero value.

LastChanged A read-only value indicating the value of sysUpTime at the time thisentry was last updated. If this entry was updated prior to the lastreinitialization of the local network management subsystem, this objectcontains a zero value.

Configuring route advertisementConfigure route advertisement in IPv6 for neighbor discovery (ND). IPv6 nodes on the samelink use ND to discover link-layer addresses and to obtain and advertise various networkparameters and reachability information. ND combines the services provided by AddressResolution Protocol (ARP) and router discovery for IPv4.

Procedure steps

1. In the navigation tree, open the Configuration > IPv6 folders.2. Click IPv6.3. Click the Route Advertisement tab.4. Edit the fields as required.5. Click Apply.

Configuring route advertisement


Variable definitionsUse the data in the following table to configure IPv6 route advertisement.


(VLAN). For the brouter port, the value is the ifindex of the port, andfor the VLAN, the value is the ifindex of the VLAN.

SendAdverts Indicates whether the router sends periodic router advertisementsand responds to router solicitations on this interface. The default isTrue.

UseDefaultVal Select one included value to use the default value, or use all bits toconfigure all options to their default value.

MaxInterval Configure the maximum interval (in seconds) at which thetransmission of route advertisements occurs on this interface. Thismust be no less than 4 seconds and no greater than 1800 seconds.The default is 600.

MinInterval Configure the minimum interval (in seconds) at which thetransmission of route advertisements can occur on this interface.The value must be no less than 3 seconds and no greater than .75x max-interval. The default is 200.

ReachableTime The value (in milliseconds) placed in the router advertisementmessage sent by the router. The value zero means unspecified (bythis router). Configure the amount of time that a remote IPv6 nodeis considered reachable after a reachability confirmation event. Thedefault is 30000.

RetransmitTimer The value (in milliseconds) placed in the retransmit timer field in therouter advertisement message sent from this interface. The valuezero means unspecified (by this router). The value configures theamount of time that router waits for the transmission to occur. Thedefault is 1000.

DefaultLifeTime The value placed in the router lifetime field of router advertisementssent from this interface. This value must be either 0 or betweenrcIpv6RouterAdvertMaxInterval and 9000 seconds. A value of zeroindicates that the router is not a default router. The default is 3 timesthe value of rcIpv6RouterAdvertMaxInterval or 1800.

CurHopLimit The default value placed in the current hop limit field in routeradvertisements sent from this interface. The value must be thecurrent diameter of the Internet. A value of zero in the routeradvertisement indicates that the advertisement is not specifying avalue for curHopLimit. The value must be the value specified in theIANA Web pages (http://www.iana.org). The default is 30.



http://www.iana.org

Variable ValueManagedFlag If enabled, the ManagedFlag configures the M-bit or the managed

address configuration in the router advertisement. The default isfalse.

OtherConfigFlag If set to true, then the O-bit (Other stateful configuration) in the routeradvertisement is set. Reference RFC2461 Section 6.2.1. The defaultvalue is false.

DadNSNum The number of neighbor solicitation messages for duplicate addressdetection (DAD). A value of 0 disables the DAD process on thisinterface. A value of 1 sends one advertisement withoutretransmissions.

LinkMTU The value placed in MTU options sent by the router on this interface.A value of zero indicates that the router sends no MTU options.

Configuring route advertisement on a VLANConfigure route advertisement in IPv6 for neighbor discovery (ND). IPv6 nodes on the samelink use ND to discover link-layer addresses and to obtain and advertise various networkparameters and reachability information. ND combines the services provided by AddressResolution Protocol (ARP) and router discovery for IPv4.

Procedure steps

1. In the navigation tree, open the Configuration > VLAN folders.2. Click VLANs.3. Click the Basic tab.4. Select a VLAN to configure.5. Click IPv6.6. Click the Route Advertisement tab.7. Edit the fields as required.8. Click Apply.

Variable definitionsUse the data in the following table to configure IPv6 route advertisement.

Configuring route advertisement on a VLAN



(VLAN). For the brouter port, the value is the ifindex of the port, andfor the VLAN, the value is the ifindex of the VLAN.

SendAdverts Indicates whether the router sends periodic router advertisementsand responds to router solicitations on this interface. The default isTrue.

UseDefaultVal Select one included value to use the default value, or use all bits toconfigure all options to their default value.

MaxInterval Configure the maximum interval (in seconds) at which thetransmission of route advertisements occurs on this interface. Thismust be no less than 4 seconds and no greater than 1800 seconds.The default is 600.

MinInterval Configure the minimum interval (in seconds) at which thetransmission of route advertisements can occur on this interface.The value must be no less than 3 seconds and no greater than .75x max-interval. The default is 200.

ReachableTime The value (in milliseconds) placed in the router advertisementmessage sent by the router. The value zero means unspecified (bythis router). Configure the amount of time that a remote IPv6 nodeis considered reachable after a reachability confirmation event. Thedefault is 30000.

RetransmitTimer The value (in milliseconds) placed in the retransmit timer field in therouter advertisement message sent from this interface. The valuezero means unspecified (by this router). The value configures theamount of time that router waits for the transmission to occur. Thedefault is 1000.

DefaultLifeTime The value placed in the router lifetime field of router advertisementssent from this interface. This value must be either 0 or betweenrcIpv6RouterAdvertMaxInterval and 9000 seconds. A value of zeroindicates that the router is not a default router. The default is 3 timesthe value of rcIpv6RouterAdvertMaxInterval or 1800.

CurHopLimit The default value placed in the current hop limit field in routeradvertisements sent from this interface. The value must be thecurrent diameter of the Internet. A value of zero in the routeradvertisement indicates that the advertisement is not specifying avalue for curHopLimit. The value must be the value specified in theIANA Web pages (http://www.iana.org). The default is 30.

ManagedFlag If enabled, the ManagedFlag configures the M-bit or the managedaddress configuration in the router advertisement. The default isfalse.

OtherConfigFlag If set to true, then the O-bit (Other stateful configuration) in the routeradvertisement is set. Reference RFC2461 Section 6.2.1. The defaultvalue is false.



http://www.iana.org

Variable ValueDadNsNum The number of neighbor solicitation messages for duplicate address

detection (DAD). A value of 0 disables the DAD process on thisinterface. A value of 1 sends one advertisement withoutretransmissions.

LinkMTU The value placed in MTU options sent by the router on this interface.A value of zero indicates that the router sends no MTU options.

Configuring the neighbor cacheNeighbor cache in IPv6 is similar to the IPv4 Address Resolution Protocol (ARP) table. Theneighbor cache is a set of entries for individual neighbors to which traffic was sent recently.You make entries on the neighbor on-link unicast IP address, including information such asthe link-layer address. A neighbor cache entry contains information used by the NeighborUnreachability Detection algorithm, including the reachability state, the number of unansweredprobes, and the time the next Neighbor Unreachability Detection event is scheduled.

Procedure steps

1. In the navigation tree, open the Configuration > IPv6 folders.2. Click IPv6.3. Click the Neighbors tab.4. Click Insert.5. In the IfIndex box, click Port or VLAN, and select a port number or VLAN.6. Edit the remaining fields.7. Click Insert.8. Click Apply.

Variable definitionsUse the data in the following table to configure the IPv6 neighbor cache.


(VLAN). For the brouter port, the value is the ifindex of the port, and forthe VLAN, the value is the ifindex of the vlan.

NetAddress The IP address corresponding to the media-dependent physicaladdress.

Configuring the neighbor cache


Variable ValuePhyAddress The media-dependent physical address. The range is 0–65535. For

Ethernet, this is a MAC address.

Interface Either a physical port ID or the MLT port ID. This entry is associated eitherwith a port or with the MLT in a VLAN/brouter port.

LastUpdated The value of sysUpTime at the time this entry was last updated. If thisentry was updated prior to the last reinitialization of the local networkmanagement subsystem, this object contains a zero value.

Type The mapping type is as follows:

• Dynamic type: indicates that the IP address to the physical addressmapping was dynamically resolved using, for example, IPv4 ARP orthe IPv6 Neighbor Discovery Protocol.

• Static type: indicates that the mapping was statically configured.

• Local type: indicates that the mapping is provided for the interfaceaddress.

The default is static.

State The Neighbor Unreachability Detection state for the interface when theaddress mapping in this entry is used. If Neighbor UnreachabilityDetection is not in use (for example, for IPv4), this object is alwaysunknown. Options include the following:

• reachable: confirmed reachability

• stale: unconfirmed reachability

• delay: waiting for reachability confirmation before entering the probestate

• probe: actively probing

• invalid: an invalidated mapping

• unknown: state cannot be determined

• incomplete: address resolution is being performed

Adding a static neighbor to the cacheAdd a static neighbor to create an entry for the neighbor route.

Procedure steps

1. In the navigation tree, open the Configuration > IPv6folders.2. Click IPv6.3. Click the Neighbors tab.



4. Click Insert.5. In the IfIndex box, click Port or VLAN, and select a port number or VLAN.6. In the Type list, select static.7. Edit the remaining fields as required.8. Click Insert.

Configuring IPv6 routing and ICMPEnable IPv6 routing to route IPv6 traffic on the switch.

IPv6 packets transport Internet Control Message Protocol (ICMP) error and informationmessages. Configure the rate, in milliseconds, at which ICMP sends messages to conservesystem resources.

To view a list of ICMP messages, see ICMPv6 type and code on page 427.

Procedure steps

1. In the navigation tree, open the Configuration > IPv6 folders.2. Click IPv6.3. To enable IPv6 routing, in the Forwarding box, select forwarding.4. Configure the routing and ICMP parameters as required.5. Click Apply.

Variable definitionsUse the data in the following table to configure IPv6 global properties.

Variable ValueForwarding Configures whether this entity is an IPv6 router with respect

to the forwarding of datagrams received by, but not addressedto, this entity. Select forwarding to act as a router. SelectnotForwarding to not act as a router. The default isnotForwarding.

DefaultHopLimit Configures the hop limit. The default is 30.

Interfaces A read-only value indicating the number of interfaces.

IfTableLastChange A read-only value indicating the date of the last interface tablechange.

IcmpNetUnreach If selected, enables the ICMP network unreachable feature.The default is disabled.

Configuring IPv6 routing and ICMP


Variable ValueIcmpRedirectMsg If selected, enables the ICMP redirect message feature. The

default is disabled.

IcmpErrorInterval Configures the interval (in milliseconds) for sending ICMPv6error messages. The default is 1000 milliseconds. An entry of0 seconds results in no sent ICMPv6 error messages.

IcmpErrorQuota The number of ICMP error messages that can be sent duringthe ICMP error interval. A value of zero specifies not to sendany. The default value is 50.

MulticastAdminStatus If selected, enables multicasting. The default is false.

Configuring an IPv6 discovery prefixThe IPv6 discovery prefix determines the source of an IP address or set of IP addresses. Thediscovery prefix also permits other tables to share the information through a pointer rather thanby copying. For example, when the node configures both a unicast and anycast address for aprefix, the ipAddressPrefix objects for those addresses point to a single row in the table.

You can use IPv4 addresses in IPv6. IPv4 prefixes use default values. You can override eachvalue if an object is meaningful to the node.

Procedure steps

1. In the navigation tree, open the Configuration > IPv6 folders.2. Click IPv6.3. Click the Discovery Prefix tab.4. Click Insert.5. In the IfIndex box, click Port or VLAN, and select a port number or VLAN.6. Edit the remaining fields.7. Click Insert.8. Click Apply.

Variable definitionsUse the data in the following table to configure the discovery prefix.



Variable ValueIfIndex A read-only value indicating the unique value to identify an IPv6 interface.

For the brouter port, it is the ifindex of the port and, in the case of theVLAN, it is the ifindex of the VLAN.

Prefix Configures the prefix to create an IPv6 address in the IPv6 interfacetable.

PrefixLen Configures the mask to create an IPv6 prefix entry as either advertisedor suppressed.

VlanId Specifies the VLAN ID of the IPv6 interface.

UseDefaultVal Select one of the values to set its value to default value. This is a bitmaskfield, setting all the bits means that all the options will be reverted todefault values.

ValidLife Configures the valid lifetime in seconds that indicates the length of timethis prefix is advertised. The default is 2592000.

PreferredLife Configures the preferred lifetime in seconds that indicates the length oftime this prefix is advertised. The default value is 604800.

Infinite Configures the prefix valid lifetime so it never expires. The default isfalse.

OnLinkFlag Configures the prefix for use when determining if a node is onlink. Thisvalue is placed in the L-bit field in the prefix information option. It is a 1-bit flag. The default is true.

AutoFlag Configures the prefix for use as the autonomous address configuration.This value is placed in the autoflag field in the prefix information option.It is a 1-bit flag. The default is true.

AddressEui Configures the EUI address. Use an EUI-64 interface ID in the low-order64-bits of the address when the ID is not specified in the address field. Ifenabled, use EUI, or use EUI-64 and the complement Universal/Local(U/L) bit. This operation provides for both global and link-local addresses.After you create the entry, you cannot modify this value. This value isvalid for use only when the PrefixLength is 64 or less. The default is eui-not-used.

NoAdvertise Select true to not include the prefix in the neighbor advertisement. Thedefault is false.

Configuring an IPv6 discovery prefix for a VLANThe IPv6 discovery prefix determines the source of an IP address or set of IP addresses. Thediscovery prefix also permits other tables to share the information through a pointer rather thanby copying. For example, when the node configures both a unicast and anycast address for aprefix, the ipAddressPrefix objects for those addresses point to a single row in the table.

Configuring an IPv6 discovery prefix for a VLAN


You can use IPv4 addresses in IPv6. IPv4 prefixes use default values. You can override eachvalue if an object is meaningful to the node.

Procedure steps

1. In the navigation tree, open the Configuration > VLAN folders.2. Click VLANs.3. Click the Basic tab.4. Select a VLAN to configure.5. Click IPv6.6. Click the Discovery Prefix tab.7. Click Insert.8. Edit the fields.9. Click Insert.

10. Click Apply.

Variable definitionsUse the data in the following table to configure the discovery prefix.

Variable ValueIfIndex A read-only value indicating the unique value to identify an IPv6 interface.

For the brouter port, it is the ifindex of the port and, in the case of theVLAN, it is the ifindex of the VLAN.

Prefix Configures the prefix to create an IPv6 address in the IPv6 interfacetable.

PrefixLen Configures the mask to create an IPv6 prefix entry as either advertisedor suppressed.

VlanId Specifies the VLAN ID of the IPv6 interface.

UseDefaultVal Select one of the values to set its value to default value. This is a bitmaskfield, setting all the bits means that all the options will be reverted todefault values.

ValidLife Configures the valid lifetime in seconds that indicates the length of timethis prefix is advertised. The default is 2592000.

PreferredLife Configures the preferred lifetime in seconds that indicates the length oftime this prefix is advertised. The default value is 604800.

Infinite Configures the prefix valid lifetime so it never expires. The default isfalse.



Variable ValueOnLinkFlag Configures the prefix for use when determining if a node is onlink. This

value is placed in the L-bit field in the prefix information option. It is a 1-bit flag. The default is true.

AutoFlag Configures the prefix for use as the autonomous address configuration.This value is placed in the autoflag field in the prefix information option.It is a 1-bit flag. The default is true.

AddressEui Configures the EUI address. Use an EUI-64 interface ID in the low-order64-bits of the address when the ID is not specified in the address field. Ifenabled, use EUI, or use EUI-64 and the complement Universal/Local(U/L) bit. This operation provides for both global and link-local addresses.After you create the entry, you cannot modify this value. This value isvalid for use only when the PrefixLength is 64 or less. The default is eui-not-used.

NoAdvertise Select true to not include the prefix in the neighbor advertisement. Thedefault is false.

Deleting an IPv6 addressDelete an IPv6 address from an interface to stop IPv6 routing on the interface.

Procedure steps

1. In the navigation tree, open the Configuration > IPv6 folders.2. Click IPv6.3. Click the Addresses tab.4. Select the address you want to delete.5. Click Delete.

Deleting an IPv6 interfaceDelete an IPv6 VLAN or brouter port to remove the IPv6 interface from the currentconfiguration.

Procedure steps

1. In the navigation tree, open the Configuration > IPv6 folders.2. Click IPv6.3. Click the Interfaces tab.

Deleting an IPv6 address


4. Select the interface you want to delete.5. Click Delete.

Deleting an IPv6 discovery prefixDelete an IPv6 discovery prefix to remove it from the current configuration.

Procedure steps

1. In the navigation tree, open the Configuration > IPv6 folders.2. Click IPv6.3. Click the Discovery Prefix tab.4. Select the prefix you want to delete.5. Click Delete.

Removing an entry from the neighbor cacheRemove entries from the neighbor cache to remove the route from the table.

Procedure steps

1. In the navigation tree, open the Configuration > IPv6 folders.2. Click IPv6.3. Click the Neighbors tab.4. Select the neighbor you want to remove.5. Click Delete.



Chapter 6: Basic IPv6 configuration usingthe CLI

This chapter describes how to use the command line interface (CLI) to perform basic IPv6 connectivityconfiguration.

Basic IPv6 configuration navigation• Job aid: Roadmap of basic IPv6 CLI commands on page 100

• Assigning an IPv6 address to the management port on page 101

• Configuring a management route on page 102

• Configuring a management virtual IPv6 address on page 103

• Creating a VLAN on page 103

• Configuring the VLAN as an IPv6 VLAN on page 105

• Assigning an IPv6 address to the VLAN on page 106

• Configuring the administrative status for the VLAN on page 107

• Assigning an IPv6 address to the brouter port on page 107

• Setting the administrative status on a brouter port on page 108

• Configuring IPv6 ICMP on page 109

• Configuring neighbor discovery prefixes on page 109


• Adding static entries to the neighbor cache on page 113

• Deleting an IPv6 address from the Ethernet SF/CPU slot on page 114

• Deleting an IPv6 address on page 115

• Deleting an IPv6 interface on page 116

• Modifying interface parameters on page 117

• Deleting a management route on page 118

• Deleting a neighbor discovery prefix on page 119

• Removing an entry from the neighbor cache on page 120


Job aid: Roadmap of basic IPv6 CLI commandsThe following table lists the commands and parameters that you use to perform the proceduresin this chapter.

Table 7: Job aid: Roadmap of basic IPv6 CLI commands

Command Parameterconfig ethernet slot/port ipv6 nd-prefix<prefix/prefix length> create

create

default

delete

infinite

info

no-advertise

pref-life

valid-life

config ipv6 icmp-error-interval <0 through2147483647>

--

config sys dns --

config sys net6-mgmt ipv6 add <IPv6address/prefix length> cpu-slot <slot-id>

--

config sys net6-mgmt ipv6 del <IPv6address/prefix length> cpu-slot <slot-id>

--

config sys net6-mgmt route add <networkIPv6 address> <network gateway>

--

config sys net6-mgmt route del <networkIPv6 address> <network gateway>

--

config sys set mgmt-virtual-ipv6<ipv6address/prefixlen>

--

config sys set snmp --

config vlan <vlan ID> ipv6 create link-local

descr

addr

addr-type

delete

Basic IPv6 configuration using the CLI


Command Parameteradmin

mcast

mtu

reachable-time

retransmit-time

config vlan <vlan id> ipv6 nd dad-ns

default

hop-limit

info

life-time

managed-flag

other-stateful

route-advertisement

rtr-advert

Assigning an IPv6 address to the management portThe Avaya Ethernet Routing Switch 8800/8600 switch contains an Ethernet port in the SF/CPUslot. You can assign IPv6 addresses to this port to manage the device.

Perform duplicate address detection (DAD) for the management IPv6 address.

Important:Do not advertise the management route to the regular routing domain (OSPFv3) or advertisethe prefix information for the management interface in router advertisement.

Procedure steps

Assign an IPv6 address to the management port:

Assigning an IPv6 address to the management port


config sys net6-mgmt ipv6 add <IPv6 address/prefix length> cpu-slot <slot-id>

Variable definitionsUse the data in the following table to use the config sys net6-mgmt ipv6 addcommand.

Variable Value<IPv6 address/prefix length> Specifies the IPv6 address and prefix length

to assign to the port.

<slot-id> Specifies the slot number where the port islocated. If a slot ID is not specified, theaddress is configured for the current SF/CPU.

Configuring a management routeConfigure a management route to establish communication between networks.

Procedure steps

Configure the management route by using the following command:

config sys net6-mgmt route add <network IPv6 address> <network gateway>

Variable definitionsUse the data in the following table to use the config sys net6-mgmt route addcommand.

Variable Valuenetwork gateway Specifies the IPv6 address of the gateway.

network IPv6 address Specifies the IPv6 address of the network toadd.



Configuring a management virtual IPv6 addressConfigure a system virtual IPv6 address to manage of the SF/CPU Ethernet port in failoversituations.

Procedure steps

Configure a virtual IPv6 address by using the following command:

config sys set mgmt-virtual-ipv6 <ipv6address/prefixlen>

Variable definitionsUse the data in the following table to use the config sys set mgmt-virtual-ipv6command.

Variable Value<ipv6address/prefixlen> Specifies the IPv6 address and prefix length

to add to the port.The default value is 0:0:0:0:0:0:0:0/0.

Creating a VLANYou must create a VLAN before you can configure it as an IPv6 VLAN. The Avaya EthernetRouting Switch 8800/8600 supports three types of VLANs:

• port-based VLANs• protocol-based VLANs• MAC-source-based VLANs

Specify the type of VLAN and assign an IP address to the VLAN. VLAN 1 is the defaultVLAN.

Procedure steps

Create a VLAN by using the following command:

Configuring a management virtual IPv6 address


config vlan <vid> create

Variable definitionsUse the data in the following table to use the config vlan create command.

Variable Valuebyport <sid> [name <value> ] [color<value> ]

Creates a port-based VLAN.

• sid is the spanning tree group ID from 1-64characters.

• name <value> is the name of the VLAN from0-64 characters.

• color <value> is the color of the VLAN (0-32).The color attribute is used by Optivity softwareto display the VLAN.

byprotocol <sid> <ip|appleTalk|declat|decOther|sna802dot2|snaEthernet2|netBios|xns|vines|ipV6|usrDefined|rarp|PPPoE> [<pid>] [name <value>] [color<value>] [encap <value>]

Creates a protocol-based VLAN.

• sid is the spanning tree ID 1-64.

• ip|appleTalk|decLat|decOther|sna802dot2|snaEthernet2|netBios|xns|vines|ipV6|usrDefined|rarp| PPPoE specifies the protocol.

• pid is a user-defined protocol ID number inhexadecimal format (0 to 65535).



• encap <value> is the frame encapsulationmethod.

bysrcmac <sid> [name <value> ] [color<value>]

Creates a VLAN by MAC-source address.

• sid is the spanning tree ID 1-64.



This command is available only for the AvayaEthernet Routing Switch 8800/8600.

info Shows information about the specified VLAN.



Variable Value<vid> Specifies the VLAN ID (from 1-4094).

Configuring the VLAN as an IPv6 VLANConfigure a VLAN as an IPv6 VLAN to use IPv6 routing on the VLAN.

Prerequisites

You must create the VLAN before you configure it as an IPv6 VLAN.

Procedure steps

Configure the VLAN by using the following command:

config vlan <vlan ID> ipv6 create

Variable definitionsUse the data in the following table to use the config vlan ipv6 create command.

Variable Valueaddr Specifies the IPv6 address and prefix length in

the format address and prefix length.

addr-type 1—unicast, 2—anycast.The default values is 1—unicast.

admin Enables or disables the administrative state of theinterface.

delete Deletes one of the following:

• addr <value>

• all

• interface

descr Views or updates the description for theinterface.

Configuring the VLAN as an IPv6 VLAN


Variable Valueinfo Displays information about the configuration.

link-local Specifies a numeric identifier for the interface.

mcast Enables or disables MLD.The default value is disable.

mtu Configures the maximum transmission unit forthe interface.The default value is 1500.

reachable-time Configures the time, in milliseconds, a neighboris considered reachable after receiving areachability confirmation.The default value is 30000.

retransmit-time Configures the time, in milliseconds, betweenretransmissions of Neighbor Solicitationmessages to a neighbor when resolving theaddress or when probing the reachability of aneighbor.The default value is 1000.

<vid> Specifies the VLAN ID, from 1-4094.

Assigning an IPv6 address to the VLANAssign an IPv6 address to the VLAN to enable IPv6 routing on the VLAN.

Procedure steps

Assign an IPv6 address by using the following command:

config vlan <vlan id> ipv6 create addr <ipv6 address>

Variable definitionsUse the data in the following table to use the config vlan ipv6 create addrcommand.

Variable Valueipv6 address Specifies the IPv6 address to add to the

VLAN.



Variable Valuevlan id Specifies the ID of the VLAN, from 1-4094.

Example of assigning an IPv6 address to a VLANProcedure steps

Assign an IPv6 address:

ERS-8610:5# config vlan 13 ipv6 create addr8888:0:0:0:0:0:0:1/96

Configuring the administrative status for the VLANConfigure the administrative status to enable the IPv6 VLAN.

Procedure steps

Configure the administrative status by using the following command:

config vlan <vlan id> ipv6 admin enable

Variable definitionsUse the data in the following table to use the config vlan ipv6 admin enablecommand.

Variable Valuevlan id Specifies the ID of the VLAN, from 1 to

4094.

Assigning an IPv6 address to the brouter portAssign an IPv6 address to a brouter port on a VLAN to customize the IPv6 VLANconfiguration.

Configuring the administrative status for the VLAN


Procedure steps

Assign an IPv6 address by using the following command:

config ethernet <slot/port> ipv6 create addr <ipv6 address> vlan <vlan id>

Variable definitionsUse the data in the following table to use the config ethernet ipv6 create addr vlancommand.

Table 8: Variable defintions

Variable Valueipv6 address Specifies the IPv6 address to add to the

port.

slot/port Identifies the slot and port location.

vlan id Specifies the ID of the VLAN, from 1-4094.

Setting the administrative status on a brouter portEnable the brouter port by setting the administrative status.

Procedure steps

Configure the administrative status by using the following command:

config ethernet <slot/port> ipv6 admin enable

Variable definitionsUse the data in the following table to use the config ethernet ipv6 admin enablecommand.



Variable Valueslot/port Specifies the slot and port location for the

port.

Configuring IPv6 ICMPConfigure Internet Control Message Protocol (ICMP) to transport error and informationmessages within IPv6 packets.


Procedure steps

Configure the ICMP rate by using the following command:

config ipv6 icmp-error-interval <0 through 2147483647>

Configuring neighbor discovery prefixesIPv6 nodes on the same link use ND to discover link-layer addresses and to obtain andadvertise various network parameters and reachability information. ND combines the servicesprovided by Address Resolution Protocol (ARP) and router discovery for IPv4. IPv6 routeradvertisement includes discovery prefixes.

Procedure steps

1. Configure discovery prefixes for a brouter port by using the following command:

config ethernet <slot/port> ipv6 nd-prefix <prefix/prefix length>create

2. Configure discovery prefixes for a VLAN by using the following command:

config vlan <vlan id> ipv6 nd-prefix <prefix/prefix length> create

Configuring IPv6 ICMP


Variable definitionsUse the data in the following table to use the config ethernet ipv6 nd-prefix createand config vlan ipv6 nd-prefix create commands.

Variable Valuecreate Creates discovery prefixes and configures the

following options:

• on-link-flag: if assigned, onlink determination usesthe prefix. This value is placed in the L-bit field in theprefix information option. It is a 1-bit flag.The default value is true.

• auto-flag: if assigned, the prefix is used forautonomous address configuration.The default value is true.

• eui: (1) Extended Unique Identifier (EUI) not used,(2) EUI with Universal/Local bit (U/L) complementenabled, (3) EUI used without U/L.The default value is (EUI) not used.

• no-advertise: if true, the prefix is not advertised. Iffalse, the prefix is advertised.The default value is false.

default Select one of the values to use as the default value.This is a bitmask field; using all the bits means that allthe options revert to default values:

• (0) valid-life

• (1) preferred-life

• (3) no-advertise

delete Deletes the prefix.

infinite If assigned, the prefix does not expire.The default value is false.

info Subcontext commands.

no-advertise Modify whether the prefix is advertised. The truesetting prevents prefix advertisement.The default value is false.

pref-life The number of seconds that the prefix can accept anduse new connections.The default value is 604800.

prefix/prefix length Specifies the IP address and prefix.



Variable Valueslot/port Specifies the slot and port location of the brouter

port.

valid-life The number of seconds that the prefix advertised inthe neighbor advertisement is valid. During the validlifetime, existing connections can be used. Newconnections cannot be opened.The default value is 2592000.

vlan id Specifies the ID of the VLAN from 1-4094.

Example of configuring neighbor discovery prefixesProcedure steps

1. Configure brouter port 4/18 with an IPv6 address of 4040::1/96.

ERS-8610:5# config ethernet 4/18 ipv6 nd-prefix 4040::0/96create

2. Configure VLAN 13 with an IPv6 address of 8888::1/96.

ERS-8610:5# config vlan 13 ipv6 nd-prefix 8888::1/96 create

Configuring route advertisementUse route advertisement to discover potential default routers in a network and to discover linkinformation.

Procedure steps

1. Configure route advertisement on a brouter port by using the following command:

config ethernet <slot/port> ipv6 nd2. Configure route advertisement on a VLAN by using the following command:

config vlan<vlan id> ipv6 nd



Variable definitionsUse the data in the following table to use the config ethernet ipv6 nd and configvlan ipv6 nd commands.

Variable Valuedad-ns The number of neighbor solicitation messages from

duplicate address detection. The acceptable range is0-600. A value of 0 disables duplicate addressdetection on the specified interface. A value of 1configures a single transmission without follow-uptransmissions.The default value is 1.

default Select one or multiple entries to configure the defaultvalue.

• max-interval

• min-interval

• life-time

• hop-limit

• managed-flag

• other-config-flag

• dad-ns-num

• all

hop-limit Configures the maximum number of hops beforepackets drop.The default value is 30.

info Display subcontext commands.

life-time Enter the router lifetime included in routeradvertisement. Other devices use this information todetermine if the router can be reached.

managed-flag Configure to true to enable M-bit (managed addressconfiguration) on the router.The default value is false.

other-stateful Configure to true to enable the O-bit (other statefulconfiguration) in the router advertisement. Otherstateful configuration autoconfigures receivedinformation without addresses.The default value is false.

route-advertisement Enable or disable periodic router advertisementmessages.



Variable ValueThe default value is true.

rtr-advert min <value>: The minimum time allowed betweensending unsolicited multicast router advertisements.The default value is 200.max <value>: The maximum time allowed betweensending unsolicited multicast router advertisementsfrom the interface, in seconds. (3-200 seconds).The default value is 600.

Adding static entries to the neighbor cacheThe neighbor cache is populated with information about IPv6 neighbors to which the IPv6device sends traffic. You can add neighbors to the cache manually.

Procedure steps

Add a neighbor by using the following command:

config ipv6 neighbor add ports <slot/port> ipv6addr <ipv6 address> mac<mac address> vlanid <vlan id>

Variable definitionsUse the data in the following table to use the config ipv6 neighbor add portscommand.

Variable Valueipv6 address Specifies the IPv6 address in hexadecimal

colon format {string length 0..128}

mac address Specifies the MAC address in the followingformat: {0x00:0x00:0x00:0x00:0x00:0x00}

slot/port Specifies the slot and port location to add aneighbor for a brouter port.

vlan id Specifies the ID of the VLAN to add aneighbor for a VLAN.

Adding static entries to the neighbor cache


Example of adding static entries to the neighbor cacheProcedure steps

1. Add a VLAN static entry.

ERS-8610:5# config ipv6 neighbor add ports 4/17 ipv6addr9999:0:0:0:0:0:0:1 mac 00:80:2d:c0:92:03 vlanid 14

2. Add a brouter port static entry.

ERS-8610:5# config ipv6 neighbor add ports 4/18 ipv6addr4040:0:0:0:0:0:0:1 mac 00:80:2d:c0:92:03

Deleting an IPv6 address from the Ethernet SF/CPU slotYou can assign multiple addresses to the Ethernet SF/CPU slot on the Avaya Ethernet RoutingSwitch 8800/8600. Delete an address to remove it from the configuration.

Procedure steps

Remove an IPv6 address from the Ethernet SF/CPU slot by using the followingcommand:

config sys net6-mgmt ipv6 del <IPv6 address/prefix length> cpu-slot <slot-id>

Variable definitionsUse the data in the following table to use the config sys net6-mgmt ipv6 delcommand.

Variable ValueIPv6 address/prefix length Specifies the IPv6 address and prefix length

to delete from the port.

slot-id Specifies the slot number where the port islocated. If a slot ID is not specified, theaddress is deleted from the current SF/CPU.



Deleting an IPv6 addressDelete the IPv6 address to stop IPv6 routing.

Procedure steps

1. Delete the IPv6 address on a VLAN by using the following command:

config vlan <vlan id> ipv6 delete addr <Ipv6 address>

2. Delete the IPv6 address on a brouter port by using the following command:

config ethernet <slot/port> ipv6 delete addr <IPv6 address>

Variable definitionsUse the data in the following table to use the config vlan ipv6 delete addr andconfig ethernet ipv6 delete addr commands.

Variable ValueIPv6 address Specifies the IPv6 address to delete.

slot/port Specifies the slot and port location of thebrouter port from which to delete the IPv6address.

vlan id Specifies the ID of the VLAN from which todelete the IPv6 address.

Example of deleting an IPv6 addressProcedure steps

1. Delete the IPv6 address on a VLAN:

ERS-8610:5# config vlan 13 ipv6 delete addr 9898::12. Delete the IPv6 address on a brouter port:

ERS-8610:5# config ethernet 1/18 ipv6 delete addr 4040::1

Deleting an IPv6 address


Deleting an IPv6 interfaceDelete an IPv6 interface to remove it from the configuration.

Procedure steps

1. Delete an IPv6 interface from a VLAN by using the following command:

config vlan <vlan id> ipv6 delete interface2. Delete an IPv6 interface from a brouter port by using the following command:

config ethernet <slot/port> ipv6 delete interface

Variable definitionsUse the data in the following table to use the config vlan ipv6 delete interface andconfig ethernet ipv6 delete interface commands.

Variable Valueslot/port Specifies the slot and port location of the

brouter port from which to delete the IPv6interface.

vlan id Specifies the ID of the VLAN from which todelete the IPv6 interface.

Example of deleting an IPv6 interfaceProcedure steps

1. Delete the IPv6 interface on a VLAN:

ERS-8610:5# config vlan 13 ipv6 delete interface2. Delete the IPv6 interface on a brouter port:

ERS-8610:5# config ethernet 1/18 ipv6 delete interface



Modifying interface parametersModify interface parameters to update configured settings for VLAN or brouter portparameters.

Procedure steps

1. Modify parameters for a VLAN by using the following command:

config vlan <vlan id> ipv62. Modify parameters for a brouter port by using the following command:

config ethernet <slot/port> ipv6

Variable definitionsUse the data in the following table to use the config vlan ipv6 and config ethernetipv6 commands.

Variable Valueadmin Enables or disables the interface.

create Creates an interface and configures the following:

• link-local

• descr: modify the description for the interface.

• addr: modify the IPv6 address for the interface.

• addr-type: unicast or anycastThe default value is unicast.

delete Deletes one of the following:

• addr

• all

• interface

mcast Enables or disables the multicast administrative statusof the interface.The default value is disable.

mtu Configures the maximum transmission unit in bytes forthe interface.

Modifying interface parameters


Variable ValueThe default value is 1500.

reachable-time Configures the time (in milliseconds) a neighbor isconsidered reachable after receiving a reachabilityconfirmation.The default value is 30000.

retransmit-timer Configures the time (in milliseconds) betweenretransmissions of Neighbor Solicitation messages toa neighbor when resolving the address or whenprobing the reachability of a neighbor.The default value is 1000.

slot/port Specifies the slot and port location of the brouterport.


Deleting a management routeDelete a management route to stop communication between networks.

Procedure steps

Delete a management route by using the following command:

config sys net6-mgmt route del <network IPv6 address> <network gateway>

Variable definitionsUse the data in the following table to use the config sys net6-mgmt route delcommand.

Variable Valuenetwork gateway Specifies the IPv6 address of the gateway.

network IPv6 address Specifies the IPv6 address of the network todelete.



Deleting a neighbor discovery prefixDelete a neighbor discovery prefix to remove it from the configuration.

Procedure steps

1. Delete a neighbor discovery prefix from a VLAN by using the following command:

config vlan <vlan id> ipv6 nd-prefix <prefix/length> delete2. Delete a neighbor discovery prefix from a brouter port by using the following

command:

config ethernet <slot/port> ipv6 nd-prefix <prefix/length>delete

Variable definitionsUse the data in the following table to use the config vlan ipv6 nd-prefix delete andconfig ethernet ipv6 nd-prefix delete command.

Variable Valueprefix/length Specifies the IP address and prefix.

slot/port Specifies the slot and port location of thebrouter port.


Example of deleting a neighbor discovery prefixProcedure steps

1. Delete a neighbor discovery prefix from a VLAN:

ERS-8610:5# config vlan 13 ipv6 nd-prefix 9898::0/96 delete2. Delete a neighbor discovery prefix from a brouter port:

ERS-8610:5# config ethernet 1/18 ipv6 nd-prefix 4040::0/96delete

Deleting a neighbor discovery prefix


Removing an entry from the neighbor cacheRemove an entry from the neighbor cache to delete it from the static configuration.

Procedure steps

Remove an entry by using the following command:

config ipv6 neighbor delete <ipv6 address> port <slot/port>vlanid <vlan id>

Variable definitionsUse the data in the following table to use the config ipv6 neighbor deletecommand.


colon format (string length 0-128).

slot/port Specifies the slot and port location to removea neighbor for a brouter port.

vlan id Specifies the ID of the VLAN to remove aneighbor for a VLAN.

Example of removing an entry from the neighbor cacheProcedure steps

Remove a VLAN entry from the neighbor cache:

ERS-8610:5# config ipv6 neighbor delete 8888:0:0:0:0:0:0:1vlanid 13



Chapter 7: Basic IPv6 configuration usingthe ACLI

This section describes how to use the Avaya command line interface (ACLI) to perform basic IPv6connectivity configuration.

Basic IPv6 configuration navigation• Job aid: Roadmap of basic IPv6 ACLI commands on page 121

• Assigning an IPv6 address to the management port on page 123

• Configuring a management route on page 124

• Configuring a management virtual IPv6 address on page 125

• Creating a VLAN on page 125

• Configuring an interface as an IPv6 interface on page 127

• Configuring the VLAN as an IPv6 VLAN on page 129

• Configuring IPv6 ICMP on page 130

• Configuring neighbor discovery prefixes on page 131


• Adding static entries to the neighbor cache on page 134

Job aid: Roadmap of basic IPv6 ACLI commandsThe following table lists the commands and parameters that you use to perform the proceduresin this section.

Table 9: Job aid: Roadmap of basic IPv6 ACLI commands

Command ParameterGlobal Configuration mode

ipv6 icmp error-interval <0 through 2147483647>


Command Parameterredirect-msg

unreach-msg

ipv6 mgmt-virtual <ipv6address/prefixlen>

--

ipv6 neighbor <ipv6 address> port <slot/port> mac <mac address> vlan <vlanid>

net6-mgmt ipv6 <IPv6 address/prefix length>

route <network IPv6 address>

vlan create <vid> name <value>

type <value>

Interface Configuration mode

ipv6 interface address-type <1-2>

enable

link-local <word>

mtu <bytes>

multicast-routing

name

reachable-time <ms>

retransmit-time <ms>

vlan <vlan id>

ipv6 interface address <ipv6 address> address-type <1-2>

link-local <word>

mtu <bytes>

multicast-routing

reachable-time <ms>

retransmit-time <ms>

ipv6 nd dad-ns

hop-limit

managed-config-flag

other-config-flag

ra-lifetime

rtr-advert-max-interval

Basic IPv6 configuration using the ACLI


Command Parameterrtr-advert-min-interval

send-ra

ipv6 nd prefix <prefix/prefix length> infinite

no-advertise

preferred-life <seconds>

valid-life <seconds>

ipv6 nd prefix-interface <Ipv6address-prefix>

no-autoconfig <false|true>

eui <1-3>

no-advertise

no-onlink <false|true>

Assigning an IPv6 address to the management portThe Avaya Ethernet Routing Switch 8800/8600 switch contains an Ethernet port in the SF/CPUslot. You can assign IPv6 addresses to this port to manage the device.

Perform duplicate address detection (DAD) for the management IPv6 address.

Important:Do not advertise the management route to the regular routing domain (OSPFv3) or advertisethe prefix information for the management interface in router advertisement.

Prerequisites

You must log on to the Global Configuration mode in the ACLI.

Procedure steps

Assign an IPv6 address to the management port by using the following command:

Assigning an IPv6 address to the management port


net6-mgmt ipv6 <IPv6 address/prefix length>

Variable definitionsUse the data in the following table to use the net6-mgmt ipv6 command.

Variable ValueIPv6 address/prefix length Specifies the IPv6 address and prefix length

to assign to the management interface.The default value is none.

Configuring a management routeConfigure a management route to establish communication between networks.

Prerequisites


Procedure steps

Configure the management route by using the following command:

net6-mgmt ipv6 route <network IPv6 address>

Variable definitionsUse the data in the following table to use the net6-mgmt ipv6 route command.

Variable Valuenetwork IPv6 address Specifies the IPv6 address and prefix length

of the network to add.The default value is none.



Configuring a management virtual IPv6 addressConfigure a system virtual IPv6 address to manage of the SF/CPU Ethernet port in failoversituations.

Prerequisites


Procedure steps

Configure a virtual IPv6 address by using the following command:

ipv6 mgmt-virtual <ipv6address/prefixlen>

Variable definitionsUse the data in the following table to use the ipv6 mgmt-virtual command.

Variable Valueipv6address/prefixlen Specifies the IPv6 address and prefix length

to add to the port. To configure this option tothe default value, use the default operatorwith the command: default ipv6 mgmt-virtual.The default value is 0:0:0:0:0:0:0:0/0.

Creating a VLANYou must create a VLAN before you can configure it as an IPv6 VLAN. Avaya Ethernet RoutingSwitch 8800/8600 supports three types of VLANs:

• port-based VLANs• protocol-based VLANs• MAC-source-based VLANs

Configuring a management virtual IPv6 address


Specify the type of VLAN and assign the VLAN a name. VLAN 1 is the default VLAN.

Prerequisites


Procedure steps

Create a VLAN by using the following command:

vlan create <vid> name <value> type <value>

Variable definitionsUse the data in the following table to use the vlan create command.

Variable Valuename <value> Configures a name for the VLAN.

type <value> Specifies the type of VLAN to create:

• port [<stgId:1-16>|cist|msti <1-15>]

• protocol-ApltkEther2Snap

• protocol-decEther2

• protocol-decOtherEther2

• protocol-ipEther2

• protocol-ipv6Ether2

• protocol-Netbios

• protocol-RarpEther2

• protocol-sna802.2

• protocol-snaEther2

• protocol-Userdef <4096-65534>

• protocol-vinesEther2

• protocol-xnsEther2

• ipsubnet-mstprstp <1-63> <A.B.C.D/0-32>[color<1-32>]



Variable Value

• port-mstprstp <1-63> <A.B.C.D/0-32>[color<1-32>] [naap-vlan] [firewall-vlan][firewall-peering-vlan]

• protocol-mstprstp <1-63> ip|appleTalk|decLat|decOther|sna802dot2|snaEthernet2|netBios|xns|vines|ipV6|usrDefined|rarp|PPPoE [<pid>][color <1-32>] [encap <value>]

• srcmac-mstprstp <1-63> [color <1-32>]

• svlan-mstprstp <1-63> [color <1-32>]

• ids-mstprstp <1-63> [color <1-32>]

• ipsubnet <1-63> <A.B.C.D/mask> [color<1-32>]

• srcmac <1-63> [color <1-32>]

• svlan <1-63> [color <1-32>]

• ids <1-63> [color <1-32>]

stgId is the spanning tree group ID. color <value>is the color of the VLAN. Optivity software usesthe color attribute to display the VLAN. pid is auser-defined protocol ID number in hexadecimalformat (0–65535). encap <value> is the frameencapsulation method.

Important:The mstprstp options are available for theAvaya Ethernet Routing Switch 8800/8600only.

vid Specifies the VLAN ID (from 1–4094).

Configuring an interface as an IPv6 interfaceConfigure an interface as an IPv6 interface to use IPv6 routing on the interface.

Configuring an interface as an IPv6 interface


Prerequisites

You must log on to the Interfaces configuration mode in ACLI for the required port or portlist.

Procedure steps

1. Configure the IP address by using the following command:

ipv6 interface address <ipv6 address> vlan <vlan id>2. Configure additional parameters for the port by using the following command:

ipv6 interface [address-type <1-2>] [mtu <bytes>] [muticast-routing] [reachacble-time <ms>] [retransmit-time <ms>] [vlan<vlan id>]

Variable definitionsUse the data in the following table to use the ipv6 interface and ipv6 interfaceaddress commands.

Variable Valueaddress <ipv6 address> Configures the IPv6 address and prefix length in

the format address and prefix length.The default value is none.

address-type <1-2> 1—unicast, 2—anycast.The default value is 1—unicast.

mtu <bytes> Configures the maximum transmission unit for theinterface.The default value is 1500.

multicast-routing Enables or disables MLD.The default value is disable.

reachable-time <ms> Configures the time, in milliseconds, that aneighbor is considered reachable after receivinga reachability confirmation.The default value is 30000.

retransmit-time <ms> Configures the time, in milliseconds, betweenretransmissions of Neighbor Solicitationmessages to a neighbor when resolving theaddress or when probing the reachability of aneighbor.The default value is 1000.



Variable Valuevlan <vlan id> Specifies the VLAN ID.

Configuring the VLAN as an IPv6 VLANConfigure a VLAN as an IPv6 VLAN to use IPv6 routing on the VLAN.

Prerequisites

• You must log on to the VLAN Interfaces configuration mode in ACLI for the required VLANID.

• You must create the VLAN before you configure it as an IPv6 VLAN.

Procedure steps

1. Configure the IP address by using the following command:

ipv6 interface address <ipv6 address>2. Configure additional parameters for the VLAN by using the following command:

ipv6 interface [address-type <1-2>] [mtu <bytes>] [muticast-routing] [reachacble-time <ms>] [retransmit-time <ms>]

Variable definitionsUse the data in the following table to use the ipv6 interface and ipv6 interfaceaddress commands.

Variable Valueaddress <ipv6 address> Configures the IPv6 address/prefix length.

The default value is none.

address-type <1-2> 1—unicast, 2—anycast.The default value is 1—unicast.

mtu <bytes> Configures the maximum transmission unit for theinterface.The default value is 1500.

multicast-routing Enables or disables MLD.The default value is disable.

Configuring the VLAN as an IPv6 VLAN


Variable Valuereachable-time <ms> Configures the time, in milliseconds, a neighbor

is considered reachable after receiving areachability confirmation.The default value is 30000.

retransmit-time <ms> Configures the time, in milliseconds, betweenretransmissions of Neighbor Solicitationmessages to a neighbor when resolving theaddress or when probing the reachability of aneighbor.The default value is 1000.

Configuring IPv6 ICMPConfigure Internet Control Message Protocol (ICMP) to transport error and informationmessages within IPv6 packets.


Prerequisites


Procedure steps

1. Configure the ICMP rate by using the following command:

ipv6 icmp error-interval <0 through 2147483647>2. Set the status for redirect messages by using the following command:

ipv6 icmp redirect-msg3. Configure the status for unreachable messages by using the following command:

ipv6 icmp unreach-msg

Variable definitionsUse the data in the following table to use the ipv6 icmpcommand.



Variable Valueerror-interval <0 through 2147483647> Configures the error interval in milliseconds.

The interval is the time between transmissionof error messages. To configure this optionto the default value, use the default operatorwith the command.The default value is 1000.

redirect-msg Configures the administrative status forICMP redirect messages. Use the nooperator to remove this configuration. Toconfigure this option to the default value, usethe default operator with the command.The default value is disable.

unreach-msg Configures the administrative status forICMP unreachable messages. Use the nooperator to remove this configuration. Toconfigure this option to the default value, usethe default operator with the command.The default value is disable.

Configuring neighbor discovery prefixesIPv6 nodes on the same link use ND to discover link-layer addresses and to obtain andadvertise various network parameters and reachability information. ND combines the servicesprovided by Address Resolution Protocol (ARP) and router discovery for IPv4. IPv6 routeradvertisement includes discovery prefixes.

Prerequisites

You must log on to the Interface Configuration mode in the ACLI.

Procedure steps

1. Configure discovery prefixes by using the following command:

ipv6 nd prefix-interface < Ipv6address-prefix> [no-autoconfig<false|true>] [eui <1-3>] [no-advertise] [no-onlink <false|true>]

2. Configure neighbor discovery prefix parameters by using the following command:

Configuring neighbor discovery prefixes


ipv6 nd prefix <prefix/prefix length> [infinite] [no-advertise] [preferred-life <seconds>] [valid-life <seconds>]

Variable definitionsUse the data in the following table to use the ipv6 nd prefix and ipv6 nd prefix-interface commands.

Variable Valueno-autoconfig <false|true> If true, the prefix is used for autonomous

address configuration.The default value is true.

eui <1-3> (1) eui (extended unique identifier) notused, (2) eui with U/L (Universal/Local bit)complement enabled, (3) eui used withoutu/l.The default value is eui not used.

infinite Configures the prefix as infinite.The default value is disable.

no-advertise Removes the prefix from the neighboradvertisement. Use the no operator toremove this option. Use the defaultoperator to configure this value to thedefault setting.The default value is disable.

no-onlink <false|true> If true, onlink determination uses the prefix.This value is placed in the L-bit field in theprefix information option. It is a 1-bit flag.The default value is true.

preferred-life <seconds> Configures the preferred life, in seconds.The valid range is 0–3600000. Use thedefault operator to configure this value tothe default setting.The default value is 604800.

prefix/prefix length Specifies the IP address and prefix.

valid-life <seconds> Configures the valid life, in seconds. Thevalid range is 0–3600000. Use the defaultoperator to configure this value to thedefault setting.The default value is 2592000.



Configuring route advertisementUse route advertisement to discover potential default routers in a network and to discover linkinformation.

Prerequisites


Procedure steps

Configure route advertisement on a brouter port by using the following command:

ipv6 nd [dad-ns <0-600>] [hop-limit <1-255>] [managed-config-flag] [other-config-flag] [ra-lifetime <0|4-9000>] [rtr-advert-max-interval <4-1800>] [rtr-advert-min-interval <3-1350>][send-ra]

Variable definitionsUse the data in the following table to use the ipv6 nd command.

Variable Valuedad-ns The number of neighbor solicitation messages from

duplicate address detection. The acceptable rangeis 0-600. A value of 0 disables duplicate addressdetection on the specified interface. A value of 1configures a single transmission without follow-uptransmissions. Use the default operator to configurethis value to the default setting.The default value is 1.

hop-limit Enter the maximum number of hops before packetsdrop. Use the default operator to configure this valueto the default setting.The default value is 30.

managed-config-flag Configure to true to enable M-bit (managed addressconfiguration) on the router. Use the no operator to



Variable Valueremove this option. Use the default operator toconfigure this value to the default setting.The default value is false.

other-config-flag Configure to true to enable the O-bit (other statefulconfiguration) in the router advertisement. Otherstateful configuration autoconfigures receivedinformation without addresses. Use the no operatorto remove this option. Use the default operator toconfigure this value to the default setting.The default value is false.

ra-lifetime Enter the router lifetime included in routeradvertisement. Other devices use this information todetermine if the router can be reached. The range is0 or 4–9000. Use the default operator to configurethis value to the default setting.The default value is 1800.

rtr-advert-max-interval Configures the maximum time allowed betweensending unsolicited multicast routeradvertisements.The default value is 600.

rtr-advert-min-interval Configures the minimum time allowed, in seconds(3–1350), between sending unsolicited multicastrouter advertisements from the interface. Use thedefault operator to configure this value to the defaultsetting.The default value is 200.

send-ra Enable or disable periodic router advertisementmessages. Use the no operator to remove thisoption. Use the default operator to configure thisvalue to the default setting.The default value is true.

Adding static entries to the neighbor cacheThe neighbor cache contains information about IPv6 neighbors to which the IPv6 device sendstraffic. You can manually add neighbors to the cache.



Prerequisites


Procedure steps

Add a neighbor by using the following command:

ipv6 neighbor <ipv6 address> port <slot/port> mac <mac address>vlan <vlan id>

Variable definitionsUse the data in the following table to use the ipv6 neighbor command.


colon format {string length 0..128}. Thedefault value is none.

mac address Specifies the MAC address in the followingformat: {0x00:0x00:0x00:0x00:0x00:0x00}

slot/port Specifies the slot and port location to add aneighbor for a brouter port.

vlan id Specifies the ID of the VLAN to add aneighbor for a VLAN.

Example of adding static entries to the neighbor cacheProcedure steps

Add a VLAN static entry:

ERS-8606:5(config)# ipv6 neighbor 9999:0:0:0:0:0:0:1 port 4/1mac 00:80:2d:c0:92:03 vlan 4

Adding static entries to the neighbor cache




Chapter 8: IPv6 routing configurationusing Enterprise DeviceManager

This chapter describes Enterprise Device Manager procedures to configure IPv6 static routes and theOpen Shortest Path First version 3 (OSPFv3) protocol in the Avaya Ethernet Routing Switch 8800/8600.Routers exchange network topology information with the Open Shortest Path First (OSPF) protocol. Forconceptual information relating to static routes and OSPF, see IPv6 routing fundamentals on page 15.

IPv6 routing configuration navigation• Creating IPv6 static routes on page 137

• Creating a static default route on page 139

• Enabling OSPF on a router on page 140

• Creating OSPF port interfaces on page 143

• Creating OSPF VLAN interfaces on page 146

• Adding NBMA neighbors on page 149

• Creating OSPF areas on page 151

• Creating a virtual link on page 153

• Specifying ASBRs on page 155

• Inserting OSPF area aggregate ranges on page 156

• Configuring route redistribution on page 157

Creating IPv6 static routesTo improve the static route management, you can change static routes directly with the IPv6static routing table manager. The static routing table is separate from the system routing table,which the router uses to control forwarding. Although the tables are separate, entries in thestatic routing table manager automatically change in the system routing table if the next-hopaddress in the static route is reachable and the static route is enabled.


Use static routes to manually configure routes to destination IPv6 address prefixes.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click IPv6.3. Click the Static Routes tab.4. Click Insert.5. In the Dest box, type the IPv6 address.6. In the PrefixLength box, type the length of the prefix for the IPv6 address.7. In the NextHop box, type the IPv6 address of the router through which the specified

route is accessible.8. In the IfIndex box, click Port, VLAN, or Tunnel and select an option.9. In the Cost box, type a number for the distance.

10. Select the Enable check box.11. In the Preference box, type the route preference.12. Click Insert.

The new route appears in the Static Routes tab.

Variable definitionsUse the data in the following table to configure the static route.

Variable ValueDest Configures the IPv6 destination network address. The prefix value must

match the PrefixLength.

PrefixLength Configures the number of leading one bits that form the mask as alogical value. The prefix value must match the value in the Dest box.The range is 0–128.

NextHop Configures the next hop IPv6 address.

IfIndex Select the required VLAN, port, or tunnel.

Cost Configures the cost or distance ratio to reach the destination for thisnode. The range is 1–65535.The default value is 1.

Enable Configures whether the configured static route is available on the port.The default is enable.

IPv6 routing configuration using Enterprise Device Manager


Variable Value

Important:If a static route is disabled, you must enable it before you can addthe route to the system routing table.

Status Indicates the current status of this entry.

Preference Configures the routing preference of the destination IPv6 address. Therange is 1-255.The default value is 5.

Creating a static default routeYou can statically configure the routing switches with the default route statically, or routingswitches can learn the default route through a dynamic routing protocol (RFC1812).

Important:You must configure the destination address and subnet mask for the default static route to0::0.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click IPv6.3. Click the Static Routes tab.4. Click Insert.5. In theDest box, type 0::0.

6. In the PrefixLength box, type 0.

7. In the NextHop box, select the router that leads to the specified route.8. In the IfIndex box, click Port or VLAN and select an option.9. Click Insert.

The default route record is created in the static routing table.

Creating a black hole static routeWhile aggregating or injecting routes to other routers, a router may not use a route to theaggregated destination, which causes a "black hole." To avoid routing loops, you can configure

Creating a static default route


a black hole static route to the destination it is advertising. A black hole route is a route withinvalid next hop, so that the switch drops data packets destined to this network.

Important:To create a black hole static route, the NextHop field must be set to 255.255.255.255.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click IPv6.3. Click the Static Routes tab.4. In the Destfield, type the IPv6 address.5. In the PrefixLength field, type the prefix length of the IPv6 address.6. In the NextHop field, type 255.255.255.255 as the IPv6 address of the router

through which the specified route is accessible.7. In the IfIndex field, indicate the Interface Index by clicking the Port or VLAN button

and selecting an option.8. Check the enable option.9. In the Metric field, type the LocalNextHop value.

10. In the Preference field, select the route preference.11. Click Insert.

The black hole static route record is created in the routing table.

Enabling OSPF on a routerWhen you configure an interface for the OSPF protocol, you must first enable OSPF globallyon the router and then assign an IPv6 address.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click OSPF.3. In the AdminStat option box, select enabled to activate OSPF, or select disabled

to deactivate OSPF.4. Click Apply.

The OSPF protocol is enabled (or disabled) on this router.5. Click Yes to confirm the forced SPF run.

The router performs the SPF run and the OSPF link state database is updated.



Important:After initiating an SPF run, wait 10 seconds before you initiate another SPFrun.

Variable definitionsUse the data in the following table to configure OSPF.

Variable ValueRouterID Identifies the router independent of other routers in the

OSPF domain. The IPv6 Router ID uses the same formatas an IPv4 address.

AdminStat The administrative status of OSPF in the router. The valueenabled activates OSPF on at least one interface; disableddeactivates OSPF on all interfaces. The default isdisabled.

VersionNumber Current version number of OSPF.

AreaBdrRtrStatus A read-only flag identifying this router as an area borderrouter (ABR).

Important:The AreaBdrRtrStatus value must be true to create avirtual router interface.

ASBdrRtrStatus When you select the ASBdrRtrStatus option, the router isconfigured as an autonomous system boundary router(ASBR).The default is false.

AsScopeLsaCount A read-only field displaying the number of external (LS type5) link-state advertisements in the link-state database.

AsScopeLsaCksumSum A read-only field displaying the 32-bit unsigned sum of theLS checksums of the external link-state advertisements inthe link-state database. This sum determines changes andcompares the link-state databases of two routers.

OriginateNewLsas A read-only field displaying the number of new link-stateadvertisements. The number is incremented each time therouter originates a new LSA.

RxNewLsas A read-only field displaying the number of new link-stateadvertisements received. This number does not includenew instantiations of self-originated link-stateadvertisements.

ExtLsaCount A read-only field displaying the number of external LSAs(LS type 0x4005) in the link-state database.

Enabling OSPF on a router


Variable ValueExtAreaLsdLimit The maximum number of nondefault AS-external LSAs

entries stored in the link-state database (LSDB). If thevalue is -1,no limit exists. The default is -1.You must configure the ExtAreaLsdbLimit to the samevalue for all routers attached to the OSPFv3 backbone orany regular OSPFv3 area (that is, exclude OSPFv3 stubareas and NSSAs).

MulticastExtentions A bit mask indicating whether the router is forwarding IPv6multicast datagrams based on the algorithms defined in themulticast extensions to OSPF. Possible forwardingincludes:

• intraAreaMulticast forwards to directly attached areas(called intra-area multicast routing)

• interAreaMulticast forwards between OSPFv3 areas(called inter-area multicast routing)

• interAsMulticast forwards between autonomous systems(called inter-AS multicast routing)

By default, all bits are cleared.

ExitOverflowInterval The number of seconds after entering the overflow state,that a router attempts to leave the overflow state. Therouter resends nondefault AS-external-LSAs. When thevalue is configured to 0, the router does not leave theoverflow state until the router restarts.The default value is 4294967295.

DemandExtentions The router support for demand routing.The default value is disabled.

TrafficEngineeringSupport The router support for traffic engineering extensions.The default value is disabled.

ReferenceBandwidth The reference bandwidth in kilobits per second forcalculating default interface metrics. The default value is100 000 Kbps (100 Mb/s).

RestartSupport The router support for OSPF hitless restart. Optionsinclude no restart support, only planned restarts, or bothplanned and unplanned restarts. Options include:

• none (default)

• plannedOnly

• plannedAndUnplanned

RestartStatus A read-only field indicating the current status of OSPFhitless restart:



Variable Value

• notRestarting (default)

• plannedRestart

• unplannedRestart

RestartInterval The configured OSPF hitless restart timeout interval in therange 1–1800 seconds. The default is 1800.

RestartAge A read-only field indicating the remaining time in the currentOSPF hitless restart interval in seconds. The range is 1–1800.

RestartExitReason A read-only field indicating the outcome of the last attemptat a hitless restart. Options include the following:

• none indicates no restart was attempted.

• inProgress indicates a restart attempt is currentlyunderway.

• completed indicates a completed restart.

• timedout indicates a timed-out restart.

• topologyChanged indicates a cancelled restart due totopology change.

The default is none.

Creating OSPF port interfacesYou configure an OSPF interface, or link, on an IP interface. In the Avaya Ethernet RoutingSwitch 8800/8600, an IP interface is either a single link (brouter port) or a logical interfaceconfigured on a VLAN (multiple ports). The underlying lower level protocols and the routingprotocol itself obtain the state information associated with the interface.

When you enable an OSPF interface, you designate the interface as one of the following types:

• broadcast (active)

• nonbroadcast multiaccess (NBMA)

• point-to-point

• point-to-multipoint

Important:When you enable an OSPF interface, you cannot change the interface type. You must firstdisable the interface. After you disable the interface, you can change the type and reenable

Creating OSPF port interfaces


it. On NMBA interfaces, you must also delete all manually configured neighbors before youchange the type.

Prerequisites

Before you can configure the OSPF protocol on a router interface, you must first enableOSPF globally on the router and assign an IPv6 address to the interface.

Procedure steps

1. In the Device Physical View tab, select the port to configure.2. In the navigation tree, open the following folders: Configuration > Edit > Port.3. Click IPv6.4. Select the IPv6 OSPF Interface tab.5. Click Insert.6. In the AreaId box, click the ellipsis (...) button to select the ID.7. In the Type box, select the type of OSPF interface you want to create: broadcast,

nbma, pointToPoint or pointToMultipoint.8. In the AdminState box, select enabled.9. In the RtrPriority box, modify the value if required.

10. In the TransitDelay, RetransitInterval, HelloInterval, RtrDeadInterval, andPollInterval boxes, modify values as required.

11. In the Metric Value box, type the metric value for a demand for an instance.12. In the InstId box, type the instance ID.13. Click Insert.14. On the Interfaces tab, click Apply.

Variable definitionsUse the data in the following table to configure an OSPF port interface.

Variable ValueIndex The interface index of this OSPFv3 interface. The index

corresponds to the interface index of the IPv6 interfacewhere OSPFv3 is configured.

AreaId Dotted decimal value to designate the OSPF area name.VLANs maintaining the default area setting on the interfacecause the LSDB to be inconsistent.



Variable Value

Important:The area name is not related to an IPv6 address. Youcan use any value for the OSPF area name (forexample, 1.1.1.1 or 200.200.200.200).

Type Type of OSPF interface (broadcast, nbma, point-to-point,or point-to-multipoint).

AdminStat Current administrative state of the OSPF interface(enabled or disabled).

Rtrpriority OSPF priority for the interface during the election processfor the designated router. The interface with the highestpriority number is the designated router. The interface withthe second-highest priority becomes the backupdesignated router. If the priority is 0, the interface cannotbecome the designated router or the backup. The priorityis used only during election of the designated router andbackup designated router. The range is 0–255. The defaultis 1.

TransitDelay Length of time, in seconds (1–1800), required to transmitan LSA update packet over the interface.The default value is 1.

RetransInterval Length of time, in seconds (1–1800), required betweenLSA retransmissions.The default value is 5.

HelloInterval Length of time, in seconds, between hello packets. Thisvalue must be the same for all routers attached to acommon network. The default is 10 seconds.

Important:When you change the Hello interval values, you mustsave the configuration file and reboot the switch for thevalues to be restored and checked for consistency.

RtrDeadInterval Adjacent routers use this interval to determine if the routeris removed from the network. The interval must be identicalon all routers on the subnet and a minimum of four timesthe hello interval. To avoid interpretability issues, theRtrDeadInterval value for the OSPF interface must matchthe RtrDeadInterval value for the OSPF virtual interface.The default is 40 seconds.

PollInterval Length of time, in seconds, between hello packets sent toan inactive OSPF router. The default value is 120.

State A read-only field indicating the OSPFv3 interface state.Options include:

Creating OSPF port interfaces


Variable Value

• down

• loopback

• waiting

• pointToPoint

• designatedRouter

• backupDesignatedRouter

• otherDesignatedRouter

DesignatedRouter A read-only field indicating the router ID of the designatedrouter.

BackupDesignatedRouter A read-only field indicating the router ID of the backupdesignated router.

Events A read-only field indicating the number of times this OSPFinterface changed state or an error occurred.

MetricValue The metric assigned to this interface. The default metricvalue is the reference bandwidth or ifSpeed. The value ofthe reference bandwidth is configured by thercOspfv3ReferenceBandwidth object.

LinkScopeLsaCount A read-only field indicating the number of Link-Scope link-state advertisements in the link-state database.

LinkLsaChksumSum A read-only field indicating the 32-bit unsigned sum of theLink-Scope link-state advertisement LS checksums in thelink-state database. The sum determines a change in therouter link-state database and compares the link-statedatabase of two routers.

Creating OSPF VLAN interfacesYou configure an OSPF interface, or link, on an IP interface. In the Avaya Ethernet RoutingSwitch 8800/8600, an IP interface is either a single link (brouter port) or a logical interfaceconfigured on a VLAN (multiple ports). The underlying low level protocols and the routingprotocol itself obtain the state information associated with the interface.

When you enable an OSPF interface, you designate the interface as one of the following types:

• broadcast (active)

• nonbroadcast multiaccess (NBMA)



• point-to-point

• point-to-multipoint

Important:When you enable an OSPF interface, you cannot change the interface type. You must firstdisable the interface. After you disable the interface, you can change the type and reenableit. On NMBA interfaces, you must also delete all manually configured neighbors before youchange the type.

Prerequisites

Before you can configure the OSPF protocol on a router interface, you must first enableOSPF globally on the router and assign an IPv6 address to the interface.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > VLAN.2. Click VLANs.3. In the Basic tab, select the VLAN for which to configure an OSPF interface.4. Click IPv6.5. Click the IPv6 OSPF Interface tab.6. Click Insert.7. In the AreaId box, click the ellipsis (...) button to select the ID.8. In the Type box, select the type of OSPF interface to create: broadcast, nbma,

pointToPoint, or pointToMultipoint.9. In the AdminState box, select enabled.

10. In the RtrPriority box, modify the value if required.11. In the TransitDelay, RetransitInterval, HelloInterval, RtrDeadInterval, and

PollInterval boxes, modify values as required.12. In the Metric Value box, type the metric value for a demand for an instance.13. In the InstId box, type the instance ID.14. Click Insert.15. On the Interfaces tab, click Apply.

Variable definitionsUse the data in the following table to configure an OSPF VLAN interface.

Creating OSPF VLAN interfaces


Variable ValueIndex The interface index of this OSPFv3 interface. The index

corresponds to the interface index of the IPv6 interfacewhere OSPFv3 is configured.

AreaId Dotted decimal value to designate the OSPF area name.VLANs maintaining the default area setting on the interfacecause the LSDB to be inconsistent.

Important:The area name is not related to an IPv6 address. Youcan use any value for the OSPF area name (forexample, 1.1.1.1 or 200.200.200.200).

Type Type of OSPF interface (broadcast, nbma, point-to-point,or point-to-multipoint).

AdminStat Current administrative state of the OSPF interface(enabled or disabled).

Rtrpriority OSPF priority for the interface during the election processfor the designated router. The interface with the highestpriority number is the designated router. The interface withthe second-highest priority becomes the backupdesignated router. If the priority is 0, the interface cannotbecome the designated router or the backup. The priorityis used only during election of the designated router andbackup designated router. The range is 0—255. Thedefault is 1.

TransitDelay Length of time, in seconds (1—1800), required to transmitan LSA update packet over the interface.The default value is 1.

RetransInterval Length of time, in seconds (1—1800), required betweenLSA retransmissions.The default value is 5.

HelloInterval Length of time, in seconds, between hello packets. Thisvalue must be the same for all routers attached to acommon network. The default is 10 seconds.

Important:When you change the Hello interval values, you mustsave the configuration file and reboot the switch for thevalues to be restored and checked for consistency.

RtrDeadInterval Adjacent routers use this interval to determine if the routeris removed from the network. The interval must be identicalon all routers on the subnet and a minimum of four timesthe Hello Interval. To avoid interpretability issues, theRtrDeadInterval value for the OSPF interface must matchwith the RtrDeadInterval value for the OSPF virtualinterface. The default is 40 seconds.



Variable ValuePollInterval Length of time, in seconds, between hello packets sent to

an inactive OSPF router. The default value is 120.

State A read-only field indicating the OSPFv3 interface state:

• down

• loopback

• waiting

• pointToPoint

• designatedRouter

• backupDesignatedRouter

• otherDesignatedRouter

DesignatedRouter A read-only field indicating the router ID of the designatedrouter.

BackupDesignatedRouter A read-only field indicating the router ID of the backupdesignated router.

Events A read-only field indicating the number of times this OSPFinterface changed state or an error occurred.

MetricValue The metric assigned to this interface. The default value ofthe metric is the reference bandwidth or ifSpeed. The valueof the reference bandwidth is configured by thercOspfv3ReferenceBandwidth object.

LinkScopeLsaCount A read-only field indicating the number of Link-Scope link-state advertisements in the link-state database.

LinkLsaChksumSum A read-only field indicating the 32-bit unsigned sum of theLink-Scope link-state advertisement LS checksums in thelink-state database. The sum determines a change in therouter link-state database and compares the link-statedatabase of two routers.

InstId Enables multiple instances of OSPFv3 over a single link.The switch assigns each protocol instance a separate ID.This ID is significant for local links only. The default is 0.

Adding NBMA neighborsIn contrast to a broadcast network where switches multicast (send to AllSPFRouters andAllDRouters) certain OSPF protocol packets, switches replicate and send NBMA packets toeach neighboring router as unicast. NBMA networks drop all OSPF packets with destinationaddresses AllSPFRouters and AllDRouters. Because the NBMA network does not broadcast,

Adding NBMA neighbors


you must manually configure a list of neighbors and priorities for all routers in the network thatcan become the designated router (DR). Potential DRs use a positive nonzero router priority.

An NMBA interface with a positive nonzero router priority is eligible to become the DR for theNBMA network and is configured with the identification of all attached routers, IPv6 addresses,and router priorities.

Prerequisites

Before you begin this configuration, identify the following:

- specific interfaces to include in the NBMA network- the IPv6 address for each interface- the router priority for each interface- the HelloInterval for the network- the RtrDeadInterval for the network- the PollInterval for the network

After you gather the information, you can configure the interfaces and add neighbors for eachinterface that is eligible to become the DR.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click OSPF.3. Click the Interfaces tab.4. Select an NBMA interface with a positive nonzero router priority.5. Click the NBMA Neighbors tab.6. Click Insert.7. In the IfIndex box, click Port or VLAN, and select the required interface.8. In the Address box, type the IPv6 address for the first neighbor.9. In the Priority box, type the priority for the neighbor.

10. Click Insert.

Variable definitionsUse the data in the following table to configure an OSPF NBMA neighbor.

Variable ValueIfIndex The local link ID of the link over which the neighbor can be

reached



Variable ValueAddress The IPv6 address of the neighbor associated with the local

link.

Priority The priority of this neighbor in the designated routerelection algorithm. The value 0 signifies that the neighboris not eligible to become the designated router on thisparticular network.

RtrId A 32-bit integer (represented as a type IpAddress) uniquelyidentifying the neighboring router in the AutonomousSystem. A value of 0.0.0.0 is returned until a Hello isreceived from the configured neighbor.

State The State of the relationship with this Neighbor.

Creating OSPF areasA stub area does not receive advertisements for external routes, which reduces the size of thelink-state database. A stub area uses only one area border router. Any packets destined foroutside the area are routed to the area border exit point, examined by the area border router,and forwarded to a destination.

A not so stubby area (NSSA) prevents the flooding of AS-External link-state advertisementsinto the area by replacing them with a default route. NSSAs also import small stub (non-OSPF)routing domains into OSPF.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click OSPF.3. Click the Areas tab.4. Click Insert.5. Type the required values.6. Click Insert.7. Click Apply.

Variable definitionsUse the data in the following table to configure the OSPF area.

Creating OSPF areas


Variable ValueId A 32-bit integer uniquely identifying an area. Area ID 0.0.0.0 is

used for the OSPF backbone.VLANs with the default area setting on the interface causeLSDB inconsistency.

ImportAsExtern The area support for importing AS-external link-stateadvertisements. Options include importExternal (default),importNotExternal, or importNssa (not so stubby area).

SpfRuns Indicates the number of SPF calculations OSPF performs.

BdrRtrCount The number of area border routers reachable within this area.The switch calculates the value, initially zero, in each SPFpass.

AsBdrRtrCount The number of autonomous system border routers reachablewithin this area. The switch calculates the value, initially zero,in each SPF pass.

ScopeLsaCount The number of link-state advertisements in the area link-statedatabase, excluding AS External LSAs.

ScopeLsaCksumSum The 32-bit unsigned sum of the link-state advertisements. Thissum excludes external (LS type-5) link-state advertisements.The sum determines changes in a router link-state databaseand compares the link-state databases of two routers.

Summary The area support for summary advertisements in a stub area.The default value is sendAreaSummary.

StubMetric The number of active interfaces in this area.The default value is 10.

NssaTranslatorRole Indicates an NSSA border router ability to translate NSSAtype-7 LSAs into type-5 LSAs:

• always (default)

• candidate

NssaTranslatorState Indicates if and how an NSSA border router translates NSSAtype-7 LSAs into type-5 LSAs:

• enabled indicates the NSSA border router translator role isconfigured to always.

• elected indicates a candidate NSSA border router istranslating type-7 LSAs into type-5.

• disabled indicates a candidate NSSA border router is nottranslating type-7 LSAs into type-5.

NssaTranslatorStabilityInterval

The number of seconds after an elected translator determinestranslation is not required that it resumes translation duties. Thedefault value is 40.



Variable ValueNssaTranslatorEvents A read-only field indicating the number of translator state

changes since the last startup.

StubMetricType Configures the type of metric advertised as a default route:

• ospfv3Metric indicates the OSPF metric

• comparableCost indicates an external type 1

• nonComparable indicates and external type 2

The default value is ospfv3Metric.

Creating a virtual linkWhen you use OSPF, an Avaya Ethernet Routing Switch 8800/8600 that functions as an ABRmust connect directly to the backbone. If the switch does not directly connect, it requires avirtual link. In an Ethernet Routing Switch 8800/8600, you can automatically create virtual linksor you can manually configure a virtual link.

Virtual linking is similar to backup redundancy. With virtual linking configured, the switchcreates a virtual link for vital traffic paths in your OSPF configuration if traffic is interrupted,such as when an interface cable providing connection to the backbone (either directly orindirectly) is disconnected from the switch. Automatic virtual linking ensures that a link iscreated by using another switch.

If automatic virtual linking requires more resources than you want to expend, create manualvirtual links. Manual virtual links conserve resources and provide specific control over virtuallink placement in your OSPF configuration.

OSPF behavior is modified according to OSPF standards so that OSPF routes cannot belearned through an ABR unless it connects to the backbone or through a virtual link.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click OSPF.3. Click the Virtual If tab.4. Click Insert.5. In the AreaId box, specify the area ID for the transit area.

The transit area is the common area between two ABRs.6. In the Neighbor box, specify the neighbor ID.

The neighbor ID is the IP router ID of the ABR through which the other ABR mustroute traffic destined for the backbone.

Creating a virtual link


7. Click Insert.8. To verify that the virtual link is active, refresh the Virtual If tab and check the State

column.

If the state is point-to-point, the virtual link is active. If the state is down, the virtuallink is configured incorrectly.

Variable definitionsUse the data in the following table to configure the virtual link.

Variable ValueAreaId A read-only field indicating the transit area ID that the virtual link

traverses.

Neighbor A read-only field indicating the router ID of the virtual neighbor.

TransitDelay The estimated number of seconds required to transmit a link-stateupdate packet over this interface. The range is 1–1800 and thedefault is 1 second.

RetransInterval The number of seconds between link-state advertisement, andretransmissions, for adjacencies belonging to this interface. Thisvalue is also used when retransmitting the database description andthe link-state request packets. This value must exceed the expectedround- trip time. The range is 1–1800 and the default is 5 seconds.

HelloInterval The length of time, in seconds, between the hello packets that therouter sends on the interface. This value must be the same for thevirtual neighbor. The default value is 10 seconds.

RtrDeadInterval The number of seconds during which router hello packets are notreceived before neighbors declare the router down. Use a multipleof the hello interval. You must configure this same value on the virtualneighbor. The default value is 60 seconds.

State OSPF virtual interface states.

Events The number of state changes or error events on this virtual link

LinkScopeLsaCount The total number of Link-Scope link-state advertisements in thisvirtual link's link-state database.

LinkLsaCksumSum The 32-bit unsigned sum of the Link-Scope link-stateadvertisements' LS checksums contained in this virtual link's link-state database. The sum can be used to determine if there has beena change in a router's link state database, and to compare the link-state database of two routers.



Specifying ASBRsAutonomous system boundary routers (ASBR) advertise non-OSPF routes into OSPFdomains, communicating routes throughout the OSPF routing domain. A router can functionas an ASBR if you connect one or more interfaces to a non-OSPF network (for example, RIPor BGP).

To conserve resources, or to specifically control which routers perform as ASBRs, you can limitthe number of ASBRs on your network.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click OSPF.3. Select the ASBdrRtrStatus box to designate the router as an ASBR.

OR

Clear the box to remove ASBR status from the router.4. Click Apply.

If Metrics tab fields

Table 10: If Metrics tab fields

Field DescriptionIpAddress The Internet Protocol address of the device used to represent a point

of attachment in a TCP/IP internetwork.

AddressLessIf For the purpose of easing the instancing of addressed andaddressless interfaces. This variable takes the value 0 on interfaceswith IP addresses and the corresponding value of ifIndex forinterfaces having no IP address.

TOS Type of service is a mapping to the IP type of service flags as definedin the IP forwarding table MIB.

Value The value advertised to other areas indicating the distance from theOSPF router to any network in the range.

Status Active or not active. Not configurable.

Specifying ASBRs


Stub Area Metrics tab fields

Table 11: Stub Area Metrics tab fields

Field DescriptionAreaID The 32-bit identifier for the stub area. On creation, it

can be derived from the instance.

TOS The type of service associated with the metric. Oncreation, it can be derived from the instance.

Metric The metric value applied at the indicated type ofservice. By default, it equals the lowest metric value atthe type of service among the interfaces to otherareas.

Status Active or not active. Not configurable.

Inserting OSPF area aggregate rangesConfigure an area address range on the OSPF router to reduce the number of ABRadvertisements into other OSPF areas. An area address range is an implied contiguous rangeof area network addresses for which the ABR advertises a single summary route.

You can use any value for the OSPF area name (for example, 1.1.1.1 or 200.200.200.200).

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click OSPF.3. Click the Area Aggregate tab.4. Click Insert.5. In the AreaId box, click the ellipsis button (...) to select the required area ID of the

aggregate address.6. In the AreaLsdbType box, select the required option:

• interAreaPrefixLsa: to generate an aggregated summary• nssaExternalLink: to generate an NSSA link summary

7. In the Prefix box, type the prefix of the area IPv6 address.8. In the Prefix Length box, type the number of bits you want to advertise from the

IPv6 address.



9. In the Effect box, select the required option:

• advertiseMatching: to advertise the aggregate summary LSA with the samelink-state ID

• doNotAdvertiseMatching: to suppress all networks that fall within the entirerange

10. In the AdvertiseMetric box, type a cost value (in the range 0 to 65535) to advertisefor the OSPF area range.

11. Click Insert.

Variable definitionsUse the data in the following table to configure the IPv6 OSPF area aggregate.

Variable ValueAreaID Specifies the address of an OSPF area. Use

dotted decimal notation to specify the areaname.

AreaLsdbType Specifies the LSA type.

Prefix Specifies the IPv6 address range of anOSPF area.

PrefixLength Specifies the prefix length value for thisaddress.

Effect Specifies the area range advertise mode asadvertise or no-advertise.The default value is advertiseMatching.

AdvertiseMetric Specifies the advertise metric value in therange 0 to 65535.

Configuring route redistributionYou can configure a redistribute entry for OSPF to announce routes of a certain source type,such as static, RIP, or direct. If you do not configure a route policy field for a redistribute entry,the switch uses the default action on the basis of metric, metric-type, and subnet. The defaultaction is called basic redistribution. Otherwise, the specified route policy performs detailedredistribution. If you do not configure a redistribution entry, the switch generates no externalLSA for non-OSPF routes.

Configuring route redistribution


Important:Changing OSPF redistribute contexts is a process-oriented operation that can affect systemperformance and network reachability. Avaya recommends that you change defaultpreferences for an OSPF redistribute context before you enable the protocols.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click OSPF.3. Click the Redistribute tab.

The Redistribute tab appears.4. Click Insert.5. Modify options as required.6. Click Insert.7. Click Apply.

Variable definitionsUse the data in the following table to configure the route redistribution.

Variable ValueDstVrfId Specifies the ID of the destination virtual router and forwarder (VRF).

Protocol Specifies any one of the dynamic routing protocols, which is interestedin receiving the external routing info.

SrcVrfId Specifies the ID of the source VRF.

RouteSource Select the route source protocol for the redistribution entry.

Enable Enable (or disable) an OSPF redistribution entry for a specified sourcetype.You can also enable or disable this feature in the OSPF Redistribute tabof the Policy dialog box by clicking in the field and selecting enable ordisable from the menu.



Chapter 9: IPv6 routing configurationusing the CLI

This chapter contains procedures to configure IPv6 static routes and the Open Shortest Path First version3 (OSPFv3) protocol.

IPv6 routing configuration navigation• Job aid: Roadmap of IPv6 static route and OSPFv3 CLI commands on page 159

• Configuring IPv6 static routes on page 162

• Configuring OSPF global parameters on page 165

• Configuring OSPF areas on page 165

• Configuring OSPF area ranges on page 167

• Configuring OSPF area virtual interfaces on page 168

• Configuring OSPF direct redistribution on page 171

• Configuring OSPF static redistribution on page 172

• Configuring port-based OSPF parameters on page 173

• Configuring port-based OSPF neighbor parameters on page 175

• Configuring OSPF parameters for a VLAN on page 176

• Configuring OSPF neighbor parameters for a VLAN on page 178

Job aid: Roadmap of IPv6 static route and OSPFv3 CLIcommands

The following table lists the commands and parameters that you use to perform the proceduresin this section.


Table 12: Job aid: Roadmap of IPv6 static route and OSPFv3 CLI commands

Command Parameterconfig ethernet <ports> ipv6 ospf info

admin-status <enable|disable>

create <area> {priority <value>] [metric<value>] [retransmit-interval <value>][transit-delay <value>] [hello-interval<value>] [dead-interval <value>] [type<value>]

delete

hello-interval <seconds>

dead-interval <seconds>

poll-interval <seconds>

metric <metric>

priority <priority>

retransmit-interval <seconds>

transit-delay <seconds>

config ethernet <ports> ipv6 ospf nbma-nbr<ipv6address>

info

create <priority>

delete

priority <priority>

config ipv6 ospf info

disable

enable

as-boundary-router <enable|disable>

router-id <RTR_ADDR>

config ipv6 ospf area <ipaddr> info

create [<type>] [stub-metric <value>][translator-role <value>]

delete

import-summaries <true|false>

nssa <true|false>

stub <true|false>

stub-metric <cost>

IPv6 routing configuration using the CLI


Command Parameterconfig ipv6 ospf area <ipaddr> range<ipv6addr-prefix>

info

advertise-metric <cost> lsa-type <value>

advertise-mode <advertise|no-advertise>

delete lsa-type <value>

create advertise-mode <value> lsa-type<value> [advertise-metric <value>]

config ip ospf area <ipv6addr> virtual-interface <ipv6addr>

info

create


delete




config ipv6 ospf redistribute direct info

disable

enable

config ipv6 ospf redistribute static info

disable

enable

config ipv6 static-route info

create <ipv6addr-prefix> cost <value> [next-hop <value>] port <value> [vlan <value>][tunnel <value>] [preference <value>]

delete <ipv6addr-prefix> [next-hop <value>][port <value>] [vlan <value>] [tunnel<value>]

disable <ipv6addr-prefix> [next-hop<value>] [port <value>] [vlan <value>][tunnel <value>]

enable <ipv6addr-prefix> [next-hop <value>][port <value>] [vlan <value>] [tunnel<value>]

preference <preference> <ipv6addr-prefix>[next-hop <value>] [port <value>] [vlan<value>] [tunnel <value>]

Job aid: Roadmap of IPv6 static route and OSPFv3 CLI commands


Command Parameterconfig vlan <vid> ipv6 ospf info


create <area> [priority <value>] [metric<value>] [retransmit-interval <value>][transit-delay <value>]

delete




metric <metric>

priority <priority>



config vlan <vid> ipv6 ospf nbma-nbr<ipv6address>

info

create <priority>

delete

priority <priority>

Configuring IPv6 static routesConfigure IPv6 static routes to change static routes directly with the IPv6 static routing tablemanager. Create a new static route or modify existing static route parameters.

Procedure steps

Configure static routes by using the following command:

config ipv6 static-route

Variable definitionsUse the data in the following table to use the config ipv6 static-route command.



Variable Valuecreate <ipv6addr-prefix> cost<value> [next-hop <value> ] port<value> [vlan <value> ] [tunnel<value> ] [preference <value> ]

Adds a static or default route to the switch.

• ipv6addr-prefix is the IP address and prefix for theroute destination as a string 0–46 characters.

• cost <value> is the metric of the route in the rangeof 1–65535.

• next-hop <value> is the IP address of the next-hoprouter; the next router at which packets must arriveon this route. The string length is 0–46 characters.

• port <value> is the slot/port number.

• vlan <value> is the VLAN ID in the range of 1–4094.

• tunnel <value> configures the tunnel ID in the rangeof 1–2147477248.

• preference <value> configures the preference valuein the range of 1–255.

delete <ipv6addr-prefix> [next-hop<value> ] [port <value> ] [vlan<value> ] [tunnel <value> ]

Deletes a static route.


• next-hop <value> is the IP address of the next-hoprouter-- the next router at which packets must arriveon this route. The string length is 0–46 characters.



• tunnel <value> is the tunnel ID value in the range 1–2147477248. When you select a tunnel, you mustprovide the VLAN, port, and next hop. You mustconfigure an IPv6 tunnel before entering this value.

disable <ipv6addr-prefix> [next-hop <value> ] [port <value> ] [vlan<value> ] [tunnel <value> ]

Disables a static route.


• next-hop <value> is the IP address of the next hoprouter; the next router at which packets must arriveon this route. The string length is 0–46 characters.



• tunnel <value> is the tunnel ID value in the range of1-5000. When you select a tunnel, you must provide

Configuring IPv6 static routes


Variable Value

the VLAN, port, and next hop. You must configurean IPv6 tunnel first.

enable <ipv6addr-prefix> [next-hop<value> ] [port <value> ] [vlan<value> ] [tunnel <value> ]

Enables a static route.


• next-hop <value> is the IP address of the next-hoprouter–the next router at which packets must arriveon this route. The string length is 0–46 characters.



• tunnel <value> is the tunnel ID value in the range of1–2147477248. When you select a tunnel, you mustprovide the VLAN, port, and next hop. You mustconfigure an IPv6 tunnel first.

info Displays characteristics of the created static route.

preference <preference><ipv6addr-prefix> [next-hop<value> ] [port <value> ] [vlan<value> ] [tunnel <value> ]

Modifies static route preference.

• preference configures the route preference in therange of 1–255.


• next-hop <value> is the IP address of the next-hoprouter–the next router at which packets must arriveon this route. The string length is 0–46 characters.



• tunnel <value> is the tunnel ID value in the range of1-5000. When you select a tunnel, you must providethe VLAN, port, and next hop. You must configurean IPv6 tunnel before you enter this value.

Important:A black hole route is a route with an invalid next hop,so the switch drops data packets destined to thisnetwork. When you specify a route preference, besure that you configure the preference valueappropriately so that when the black hole route isused, it is elected as the best route.



Configuring OSPF global parametersConfigure Open Shortest Path First (OSPF) version 3 global parameters to affect OSPF routingon the entire switch. Routers use the OSPFv3 protocol to exchange network topologyinformation, providing each router with a map of the network.

Procedure steps

Configure OSPFv3 by using the following command:

config ipv6 ospf

Variable definitionsUse the data in the following table to use the config ipv6 ospf command.

Variable Valueas-boundary-router <enable|disable>

Enables or disables the OSPF Autonomous Systemboundary router. The default is disable.

disable Globally disables OSPF on the switch.

enable Globally enables OSPF on the switch.

info Displays the current OSPF configuration on theswitch.

router-id <RTR_ADDR> Configures the OSPF router ID IPv4 address.<RTR_ADDR> is the IPv4 address in dotted decimalformat {a.b.c.d}.

Configuring OSPF areasOSPF supports hierarchical routing by dividing the Autonomous System into different areas.When two or more areas exist, the backbone area (area 0.0.0.0) must always be present.


Configuring OSPF global parameters


Procedure steps

Configure an OSPF area by using the following command:

config ipv6 ospf area <ipaddr>

Variable definitionsUse the data in the following table to use the config ipv6 ospf area command.

Variable Valuecreate [ <type> ][stub-metric<value> ][translator-role <value> ]

Creates an OSPF area.

• type is the type of area (stub or nssa).

• stub-metric <value> is the cost from 0–16777215.This is the metric value applied at the indicated typeof service.

• translator-role <value> is either 1 for always or 2 forcandidate.

delete Deletes an OSPF area.

import-summaries <true|false> Configures the area support for importing summaryadvertisements into a stub area. Use this entry only ifthe stub area is configured to true.

info Displays OSPF area characteristics.

ipaddr Specifies the address of an OSPF area. Use dotteddecimal notation to specify the area name.

nssa <true|false> Configures a not so stubby area (true or false). AnNSSA prevents flooding of normal routeadvertisements into the area by replacing them with adefault route.

stub <true|false> Configures the import external option for this area tobe stub or not {true|false}. A stub area uses only oneexit point (router interface) out of the area.

stub-metric <cost> Stub default metric for this stub area.cost is the range from 0–16777215. This is the metricvalue applied at the indicated type of service.



Configuring OSPF area rangesConfigure an area address range on the OSPF router to reduce the number of ABRadvertisements into other OSPF areas. An area address range is an implied contiguous rangeof area network addresses for which the ABR advertises a single summary route.


Procedure steps

Configure an OSPF area range by using the following command:

config ipv6 ospf area <ipaddr> range <ipv6addr-prefix>

Variable definitionsUse the data in the following table to use the config ipv6 ospf area rangecommand.

Variable Valueadvertise-metric <cost> lsa-type<value>

Specifies the advertise metric value and LSA type.

• cost is the advertise metric vlaue in the range 0–65535.

• value is the LSA type as either inter-area-prefix-linkor nssa-extlink.


Specifies the area range advertise mode as advertiseor no-advertise.

delete lsa-type <value> Deletes an LSA type.

value is the LSA type as either inter-area-prefix-linkor nssa-link.

create advertise-mode <value> lsa-type <value> [advertise-metric<value> ]

Creates an advertise mode for a range of IPv6 areaaddresses.

Configuring OSPF area ranges


Variable Value

• create advertise-mode <value> is advertise or no-advertise.

• lsa-type <value> value is the LSA type as eitherinter-area-prefix-link or nssa-extlink.

• advertise-metric <value> is the advertise metric 0–65535.

info Displays OSPF range characteristics.

ipaddr Specifies the address of an OSPF area. Use dotteddecimal notation to specify the area name.

ipv6addr-prefix Configures the IPv6 address range of an OSPF area.The string length is 0–255 characters.

Configuring OSPF area virtual interfacesIf a remote OSPF ABR uses no connection to the backbone area but needs to be part of thesame routing domain (AS) in which the switch resides, configure an OSPFv3 virtual interfaceto the ABR.

You can use any value for the OSPFv3 area name (for example, 1.1.1.1 or200.200.200.200).

Important:OSPFv3 behavior is modified according to OSPFv3 standards so that OSPFv3 routescannot be learned through an area border router (ABR) unless the router connects to thebackbone or through a virtual link.

Procedure steps

Configure an OSPFv3 area virtual interface by using the following command:

config ipv6 ospf area <ipaddr> virtual-interface <ipaddr>

Variable definitionsUse the data in the following table to use the config ip ospf area virtual-interfacecommand.



Variable Valuecreate Creates a virtual interface for an area.

dead-interval <seconds> Specifies the dead interval, in seconds, as arange 1–4095.

delete Deletes a virtual interface for an area.

hello-interval <seconds> Specifies the hello interval, in seconds, at whichhello packets send between switches for a virtualinterface in an OSPF area. The range is 1–65535.

info Displays OSPF virtual interface characteristics.

ipaddr Specifies the address of an OSPF area. Usedotted decimal notation to specify the areaname.

retransmit-interval <seconds> Configures the retransmit interval for the OSPFinterface, the number of seconds between link-state advertisement retransmissions.seconds is an integer between 1–1800.

transit-delay <seconds> Configures the transit delay time for the OSPFinterface, the estimated time in seconds it takesto transmit a link-state update packet over theinterface.seconds is an integer between 1–1800.

Configuring an OSPF interfaceConfigure an OSPF interface for designated router (DR) and backup designated router (BDR)election to reduce the amount of routing traffic.

Prerequisites

Before you can configure OSPF parameters on an interface, you must first configure an IPaddress on that interface.

Procedure steps

Configure an OSPF interface by using the following command:

Configuring an OSPF interface


config ipv6 ospf interface <interface-id>

Variable definitionsUse the data in the following table to use the config ipv6 ospf interface command.

Variable Valueadmin-status <enable|disable> Configures the state (enabled or disabled) of the

OSPF interface.

create <area> [priority <value> ][metric <value> ] [retransmit-interval <value> ] [transit-delay<value> ] [hello-interval <value> ][dead-interval <value> ] [type<value> ]

Creates an OSPF interface.

• <area> is the area ID (0–2147483647) or area IPaddress (0.0.0.0–255.255.255.255) {a.b.c.d}.

• priority <value> is the priority in the range 0–255.

• metric <value> is the metric in the range 0–65535.

• retransmit-interval <value> is the retransmit intervalin the range 1–1800 seconds.

• transit-delay <value> is the transmit interval in therange 1–1800 seconds.

• hello-interval <value> is the hello interval in therange 1–65535 seconds.

• dead-interval <value> is the dead interval in therange 1–4095 seconds.

• type <st|nbma|p2p|p2mp> is the type of interfacewhere 1 is ethernet, 2 is nbma, 3 is p2p, 4 islookback, and 5 is p2mp.

dead-interval <seconds> Configures the OSPF dead interval for the interface.seconds is the number of seconds the switch OSPFneighbors wait before determining that this OSPFrouter is down. The range is from 1–2147483647. Thisvalue must be at least four times the hello intervalvalue. The default is 40.

delete Deletes an OSPF interface.

hello-interval <seconds> Configures the OSPF hello interval for the interface.seconds is the number of seconds between hellopackets sent on this interface. The range is 1–65535.The default is 10.

Important:When you change the hello interval values, youmust save the configuration file and reboot theswitch for the values to be restored and checked forconsistency.



Variable Valueinfo Displays OSPF characteristics for the interface.

interface-id Specifies the interface ID number in the range 0–4095.

metric <metric> Configures the OSPF metric for the interface. Theswitch advertises the metric in router linkadvertisements.metric is the range 0–65535.

poll-interval <seconds> Configures the polling interval for the OSPF interfacein seconds.seconds is between 0–2147483647.

priority <priority> Configures the OSPF priority for the interface duringthe election process for the designated router. Theinterface with the highest priority number is thedesignated router. The interface with the second-highest priority becomes the backup designatedrouter. If the priority is 0, the interface cannot becomeeither the designated router or a backup. The priorityis used only during election of the designated routerand backup designated router.priority is in the range 0–255. The default is 1.

retransmit-interval <seconds> Configures the retransmit interval for the OSPFinterface, the number of seconds between link-stateadvertisement retransmissions.seconds is an integer between 1–1 800.

transit-delay <seconds> Configures the transit delay time for the OSPFinterface, the estimated time in seconds it takes totransmit a link-state update packet over theinterface.seconds is an integer between 1–1 800.

Configuring OSPF direct redistributionEnable or disable direct redistribution to obtain information about redistributing IPv6 directroutes into an OSPFv3 routing domain.

Procedure steps

Configure OSPF direct redistribution by using the following command:

Configuring OSPF direct redistribution


config ipv6 ospf redistribute direct

Variable definitionsUse the data in the following table to use the config ipv6 ospf redistribute directcommand.

Variable Valuedisable Disables an OSPF direct redistribution policy. The

default value is disable.

enable Enables an OSPF direct redistribution policy.

info Displays information about the OSPF directredistribution policy settings.

Configuring OSPF static redistributionEnable or disable static redistribution to obtain information about redistributing IPv6 staticroutes into an OSPFv3 routing domain.

Procedure steps

Configure OSPF static redistribution by using the following command:

config ipv6 ospf redistribute static

Variable definitionsUse the data in the following table to use the config ipv6 ospf redistribute staticcommand.

Variable Valuedisable Disables an OSPF static redistribution policy. The

default value is disable.

enable Enables an OSPF static redistribution policy.

info Displays information about the OSPF staticredistribution policy settings.



Configuring port-based OSPF parametersConfigure port-based OSPFv3 parameters to customize your OSPF IPv6 configuration.

Important:Both sides of the OSPF connection must use the same authentication type and key.

Variable definitionsUse the data in the following table to use the config ethernet ipv6 ospf command.


OSPF interface.

create <area> [priority <value> ] [metric<value> ] [retransmit-interval <value> ][transit-delay <value> ] [hello-interval<value> ][dead-interval <value> ] [type <value> ]


• <area> is the area ID (0–2147483647) or areaIP address (0.0.0.0 to 255.255.255.255){a.b.c.d}.



• retransmit-interval <value> is the retransmitinterval in the range 1–1800 seconds.

• transit-delay <value> is the transit delay in therange 1–1800 seconds.

• hello-interval <value> is the hello interval in therange 1–65535 seconds.

• dead-interval <value> is the dead interval in therange 0–4095 seconds.

• type <st|nbma|p2p|p2mp> is the type ofinterface where 1 is ethernet, 2 is nbma, 3 isp2p, 4 is lookback, and 5 is p2mp.

dead-interval <seconds> Configures the OSPF dead interval for theinterface.seconds is the number of seconds the switchOSPF neighbors wait before determining that thisOSPF router is down. The range is from 1–4095.

Configuring port-based OSPF parameters


Variable ValueThis value must be at least four times the Hellointerval value. The default is 40.


hello-interval <seconds> Configures the OSPF hello interval for theinterface.seconds is the number of seconds between hellopackets sent on this interface. The range is 1–65535. The default is 10.

Important:When you change the hello interval values, youmust save the configuration file and restart theswitch to restore the values and check forconsistency.

info Displays OSPF characteristics on the port.

metric <metric> Configures the OSPF metric for the interface. Theswitch advertises the metric in router linkadvertisements.metric is the range 0–65535.

poll-interval <seconds> Configures the polling interval for the OSPFinterface in seconds.seconds is 0–214783674.

ports Specifies the port or range of ports you configurein the format slot/port.

priority <priority> Configures the OSPF priority for the interfaceduring the election process for the designatedrouter. The interface with the highest prioritynumber is the designated router. The interfacewith the second-highest priority becomes thebackup designated router. If the priority is 0, theinterface cannot become either the designatedrouter or a backup. The priority is used only duringelection of the designated router and backupdesignated router. The range is 0–255. Thedefault is 1.

retransmit-interval <seconds> Configures the retransmit interval for the OSPFinterface; the number of seconds between link-state advertisement retransmissions.seconds is an integer 1–1800.

transit-delay <seconds> Configures the transit delay time for the OSPFinterface, the estimated time, in seconds,required to transmit a link-state update packetover the interface.seconds is an integer 1–1800.



Procedure steps

Configure port-based OSPF by using the following command:

config ethernet <ports> ipv6 ospf

Configuring port-based OSPF neighbor parametersConfigure port-based OSPFv3 neighbor parameters for specified ports to customize yourOSPF IPv6 configuration.


Procedure steps

Configure port-base OSPF neighbor parameters by using the following command:

config ethernet <ports> ipv6 ospf nbma-nbr <ipv6address>

Important:You must use an IPv6 link-local address as an NBMA neighbor.

Variable definitionsUse the data in the following table to use the config ethernet ipv6 ospf nbma-nbrcommand.

Variable Valuecreate <priority> Creates a neighbor priority. The range is 0–255. The

default is 1.

delete Deletes an OSPF NBMA neighbor.


ipv6address Specifies the IPv6 address of the neighbor as a stringof 0–43.

Configuring port-based OSPF neighbor parameters


Variable Valueports Specifies the port or range of ports to configure in the

format slot/port.

priority <priority> Configures the OSPF priority for the interface duringthe election process for the designated router. Theinterface with the highest priority number is thedesignated router. The interface with the second-highest priority becomes the backup designatedrouter. If the priority is 0, the interface cannot becomeeither the designated router or a backup. The priorityis used only during election of the designated routerand backup designated router. The range is 0–255.The default is 1.

Configuring OSPF parameters for a VLANConfigure OSPFv3 parameters for a specified VLAN to customize your OSPF IPv6configuration.

Procedure steps

Configure OSPF parameters for a VLAN by using the following command:

config vlan <vid> ipv6 ospf

Variable definitionsUse the data in the following table to use the config vlan ipv6 ospf command.

Variable Valueadmin-status <enable|disable>

Configures the state (enabled or disabled) of the OSPFinterface.

create <area> [priority<value> ] [metric<value> ] [retransmit-interval <value> ] [transit-delay <value> ] [hello-interval <value> ] [dead-interval <value> ] [type<value> ]


• <area> is the area IP address (0.0.0.0 to 255.255.255.255){a.b.c.d}.





Variable Value

• retransmit-interval <value> is the retransmit interval in therange 1–1800 seconds.

• transit-delay <value> is the transit delay in the range 1–1800seconds.

• hello-interval <value> is the hello interval in the range 1–65535 seconds.

• dead-interval <value> is the dead interval in the range 1–4095seconds.

• type <st|nbma|p2p|p2mp> is the type of interface where 1 isethernet, 2 is nbma, 3 is p2p, 4 is lookback, and 5 is p2mp.

dead-interval <seconds> Configures the OSPF dead interval for the interface.seconds is the number of seconds the switch OSPF neighborswait before determining that this OSPF router is down. Therange is 1–4095. This value must be at least four times the hellointerval value. The default is 40.


hello-interval <seconds> Configures the OSPF hello interval for the interface.seconds is the number of seconds between hello packets senton this interface. The range is 1–65535. The default is 10.

Important:When you change the hello interval values, you must savethe configuration file and reboot the switch to restore thevalues and check for consistency.

info Displays OSPF characteristics on the VLAN.

metric <metric> Configures the OSPF metric for the interface. The switchadvertises the metric in router link advertisements.metric is the range 0–65535.

poll-interval <seconds> Configures the polling interval for the OSPF interface inseconds.seconds is 0–2147483647.

priority <priority> Configures the OSPF priority for the interface during theelection process for the designated router. The interface withthe highest priority number is the designated router. Theinterface with the second-highest priority becomes the backupdesignated router. If the priority is 0, the interface cannotbecome either the designated router or a backup. The priorityis used only during election of the designated router and backupdesignated router.priority is in the range 0–255. The default is 1.

Configuring OSPF parameters for a VLAN


Variable Valueretransmit-interval<seconds>

Configures the retransmit interval for the OSPF interface; thenumber of seconds between link-state advertisementretransmissions.seconds is an integer from 1–1800.

transit-delay <seconds> Configures the transit delay time for the OSPF interface, theestimated time, in seconds, required to transmit a link-stateupdate packet over the interface.seconds is an integer from 1–1800.

vid Specifies a unique integer value in the range 1–4094 thatidentifies the VLAN to configure.

Configuring OSPF neighbor parameters for a VLANConfigure port-based OSPFv3 neighbor parameters for a VLAN to customize your OSPF IPv6configuration.


Procedure steps

Configure OSPF neighbor parameters for a VLAN by using the following command:

config vlan <vid> ipv6 ospf nbma-nbr <ipv6address>

Variable definitionsUse the data in the following table to use the config vlan ipv6 ospf nbma-nbrcommand.

Variable Valuecreate <priority> Creates a neighbor priority.

priority is in the range 0–255. The default is 1.

delete Deletes an OSPF NBMA neighbor.




Variable Valueipv6address Specifies the IPv6 address of the neighbor as a string of 0–43

characters.

priority <priority> Configures the OSPF priority for the interface during theelection process for the designated router. The interface withthe highest priority number is the designated router. Theinterface with the second-highest priority becomes the backupdesignated router. If the priority is 0, the interface cannotbecome either the designated router or a backup. The priorityis used only during election of the designated router and backupdesignated router.priority is in the range 0–255. The default is 1.

vid Specifies a unique integer value in the range 1–4094 thatidentifies the VLAN to configure.

Configuring OSPF neighbor parameters for a VLAN




Chapter 10: IPv6 routing configurationusing the ACLI

This chapter contains procedures to configure IPv6 static routes and the Open Shortest Path First version3 (OSPFv3) protocol.

IPv6 routing configuration navigation• Job aid: Roadmap of IPv6 static route and OSPFv3 ACLI commands on page 181

• Configuring IPv6 static routes on page 183

• Configuring OSPF global parameters on page 185

• Configuring OSPF areas on page 186

• Configuring OSPF area ranges on page 187

• Configuring OSPF area virtual interfaces on page 188

• Configuring an OSPF interface on page 190

• Configuring OSPF direct redistribution on page 192

• Configuring OSPF static redistribution on page 193

• Configuring port-based OSPF neighbor parameters on page 193

• Configuring OSPF parameters for a VLAN on page 194

• Configuring OSPF neighbor parameters for a VLAN on page 197

Job aid: Roadmap of IPv6 static route and OSPFv3 ACLIcommands

The following table lists the commands and parameters that you use to perform the proceduresin this section.


Table 13: Job aid: Roadmap of IPv6 static route and OSPFv3 ACLI commands


ipv6 route <Ipv6 address/prefix> enable [next-hop <Ipv6 address/prefix>] [port<slot/port>] [tunnel <tunnel-id>] [vlan <vlan id>]

cost <1-65535>

preference <1-255>

router ospf ipv6-enable


ipv6 ospf area <A.B.C.D> enable

cost <metric>




priority <value>


transmit-delay <seconds>

ipv6 ospf nbma-nbr <Ipv6address/prefix-len> priority <priority>

OSPF Router Configuration mode

ipv6 as-boundary-router enable

router-id <A.B.C.D>

ipv6 area <A.B.C.D> default-cost <cost>

import <value>

import-summaries enable

translator-role <value>

type <nssa|stub>

ipv6 ipv6 area range <Ipv6 address/prefix><A.B.C.D>

inter-area-prefix-link advertise-mode<advertise|not-advertise> advertise-mode<advertise|not-advertise> advertise-metric<0–65535>

nssa-extlink advertise-metric <0-65535>

ipv6 area virtual-link <area IP address><virtual link IP address>



IPv6 routing configuration using the ACLI


Command Parameterretransmit-interval <seconds>


ipv6 redistribute direct enable

static enable

Configuring IPv6 static routesConfigure IPv6 static routes to change static routes directly with the IPv6 static routing tablemanager. Create a new static route or modify existing static route parameters.

Prerequisites


Procedure steps

1. Create the static route by using the following command:

ipv6 route <Ipv6 address/prefix> enable [next-hop <Ipv6address/prefix>] [port <slot/port>] [tunnel <tunnel-id>][vlan <vlan id>]

2. Assign the cost by using the following command:

ipv6 route <Ipv6 address/prefix> cost <1-65535>3. Configure the preference by using the following command:

ipv6 route <Ipv6 address/prefix> preference <1-255>

Variable definitionsUse the data in the following table to use the ipv6 route command.

Variable Valuecost <1-65535> cost <value> is the metric of the route in the range

of 1–65535.

Configuring IPv6 static routes


Variable Valueenable [next-hop <Ipv6 address/prefix>] [port <slot/port>] [tunnel<tunnel-id>] [vlan <vlan id>]

Adds a static or default route to the switch.

• ipv6address/prefix is the IP address and prefix forthe route destination as a string of 0–46characters.

• next-hop <value> is the IP address of the next-hoprouter—the next router at which packets must arriveon this route. The string length is 0–46 characters.When creating a black hole static route, set this fieldto 255.255.255.255 as the IP address of the routerthrough which the specified route is accessible.



• tunnel <value> configures the tunnel ID in the rangeof 1-5000.

preference <preference><ipv6addr-prefix> [next-hop<value> ] [port <value> ] [vlan<value> ] [tunnel <value> ]

Modifies static route preference.

• preference configures the route preference in therange of 1–255. The default value is 0.


• next-hop <value> is the IP address of the next-hoprouter—the next router at which packets must arriveon this route. The string length is 0–46 characters.



• tunnel <value> is the tunnel ID value in the range of1-5000. When you select a tunnel, you must providethe VLAN, port, and next hop. You must configurean IPv6 tunnel before you enter this value.

Important:A black hole route is a route with an invalid next hop,so the switch drops data packets destined to thisnetwork. When you specify a route preference, besure that you configure the preference valueappropriately so that when you use the black-holeroute, it is elected as the best route.



Configuring OSPF global parametersConfigure Open Shortest Path First (OSPF) global parameters to affect OSPF routing on theentire switch. Routers use the OSPF protocol to exchange network topology information,providing each router with a map of the network.

Prerequisites


Procedure steps

1. Enable OSPF for IPv6 by using the following command:

router ospf ipv6-enable2. Log on to the OSPF Router configuration mode by using the following command:

router ospf3. Enable the OSPF autonomous system boundary router by using the following

command:

ipv6 as-boundary-router enable4. Configure the OSPF router ID by using the following command:

ipv6 router-id <A.B.C.D>

Variable definitionsUse the data in the following table to use the ipv6 router-id command.

Variable Valuerouter-id <A.B.C.D> Configures the OSPF router ID IPv6 address.

Configuring OSPF global parameters


Configuring OSPF areasOSPF supports hierarchical routing by dividing the Autonomous System into different areas.When two or more areas exist, the backbone area (area 0.0.0.0) must always be present.


Prerequisites

You must log on to the OSPF Router Configuration mode in the ACLI.

Procedure steps

Create and configure an OSPF area by using the following command:

ipv6 area <A.B.C.D> default-cost <cost> import <value> [import-summaries enable] translator-role <value> type <nssa|stub>

Variable definitionsUse the data in the following table to use the ipv6 area command.

Variable Valuedefault-cost <cost> Stub default metric for this stub area.

cost is the range from 0 to 16777215. This is the metricvalue applied at the indicated type of service.To configure this option to the default value, use thedefault operator with the command.The default value is 10.

import <value> Configures the area support for importingadvertisements. The options are:

• external—Stub and nssa are both false

• noexternal—Configure the area as stub area

• nssa—Configure the area as nssa

To configure this option to the default value, use thedefault operator with the command.The default value is external.



Variable Valueimport-summaries enable Configures the area support for importing summary

advertisements into a stub area. Use this entry only fora stub area. To configure this option to the defaultvalue, use the default operator with the command.The default value is true.

translator-role <value> Indicates an NSSA Border router ability to performtranslation of type-7 LSAs into type-5 LSAs.Valid values are 1 (always) or 2 (candidate). Defaultvalue is 1 (always).

type <nssa|stub> Configures the type of area. An NSSA preventsflooding of normal route advertisements into the areaby replacing them with a default route. A stub areauses only one exit point (router interface) from thearea.By default, the area is neither a stub area or anNSSA.

Configuring OSPF area rangesConfigure an area address range on the OSPF router to reduce the number of ABRadvertisements into other OSPF areas. An area address range is an implied contiguous rangeof area network addresses for which the ABR advertises a single summary route.

Configure the area by using one of the two LSA types: inter-area-prefix-link or nssa-extlink.


Prerequisites


Procedure steps

Configure an OSPF area range by using the following command:

Configuring OSPF area ranges


ipv6 area range <A.B.C.D> <Ipv6 address/prefix> <inter-area-prefix-link|nssa-extlink> advertise-mode <advertise|not-advertise>] advertise-metric <0–65535>

Variable definitionsUse the data in the following table to use the ipv6 area range command.

Variable ValueA.B.C.D Specifies the IP address of the area.

advertise-metric <0–65535> Specifies the advertise metric value and LSA type.The default value is 0.


Specifies the area range advertise mode asadvertise or no-advertise.The default value is advertise.

ipv6addrress/prefix Configures the IPv6 address range of an OSPF area.The string length is 0–255 characters.

Configuring OSPF area virtual interfacesIf a remote OSPF ABR uses no connection to the backbone area but needs to be part of thesame routing domain (AS) in which the switch resides, configure an OSPF virtual interface tothe ABR.


Important:OSPF behavior is modified according to OSPF standards so that OSPF routes cannot belearned through an area border router (ABR) unless the router connects to the backbone orthrough a virtual link.



Prerequisites


Procedure steps

Configure an OSPF area virtual interface by using the following command:

ipv6 area virtual-link <area IP address> <virtual link IPaddress> dead-interval <seconds> hello-interval <seconds>retransmit-interval <seconds> transit-delay <seconds>

Variable definitionsUse the data in the following table to use the ipv6 area virtual-link command.

Variable Valuedead-interval <seconds> Specifies the dead interval, in seconds, as a

range 1–4 095. To configure this option to thedefault value, use the default operator with thecommand.The default value is 60.

hello-interval <seconds> Specifies the Hello interval, in seconds, sentbetween switches for a virtual interface in anOSPF area. The range is 1–65535. To configurethis option to the default value, use the defaultoperator with the command.The default value is 10.

retransmit-interval <seconds> Specifies the retransmit interval, in seconds, sentbetween switches for a virtual interface in anOSPF area. The range is 1–1800. To configurethis option to the default value, use the defaultoperator with the command.The default value is 5.

transit-delay <seconds> Specifies the transit delay interval, in seconds,sent between switches for a virtual interface in anOSPF area. The range is 1–1800. To configurethis option to the default value, use the defaultoperator with the command.The default value is 1.

Configuring OSPF area virtual interfaces


Configuring an OSPF interfaceConfigure an OSPF interface for designated router (DR) and backup designated router (BDR)election to reduce the amount of routing traffic.

Prerequisites

• Before you can configure OSPF parameters on an interface, you must first configure IPon the interface.

• You must log on to the Interface Configuration mode in the ACLI.

Procedure steps

1. Associate the interface with an OSPF area with the following command:

ipv6 ospf area <A.B.C.D>2. Enable OSPF on the interface by using the following command:

ipv6 ospf enable3. Configure the OSPF area by using the following command:

ipv6 ospf area <A.B.C.D> cost <metric> [dead-interval<seconds>] [hello-interval <seconds>][network <value>][priority <value>] [retransmit-interval <seconds>][transmit-delay <seconds>]

4. Enable an OSPF area on an interface by using the following command:

ipv6 ospf area <A.B.C.D>5. Configure the interface by using the following command:

ipv6 ospf cost <metric> [priority <value>]

Variable definitionsUse the data in the following table to use the ipv6 ospf command.



Variable Valuearea <A.B.C.D> Specifies the area IP address (0.0.0.0 to

255.255.255.255) {a.b.c.d}.

cost <metric> Configures the OSPF metric for the interface. Theswitch advertises the metric in router linkadvertisements.metric is the range 0–65535.To configure this option to the default value, use thedefault operator with the command.The default value is 1.

dead-interval <seconds> Configures the OSPF dead interval for the interface.seconds is the number of seconds the switch OSPFneighbors wait before determining that this OSPFrouter is down. The range is from 1-4095. This valuemust be at least four times the Hello interval value. Thedefault is 40.To configure this option to the default value, use thedefault operator with the command.



To configure this option to the default value, use thedefault operator with the command.

network <value> Configures the type of interface:

• eth: broadcast

• nbma: NBMA

• p2mp: point-to-multipoint

• p2p: point-to-point

poll-interval <seconds> Configures the polling interval for the OSPF interfacein seconds.seconds is 0–2147483647.To configure this option to the default value, use thedefault operator with the command.The default value is 120.

priority <value> Configures the OSPF priority for the interface duringthe election process for the designated router. Theinterface with the highest priority number is thedesignated router. The interface with the second-

Configuring an OSPF interface


Variable Valuehighest priority becomes the backup designatedrouter. If the priority is 0, the interface cannot becomeeither the designated router or a backup. The priorityis used only during election of the designated routerand backup designated router.value is in the range 0–255. The default is 1.To set this option to the default value, use the defaultoperator with the command.

retransmit-interval <seconds> Configures the retransmit interval for the OSPFinterface; the number of seconds between link-stateadvertisement retransmissions.seconds is an integer from 1–1 800.To configure this option to the default value, use thedefault operator with the command.The default value is 5.

transit-delay <seconds> Configures the transit delay time for the OSPFinterface, the estimated time in seconds it takes totransmit a link-state update packet over theinterface.seconds is an integer from 1–1 800.To configure this option to the default value, use thedefault operator with the command.The default value is 1.

Configuring OSPF direct redistributionEnable or disable direct redistribution to redistribute IPv6 direct routes into an OSPFv3 routingdomain.

Prerequisites


Procedure steps

Configure OSPF direct redistribution by using the following command:



ipv6 redistribute direct enable

Configuring OSPF static redistributionEnable or disable static redistribution to redistribute IPv6 static routes into an OSPFv3 routingdomain.

Prerequisites


Procedure steps

Configure OSPF static redistribution by using the following command:

ipv6 redistribute static enable

Configuring port-based OSPF neighbor parametersConfigure port-based OSPFv3 neighbor parameters for specified ports to customize yourOSPF IPv6 configuration.


Prerequisites


Procedure steps

Configure port-based OSPF neighbor parameters by using the following command:


Configuring OSPF static redistribution


Important:You must use an IPv6 link-local address as an NBMA neighbor.

Variable definitionsUse the data in the following table to use the ipv6 ospf nbma-nbr command.

Variable ValueIpv6address/prefix-len Specifies the IPv6 address of the neighbor as a string

of 0–43 characters.

priority <priority> Configures the OSPF priority for the interface duringthe election process for the designated router. Theinterface with the highest priority number is thedesignated router. The interface with the second-highest priority becomes the backup designatedrouter. If the priority is 0, the interface cannot becomeeither the designated router or a backup. The priorityis used only during election of the designated routerand backup designated router. The range is 0 to 255.The default is 1. To configure this option to the defaultvalue, use the default operator with the command.

Configuring OSPF parameters for a VLANConfigure OSPFv3 parameters for a specified VLAN to customize your OSPF IPv6configuration.

Prerequisites

You must log on to the VLAN Interface Configuration mode in the ACLI.

Procedure steps

1. Associate the OSPF area with an interface by using the following command:

ipv6 ospf area <A.B.C.D>2. Enable OSPF on the interface with the following command:



ipv6 ospf enable3. Configure the area by using the following command:

ipv6 ospf area <A.B.C.D> cost <metric> [dead-interval<seconds>] [hello-interval <seconds>][network <value>][priority <value>] [retransmit-interval <seconds>][transmit-delay <seconds>]

4. Configure the interface by using the following command:

ipv6 ospf cost <metric> [priority <value>]

Variable definitionsUse the data in the following table to use the ipv6 ospf command.

Variable Valuearea <A.B.C.D> Specifies the area IP address (0.0.0.0 to

255.255.255.255) {a.b.c.d}.

cost <metric> Configures the OSPF metric for the interface. Theswitch advertises the metric in router linkadvertisements.metric is the range 0–65535.To configure this option to the default value, use thedefault operator with the command.The default value is 1.

dead-interval <seconds> Configures the OSPF dead interval for the interface.seconds is the number of seconds the switch OSPFneighbors wait before determining that this OSPFrouter is down. The range is from 1-4095. This valuemust be at least four times the Hello interval value. Thedefault is 40.To configure this option to the default value, use thedefault operator with the command.

hello-interval <seconds> Configures the OSPF hello interval for the interface.seconds is the number of seconds between hellopackets sent on this interface. The range is 1–65 535.The default is 10.

Important:When you change the hello interval values, youmust save the configuration file and restart theswitch to restore the values and check forconsistency.


Configuring OSPF parameters for a VLAN


Variable Valuenetwork <value> Configures the type of interface:

• eth—broadcast

• nbma—NBMA

• p2mp—point-to-multipoint

• p2p—point-to-point

poll-interval <seconds> Configures the polling interval for the OSPF interfacein seconds.seconds is from 0–2147483647.To configure this option to the default value, use thedefault operator with the command.The default value is 120.

priority <value> Configures the OSPF priority for the interface duringthe election process for the designated router. Theinterface with the highest priority number is thedesignated router. The interface with the second-highest priority becomes the backup designatedrouter. If the priority is 0, the interface cannot becomeeither the designated router or a backup. The priorityis used only during election of the designated routerand backup designated router.value is in the range 0–255. The default is 1.To configure this option to the default value, use thedefault operator with the command.

retransmit-interval <seconds> Configures the retransmit interval for the OSPFinterface; the number of seconds between link-stateadvertisement retransmissions.seconds is an integer from 1–1800.To configure this option to the default value, use thedefault operator with the command.The default value is 5.

transit-delay <seconds> Configures the transit delay time for the OSPFinterface, the estimated time in seconds it takes totransmit a link-state update packet over theinterface.seconds is an integer from 1–1800.To configure this option to the default value, use thedefault operator with the command.The default value is 1.



Configuring OSPF neighbor parameters for a VLANConfigure port-based OSPFv3 neighbor parameters for a VLAN to customize your OSPF IPv6configuration.


Prerequisites


Procedure steps

Configure OSPF neighbor parameters for a VLAN by using the following command:


Variable definitionsUse the data in the following table to use the ipv6 ospf nbma-nbr command.

Variable ValueIpv6address/prefix-len Specifies the IPv6 address of the neighbor as a string

of 0–43.

priority <priority> Configures the OSPF priority for the interface duringthe election process for the designated router. Theinterface with the highest priority number is thedesignated router. The interface with the second-highest priority becomes the backup designatedrouter. If the priority is 0, the interface cannot becomeeither the designated router or a backup. The priorityis used only during election of the designated routerand backup designated router. The range is 0–255.The default is 1. To configure this option to the defaultvalue, use the default operator with the command.

Configuring OSPF neighbor parameters for a VLAN




Chapter 11: IPv6 DHCP Relay configurationusing Enterprise DeviceManager

Use the Forward Path tab to configure the DHCP Relay forward path, and use the Interface tab toconfigure the related parameters (for example, max hops and remote ID).

DHCP configuration navigation• Configuring the DHCP relay forwarding path on page 199

• Configuring DHCP relay interface parameters on page 200

• Viewing DHCP Relay statistics on page 202

Configuring the DHCP relay forwarding pathConfigure forwarding policies to indicate the relay agent and the DHCP server to which packetsare forwarded.

Procedure steps

1. In the navigation tree, open the Configuration > IPv6 folders.

2. Click DHCP Relay.

3. Click the Forward Path tab.

4. Click Insert.

5. In the AgentAddr box, type the agent address.

6. In the ServerAddr box, type the server address.


7. Click Enabled to enable DHCP relay. You can enable or disable each agent serverforwarding path. The default is enabled.

8. Click Insert.

Variable definitionsUse the data in the following table to configure the DHCP Relay forward path.

Variable ValueAgentAddr The IP address of the input interface (agent) on which the DHCP request

packets are received for forwarding. This address is the IP address ofeither a brouter port or a VLAN for which forwarding is enabled.

ServerAddr This parameter is the IP address of the DHCP server. The request isunicast to the server address.

Enable Enables DHCP relay on the routing switch.

Configuring DHCP relay interface parametersConfigure the DHCP relay behavior on the interface.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.


3. In the Interface tab, click Insert.

4. Enter the appropriate values.

5. Click Apply.

Variable definitionsUse the data in the following table to configure the DCHP Relay interface parameters.

IPv6 DHCP Relay configuration using Enterprise Device Manager


Variable ValueIfIndex A read-only value indicating the unique value to identify an IPv6

interface. For the brouter port, it is the ifindex of the port and, in thecase of the VLAN, it is the ifindex of the VLAN.

MaxHop Specifies the maximum number of hops a DHCP packet can takefrom the DHCP client to the DHCP server.

RemoteIdEnabled Enables or disables remote ID.

DhcpEnabled Specifies whether DHCP is enabled or disabled on the interface.

Configuring DHCP relay interface parameters on a VLANConfigure the DHCP relay behavior on the interface.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > VLAN.

2. Click VLANs.

3. Click the Basic tab.

4. Select a VLAN to configure.

5. Click IPv6.

6. Click the DHCP tab.

7. Edit the fields as required.

8. Click Apply.

Variable definitionsUse the data in the following table to configure the DCHP Relay interface parameters.

Variable ValueIfIndex A read-only value indicating the unique value to identify an IPv6

interface. For the brouter port, it is the ifindex of the port and, in thecase of the VLAN, it is the ifindex of the VLAN.

MaxHop Specifies the maximum number of hops a DHCP packet can takefrom the DHCP client to the DHCP server.

Configuring DHCP relay interface parameters on a VLAN


Variable ValueRemoteIdEnabled Enables or disables remote ID.

DhcpEnabled Specifies whether DHCP is enabled or disabled on the interface.

Viewing DHCP Relay statisticsView DHCP Relay statistics to monitor network performance.

Procedure steps



3. In the Interface tab, select an interface and click Statistics.

Variable definitionsUse the data in the following table to use the DHCP Relay Statistics tab.

Variable ValueNumRequests The count of request messages.

NumReplies The count of reply messages.

IPv6 DHCP Relay configuration using Enterprise Device Manager


Chapter 12: IPv6 DHCP Relay configurationusing the CLI

Dynamic Host Configuration Protocol (DHCP) provides host configuration information to the workstationsdynamically. Use the DHCP relay commands to set DHCP relay behavior on a port or on a VLAN.

This section describes the CLI commands for IPv6 DHCP Relay configuration functions in the AvayaEthernet Routing Switch 8800/8600.

To configure DHCP Relay, you can use the config ipv6 dhcp-relay command, which allows you to specifythe IP address of the port or VLAN to use as a relay agent, or use the config {vlan <vid> |ethernet <ports>} ipv6 dhcp-relay command to explicitly specify the port or VLAN to use asthe relay agent.

IPv6 DHCP relay configuration navigation• Job aid: Roadmap of IPv6 DHCP Relay CLI commands on page 203

• Configuring an IPv6 DHCP relay interface on page 204

• Configuring IPv6 DHCP relay on a port or VLAN on page 206

• Showing IPv6 DHCP relay information on page 207

• Showing IPv6 DHCP relay information for a port or VLAN on page 208

Job aid: Roadmap of IPv6 DHCP Relay CLI commandsThe following table lists the IPv6 DHCP Relay commands and their parameters that you useto complete the procedures in this section.

Table 14: IPv6 DHCP Relay configuration commands

Command Parameterconfig ipv6 dhcp-relay info

create-fwd-path agent <value> server<value> [state <value>]


Command Parameterdelete-fwd-path agent <value> server<value>

disable-fwd-path agent <value> server<value>

enable-fwd-path agent <value> server<value>

config {ethernet <ports> | vlan <vlan-id>}ipv6 dhcp-relay

info

create-fwd-path server <value> [state<value>]

delete-fwd-path server <value>

disable

disable-fwd-path server <value>

enable

enable-fwd-path server <value>

max-hop <max-hop>

remote-id {enable|disable}

show ipv6 dhcp-relay fwd-path

show ipv6 dhcp-relay counters

show vlan info dhcp-relay

show ports info dhcp-relay [vlan <vid>][port<value>]

Configuring an IPv6 DHCP relay interfaceConfigure an IPv6 DHCP relay interface.

Procedure steps

1. Configure DHCP parameters globally with the following command: config ipv6dhcp-relay

2. Confirm your configuration with the following command: config ipv6 dhcp-relay info

IPv6 DHCP Relay configuration using the CLI


Variable definitionsUse the data in the following table to use the following commands:

config ipv6 dhcp-relay

Variable Valuecreate-fwd-path agent <value> server<value> [state <value>]

Configures the forwarding path from the client tothe server.

• agent <value> is the IPv6 address configuredon an interface (a locally configured IPv6address) that must be configured to forward orrelay DHCP messages.

• server <value> is the IPv6 address of the DHCPserver in the network.

• state <value> enables or disables theforwarding path.

delete-fwd-path agent <value> server<value>

Deletes the forwarding path from the client to theserver.

• agent <value> is the IPv6 address configuredon an interface (a locally configured IPv6address).


disable-fwd-path agent <value> server<value>

Disables DHCP relaying on the path from the IPaddress to the server. This is the default.



enable-fwd-path agent <value> server<value>

Enables DHCP relaying on the path from the IPv6address to the server.



info Displays the current DHCP global configurationon the switch.

Configuring an IPv6 DHCP relay interface


Configuring IPv6 DHCP relay on a port or VLANYou can configure DHCP parameters on specific ports or VLANs.

Procedure steps

1. Configure DHCP parameters on a specified port or VLAN by using the followingcommand: config {vlan <vid> | ethernet <ports>} ipv6 dhcp-relay

2. Confirm your configuration by using the following command: config {vlan|ethernet} ipv6 dhcp-relay info

Variable definitionsUse the data in the following table to use the config {vlan <vid> | ethernet<ports>} ipv6 dhcp-relay command.

Variable Valuecreate-fwd-path server <value>[state <value>]

Configures the forwarding path from the client (port orVLAN) to the server.


• state <value> enables or disables the forwardingpath.

delete-fwd-path server <value> Deletes the forwarding path to the specified server.

value is the IPv6 address in the format X:X::X:X.

disable Disables DHCP relay on the port. This is the defaultstate.

disable-fwd-path server <value> Disables the forwarding path to the specified server.

value is the IPv6 address in the format X:X::X:X.

enable Enables DHCP relay on the port.

enable-fwd-path server <value> Enables the forwarding path server to the specifiedserver.

value is the IPv6 address in the form X:X::X:X.

info Displays the current DHCP configuration on the port.



Variable Valuemax-hop <max-hop> Sets the maximum number of hops before a DHCP

packet is discarded (1 to 32). The default is 32.

remote-id {enable | disable} Enables or disables remote ID.

Showing IPv6 DHCP relay informationDisplay DHCP relay information to show forward paths and counters.

Procedure steps

1. Display information about the DHCP relay forward path with the following command:

show ipv6 dhcp-relay fwd-path2. Display information about DHCP relay counters by using the following command:


Job aidThe following table shows the field descriptions for the show ipv6 dhcp-relay counterscommand.

Table 15: show ip dhcp-relay command

Parameter DescriptionINTERFACE Indicates the interface IPv6 address.

REQUEST Indicates the total number of DHCP requests received on thisinterface.

REPLIES Indicates the total number of DHCP replies received on thisinterface.

The following table shows the field descriptions for the show ipv6 dhcp-relay fwd-pathcommand.

Table 16: show ip dhcp-relay command

Parameter DescriptionINTERFACE Indicates the interface IPv6 address.

Showing IPv6 DHCP relay information


Parameter DescriptionSERVER Indicates the DHCP server IPv6 address.

ENABLE Indicates if DHCP is enabled on the interface.

Showing IPv6 DHCP relay information for a port or VLANYou can display the IPv6 DHCP parameters for ports or VLANs.

Procedure steps

1. Display the DHCP parameters for VLANs by using the following command: showipv6 dhcp-relay interface ports <ports>

2. Display the DHCP parameters for ports by using the following command:

show ipv6 dhcp-relay interface vlan <vid>

Variable definitionsUse the data in the following table to use the show ipv6 dhcp-relay interfacecommand.

Variable Valueport <ports> The port list {slot/port[-slot/port][,...]}.

vid The VLAN ID, which is a value from 1 to 4094.

Job aidThe following table shows the field descriptions for the show ipv6 dhcp-relayinterface vlan <vid> command.

Table 17: show ipv6 dhcp-relay interface vlan command

Parameter DescriptionVLAN ID Indicates the VLAN ID number.

IF INDEX Indicates the interface index number. Numbers 1 to 256 areports; numbers above 257 are VLANs.



Parameter DescriptionMAX HOP Indicates the maximum number of hops a DHCP packet can

take from the source device (DHCP client) to the destinationdevice (DHCP server).

DHCP-RELAY Indicates whether DHCP Relay is enabled or disabled.

REMOTE ID Indicates whether Remote ID is enabled or disabled.

The following table shows the field descriptions for the show ipv6 dhcp-relayinterface ports <ports> command.

Table 18: show ipv6 dhcp-relay interface ports command

Parameter DescriptionPORT_NUM Indicates the port number.

IF INDEX Indicates the interface index number. Numbers 1 to 256 areports; numbers above 257 are VLANs.

MAX HOP Indicates the maximum number of hops a DHCP packet cantake from the source device (DHCP client) to the destinationdevice (DHCP server).

DHCP-RELAY Indicates whether DHCP Relay is enabled or disabled.

REMOTE ID Indicates whether Remote ID is enabled or disabled.

Showing IPv6 DHCP relay information for a port or VLAN




Chapter 13: IPv6 DHCP Relay configurationusing the ACLI

Dynamic Host Configuration Protocol (DHCP) provides host configuration information to workstationsdynamically. Use the DHCP relay commands to set DHCP relay behavior on a port or on a VLAN.

This section describes the ACLI commands for IPv6 DHCP Relay configuration functions on the AvayaEthernet Routing Switch 8800/8600.

To configure DHCP Relay, you can use the ipv6 dhcp-relay command in Global configuration mode, whichallows you to specify the IP address of the port or VLAN to use as a relay agent, or use the ipv6 dhcp-relay in Interface Configuration mode to first select the port or VLAN to use as the relay agent, and thenspecify the DHCP server and related parameters.

IPv6 DHCP configuration navigation• Job aid: Roadmap of DHCP Relay ACLI commands on page 211

• Configuring IPv6 DHCP relay in Global configuration mode on page 212

• Configuring IPv6 DHCP relay parameters on a port or VLAN on page 213

• Showing IPv6 DHCP relay information on page 214

Job aid: Roadmap of DHCP Relay ACLI commandsThe following table lists the commands and parameters that you use to complete the IPv6DHCP Relay procedures in this section.

Table 19: Roadmap of IPv6 DHCP Relay commands


ipv6 dhcp-relay fwd-path <agent-addr> <server-addr>[enable]

Interface Configuration Mode

ipv6 dhcp-relay fwd-path <server-addr> [enable]


Command Parametermax-hop <1-32>

remote-id {enable | disable}

PrivExec mode


show ipv6 dhcp-relay fwd-path

show ip dhcp-relay interface <interface-type> <interface-id>

Configuring IPv6 DHCP relay in Global configuration modeIn Global configuration mode, you can configure the DHCP relay forwarding path, but youcannot configure related parameters (for example, max hops or remote ID).

Prerequisites

Access Global configuration mode.

Procedure steps

1. Create the forwarding path from the client to the server by using the followingcommand: ipv6 dhcp-relay fwd-path <agent-addr> <server-addr>

2. Enable the forwarding path by using the following command: ipv6 dhcp-relayfwd-path <agent-addr> <server-addr> enable

Variable definitionsUse the data in the following table to use the preceding commands.

Variable Valuefwd-path <agent-addr> <server-addr> [enable]

Configures the forwarding path from the client to theserver.

IPv6 DHCP Relay configuration using the ACLI


Variable Value

• <agent-addr> is the IPv6 address configured on aninterface (a locally configured IPv6 address) toforward or relay DHCP.

• <server-addr> is the IPv6 address of the DHCP serverin the network.

Use the enable operator to enable the path.Use the no or default operators to delete the forwardingpath: no ipv6 dhcp-relay fwd-path <agent-addr><server-addr> default ipv6 dhcp-relay fwd-path <agent-addr> <server-addr>

{default|no} ipv6 dhcp-relay fwd-path <agent-addr> <server-addr>enable

To disable the specified path, use the no or defaultoperators with the enable option.

Configuring IPv6 DHCP relay parameters on a port orVLAN

In Interface Configuration mode, you can configure the DHCP relay forwarding path andparameters for a specified port or VLAN.

Prerequisites

Access Interface configuration mode.

Procedure steps

Configure DHCP relay parameters on the specified port or VLAN by using the followingcommand: ipv6 dhcp-relay

Variable definitionsUse the data in the following table to use the ipv6 dhcp-relay command.

Configuring IPv6 DHCP relay parameters on a port or VLAN


Variable Valuefwd-path <server-addr> [enable] Creates a DHCP relay forwarding path.

<server-addr> is the server IPv6 address.

Use the enable option to enable a forward path.Use the no or default operators to delete a forwardpath no ip dhcp-relay fwd-path <server-addr> defaultip dhcp-relay fwd-path <server-addr>

max-hop <1-32> Sets the maximum number of hops before a DHCPpacket is discarded (1 to 32). The default is 32.To set this option to the default value, use the defaultoperator with this command.

remote-id {enable|disable} Enables or disables remote ID.

{default|no} ipv6 dhcp-relay fwd-path <server-addr> enable

To disable the specified path, use the no or defaultoperators with the enable option.

Showing IPv6 DHCP relay informationDisplay relay information about DHCP relay routes and counters.

Prerequisites

Access privExec Configuration Mode.

Procedure steps

1. Display information about DHCP relay forward paths by using the followingcommand: show ipv6 dhcp-relay fwd-path

2. Display information about DHCP relay counters by using the following command:show ipv6 dhcp-relay counters

3. Display information about DHCP relay interfaces by using the following command:show ipv6 dhcp-relay interface <interface-type> <interface-id>

IPv6 DHCP Relay configuration using the ACLI


Chapter 14: IPv6 VRRP configuration usingEnterprise Device Manager

To provide fast failover of a default router for IPv6 LAN hosts, the Avaya Ethernet Routing Switch8800/8600 supports the Virtual Router Redundancy Protocol (VRRP v3) for IPv6. VRRP supports a virtualIPv6 address shared between two or more routers connecting the common subnet to the enterprisenetwork. VRRPv3 for IPv6 provides a faster switchover to an alternate default router than is possible usingthe ND protocol.

To configure a VRRP interface, you can either configure the interface using the Configuration, IPv6, VRRPpath from the navigation tree, or by first selecting a port or VLAN and selecting the IPv6, VRRP path fromthere.

Important:An Ethernet Routing Switch 8800/8600 acting as a VRRP Master does not reply to SNMP Get requeststo the VRRP virtual interface address. It will, however, respond to SNMP Get requests to its physicalIP address.

Prerequisites to VRRP configuration

• Assign an IPv6 address to the interface.

• Enable routing globally.

• RSMLT is not configured on the VLAN.

Navigation• Configuring a VRRP interface on page 216

• Configuring additional addresses on the VRRP interface on page 218

• Configuring VRRP notification control on page 219

• Configuring VRRP on a port on page 220

• Configuring VRRP on a VLAN on page 222


• Viewing VRRP statistics on page 224

• Viewing VRRP interface statistics on page 226

Configuring a VRRP interfaceUse this procedure to create a VRRP interface.

Procedure steps


2. Click VRRP.

3. Click the Interface tab.

4. Click Insert.

5. Complete the fields as required.

6. Click Apply.

Variable definitionsUse the data in the following table to configure a VRRP interface.

Variable ValueIfIndex The index value that uniquely identifies the interface to which

this entry is applicable.

InetAddrType The address type for the VRRP interface. In this case, IPv6.

VrId A number that uniquely identifies a virtual router on a VRRProuter. The virtual router acts as the default router for one ormore assigned addresses (1 to 255).

LinkLocal The assigned IPv6 addresses that a virtual router is responsiblefor backing up.

VirtualMacAddr The MAC address of the virtual router interface.

State The state of the virtual router interface:

IPv6 VRRP configuration using Enterprise Device Manager


Variable Value

• initialize—waiting for a startup event

• backup—monitoring availability and state of the master router

• master—functioning as the forwarding router for the virtualrouter IP addresses.

Control Displays whether VRRP is enabled or disabled for the port (orVLAN).

Priority The priority value used by this VRRP router. Set a value from 1to 255, where 255 is reserved for the router that owns the IPaddresses associated with the virtual router. The default is100.

AdvInterval The time interval (in seconds) between sending advertisementmessages. The range is 1 to 255 seconds with a default of 1second. Only the master router sends advertisements.

MasterIpAddr The IP address of the physical interface of the master virtualrouter that forwards packets sent to the virtual IP addressesassociated with the virtual router.

UpTime The time interval (in hundredths of a second) since the virtualrouter was initialized.

CriticalIpAddr An IP interface on the local router configured so that a changein its state causes a role switch in the virtual router (for example,from master to backup) in case the interface stopsresponding.

CriticalIpAddrEnabled Sets the IP interface on the local router to enable or disable thebackup.

BackUpMaster Lets you use the backup VRRP switch traffic forwarding. Thisreduces the traffic on the IST link. The default is disabled.

BackUpMasterState Indicates whether the backup VRRP switch traffic forwarding isenabled or disabled.

FasterAdvIntervalEnable Enables or disables the Fast Advertisement Interval. Whendisabled, the regular advertisement interval is used. The defaultis disable.

FasterAdvInterval Sets the Fast Advertisement Interval between sending VRRPadvertisement messages. The interval is between 200 and1000 milliseconds, and you must enter the same value on allparticipating routers. The default is 200. You must enter thevalues in multiples of 200 milliseconds.

AcceptMode Controls whether a master router accepts packets addressedto the address owner's IPv6 address as its own if it is not theIPv6 address owner. The default value is disable.

Configuring a VRRP interface


Variable ValueAction Lists options to override the holddown timer manually and force

preemption:

• none does not override the timer

• preemptHoldDownTimer preempts the timer

HoldDownTimer Configures the amount of time (in seconds) to wait beforepreempting the current VRRP master.

HoldDownTimeRemaining

Indicates the amount of time (in seconds) left before theHoldDownTimer expires.

GlobalIPAddr The global IPv6 address assigned to the virtual routerinterface.

Configuring additional addresses on the VRRP interfaceUse this procedure to specify additional addresses for the VRRP interface to back up.

Procedure steps


2. Click VRRP.


4. Select an existing VRRP interface.

5. Click AssociatedIPAddr.

Note that you can also access the AssociatedIPAddr button from the Port VRRPtab (Configuration > Edit > Port > IPv6 > VRRP) or from the VLAN VRRP tab(Configuration > VLANs > IPv6 > VRRP)

6. Click Insert.

7. Complete the fields for the associated address.

8. Click Apply.

Variable definitionsUse the data in the following table to configure additional VRRP addresses.







IpAddr The additional IPv6 address that the virtual router is responsiblefor backing up.

IpAddrPrefixLength The IPv6 prefix length.

Configuring VRRP notification controlUse this procedure to configure VRRP notification control.

Procedure steps


2. Click VRRP.

3. In the NotificationCtrl box, click to enable or disable notification control.

4. Click Apply.

Variable definitionsUse the data in the following table to configure VRRP notification control.

Variable ValueNotificationCntl Indicates whether the VRRP-enabled router generates SNMP

traps for events.

• enabled—SNMP traps are generated

• disabled—no SNMP traps are sent

Configuring VRRP notification control


Configuring VRRP on a portUse this procedure to configure VRRP on a port. You can configure VRRP on a port only if theport is assigned an IP address.

Procedure steps

1. From the Device Physical View, select a port.

2. In the navigation tree, open the following folders: Configuration > Edit > Port.

3. Click IPv6.

4. Click the VRRP tab.

5. Click Insert.

6. In the VrId box, enter a virtual router ID.

7. Select the AcceptMode box if you want the master router to accept packets forwhich it is not the IPv6 address owner as its own.

8. In the LinkLocal box, enter an IPv6 address.

9. Enter an advertisement interval.

10. Specify the priority.

11. Click Insert.

Variable definitionsUse the data in the following table to configure VRRP on a port.





LinkLocal The assigned IPv6 addresses that a virtual router is responsiblefor backing up.




Variable ValueState The state of the virtual router interface:




Control Displays whether VRRP is enabled or disabled for the port (orVLAN).

Priority The priority value used by this VRRP router. Set a value from 1to 255, where 255 is reserved for the router that owns the IPaddresses associated with the virtual router. The default is100.

AdvInterval The time interval (in seconds) between sending advertisementmessages. The range is 1 to 255 seconds with a default of 1second. Only the master router sends advertisements.

MasterIpAddr The IP address of the physical interface of the master virtualrouter that forwards packets sent to the virtual IP addressesassociated with the virtual router.


CriticalIpAddr An IP interface on the local router configured so that a changein its state causes a role switch in the virtual router (for example,from master to backup) in case the interface stopsresponding.

CriticalIpAddrEnabled Sets the IP interface on the local router to enable or disable thebackup.

BackUpMaster Lets you use the backup VRRP switch traffic forwarding. Thisreduces the traffic on the IST link. The default is disabled.


FasterAdvIntervalEnable Enables or disables the Fast Advertisement Interval. Whendisabled, the regular advertisement interval is used. The defaultis disable.

FasterAdvInterval Sets the Fast Advertisement Interval between sending VRRPadvertisement messages. The interval is between 200 and1000 milliseconds, and you must enter the same value on allparticipating routers. The default is 200. You must enter thevalues in multiples of 200 milliseconds.

AcceptMode Controls whether a master router accepts packets addressedto the address owner's IPv6 address as its own if it is not theIPv6 address owner. The default value is disable.

Configuring VRRP on a port


Variable ValueAction Lists options to override the holddown timer manually and force

preemption:

• none does not override the timer

• preemptHoldDownTimer preempts the timer

HoldDownTimer Configures the amount of time (in seconds) to wait beforepreempting the current VRRP master.


Indicates the amount of time (in seconds) left before theHoldDownTimer expires.

GlobalIPAddr The global IPv6 address assigned to the virtual routerinterface.

Configuring VRRP on a VLANUse this procedure to configure VRRP on a VLAN. You can configure VRRP on a VLAN onlyif the VLAN is assigned an IP address.

Procedure steps


2. Click VLANs.

3. In the Basic tab, select a VLAN.

4. Click IPv6.

5. Select the VRRP tab.

6. Click Insert.

7. Edit the fields as required.

8. Click Insert.

Variable definitionsUse the data in the following table to use configure VRRP on a VLAN.







LinkLocal The IP address of the virtual router interface.


State The state of the virtual router interface:




Control Displays whether VRRP is enabled or disabled for the port orVLAN.

Priority Priority value used by this VRRP router. The range is from 1 to255, where 255 is reserved for the router that owns the IPaddresses associated with the virtual router. The default is100.

AdvertisementInterval The time interval (in seconds) between sending advertisementmessages. The range is from 1 to 255 seconds with a defaultof 1 second. Only the master router sends advertisements.

MasterIPAddr The IP address of the master router.


CriticalIpAddr Indicates if a user-defined critical IP address must be enabled.There is no effect if a user-defined IP address does not exist.

CriticalIpAddrEnable Sets the IP interface on the local router to enable or disable thebackup.

BackUpMaster Lets you use the VRRP backup master switch.


FasterAdvIntervalEnabled

Lets you use the Fast Advertisement Interval. When disabled,the regular advertisement interval is used. The default isdisabled.

FasterAdvInterval Sets the Fast Advertisement Interval between sending VRRPadvertisement messages. The interval can be between 200 and1000 milliseconds, and it must be the same on all participating

Configuring VRRP on a VLAN


Variable Valuerouters. The default is 200. Enter the values in multiples of 200milliseconds.

Action Use the action list to manually override the delay timer and forcepreemption:

• preemptHoldDownTimer—preempt the timer

• none—allow the timer to keep working

HoldDownTimer The time interval (in seconds) a router is delayed for thefollowing conditions:

• The VRRP hold-down timer runs when the switch transitionsfrom initialization to backup to master. This occurs only on aswitch bootup.

• The VRRP hold-down timer does not run under the followingcondition: In a nonbootup condition, the backup switchbecomes master after the Master Downtime Interval (3 * hellointerval), if the master virtual router goes down.

• The VRRP hold-down timer also applies to the VRRPBackupMaster feature.


The seconds remaining before preemption.

GlobalIPAddr Specifies the global IPv6 address associated with the link-localVRRP IPv6 address that the virtual router backs up.

Viewing VRRP statisticsView VRRP statistics to monitor network performance.

Procedure steps


2. Click VRRP.

3. Click the Stats tab.

Note that you can also access a VRRP Statistics button from the Port VRRP tab(Configuration > Edit > Port > IPv6 > VRRP) or from the VLAN VRRPtab(Configuration > VLANs > IPv6 > VRRP)



Variable definitionsUse the data in the following table to use the VRRP Stats tab.

Variable ValueMasterTransitions Specifies the total number of times that this virtual router's state

has transitioned to MASTER. Discontinuities in the value of thiscounter can occur at re-initialization of the managementsystem, and at other times as indicated by the value of theDiscontinuityTime.

RcvdAdvertisements Specifies the total number of VRRP advertisements received bythis virtual router. Discontinuities in the value of this counter canoccur at re-initialization of the management system, and atother times as indicated by the value of the DiscontinuityTime.

AdvIntervalErrors Specifies the total number of VRRP advertisement packetsreceived for which the advertisement interval is different thanthe one configured for the local virtual router. Discontinuities inthe value of this counter can occur at re-initialization of themanagement system, and at other times as indicated by thevalue of DiscontinuityTime.

IpTtlErrors Specifies the total number of VRRP packets received by theVirtual router with IPv4 TTL (for VRRP over IPv4) or IPv6 HopLimit (for VRRP over IPv6) not equal to 255. Discontinuities inthe value of this counter can occur at re-initialization of themanagement system, and at other times as indicated by thevalue of the DiscontinuityTime

RcvdPriZeroPackets Specifies the total number of VRRP packets received by thevirtual router with a priority of '0'. Discontinuities in the value ofthis counter can occur at re-initialization of the managementsystem, and at other times as indicated by the value of theDiscontinuityTime.

SentPriZeroPackets Specifies the total number of VRRP packets sent by the virtualrouter with a priority of '0'. Discontinuities in the value of thiscounter can occur at re-initialization of the managementsystem, and at other times as indicated by the value of theDiscontinuityTime.

RcvdInvalidTypePkts Specifies the number of VRRP packets received by the virtualrouter with an invalid value in the 'type' field. Discontinuities inthe value of this counter can occur at re-initialization of themanagement system, and at other times as indicated by thevalue of the DiscontinuityTime.

AddressListErrors Specifies the total number of packets received for which theaddress list does not match the locally configured list for thevirtual router. Discontinuities in the value of this counter can

Viewing VRRP statistics


Variable Valueoccur at re-initialization of the management system, and atother times as indicated by the value of the DiscontinuityTime.

PacketLengthErrors Specifies the total number of packets received with a packetlength less than the length of the VRRP header. Discontinuitiesin the value of this counter can occur at re-initialization of themanagement system, and at other times as indicated by thevalue of the DiscontinuityTime.

RcvdInvalidAuthentications

Specifies the total number of packets received with an unknownauthentication type.

Viewing VRRP interface statisticsView VRRP interface statistics to monitor network performance.

Procedure steps


2. Click VRRP.


4. Select an interface.

5. Click the Statistics button.

Variable definitionsUse the data in the following table to use the VRRP Stats tab.

Variable ValueMasterTransitions The total number of times that this virtual router's state has

transitioned to MASTER. Discontinuities in the value of thiscounter can occur at re-initialization of the managementsystem, and at other times as indicated by the value ofDiscontinuityTime.

RcdAdvertisements The total number of VRRP advertisements received by thisvirtual router. Discontinuities in the value of this counter canoccur at re-initialization of the management system, and atother times as indicated by the value of DiscontinuityTime.



Variable ValueAdvIntervalErrors The total number of VRRP advertisement packets received for

which the advertisement interval is different than the oneconfigured for the local virtual router. Discontinuities in the valueof this counter can occur at re-initialization of the managementsystem, and at other times as indicated by the value ofDiscontinuityTime.

IpTtlErrors The total number of VRRP packets received by the Virtual routerwith IPv4 TTL (for VRRP over IPv4) or IPv6 Hop Limit (for VRRPover IPv6) not equal to 255. Discontinuities in the value of thiscounter can occur at re-initialization of the managementsystem, and at other times as indicated by the value ofDiscontinuityTime.

RcvdPriZeroPackets The total number of VRRP packets received by the virtual routerwith a priority of '0'. Discontinuities in the value of this countercan occur at re-initialization of the management system, and atother times as indicated by the value of DiscontinuityTime.

SentPriZeroPackets The total number of VRRP packets sent by the virtual router witha priority of '0'. Discontinuities in the value of this counter canoccur at re-initialization of the management system, and atother times as indicated by the value of DiscontinuityTime.

RcvdInvalidTypePkts The number of VRRP packets received by the virtual router withan invalid value in the 'type' field. Discontinuities in the value ofthis counter can occur at re-initialization of the managementsystem, and at other times as indicated by the value ofDiscontinuityTime.

AddressListErrors The total number of packets received for which the address listdoes not match the locally configured list for the virtual router.Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times asindicated by the value of DiscontinuityTime.

PacketLengthErrors The total number of packets received with a packet length lessthan the length of the VRRP header. Discontinuities in the valueof this counter can occur at re-initialization of the managementsystem, and at other times as indicated by the value ofDiscontinuityTime.

RcvdInvalidAuthentications

The total number of packets received with an unknownauthentication type.

DiscontinuityTime The value of sysUpTime on the most recent occasion at whichany one or more of this entry's counters suffered a discontinuity.If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then thisobject contains a zero value.

Viewing VRRP interface statistics


Variable ValueRefreshRate The minimum reasonable polling interval for this entry. This

object provides an indication of the minimum amount of timerequired to update the counters in this entry.



Chapter 15: IPv6 VRRP configuration usingthe CLI


Important:An Avaya Ethernet Routing Switch 8800/8600 acting as a VRRP Master does not reply to SNMP Getrequests to the VRRP virtual interface address. It will, however, respond to SNMP Get requests to itsphysical IP address.

When you use the Fast Advertisement Interval option to configure a master and backup switch, you mustenable the Fast Advertisement Interval option on both switches for VRRP to work correctly. If you configureone switch with the regular advertisement interval, and the other switch with the Fast AdvertisementInterval, it causes an unstable state and drops advertisements.

Prerequisites to VRRP configurationEnsure that RSMLT is not configured on the VLAN.

Navigation• Job aid: Roadmap of IPv6 VRRP CLI commands on page 230• Configuring VRRP on a port on page 231• Configuring VRRP on a VLAN on page 234• Showing VRRP information for a VLAN on page 239• Showing VRRP interface information on page 236• Clearing IPv6 VRRP statistics on page 241


Job aid: Roadmap of IPv6 VRRP CLI commandsThe following table lists the IPv6 VRRP commands and parameters that you use to performthe procedures in this section.

Table 20: Roadmap of IPv6 VRRP commands

Command Parameterconfig ethernet <ports> ipv6 vrrp <vrid> info

action <action_choice>

accept-mode {enable|disable}

address [link-local <link-local-addr>] [addr<global-addr>]

adver-int <seconds>

backup-master <enable|disable>

critical-ipv6 <ipaddr>

critical-ipv6-enable <enable|disable>

delete [addr <addr>] [all]

disable

enable

fast-adv-enable <enable|disable>

fast-adv-int <milliseconds>

holddown-timer <seconds>

priority <prio>

config ipv6 vrrp info

send-trap <enable|disable>

config vlan <vid> ipv6 vrrp <vrid> info

action <action_choice>

accept-mode {enable|disable}


adver-int <seconds>

backup-master <enable|disable>

IPv6 VRRP configuration using the CLI


Command Parametercritical-ipv6 <ipaddr>


delete [addr <addr>] [all]

disable

enable

fast-adv-enable <enable|disable>

fast-adv-int <milliseconds>


priority <prio>

show ipv6 vrrp global-settings

info [vrid <value>] [link-local <value>]

show-all

stats [vrid <value>] [link-local <value>]

clear ipv6 global-stats

ports <ports> vrid <value>

vlan <vid> vrid <value>

Configuring VRRP on a portUse the following procedure to configure VRRP on a port.

Procedures steps

1. To configure VRRP on a port, enter: config ethernet <ports> ipv6 vrrp<vrid>

2. To confirm your configuration, enter: config ethernet <ports> ipv6 vrrp<vrid> info



Variable definitionsUse the data in the following table to use the config ethernet <ports> ipv6 vrrp<vrid> command.

Variable Value<vrid> A unique integer value that represents the

virtual router ID in the range 1 to 255. Thevirtual router acts as the default router for oneor more assigned addresses.

action <action_choice> Indicates options to override the hold-downtimer manually and force preemption.

action_choice can be set to preempt topreempt the timer or set to none to allowthe timer to keep working.

accept-mode <enable|disable> Controls whether a master router acceptspackets addressed to the address owner'sIPv6 address as its own if it is not the IPv6address owner. The default value isdisable.


Sets the IPv6 address to associate with thevirtual router ID.

• <link-local-addr> is the link-local IPv6address.

• <global-addr> is the global IPv6 address.

adver-int <seconds> Sets the the time interval between sendingVRRP advertisement messages.

seconds is between 1 and 255 seconds.The value must be the same on allparticipating routers. The default is 1.

backup-master <enable|disable> Enables or disables the VRRP backupmaster.This option is supported only on triangularSplit MultiLink Trunking (SMLT) ports.

Important:Do not enable Backup Master if Critical IPis enabled.

critical-ipv6 <ipv6addr> Sets the critical IPv6 address for VRRP.

ipv6addr is the IPv6 address on the localrouter, which is configured so that a change



Variable Value

in its state causes a role switch in the virtualrouter (for example, from master to backupin case the interface goes down).

critical-ipv6-enable <enable|disable> Enables or disables the critical IPv6 addressoption.

Important:Do not enable Critical IPv6 if BackupMaster is enabled.

delete [addr <addr>] [all] Deletes the specified VRRP address fromthe port.

disable Disables VRRP on the port.

enable Enables VRRP on the port.

fast-adv-enable <enable|disable> Enables or disables the Fast AdvertisementInterval. The default is disabled.

• enable means use the Fast AdvertisementInterval.

• disable means use the regularadvertisement interval.

fast-adv-int <milliseconds> Sets the Fast Advertisement Interval, thetime interval between sending VRRPadvertisement messages.

milliseconds can be between 200 and 1000milliseconds, and must be the same on allparticipating routers. The default is 200.You must enter values in multiples of 200milliseconds.

holddown-timer <seconds> Modifies the behavior of the VRRP failovermechanism by allowing the router enoughtime to detect the Open Shortest Path First(OSPF) or Routing Information Protocol(RIP) routes.

seconds is the time interval (in seconds) arouter is delayed when changing to masterstate.

info Displays the current port VRRPconfiguration.

priority <prio> Sets the port VRRP priority.

prio is the value (between 1 and 254) usedby the VRRP router. The default is 100.Assign the value 255 to the router that



Variable Value

owns the IP address associated with thevirtual router.

Configuring VRRP on a VLANUse this procedure to configure VRRP on a VLAN.

Procedure steps

1. Configure VRRP on a VLAN by using the following command: config vlan<vid> ipv6 vrrp <vrid>

2. Confirm your configuration by using the following command: config vlan <vid>ipv6 vrrp <vrid> info

Variable definitionsUse the data in the following table to use the config vlan <vid> ipv6 vrrp <vrid>command.

Variable Value<vid> The VLAN ID in the range of 1 to 4094.

<vrid> The virtual router ID in the range of 1 to 255, anumber that uniquely identifies a virtual router on aVRRP router. The virtual router acts as the defaultrouter for one or more assigned addresses.

action <action_choice> Indicates options to override the hold-down timermanually and force preemption.

action_choice can be set to preempt to preempt thetimer or set to none to allow the timer to keepworking.

accept-mode <enable|disable> Controls whether a master router accepts packetsaddressed to the address owner's IPv6 address asits own if it is not the IPv6 address owner. The defaultvalue is disable.

address [link-local <link-local-addr>][addr <global-addr>]

Sets the IPv6 address to associate with the virtualrouter ID.



Variable Value

• <link-local-addr> is the link-local IPv6 address.

• <global-addr> is the global IPv6 address.

adver-int <seconds> Sets the time interval (in seconds) between sendingadvertisement messages.

seconds is in the range of 1 to 255. The default is1.

backup-master <enable|disable> Enables or disables the VRRP backup master for aVLAN.This option is only supported on SMLT ports.

Important:Do not enable Backup Master if Critical IP isenabled.


Enables or disables the critical IPv6 address option.

Important:Do not enable Critical IP if Backup Master isenabled.

critical-ip <ipv6addr> Sets the critical IPv6 address for VRRP.

ipv6addr is the IPv6 address on the local routerconfigured so that a change in its state causes arole switch in the virtual router (for example, frommaster to backup in case the interface goesdown).

delete [addr <addr>] [all] Deletes the specified VRRP address from theVLAN.

disable Disables the VRRP on the VLAN.

enable Enables VRRP on the VLAN.

fast-adv-enable <enable|disable> Enables or disables the Fast Advertisement Interval.The default is disabled.

• enable enables the Fast Advertisement Interval.

• disable enables the Regular AdvertisementInterval.

fast-adv-int <milliseconds> Sets the time interval between sending FastAdvertisement messages.

milliseconds is the interval between 200 and 1000milliseconds. This interval must be the same on allparticipating routers. The default is 200. You mustenter values in multiples of 200 milliseconds.

Configuring VRRP on a VLAN


Variable Valueholddown-timer <seconds> Sets the time interval (in seconds) that a router is

delayed when changing to master state.

info Displays the current VLAN VRRP settings.

priority <prio> Sets the port VRRP priority value used by this VRRProuter.

prio is between 1 and 254. The default is 100.Assign the value 255 to the router that owns the IPaddress associated with the virtual router.

Configuring global VRRP settingsConfigure global VRRP settings to enable or disable SNMP traps.

Procedure steps

1. Configure global VRRP settings by using the following command:

config ipv6 vrrp send-trap <enable|disable>2. Confirm the configuration by using the following comman d:

config ipv6 vrrp send-trap info

Showing VRRP interface informationIf you enter a virtual router ID or an IP address when showing VRRP interface information, theinformation displays only for that virtual router ID or for that interface.



Procedure steps

To display VRRP information about the interface, enter: show ipv6 vrrp global-settings info [vrid <value>] [link-local <value>] show-allstats [vrid <value>] [link-local <value>]

Variable definitionsUse the data in the following table to use the show ipv6 vrrp info command.

Variable Valueglobal-settings Displays global VRRP settings.

info Displays VRRP interface configurations.

vrid <value> A unique integer value that represents thevirtual router ID in the range 1 to 255. Thevirtual router acts as the default router for oneor more assigned addresses.

[link-local <value>] The link-local IPv6 VRRP address.

show-all Displays all VRRP output: global settings,configuration information, and statistics.

stats Displays VRRP statistics.

Job aidThe following table describes parameters for the show ipv6 vrrp info command.

Parameter DescriptionVRID Indicates the virtual router ID on a VRRP router.

P/V Indicates whether this device responds to pings directed to avirtual router IP address.

IP Indicates the assigned IP addresses that a virtual router backsup.

MAC Indicates the virtual MAC address of the virtual router in theformat 00-00-5E-00-02-<VRID>, where the first three octetsconsist of the IANA OUI; the next two octets indicate theaddress block of the VRRP protocol; and the remaining octetsconsist of the VRID.

Showing VRRP interface information


Parameter DescriptionSTATE Indicates the current state of the virtual router.


• backup—monitoring the state and availability of the masterrouter

• master—forwarding IP addresses associated with this virtualrouter.

CONTROL Indicates the virtual router function. Set the value to enabledto transition the state of the router from initialize to backup. Setthe value to disabled to transition the router from master orbackup to initialize.

PRIO Indicates the priority for the virtual router (for example, masterelection) with respect to other virtual routers that are backingup one or more associated IP addresses. Higher valuesindicate higher priority.A priority of 0, which you cannot set, indicates that this routerstopped participating in VRRP and a backup virtual routertransitions to become the new master.A priority of 255 is used for the router that owns the associatedIP addresses.

ADV Indicates the advertisement interval, in milliseconds, betweensending advertisement messages.

MASTER Indicates the master router real (primary) IP address. This isthe IP address listed as the source in the VRRP advertisementlast received by this virtual router.

UP TIME Indicates the time interval (in hundredths of a second) sincethis virtual router was initialized.

CRITICAL IP Indicates the IP address of the interface that causes ashutdown event.

CRITICAL IP (ENABLED) Indicates if the critical IP address is enabled.

BACKUP MASTER Indicates the backup master IP address.

BACKUP MASTER STATE Indicates the backup master state.

FAST ADV Indicates the Fast Advertisement Interval, in milliseconds,between sending advertisement messages. When the FastAdvertisement Interval is enabled, the Fast AdvertisementInterval is used instead of the regular advertisement interval.

FAST ADV (ENABLED) Indicates the state of fast advertisement.

ACCEPT MODE Controls whether a master router accepts packets addressedto the address owner's IPv6 address as its own if it is not theIPv6 address owner. The default value is disable.



Parameter DescriptionACTION Specifies whether to override the holddown timer manually

and force preemption. Options are none (does not override thetimer) and preempt (preempts the timer).

HLD DWN Indicates the amount of time (in seconds) to wait beforepreempting the current VRRP master.

REM Remaining hold-down timer value.

GLOBAL ADDRESS Specifies the global IPv6 address associated with the link-localVRRP IPv6 address that the virtual router backs up.

Showing VRRP information for a VLANShow VLAN information to display the extended VRRP configuration for all VLANs or aspecified VLAN on the switch.

Procedure steps

Show the extended VRRP configuration for all VLANs on the switch or for a specifiedVLAN by using the following command: show vlan info vrrp ipv6<extended|main> [<vid>]

Variable definitionsUse the data in the following table to use the show vlan info vrrp ipv6 command.

Variable Value<main|extended> Indicates values for extended or main VRRP

configurations.

<vid> Indicates the VLAN ID in the range of 1 to 4094.

Job aidThe following table shows the field descriptions for the show vlan info vrrp ipv6maincommand.

Showing VRRP information for a VLAN


Parameter DescriptionVLAN ID Indicates the VLAN ID.

VRRP ID Indicates the virtual router ID

IPv6 ADDRESS The IPv6 address associated with the virtual router.

VIRTUAL MACADDRESS

The MAC address associated with the virtual router.

The following table shows the field descriptions for the show vlan info vrrp ipv6extendedcommand.



STATE Indicates the current state of the virtual router.


• backup—monitoring the state or availability of the masterrouter

• master—forwarding IP addresses associated with this virtualrouter

CONTROL Indicates the virtual router function. Set the value to enabled totransition the state of the router from initialize to backup. Setthe value to disabled to transition the router from master orbackup to initialize.

PRIORITY Indicates the priority for the virtual router (for example, masterelection) with respect to other virtual routers that are backingup one or more associated IP addresses. Higher valuesindicates higher priority.A priority of 0, which you cannot set, indicates that this routerceased to participate in VRRP and a backup virtual routertransitions to become a new master.Use a priority of 255 for the router that owns the associated IPaddresses.

MASTER IPADDR Indicates the master router real (primary) IP address. This isthe IP address listed as the source in the VRRP advertisementlast received by this virtual router.

ADVERTISE INTERVAL Indicates the time interval, in seconds, between sendingadvertisement messages. Only the master router sends VRRPadvertisements.

CRITICAL IPADDR Indicates the IP address of the interface that causes a shutdownevent.



Parameter DescriptionHOLDDWN Indicates the amount of time (in seconds) to wait before

preempting the current VRRP master.

ACTION TIME Specifies whether to override the holddown timer manually andforce preemption. Options are none (does not override thetimer) and preempt (preempts the timer).

CRITICAL IP ENABLE Indicates that a user-defined critical IP address is enabled. Noindicates the use of the default IP address (::or0:0:0:0:0:0:0:0).

BACKUP MASTER Indicates the state of designating a backup master router.

BACKUP MASTERSTATE

Indicates the state of the backup master router.

FAST ADV INTERVAL Indicates the time interval, in milliseconds, between sendingFast Advertisement messages. When the Fast AdvertisementInterval is enabled, the Fast Advertisement Interval is usedinstead of the regular advertisement interval.

FAST ADV ENABLE Indicates the Fast Advertisement Interval status.

Clearing IPv6 VRRP statisticsUse the following procedure to clear IPv6 VRRP statistics.

Procedure steps

1. To clear global IPv6 VRRP statistics, enter:

clear ipv6 vrrp2. To clear IPv6 VRRP statistics on a particular port, enter:

clear ipv6 vrrp ports <ports> vrid <value>3. To clear IPv6 VRRP statistics on a particular VLAN, enter:

clear ipv6 vrrp VLAN <vid> vrid <value>

Clearing IPv6 VRRP statistics


Variable definitionsUse the data in the following table to use the clear ipv6 vrrp command.

Variable Value<ports> Specifies the port value.

<vid> Indicates the VLAN ID in the range of 1 to 4094.

vrid <value> A unique integer value that represents the virtualrouter ID in the range 1 to 255. The virtual router actsas the default router for one or more assignedaddresses.



Chapter 16: IPv6 VRRP configuration usingthe ACLI


Important:An Avaya Ethernet Routing Switch 8800/8600 acting as a VRRP Master does not reply to SNMP Getrequests to the VRRP virtual interface address. It will, however, respond to SNMP Get requests to itsphysical IP address.

When you use the Fast Advertisement Interval option to configure a master and backup switch, you mustenable the Fast Advertisement Interval option on both switches for VRRP to work correctly. If you configureone switch with the regular advertisement interval, and the other switch with the Fast AdvertisementInterval, it causes an unstable state and drops advertisements.

VRRP configuration prerequisitesEnsure that RSMLT is not configured on the VLAN.

Navigation• Job aid: Roadmap of IPv6 VRRP ACLI commands on page 244• Configuring VRRP on a port or a VLAN on page 245• Showing VRRP interface information on page 250• Showing VRRP interface information on page 250• Clearing IPv6 VRRP statistics on page 241


Job aid: Roadmap of IPv6 VRRP ACLI commandsThe following table lists the commands and their parameters that you use to complete theprocedures in this section.

Table 21: Roadmap of IPv6 VRRP commands

Command ParameterFastEthernet/Gigabit Ethernet/VLAN Interface Configuration Mode

ipv6 vrrp <1-255> accept-mode enable

action {none|preempt }

adver-int <1-255>

backup-master enable

critical-ipv6-addr <X:X:X:X:X:X:X:X>

critical-ipv6 enable

enable

fast-adv enable

fast-adv-int <200-1000>

holddown-timer <0-21600>

priority <1-255>

ipv6 vrrp address <1-255> global <X:X::X:X>/len

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

PrivExec Mode

show ipv6 vrrp

show ipv6 vrrp address link-local <fe80::X:X:X:X>

vrid <1-255>

show ipv6 vrrp interface <port-type> [<portList>] [<1-4094>][statistics]

vlan [<1-4094>] [<portList>]

verbose

vrid <1-255>

show ipv6 vrrp statistics link-local <fe80::X:X:X:X>

vrid <1-255>

IPv6 VRRP configuration using the ACLI


Command Parameterclear ipv6 vrrp {fastethernet <slot|port>|gigabitethernet <slot|port>| vlan <vid>} vrid<value>

Configuring VRRP on a port or a VLANUse the following procedure to configure VRRP on a port or a VLAN.

Prerequisites

• Access Interface configuration mode.

• Enable IPv6 forwarding globally.

• Configure IPv6 on the interface.

Procedure steps

1. Configure the VRRP address on a port by using the following command: ipv6vrrp address <1-255> {[global <X:X:X:X:X:X:X:X>/len] [link-local <fe80::X:X:X:X>}

2. Configure VRRP properties on a port by using the following command: ipv6 vrrp<1-255>

3. Enable the VRRP instance by using the following command: ipv6 vrrp <1-255>enable

4. Delete VRRP from the port by using the following command: no ipv6 vrrp<1-255>

5. Show the global VRRP settings by using the following command: show ipv6vrrp

Variable definitionsUse the data in the following table to configure VRRP.

Configuring VRRP on a port or a VLAN


Variable Value{[global <X:X:X:X:X:X:X:X>/len][link-local <fe80::X:X:X:X>}

Specifies a global or link-local (or both) IPv6 VRRPaddress.

accept-mode enable Controls whether a master router accepts packetsaddressed to the address owner's IPv6 address as itsown if it is not the IPv6 address owner. The default valueis disable.

action {none|preempt} Use the action choice option to manually override thehold-down timer and force preemption.

none|preempt can be set to preempt the timer or set tonone to allow the timer to keep working.

To set this option to the default value, use the defaultoperator with this command.

adver-int <1-255> Sets the the time interval between sending VRRPadvertisement messages. The range is between 1 and255 seconds. This value must be the same on allparticipating routers. The default is 1.To set this option to the default value, use the defaultoperator with this command.

backup-master enable Enables the VRRP backup master.This option is supported only on triangular Split MultiLinkTrunking (SMLT) ports.Use the no operator to disable the VRRP backup master:no ipv6 vrrp <1-255> backup-master enableTo set this option to the default value, use the defaultoperator with this command.

Important:Do not enable Backup Master if Critical IPv6 isenabled.

critical-ipv6-addr<X:X:X:X:X:X:X:X>

Sets the critical IPv6 address for VRRP.

X:X:X:X:X:X:X:X is the IPv6 address on the local router,which is configured so that a change in its state causesa role switch in the virtual router (for example, frommaster to backup in case the interface goes down).

critical-ipv6 enable Enables the critical IPv6 address option.Use the no operator to disable the critical IPv6 addressoption: no ipv6 vrrp <1-255> critical-ipv6 enableTo set this option to the default value, use the defaultoperator with this command.

Important:Do not enable Critical IPv6 if Backup Master isenabled.

enable Enables VRRP on the port.



Variable ValueUse the no operator to disable VRRP on the port: no ipv6vrrp <1-255> enableTo set this option to the default value, use the defaultoperator with this command.

fast-adv enable Enables the Fast Advertisement Interval. The default isdisabled.Use the no operator to disable VRRP on the port: no ipv6vrrp <1-255> fast-adv enableTo set this option to the default value, use the defaultoperator with this command.

fast-adv-int <200-1000> Sets the Fast Advertisement Interval, the time intervalbetween sending VRRP advertisement messages.

200-1000 is the range in milliseconds, and must be thesame on all participating routers. The default is 200. Youmust enter values in multiples of 200 milliseconds.


holddown-timer <0-21600> Modifies the behavior of the VRRP failover mechanism byallowing the router enough time to detect the OpenShortest Path First (OSPF) or Routing InformationProtocol (RIP) routes.

0-21600 is the time interval (in seconds) a router isdelayed when changing to master state.


priority <1-255> Sets the port VRRP priority.

1-255 is the value used by the VRRP router. The defaultis 100. Assign the value 255 to the router that owns theIPv6 address associated with the virtual router.


Showing VRRP port or VLAN informationDisplay VRRP port or VLAN information to verify your configuration.

Showing VRRP port or VLAN information


Prerequisites


Procedure steps

Show the extended VRRP configuration for all VLANs on the switch or for the specifiedVLAN by using the following command: show ipv6 vrrp interface <port-type> [<1-4094>] [<portList>] vlan [<1-4094>] [<portList>] vrid<1-255> [statistics] [verbose]

Variable definitionsUse the data in the following table to use the show ipv6 vrrp interface command.

Variable Value<port-type> [<1-4094>][<portList>]

Displays information by port type, and optionally byspecified VLAN ID and ports.

vlan [<1-4094>] [<portList>] Displays information by VLAN, and optionally by specifiedVLAN ID and ports.

vrid <1-255> Displays information by virtual router ID.

statistics Displays VRRP statistics for the interface.

verbose Displays extended information.

Job aidThe following table shows the field descriptions for the show ipv6 vrrp interfacecommand.


PORT NUM Indicates the port number.

VRRP ID Indicates the virtual router ID on a VRRP router.

IPv6 ADDRESS Indicates the assigned IPv6 addresses that a virtual routerbacks up.



Parameter DescriptionVIRTUAL MACADDRESS

Indicates the virtual MAC address of the virtual router in theformat 00-00-5E-00-02-<VRID>, where the first three octetsconsist of the IANA OUI; the next two octets indicate theaddress block of the VRRP protocol; and the remaining octetsconsist of the VRID.

The following table shows the field descriptions for the show ipv6 vrrp interfaceverbosecommand.


PORT NUM Indicates the port number.


STATE Indicates the current state of the virtual router.



• master—forwarding IP addresses associated with this virtualrouter

CONTROL Indicates the virtual router function. Set the value to enabled totransition the state of the router from initialize to backup. Setthe value to disabled to transition the router from master orbackup to initialize.

PRIORITY Indicates the priority for the virtual router (for example, masterelection) with respect to other virtual routers that are backingup one or more associated IP addresses. Higher valuesindicates higher priority.A priority of 0, which you cannot set, indicates that this routerceased to participate in VRRP and a backup virtual routertransitions to become a new master.Use a priority of 255 for the router that owns the associated IPaddresses.

MASTER IPADDR Indicates the master router real (primary) IP address. This isthe IP address listed as the source in the VRRP advertisementlast received by this virtual router.

ADVERTISE INTERVAL Indicates the time interval, in seconds, between sendingadvertisement messages. Only the master router sends VRRPadvertisements.

CRITICAL IPADDR Indicates the IP address of the interface that causes a shutdownevent.

Showing VRRP port or VLAN information


Parameter DescriptionHOLDDWN Indicates the amount of time (in seconds) to wait before

preempting the current VRRP master.

ACTION TIME Specifies whether to override the holddown timer manually andforce preemption. Options are none (does not override thetimer) and preempt (preempts the timer).

CRITICAL IP ENABLE Indicates that a user-defined critical IP address is enabled. Noindicates the use of the default IP address (::or0:0:0:0:0:0:0:0).

BACKUP MASTER Indicates the state of designating a backup master router.

BACKUP MASTERSTATE

Indicates the state of the backup master router.

FAST ADV INTERVAL Indicates the time interval, in milliseconds, between sendingFast Advertisement messages. When the Fast AdvertisementInterval is enabled, the Fast Advertisement Interval is usedinstead of the regular advertisement interval.

FAST ADV ENABLE Indicates the Fast Advertisement Interval status.

Showing VRRP interface informationUse this procedure to show VRRP information by IPv6 address or virtual router ID.

If you enter a virtual router ID or an IPv6 address when showing VRRP information, theinformation displays only for that virtual router ID or for that interface.



Prerequisites


Procedure steps

1. To display VRRP configuration information, enter the following command: showipv6 vrrp address [link-local <fe80::X:X:X:X>] [vrid<1-255>]

2. To display VRRP statistics, enter the following command: show ipv6 vrrpstatistics [link-local <fe80::X:X:X:X>] [vrid <1-255>]

Variable definitionsUse the data in the following table to use the show ipv6 vrrp command.

Variable Value[link-local <fe80::X:X:X:X>] Displays information by link-local IPv6 address.

[vrid <1-255>] Displays information by virtual router ID.

Job aidThe following table shows the field descriptions for the show ipv6 vrrp addresscommand.

Parameter DescriptionVRID Indicates the virtual router ID on a VRRP router.

P/V Indicates whether this device responds to pings directed to avirtual router's IPv6 address.

IP Indicates the assigned IPv6 addresses that a virtual routerbacks up.

MAC Indicates the virtual MAC address of the virtual router in theformat 00-00-5E-00-02-<VRID>, where the first three octetsconsist of the IANA OUI; the next two octets indicate theaddress block of the VRRP protocol; and the remaining octetsconsist of the VRID.

Showing VRRP interface information


Parameter DescriptionSTATE Indicates the current state of the virtual router.



• master—forwarding IPv6 addresses associated with thisvirtual router.

CONTROL Indicates the virtual router function. Set the value to enabledto transition the state of the router from initialize to backup. Setthe value to disabled to transition the router from master orbackup to initialize.

PRIO Indicates the priority for the virtual router (for example, masterelection) with respect to other virtual routers that are backingup one or more associated IPv6 addresses. Higher valuesindicate higher priority.A priority of 0, which you cannot set, indicates that this routerhas stopped participating in VRRP and a backup virtual routertransitions to become the new master.A priority of 255 is used for the router that owns the associatedIPv6 addresses.

ADV Indicates the Advertisement Interval, in milliseconds, betweensending advertisement messages.

MASTER Indicates the master router real (primary) IPv6 address. Thisis the IPv6 address listed as the source in the VRRPadvertisement last received by this virtual router.

UP TIME Indicates the time interval (in hundredths of a second) sincethis virtual router was initialized.

CRITICAL IPv6 Indicates the IPv6 address of the interface that causes ashutdown event.

CRITICAL IPv6(ENABLED)

Indicates if the critical IPv6 address is enabled.

BACKUP-MASTER Indicates the backup master IPv6 address.

BACKUP-MASTER STATE Indicates the backup master state.

FAST ADV Indicates the Fast Advertisement Interval, in milliseconds,between sending advertisement messages. When the FastAdvertisement Interval is enabled, the Fast AdvertisementInterval is used instead of the regular advertisement interval.

FAST ADV (ENABLED) Indicates the state of fast advertisement.

ACCEPT MODE Controls whether a master router accepts packets addressedto the address owner's IPv6 address as its own if it is not theIPv6 address owner. The default value is disable.



Parameter DescriptionACTION Specifies whether to override the holddown timer manually

and force preemption. Options are none (does not override thetimer) and preempt (preempts the timer).

HLD DWN Indicates the amount of time (in seconds) to wait beforepreempting the current VRRP master.

REM Indicates the remaining hold-down timer value.

GLOBAL ADDRESS Specifies the global IPv6 address associated with the link-local VRRP IPv6 address that the virtual router backs up.

Clearing VRRP statisticsUse the following procedure to clear IPv6 VRRP statistics.

Procedure steps

To clear IPv6 VRRP statistics, enter: clear ipv6 vrrp {fastethernet <slot|port>| gigabitethernet <slot|port>| vlan <vid>} vrid <value>

Variable definitionsUse the data in the following table to use the clear ipv6 vrrp command.

Variable Value{fastethernet <slot|port>|gigabitethernet <slot|port>| vlan<vid>}

Specifies the port or VLAN for which to clear statistics.

[vrid <1-255>] Specifies the virtual router ID.

Clearing VRRP statistics




Chapter 17: IPv6 RSMLT configurationusing Enterprise DeviceManager

Routed Split MultiLink Trunking (RSMLT) forwards packets in the event of core router failures, thusminimizing dropped packets during the routing protocol convergence.

To configure IPv6 RSMLT functionality, use the same configuration path as required for IPv4 RSMLT.RSMLT configuration on a given VLAN simultaneously affects both IPv4 and IPv6. All options apply equallyto IPv6 and IPv4 RSMLT.

Note that enabling RSMLT on a VLAN for IPv6 enables RSMLT even in the absence of IPv4 configurationon the VLAN.

In addition to the IPv4 RSMLT tabs, the Enterprise Device Manager provides tabs for viewing IPv6-specificRSMLT information.

Navigation• Configuring RSMLT on a VLAN on page 255

• Enabling RSMLT-edge on page 257

• Viewing and editing IPv6 RSMLT local information on page 257

• Viewing and editing IPv6 RSMLT peer information on page 258

• Viewing IPv6 RSMLT-edge information on page 260

Configuring RSMLT on a VLANYou can configure RSMLT on each IP VLAN interface.


Prerequisites

• IP routing protocol on VLAN Layer 3 interfaces is enabled.

• VLANs with Layer 3 interfaces participate in Split MultiLink Trunking (SMLT).

Procedure steps


2. Click VLANs.

3. In the VLANs Basic tab, select a VLAN.

4. Click IP.

5. Click the RSMLT tab.

6. Select Enable.

7. In the HoldDownTimer box, enter a hold-down timer value.

8. In the HoldUpTimer box, enter a hold-up timer value.

9. Click Apply.

Variable definitionsUse the data in the following table to configure RSMLT.

Variable ValueEnable Enables RSMLT.

HoldDownTimer Defines how long the recovering or rebooting switchremains in a non-Layer 3 forwarding mode for the peerrouter MAC address.The range of this value is from 0 to 3600 seconds.

HoldUpTimer Defines how long the RSMLT switch maintainsforwarding for its peer. The value is a range from 0 to3600 seconds or 9999. 9999 means infinity.

IPv6 RSMLT configuration using Enterprise Device Manager


Enabling RSMLT-edgeEnable RSMLT-edge to store the RSMLT peer MAC/IP address-pair in its local configurationfile and restore the configuration if the peer does not restore after a simultaneous reboot ofboth RSMLT peer switches.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IP.

2. Click RSMLT.

3. In the Globals tab, select the EdgeSupportEnable option box.

4. Click Apply.

Viewing and editing IPv6 RSMLT local informationUse the following procedure to view and edit RSMLT local VLAN switch information.

Any configurations you make using this tab are not specific to IPv6. The configurations appliedunder the IPv6 RSMLT tab also apply to IPv4 RSMLT.

Procedure steps


2. Click RSMLT.

3. In the Local tab, edit fields as required.

4. Click Apply.

Variable definitionsUse the data in the following table to view and edit IPv6 RSMLT local information.

Variable ValueIfIndex The IP route SMLT operation index.

Enabling RSMLT-edge


Variable ValueIpv6Addr The IP address of the VLAN when RSMLT is enabled.

Ipv6PrefixLength

The IPv6 prefix length.

Enable Specifies the status of RSMLT

HoldDownTimer Defines how long the recovering/rebooting switch remains in a non-Layer3 forwarding mode for the peer router MAC address.The range of this value is from 0 to 3600 seconds.


Indicates the time remaining in the HoldDownTimer.

HoldUpTimer Defines how long the RSMLT switch maintains forwarding for its peer.The value is a range from 0 to 3600 seconds or 9999. 9999 meansinfinity.

HoldUpTimeRemaining

Indicates the time remaining in the HoldUpTimer.

OperStatus Displays the RSMLT operating status as either up or down.

SmltId The ID range for the SMLT. A valid range is 1 to 32.

SltId The ID range for the SMLT. A valid range is 1 to 512.

VlanId The VLAN ID of the chosen VLAN.

MacAddr The MAC address of the selected VLAN.

VrfId Identifies the VRF.

VrfName Indicates the VRF name.

Viewing and editing IPv6 RSMLT peer informationUse this procedure to view and edit RSMLT peer switch information.

Any configurations you make using this tab are not specific to IPv6. The configurations appliedunder the IPv6 RSMLT tab also apply to IPv4 RSMLT.

Procedure steps


2. Click RSMLT.

3. Click the Peer tab.



4. Edit fields as required.

5. Click Apply.

Variable definitionsUse the data in the following table to view and edit IPv6 RSMLT peer information.

Variable ValueIfIndex The IP route SMLT operation index.

Ipv6Addr The IP address of the VLAN when RSMLT is enabled.

Ipv6PrefixLength IPv6 prefix length.

AdminStatus Indicates whether the peer is enabled.

HoldDownTimer Defines how long the recovering/rebooting switch remains in anon-Layer 3 forwarding mode for the peer router MACaddress.The range of this value is from 0 to 3600 seconds.


Displays the time remaining of the HoldDownTimer.

HoldUpTimer Defines how long the RSMLT switch maintains forwarding forits peer.The value is a range from 0 to 3600 seconds or 9999. 9999means infinity.

HoldUpTimeRemaining Displays the time remaining of the HoldUpTimer.

OperStatus Displays the RSMLT operating status as either up or down.

SmltId The ID range for the Split MultiLink Trunk. A valid range is 1 to32.

SltId The ID range for the Split MultiLink Trunk. A valid range is 1 to512.

VlanId The ID of the VLAN on which RSMLT is enabled.

MacAddr The MAC address of the selected VLAN.

VrfId Identifies the VRF.

VrfName Indicates the VRF name.

Viewing and editing IPv6 RSMLT peer information


Viewing IPv6 RSMLT-edge informationView RSMLT-edge to verify the RSMLT peer MAC/IP address-pair in its local config file andrestore the configuration if the peer does not restore after a simultaneous reboot of bothRSMLT-peer switches.

Procedure steps


2. Click RSMLT.

3. Click the Edge Peer tab.

Variable definitionsUse the data in the following table to view IPv6 RSMLT-edge information.

Parameter DescriptionPeerVlanId The ID of the VLAN associated with this entry

PeerIpv6Address The IPv6 address of the peer RSMLT interface.

PeerIpv6PrefixLength Peer IPv6 address prefix.

PeerMacAddress The peer MAC address.

PeerVrfId Identifies the Peer VRF.

PeerVrfName The Peer VRF name.

PeerlsRaPrefix True if this is a Router Advertisement prefix, False if this is aglobal address.

PeerConfType Type of configured address, passed opaquely to Infinity.

PeerNoAdvertise True if advertisement of this prefix is disabled, passed opaquelyto Infinity.

PeerOspf6Advertise True if OSPFv3 advertisement of this prefix is enabled, passedopaquely to Infinity.

PeerPrefCandidate True if address is considered for preferred selection, passedopaquely to Infinity.

PeerPfxValidLife Valid lifetime in seconds, passed opaquely to Infinity.

PeerPfxPrefLife Preferred lifetime in seconds, passed opaquely to Infinity.



Parameter DescriptionPeerPfxOnLinkFlag If set then this prefix can be used for onlink determination,

passed opaquely to Infinity.

PeerPfxAutoFlag If set then this prefix can be used for address autoconfig,passed opaquely to Infinity.

Viewing IPv6 RSMLT-edge information




Chapter 18: IPv6 RSMLT configurationusing the CLI


To configure IPv6 RSMLT functionality, use the same set of commands as required for IPv4 RSMLT.RSMLT configuration on a given VLAN simultaneously affects both IPv4 and IPv6. For example, thefollowing command is used for configuring IPv6 RSMLT on VLAN:

config vlan <vid> ip rsmltAll options apply equally to IPv6 and IPv4 RSMLT.

Note that the preceding command enables IPv6 RSMLT on a VLAN even in the absence of IPv4configuration on the VLAN.

RSMLT configuration proceduresThis task flow shows you the sequence of procedures you perform to configure RSMLT.

RSMLT configuration navigation• Job aid: Roadmap of IPv6 RSMLT CLI commands on page 263

• Configuring RSMLT on a VLAN on page 264

• Showing IP RSMLT information on page 265

• Configuring RSMLT-edge on page 266

Job aid: Roadmap of IPv6 RSMLT CLI commandsThe following table lists the commands and their parameters that you use to complete theprocedures in this section.


Table 22: Roadmap of RSMLT commands

Command Parameterconfig vlan <vid> ip rsmlt info

disable

enable


holdup-timer <seconds>

config ip rsmlt rsmlt-edge-support <enable|disable>

clear-rsmlt-peer [<vlanId>]

info

show ip rsmlt info [<local|peer>]


Prerequisites

• The IPv6 routing protocol must be enabled on the VLAN interfaces.• VLANs with Layer 3 interfaces must also participate in Split MultiLink Trunking (SMLT).

Procedure stepsProcedure steps

1. Create an RSMLT on a VLAN by using the following command: config vlan<vid> ip rsmlt

2. Confirm your configuration by using the following command: config vlan <vid>ip rsmlt info

Variable definitionsUse the data in the following table to use the config vlan ip rsmlt command.

IPv6 RSMLT configuration using the CLI


Variable Valuedisable Disables RSMLT on the VLAN.

enable Enables RSMLT on the VLAN.

holddown-timer <seconds> Defines how long the recovering/rebootingswitch remains in a non-Layer 3 forwardingmode for the peer router MAC address.

seconds is the timer value in seconds. Therange of the value is from 0 to 3600seconds.

holdup-timer <seconds> Defines how long the RSMLT switchmaintains forwarding for its peer.

seconds is the timer value in seconds. Thevalue is a range from 0 to 3600 seconds or9999. 9999 means infinity.

info Displays the RSMLT local and peerinformation.

vid The VLAN ID in the range of 1 to 4094.

Showing IP RSMLT informationShow RSMLT information to view data for all RSMLT interfaces. The output of the commandincludes the IPv6 formation for the local and peer nodes.

Procedure steps

Display RSMLT information about the interface by using the following command: showip rsmlt info [<local|peer>]

Variable definitionsUse the data in the following table to use the show ip rsmlt info [<local|peer>]command.

Variable Value[<local|peer>] Specifies the local or peer switch.

Showing IP RSMLT information


Job aidThe following table shows the field descriptions for the show ip rsmlt info command.

Table 23: show ip rsmlt info command

Parameter DescriptionVID Indicates the VLAN ID.

IP Indicates the IP address of the router.

MAC Indicates the MAC address assigned.

ADMIN Indicates the administrative status of RSMLT on the router.

OPER Indicates the operational status of RSMLT on the router.

HDTMR Indicates the hold-down timer value in the range of 0 to 3600 seconds.

HUTMR Indicates the range of the hold-up timer in the range of 0 to 3600 secondsor 9999. 9999 means infinity.

HDT REMAIN Indicates the time remaining of the hold-down timer.

HUT REMAIN Indicates the time remaining of the hold-up timer.

SMLT ID Indicates the Split MultiLink Trunk ID.

SLT ID Indicates the SLT ID.

Configuring RSMLT-edgeConfigure RSMLT-edge to store the RSMLT peer MAC/IP address pair in its local configurationfile and restore the configuration if the peer does not restore after a simultaneous reboot ofboth RSMLT peer switches. If enabled, all peer MAC/IP information for all RSMLT-enabledVLANs saved during next the save configuration command.

Procedure steps

1. Enable or disable RSMLT-edge by using the following command: config iprsmlt rsmlt-edge-support <enable|disable>

2. Clear the peer MAC/IP information for the VLAN by using the following command:config ip rsmlt clear-rsmlt-peer <vlanId>

3. Display RSMLT configuration and status information by using the followingcommand: config ip rsmlt info



Variable definitionsUse the data in the following table to use the config ip rsmlt rsmlt-edge-supportcommand.

Variable Valuedisable Disables RSMLT peer forwarding.

enable Enables RSMLT peer forwarding.

Configuring RSMLT-edge




Chapter 19: IPv6 RSMLT configurationusing the ACLI


To configure IPv6 RSMLT functionality, use the same set of commands as required for IPv4 RSMLT.RSMLT configuration on a given VLAN simultaneously affects both IPv4 and IPv6. For example, thefollowing command is used for configuring IPv6 RSMLT on a VLAN:

(config-if)# ip rsmltAll options apply equally to IPv6 and IPv4 RSMLT.

Note that the preceding command enables IPv6 RSMLT on a VLAN even in the absence of IPv4configuration on the VLAN.

RSMLT configuration proceduresRefer to the following procedures to configure RSMLT.

RSMLT navigation• Job aid: Roadmap of IPv6 RSMLT ACLI commands on page 269

• Configuring RSMLT on a VLAN on page 270

• Showing IP RSMLT information on page 271

• Configuring RSMLT-edge on page 272

Job aid: Roadmap of IPv6 RSMLT ACLI commandsThe following table lists the commands and their parameters that you use to complete theprocedures in this section.


Table 24: Roadmap of RSMLT commands

Command ParameterPrivExec Mode

show ip rsmlt edge-support

<local|peer>

Interface Configuration Mode

ip rsmlt holddown-timer <0-3600>

holdup-timer <seconds>

Global Configuration Mode

ip rsmlt edge-support

no ip rsmlt peer-address


Prerequisites

• Access VLAN Interface Configuration Mode.

• The IPv6 routing protocol must be enabled on the VLAN interfaces.

• VLANs with Layer 3 interfaces must also participate in Split MultiLink Trunking (SMLT).

Procedure steps

Enable RSMLT on a VLAN by using the following command: ip rsmltUse the no operator to disable RSMLT: no ip rsmltTo set this value to the default value, use the default operator with this command.

Variable definitionsUse the data in the following table to use the ip rsmlt command.

IPv6 RSMLT configuration using the ACLI


Variable Valueholddown-timer <0-3600> Defines how long the RSMLT switch does not

participate in Layer 3 forwarding.

0-3600 is the timer value in seconds.

To set this value to the default value, use the defaultoperator with this command.Avaya recommends that you configure this value to belonger than the anticipated routing protocolconvergence.

holdup-timer <seconds> Defines how long the RSMLT switch maintainsforwarding for its peer.

seconds is the timer value in seconds. The value isa range from 0 to 3600 seconds or 9999. 9999means infinity.

To set this value to the default value, use the defaultoperator with this command.

Showing IP RSMLT informationShow IP RSMLT information to view data about all RSMLT interfaces. The output of thecommand includes the IPv6 formation for the local and peer nodes.

Prerequisites

Access privExec Configuration Mode or Global Configuration Mode.

Procedure steps

Display RSMLT information about the interface by using the following command: showip rsmlt [<local|peer>]

Variable definitionsUse the information in the following command to complete the show ip rsmlt command.

Showing IP RSMLT information



Variable Value[<local|peer>] Specifies values for the local or peer switch.

Job aidThe following table shows the field descriptions for theshow ip rsmlt [<local|peer>]command.


Parameter DescriptionVID Indicates the VLAN ID.

IP Indicates the IP address of the router.

MAC Indicates the MAC address assigned.

ADMIN Indicates the administrative status of RSMLT on the router.

OPER Indicates the operational status of RSMLT on the router.

HDTMR Indicates the hold-down timer value in the range of 0 to 3600 seconds.

HUTMR Indicates the hold-up timer value in the range of 0 to 3600 seconds or9999. 9999 means infinity.

HDT REMAIN Indicates the time remaining of the hold-down timer.

HUT REMAIN Indicates the time remaining of the hold-up timer.

SMLT ID Indicates the Split MultiLink Trunk ID.

SLT ID Indicates the SLT ID.

Configuring RSMLT-edgeConfigure RSMLT-edge to store the RSMLT peer MAC/IP address-pair in its local config fileand restore the configuration if the peer does not restore after a simultaneous reboot of bothRSMLT-peer switches. If enabled, all peer MAC/IP information for all RSMLT-enabled VLANsare saved during next the save config command.



Prerequisites

Access Global configuration mode.

Procedure steps

1. Enable RSMLT-edge by using the following command: ip rsmlt edge-supportUse the no operator to disable RSMLT-edge: no ip rsmlt edge-support

2. Clear RSMLT peer information and delete the RSMLT peer address by using thefollowing command: no ip rsmlt peer-address <vlan ID>

3. Display RSMLT-edge status information by using the following command: show iprsmlt edge-support

Variable definitionsUse the data in the following table to use the no ip rsmlt peer-address command.

Variable Value<vlan ID> The ID of the VLAN in the range of 0 to 4094.

Configuring RSMLT-edge




Chapter 20: IPv4-to-IPv6 transitionmechanism configuration usingEnterprise Device Manager

This section describes how to use Enterprise Device Manager to configure transition mechanisms, ortunnels, for IPv6 traffic through IPv4 networks. For conceptual information about tunnels, see IPv6 routingfundamentals on page 15.

Prerequisites to IPv4-to-IPv6 transition mechanismconfiguration

Both the source and destination devices must use IPv6 and IPv4 addresses.

IPv4-to-IPv6 transition mechanism configurationnavigation

• Configuring the local VLAN or brouter port on page 275

• Configuring the destination VLAN or brouter port on page 277

• Configuring OSPF on a tunnel on page 278

• Deleting a tunnel on page 279

• Modifying tunnel hop limits on page 279

Configuring the local VLAN or brouter portConfigure a tunnel for IPv6 VLANs or brouter ports to communicate through an IPv4 network.Manual tunnels are point-to-point, so you configure both source and destination addresses.You must configure both IPv6 and IPv4 addresses for both source and destination devices.


The IPv6 addresses must represent the same network, for example 6666::1/96 and6666::2/96.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click Tunnel.3. Click Insert.4. In the LocalAddress box, click the button and select the IPv4 address for the local

VLAN or brouter port.5. In the RemoteAddress box, type the IPv4 address for the destination VLAN or

brouter port.6. In the EncapsMethod area, select manual.7. In the ID box, type a number to represent the tunnel.8. In the IPv6AddressAddr box, type the IPv6 address assigned to the tunnel VLAN

or brouter port.9. In the IPv6AddressPrefixLength box, type the number of bits to advertise in the

IPv6 address.10. Click Insert.

After you create the tunnel, the Local Address tab displays the IPv4 addressesassociated with the tunnel.

Variable definitionsUse the data in the following table to use the Tunnel tab.

Variable ValueAddress Type Displays the address type for the tunnel: IPv4 for IPv6

packets encapsulated in IPv4.

LocalAddress Identifies the local endpoint address of the tunnel.

RemoteAddress Identifies the remote endpoint of the tunnel.

EncapsMethod Displays the tunnel mode: IPv6 for manually configuredtunnels and sixtoFour for automatically configuredtunnels.The default value is manual.

ID Identifies the tunnel number.

IfIndex Displays a unique value that identifies the tunnel interfaceinternally. The value is derived from the tunnel ID.

IPv4-to-IPv6 transition mechanism configuration using Enterprise Device Manager


Configuring the destination VLAN or brouter portUse the following procedure to configure a tunnel for IPv6 VLANs or brouter ports tocommunicate through an IPv4 network. Manual tunnels are point-to-point, so you configureboth source and destination addresses. You must configure both IPv6 and IPv4 addresses forboth source and destination devices. The IPv6 addresses must represent the same network,for example 6666::1/96 and 6666::2/96.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click Tunnel.3. Click Insert.4. In the LocalAddress box, click the button and select the IPv4 address for the

destination VLAN or brouter port.5. In the RemoteAddress box, type the IPv4 address for the local VLAN or brouter

port.6. In the EncapsMethod area, select manual.7. In the ID box, type a number to represent the tunnel.8. In the IPv6AddressAddr box, type the IPv6 address that you configured for the

tunnel VLAN or brouter port for the destination VLAN or brouter port.9. In the IPv6AddressPrefixLength box, type the number of bits to advertise in the

IPv6 address.10. Click Insert.

After you create the tunnel, the Local Address tab displays the IPv4 addressesassociated with the tunnel.

Variable definitionsUse the data in the following table to use the Tunnel tab.

Variable ValueAddress Type Displays the address type for the tunnel: IPv4 for IPv6

packets encapsulated in IPv4.

LocalAddress Identifies the local endpoint address of the tunnel.

RemoteAddress Identifies the remote endpoint of the tunnel.

Configuring the destination VLAN or brouter port


Variable ValueEncapsMethod Displays the tunnel mode: IPv6 for manually configured

tunnels and sixtoFour for automatically configuredtunnels.

ID Identifies the tunnel number.

IfIndex Displays a unique value that identifies the tunnel interfaceinternally. The value is derived from the tunnel ID.

Configuring OSPF on a tunnelConfigure the Open Shortest Path First (OSPF) protocol on IPv6 tunnels to support dynamicrouting on the tunnel.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click Tunnel.3. Select the tunnel on which to configure OSPF.4. Click IPv6 OSPF.

The OSPF Interface tab appears.5. Click Insert.6. In the AreaId box, click the button and select the required area ID.7. In the AdminStat area, select enabled.8. In the RtrPriority box, modify the priority value if required.9. Modify values in the TransitDelay, RetransitInterval, HelloInterval,

RtrDeadInterval, or PollInterval boxes, if required.10. In the MulticastForwarding area, select the required option: blocked, multicast,

or unicast.11. Select the Demand check box to enable demand for an instance.12. In the Metric box, type the metric value for a demand for an instance.13. In the InstId box, type the instance ID.14. Click Insert.15. On the OSPF Interface tab, click Apply.



Deleting a tunnelDelete a tunnel to remove it from the configuration.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click Tunnel.3. Select the tunnel to delete.4. Click Delete.

Modifying tunnel hop limitsModify tunnel hop limits to update hop limit values on previously configured tunnels.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click Tunnel.3. Click the Tunnel Interface tab.4. In the row for the tunnel to configure, click the HopLimit column to modify the

displayed information as required.5. Click Apply.

Variable definitionsUse the data in the following table to use the Tunnel Interface tab.

Variable ValueIndex Identifies the tunnel interface internally. The value is derived

from the tunnel ID.

EncapsMethod Displays the tunnel mode: IPv6 for manually configured tunnelsand 6to4 for automatically configured tunnels.

HopLimit Configures the maximum number of hops in the tunnel.The default value is 255.

Security Indicates the type of security on the tunnel interface.

Deleting a tunnel


Variable ValueTOS Displays the method used to configure the high 6 bits (the

differentiated services codepoint) of the IPv4 type of service(TOS) or IPv6 traffic class in the outer IP header. A value of -1indicates that the bits are copied from the payload header. Avalue of -2 indicates that a traffic conditioner is invoked andmore information can be available in a traffic conditioner MIBmodule. A value from 0 to 63 indicates that the bit field isconfigured to the indicated value.

FlowLabel Displays the method used to set the IPv6 Flow Label value. Thisobject need not be present in rows where tunnelIfAddressTypeindicates the tunnel is not over IPv6. A value of -1 indicates thata traffic conditioner is invoked and more information can beavailable in a traffic conditioner MIB. Any other value indicatesthat the Flow Label field is configured to the indicated value.

AddressType Displays Manual for a manually configured tunnel, or sixToFourfor autoconfigured tunnels.

LocalInetAddress Identifies the local endpoint address of the tunnel.

RemoteInetAddress Identifies the remote endpoint of the tunnel.

EncapsLimit Displays the address of the local endpoint of the tunnel (that is,the source address used in the outer IP header). If the addressis unknown, the value is 0.0.0.0 for IPv4 or :: for IPv6. ThetunnelIfAddressType displays the object type.



Chapter 21: IPv4-to-IPv6 transitionmechanism configuration usingthe CLI

This chapter describes how to use the CLI to configure IPv6 transition mechanisms, or tunnels. Forconceptual information about tunnels, see IPv6 routing fundamentals on page 15.


• You must configure the local and remote switches with IPv4 addresses that you canping.

• You must configure the local and remote switches with one or more of the followingprotocols to route IPv4 traffic: Static, RIP, or OSPF.


• Job aid: Roadmap of tunnel configuration CLI commands on page 281

• Configuring manual tunnels on page 282


• Deleting a tunnel on page 286

Job aid: Roadmap of tunnel configuration CLI commandsThe following table lists the commands and parameters that you use to perform the proceduresin this chapter.


Table 27: Job aid: Roadmap of tunnel configuration CLI commands

Command Parameterconfig ipv6 tunnel <tunnel id> create local-addr <source ipv4 address> ipv6addr<source ipv6address/prefix-lenth> remot-address <dst ipv4address>

info

delete

hop-limit <value>

config ipv6 tunnel <tunnel-id> ospf info


create <area> [priority <value>] [metric<value>] [retransmit-interval <value>][transit-delay <value>] [hello-interval<value>] [dead-interval <value>]

delete




metric <metric>

priority <priority>



Configuring manual tunnelsCreate a tunnel to transfer traffic between IPv6 devices in an IPv4 network. Configure manualtunnels when you want to define both the local and destination addresses.

Use this procedure to configure the tunnel at both the source and destination addresses.

Procedure steps

1. Configure the tunnel at the source by using the following command:

config ipv6 tunnel <tunnel id> create local-addr <source ipv4 address>ipv6addr <source ipv6 address/prefix length> remote-address <remote ipv4address>

2. Configure the tunnel at the destination by using the following command:

IPv4-to-IPv6 transition mechanism configuration using the CLI


config ipv6 tunnel <tunnel id> create local-addr <remote ipv4 address>ipv6 addr <remote ipv6 address/prefix length> remote-address <source ipv4address>

Variable definitionsUse the data in the following table to use the config ipv6 tunnel command.

Variable Valuecreate [local addr <value> ][ipv6addr <value> ] [remote-address <value>]

Creates the tunnel for a VLAN or brouter port.

• local addr <value> configures the address for thelocal device.

• ipv6addr <value> configures the local address forthe tunneled device in IPv6/prefix-length format.

• remote-address <value> configures the address forthe device that is tunneled to in IPv4 or IPv6/prefix-length format.

delete Deletes the tunnel.

hop-limit <value> Configures the maximum number of hops that apacket can make before it is dropped.

value is in the range 0–255.

info Displays the current settings for the command.

tunnel id Specifies the ID number of the tunnel in the range of1-5000.

Example of configuring manual tunnelsProcedure steps

1. Configure the tunnel at the source.

ERS-8610:5#config ipv6 tunnel 1044 create local addr20.10.10.107 ipv6addr0100:0200:0300:0004:0005:0006:0000:aa01/80 remote-address10.20.20.105

2. Configure the tunnel at the destination.

ERS-8610:5#config ipv6 tunnel 1045 create local addr10.20.20.105 ipv6addr0100:0200:0300:0004:0005:0006:0000:aa02/80 remote-address20.10.10.107

Configuring manual tunnels


Configuring OSPF on a tunnelConfigure OSPF on a VLAN or brouter tunnel to create a dynamic IPv6 tunnel on the OSPFinterface.

Procedure steps

Configure OSPF on a tunnel by using the following command:

config ipv6 tunnel <tunnel-id> ospf

Variable definitionsUse the data in the following table to use the config ipv6 tunnel ospf command.


OSPF interface.

create <area> [priority <value> ][metric <value> ] [retransmit-interval <value> ] [transit-delay<value> ] [hello-interval <value> ][dead-interval <value> ] [type<value> ]


• <area> is the area IP address (0.0.0.0 to255.255.255.255) {a.b.c.d}.



• retransmit-interval <value> is theretransmit interval in the range 1–1800 seconds.

• transit-delay <value> is the transit delay inthe range 1–1800 seconds.

• hello-interval <value> is the hello interval inthe range 1–65535 seconds.

• dead-interval <value> is the dead interval inthe range 1–4095 seconds.

dead-interval <seconds> Configures the OSPF dead interval for the interface.seconds is the number of seconds the switch OSPFneighbors wait before determining that this OSPFrouter is down. The range is from 1–4095. This value



Variable Valuemust be at least four times the Hello interval value. Thedefault is 40.




info Displays OSPF characteristics for the interface.

metric <metric> Configures the OSPF metric for the interface. Theswitch advertises the metric in router linkadvertisements.

metric is the range 0–65535.

poll-interval <seconds> Configures the polling interval for the OSPF interfacein seconds.

seconds is 0–2147483647.

priority <priority> Configures the OSPF priority for the interface duringthe election process for the designated router. Theinterface with the highest priority number is thedesignated router. The interface with the second-highest priority becomes the backup designatedrouter. If the priority is 0, the interface cannot becomeeither the designated router or a backup. The priorityis used only during election of the designated routerand backup designated router.priority is in the range 0–255. The default is 1.

retransmit-interval <seconds> Configures the retransmit interval for the OSPFinterface; the number of seconds between link-stateadvertisement retransmissions.seconds is an integer 1–1800.

transit-delay <seconds> Configures the transit delay time for the OSPFinterface, the estimated time in seconds required totransmit a link-state update packet over theinterface.seconds is an integer 1–1,800.

tunnel-id Specifies the ID number of the tunnel in the range of1–2147477248.

Configuring OSPF on a tunnel


Deleting a tunnelDelete a configured tunnel to remove it from the configuration.

Procedure steps

Delete a tunnel by using the following command:

config ipv6 tunnel <tunnel ID> delete

Variable definitionsUse the data in the following table to use the config ipv6 tunnel delete command.

Variable Valuetunnel-id Specifies the ID number of the tunnel in the

range of 1–2147477248.



Chapter 22: IPv4-to-IPv6 transitionmechanism configuration usingthe ACLI

This section describes how to use the ACLI to configure IPv6 transition mechanisms, or tunnels. Forconceptual information about tunnels, see IPv6 routing fundamentals on page 15.


• You must configure the local and remote switches with IPv4 addresses that you canping.

• You must configure the local and remote switches with one or more of the followingprotocols to route IPv4 traffic: Static, RIP, or OSPF.


• Job aid: Roadmap of tunnel configuration ACLI commands on page 287

• Configuring manual tunnels on page 288


Job aid: Roadmap of tunnel configuration ACLIcommands

The following table lists the commands and their parameters that you use to complete theprocedures in this section.


Table 28: Job aid: Roadmap of tunnel configuration ACLI commands


ipv6 tunnel <tunnel id> source <A.B.C.D> address <ipv6 address/prefix-len> destination <A.B.C.D>

hop-limit <value>

OSPF Router Configuration mode

ipv6 tunnel <tunnel id> dead-interval <seconds>

enable


metric <value>


priority <value>


transmit-delay <seconds>

area <A.B.C.D> [dead-interval <seconds>][hello-interval <seconds>] [metric <value>][priority <value>] [retransmit-interval<seconds>] [transmit-delay <seconds>]

Configuring manual tunnelsCreate a tunnel to transfer traffic between IPv6 devices in an IPv4 network. Configure manualtunnels when you want to define both the local and destination addresses.

Use this procedure to configure the tunnel at both the source and destination addresses.

Prerequisites


Procedure steps

1. Configure the tunnel at the source and destination by using the following command:

IPv4-to-IPv6 transition mechanism configuration using the ACLI


ipv6 tunnel <tunnel id> source <A.B.C.D> address <ipv6address/prefix-len> destination <A.B.C.D>

2. Configure the hop limit by using the following command:

ipv6 tunnel <tunnel id> hop-limit <value>

Variable definitionsUse the data in the following table to use the ipv6 tunnel command.

Variable Valueaddress <ipv6 address/prefix-len> Configures the local address for the tunneled device

in IPv6/prefix-length format.

destination <A.B.C.D> Configures the address for the device that is tunneledto in IPv4 or IPv6/prefix-length format.

hop-limit <value> Configures the maximum number of hops that apacket can make before it is dropped.

value is in the range 0–255.

To set this option to the default value, use the defaultoperator with the command.The default value is 255.

source <A.B.C.D> Configures the address for the local device.

tunnel id Specifies the ID number of the tunnel in the range of1-5000.

Example of configuring manual tunnelsProcedure steps

1. Configure the tunnel at the source.

ERS-8606:5(config)# ipv6 tunnel 1044 source 20.10.10.107address 0100:0200:0300:0004:0005:0006:0000:aa01/80destination 10.20.20.105

2. Configure the tunnel at the destination.

ERS-8606:5(config)# ipv6 tunnel 1045 source 10.20.20.105address 0100:0200:0300:0004:0005:0006:0000:aa02/80destination 20.10.10.107

Configuring manual tunnels


Configuring OSPF on a tunnelConfigure OSPF on a VLAN or brouter tunnel to create a dynamic IPv6 tunnel on the OSPFinterface.

Prerequisites


Procedure steps

1. Configure OSPF on a tunnel by using the following command:

ipv6 tunnel <tunnel id> [dead-interval <seconds>] enable[hello-interval <seconds>] [metric <value>] [poll-interval<seconds>] [priority <value>] [retransmit-interval<seconds>] [transmit-delay <seconds>]

2. Configure the OSPF area for the tunnel by using the following command:

ipv6 tunnel <tunnel id> area <A.B.C.D> [dead-interval<seconds>] [hello-interval <seconds>] [metric <value>][priority <value>] [retransmit-interval <seconds>][transmit-delay <seconds>]

Variable definitionsUse the data in the following table to use the ipv6 tunnel command.

Variable Valuearea <A.B.C.D> Configures the area IP address (0.0.0.0 to

255.255.255.255) {a.b.c.d}.

dead-interval <seconds> Configures the OSPF dead interval for the interface.

seconds is the number of seconds the switch OSPFneighbors wait before determining that this OSPFrouter is down. The range is from 1-4095. This value



Variable Value

must be at least four times the hello interval value.The default is 40.

To set this option to the default value, use the defaultoperator with the command.

enable Configures the state (enabled or disabled) of theOSPF interface. To set this option to the default value,use the default operator with the command.

hello-interval <seconds> Configures the OSPF Hello interval for the interface.

seconds is the number of seconds between hellopackets sent on this interface. The range is 1–65535. The default is 10.



metric <value> Configures the OSPF metric for the interface. Theswitch advertises the metric in router linkadvertisements.

value is the range 0–65535.


poll-interval <seconds> Configures the polling interval for the OSPF interfacein seconds.

seconds is between 1–2 147 483 647.


priority <value> Configures the OSPF priority for the interface duringthe election process for the designated router. Theinterface with the highest priority number is thedesignated router. The interface with the second-highest priority becomes the backup designatedrouter. If the priority is 0, the interface cannot becomeeither the designated router or a backup. The priority

Configuring OSPF on a tunnel


Variable Valueis used only during election of the designated routerand backup designated router.

value is in the range 0–255. The default is 1.


retransmit-interval <seconds> Configures the retransmit interval for the OSPFinterface; the number of seconds between link-stateadvertisement retransmissions.

seconds is an integer between 1–1800.

To set this option to the default value, use thedefault operator with the command.The default value is 5.

transit-delay <seconds> Configures the transit delay time for the OSPFinterface, the estimated time in seconds required totransmit a link-state update packet over theinterface.

seconds is an integer between 1–1800.


tunnel-id Specifies the ID number of the tunnel in the range of1-5000.



Chapter 23: Multicast protocolconfiguration using EnterpriseDevice Manager

This chapter contains procedures to configure Multicast Listener Discovery (MLD).

MLD discovers devices soliciting multicast traffic to update multicast tables. This improves efficiency andsaves bandwidth; only devices that require multicast traffic receive it rather than every device on thenetwork.

For more information about MLD concepts, see IPv6 routing fundamentals on page 15.

Multicast protocol configuration proceduresThis task flow shows you the sequence of procedures you perform to configure multicastrouting protocols for IPv6.


Figure 17: Multicast protocol configuration procedures

Multicast protocol configuration navigation• Configuring a multicast router on page 294

• Configuring an MLD host on page 295

• Configuring an MLD router interface on page 295

• Viewing the MLD cache on page 298

Configuring a multicast routerConfigure a multicast router to enable Multicast Listening Discovery (MLD) on the router at achassis level.

Multicast protocol configuration using Enterprise Device Manager


Procedure steps

1. In the navigation tree, open the following folders: Configuration > Edit.2. Click Chassis.3. Click the Mcast Mlt Distribution tab.4. Select the Enable check box to enable multicast multilink trunk (MLT) routing.5. In the GrpMask box, type the group mask address in IPv4 format. The default is

255.255.255.255.6. In the SrcMask box, type the source mask address in IPv4 format. The default is

255.255.255.255.7. Select the RedistributeEnable check box to enable redistribution.8. Click Apply.

Configuring an MLD hostConfigure the switch as an MLD host to listen to multicast packets.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click MLD.3. Select the MulticastAdminStatus check box.4. Click Apply.

Variable definitionsUse the data in the following table to configure the MLD Globals tab.

Variable ValueMulticastAdminStatus Select to configure the switch as an MLD

host.

Configuring an MLD router interfaceConfigure MLD on a router interface to customize the MLD configuration.

Configuring an MLD host


Prerequisites

• Configure a multicast router.• Configure the switch as a multicast host.• Add an IPv6 interface ID to the port or VLAN, ensuring MulticastAdminStatus is true.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click MLD.3. Click the Interfaces tab.4. Edit the values as required.5. Click Apply.

Variable definitionsUse the data in the following table to use the MLD Interfaces tab.

Variable ValueIfIndex Configures a unique value identifying a physical

interface or a logical interface (VLAN).

Query Interval Configures the query interval in seconds. The range is0–65535. The default is 125.

Version Configures the version of MLD. The versions are 1 or2. The default is 1.

Querier Indicates the IPv6 address to query.

QueryMaxResponseDelay Configures the query maximum response time in 1/10of a second. The range is 0–65535. The default is10.

Joins Indicates the number of joins.

Groups Indicates the groups being listened to.

Robustness Configures the robustness value. The range is 0–65535. The default is 2.

LastListenQueryIntvl Configures the last member query interval in 1/10 of asecond. The range is 0–65535. The default is 1.

QuerierUpTime Indicates the amount of time that the querier isenabled.

QuerierExpiryTime Inidcates the expiry time for the querier.



Configuring an MLD router interface on a VLANConfigure MLD on a router interface to customize the MLD configuration.

Prerequisites

• Configure a multicast router.• Configure the switch as a multicast host.• Create a VLAN to use as the MLD router interface.• Add an IPv6 interface ID to the VLAN, ensuring MulticastAdminStatus is true.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > VLAN.2. Click VLANs.3. Click the Basic tab.4. Select a VLAN to configure.5. Click IPv6.6. Click the MLD Interfaces tab.7. Edit the values as required.8. Click Apply.

Variable definitionsUse the data in the following table to use the MLD Interfaces tab.

Variable ValueIfIndex Configures a unique value identifying a physical

interface or a logical interface (VLAN).

QueryInterval Configures the query interval in seconds. The range is0–65535. The default is 125.

Version Configures the version of MLD. The versions are 1 or2. The default is 1.

Querier Indicates the IPv6 address to query.

QueryMaxResponseDelay Configures the query maximum response time in 1/10of a second. The range is 0–65535. The default is10.

Configuring an MLD router interface on a VLAN


Variable ValueJoins Indicates the number of joins.

Groups Indicates the groups being listened to.

Robustness Configures the robustness value. The range is 0–65535. The default is 2.

LastListenQueryIntvl Configures the last member query interval in 1/10 of asecond. The range is 0–65535. The default is 1.

QuerierUpTime Indicates the amount of time that the querier isenabled.

QuerierExpiryTime Inidcates the expiry time for the querier.

Viewing the MLD cacheView the MLD cache to see IPv6 multicast groups for which members exist on an interface.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click MLD.3. Click the Cached tab.

Variable definitionsUse the data in the following table to use the MLD Cached tab.

Variable ValueAddress Displays the IPv6 address for the interface.

IfIndex Displays a unique value to identify a physical interface or alogical interface (VLAN).

Self Indicates if the local system is a member of the group addresson the current interface.

LastReporter Displays the source IPv6 address for the last receivedmembership report for the IPv6 multicast group address on thecurrent interface. If no membership report is received, the objectvalue is 0::0.

UpTime Indicates the duration of time that MLD is enabled.

ExpiryTime Indicates the expiry time.



Chapter 24: Multicast protocolconfiguration using the CLI

This chapter describes the procedures to configure Multicast Listener Discovery (MLD) on your AvayaEthernet Routing Switch 8800/8600.

MLD provides group management capabilities by allowing hosts to inform routers of membership statuswithin groups. MLD discovers the presence of multicast listeners on directly attached links. MLD providesthe necessary information to route multicast packets to routers requiring multicast traffic.





Multicast protocol configuration navigation• Job aid: Roadmap of IPv6 multicast CLI commands on page 301

• Enabling a multicast router on page 301

• Enabling a VLAN for multicast routing on page 302

• Configuring MLD on a VLAN on page 302

• Enabling multicasting on a brouter port on page 303

• Configuring MLD on a brouter port on page 304

Multicast protocol configuration using the CLI


Job aid: Roadmap of IPv6 multicast CLI commandsThe following table lists the commands and parameters that you use to perform the proceduresin this chapter.

Table 29: Job aid: Roadmap of IPv6 multicast CLI commands

Command Parameterconfig ethernet <ports> ipv6 mcast <enable|disable>

config ethernet <ports> ipv6 mld info

last-memb-query-int <seconds>

query-interval <seconds>

query-maxresp <1seconds>

robustval <integer>

version <1|2>

config ipv6 mcast <enable|disable> –

config vlan <vid> ipv6 mcast <enable|disable>

–

config vlan <vid> ipv6 mld info

last-memb-query-int <seconds>

query-interval <seconds>

query-maxresp <1seconds>

robustval <integer>

version <1|2>

Enabling a multicast routerEnable the router for multicast traffic to globally enable the MLD protocol.

Job aid: Roadmap of IPv6 multicast CLI commands


Procedure steps

Enable the multicast router by using the following command:

config ipv6 mcast <enable|disable>

Enabling a VLAN for multicast routingConfigure a VLAN for multicast traffic to enable MLD on the VLAN.

Procedure steps

Enable a VLAN for multicast routing by using the following command:

config vlan <vid> ipv6 mcast <enable|disable>

Variable definitionsUse the data in the following table to use the config vlan ipv6 mcast <enable|disable> command.

Variable Value<vid> Specifies a VLAN ID in the range of 1–

4094.

Configuring MLD on a VLANConfigure MLD on a VLAN to customize the configuration.

Procedure steps

Configure MLD by using the following command:



config vlan <vid> ipv6 mld

Variable definitionsUse the data in the following table to use the config vlan ipv6 mld command.

Variable Valueinfo Displays the current VLAN MLD configuration

setting.

last-memb-query-int <seconds> Configures the query interval time in 1/10 of a secondfor the last member.seconds is in the range 0–65535.

query-interval <seconds> Configures the query interval time in 1/10 of asecond.seconds is in the range 0–65535.

query-maxresp <1seconds> The maximum query response time advertised in MLDqueries on this interface.seconds is in the range 0–65535.

robustval <integer> Configures the robustness value.integer is in the range 0–65535.

version <1|2> Configures the version of MLD to version 1 or version2.

<vid> Specifies a VLAN ID in the range of 1–4094.

Enabling multicasting on a brouter portConfigure multicasting on a brouter port to enable MLD on the port.

Procedure steps

Enable multicasting by using the following command:

Enabling multicasting on a brouter port


config ethernet <ports> ipv6 mcast <enable|disable>

Variable definitionsUse the data in the following table to use the config ethernet ipv6 mcast command.

Variable Valueports Specifies a port/slot or a port list.

Configuring MLD on a brouter portConfigure MLD on a brouter port to customize the configuration.

Procedure steps


config ethernet <ports> ipv6 mld

Variable definitionsUse the data in the following table to use the config ethernet ipv6 mld command.

Variable Valueinfo Displays the current brouter port MLD configuration

setting.

last-memb-query-int <seconds> Configures the query interval time in 1/10 of a secondfor the last member.seconds is in the range 0–65535.

ports Specifies a port/slot or a port list.

query-interval <seconds> Configures the query interval time in 1/10 of asecond.seconds is in the range 0–65535.

query-maxresp <1seconds> The maximum query response time advertised in MLDqueries on this interface.seconds is in the range 0–65535.



Variable Valuerobustval <integer> Configures the robustness value.

integer is in the range 0–65535.

version <1|2> Configures the version of MLD to version 1 or version2.

Configuring MLD on a brouter port




Chapter 25: Multicast protocolconfiguration using the ACLI

This chapter describes the procedures used to configure Multicast Listener Discovery (MLD) on yourAvaya Ethernet Routing Switch 8800/8600.

MLD provides group management capabilities by allowing hosts to inform routers of membership statuswithin groups. MLD discovers the presence of multicast listeners on directly attached links. MLD providesthe necessary information to route multicast packets to routers requiring multicast traffic.





Multicast protocol configuration navigation• Job aid: Roadmap of IPv6 multicast ACLI commands on page 309

• Enabling a multicast router on page 309

• Enabling a VLAN for multicast routing on page 310

• Configuring MLD on a VLAN on page 310

• Enabling multicasting on a brouter port on page 312

• Configuring MLD on a brouter port on page 312

Multicast protocol configuration using the ACLI


Job aid: Roadmap of IPv6 multicast ACLI commandsThe following table lists the commands and parameters that you use to perform the proceduresin this chapter.

Table 30: Job aid: Roadmap of IPv6 multicast ACLI commands


ipv6 multicast-routing –


ipv6 interface multicast-routing mtu <bytes>

reachable-time <value>

retransmit-timer <value>

ipv6 mld last-memb-query-int <value>

query-interval <value>

query-max-response-time <value>

robustval <value>

version <1|2>

Enabling a multicast routerEnable the router for multicast traffic to globally enable MLD.

Prerequisites


Procedure steps

Enable the multicast router by using the following command:

Job aid: Roadmap of IPv6 multicast ACLI commands


ipv6 multicast-routing

Enabling a VLAN for multicast routingConfigure a VLAN for multicast traffic to enable MLD on the VLAN.

Prerequisites


Procedure steps

Enable a VLAN for multicast routing by using the following command:

ipv6 interface multicast-routing [reachable-time <value>][retransmit-timer <value>]

Variable definitionsUse the data in the following table to use the ipv6 interface multicast-routingcommand.

Variable Valuereachable-time <value> Configures the reachable time, in

milliseconds, for the interface. The range is0–3600000.

retransmit-timer <value> Configures the time between attempts totransmit multicast packets, in milliseconds,for the interface. The range is 0–3600000.

Configuring MLD on a VLANConfigure MLD on a VLAN to customize the configuration.



Prerequisites


Procedure steps


ipv6 mld [last-memb-query-int <value>] [query-interval <value>][query-max-response-time <value>] [robustval <value>] [version<1|2>]

Variable definitionsUse the data in the following table to use the ipv6 mld command.

Variable Valuelast-memb-query-int <value> Configures the query interval time in 1/10 of a second

for the last member.value is in the range 0–65535.The default value is 1.

query-interval <value> Configures the maximum query response timeadvertised in MLD queries on this interface.value is in the range 0–65535.The default value is 125.

query-max-response-time <value> Configures the query interval time in 1/10 of a secondfor the last member.value is in the range 0–65535.The default value is 10.

robustval <value> Configures the robustness value.value is in the range 0–65535.The default value is 2.

version <1|2> Configures the version of MLD to version 1 or version2.The default value is 1.

Configuring MLD on a VLAN


Enabling multicasting on a brouter portConfigure multicasting on a brouter port to enable MLD on the port.

Prerequisites


Procedure steps

Enable multicasting by using the following command:

ipv6 interface multicast-routing [reachable-time <value>][retransmit-timer <value>]

Variable definitionsUse the data in the following table to use the ipv6 interface multicast-routingcommand.

Variable Valuereachable-time <value> Configures the reachable time, in

milliseconds, for the interface. The range is–03600000.

retransmit-timer <value> Configures the time between attempts totransmit multicast packets, in milliseconds,for the interface. The range is 0–3600000.

Configuring MLD on a brouter portConfigure MLD on a brouter port to customize the configuration.



Prerequisites


Procedure steps


ipv6 mld [last-memb-query-int <value>] [query-interval <value>][query-max-response-time <value>] [robustval <value>] [version<1|2>]

Variable definitionsUse the data in the following table to use the ipv6 mld command.

Variable Valuelast-memb-query-int <value> Configures the query interval time in 1/10 of a second

for the last member.value is in the range 0–65535.The default value is 1.

query-interval <value> Configures the query interval time in 1/10 of asecond.value is in the range 0–65535.The default value is 125.

query-max-response-time <value> Configures the maximum query response timeadvertised in MLD queries on this interface.value is in the range 0–65535.The default value is 10.

robustval <value> Configures the robustness value.value is in the range 0–65535.The default value is 2.

version <1|2> Configures the version of MLD to version 1 or version2.The default value is 1.

Configuring MLD on a brouter port




Chapter 26: IPv6 traffic filter configurationusing Enterprise DeviceManager

This chapter describes how to configure and manage traffic filters for R, RS, and 8800 modules on theAvaya Ethernet Routing Switch 8800/8600 with Enterprise Device Manager. Specifically, it providesconfiguration instructions for advanced filtering features using the appropriate options under Security, DataPath, Advanced Filters (ACE/ACLs ) on the main Enterprise Device Manager menu. For conceptualinformation about IP filters, see IPv6 routing fundamentals on page 15.

For additional information about IPv4 filters, see Avaya Ethernet Routing Switch 8800/8600 Configuration— QoS and IP Filtering, NN46205-507.

This module describes how to use Enterprise Device Manager to configure and manage traffic filters onthe Avaya Ethernet Routing Switch 8800/8600. Specifically, it provides configuration instructions foradvanced filtering features using that option under Security on the main Enterprise Device Managermenu.

IPv6 traffic filter configuration navigation• Configuring an ACT on page 316

• Modifying ACT attributes on page 317

• Inserting a pattern in an ACT on page 318

• Inserting an ACL on page 319

• Modifying an ACL on page 321

• Inserting ACE common entries on page 322

• Modifying ACE common entries on page 324

• Configuring a list of IPv6 source IP addresses for an ACE on page 324

• Configuring a list of IPv6 destination IP addresses for an ACE on page 326

• Configuring an IPv6 next header rule for an ACE on page 327

• Deleting an ACT on page 328

• Deleting an ACL on page 328

• Deleting ACE common entries on page 328


Configuring an ACTConfigure an access control template (ACT) to create, delete, apply, or specify attributes. Afteryou apply the ACT you cannot change the attributes. ACT IDs 4001 to 4096 are reserved forsystem-defined ACTs.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > Security > DataPath.

2. Click Advanced Filters (ACE/ACLs).3. Click Insert to add a new ACT.4. Select the required IPv6 attributes.5. Click Insert.

Variable definitionsUse the data in the following table to configure an ACT.

Variable ValueActId Specifies a unique identifier for the ACT. The

range is 1–4096.

Name Specifies a descriptive user-defined namefor the ACT entry.

ArpAttrs Specifies one of the following ARP attributes:

• none

• operation (This is the only valid option forARP attributes.)

Important:ArpAttrs is not a supported for IPv6filters.

EthernetAttrs Specifies one or more of the followingEthernet attributes:

• none

• srcMac

• dstMac

• etherType

IPv6 traffic filter configuration using Enterprise Device Manager


Variable Value

• port

• vlan

• vlanTagPrio

IpAttrs Specifies one or more of the following IPattributes:

• none

• scrip

• dstip

• ipFragFlag

• ipOptions

• ipProtoType

• dscp

ProtocolAttrs Specifies one or more of the followingprotocol attributes:

• none

• tcpSrcPort

• udpSrcPort

• tcpDstPort

• udpDstport

• tcpFlags

• icmpMsgFlags

IPv6Attrs Specifies one or more of the following IPv6attributes:

• none

• srcIpv6

• dstIpv6

• NextHdr

Modifying ACT attributesModify ACT attributes to change the configuration.

Modifying ACT attributes


Procedure steps


2. Click Advanced Filters (ACE/ACLs).3. Click the required attribute field on the ACT tab.4. Select the required options.5. Click OK to apply the required attributes.6. In the Apply column for the modified entry, ensure that True is selected.7. Click Apply.

The specified attributes field on the ACT tab updates.

Important:You can only modify an ACT once. If you require further modifications, delete the entry andcreate a new ACT with the required attributes.

Inserting a pattern in an ACTInsert a pattern in an ACT to apply the template.

Procedure steps


2. Click Advanced Filters (ACE/ACLs).3. Select the ACT in which to insert a pattern.4. Click the Pattern button.5. Click Insert.

Important:An ACT uses IPv4 or IPv6 attributes, but not both. You cannot combine IPv4 andIPv6 attributes in the same ACL.

6. Select the required options in the dialog box.7. Click Insert.

Variable definitionsUse the data in the following table to configure the Pattern tab.



Variable ValueActId Specifies a unique identifier for the ACT. The range is 1–4096.

Index Index identifier.

Name Specifies a descriptive, user-defined name for the ACL pattern entry.

Base Specifies one of the following as the user-defined header for the accesscontrol entries (ACE) of the ACL.

• none

• macSrcBegin

• ipHdrBegin

• ipTosBegin

• ipDstBegin

• tcpDstportBegin

• udpSrcportBegin

• ipHdrEnd

• updEnd

• etherBegin

• ethTypeLenBegin

• ipOptionsBegin

• ipProtoBegin

• tcpBegin

• tcpFlagsEnd

• udpDstportBegin

• icmpMsgBegin

• ipv6HdrBegin

• macDstBegin

• arpBegin

• ipPayloadBegin

• ipSrcBegin

• tcpSrcportBegin

• udpBegin

• etherEnd

• tcpEnd

Offset Set the offset in bits to the beginning offset of the user-defined field withthe selected header option as a base. Valid values range from 0–76800.

Length Configures the number of bits to extract from the beginning of the offset.Valid values range from 1–56.

Inserting an ACLAn ACL comprises an ordered list of filter rules or ACEs. The ACEs provide specific actionsthat you configure. After you configure an ACE, when a packet meets the match criteriaspecified in one or more ACEs within an ACL, the corresponding action runs.

Important:If you configured any IPv6 attributes on the ACT, you must select IPv6 in the PktType fieldwhen you insert the ACL. If an ACT uses only Ethernet attributes, you can configure a singleIPv4 ACL and a single IPv6 ACL.

Procedure steps


2. Click Advanced Filters (ACE/ACLs).3. Click the ACL tab.

Inserting an ACL


4. Click Insert.5. Type an ACL ID from 1 through 4096.6. Select the act ID by clicking the ellipsis button (...).7. Click OK.8. Specify the ACL type.9. Type a name for the ACL entry.

10. In the VlanList box, click the button and select the required entry.11. In the PortList box, click the button and select the required entry.12. Specify the DefaultAction and the GlobalAction.13. Enable or disable the state.14. In the PktType box, select the IPv6 option.15. Click Insert.

Variable definitionsUse the data in the following table to configure the ACL.

Variable ValueAclId Specifies a unique identifier for the ACL entry in the range

1–4096.

ActId Specifies a unique identifier for the ACT entry in the range1–4096.

Type Specifies whether the ACL is VLAN or port-based. Validoptions:

• inVlan

• outVlan

• inPort

• outPort

Important:The inVlan and outVlan ACL types drop packets if theVLAN is added after ACE creation. For VLAN-basedfilters, ensure that the ACE configuration is set to all R,RS, 8800 module slots, regardless of the VLAN portmembership on a slot.

Name Specifies a descriptive user-defined name for the ACLentry.



Variable ValueVlanList Identifies an array indicating all the VLANs associated with

the ACL entry. The value is used only with inVlan andoutVlan ACL types.

PortList Specifies the ports added to the ACL entry. The value isused only with inPort and outPort ACL types.

DefaultAction Specifies the action taken when no ACEs in the ACL match.Valid options are deny and permit, with permit as thedefault.

GlobalAction Indicates the action applied to all ACEs that match in anACL:

• none

• mirror

• count

• mirror-count

Important:Mirroring is not supported for egress filters in the AvayaEthernet Routing Switch 8800/8600 Release 4.1software.

State Enables or disables all of the ACEs in the ACL. The defaultvalue is enable.

PktType Specifies if the packet type is IPv4 or IPv6.

Modifying an ACLModify an ACL to change the configuration.

Procedure steps


2. Click Advanced Filters (ACE/ACLs).3. Click the ACL tab.4. Click the field you want to change.

For example, if you click the GlobalAction field, you can select from several optionsin the activated list.

Modifying an ACL


5. Select the required option.6. Click Apply to commit the required action.

Inserting ACE common entriesInsert access control entries (ACE) to add an ACE to an ACL.

Procedure steps


2. Click Advanced Filters (ACE/ACLs).3. Click the ACL tab.4. Select the ACL to which to add an ACE.5. Click the ACE button.6. Click Insert.7. Type data in the required fields.8. Click Insert.

Variable definitionsUse the data in the following table to configure the ACE.

Variable ValueAceId Specifies a unique identifier and priority for the ACE.

Name Specifies a descriptive, user-defined name for theACE entry. The system automatically assigns a nameif you do not choose one.

Mode Indicates the operating mode associated with theACE. Valid options are deny and permit, with none asthe default.

MltIndex Specifies whether to override the MLT index picked bythe MLT algorithm when a packet is sent on MLT ports.Valid values range 0–8, with 0 as the default.

RemarkDscp Specifies whether the Differentiated Services CodePoint (DSCP) field value marks non standard trafficclasses and local use Per Hop Behavior (PHB). Thedefault is disable.



Variable ValueRemarkDot1Priority Specifies whether Dot1 Priority as described by Layer

2 standards, 802.1Q, and 802.1P is enabled. Thedefault is disable.

Police Configures the desired policing profile identifier. Validvalues range from 0–16383, with zero (0) as thedefault. When policing is not desired, you mustconfigure the value to zero.

RedirectNextHop Redirects matching IP traffic to the next hop.

RedirectUnreach Configures the desired behavior for redirected trafficin case the specified next hop is not reachable. Thedefault value is deny.

EgressQueue Specifies the egress queue for 10/100 GbE module.

• If you specify only 1 value, then this value is appliedto the 1 Gb and 10 Gb queues as well.

• If you specify 2 values, then the first value is appliedto the 10/100 module and the second value isapplied to 1 Gb and 10 Gb modules.

• If you specify all three values, then all three valuesapply respectively to the appropriate egressqueue.

• If you specify a value greater than 8, it is not appliedto the 10/100 GbE module because it uses only 8queues. However, the value is applied only to the 1Gb and 10 Gb module types. The default value is64.

EgressQueue1g Specifies the egress queue for the 1 Gb module. Thedefault value is 64.

EgressQueue10g Specifies the egress queue for the 10 Gb module. Thedefault value is 64.

EgressQueueNSC Identifies the configured ACE Networks Service Class(NSC). The default is disable.

StopOnMatch Indicates whether to stop or continue if an ACEmatching the packet is found. When a match occurs,the switch does not attempt a match on the other ACEswith a lower priority.

Flags Specifies one of the following flag values:

• none: Default value for the flags.

• count: Enables or disables counting if a packetmatching the ACE is found.

• copyToPrimaryCp: Enables or disables the copyingof matching packets to the primary CP.

Inserting ACE common entries


Variable Value

• copyToSecondaryCp: Enables or disables thecopying of matching packets to the secondary CP.

• mirror: Enables or disables mirroring the matchingpackets to an interface. The Avaya Ethernet RoutingSwitch 8800/8600 mirrors one port or mirrors to oneport.

IPfixState Enables or disables IP flow information export (IPfix).

RedirectNextHopIpv6 The IPv6 address to redirect the next hop.

Modifying ACE common entriesModify ACE common entries to change the current configuration.

Important:Except the debug actions, disable the AdminState of the ACE before you perform anymodifications.

Procedure steps


2. Click Advanced Filters (ACE/ACLs).3. Click the ACL tab.4. Select the ACL.5. Click the ACE button.6. Click a field you want to change.

For example, if you click on the Mode field, you can select from several options inthe activated list.

7. Select the required option.8. Click Apply to commit the action.

Configuring a list of IPv6 source IP addresses for an ACEConfigure an ACE IPv6 source address so that the filter looks for a specific IPv6 sourceaddress.



Prerequisites

• The associated ACL packet type must be IPv6.• The associated ACT IPv6 attributes must be srcIpv6

Procedure steps


2. Click Advanced Filters (ACE/ACLs).3. Click the ACL tab.4. Select an IPv6 ACL.5. Click ACE.6. From the ACE Common tab, select an ACE.7. ClickIPv6.8. Click Insert.9. Specify the operation (the only option is eq [equals]) and the IPv6 addresses.

10. Click Insert.

Variable definitionsUse the data in the following table to configure the Source Address tab.

Variable ValueAclId Specifies the ACL ID.

AceId Specifies the ACE ID.

Oper Specifies the ACE operation. The only option is eq(equals).

List Specifies the IPv6 addresses—a binary string of 16octets in network byte-order. Enter a single IPv6address, range of IPv6 addresses, or multiple IPv6addresses.

Configuring a list of IPv6 source IP addresses for an ACE


Configuring a list of IPv6 destination IP addresses for anACE

Configure an ACE IPv6 destination address to have the filter look for a specific IPv6 destinationaddress.

Prerequisites

• The associated ACL packet type must be IPv6.• The associated ACT IPv6 attributes must be dstIpv6.

Procedure steps


2. Click Advanced Filters (ACE/ACLs).3. Click the ACL tab.4. Select an IPv6 ACL.5. Click ACE.6. From the ACE Common tab, select an ACE.7. ClickIPv6.8. Click the Destination Address tab.9. Click Insert.

10. Specify the operation (the only option is eq [equals]) and the IPv6 addresses.11. Click Insert.

Variable definitionsUse the data in the following table to configure the Destination Address tab.



Oper Select eq to specify IPv6 addresses equal to the addressesincluded in the List field.

List Type a single IPv6 address, range of IPv6 addresses, ormultiple IPv6 addresses.



Configuring an IPv6 next header rule for an ACEConfigure an ACE IPv6 next header so that the filter looks for a packets with the next headerparameter set.

Prerequisites

• The associated ACL packet type must be IPv6.• The associated ACT IPv6 attributes must be nxtHdr.

Procedure steps


2. Click Advanced Filters (ACE/ACLs).3. Click the ACL tab.

The ACL box appears with the ACL tab displayed.4. Select an IPv6 ACL.5. Click ACE.6. Select an ACE.7. ClickIPv6.8. Click the Next Hdr tab.9. Click Insert.

10. Specify the operation and the Next header parameters.11. Click Insert.

Variable definitionsUse the data in the following table to configure the next header rule.



Oper Specifies the ACE operation. The options are eq(equal) or ne (not equal).

NxtHdr Specifies the next header. .

Configuring an IPv6 next header rule for an ACE


Deleting an ACTDelete an ACT to remove it from the configuration.

Important:You cannot delete or modify an ACT associated with ACLS.

Procedure steps


2. Click Advanced Filters (ACE/ACLs).3. Select the ActId or name of the ACT to delete.4. Click Delete.

Deleting an ACLDelete an ACL to remove it from the configuration.

Procedure steps


2. Click Advanced Filters (ACE/ACLs).3. Click the ACL tab.4. Select the ACL to delete.5. Click Delete to remove the selected ACL.

A dialog box prompts you to confirm the deletion.6. Click Yes to delete the ACL.

Deleting ACE common entriesDelete ACE common entries to remove them from the configuration.



Procedure steps


2. Click Advanced Filters (ACE/ACLs).3. Click the ACL tab.4. Select the ACL.5. Click the ACE button.6. Select the name of the ACE common entry to delete.7. Click Delete to remove the selected entry.

Deleting ACE common entries




Chapter 27: IPv6 traffic filter configurationusing the CLI

This chapter describes how to block unwanted traffic from entering a switch or to prioritize desired traffic.Traffic filters instruct an interface to selectively handle specified traffic. The switch determines whichpackets receive special handling based on information in the packet headers.

Using traffic filters, you can reduce network congestion and control access to network resources byblocking, forwarding, or prioritizing specified traffic on an interface. You can apply multiple traffic filters toa single interface.

For conceptual information about traffic filtering, see IPv6 routing fundamentals on page 15.

For additional information about filters, see Avaya Ethernet Routing Switch 8800/8600 Configuration —QoS and IP Filtering, NN46205-507 .

IPv6 traffic filter configuration navigation• Job aid: Roadmap of traffic filter CLI commands on page 331

• Configuring ACTs on page 333

• Creating a template for user-created patterns on page 335

• Applying the ACT on page 337

• Configuring ACLs on page 337

• Configuring global and default actions for an ACL on page 338

• Associating VLANs for an ACL on page 339

• Associating ports for an ACL on page 340

• Adding an ACE with IPv6 header attributes on page 341

Job aid: Roadmap of traffic filter CLI commandsThe following table lists the commands and parameters that you use to perform the proceduresin this chapter.


Table 31: Job aid: Roadmap of traffic filter CLI commands

Command Parameterconfig filter acl <acl-id> create <type> act <value> [pktType] <value>

[name <value>]

delete

enable

disable

name <value>

info

config filter acl <acl-id> ace <ace-id> create [name <value>]

delete

enable

disable

name <value>

info

config filter acl <acl-id> ace <ace-id>advanced

custom-filter1<pattern1-name><ace-op><value>



delete

config filter acl <acl-id> ace <ace-id> ipv6 delete <ipv6-attributes>

dst-ipv6 <ace-op> <dst-ipv6-list>

info

src-ipv6 <ace-op> <src-ipv6-list>

nxt-hdr <ace-op> <nxt-hdr>

config filter acl <acl-id> port add <ports>

remove <ports>

info

config filter acl <acl-id> set default-action <value>

global-action <value>

info

IPv6 traffic filter configuration using the CLI


Command Parameterconfig filter acl <acl-id> vlan add <vid> [<vid2-vid3>]

remove <vid> [<vid2-vid3>]

info

config filter act <act-id> create [name <value>]

delete

apply

name <value>

info

arp <arp-attributes>

ip <ip-attributes>

ipv6 <ipv6-attributes>

ethernet <ethernet-attributes>

protocol <protocol-attributes>

config filter act <act-id> pattern <pattern-name>

add <base> <offset> <length>

name <pattern-name>

info

Configuring ACTsConfigure an access control template (ACT) to create, delete, apply, and specify attributes.After you apply the ACT you cannot change the attributes. ACT IDs 4001 to 4096 are reservedfor system-defined ACTs.

System-defined ACTs are available for filters as required.

Important:An ACT can use IPv4 or IPv6 attributes, but not both. You cannot combine IPv4 and IPv6attributes in the same ACL.

Procedure steps

Configure an ACT by using the following command:

Configuring ACTs


config filter act <act-id>

Variable definitionsUse the data in the following table to use the config filter act command.

Variable Valueact-id Specifies an ACT ID in the range 1–4096.

apply Applies or commits the ACT. After the switch issuesthe command, you can make changes to the ACT onlyby first deleting it if no ACLs are associated with theACT.

arp <arp-attributes> Specifies the permitted ARP attributes for the ACTtemplate. The list of allowed attributes must beseparated by commas and includes,[none | operation]

create [name <value> ] Creates an ACT. Name <value> is an optionalparameter that specifies a descriptive name for theACT using 0–32 characters. If you do not enter aname, a default name is generated, for example,ACT-1 for act-id = 1.

Important:In the Avaya Ethernet Routing Switch 8800/8600,act-id acts as an index to the ACT table. Thus, youcan change the name at any time, even after youapply it.

delete Deletes an ACT only when no ACLs are associatedwith the ACT.

ethernet <ethernet-attributes> Specifies the permitted Ethernet attributes for the ACTtemplate. The list of allowed attributes must beseparated by commas and includes,[none | srcMac, dstMac, etherType, [portvlan],vlanTagPrio].

Important:

1. You can select port or vlan-id, but not both.2. If you select none,

• The entry deletes the Ethernet node.• The entry prevents you from selecting any

other attribute choices.

info Information about the ACTs that you created.



Variable Valueip <ip-attributes> Specifies the permitted IP attributes for the ACT

template. The list of allowed attributes must beseparated by commas and includes,[none | srcIp, dstIp, ipFragFlag, ipOptions,ipProtoType, dscp].

ipv6 <ipv6-attributes> Specifies the permitted IPv6 for the ACT template. Thelist of allowed attributes must be separated bycommas and includes,[none | srcIpv6, dstIpv6, nextHdr]

name <value> Specifies a name for the ACT. <value> is an optionalparameter that specifies a name for the ACT using 0–32 characters.

protocol <protocol-attributes> Specifies the permitted protocol attributes for the ACTtemplate. The list of allowed attributes must beseparated by commas and includes,[none | tcpSrcPort, udpSrcPort, tcpDstPort,udpDstPort, tcpFlags, icmpMsgFlags]

Creating a template for user-created patternsCreate a template for patterns within an ACT. You can associate a maximum of three patternswith an ACT.

Procedure steps

Create a template by using the following command:

config filter act <act-id> pattern <pattern-name>

Variable definitionsUse the data in the following table to use the config filter act pattern command.

Variable Valueact-id Specifies an ACT ID in the range of 1–4096.

add <base> <offset><length>

Adds a template for patterns you create. Options include:

Creating a template for user-created patterns


Variable Value

• base: the base and the offset together determine thebeginning of the pattern. Permitted values for the base includethe following:

- ether-begin

- mac-dst-begin

- mac-src-begin

- ethTypeLen-begin

- arp-begin

- ip-hdr-begin

- ip-options-begin

- ip-payload-begin

- ip-tos-begin

- ip-proto-begin

- ip-src-begin

- ip-dst-begin

- ipv6-hdr-begin

- tcp-begin

- tcp-srcport-begin

- tcp-dstport-begin

- tcp-flags-end

- udp-begin

- udp-srcport-begin

- udp-dstport-begin

- ether-end

- ip-hdr-end

- icmp-msg-begin

- tcp-end

- udp-end

• offset: the number of bits from the base where the patternstarts.

• length: the length in bits of the user-defined field from 1–56.

info Displays information about the template patterns you createdunder an ACT.



Variable Valuename <pattern-name> Renames the pattern with a new name that you define. Each of

the three patterns must use a unique name.

pattername Specifies a pattern name with a range 0–32 characters.

Applying the ACTAfter you create and configure the ACT, apply it to implement the configuration.

Procedure steps

Apply the ACT by using the following command:

configure filter act <act id> apply

Configuring ACLsConfigure access control lists (ACL) to create lists of rules for the ACT.

Important:If the ACT contains IPv6 attributes, you must configure an ACL of pktType IPv6. If the ACTuses only Ethernet attributes, you can configure one ACL of pktType IPv4 and an ACL ofpktType IPv6.

Procedure steps

Configure an ACL by using the following command:

config filter acl <acl-id>

Variable definitionsUse the data in the following table to use the config filter acl command.

Applying the ACT


Variable Valueacl-id Specifies an ACL ID in the range 1–4096.

create <type> act <value>[pktType] <value> [name <value> ]

Creates an access control list (ACL) only when anACT is associated with that ACL:

• <type>: type of ACL, including [InVlan | outVlan |InPort | outPort].

• act <value>: an ACT template ID in the range from1–4096.

• pktType <value>: ipv4 or ipv6

• name <value>: an optional parameter that specifiesa descriptive name for the ACL using 0–31characters. If you do not enter a name when youcreate the ACL, a default name is generated, forexample, ACL-2 for acl-id = 2

Important:The pktType field is optional for IPv4 traffic filters. Itis required if you apply the ACL to IPv6 packets.

delete Deletes an ACL.

Important:This command removes all VLANs or brouter portsunder this ACL and deletes all ACEs. Thecommand does not delete the ACTs.

disable Disables the ACL state along with all of the ACEsbelow it. The default value is disable.

enable Enables the ACL state along with all of the ACEsbelow it.Enable is the default state for the ACL.

info Displays information about the ACL.

name <value> Renames an ACL.

Configuring global and default actions for an ACLConfigure global and default actions for an ACL to apply the configuration globally.



Procedure steps

Configure global and default actions by using the following command:

config filter acl <acl-id> set

Variable definitionsUse the data in the following table to use the config filter acl set command.

Variable Valueacl-id Specifies an ACL ID in the range of 1–4096.

default-action <value> Specifies the default action when no ACEs match.Permitted options include [deny | permit], with a defaultof permit.

global-action <value> Specifies the global action for the matching ACEs.Permitted options include [none | mirror | count |mirror-count|ipfix|mirror-ipfix|count-ipfix|mirror-count-ipfix]. The default is none.

info Displays the status of the global and default actions.

Associating VLANs for an ACLAssociate or remove VLANs for a particular ACL.

Procedure steps

Associate or remove VLANs by using the following command:

config filter acl <acl-id> vlan

Variable definitionsUse the data in the following table to use the config filter acl vlan command.

Associating VLANs for an ACL



add <vid> [ <vid2-vid3>] Associates a VLAN or a VLAN list with a particularACL. <vid> is a list of VLANs separated by a commaor a range of VLANs specified as low-high [vlan-id -vlan-id].

info Displays the ACL VLAN status.

remove <vid> [ <vid2-vid3> ] Removes a VLAN or VLAN list from a particular ACL.<vid> is a list of VLANs separated by a comma or arange of VLANs specified as low-high [vlan-id -vlan-id].

Associating ports for an ACLAssociate or remove ports for a particular ACL.

Procedure steps

Associate or remove ports by using the following command:

config filter acl <acl-id> port

Variable definitionsUse the data in the following table to use the config filter acl port command.


add <ports> ] Associates a port or a port list with a particular ACL.<ports> is a list of ports separated by a comma or arange of ports specified as low-high [slot/port-slot/port].

info Displays the ACL port status.

remove <ports> Removes a port or a port list from a particular ACL.<ports> is a list of ports separated by a comma or arange of ports specified as low-high [slot/port-slot/port].



Adding an ACE with IPv6 header attributesAdd an ACE with IP header attributes as match criteria.

Important:Be aware of the following:

• You cannot select (*) after <ace-op>.• If you select no entry, You delete the Ethernet, ARP, or IPv6 protocol node.

Procedure steps

Add an ACE with IPv6 header attributes by using the following command:

config filter acl <acl-id> ace <ace-id> ipv6

Variable definitionsUse the data in the following table to use the config filter acl ace ipv6 command.

Variable Valueace-id Specifies an ACE ID in the range 1–1000.

acl-id Specifies an ACL ID in the range 1–4096.

delete <ipv6-attributes> Deletes the specified IPv6 ACE attributes.

dst-ipv6 <ace-op> <dst-ipv6-list> Specifies the following:

• an operator for a field match condition (eq)

• the list of destination IPv6 addresses separated bycommas

info Displays the current level parameter setting and thenext level directories.

nxt-hdr <ace-op> <nxt-hdr> Specifies the following:

• an operator for a field match condition (eq | ne)

• the next header value

src-ipv6 <ace-op> <src-ipv6-list> Specifies the following:

Adding an ACE with IPv6 header attributes


Variable Value

• an operator for a field match condition (eq)

• the list of source IPv6 addresses separated bycommas



Chapter 28: IPv6 traffic filter configurationusing the ACLI

This chapter describes how to block unwanted traffic from entering a switch or to prioritize desired traffic.Traffic filters instruct an interface to selectively handle specified traffic. The switch determines whichpackets receive special handling based on information in the packet headers.

Using traffic filters, you can reduce network congestion and control access to network resources byblocking, forwarding, or prioritizing specified traffic on an interface. You can apply multiple traffic filters toa single interface.

For conceptual information about traffic filtering, see IPv6 routing fundamentals on page 15.

For additional information about filters, see Avaya Ethernet Routing Switch 8800/8600 Configuration —QoS and IP Filtering, NN46205-507.

IPv6 traffic filter configuration navigation• Job aid: Roadmap of traffic filter ACLI commands on page 343

• Configuring ACTs on page 344

• Creating a template for user-created patterns on page 346

• Applying the ACT on page 348

• Configuring ACLs on page 349

• Configuring global and default actions for an ACL on page 350

• Associating VLANs for an ACL on page 351

• Associating ports for an ACL on page 352

• Adding an ACE with IPv6 header attributes on page 352

Job aid: Roadmap of traffic filter ACLI commandsThe following table lists the commands and parameters that you use to perform the proceduresin this chapter.


Table 32: Job aid: Roadmap of traffic filter ACLI commands

Command ParameterPrivileged EXEC mode

filter apply act <act-id> –

Global Configuration mode

filter acl <acl-id> enable

name <word>

type <inVlan|outVlan|inPort|outPort>

act <act-id>

pktType <ipv4|ipv6>

filter acl ace ipv6 <acl-id> <ace-id> dst-ipv6 eq <word>

nxt-hdr <eq|ne> <next-header>

src-ipv6 eq <word>

filter acl port <acl-id> <port> –

filter acl set <acl-id> default-action <value>

global-action <value>

filter acl vlan <acl-id> <vlan-id> –

filter act <act-id> arp <operation>

ethernet <word>

ip <word>

ipv6 <word>

name <word>

protocol <word>

filter act pattern <act-id> <word>

<base> <offset> <length>

name <pattern-name>

Configuring ACTsConfigure an access control template (ACT) to create, delete, apply, and specify attributes.After you apply the ACT you cannot change the attributes. ACT IDs 4001 to 4096 are reservedfor system-defined ACTs.

IPv6 traffic filter configuration using the ACLI


System-defined ACTs are available for filters as required.

Important:An ACT can use IPv4 or IPv6 attributes, but not both. You cannot combine IPv4 and IPv6attributes in the same ACL.

Prerequisites


Procedure steps

1. Create an ACT by assigning it an ID by using the following command:

filter act <act-id>2. Configure parameters for the ACT by using the following command:

filter act <act-id> [arp <operation>] [ethernet <word>] [ip<word>] [ipv6 <word>] [name <word>] [protocol <word>]

Variable definitionsUse the data in the following table to use the filter act command.

Variable Valueact-id Specifies an ACT ID in the range 1–4096.

Important:In the Avaya Ethernet Routing Switch 8800/8600,act-id is an index to the ACT table. Thus, you canchange the name at any time, even after you applyit.


arp <operation> Specifies the permitted ARP attributes for the ACTtemplate. The list of allowed attributes must beseparated by commas and includes:[operation]

ethernet <word> Specifies the permitted Ethernet attributes for the ACTtemplate. The list of allowed attributes must beseparated by commas and includes:

Configuring ACTs


Variable Value[none | srcMac, dstMac, etherType, [portvlan],vlanTagPrio].

Important:

1. You can select port or vlan-id, but not both.2. If you select none:

• The entry deletes the Ethernet node.• The entry prevents you from selecting any

other attribute choices.

ip <word> Specifies the permitted IP attributes for the ACTtemplate. The list of allowed attributes must beseparated by commas and includes:[none | srcIp, dstIp, ipFragFlag, ipOptions,ipProtoType, dscp].

ipv6 <word> Specifies the permitted IPv6 for the ACT template. Thelist of allowed attributes must be separated bycommas and includes:[none | srcIpv6, dstIpv6, nextHdr]

name <word> Specifies a name for the ACT. <word> is an optionalparameter that specifies a name for the ACT using 0–32 characters. If you do not enter a name, a defaultname is generated, for example, ACT-1 for act-id =1.

protocol <word> Specifies the permitted protocol attributes for the ACTtemplate. The list of allowed attributes must beseparated by commas and includes:[none | tcpSrcPort, udpSrcPort, tcpDstPort,udpDstPort, tcpFlags, icmpMsgFlags]

Creating a template for user-created patternsCeate a template for patterns within an ACT. You can associate a maximum of three patternswith an ACT.



Prerequisites


Procedure steps

Create a template by using the following command:

filter act pattern <act-id> <word> <base> <offset> <length>

Variable definitionsUse the data in the following table to use the filter act pattern command.

Variable Valueact-id Specifies an ACT ID in the range of 1–4096.

<base> <offset> <length> Adds a template for patterns you create:

• base: the base and the offset together determine thebeginning of the pattern. Permitted values for the base includethe following:

- ether-begin

- mac-dst-begin

- mac-src-begin

- ethTypeLen-begin

- arp-begin

- ip-hdr-begin

- ip-options-begin

- ip-payload-begin

- ip-tos-begin

- ip-proto-begin

- ip-src-begin

- ip-dst-begin

- ipv6-hdr-begin

- tcp-begin

- tcp-srcport-begin

Creating a template for user-created patterns


Variable Value

- tcp-dstport-begin

- tcp-flags-end

- udp-begin

- udp-srcport-begin

- udp-dstport-begin

- ether-end

- ip-hdr-end

- icmp-msg-begin

- tcp-end

- udp-end

• offset: the number of bits from the base where the patternstarts. This is a range from 0–76800.

• length: the length in bits of the user-defined field from 1–56.

name <pattern-name> Renames the pattern with a new name that you define. Each ofthe three patterns must have a unique name.

word Specifies a name for the pattern in the range of 1–32 characters.To set this option to the default value, use the default operatorwith the command.

Applying the ACTAfter you create and configure the ACT, apply it to implement the configuration.

Prerequisites

You must log on to the Privileged EXEC mode in the ACLI.

Procedure steps

Apply the ACT by using the following command:



filter apply act <act-id>

Configuring ACLsConfigure access control lists (ACL) to create rules for the ACT.

Important:If an ACT contains IPv6 attributes, you must configure an ACL of pktType IPv6. If the ACTuses only Ethernet attributes, you can configure one ACL of pktType IPv4 and an ACL ofpktType IPv6.

Prerequisites


Procedure steps

1. Configure an ACL by using the following command:

filter acl <acl-id> type <inVlan|outVlan|inPort|outPort> act<act-id> pktType <ipv4|ipv6> name <word>

2. Enable an ACL by using the following command:

filter acl <acl-id> enable

Variable definitionsUse the data in the following table to use the filter acl command.


act <act-id> Specifies the ACT ID to associate with the ACL.

enable Enables the ACL state along with all ACEs below it.Enable is the default state for the ACL.

name <word> Renames an ACL. To configure this option to thedefault value, use the default operator with thecommand.

Configuring ACLs


Variable ValuepktType <ipv4|ipv6> Configures the packet type for the ACL.

Important:The pktType field is optional for IPv4 traffic filters. Itis required if you apply the ACL to IPv6 packets.

type <inVlan|outVlan|inPort|outPort>

Configures the type of ACL.

Configuring global and default actions for an ACLConfigure global and default actions for an ACL to globally apply the configuration.

Prerequisites


Procedure steps

1. Configure default actions by using the following command:

filter acl set <acl-id> default-action <value>2. Configure global actions by using the following command:

filter acl set <acl-id> global-action <value>

Variable definitionsUse the data in the following table to use the filter acl set command.


default-action <value> Specifies the default action when no ACEs match.Permitted options include [deny|permit], with a defaultof permit. To configure this option to the default value,use the default operator with the command.



Variable Valueglobal-action <value> Specifies the global action for the matching ACEs.

Permitted options include [none|count|count-ipfix|ipfix|mirror|mirror-count|mirror-count-ipfix|mirror-ipfix]. The default is none. To configure this option tothe default value, use the default operator with thecommand.

Associating VLANs for an ACLAssociate or remove VLANs for a an ACL.

Prerequisites


Procedure steps

Associate or remove VLANs by using the following command:

filter acl vlan <acl-id> <vlan-id>

Variable definitionsUse the data in the following table to use the filter acl vlan command.

Variable Valueacl-id Specifies an ACL ID in the range of 1–4096. To

configure this option to the default value, use thedefault operator with the command.

vlan-id Associates a VLAN or a VLAN list with a particularACL. Format a list of VLANs separated by a commaor a range of VLANs specified as low-high [vlan-id -vlan-id]. To configure this option to the default value,use the default operator with the command.

Associating VLANs for an ACL


Associating ports for an ACLAssociate or remove ports for an ACL.

Prerequisites


Procedure steps

Associate or remove ports by using the following command:

filter acl port <acl-id> <port>

Variable definitionsUse the data in the following table to use the filter acl port command.


port Associates a port or a port list with a particular ACL.Format a list of ports separated by a comma or a rangeof ports specified as low-high [slot/port -slot/port].

Adding an ACE with IPv6 header attributesAdd an ACE with IP header attributes as match criteria.

Important:Be aware of the following:

• You cannot select (*) after <ace-op>.• If you select no entry, it indicates that you want to delete the respective Ethernet, ARP,

or IPv6 protocol node.



Prerequisites


Procedure steps

Add an ACE with IPv6 header attributes by using the following command:

filter acl ace ipv6 <acl-id> <ace-id> [dst-ipv6 eq <word>][nxt-hdr <eq|ne> <next-header>] [src-ipv6 eq <word>]

Variable definitionsUse the data in the following table to use the filter acl ace ipv6 command.

Variable Valueace-id Specifies an ACE ID in the range 1–1000. To configure

this option to the default value, use the defaultoperator with the command.

acl-id Specifies an ACL ID in the range 1–4096. To configurethis option to the default value, use the defaultoperator with the command.

dst-ipv6 eq <word> Specifies the following:

• an operator for a field match condition—eq

• the list of destination IPv6 addresses separated bycommas

nxt-hdr <eq|ne> <nxt-hdr> Specifies the following:

• an operator for a field match condition (eq | ne)

• the next header value from one of the following:fragment|hop-by-hop|icmpv6|ipsecah|ipsecesp|noHdr|routing|tcp|udp| undefined

src-ipv6 eq <word> Specifies the following:

• an operator for a field match condition—eq

• the list of source IPv6 addresses separated bycommas

Adding an ACE with IPv6 header attributes




Chapter 29: Interoperability

The Avaya Ethernet Routing Switch 8800/8600 provides interoperability with servers running Linux andWindows XP. This chapter provides basic configuration and verification procedures for the varioussystems.

Interoperability navigation• Enabling IPv6 in Windows XP on page 355

• Pinging the switch from a Windows XP system on page 355

• Enabling IPv6 in Linux on page 356

• Pinging the Linux system from the switch on page 357

• Pinging the Avaya Ethernet Routing Switch 8800/8600 from the Linux system onpage 357

• Assigning IPv6 addresses to the Linux system on page 358

• Viewing IPv6 neighbors from the Linux system on page 358

Enabling IPv6 in Windows XPEnable IPv6 to add IPv6 functionality on the Windows XP system.

Procedure steps

1. Open the command prompt.2. At the prompt, enter ipv6 install.

Pinging the switch from a Windows XP systemPing the switch to test connectivity.


Procedure steps

At the command prompt on a Windows XP system, ping the switch by using thefollowing command:

ping <IPv6 address>%interface IDFor example:

C:\Documents and Settings\userid>ping fe80::240:5ff:fe31:ce1d%5

Job aid: sample ping outputFigure 20: Job aid: Ping from a Windows XP system on page 356 shows sample output forpinging the Avaya Ethernet Routing Switch 8800/8600 from a Windows XP system.

Figure 20: Job aid: Ping from a Windows XP system

Enabling IPv6 in LinuxEnable IPv6 to allow IPv6 functionality on the Linux system. (This procedure is specific toRedhat Linux systems. For other Linux systems, see the appropriate system instructions.)

Procedure steps

1. Type the following command on the Linux system in /etc/sysconfig/network:

NETWORKING_IPV6=yesIPV6INIT=yes

2. Reboot the Linux system.

Interoperability


Pinging the Linux system from the switchPing the Linux system from the switch by using Enterprise Device Manager to testconnectivity.

Procedure steps

1. From the Device Manager menu bar, choose Device, Open.

OR

From the Device Manager toolbar, click Open Device.2. In the Device Name box, identify the device:

<ipv6 address>%interface num=number of ping messagesFor example: f8a:0:0:0:0:0:203:1%eth0 num=1

Pinging the Avaya Ethernet Routing Switch 8800/8600 fromthe Linux system

Ping the switch from the Linux system to test connectivity.

Procedure steps

Enter the following command on the Linux system to test communication with theAvaya Ethernet Routing Switch 8800/8600:

# ping6 interface number <8600 IPv6 address>%<interface number>

Example of pinging the switch from a Linux systemProcedure steps

Ping the switch:

Pinging the Linux system from the switch


# ping6 -I eth0 58a:0:0:0:0:0:204:1

Job aid: Sample ping outputFigure 21: Job aid: Ping from a LINUX system on page 358 shows sample output for pingingthe switch from a LINUX system.

Figure 21: Job aid: Ping from a LINUX system

Assigning IPv6 addresses to the Linux systemAssign IPv6 addresses to interfaces on the Linux system.

Procedure steps

1. Navigate to /etc/sysconfig/network-scripts/ifcfg-<interface number>.2. Enter the following command:

IPV6ADDR=<ipv6 address>3. Add IPv6 addresses, if required, by using the following command:

#ifconfig <interface number> inet6 add <IPv6 address>

Viewing IPv6 neighbors from the Linux systemView IPv6 neighbors from the Linux system.

Procedure steps

View IPv6 neighbors by using the following command:

Interoperability


# /sbin/ip -6 neigh show

Viewing IPv6 neighbors from the Linux system


Interoperability


Chapter 30: Common procedures usingEnterprise Device Manager

This chapter provides common procedures that you use to configure IPv6 routing on the Avaya EthernetRouting Switch 8800/8600.

Common procedures navigation• Viewing advertisements in the link-state database on page 361

• Viewing characteristics in the AS-scope link-state database on page 362

• Viewing characteristics in the Link-scope link-state database on page 363

• Viewing virtual links on neighboring devices on page 364

• Viewing OSPF neighbor information on page 366

• Viewing TCP and UDP information on page 368

• Viewing routes information on page 372

• Viewing IPv6 attributes for an ACL on page 373

Viewing advertisements in the link-state databaseView the advertisements of areas throughout the link-state database (LSDB).

Procedure steps

1. In the navigation tree, open the following folders:Configuration > IPv6.2. Click OSPF.3. Click the Area-scope LSDB tab.

Variable definitionsUse the data in the following table to use the Area-scope LSDB tab.


Variable ValueAreaId A read-only field indicating the 32-bit integer that uniquely identifies an

area. Area ID 0.0.0.0 is used for the OSPF backbone.

Type A read-only field indicating the OSPF interface type. By default,switches can determine this value from the corresponding value ofifType. Broadcast LANs, such as Ethernet and IEEE 802.5, use thevalue broadcast; X.25 and similar technologies use the value nbma;and point-to-point links use the value pointToPoint.

RouterId A read-only field indicating the 32-bit integer that uniquely identifies therouter in the autonomous system.

Lsid A read-only field indicating that the link-state ID is an LS type-specificfield containing either a router ID or an IPv6 address. It identifies thepiece of the routing domain described by the advertisement.

Sequence A read-only field indicating that the sequence number is a signed 32-bit integer that identifies old and duplicate link-state advertisements.

Age A read-only field indicating the age in seconds of the link-stateadvertisement.

Checksum A read-only field indicating the checksum of the complete contents ofthe advertisement, except the age field. The age field is not included sothat the advertisement age increments without updating the checksum.The checksum used is the same for Industry Standards Organization(ISO) connectionless datagrams, the Fletcher checksum.

TypeKnown A read-only field indicating the LSA type recognized by this router.

Viewing characteristics in the AS-scope link-statedatabase

View the characteristics of the autonomous system (AS)-scope link-state database.

Procedure steps

1. In the navigation tree, open the following folders:Configuration > IPv6.2. Click OSPF.3. Click the AS-scope LSDB tab.

Variable definitionsUse the data in the following table to use the AS-scope LSDB tab.

Common procedures using Enterprise Device Manager


Variable ValueType A read-only field indicating the OSPF interface type. By default,

switches can determine this value from the corresponding value ofifType. Broadcast LANs, such as Ethernet and IEEE 802.5, use thevalue broadcast; X.25 and similar technologies use the value nbma;and point-to-point links use the value pointToPoint.

RouterId A read-only field indicating the 32-bit integer that uniquely identifiesthe router in the autonomous system.




Checksum A read-only field indicating the checksum of the complete contents ofthe advertisement, except the age field. The age field is not affectedso that the advertisement age value increments without updating thechecksum. The checksum used is the same for ISO connectionlessdatagrams, the Fletcher checksum.


Viewing characteristics in the Link-scope link-statedatabase

View the characteristics of the Link-scope link-state database.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click OSPF.3. Click the Link-scope LSDB tab.

Variable definitionsUse the data in the following table to use the Link-scope LSDB tab.

Viewing characteristics in the Link-scope link-state database


Variable ValueLocalIfIndex A read-only field indicating the identifier of the link from which the LSA

was received.

Type A read-only field indicating the OSPF interface type. By default,switches can determine this value from the corresponding value ofifType. Broadcast LANs, such as Ethernet and IEEE 802.5, use thevalue broadcast; X.25 and similar technologies use the value nbma;and point-to-point links use the value pointToPoint.

RouterId A read-only field indicating the 32-bit integer that uniquely identifies therouter in the autonomous system.




Checksum A read-only field indicating the checksum of the complete contents ofthe advertisement, except the age field. The age field is not affected sothat the advertisement age value increments without updating thechecksum. The checksum used is the same for ISO connectionlessdatagrams, the Fletcher checksum.


Viewing virtual links on neighboring devicesYou can view area and virtual link configuration for the neighboring device on the VirtualNeighbor tab.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click OSPF.3. Click the Virtual Neighbors tab.

Variable definitionsUse the data in the following table to use the Virtual Neighbors tab.



Variable ValueArea A read-only field that indicates the subnetwork in which the

virtual neighbor resides.

RtrId A read-only field that indicates the 32-bit integer (representedas a type IpAddress) uniquely identifying the neighboring routerin the autonomous system.

LocalIfIndex A read-only field that indicates the interface index number of thevirtual neighboring router.

AddressType A read-only field that indicates the address type of OSPFv3addresses including,

• unknown

• ipv4

• ipv6

• ipv4z

• ipv6z

• dns

Address A read-only field that indicates the virtual neighboring routerIPv6 address.

Options A read-only field that indicates the bit mask corresponding tothe neighbor options field.

State A read-only field that indicates the OSPF interface state,

• down

• attempt

• init

• twoWay

• exchangeStart

• exchange

• loading

• full

Events A read-only field that indicates the number of state changes orerror events that occurred between the OSPF router and theneighbor router.

LsRetransQLen A read-only field that indicates the number of elapsed secondsbetween advertising retransmissions of the same packet to aneighbor.

HelloSuppressed A read-only field that indicates whether Hello packets aresuppressed on the neighbor.

Viewing virtual links on neighboring devices


Variable ValueNbrIfId A read-only field that indicates the interface ID that the neighbor

advertises in Hello packets on this link; the local interface indexfor the neighbor.

RestartHelperStatus A read-only field that indicates whether the router is a hitlessrestart helper for the neighbor,

• notHelping

• helping

RestartHelperAge A read-only field that indicates the remaining time in the currentOSPF hitless restart interval. The range is 1 through 1800.

RestartHelperExitReason A read-only field that indicates the outcome of the last attemptto act as a hitless restart helper for the neighbor,

• none indicates no restart was attempted (default)

• inProgress indicates a restart attempt is currently underway

• completed indicates a completed restart

• timedout indicates a timed-out restart

• topologyChanged indicates a cancelled restart due to atopology change

Viewing OSPF neighbor informationTwo routers with interfaces to a common network are neighbors and appear on the Neighborstab for each neighboring router. The OSPF Hello protocol maintains and dynamically discoversneighbor relationships. The exception is an NBMA network; you manually configure permanentneighbors on each router eligible to become the DR.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click OSPF.3. Click the Neighbors tab.

Variable definitionsUse the data in the following table to configure the Neighbors tab.



Variable ValueIfIndex A read-only field indicating the local link ID of the link over

which the neighbor is reached.

Rtrld A read-only field indicating the router ID of the neighboringrouter, which in OSPF uses the same format as an IPv6address but identifies the router independent of IPv6address.

Address A read-only field indicating the IPv6 address for the neighborassociated with the local link.

Options A read-only field indicating the bit mask corresponding to theoptions field on the neighbor.

Priority A read-only field indicating the preferential treatmentassignment, which places the transmitted packets into queues.The priority field also indicates the possible selection of thepriority field in the data link header when the switch forwardsthe packet.

State A read-only field indicating the OSPF interface state:

• down

• attempt

• init

• twoWay

• exchangeStart

• exchange

• loading

• full

Events A read-only field indicating the number of state changes orerror events occurring between the OSPF router and theneighbor router.

LSRetransQLen A read-only field indicating the number of elapsed secondsbetween advertising retransmissions of the same packet to aneighbor.

HelloSuppressed A read-only field indicating whether hellos are suppressed at aneighbor.

NbrIfid A read-only field indicating the interface ID that the neighboradvertises in hello packets on this link; that is, the neighborlocal interface index.

RestartHelperStatus A read-only field indicating that the router is a hitless restarthelper for the neighbor,

Viewing OSPF neighbor information


Variable Value

• notHelping

• helping

RestartHelperAge A read-only field indicating the time remaining in current OSPFhitless restart interval, if the router acts as a restart helper forthe neighbor. The range is 1 through 1800 seconds.

RestartHelperExitReason A read-only field indicating the outcome of the last attempt toact as a hitless restart helper for the neighbor,

• none indicates no restart was attempted (default)

• inProgress indicates a restart attempt is currently underway

• completed indicates a completed restart

• timedout indicates a timed-out restart

• topologyChanged indicates a cancelled restart due to thetopology change

Viewing TCP and UDP informationView TCP and UDP information to view the current configuration.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click TCP/UDP.3. Select the required tab:

• TCP Globals• TCP Connections• TCP Listeners• UDP Endpoints

Variable definitionsUse the data in the following table to use the TCP/UDP tabs.

Variable ValueTCP Globals tab



Variable ValueRtoAlgorithm Determines the timeout value used for

retransmitting unacknowledged octets.

RtoMin Displays the minimum time (in milliseconds)permitted by a TCP implementation for theretransmission timeout.

RtoMax Displays the maximum time (in milliseconds)permitted by a TCP implementation for theretransmission timeout.

MaxConn Displays the maximum connections for thedevice.

TCP Connections tab

LocalAddressType Displays the type (IPv6 or IPv4) for theaddress in the LocalAddress field.

LocalAddress Displays the IPv6 address for the TCPconnection.

LocalPort Displays the local port number for the TCPconnection.

RemAddressType Displays the type (IPv6, IPv4) for the remoteaddress for the TCP connection.

RemAddress Displays the IPv6 address for the remoteTCP connection.

RemPort Displays the remote port number for the TCPconnection.

State Displays an integer that represents the statefor the connection:

• 1: closed

• 2: listen

• 3: synSent

• 4: synReceived

• 5: established

• 6: finWait1

• 7: finWait2

• 8: closeWait

• 9: lastAck(9)

• 10: closing

• 11: timeWait

• 12: deleteTCB

Viewing TCP and UDP information


Variable ValueProcess Displays the process ID for the system

process associated with the TCPconnection.

TCP Listeners tab

LocalAddressType Displays the type for the address (IPv6 orIPv4).

LocalAddress Displays the local IPv6 address.

LocalPort Displays the local port number.

Process Displays the ID for the TCP process.

UDP Endpoints tab

LocalAddressType Displays the local address type (IPv6 orIPv4).



RemoteAddressType Displays the remote address type (IPv6 orIPv4).

RemoteAddress Displays the remote IPv6 address.

RemotePort Displays the remote port number.

Instance Distinguishes between multiple processesconnected to the UDP endpoint.

Process Displays the ID for the UDP process.

TCP Globals tabUse the data in the following table to use the TCP Globals tab.

Variable ValueRtoAlgorithm Determines the timeout value used for retransmitting

unacknowledged octets.

RtoMin Displays the minimum time (in milliseconds) permitted by a TCPimplementation for the retransmission timeout.

RtoMax Displays the maximum time (in milliseconds) permitted by aTCP implementation for the retransmission timeout.

MaxConn Displays the maximum connections for the device.



TCP Connections tabUse the data in the following table to use the TCP Connections tab.

Variable ValueLocalAddressType Displays the type (IPv6 or IPv4) for the address in the

LocalAddress field.

LocalAddress Displays the IPv6 address for the TCP connection.

LocalPort Displays the local port number for the TCP connection.

RemAddressType Displays the type (IPv6, IPv4) for the remote address for theTCP connection.

RemAddress Displays the IPv6 address for the remote TCP connection.

RemPort Displays the remote port number for the TCP connection.

State Displays an integer that represents the state for the connection:

• 1: closed

• 2: listen

• 3: synSent

• 4: synReceived

• 5: established

• 6: finWait1

• 7: finWait2

• 8: closeWait

• 9: lastAck(9)

• 10: closing

• 11: timeWait

• 12: deleteTCB

Process Displays the process ID for the system process associated withthe TCP connection.

TCP Listeners tabUse the data in the following table to use the TCP Listeners tab.

Viewing TCP and UDP information


Variable ValueLocalAddressType Displays the type for the address (IPv6 or IPv4).



Process Displays the ID for the TCP process.

UDP EndpointsUse the data in the following table to use the UDP Endpoints tab.

Variable ValueLocalAddressType Displays the local address type (IPv6 or IPv4).



RemoteAddressType Displays the remote address type (IPv6 or IPv4).

RemoteAddress Displays the remote IPv6 address.

RemotePort Displays the remote port number.

Instance Distinguishes between multiple processes connected to theUDP endpoint.

Process Displays the ID for the UDP process.

Viewing routes informationView routes information to view the current configuration.

Procedure steps

1. In the navigation tree, open the following folders: Configuration > IPv6.2. Click IPv6.3. Click the Routes tab.

Variable definitionsUse the data in the following table to use the Routes tab.



Variable ValueDest Displays the IPv6 destination network address. The prefix value

must match the PrefixLength.

PfxLength Displays the number bits you want to advertise from the prefix.The prefix value must match the value in the Dest field. Therange is 0 to 128.

IfIndex Displays the ID for the VLAN or port.

NextHop Displays the IPv6 address of the next hop of this route.

Protocol Displays the routing protocol (OSPF).

Metric Displays the metric assigned to this interface. The default valueof the metric is the reference bandwidth or ifSpeed. The valueof the reference bandwidth is configured by thercOspfv3ReferenceBandwidth object.

Viewing IPv6 attributes for an ACLView IPv6 attributes for an ACL to view ACE Advanced entries associated with an ACL.

Procedure steps


2. Click Advanced Filters (ACE/ACLs).3. Click the ACL tab.4. Select any of the parameters of an IPv6 ACL.5. Click IPv6.

Variable definitionsUse the data in the following table to use the ACE IPv6, ACL (x) dialog box.

Variable ValueACL ID Specifies the unique identifier for the ACL.

ACEID Specifies the unique identifier for the ACE.

SrcAddrList Lists the source IPv6 addresses.

SrcAddrOper Specifies equal (eq) or not equal (ne) or any in relation to thelisted source addresses.

Viewing IPv6 attributes for an ACL


Variable ValueDstAddrList Lists the IPv6 destination addresses.

DstAddrOper Specifies equal (eq) or not equal (ne) or any in relation to thelisted destination addresses.

NxtHdrNxtHdr Displays the next header value.

NxtHdrOper Specifies equal (eq) or not equal (ne) or any in relation to thelisted next header.



Chapter 31: Common procedures using theCLI

This chapter describes common procedures that you use while configuring IPv6 routing on the AvayaEthernet Routing Switch 8800/8600.

Common procedures navigationPinging a device on page 375

Pinging a deviceWhen you ping a device, the switch sends an Internet Control Message Protocol (ICMP) packetto the target device. If the device receives the packet, it sends a ping reply. When the switchreceives the reply, a message indicates that the specified IP address is responding. If no replyis received, a message indicates that the address is not responding.

Procedure steps

Ping a device by using the following command:

ping <HostName/ipv4address/ipv6address> [scopeid <value>][datasize <value> ] [count <value> ] [-s] [-I <value> ] [-t <value> ] [-d]

Variable definitionsUse the data in the following table to use the ping command.

Variable Valuecount <value> Configures the number of times to ping. For

IPv4 or IPv6, the range is 1–9999.


Variable Value

Important:To specify a count for the ping operation,you must also specify a size. For example:ping 8888:0:0:0:0:0:0:1 count 10

-d Configures ping debugging (for IPv4/IPv6).

datasize <value> Configures the size of ping data sent in bytes,for IPv4: 16–4076, for IPv6: 16-65487.

HostName/ipv6address Specifies the host name or IPv6(x:x:x:x:x:x:x:x) address {string length 1–256}.

-I <value> Configures the interval betweentransmissions in seconds (1–60).

-s Configures the continuous ping at theinterval rate defined by the [-I] parameter (forIPv4/IPv6)

scopeid <value> Configures the circuit ID (for IPv6) (1–9999).

-t <value> Configures the no answer timeout value(IPv4 or IPv6) {1–120}.

Common procedures using the CLI


Chapter 32: Common procedures using theACLI

This chapter describes common procedures that you use while configuring IPv6 routing on the AvayaEthernet Routing Switch 8800/8600.

Common procedures navigationPinging a device on page 377

Pinging a deviceWhen you ping a device, the switch sends an Internet Control Message Protocol (ICMP) packetto the target device. If the device receives the packet, it sends a ping reply. When the switchreceives the reply, a message indicates that the specified IP address is responding. If no replyis received, a message indicates that the address is not responding.

Procedure steps

Ping a device by using the following command:

ping <HostName/ipv4address/ipv6address> [scopeid <value>][datasize <value> ] [count <value> ] [-s] [-I <value> ] [-t <value> ] [-d]

Variable definitionsUse the data in the following table to use the ping command.

Variable Valuecount <value> Configures the number of times to ping (for

IPv4 or IPv6). The range is 1–9999.


Variable Value

Important:To specify a count for the ping operation,you must also specify a size. For example:ping 8888:0:0:0:0:0:0:1

-d <value> Configures ping debugging (for IPv4 orIPv6).

datasize <value> Configures the size of ping data sent in bytes,for IPv4:16–4076, for IPv6: 16-65487.

HostName/ipv6address Specifies the host name or IPv6(x:x:x:x:x:x:x:x) address {string length 1–256}.

-I <value> Configures the interval betweentransmissions in seconds (1–60).

-s Configures the continuous ping at theinterval rate defined by the [-I] parameter(for IPv4 or IPv6).

scopeid <value> Configures the circuit ID (for IPv6) (1–9999).

-t <value> Configures the no answer timeout value (forIPv4 or IPv6) {1–120}.

Common procedures using the ACLI


Chapter 33: IPv6 CLI configuration

This chapter contains enhanced configuration examples of IPv6 routing with the Avaya Ethernet RoutingSwitch 8800/8600.

IPv6 CLI configuration navigation• OSPF configuration on page 379

• Routing both IPv4 and IPv6 traffic on page 382

• Tunnel configuration between brouter ports on page 384

• Tunnel configuration between VLANs on page 387

OSPF configurationYou can configure OSPFv3 on an interface (brouter port) or VLAN. This configuration exampleconfigures the following in reference to Avaya Ethernet Routing Switch 8800/8600-B:

• Configure an IPv6 VLAN, VLAN 2, with port member 3/1.• Configure a core IPv6 brouter port, port 7/1.• Use IPv6 address 2001:100:102::/64.

Figure 22: Configuration example network on page 379 represents the network for theconfiguration example.

Figure 22: Configuration example network


Configuring OSPFv3Procedure steps

1. Configure VLAN 2 and add port members.

For IPv6, configure port-based or protocol-based VLANs. For this example, createport-based VLAN 2:

ERS8600-B:5# config vlan 2 create byport 1ERS8600-B:5# config vlan 2 ports add 3/1

2. Configure and enable the IPv6 address on VLAN 2:

ERS8600-B:5# config vlan 2 ipv6 create addr2001:100:102:202::1/64ERS8600-B:5# config vlan 2 ipv6 admin enable

3. Enable OSPFv3 on VLAN 2:

ERS8600-B:5# config vlan 2 ipv6 ospf create 0.0.0.0ERS8600-B:5# config vlan 2 ipv6 ospf admin-status enable

4. Configure brouter port 7/1 with IPv6:

ERS8600-B:5# config ethernet 7/1 ipv6 create addr2001:100:102:201::1/64 vlan 3999ERS8600-B:5# config ethernet 7/1 ipv6 admin enable

5. Enable OSPFv3 on brouter port 7/1:

ERS8600-B:5# config Ethernet 7/1 ipv6 ospf create 0.0.0.0ERS8600-B:5# config ethernet 7/1 ipv6 ospf admin-statusenable

By default, IPv6 router discovery is enabled. Any IPv6 device connected to VLAN 2 discoversthe 2001:100:102:202::1 address belonging to ERS8600-B. Verify the discovery by using thefollowing command:

ERS8600-B:5# config vlan 2 ipv6 nd info

Verifying operations from ERS 8600-AThe following commands verify that ERS 8600-A is learning routes from ERS 8600-B.

Procedure steps

1. Enter the following command to verify that ERS 8600-A learned routes to VLAN 2from ERS 8600-B:

IPv6 CLI configuration


ERS8600-A:6# show ipv6 route info2. Verify connectivity to both IPv6 interfaces with the ping command:

ERS8600-A:6# ping 2001:100:102:201::12001:0100:0102:0201:0000:0000:0000:0001 is AliveERS8600-A:6# ping 2001:100:102:202::12001:0100:0102:0202:0000:0000:0000:0001 is Alive

3. Verify the OSPFv3 neighbor by using the following command:

ERS8600-A:6# show ipv6 ospf neighbor4. From ERS 8600-A, verify the OSPF router ID and link state information through

ERS 8600-B by using the following command:

ERS8600-A:6# show ipv6 ospf lsdb detail5. Verify the IPv6 neighbor cache by using the following command:

ERS8600-A:6# show ipv6 neighbor info

Verifying operations from ERS 8600-BVerify the OSPFv3 configuration and operations from ERS 8600-B.

Procedure steps

1. Verify OSPF by using the following command:

ERS8600-B:5# show ipv6 ospf info2. Verify IPv6 addresses:

ERS8600-B:5# show ipv6 addr info3. Verify neighbor discovery by using the following command. In a successful

configuration, the IPv6 VLAN 2 and brouter port 7/1 prefixes appear in the output.

ERS8600-B:5# show ipv6 nd_prefix info

Verifying OSPFv3 operations from a PCIn the following example, a Windows XP desktop PC connects to VLAN 2 on ERS 8600-B.

Procedure steps

1. At the command prompt (select Start, Run, enter cmd, and click OK), enter thefollowing commands to verify that the IPv6 addresses from ERS 8600-B appears inthe output:

OSPF configuration


C:\> netsh netsh>interface netsh interface>ipv6 netshinterface ipv6>show neighbors

2. Verify that you can ping the IPv6 network address for ERS 8600-B:

C:\> ping 2001:100:102:202::13. Verify that you can ping the IPv6 network address for ERS 8600-A:

C:\> ping 2001:100:102:201::2

Routing both IPv4 and IPv6 trafficThe following figure shows the configuration of a dual-stack system or a switch that routes bothIPv4 and IPv6 traffic. The following example contains steps to configure both brouter ports andVLANs.

Figure 23: Dual stack system

Use the following example to configure OSPF.



Procedure steps

1. Create an IPv4 interface.

Enter the following command for a VLAN:

config vlan 100 ip create 1.1.1.1/24 100Enter the following command for a brouter port:

config ethernet 2/1 ip create 1.1.1.1/24 1002. Configure an OSPF area for the interface.


config vlan 100 ip ospf area 1.1.1.1Enter the following command for a brouter port:

config ethernet 2/1 ip ospf area 1.1.1.13. Enable OSPF on the interface.


config vlan 100 ip ospf enableEnter the following command for a brouter port:

config ethernet 2/1 ip ospf enable4. Create an IPv6 interface on the same VLAN or brouter port where you configured

IPv4.


config vlan 100 ipv6 create addr 3001::1/64Enter the following command for a brouter port:

config ethernet 2/1 ipv6 create addr 3001::1/64 vlan 1005. Enable the IPv6 interface.


config vlan 100 ipv6 admin-status enEnter the following command for a brouter port:

config ethernet 2/1 ipv6 admin-status en6. Create an OSPFv3 area by using the following command:

config ipv6 ospf area 2.2.2.2 create7. Create an OSPFv3 interface.


config vlan 100 ipv6 ospf create 2.2.2.2 metric 2

Routing both IPv4 and IPv6 traffic


Enter the following command for a brouter port:

config ethernet 2/1 ipv6 ospf create 2.2.2.2 metric 28. Enable OSPF on the IPv6 interface.


config vlan 100 ipv6 ospf admin enableEnter the following command for a brouter port:

config ethernet 2/1 ipv6 ospf admin enable

Tunnel configuration between brouter portsThe following figure shows the tunnel configuration between brouter ports.

Figure 24: Tunnel configuration between brouter ports

Prerequisites

• You must configure static routes, RIP, or OSPF on both the source (8600 1) and remote(8600 2) IPv4 interfaces to communicate on an IPv4 network.

• The brouter ports on the source and destination devices use IPv4 addresses availablethrough the IPv4 network.

This example section requires you to perform the following procedures:

1. Creating an IPv6 VLAN with ports on the source device on page 385

2. Creating an IPv4 brouter port on the source device on page 385

3. Creating an IPv6 VLAN with ports on the remote device on page 385



4. Creating an IPv4 brouter port on the destination device on page 386

5. Configuring a tunnel on the source device on page 386

6. Configuring a tunnel on the destination device on page 386

Creating an IPv6 VLAN with ports on the source deviceConfigure the IPv6 VLAN with ports (VLAN 10 in the figure) on the source device, or 8600.

Procedure steps

1. Create a VLAN by using the following command:

config vlan 10 create byport 12. Add ports to the VLAN by using the following command:

config vlan 10 ports add 3/13. Assign an IPv6 address to the to the VLAN by using the following command:

config vlan 10 ipv6 create addr 4000::1/1204. Enable the new VLAN by using the following command:

config vlan 10 ipv6 admin enable

Creating an IPv4 brouter port on the source deviceProcedure steps

1. Create a brouter port with an IPv4 address by using the following command:

config ethernet 3/30 ip create 172.21.80.1/24 10002. Enable OSPF on the port by using the following command:

config ethernet 3/30 ip ospf enable3. Enable OSPF on the device by using the following command:

config ip ospf enable

Creating an IPv6 VLAN with ports on the remote deviceConfigure the IPv6 VLAN with ports (VLAN 40 in the figure) on the destination device, or8600.

Tunnel configuration between brouter ports


Procedure steps






Creating an IPv4 brouter port on the destination deviceCreate an IPv4 brouter port on the destination device.

Procedure steps

1. Create a brouter port with an IPv4 address by using the following command:

config ethernet 3/30 ip create 192.168.20.1/24 20002. Enable OSPF on the port by using the following command:

config ethernet 3/30 ip ospf enable3. Enable OSPF on the device by using the following command:


Configuring a tunnel on the source deviceConfigure a tunnel on the source device.

Procedure steps

Enter the following command to configure a tunnel on the source device. Enter theIPv4 address for the destination port for the remote-address value.

config ipv6 tunnel 1 create local-addr 172.21.80.1 ipv6addr2500::1/120 remote-address 192.168.20.1

Configuring a tunnel on the destination deviceConfigure a tunnel on the destination device.



Procedure steps

Enter the following command to configure a tunnel on the destination device. Enter theIPv4 address for the source port for the remote-address value.


Tunnel configuration between VLANsThe following figure shows the configuration of a tunnel between VLANs.

Figure 25: Tunnel configuration between VLANs

Prerequisites

• You must configure static routes, RIP, or OSPF on both the source (8600 1) and remote(8600 2) IPv4 interfaces to communicate on an IPv4 network.

• Configure IPv4 address on the VLANs. Test the source and destination addresses byusing the ping command.

This example requires you to perform the following procedures:

1. Configuring an IPv6 VLAN on the source device on page 388

2. Configuring an IPv4 VLAN on the source device on page 388

3. Configuring an IPv6 VLAN on the destination device on page 389

4. Configuring an IPv4 VLAN on the destination device on page 389

5. Configuring the tunnel on the source device on page 390

6. Configuring the tunnel on the destination device on page 390

Tunnel configuration between VLANs


Configuring an IPv6 VLAN on the source deviceConfigure the IPv6 VLAN (VLAN 10 in the figure) on the source device, or 8600 1 in thefigure.

Procedure steps






Configuring an IPv4 VLAN on the source deviceConfigure an IPv4 VLAN (VLAN 20 in the figure) on the source device (8600 1 in the figure).The IPv4 VLAN encapsulates the IPv6 VLAN across the IPv4 network.

Procedure steps

1. Create the VLAN by using the following command:


config vlan 20 ports add 3/303. Assign an IPv4 address to the VLAN by using the following command:

config vlan 20 ip create 172.21.80.1/244. Enable OSPF on the VLAN by using the following command:

config vlan 20 ip ospf enable5. Enable OSPF on the device by using the following command:




Configuring an IPv6 VLAN on the destination deviceConfigure the IPv6 VLAN (VLAN 40 in the figure) on the destination device, or 8600 2 in thefigure.

Procedure steps






Configuring an IPv4 VLAN on the destination deviceConfigure an IPv4 VLAN (VLAN 30 in the figure) on the destination device (8600 2 in the figure).The IPv4 VLAN encapsulates the IPv6 VLAN across the IPv4 network.

Procedure steps

1. Create the VLAN by using the following command:


config vlan 30 ports add 3/303. Assign an IPv4 address to the VLAN by using the following command:

config vlan 30 ip create 192.168.20.1/244. Enable OSPF on the VLAN by using the following command:

config vlan 30 ip ospf enable5. Enable OSPF on the device by using the following command:


Tunnel configuration between VLANs


Configuring the tunnel on the source deviceProcedure steps

Enter the following command to configure the tunnel on the source device. Enter theIPv4 address for the destination device (8600 2) for the remote-address value.


Configuring the tunnel on the destination deviceProcedure steps

Enter the following command to configure the tunnel on the destination device. Enterthe IPv4 address for the source device (8600 1) for the remote-address value.




Chapter 34: CLI show commands

This chapter describes show commands to view the operational status of IPv6 routing on the AvayaEthernet Routing Switch 8800/8600.

CLI show command navigation• ACL or ACE information on page 392

• ACT data on page 393

• ACT pattern data on page 394

• Basic OSPF information about a port on page 395

• Extended OSPF information on page 395

• Interface (VLAN or brouter port) configuration output on page 396

• IPv6 static route information on page 397

• MLD cache on page 397

• MLD configuration for a brouter port on page 398

• MLD configuration for a VLAN on page 398

• Neighbor cache on page 399

• Neighbor discovery prefixes on page 400

• OSPF areas on page 400

• OSPF configuration settings for a port on page 401

• OSPF information on page 401

• OSPF interface information on page 402

• OSPF interface timer settings on page 403

• OSPF link-state database table on page 404

• OSPF neighbors on page 405

• OSPF parameters configured for VLANs on page 406

• OSPFv3 information for brouter ports on page 407

• OSPFv3 information for VLANs on page 407


• Tunnel information on page 408

• Tunnel interface information on page 409

ACL or ACE informationUse the show filter acl ace command to display information about ACLs or ACEs. Thesyntax for this command is as follows.

show filter acl ace [ <acl-id> ] [ <ace-id> ]The following table explains parameters for this command.

Table 33: Command parameters

Parameter Descriptionace-id Specifies a unique identifier (in the range 1–

1000) for this ACE entry.

acl-id Specifies a unique identifier (in the range 1–4096) for this ACL entry.

If you enter the <acl-id>, ACE information appears for all ACEs associated with the ACL. If youenter the <ace-id>, ACE information for the requested ACE appears. If you provide no <acl-id>, the command shows switch-wide ACL configuration data as viewed in the followingfigure.

CLI show commands


Figure 26: show filter acl ace partial command output

ACT dataUse the show filter act command to display ACT data. The syntax for this command isas follows.

show filter act [ <act-id> ]The following table explains parameters for this command.

ACT data



Parameter Descriptionact-id Specifies a unique identifier (in the range 1–

4096) for this ACT entry.

If you provide no <act-id>, the command shows switch-wide ACT configuration data.

Important:Any show command that displays information that cannot fit on oe screen appears as twotables: Part 1 and Part 2.

ACT pattern dataUse the show filter act-pattern command to display ACT pattern data. The syntax forthis command is as follows.

show filter act-pattern [ <act-id> ]The following table explains parameters for this command.




The following figure shows sample output for this command.

Figure 27: show filter act-pattern command output

CLI show commands


Basic OSPF information about a portUse the show ports stats ospf main port command to display basic OSPFinformation about the specified port or for all ports. The syntax for this command is asfollows.

show ports stats ospf main port <value>

The following table explains parameters for this command.


Parameter Descriptionport <value> Specifies the port or range of ports

configured in the format slot/port.

Figure 28: show ports stats ospf main command output on page 395 shows sample output forthis command.

Figure 28: show ports stats ospf main command output

Extended OSPF informationUse the show ports stats interface extended command to display extended OSPFinformation about the specified port or for all ports. The syntax for this command is asfollows.

show ports stats interface extended [port <value> ]The following table explains the parameters for this command.


Parameter Descriptionport <value> Specifies the port or range of ports to

configure in the format slot/port.

Basic OSPF information about a port


Figure 29: show ports stats interface extended command output on page 396 shows sampleoutput for this command.

Figure 29: show ports stats interface extended command output

Interface (VLAN or brouter port) configuration outputUse the show ipv6 interface info command to view the output of all configuredinterfaces. The syntax for this command is as follows.

show ipv6 interface infoView the output of a specific configured interface by using the following command:

show ipv6 interface info <interface ID>The following figure shows sample output for this command.

CLI show commands


Figure 30: show ipv6 interface info command output

IPv6 static route informationUse the show ipv6 static-route info command to display the existing IPv6 staticroutes for the switch or for a specific net or subnet. The syntax for this command is asfollows.

show ipv6 static-route infoFigure 31: show ipv6 static-route info command output on page 397 shows sample output forthis command.

Figure 31: show ipv6 static-route info command output

MLD cacheUse the show ipv6 mld mld-cache command to display the MLD cache for a brouter port,VLAN, or group address. The syntax for this command is as follows.

IPv6 static route information


Enter the following command to view the MLD cache for a brouter port:

show ipv6 mld mld-cache port <slot/port> detailEnter the following command to view the MLD cache for a VLAN:

show ipv6 mld mld-cache vlan <vlan id> detailEnter the following command to view the MLD cache for a group address:

show ipv6 mld mld-cache grp-address <address> detail

MLD configuration for a brouter portUse the show ports info mld command to display configuration details for MLD on abrouter port. The syntax for this command is as follows.

show ports info mldThe following figure shows sample output for this command.

Figure 32: show ports info mld command output

MLD configuration for a VLANUse the show vlan info mld command to display configuration details for MLD on a VLAN.The syntax for this command is as follows.

show vlan info mld

CLI show commands


Figure 33: Output for the show vlan info mld command on page 399 shows sample output forthis command.

Figure 33: Output for the show vlan info mld command

Neighbor cacheUse the show ipv6 neighbor info command to view entries in the neighbor cache. Thesyntax for this command is as follows.

show ipv6 neighbor infoFigure 34: show ipv6 neighbors info on page 399 shows sample output for the show ipv6neighbors info command.

Figure 34: show ipv6 neighbors info

Neighbor cache


Neighbor discovery prefixesUse the show ipv6 nd-prefix info command to view all configured neighbor discoveryprefixes. The syntax for this command is as follows.

show ipv6 nd-prefix infoThe following figure shows sample output for the show ipv6 nd-prefix infocommand.

Figure 35: show ipv6 nd-prefix info command output

OSPF areasUse the show ipv6 ospf area command to display information about OSPF areaparameters. The syntax for this command is as follows.

show ipv6 ospf areaFigure 36: show ipv6 ospf area command output on page 400 shows sample output for thiscommand.

Figure 36: show ipv6 ospf area command output

CLI show commands


OSPF configuration settings for a portUse the show ports info ospf command to display information about the OSPFparameters of the specified port or all ports. The syntax for this command is as follows.

show ports info ospf [ <ports> ]The following table explains the parameters for this command.


Parameter Descriptionports Specifies the port or range of ports to

configure in the format slot/port.

Figure 37: show ports info ospf command (partial output) on page 401 shows sample outputfor this command.

Figure 37: show ports info ospf command (partial output)

OSPF informationUse the show ipv6 ospf info command to display the current OSPF settings for theswitch. The syntax for this command is as follows.

show ipv6 ospf info

OSPF configuration settings for a port


Figure 38: show ipv6 ospf info command output on page 402 shows sample output for thiscommand.

Figure 38: show ipv6 ospf info command output

OSPF interface informationUse the show ipv6 ospf interface command to display information about the OSPFinterface.

show ipv6 ospf interfaceFigure 39: show ipv6 ospf interface command output on page 403 shows sample output forthis command.

CLI show commands


Figure 39: show ipv6 ospf interface command output

OSPF interface timer settingsUse the show ipv6 ospf int-timers command to display OSPF interface timer settings.The syntax for this command is as follows:

show ipv6 ospf int-timersFigure 40: show ipv6 ospf int-timers command output on page 403 shows sample output forthis command.

Figure 40: show ipv6 ospf int-timers command output

OSPF interface timer settings


OSPF link-state database tableUse the show ipv6 ospf lsdb command to display the OSPF link-state database (LSDB)table. The syntax for this command is as follows.

show ipv6 ospf lsdb [scope <value> ] [port <value> ] [vlan <value> ] [tunnel<value> ] [area <value> ] [lsatype <value> ] [lsid <value> ] [adv_rtr <value> ][detail]You can specify a scope, VLAN, tunnel, area string, link-state advertisement type (0 to 5), linkstate ID, or advertising router. If you add the detail option to the command, the outputcontains more information.

Figure 41: show ipv6 ospf lsdb command output on page 404 shows sample output with novariables for this command.

Figure 41: show ipv6 ospf lsdb command output

Figure 42: show ipv6 ospf lsdb detail command output on page 405 shows partial output ofthis command with the detail option.

CLI show commands


Figure 42: show ipv6 ospf lsdb detail command output

OSPF neighborsUse the show ipv6 ospf neighbor command to display OSPF neighbors configurationinformation. The syntax for this command is as follows.

show ipv6 ospf neighborFigure 43: show isv6 ospf neighbor command output on page 406 shows sample commandoutput for this command.

OSPF neighbors


Figure 43: show isv6 ospf neighbor command output

OSPF parameters configured for VLANsUse the show vlan info ospf command to display OSPF parameters configured for allVLANs or a specified VLAN. The syntax for this command is as follows.

show vlan info ospf [ <vid> ] [port <value> ]The following table explains the parameters for this command.


Parameter Descriptionport <value> Specifies the port or range of ports


vid Specifies a unique integer value in the range1–4094 that identifies the VLAN toconfigure.

Figure 44: show vlan info ospf command output on page 407 shows sample output for thiscommand.

CLI show commands


Figure 44: show vlan info ospf command output

OSPFv3 information for brouter portsUse the show ports info ospfv3 command to view OSPFv3 information for brouter ports.The syntax for this command is as follows.

show ports info ospfv3Figure 46: Output for show vlan info ospfv3 on page 408 shows sample output for thiscommand.

Figure 45: Output for show ports info ospfv3

OSPFv3 information for VLANsUse the show vlan info ospfv3 command to view OSPFv3 information for VLANs. Thesyntax for this command is as follows.

OSPFv3 information for brouter ports


show vlan info ospfv3Figure 46: Output for show vlan info ospfv3 on page 408 shows sample output for thiscommand.

Figure 46: Output for show vlan info ospfv3

Tunnel informationUse the show ipv6 tunnel info command to show general tunnel information. The syntaxfor this command is as follows.

show ipv6 tunnel info [ <tunnel-id> ]The following table explains the parameters for this command.


Parameter Descriptiontunnel-id Specifies the ID number of the tunnel in the

range 1-2147477248.

Figure 47: show ipv6 tunnel info output on page 408 shows sample output for the show ipv6tunnel info command.

Figure 47: show ipv6 tunnel info output

CLI show commands


Tunnel interface informationUse the show ipv6 tunnel interface command to show IPv6 tunnel interfaceinformation. The syntax for this command is as follows.

show ipv6 tunnel interface [<tunnel-id>]The following table explains the parameters for this command.


Parameter Descriptiontunnel-id Specifies the ID number of the tunnel in the

range 1-2147477248 .

Figure 48: show ipv6 tunnel interface on page 409 shows sample output for the show ipv6tunnel interface command.

Figure 48: show ipv6 tunnel interface

Tunnel interface information


CLI show commands


Chapter 35: ACLI show commands

This chapter describes privExec mode show commands to view the operational status of IPv6 routing onthe Avaya Ethernet Routing Switch 8800/8600.

ACLI show command navigation• ACL or ACE information on page 412

• ACT data on page 413

• ACT pattern data on page 414

• Basic OSPF information about a port on page 415

• Extended OSPF information on page 415

• Interface (VLAN or brouter port) configuration output on page 416

• IPv6 static route information on page 417

• MLD cache on page 417

• MLD configuration on page 418

• Neighbor cache on page 419

• Neighbor discovery prefixes on page 420

• OSPF areas on page 421

• OSPF configuration settings for a port on page 421

• OSPF information on page 422

• OSPF interface information on page 423

• OSPF interface timer settings on page 423

• OSPF link-state database table on page 424

• OSPF neighbors on page 424

• OSPFv3 information for VLANs on page 425

• Tunnel information on page 425


ACL or ACE informationUse the show filter acl ace command to display information about ACLs or ACEs. Thesyntax for this command is as follows.

show filter acl ace [ <acl-id> ] [ <ace-id> ]The following table explains parameters for this command.


Parameter Descriptionace-id Specifies a unique identifier (in the range 1–

1000) for this ACE entry.

acl-id Specifies a unique identifier (in the range 1–4096) for this ACL entry.

If you enter the <acl-id>, ACE information appears for all ACEs associated with the ACL. If youenter the <ace-id>, ACE information for the requested ACE appears. If you provide no <acl-id>, the command shows switch-wide ACL configuration data as viewed in the followingfigure.

ACLI show commands


Figure 49: show filter acl ace partial command output

ACT dataUse the show filter act command to display ACT data. The syntax for this command isas follows.

show filter act [ <act-id> ]The following table explains parameters for this command.

ACT data



Parameter Descriptionact-id Specifies a unique identifier (in the range 1

through 4096) for this ACT entry.

If you provide no<act-id>, the command shows switch-wide ACT configuration data.

Important:Any show command that displays information that cannot fit on one screen appears as twotables: Part 1 and Part 2.

ACT pattern dataUse the show filter act-pattern command to display ACT pattern data. The syntax forthis command is as follows.

show filter act-pattern [ <act-id> ]The following table explains parameters for this command.





Figure 50: show filter act-pattern command output

ACLI show commands


Basic OSPF information about a portUse the show ports statistics ospf main command to display basic OSPFinformation about the specified port or for all ports. The syntax for this command is asfollows.

show ports statistics ospf main <ports>

The following table explains parameters for this command.


Parameter Description<ports> Specifies the port or range of ports


Extended OSPF informationUse the show routing statistics interface command to display extended OSPFinformation about the specified port or for all ports. The syntax for this command is asfollows.

show routing statistics interface <interface> [slot/port]The following table explains the parameters for this command.


Parameter Descriptioninterface Specifies the interface type for which to

report statistics. The options includefastethernet and gigabitEthernet.

slot/port Specifies a particular slot and port or list ofports for which to provide results. If you omita specific port or port list, results include allports on the interface type.


Basic OSPF information about a port


Figure 51: show routing statistics interface command output

Interface (VLAN or brouter port) configuration outputUse the show ipv6 interface command to view the output of all configured interfaces.The syntax for this command is as follows.

show ipv6 interface [<interface-type>] [<interface-id>] [<interface-index>]The following table explains the parameters for this command.


Parameter Descriptioninterface-id Specifies the interface ID

interface-index Specifies the index from 1–4096.

interface-type Specifies the type of interface if you want tolimit the output. The options are fastEthernet,gigabitEthernet, icmpstatistics, statistics, orvlan.

Figure 52: show ipv6 interface on page 417 shows sample output for this command.

ACLI show commands


Figure 52: show ipv6 interface

IPv6 static route informationUse the show ipv6 route command to display the existing IPv6 static routes for the switchor for a specific net or subnet. The syntax for this command is as follows.

show ipv6 route staticFigure 53: show ipv6 route static on page 417 shows sample output for this command.

Figure 53: show ipv6 route static

MLD cacheUse the show ipv6 mld-cache interface command to display the MLD cache for abrouter port, VLAN, or group address. The syntax for this command is as follows.

IPv6 static route information


show ipv6 mld-cache interface <interface-type> <interface-id> [grp-address <0-46>] [detail]The following table explains the parameters for this command.


Parameter Descriptiongrp-address Specifies the group address to display.

interface-id Specifies the interface ID.

interface-type Specifies the type of interface if you want tolimit the output. The options are fastEthernet,gigabitEthernet, or vlan.

MLD configurationUse the show ipv6 mld interface command to display configuration details for all MLDinterfaces. The syntax for this command is as follows.

show ipv6 mld interface [<interface-type> <interface-id>] [detail]The following table explains the parameters for this command.


Parameter Descriptioninterface-id Specifies the interface ID.


Figure 54: show ipv6 mld interface on page 419 shows sample output for this command.

ACLI show commands


Figure 54: show ipv6 mld interface

Neighbor cacheUse the show ipv6 neighbor command to view entries in the neighbor cache. The syntaxfor this command is as follows.

show ipv6 neighbor [<ipv6addr>] [type {other|dynamic|static|local}][interface <interface-type> <interface-id>]The following table explains the parameters for this command.




type Specifies the type of mapping as one of thefollowing:

• other

• dynamic

• static

• local

Neighbor cache


Figure 55: show ipv6 neighbor on page 420 shows sample output for the show ipv6neighbor command.

Figure 55: show ipv6 neighbor

Neighbor discovery prefixesUse the show ipv6 nd-prefix interface command to view all configured neighbordiscovery prefixes. The syntax for this command is as follows.

show ipv6 nd-prefix interface <interface-type> <interface-id>]The following table explains the parameters for this command.




Figure 56: show ipv6 nd-prefix interface on page 421 shows sample output for the show ipv6nd-prefix interface command.

ACLI show commands


Figure 56: show ipv6 nd-prefix interface

OSPF areasUse the show ipv6 ospf area command to display information about OSPF areaparameters. The syntax for this command is as follows.

show ipv6 ospf areaThe following figure shows sample output for this command.

Figure 57: show ipv6 ospf area

OSPF configuration settings for a portUse the show ip ospf interface command to display information about the OSPFparameters of the specified port or all ports. The syntax for this command is as follows.

show ip ospf interface [<interface-type>] [<interface-id>]

OSPF areas


The following table explains the parameters for this command.



interface-type Specifies the type of interface if you want tolimit the output. The options are fastethernet,gigabitethernet, pos, or vlan.

Figure 58: show ip ospf interface on page 422 shows sample output for this command.

Figure 58: show ip ospf interface

OSPF informationUse the show ipv6 ospf command to display the current OSPF settings for the switch. Thesyntax for this command is as follows.

show ipv6 ospfThe following figure shows sample output for this command.

Figure 59: show ipv6 ospf command output

ACLI show commands


OSPF interface informationUse the show ipv6 ospf interface command to display information about the OSPFinterface.

show ipv6 ospf interface [{vlan|fastEthernet|gigabitEthernet} {vlan-id|slot/port}]The following figure shows sample output for this command.

Figure 60: show ipv6 ospf interface

OSPF interface timer settingsUse the show ipv6 ospf int-timers command to display OSPF interface timer settings.The syntax for this command is as follows:

show ipv6 ospf int-timersThe following figure shows sample output for this command.

Figure 61: show ipv6 ospf int-timers command output

OSPF interface information


OSPF link-state database tableUse the show ipv6 ospf lsdb command to display the OSPF link-state database (LSDB)table. The syntax for this command is as follows.

show ipv6 ospf lsdb [scope <1-3>] [tunnel <1-2147483647>] [area<A.B.C.D>] [lsa-type <1-8>] [adv-rtr <A.B.C.D>] [lsid <0-4294967295>][detail]You can specify a scope, VLAN, tunnel, area string, link-state advertisement type (0 to 5), linkstate ID, or advertising router. If you add the detail option to the command, the outputcontains additional information.

Figure 62: show ipv6 ospf lsdb on page 424 shows sample output with no variables for thiscommand.

Figure 62: show ipv6 ospf lsdb

OSPF neighborsUse the show ipv6 ospf neighbor command to display OSPF neighbors configurationinformation. The syntax for this command is as follows.

show ipv6 ospf neighborFigure 63: show ipv6 ospf neighbor command output on page 425 shows sample commandoutput for this command.

ACLI show commands


Figure 63: show ipv6 ospf neighbor command output

OSPFv3 information for VLANsUse the show ip ospf interface command to view OSPFv3 information for VLANs. Thesyntax for this command is as follows.

show ip ospf interface vlan <vlan-id>The following figure shows sample output for this command.

Figure 64: show ip ospf interface

Tunnel informationUse the show ipv6 tunnel command to show general tunnel information. The syntax forthis command is as follows.

show ipv6 tunnel [<tunnel-id>] [local <A.B.C.D>] [remote <A.B.C.D>][detail]The following table explains the parameters for this command.

OSPFv3 information for VLANs



Parameter Descriptiondetail Displays address information in addition to

basic tunnel information.

tunnel-id Specifies the ID number of the tunnel in therange 1 through 2 147 483 647.

The following figure shows sample output for the show ipv6 tunnel command.

Figure 65: show ipv6 tunnel

ACLI show commands


Chapter 36: ICMPv6 type and code

The Internet Control Message Protocol (ICMPv6) uses many messages identified by a type and code field(see RFC2463). Error messages use message types 0 to 127. Informational messages use messagetypes 128 to 255.

Note:The switch does not send an ICMP Parameter Problem message with an ICMP code value of 1 afterit receives a non-IPv6 packet with the Next Header value of zero in the header.

Table 54: ICMPv6 type and code details

Type Name Code Reference1 Destination Unreachable 0—no route to destination

1—communication withdestination administrativelyprohibited2—(not assigned)3—address unreachable4—port unreachable

RFC 2463

2 Packet Too Big N/A RFC 2463

3 Time Exceeded 0—hop limit exceeded in transit1—fragment reassembly timeexceeded

RFC 2463

4 Parameter Problem 0—erroneous header fieldencountered1—unrecognized Next Headertype encountered2—unrecognized IPv6 optionencountered

RFC 2463

128 Echo Request N/A RFC 2463

129 Echo Reply N/A RFC 2463

130 Multicast Listener Query N/A

131 Multicast Listener Report N/A

132 Multicast Listener Done N/A

133 Router Solicitation N/A RFC 2461

134 Router Advertisement N/A RFC 2461

135 Neighbor Solicitation N/A RFC 2461


Type Name Code Reference136 Neighbor Advertisement N/A RFC 2461

137 Redirect Message N/A RFC 2461

138 Router Renumbering 0—router renumbering command1—router renumbering result255—sequence number reset

139 ICMP Node Information Query N/A

140 ICMP Node InformationResponse

N/A

141 Inverse neighbor discoverySolicitation Message

N/A RFC 3122

142 Inverse neighbor discoveryAdvertisement Message

N/A RFC 3122

143 Version 2 Multicast ListenerReport

N/A RFC 3810

144 Home Agent Address DiscoveryRequest Message

N/A RFC 3775

145 Home Agent Address DiscoveryReply Message

N/A RFC 3775

146 Mobile Prefix Solicitation N/A RFC 3775

147 Mobile Prefix Advertisement N/A RFC 3775

ICMPv6 type and code


Chapter 37: RFC reference for IPv6

The following is a list of RFCs used in IPv6:

• RFC• RFC 1812, Requirements for IP Version 4 Routers• RFC 1881, IPv6 Address Allocation Management• RFC 1886, DNS Extensions to support IP version 6• RFC 1887, An Architecture for IPv6 Unicast Address Allocations• RFC 1981, Path MTU Discovery for IP version 6• RFC 2030, Simple Network Time Protocol (SNTP) v4 for IPv4, IPv6 and OSI• RFC 2373, IPv6 Addressing Architecture• RFC 2375, IPv6 Multicast Address Assignments• RFC 2385, Protection of BGP Sessions via the TCP MD5 Signature Option• RFC 2401, Security Architecture for the Internet Protocol• RFC 2404, The Use of HMAC-SHA-1-96 within ESP and AH• RFC 2406, IP Encapsulating Security Payload (ESP)• RFC 2452,IP Version 6 Management Information Base for the Transmission Control Protocol• RFC 2454, IP Version 6 Management Information Base for the User Datagram Protocol• RFC 2460, Internet Protocol, Version 6 (IPv6) Specification• RFC 2461, Neighbor Discovery for IP Version 6 (IPv6)• RFC 2462, IPv6 Stateless Address Autoconfiguration• RFC 2463, Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6)

Specification• RFC 2464, Transmission of IPv6 Packets over Ethernet Networks• RFC 2465, Management Information Base for IP Version 6: Textual Conventions and General Group• RFC 2466, Management Information Base for IP Version 6: ICMPv6 Group• RFC 2474, Definition of the Differential Services Field (DS Field) in the IPv4 and IPv6 Headers• RFC 2526, Reserved IPv6 Subnet Anycast Addresses• RFC 2710, Multicast Listener Discovery (MLD) for IPv6• RFC 2740, OSPF for IPv6• RFC 2893, Transition Mechanisms for IPv6 Hosts and Routers• RFC 3019, IP Version 6 Management Information Base for The Multicast Listener Discovery Protocol


• RFC 3056, Connection of IPv6 Domains via IPv4 Clouds• RFC 3122, Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification• RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6)• RFC 3363, Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System

(DNS)• RFC 3364, Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6)• RFC 3446, Anycast Rendevous Point (RP) mechanism using Protocol Independant Multicast (PIM)

and Multicast Source Discovery Protocol (MSDP)• RFC 3484, Default Address Selection for IPv6• RFC 3513, Internet Protocol Version 6 (IPv6) Addressing Architecture• RFC 3587, IPv6 Global Unicast Address Format• RFC 3590, Source Address Selection for the Multicast Listener Discovery (MLD) Protocol• RFC 3596, DNS Extensions to Support IP Version 6• RFC 3618, Multicast Source Discovery Protocol (MSDP)• RFC 3775, Mobility Support in IPv6• RFC 3810, IPv6 Multicast capabilities• RFC 4022, Management Information Base for the Transmission Control Protocol (TCP)• RFC 4087, IP Tunnel MIB• RFC 4113, Management Information Base for the User Datagram Protocol (UDP)• RFC 4649, Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option• draft-ietf-vrrp-ipv6-spec-08.txt, Virtual Router Redundancy Protocol for IPv6

Descriptions of management information bases (MIBs) in this document are based on information fromthe listed RFCs.

RFC reference for IPv6


Chapter 38: Customer service

Visit the Avaya Web site to access the complete range of services and support that Avaya provides. Goto www.avaya.com or go to one of the pages listed in the following sections.

Navigation• Getting technical documentation on page 431

• Getting Product training on page 431

• Getting help from a distributor or reseller on page 431

• Getting technical support from the Avaya Web site on page 432

Getting technical documentationTo download and print selected technical publications and release notes directly from theInternet, go to www.avaya.com/support.

Getting Product trainingOngoing product training is available. For more information or to register, you can access theWeb site at www.avaya.com/support. From this Web site, you can locate the Training contactslink on the left-hand navigation pane.

Getting help from a distributor or resellerIf you purchased a service contract for your Avaya product from a distributor or authorizedreseller, contact the technical support staff for that distributor or reseller for assistance.


http://www.avaya.com/

http://www.avaya.com/support


Getting technical support from the Avaya Web siteThe easiest and most effective way to get technical support for Avaya products is from theAvaya Technical Support Web site at www.avaya.com/support.

Customer service

