Avaya Interface and Router Redundancy User Manual

Conﬁguring Interface and Router Redundancy

BayRS V ersion 12.00 Site Manager Software Version 6.00

Part No. 117346-A Rev. A September 1997

4401 Great America Parkway 8 Federal Street Santa Clara, CA 95054 Billerica, MA 01821

and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty . Users must tak e full responsibility for their applications of an y products speciﬁed in this document. The information in this document is proprietary to Bay Networks, Inc.

The software described in this document is furnished under a license agreement and may only be used in accordance with the terms of that license. A summary of the Software License is included in this document.

Trademarks

ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FN, FRE, GAME, LN, Optivity, PPX, Bay Networks, SynOptics, SynOptics Communications, Wellﬂeet and the Wellﬂeet logo are registered trademarks and Advanced Remote Node, ANH, ARN, ASN, Bay•SIS, BayStack, BayStream, BCNX, BLNX, EZ Install, EZ Internetwork, EZ LAN, IP AutoLearn, PathMan, PhonePlus, Quick2Conﬁg, RouterMan, SN, SPEX, Switch Node, Bay Networks Press, the Bay Networks logo and the SynOptics logo are trademarks of Bay Networks, Inc.

All other trademarks and registered trademarks are the property of their respective owners.

Restricted Rights Legend

Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.

Statement of Conditions

In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the right to make changes to the products described in this document without notice.

Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein.

Portions of the code in this software product are Copyright © 1988, Regents of the Univ ersity of California. All rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that such portions of the software were developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from such portions of the software without speciﬁc prior written permission.

SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

In addition, the program and information contained herein are licensed only pursuant to a license agreement that contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed by third parties).

117346-A Rev. A

Bay Networks, Inc. Software License Agreement

NOTICE:

installing the hardware unit with pre-enabled software (each of which is referred to as “Software” in this Agreement). BY COPYING OR USING THE SOFTWARE, YOU A CCEPT ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS UNDER WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these terms and conditions, return the product, unused and in the original shipping container, within 30 days of purchase to obtain a credit for the full purchase price

1. License Grant.

nonexclusive, nontransferable license: a) to use the Software either on a single computer or, if applicable, on a single authorized device identiﬁed by host ID, for which it was originally acquired; b) to copy the Software solely for backup purposes in support of authorized use of the Software; and c) to use and copy the associated user manual solely in support of authorized use of the Software by Licensee. This license applies to the Software only and does not extend to Bay Networks Agent software or other Bay Networks software products. Bay Networks Agent software or other Bay Networks software products are licensed for use under the terms of the applicable Bay Networks, Inc. Software License Agreement that accompanies such software and upon payment by the end user of the applicable license fees for such software.

2. Restrictions on use; reservation of rights.

Bay Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including any revisions made by Bay Networks or its licensors. The copyright notice must be reproduced and included with any copy of any portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use for any competitive analysis, reverse engineer, distribute, or create derivative works from the Software or user manuals or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer the Software or user manuals, in whole or in part. The Software and user manuals embody Bay Networks’ and its licensors’ conﬁdential and proprietary intellectual property. Licensee shall not sublicense, assign, or otherwise disclose to any third party the Software, or any information about the operation, design, performance, or implementation of the Software and user manuals that is conﬁdential to Bay Networks and its licensors; however, Licensee may grant permission to its consultants, subcontractors, and agents to use the Software at Licensee’s f acility, provided they have agreed to use the Software only in accordance with the terms of this license.

3. Limited warranty.

installed and operated on Bay Networks hardware or other equipment it is originally licensed for, to function substantially as described in its accompanying user manual during its warranty period, which begins on the date Software is ﬁrst shipped to Licensee. If any item of Software fails to so function during its warranty period, as the sole remedy Bay Networks will at its discretion provide a suitable ﬁx, patch, or workaround for the problem that may be included in a future Software release. Bay Networks further warrants to Licensee that the media on which the Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days from the date Software is ﬁrst shipped to Licensee. Bay Networks will replace defective media at no charge if it is returned to Bay Networks during the warranty period along with proof of the date of shipment. This warranty does not apply if the media has been damaged as a result of accident, misuse, or abuse. The Licensee assumes all responsibility for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained from the Software. Bay Networks does not warrant a) that the functions contained in the software will meet the Licensee’s requirements, b) that the Software will operate in the hardw are or softw are combinations that the Licensee may select, c) that the operation of the Software will be uninterrupted or error free, or d) that all defects in the operation of the Software will be corrected. Bay Networks is not obligated to remedy any Software defect that cannot be reproduced with the latest Software release. These warranties do not apply to the Software if it has been (i) altered, except by Bay Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’s product, resulting in the defect; or (iii) damaged by improper environment, abuse, misuse, accident, or negligence. THE FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANT ABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of

Please carefully read this license agreement before copying or using the accompanying software or

Bay Networks, Inc. (“Bay Networks”) grants the end user of the Software (“Licensee”) a personal,

The Software and user manuals are protected under copyright laws.

Bay Networks warrants each item of Software, as delivered by Bay Networks and properly

117346-A Rev. A

iii

its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or altered ﬁles, data, or programs.

4. Limitation of liability.

COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT EXCEED THE PRICE PAID TO BAY NETWORKS FOR THE SOFTWARE LICENSE.

5. Government Licensees.

by or on behalf of the United States Government. The Software and documentation are commercial products, licensed on the open market at market prices, and were developed entirely at private expense and without the use of any U.S. Government funds. The license to the U.S. Government is granted only with restricted rights, and use, duplication, or disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial Computer Software––Restricted Rights clause of F AR 52.227-19 and the limitations set out in this license for civilian agencies, and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS

252.227-7013, for agencies of the Department of Defense or their successors, whichever is applicable.

6. Use of Software in the European Community.

European Community. If Licensee uses the Software within a country in the European Community, the Software Directive enacted by the Council of European Communities Directive dated 14 May, 1991, will apply to the examination of the Software to facilitate interoperability. Licensee agrees to notify Bay Networks of any such intended examination of the Software and may procure support and assistance from Bay Networks.

7. Term and termination.

Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the Bay Networks copyright; those restrictions relating to use and disclosure of Bay Networks’ conﬁdential information shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if Licensee fails to comply with any of the terms and conditions of the license. Upon termination for any reason, Licensee will immediately destroy or return to Bay Networks the Software, user manuals, and all copies. Bay Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license.

8. Export and Re-export.

or information without ﬁrst obtaining any required export licenses or other governmental approvals. Without limiting the foregoing, Licensee, on behalf of itself and its subsidiaries and afﬁliates, agrees that it will not, without ﬁrst obtaining all export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or divert any such Software or technical data, or any direct product thereof, to any country to which such exports or re-exports are restricted or embargoed under United States export control laws and regulations, or to any national or resident of such restricted or embargoed countries; or (ii) provide the Software or related technical data or information to any military end user or for any military end use, including the design, development, or production of any chemical, nuclear, or biological weapons.

9. General.

jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement will be governed by the laws of the state of California.

Should you have any questions concerning this Agreement, contact Ba y Networks, Inc., 4401 Great America P arkway, P.O. Box 58185, Santa Clara, California 95054-8185.

LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS

AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN BAY NETWORKS AND LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST BAY NETWORKS UNLESS BAY NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT.

If any provision of this Agreement is held to be invalid or unenforceable by a court of competent

IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY

This provision applies to all Software and documentation acquired directly or indirectly

This provision applies to all Software acquired for use within the

This license is effective until terminated; however, all of the restrictions with respect to

Licensee agrees not to export, directly or indirectly, the Software or related technical data

117346-A Rev. A

About This Guide

Before You Begin .............................................................................................................xiv

Conventions .....................................................................................................................xiv

Acronyms ......................................................................................................................... xv

Ordering Bay Networks Publications ...............................................................................xvi

Bay Networks Customer Service .....................................................................................xvi

How to Get Help .............................................................................................................xvii

Chapter 1 Interface Redundancy Overview

Active Interface ...............................................................................................................1-1

Redundant Interfaces .....................................................................................................1-1

Interface Roles ...............................................................................................................1-2

Determining the Active Interface ..............................................................................1-2

Reset Active Feature .........................................................................................1-2

Determining Priority .................................................................................................1-2

BofL Parameters and Role Change Speed on Ethernet ....................................1-3

Hot and Warm Standby .....................................................................................1-3

Active Interface MAC Address ........................................................................................1-4

117346-A Rev. A

Chapter 2 Router Redundancy Overview

Primary Router ...............................................................................................................2-1

Dedicated Secondary Router .........................................................................................2-1

Redundancy Protocol .....................................................................................................2-2

Role Change ...................................................................................................................2-6

Router Failure ..........................................................................................................2-6

Interface Failure .......................................................................................................2-6

BofL Parameters and Role Change Speed for Ethernet ....................................2-6

Resource Availability ................................................................................................2-7

Requirements .................................................................................................................2-7

Chapter 3 Implementation Notes

Planning Your Network ....................................................................................................3-1

Protocols Supported .......................................................................................................3-2

LAN Interfaces ................................................................................................................3-2

Router Redundancy Requirements ................................................................................3-3

Using Interface and Router Redundancy in Combination ..............................................3-3

Compatibility ...................................................................................................................3-4

Chapter 4 Conﬁguring Interface Redundancy

Enabling Interface Redundancy ......................................................................................4-1

Adding and Deleting Interfaces within a Group ..............................................................4-6

Removing Interface Redundancy from a Circuit .............................................................4-7

117346-A Rev. A

Chapter 5 Conﬁguring Router Redundancy

Enabling Router Redundancy .........................................................................................5-2

Creating a Group Conﬁguration File ...............................................................................5-2

Router Redundancy Group Parameters .........................................................................5-8

Conﬁguring Resources .................................................................................................5-12

Router Redundancy Resource Parameters ..................................................................5-15

Applying a Group Conﬁguration File .............................................................................5-17

Router Redundancy Member Global Parameters .........................................................5-20

Sending the Conﬁguration Files to the Routers ............................................................5-22

Conﬁguring Router Redundancy on Model 5380 Routers ............................................5-22

Conﬁguring Router Redundancy on One 5380 Router ..........................................5-22

Conﬁguring Router Redundancy on Different 5380 Routers ..................................5-23

Removing Router Redundancy ....................................................................................5-23

Appendix A Site Manager Default Parameter Settings

Appendix B Router Redundancy Examples

Example 1: Two Routers at the Same Site .................................................................... B-1

Router Bootup ......................................................................................................... B-1

Possible Scenarios .................................................................................................. B-2

Secondary Router Degraded ............................................................................ B-2

Secondary Router Becomes Inoperable ........................................................... B-2

Primary Router Degraded ................................................................................. B-2

Primary Router Fails ......................................................................................... B-2

Possible Complications ........................................................................................... B-3

Router Boots and Cannot Detect Another Member .......................................... B-3

Second Router Boots After First Router’s Bidding Timer Expires ..................... B-3

Manual versus Auto Role Switching ................................................................. B-3

Example 2: Three Routers at the Same Site ................................................................. B-4

Example 3: Router Redundancy with Wide Area Networks ........................................... B-5

Example 4: Router Redundancy with Ethernet Switches .............................................. B-7

117346-A Rev. A

vii

Appendix C Worksheets for Conﬁguring Router Redundancy

Appendix D BofL Parameters

Setting BofL Parameters ................................................................................................D-1

Index

viii

117346-A Rev. A

Figures

Figure 4-1. Add Circuit Window ..................................................................................4-2

Figure 4-2. Edit Connector Window ............................................................................4-3

Figure 4-3. Circuit Deﬁnition Window .........................................................................4-4

Figure 4-4. Select Primary Window ............................................................................4-5

Figure 4-5. Circuit Deﬁnition Window with Primary Interface .....................................4-5

Figure 5-1. Main Site Manager Window .....................................................................5-3

Figure 5-2. Add Circuit Window ..................................................................................5-4

Figure 5-3. Select Protocols Window .........................................................................5-5

Figure 5-4. Router Redundancy Circuit Window ........................................................5-6

Figure 5-5. R.R. Group Global Parameters Conﬁguration Window ............................5-7

Figure 5-6. RREDUND Router Redundancy Resource List Window .......................5-13

Figure 5-7. Router Redundancy Resource Window .................................................5-14

Figure 5-8. Conﬁguration Manager Window in Member Mode .................................5-17

Figure 5-9. Conﬁguration Manager Window for Member Conﬁguration ...................5-18

Figure 5-10. R.R. Member Global Parameters Conﬁguration Window .......................5-18

Figure 5-11. Save Conﬁguration File Window ............................................................5-19

Figure B-1. Router Redundancy: Two Routers at the Same Site ............................... B-1

Figure B-2. Router Redundancy: Three Routers at the Same Site ............................ B-4

Figure B-3. Router Redundancy with Wide Area Networks ....................................... B-5

Figure B-4. Router Redundancy with 281xx Fast Ethernet Switches ........................ B-7

Figure D-1. Edit CSMA/CD Parameters Window ....................................................... D-2

117346-A Rev. A

Tables

Table 2-1. Redundancy Protocol PDU Flow Diagram for Role Bidding ....................2-2

Table 2-2. Redundancy Protocol PDU Flow Diagram for SOS PDUs .......................2-5

Table 3-1. Using Interface Redundancy across Slots with Router Redundancy .......3-4

Table A-1. Router Redundancy Group Global Parameters ...................................... A-1

Table A-2. Router Redundancy Member Global Parameters ................................... A-2

Table A-3. Router Redundancy Resource Parameters ............................................ A-2

Table C-1. Group Mode Planning Worksheet ...........................................................C-1

Table C-2. Resource Planning Worksheet ................................................................C-2

Table C-3. Member Mode Planning Worksheet ........................................................ C-2

117346-A Rev. A

About This Guide

Bay Networks® redundancy services enhance router resilience by enabling a router to recover from either interface or router failure with minimal delay.

Interface redundancy protects your network from failures of individual LAN interfaces on a router. Router redundancy protects your network from failures of the entire router. You can use these services separately or in combination to ensure smooth and continuous operation of your network.

If you want to Go to

117346-A Rev. A

Learn about interface redundancy and special aspects of the Bay Networks implementation of interface redundancy

Learn about router redundancy and special aspects of the Bay Networks implementation of router redundancy

Implement interface redundancy and router redundancy Chapter 3 Conﬁgure interface redundancy Chapter 4 Conﬁgure router redundancy Chapter 5 View default parameter values for router redundancy Appendix A Review examples of how you can use router redundancy in your

network Review worksheets that help you conﬁgure router redundancy Appendix C Conﬁgure BofL parameters Appendix B

Chapter

Chapter 2

Appendix B

xiii

Configuring Interface and Router Redundancy

Before You Begin

Before using this guide, you must complete the following procedures:

• Create and save a conﬁguration ﬁle.

• Retrieve the conﬁguration ﬁle in local or remote mode. Refer to Make sure that you are running the latest version of Bay Networks Site Manager

and router software. For instructions, refer to

7–11.xx to Version 12.00

Conventions

angle brackets (< >) Indicate that you choose the text to enter based on the

bold text

Conﬁguring and Managing Routers with Site Manager

Upgrading Routers from Version

description inside the brackets. Do not type the brackets when entering the command. Example: if command syntax is you enter

ping 192.32.10.12

ping

Indicates text that you need to enter, command names, and buttons in menu paths. Example: Enter

Example: Use the Example: ATM DXI > Interfaces >

wfsm &

dinfo

command.

PVCs

PVCs button in the window that appears when you select the Interfaces option from the ATM DXI menu.

for instructions.

<ip_address>

identiﬁes the

xiv

italic text

Indicates variable values in command syntax descriptions, new terms, ﬁle and directory names, and book titles.

quotation marks (“ ”) Indicate the title of a chapter or section within a book.

screen text

Indicates data that appears on the screen. Example:

Set Bay Networks Trap Monitor Filters

117346-A Rev. A

About This Guide

separator ( > ) Separates menu and option names in instructions and

internal pin-to-pin wire connections. Example: Protocols > AppleTalk identiﬁes the AppleTalk option in the Protocols menu.

Example: Pin 7 > 19 > 20

vertical line (|) Indicates that you enter only one of the parts of the

command. The vertical line separates choices. Do not type the vertical line when entering the command. Example: If the command syntax is

Acronyms

show at routes show at routes

BofL Breath of Life FDDI Fiber Distributed Data Interface IP Internet Protocol IPX Internet Packet Exchange LAN local area network MAC media access control MIB management information base OUI organizationally unique identiﬁer PDU protocol data unit VLAN virtual LAN WAN wide area network

nets

, you enter either

show at nets

, but not both.

117346-A Rev. A

Configuring Interface and Router Redundancy

Ordering Bay Networks Publications

To purchase additional copies of this document or other Bay Networks publications, order by part number from Bay Networks Press numbers:

• Phone--U.S./Canada: 888-422-9773

• Phone--International: 510-490-4752

• FAX--U.S./Canada and International: 510-498-2609 The Bay Networks Press catalog is available on the World Wide Web at

support.baynetworks.com/Library/GenMisc

available on the World Wide Web at

support.baynetworks.com/Library/tpubs

Bay Networks Customer Service

You can purchase a support contract from your Bay Networks distributor or authorized reseller, or directly from Bay Networks Services. For information about, or to purchase a Bay Networks service contract, either call your local Bay Networks ﬁeld sales ofﬁce or one of the following numbers:

™

at the following

. Bay Networks publications are

xvi

Region Telephone number Fax number

United States and Canada

Europe 33-4-92-96-69-66 33-4-92-96-69-96 Asia/Paciﬁc 61-2-9927-8888 61-2-9927-8899 Latin America 561-988-7661 561-988-7550

800-2LANWAN; then enter Express Routing Code (ERC) 290, when prompted, to purchase or renew a service contract

508-916-8880 (direct)

508-916-3514

Information about customer service is also available on the World Wide Web at

support.baynetworks.com

117346-A Rev. A

How to Get Help

If you purchased a service contract for your Bay Networks product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance.

If you purchased a Bay Networks service program, call one of the following Bay Networks Technical Solutions Centers:

Technical Solutions Center Telephone number Fax number

Billerica, MA 800-2LANWAN 508-916-3514 Santa Clara, CA 800-2LANWAN 408-495-1188 Valbonne, France 33-4-92-96-69-68 33-4-92-96-69-98 Sydney, Australia 61-2-9927-8800 61-2-9927-8811 Tokyo, Japan 81-3-5402-0180 81-3-5402-0173

About This Guide

117346-A Rev. A

xvii

Chapter 1

Interface Redundancy Overview

Interface redundancy provides backup of one interface by another within a single router. It protects your network from partial router or installation failures; it also enables you to maintain data transmission for critical interfaces without the expense of two routers.

You conﬁgure interfaces to be members of an group includes an services, and one or more interface fails.

You can conﬁgure multiple interface redundancy groups on the same router.

Active Interface

The active interface performs normal bridging and routing services. When you conﬁgure interface redundancy, you select one interface on the router

to have the highest priority for being the active interface. That interface is the

designated primary interface

primary interface is the active interface for the redundancy group. If the active interface fails, however, another interface in the group becomes the new active interface.

Redundant Interfaces

All members of an interface redundancy group other than the active interface are redundant interfaces. A redundant interface has no function other than to serve as a backup.

active interface,

redundant interfaces,

. Under normal circumstances, the designated

interface redundancy group

which performs normal routing and bridging

which take over if the active

. The

117346-A Rev. A

1-1

Configuring Interface and Router Redundancy

Interface Roles

Bay Networks interface redundancy software determines which interface in a redundancy group becomes the active interf ace if the current acti v e interface f ails. The software also determines the priority for each of the remaining members of the group to become the active interface.

Determining the Active Interface

When you boot a router conﬁgured with interface redundancy, the designated primary interface has 12 seconds to become active. If it does become active, data transmission begins normally.

If the designated primary interface does not become active within 12 seconds, the redundant interface with the highest priority becomes the active interface, and transmission begins. The 12-second initialization period occurs only once, and applies only to the designated primary interface. After initialization, all redundant interfaces are ready to become active immediately if the active interface fails.

Reset Active Feature

Interface redundancy includes a Reset Active feature that allows you to force the interface you have designated as primary to become the active interface. Using this feature may improve network performance. Refer to Cha information about accessing the Reset Active feature.

Determining Priority

The redundant interface with the highest priority becomes the active interface if the active interface fails.

During startup, if the designated primary interface fails to become active, the following interfaces become active, in this order:

1. Redundant interfaces on the same slot as the designated primary interface

2. Redundant interfaces on other slots

1-2

pter 4 for

117346-A Rev. A

Interface Redundancy Overview

During normal data transfer, if the active interface fails, the following interfaces become active, in this order:

1. Redundant interfaces on the slot that is processing the routing/bridging table for this circuit

2. Redundant interfaces on other slots

BofL Parameters and Role Change Speed on Ethernet

When you enable BofL, the router only sends BofL messages if the interface is idle. If the interface is transmitting regular data trafﬁc, it does not send BofL messages.

Three parameters control BofL. The BofL Retries parameter sets the number of BofL messages the interface transmits before the router declares the circuit down. The number of seconds between BofL messages is the value of the BofL Timeout parameter divided by the BofL Timeout Divisor parameter.

To increase the speed of detecting failed interfaces and changing roles on Ethernet connectors, set the BofL Timeout parameter to a short interval, such as 1 second. If you also set the BofL Retries parameter to 4, and accept the BofL Timeout Divisor parameter default value of 1, a role change occurs in under 5 seconds. If you set the BofL Timeout Divisor parameter to a higher value, the router sends BofL messages so frequently that the cost in LAN bandwidth and CPU overhead is high.

117346-A Rev. A

Refer to Appendix D for parameter descriptions and instructions for using Site Manager to edit these parameters.

Hot and Warm Standby

When a redundant interface takes over for a f ailed interface without interruption in service, it does so under one of two conditions:

hot standby

warm standby.

Hot Standby

When an active interface fails, but the circuit is still up, the new active interface retains access to the routing/bridging tables, and can continue transmission immediately.

1-3

Configuring Interface and Router Redundancy

Only if the routing/bridging tables are on another slot from the new active interface is there any loss in performance. The priority rules for interfaces to become active operate to avoid this situation whenever possible.

Warm Standby

When the active interface fails and the circuit has gone down, the CPU module processing the routing/bridging table is at fault, and the router loses the routing/bridging tables.

Transmission continues, but is slower than hot standby, because the new active interface must relearn the routing/bridging tables.

Active Interface MAC Address

When you conﬁgure interface redundancy, the active interface uses the following MAC address in hexadecimal radix:

0x 2

y yy

xx xxxx

• 0x 2 indicates that the address is locally administered by Bay Networks.

1-4

•

y yy indicates the circuit number.

• A2 identiﬁes the Bay Networks organizationally unique identiﬁer (OUI).

• xx xxxx is the unique router identiﬁcation number.

The active interface in an interface redundancy group uses the MAC address for all trafﬁc, including Breath of Life (BofL). The MAC address switches among interfaces in the interface redundancy group so that it always represents the active interface.

The MAC address affects the setup of network-layer protocol adjacent hosts on adjacent routers. For example, if you have adjacent routers and the IP adjacent host is deﬁned with its next hop being the active interface in an interface redundancy group, the adjacent host MAC address must be the active interface’s MAC address; that is, 0x 2y yy A2xx xxxx

The circuit number maps to a virtual LAN (VLAN) on the router. Multiple VLANs on the same router can be connected to frame switches.

117346-A Rev. A

Interface Redundancy Overview

You ﬁnd the complete MAC address for the active interface in the interface management information base (MIB) -- Ethernet or FDDI -- of the router on which interface redundancy is conﬁgured. For example, if you are conﬁguring Ethernet, you can ﬁnd the active MAC address in the Ethernet MIB by entering the following command from the Technician Interface:

get wfCSMACDEntry.wfCSMACDMadr.*

Among the entries displayed in the MIB is the MAC address 0x 2y yy A2xx xxxx

, which is used for interface redundancy. If you conﬁgure more

than one interface redundancy group on the same router, you will see more than one entry with the same MAC address. This is not a problem because the two redundancy groups are in different subnets.

117346-A Rev. A 1-5

Chapter 2

Router Redundancy Overview

Router redundancy protects a network from the irrecoverable failure of an entire router. You conﬁgure routers to be members of a router redundancy group. The group includes a primary router that performs normal routing and bridging services, and one or more secondary routers that take over if the primary router fails.

Note: You can conﬁgure multiple router redundancy groups on the same

network.

Primary Router

Bay Networks router redundancy software allows you to decide which router has priority to be the primary router. It includes conﬁgurable bidding timers and timeout periods. These values determine how and when a router in a redundancy group changes roles from secondary to primary.

Dedicated Secondary Router

Bay Networks recommends that you conﬁgure router redundancy so that a secondary router has no function other than to serve as a backup. A router so conﬁgured is a dedicated secondary router.

You can conﬁgure a redundant router to carry other trafﬁc, unrelated to that of its redundancy group. Be aware, however, that if a secondary router becomes the primary router in a redundancy group, it stops performing any other data transfer operations; its role in the group takes precedence over any other functions you assign it.

117346-A Rev. A 2-1

Configuring Interface and Router Redundancy

Redundancy Protocol

Routers in a redundancy group all begin in the secondary role. A router assumes the primary role according to the following criteria, which the redundancy protocol considers in the following order:

1. Number of good interfaces

2. Number of reachable resources

3. Priority to become primary, which you conﬁgure

4. Lowest member ID (for further information, see the Member ID parameter in

Chapter 5)

For example, if two routers in a router redundancy group ha ve the same number of good interfaces, the protocol considers the number of reachable resources each router has. But if one router has a larger number of good interfaces, that router becomes primary without consideration of subsequent criteria.

The routers use a bidding process to determine which router becomes the primary router. If the group has more than two members, the bidding process also determines which of the backup routers is the best secondary router. The bidding process consists of an exchange of messages called protocol data units (PDUs).

able 2-1 provides a detailed description of this process.

Table 2-1. Redundancy Protocol PDU Flow Diagram for Role Bidding

Router A PDU Router B

Starts in secondary role. Starts in secondary role. Sends Hello PDUs at periodic intervals.

These PDUs start the bidding for the primary role.

2-2 117346-A Rev. A

Hello PDU Role = Secondary

---------------->

Receives Hello PDU from Router A and stores its contents in the redundancy group database.

Checks to see if Router A is a better primary router; if so, Router B does not plan to change roles.

(continued)

Router Redundancy Overview

Table 2-1. Redundancy Protocol PDU Flow Diagram for Role Bidding

Router A PDU Router B

Receives Hello PDU from Router B and stores its contents in the redundancy group database.

Checks to see if Router B is a better primary router; if so, Router A does not plan to change roles.

After the bidding period times out, the software determines that Router A is the best primary router. Router A sends the SOS New Primary PDU, and then changes role to become the primary router.

Receives the periodic Hello PDU and updates the redundancy group database, including each member’s interf ace status information.

Continues sending periodic Primary Hello PDUs with local interface status information. The Primary Hello PDUs from the primary router have additional meaning to other members of the redundancy group.

Hello PDU Role = Secondary <----------------

SOS New Primary PDU Role = Secondary

---------------->

Hello PDU Role = Secondary <----------------

Hello PDU Role = Primary

---------------->

Time Passes

Starts sending Hello PDUs at periodic intervals; these PDUs are Router B’s bids for the primary role.

After the bidding period times out, the software determines that another member of the router redundancy group is the best primary router. Router B remains in a secondary role and continues to monitor the redundancy group status.

Continues sending periodic Hello PDUs with local interface status information.

Receives the periodic Primary Hello PDUs and updates the redundancy group database, including each member’s interf ace status information. Restarts the Primary OK Timer.

(continued)

Primary router fails. Router A is in an unknown state; ma y not

have received this PDU.

Router A remains in an unknown state; may not have received this PDU.

117346-A Rev. A 2-3

SOS New Primary PDU Role = Secondary <----------------

Hello PDU Role = Primary <----------------

Primary OK Timer expires for Router B determines that the primary router has failed.

Based on information in the redundancy group database, the software determines that Router B is the best secondary router to become the new primary router.

Router B sends an SOS New Primary PDU, which prevents any other secondary router in the group from becoming the primary router.

Router B becomes the new primary router. As the new primary router, Router B

periodically sends Primary Hello PDUs with local interface status information.

times.

Configuring Interface and Router Redundancy

The primary router periodically monitors itself to make sure it is functioning normally. If it is not functioning properly, a role change occurs, as follows:

1. The primary router notiﬁes the best secondary router that it intends to change out of the primary role.

2. The best secondary router informs the other members of the impending role change, and those members start a timer (using the Bidding Timer value) to prevent additional role changes by other members.

3. The best secondary router assumes primary status.

Table 2-2 describes how a primary router changes to a secondary role while the

best secondary router assumes the primary role.

2-4 117346-A Rev. A

Router Redundancy Overview

Table 2-2. Redundancy Protocol PDU Flow Diagram for SOS PDUs

Router A PDU Router B

Router A, currently the primary router, sends Primary Hello PDUs at periodic intervals.

Receives the periodic Hello PDUs and updates the redundancy group database.

Router A detects local partial failures; for example, an important interface has failed. Router A knows that Router B is a better primary router, so Router A plans to change its role to secondary.

Router A issues an SOS PDU to inform all members of the redundancy group of its intention to change out of the primary role.

Router A, the current primary router, receives the SOS Reply PDU with its OK indication from Router B.

Router A sends an SOS Primary Goodbye PDU, then changes out of the primary role.

Router A may not receive this PDU, but all other members of the redundancy group do. This message tells the other secondary members to delay bidding for the new primary role until after the bidding timer expires and they detect that there is no primary router.

Router A may not receive this PDU. All other members of the redundancy group do, and update their redundancy group databases.

Hello PDU Role = Primary

---------------->

Hello PDU Role = Secondary <----------------

SOS PDU Role = Primary

---------------->

SOS Reply PDU Role = Secondary <----------------

SOS Primary Goodbye PDU Role = Primary

----------------> SOS New Primary

PDU Role = Secondary <----------------

Hello PDU Role = Primary <----------------

Router B, currently a secondary router, receives the periodic Primary Hello PDUs and updates the redundancy group database.

Router B restarts the Primary OK Timer. Router B sends periodic Hello PDUs.

Router B, the best secondary router, receives the SOS PDU, and conﬁrms that it is the best secondary router by sending the SOS Reply PDU.

Router B sends the SOS Reply PDU, indicating that it is ready to be the new primary router, and that it is OK for the current primary router to change out of the primary role.

Router B receives the SOS Primary Goodbye PDU.

Router B sends the SOS New Primary PDU to indicate that it is changing roles to become the new primary router. Router B changes its role to become the new primary router.

Router B has ﬁnished the role change and is now the new primary router. Router B sends its ﬁrst periodic Primary Hello PDU.

117346-A Rev. A 2-5

Configuring Interface and Router Redundancy

Role Change

A router may change out of the primary role because of router failure, failure of one or more interfaces, or because it cannot reach its resources.

Router Failure

If the primary router in a router redundancy group fails entirely, it obviously is no longer the best primary router, and a role change occurs, as outlined in T

able 2-2.

and T

Interface Failure

If one or more interfaces on the primary router fail, it is probably no longer the best primary router, depending on the status of the interfaces on the other routers in the router redundancy group. If it is not the best primary router, it changes out of the primary role.

BofL Parameters and Role Change Speed for Ethernet

able 2-1

To increase the speed of detecting failed interfaces and changing roles on Ethernet connectors, the software automatically shortens the values in the BofL parameters when you enable router redundancy. The relevant parameters are BofL Timeout, BofL Retries, and BofL Timeout Divisor.

When you enable BofL, the router only sends BofL messages if the interface is idle. If the interface is transmitting regular data trafﬁc, it does not send BofL messages.

The BofL Retries parameter sets the number of BofL messages the interface transmits before the router declares the circuit down. The default value for router redundancy is 4.

The number of seconds between BofL messages is the value of the BofL Timeout parameter divided by the BofL Timeout Divisor parameter. The default value for the BofL Timeout parameter is 5 seconds. When you enable router redundancy, the software sets the default value of the BofL Timeout Divisor parameter to 10, and thereby shortens the interval between BofL messages to 0.5 seconds.

2-6 117346-A Rev. A

With a divisor value of 10, and a retries value of 4, the router takes 2 seconds to detect 4 missed BofLs and initiate a role change. The entire role change procedure takes about 3 seconds.

You may want to set the retries to a value higher than 4 depending on the nature of your network. If your network typically carries trafﬁc in bursts, setting the retries value to 4 could trigger frequent, unnecessary role-switching.

Refer to Appendix D for parameter descriptions and instructions for using Site Manager to edit these parameters.

Resource Availability

A router is functioning normally if it can reach the resources -- servers, printers, and other devices -- with which you conﬁgure it to communicate. If a primary router in a redundancy group cannot reach its resources, it changes out of the primary role. Resources are determined by IP address, so all resources must be running TCP/IP.

Bay Networks redundancy software includes se veral parameters that allow you to control how often and how many times a router attempts to ping its resources (refer to Cha

Router Redundancy Overview

pter 5).

Requirements

Router redundancy has the following requirements:

• Router redundancy is a Bay Networks proprietary protocol. All routers running router redundancy must be Bay Networks routers.

• Interfaces that you conﬁgure for router redundancy must be on networks with no other routers that require route advertisements on that segment of the network.

• All members of a router redundancy group must have exactly the same conﬁguration for all redundant interfaces except for Member ID, Priority, and Resources.

• A router can be a member of only one router redundancy group.

117346-A Rev. A 2-7

This chapter provides information about special features of Bay Networks interface and router redundancy.

Planning Your Network

Conﬁguring router redundancy on your network is somewhat different from conﬁguring most protocols, because router redundancy involves multiple nodes. Consider your network requirements and design your interface and router redundancy groups carefully to maximize the beneﬁts of using redundancy. In particular, keep in mind the following characteristics of router and interface redundancy:

Chapter 3

Implementation Notes

• The interfaces you conﬁgure as backed-up interfaces should perform routing services that you rate as your highest priority.

• Remember that if a router becomes the primary router in a router redundancy group, other functions it has been performing while in the secondary role terminate.

• Bay Networks recommends that you conﬁgure redundant routers as dedicated redundant routers; that is, with the backup role as their sole function.

• A router can be a member of only one router redundancy group.

117346-A Rev. A 3-1

Configuring Interface and Router Redundancy

When planning your network for router redundancy, follow these guidelines:

• Determine the backed-up interfaces in each member of the router redundancy group.

• Select the group ID and member IDs for router redundancy, noting the following:

-- The group ID must be unique for each group in the network.

-- Each member ID must be unique within the group. Role-changing rules

use the member IDs to reassign roles. When two routers have the same priority, the one with the lowest member ID becomes the primary router when a role change occurs.

• Conﬁgure more than one interface for router redundancy to avoid a single point of failure.

Refer to Appendix C for worksheets to help you plan your router redundancy groups.

Protocols Supported

Interface redundancy works with IP, IPX, spanning tree bridging, source route bridging, AppleTalk, and VINES.

Router redundancy works with IP, only on stub networks. The network segment cannot have any other routers that require route advertisements.

LAN Interfaces

Interface and router redundancy support the following LAN interfaces as redundant interfaces: 10-Mb Ethernet, 100-Mb Ethernet, and FDDI. Interface redundancy also works with Token Ring networks.

All members of an interface redundancy group must be LAN interfaces of the same type.

Multiple LAN interfaces of the same type or different types can carry the router redundancy protocol.

3-2 117346-A Rev. A

Implementation Notes

Router Redundancy Requirements

All members of a router redundancy group must

• Be the same router type; for example, BCN

• Have the same hardware conﬁguration. This includes CPU and interface module types, slot and port locations of the backed-up interfaces, and resources.

• Have the same software conﬁguration. For example, all group members must be running the same router software version and have the same loadable modules conﬁgured.

• Use exactly the same router redundancy conﬁguration, except for the member ID.

, BLN®, or ASN™.

Using Interface and Router Redundancy in Combination

Use interface redundancy with router redundancy to provide combined pr otection from internal router failure and total router failure. The combination of interface and router redundancy provides better interface protection than is possible using interface redundancy alone.

You can conﬁgure backed-up interfaces within redundant routers, and you can also conﬁgure some interfaces that are not backed up. Interface redundancy allo ws data transmission to occur without interruption in the event of a failed interface. Router redundancy provides the security of uninterrupted network service.

Caution: If you conﬁgure interface redundancy across slots with router

redundancy, and the CPU board for the slot with the active interface fails, router redundancy may take precedence over interface redundancy, even though there is a member of the interface redundancy group available to transmit data. The result will be unnecessary delays in data transmission.

117346-A Rev. A 3-3

Configuring Interface and Router Redundancy

Table 3-1 demonstrates what happens when you conﬁgure interface redundancy

across slots using router and interface redundancy together.

Table 3-1. Using Interface Redundancy across Slots with Router Redundancy

Router A Router B

Router A is in the primary role for router redundancy. It also has the active interface in the interface redundancy group.

The CPU board for the active interface fails. Router A detects that it is no longer the best primary router, so Router A changes its role to secondary.

Meanwhile, a redundant interface from the interface redundancy group has become active, with the result that Router A is again the best primary router in the router redundancy group.

Router A assumes the primary role. Router B is in the secondary role.

Data is moving again.

Router B is in the secondary role.

Router B is the new best primary router, and it assumes the primary role.

Router B recognizes that it is no longer the best primary router and changes out of the primary role.

Note that you can prevent the second role change by conﬁguring the Automatic Role Switching parameter to Switch on Failure or One Shot Auto (refer to

pter 5).

Cha

Compatibility

If you are upgrading from Version 11.0/5.0 or earlier, you must completely reconﬁgure router redundancy. If you are upgrading from Version 11.01/5.01 or later, your existing conﬁguration is compatible with the new software.

3-4 117346-A Rev. A

Chapter 4

Conﬁguring Interface Redundancy

This chapter describes how to conﬁgure interface redundancy. It assumes you have read Conﬁguring and Managing Routers with Site Manager and Chapters 1

of this guide, and that you have

and 3

1. Opened a conﬁguration ﬁle in local or remote mode

2. Speciﬁed router hardware if this is a local mode conﬁguration ﬁle

3. Selected the link- or net-module connector on which you are enabling interface redundancy

To enable interface redundancy, you must select at least two interfaces as members of an interface redundancy group. One of the interfaces is the designated primary interface; under normal circumstances it is the active interface that provides normal routing/bridging services. The other is the redundant interface; it takes over if the active interface fails.

Enabling Interface Redundancy

To conﬁgure an interface redundancy group:

1. In the Conﬁguration Manager window , select an a vailable LAN interface.

The Add Circuit window opens (F

117346-A Rev. A 4-1

igure 4-1).

Configuring Interface and Router Redundancy

Figure 4-1. Add Circuit Window

Select all other available LAN interfaces of the same type that you want

to be members of this interface redundancy group.

3. Click on OK.

Interface redundancy is now enabled on this circuit. The Select Protocols window opens.

4. Select the protocols you want to conﬁgur e on the circuit, and click on OK.

5. Repeat Steps 1 through 4 to create additional interface redundancy

groups.

6. In the Conﬁguration Manager window , select one of the connectors in the

interface redundancy group you just created.

The Edit Connector window opens (F

4-2 117346-A Rev. A

igure 4-2).

Configuring Interface Redundancy

Figure 4-2. Edit Connector Window

Select Edit Circuit.

The Circuit Deﬁnition window opens (F

igure 4-3).

117346-A Rev. A 4-3

Configuring Interface and Router Redundancy

Figure 4-3. Circuit Deﬁnition Window

Note: The Reset Active option in the path Lines > Interface Redundancy >

Primary Interface is available in dynamic mode only. This option allows you to force the interface you have designated as primary to become the active interface. Using this option may improve performance.

In the Circuit Deﬁnition window , choose Lines > Interface Redundancy >

Primary Interface.

The Select Primary window opens (F

4-4 117346-A Rev. A

igure 4-4).

Configuring Interface Redundancy

Figure 4-4. Select Primary Window

Select an interface from the list in the Select Primary window, and click

on Primary.

Site Manager redisplays the Circuit Deﬁnition window with the letter P now appended to the interface you designated as primary (F

igure 4-5).

Figure 4-5. Circuit Deﬁnition Window with Primary Interface

117346-A Rev. A 4-5

Configuring Interface and Router Redundancy

10. Choose File > Exit to return to the Conﬁguration Manager window.

Adding and Deleting Interfaces within a Group

To add an interface to an existing interface redundancy group, or to delete an interface from a group:

1. In the Conﬁguration Manager window, select any circuit in the group

that you want to change.

The Edit Connector window opens (r

2. Click on Edit Circuit.

The Circuit Deﬁnition window opens (r

3. To add an interface, select an available line of the same LAN type as the

efer to Figure 4-2).

efer to Figure 4-3).

other members of the group. To delete an interface, select the line you want to delete from the group.

4. Choose Lines > Change Lines.

The interface you selected is now added to or deleted from the interface redundancy group. If only one interface remains on the circuit, the interface redundancy group no longer exists.

4-6 117346-A Rev. A

Configuring Interface Redundancy

Removing Interface Redundancy from a Circuit

To remove interface redundancy from a circuit:

1. In the Conﬁguration Manager window, select any member of the

interface redundancy group you want to remove.

The Edit Connector window opens (r

2. Select Edit Circuit.

The Circuit Deﬁnition window opens (r

3. Deselect all but one member of the interface redundancy group.

4. Choose Lines > Change Lines.

efer to Figure 4-2).

efer to Figure 4-3).

The interface redundancy group no longer exists.

5. Choose File > Exit to exit the window.

Note: You can ﬁnd out whether interface redundancy is conﬁgured on a circuit

by selecting that circuit in the Circuit Deﬁnition window and checking the Lines menu. If Interface Redundancy appears dim, it is not conﬁgured on the circuit you selected.

117346-A Rev. A 4-7

Chapter 5

Conﬁguring Router Redundancy

This chapter describes how to conﬁgure router redundancy. It assumes you have read Conﬁguring and Managing Routers with Site Manager and Chapters 2 of this guide, and that you have already created a local conﬁguration ﬁle for a router without router redundancy.

Note: You cannot conﬁgure router redundancy in dynamic or remote mode.

and 3

To enable router redundancy, you must choose at least two routers as members of a router redundancy group. One of the routers will be the primary router; it will provide normal routing/bridging services. The other router will be the secondary, backup router; it will take over if the primary router fails. All members of a router redundancy group must have exactly the same conﬁguration for all backed-up interfaces, except for the router’s Member ID, Priority, and resources.

When you enable router redundancy , you must conﬁgure some group and member parameters. The Conﬁguration Manager supplies default values for the remaining parameters. Use the directions that follow to enable router redundancy and edit router redundancy parameters.

For each parameter, this chapter describes default settings, valid parameter options, the parameter function, instructions for setting the parameter, and the MIB object ID.

117346-A Rev. A 5-1

Configuring Interface and Router Redundancy

Enabling Router Redundancy

To conﬁgure a router redundancy group, you create a group conﬁguration ﬁle. This ﬁle is a template that you use to conﬁgure each member of the group.

The instructions in this chapter assume that you want to create a router redundancy group consisting of two members: Router 1 and Router 2. The conﬁguration ﬁle you apply to these routers is named template. This ﬁle can be an existing conﬁguration ﬁle to which you are adding router redundancy, or it can be a new ﬁle you create to conﬁgure router redundancy and other features.

Creating a Group Conﬁguration File

To create a redundancy group conﬁguration ﬁle template, complete the following steps. All group members will use the values you conﬁgure in this ﬁle.

1. In the main Site Manager window, choose Tools > Router Redundancy >

Group Conﬁguration (F

igure 5-1).

5-2 117346-A Rev. A

Configuring Router Redundancy

Figure 5-1. Main Site Manager Window

The standard ﬁle selection window opens.

2. Enter template as the ﬁle name.

The standard router window opens.

3. Choose a router.

The Conﬁguration Manager window opens.

4. Choose an empty slot.

The Module List window opens.

5. Choose a module and click on OK.

The Conﬁguration Manager window opens.

6. In the Conﬁguration Manager window, select an available connector.

117346-A Rev. A 5-3

Configuring Interface and Router Redundancy

The Add Circuit window opens (Figure 5-2).

Figure 5-2. Add Circuit Window

Select an available circuit that you want to conﬁgure for router

redundancy, and click on OK.

The Select Protocols window opens (Figure 5-3).

5-4 117346-A Rev. A

Configuring Router Redundancy

Figure 5-3. Select Protocols Window

8. Scroll through the list and choose Router Redundancy. You can also

choose other protocols that you want to conﬁgure.

9. Click on OK.

The Router Redundancy Circuit window opens (F

117346-A Rev. A 5-5

igure 5-4).

Configuring Interface and Router Redundancy

Figure 5-4. Router Redundancy Circuit Window

The Enable, Role Switch on Failure, and Send PDU Enable parameters are set to Enable.

Note: The Conﬁguration Mode opens as “group” in the Conﬁguration

Manager, Add Circuit, and Router Redundancy Circuit windows. You add router redundancy to a circuit and edit redundancy parameters only in group mode.

10. Enter the Primary MAC Address for the router (required).

11. Click on OK.

The R.R. Group Global Parameters Conﬁguration window opens (F

5-6 117346-A Rev. A

igure 5-5).

Configuring Router Redundancy

Figure 5-5. R.R. Group Global Parameters Conﬁguration Window

Site Manager supplies default values for all parameters.

12. Enter values for any parameters you want to edit, using the descriptions

that follow this procedure for guidelines.

13. Click on OK.

The Conﬁguration Manager window opens. The circuits you conﬁgured for router redundancy are either green or shaded, depending on your monitor.

14. Choose File > Save, then exit the window.

117346-A Rev. A 5-7

Configuring Interface and Router Redundancy

Router Redundancy Group Parameters

Use the following descriptions as guidelines when you edit router redundancy group global parameters.

Parameter: Enable

Default: Enable

Options: Enable

Function: This parameter is automatically set to Enable when you choose Router

Redundancy from the Select Protocols window. If you set this parameter to Disable, you temporarily disable the redundancy protocol on the router without deleting your conﬁguration ﬁle.

Instructions: Choose Disable to stop the redundancy protocol from working on this

router.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.2.1.2

Parameter: Role Switch On Failure

Default: Enable

Options: Enable

Function: Enables or disables a role change if this interface fails.

Instructions: Accept the default, Enable, or choose Disable to prevent a role change in

the event this interface fails.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.2.1.5

| Disable

5-8 117346-A Rev. A

Configuring Router Redundancy

Parameter: Send PDU Enable

Default: Enable

Options: Enable

| Disable

Function: Enables or disables sending of router redundancy PDUs on a per-circuit

basis. This parameter is automatically set to Enable when you choose Router Redundancy from the Select Protocols window.

At least one interface on each router in the group must have this parameter enabled so that all routers in the group receive status information about each other. You may want to disable this parameter on some redundant interfaces to minimize network trafﬁc on a busy interface.

Instructions: Choose Enable or Disable.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.2.1.6

Parameter: Primary MAC Address

Default: None

Options: Any unique, 48-bit MAC address that the network manager provides

Function: The primary router uses the MAC address to route data. When the

primary router fails and a backup router becomes the new primary router, the new primary router assumes this MAC address.

Instructions: Enter a unique MAC address.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.2.1.4

Parameter: Group ID

Default: 1

Options: 1 to 128

Function: Speciﬁes the identiﬁcation number for the redundanc y group. Each group

ID number in a network must be unique.

Instructions: Enter a number from 1 to 128 that you have not already assigned to a

redundancy group on the network.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.1.4

117346-A Rev. A 5-9

Configuring Interface and Router Redundancy

Parameter: Automatic Role Switching

Default: Auto

Options: Manual

Function: Auto enables automatic role switching out of the primary role when a

router detects that it is no longer the best primary router, based on priority settings among the redundant routers. When the primary router switches out of the primary role, a backup router switches into the primary role. Anything else that backup router has been doing stops when it becomes primary.

In some circumstances, you may not want the backup router to stop processing automatically . If that is the case, set this parameter to Man ual. The warning section of the log will indicate when the routers should change roles.

Switch on Failure allows a role change only when an interface on the primary router fails, or a resource becomes unreachable, and does not consider Priority or Member ID.

One Shot Auto triggers a one-time only automatic role change. Thereafter a role change occurs only if an interface fails or a resource becomes unreachable.

Instructions: Accept the default, Auto, or choose one of the other options according to

the requirements of your network.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.1.11

| Auto | Switch on Failure | One Shot Auto

Parameter: Hello Timer

Default: 2 seconds

Options: 1 to 86,400 seconds

Function: Speciﬁes the amount of time that the routers in the redundancy group

have for sending each other primary and secondary Hello PDUs. The routers use Hello PDUs to initiate the bidding process that determines which router is primary.

Instructions: Enter a value in the speciﬁed range or accept the default of 2.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.1.15

5-10 117346-A Rev. A

Parameter: Timeout Threshold

Default: 5

Options: 1 to 100

Function: Speciﬁes the number of time periods during which the secondary routers

wait to receive a Hello PDU from the primary router before they determine that the primary has failed.

Instructions: Enter a number from 1 to 100 or accept the default of 5.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.1.17

Parameter: Good Bid Count

Default: 3

Options: 1 to 10

Function: Speciﬁes the minimum number of good bids to become primary that are

required from the same secondary router before Auto Role Switching occurs. This parameter has no effect if you have conﬁgured manual role-switching.

Configuring Router Redundancy

Instructions: Enter a number from 1 to 10 or accept the default of 3.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.1.12

Parameter: Bid Duration

Default: 45 seconds

Options: 1 to 65,535 seconds

Function: Speciﬁes the number of seconds during which routers bid to become the

primary router.

Instructions: Choose a value in the speciﬁed range or accept the default of 45. This

value depends on how fast the routers boot with the conﬁgured features. For example, booting with FDDI interfaces, WAN interfaces with resources conﬁgured (such as servers and printers), OSPF, and so on, may require a larger value.

Shorten this value if you want to ensure that the ﬁrst router that boots becomes the primary.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.1.16

117346-A Rev. A 5-11

Configuring Interface and Router Redundancy

Parameter: Role Switch Delay Period

Default: 5 seconds

Options: 1 to 86,400 seconds

Function: Currently not used.

Instructions: Accept the default.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.1.19

Conﬁguring Resources

The redundancy protocol uses the Resource parameters to ensure that the primary router in the router redundancy group can reach the devices with which you have conﬁgured it to communicate. Use the procedure that follows to edit these parameters.

Although you can edit Resource parameters either in group mode or in member mode, usually it is best to conﬁgure Resource parameters in group mode because they are identical for all members of a router redundancy group. The exception is if you use router redundancy with wide area networks (refer to Example 3 in Appendix B). In this case you conﬁgure resources differently among members of a router redundancy group.

5-12 117346-A Rev. A

Configuring Router Redundancy

To edit Resource parameters:

1. Choose Protocols > Edit Router Redundancy > Resources in the Circuit

Deﬁnition window.

The RREDUND Router Redundancy Resource List window opens

igure 5-6).

Figure 5-6. RREDUND Router Redundancy Resource List Window

Click on Add.

The Router Redundancy Resource window opens (F

117346-A Rev. A 5-13

igure 5-7).

Configuring Interface and Router Redundancy

Figure 5-7. Router Redundancy Resource Window

Enter the IP address of the device you want to conﬁgur e as a r esour ce f or

this router redundancy group.

4. Click on OK.

The RREDUND Router Redundancy Resource List window opens. The IP address you entered is highlighted in the list box. Site Manager supplies default values for all parameters.

5. Enter values for any parameters you want to edit, using the descriptions

that follow this procedure for guidelines.

6. Repeat Steps 2 through 5 to conﬁgure additional resources.

7. Click on Done to exit the window and return to the Circuit Deﬁnition

window.

5-14 117346-A Rev. A

Configuring Router Redundancy

Router Redundancy Resource Parameters

Use the following descriptions as guidelines when you edit router redundancy resource parameters.

Parameter: Enable Status Update

Default: Enable

Options: Enable

Function: This parameter is automatically set to Enable when you choose Router

Redundancy from the Select Protocols window. If you set this parameter to Disable, you prevent the router from checking on the av ailability of the devices with which you conﬁgure it to communicate.

Instructions: Accept the default, Enable.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.3.1.6

Parameter: Ping Interval

Default: 600 seconds

Options: 1 to 86,399 seconds

Function: Speciﬁes the amount of time, in seconds, that the router waits between

attempts to ping the devices with which you conﬁgured it to communicate. The parameter applies when all is functioning normally.

Instructions: Accept the default, or choose another value in the speciﬁed range.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.3.1.7

| Disable

Parameter: Ping Retry Count

Default: 3

Options: 1 to 9

Function: Speciﬁes the number of times that the primary router tries to ping a de vice

before it determines that the device is unreachable.

Instructions: Accept the default, or choose another value in the speciﬁed range.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.3.1.8

117346-A Rev. A 5-15

Configuring Interface and Router Redundancy

Parameter: Ping Timeout

Default: 5 seconds

Options: 1 to 10 seconds

Function: Speciﬁes the amount of time, in seconds, that the router waits between

attempts to ping the devices with which you conﬁgured it to communicate. This parameter applies when a prior ping has been unsuccessful.

Instructions: Accept the default, or choose another value in the speciﬁed range.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.3.1.9

5-16 117346-A Rev. A

Applying a Group Conﬁguration File

To apply the group conﬁguration ﬁle template to each member of a router redundancy group:

1. In the main Site Manager window (refer to Figure 5-1), choose Tools >

Router Redundancy > Member Conﬁguration.

The standard ﬁle selection window opens.

2. Navigate through the directory structure, and choose the conﬁguration

ﬁle, template.

3. Click on Open File.

The Conﬁguration Manager window opens, but this time in member mode

igure 5-8).

Configuring Router Redundancy

Figure 5-8. Conﬁguration Manager Window in Member Mode

The circuit you previously selected for group conﬁguration is shaded or in green.

4. Choose Protocols > Router Redundancy > Member Conﬁguration in the

Conﬁguration Manager window (F

117346-A Rev. A 5-17

igure 5-9).

Configuring Interface and Router Redundancy

Figure 5-9. Conﬁguration Manager Window for Member Conﬁguration

The R.R. Member Global Parameters Conﬁguration window opens

igure 5-10).

Figure 5-10. R.R. Member Global Parameters Conﬁguration Window

5-18 117346-A Rev. A

Configuring Router Redundancy

Enter values for the member global parameters, using the descriptions

that follow this procedure for guidelines.

6. Click on OK when you are done.

The Conﬁguration Manager window opens (r

7. Choose File > Save As.

The Save Conﬁguration File window opens (F

Figure 5-11. Save Conﬁguration File Window

Enter Router1.conﬁg as the ﬁle name and click on Save.

Repeat Steps 1

through 8, using a different member ID and Router2.conﬁg as the

efer to Figure 5-9).

igure 5-11).

base ﬁle name. Do this for each member of a redundancy group.

Note: Every member of a router redundancy group should use the ﬁlename

extension .conﬁg for its router redundancy conﬁguration ﬁle. If there is a power failure, all members should boot from the same router redundancy conﬁguration.

117346-A Rev. A 5-19

Configuring Interface and Router Redundancy

Router Redundancy Member Global Parameters

Use the following descriptions as guidelines when you edit router redundancy member global parameters.

Parameter: Enable

Default: Enable

Options: Enable

Function: This parameter is automatically set to Enable when you choose Router

Redundancy from the Select Protocols window. If you set this parameter to Disable, you temporarily disable router redundancy on the router without deleting your conﬁguration ﬁle.

Instructions: Choose Disable to disable router redundancy on this router.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.1.2

Parameter: Member ID

Default: 1

Options: 1 to 128

Function: Speciﬁes the identiﬁcation number for this member of the router

redundancy group. Each member ID number in a group must be unique. For example, if there are two routers in a redundancy group, one router could have a member ID of 1 and the other could have a member ID of 2. The role-change rules use the member ID to determine a router’s priority to become the primary router if the Priority parameter for both routers is set to the same value.

Instructions: Enter a number from 1 to 128 that you have not already assigned to a

member of this redundancy group.

| Disable

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.1.5

5-20 117346-A Rev. A

Parameter: Priority

Default: 1

Options: 1 to 128

Function: Indicates this router’s priority to become primary router; the higher the

value, the higher the priority . The router with the highest priority becomes the primary router. If two routers have the same priority, the router with the lower member ID number has higher priority to become the primary router.

Instructions: Enter a number from 1 to 128.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.1.14

Parameter: Force Role Switch

Default: Don’t Switch

Configuring Router Redundancy

Options: Don’t Switch

| Switch

Function: Forces a router to switch out of the primary role when another member of

the redundancy group would make a better primary router, or prevents a router from doing so. This parameter is valid only for manual role switching.

Instructions: Choose Don’t Switch or Switch.

MIB Object ID: 1.3.6.1.4.1.18.3.5.17.1.10

Note: If a slot fails and the software cannot locate the conﬁguration ﬁle and

executable image on the volume you speciﬁed, the software searches all volumes to locate these ﬁles. We recommend that you store the image on multiple volumes to be readily available if a slot fails.

117346-A Rev. A 5-21

Configuring Interface and Router Redundancy

Sending the Conﬁguration Files to the Routers

You have now created conﬁguration ﬁles for Router 1 and Router 2 to use members of a router redundancy group. To send these ﬁles to the appropriate routers, copy the ﬁles to the router Flash card using FTP or TFTP. Copy Router1.cfg to Router 1, and Router2.cfg to Router 2.

Conﬁguring Router Redundancy on Model 5380 Routers

You can use router redundancy on a Model 5380 router in several different ways because of this router’s versatility.

A Model 5380 router may logically be a single-slot router among other single-slot routers on the same module, or all the slots may logically be ports on the same router.

Conﬁguring Router Redundancy on One 5380 Router

If you are working with a Model 5380 as a single-slot router, you can conﬁgure different slots on the same router module as members of a router redundancy group. However, the slot number is incorporated in the conﬁguration, so it is impossible to make identical conﬁguration ﬁles for any two slots on the module. Therefore, you must create two group conﬁguration ﬁles, exactly the same except for the member ID. The following steps describe this procedure:

1. Create the group mode conﬁguration ﬁle for the ﬁrst slot and save it as

Discovery1.cfg.

2. Create a second group mode conﬁguration ﬁle for the second slot,

identical to the ﬁrst ﬁle, including the same group ID, and save it as Discovery2.cfg. If you edited any parameters in Discovery1.cfg, make the same choices for Discovery2.cfg.

3. Open each of these ﬁles in Member Mode, and assign each a unique

member ID. Save each ﬁle.

4. Copy the ﬁles to the router’s Flash card.

5-22 117346-A Rev. A

Configuring Router Redundancy

Conﬁguring Router Redundancy on Different 5380 Routers

You can conﬁgure router redundancy so that a slot on one Model 5380 backs up either the same slot or a different slot on another 5380:

• To back up the same slot on another 5380, conﬁgure router redundancy in the usual way, following the directions at the beginning of this chapter.

• To back up a different slot on another 5380, you must create and use two group conﬁguration ﬁles, following the directions in the previous section, “Conﬁguring Router Redundancy on One 5380 Router.”

Removing Router Redundancy

To remove router redundancy from a circuit or from an entire router:

1. Create a new conﬁguration ﬁle or modify the existing conﬁguration ﬁle in

local or remote mode.

2. Reboot the router.

117346-A Rev. A 5-23

Appendix A

Site Manager Default Parameter Settings

This appendix lists the Site Manager default parameter settings for router redundancy. Refer to Cha

Table A-1. Router Redundancy Group Global Parameters

Parameter Default

Enable Enable Send PDU Enable Enable Primary MAC Address None Group ID 1 Automatic Role Switching Auto Hello Timer 2 seconds Timeout Threshold 5 Good Bid Count 3 Bid Duration 45 seconds Role Switch Delay Period 5 seconds

pter 5 for instructions on editing these parameters.

117346-A Rev. A A-1

Configuring Interface and Router Redundancy

Table A-2. Router Redundancy Member Global Parameters

Parameter Default

Enable Enable Member ID 1 Priority 1 Force Role Switch Don’t Switch

Table A-3. Router Redundancy Resource Parameters

Parameter Default

Enable Status Update Enable Ping Interval 600 seconds Ping Retry Count 3 Ping Timeout 5 seconds

A-2 117346-A Rev. A

Router Redundancy Examples

This appendix contains three examples of router conﬁgurations that use router redundancy.

Example 1: Two Routers at the Same Site

This example shows how router redundancy works in a conﬁguration with two routers in the redundancy group, both in the same location. F two routers conﬁgured as a redundancy group in an Ethernet or FDDI network.

Appendix B

igure B-1 illustrates

Router A Router B

FDDI

RRE0001A

Figure B-1. Router Redundancy: Two Routers at the Same Site

Router Bootup

Upon router bootup, both members of the redundancy group are in the secondary role. They bid to determine which of the routers will assume the primary role

efer to Chapter 1). When the bidding time expires, the selected primary member

(r switches into the primary role.

117346-A Rev. A B-1

Configuring Interface and Router Redundancy

Possible Scenarios

The sections below describe possible scenarios and how they would affect the redundant routers.

Secondary Router Degraded

Degradation of the secondary router’ s interface and ability to reach resources does not affect the current operation of the primary router. This change does affect the primary and best-secondary selection process because the degraded secondary router has a lesser chance to become primary.

Secondary Router Becomes Inoperable

Degradation of the secondary router to the extent that it is inoperable does not affect the operation of the primary router. However, if the primary router detects local faults, it must remain primary and continue data transfer as best it can.

Primary Router Degraded

If the degree of degradation in the primary router is so slight that it is still the best primary router, no change occurs.

If the degradation is such that the current primary router is no longer the best primary, role switch to a new primary may occur, depending on the availability of a secondary router, and on how you have set the Automatic Role Switching parameter. The primary and best-secondary selection process is the same as during initial bootup.

Primary Router Fails

The sudden failure of the primary router causes the best secondary router to switch roles to primary . Because the primary and best-secondary selection process is performed continuously and involves all members of the router redundancy group, no bidding process need occur at this time, and the switch occurs with minimal delay.

B-2 117346-A Rev. A

Possible Complications

The following sections describe complications that can occur when you use router redundancy .

Router Boots and Cannot Detect Another Member

If a member of a router redundancy group boots and cannot detect any other member of its redundancy group within the bidding period, it switches roles to become the primary router, because it is the only member from which to select the primary .

Second Router Boots After First Router’s Bidding Timer Expires

If the ﬁrst router has booted and a second router boots after the ﬁrst router’s bidding period expires, the ﬁrst router may be in the process of switching roles to become the primary router. During the switching process, the ﬁrst router does not send PDUs, so when the second router boots and begins its own bidding period, it may not detect the ﬁrst router until the ﬁrst router has completed the role switch. To avoid a situation in which both routers switch roles to become primary, set the bidding period for a longer time than the time required to perform a role switch.

Router Redundancy Examples

Manual versus Auto Role Switching

If the ﬁrst router has booted and a second router boots after the ﬁrst router’s bidding period expires, and if you conﬁgured the router to use manual role switching, the ﬁrst router continues to act as the primary router even if the second router would be a better primary. The software alerts you, and it is up to you to initiate the role switch. If you conﬁgure the router to use auto role switching, the routers perform the role switch automatically. If you conﬁgure the router to use one-shot auto, the routers perform the role switch automatically once; after that a switch occurs only when an interface fails or when a resource becomes unreachable. If you conﬁgure the router to use switch on failure, a switch occurs only when an interface fails or when a resource becomes unreachable.

During manual role switching, a secondary router switches its role to primary if it does not detect a primary router in the group.

117346-A Rev. A B-3

Configuring Interface and Router Redundancy

Example 2: Three Routers at the Same Site

Figure B-2 illustrates a router redundancy group with three routers at the same

site.

Router A

Figure B-2. Router Redundancy: Three Routers at the Same Site

Router B

FDDI

Router C

RRE0002A

The only difference between having two members and three members in a router redundancy group is that the best-secondary selection process becomes meaningful.

Any degradation of a secondary member may cause a new best secondary to be selected. Because the best-secondary selection process occurs upon any state change within the router redundancy group, the designation of the best-secondary router is current at all times.

B-4 117346-A Rev. A

Router Redundancy Examples

Example 3: Router Redundancy with Wide Area Networks

Bay Networks router redundancy services do not currently allow conﬁguration of a wide area network (WAN) interface as a backed-up or redundant interface.

You can circumvent this limitation for IP-based networks only. Refer to

igure B-3 as you read the following explanation.

Remote router

Modem

FDDI

Router A

Router B

RRE0003B

Figure B-3. Router Redundancy with Wide Area Networks

117346-A Rev. A B-5

Configuring Interface and Router Redundancy

To provide redundancy for this WAN:

1. Deﬁne the remote interface on the other side of the WAN as a resource in

the conﬁguration of Router A.

2. Set the Automatic Role Switching parameter to Auto for Router B.

These two steps allow the primary and best-secondary router selection process to consider the WAN interface as a resource, and to use the unavailability of this resource to trigger role switching.

3. Conﬁgure Router B to have a higher priority than Router A to become

the primary router.

Router B will assume the primary role only when Router A, with the lower priority to be primary, loses the remote router as a resource.

4. Conﬁgure Router B with a dial-on-demand circuit, but disable outbound

calling.

Router B is now capable of receiving a dialed call. For instructions on conﬁguring dial lines, refer to Conﬁguring Dial Services.

5. Conﬁgure the remote router with dial backup.

The remote router will only initiate a call to Router B if the WAN line to Router A fails.

If the WAN interface becomes nonfunctional for any reason, the resource deﬁned for it is unreachable. This causes Router A, the current primary router, to cease being the best primary router, and a role switch occurs. Router B, with its dial-up connection to the remote router, becomes the primary router. Note, however, that because Router A and Router B must have identical conﬁgurations, the remote router must initiate the dial backup connection.

The effect is that the dial-up connection is a redundant interface for the WAN connection. Note that in this case the dial-up synchronous interface between Router B and the remote router is active only when the WAN interface fails.

Router A and Router B can be at the branch ofﬁce; the remote router is at the central or regional ofﬁce.

B-6 117346-A Rev. A

Router Redundancy Examples

Example 4: Router Redundancy with Ethernet Switches

Figure B-4 illustrates a router redundancy group with primary and secondary

™

routers connected to BayStack

Ethernet switches, in this example a BayStack 281xx Fast Ethernet switch. This conﬁguration allows you to use router redundancy with a bridged or frame-switched network.

Router A

Hub A

281XX switch 281XX switch

Router B

Hub B

RRE0005A

Figure B-4. Router Redundancy with 281xx Fast Ethernet Switches

The routers have the same MAC address, and their redundancy conﬁgurations are identical in all other ways. Using connected hubs allows each switch to use only one port to connect to both routers. Because the switches use the spanning tree algorithm, only one of the switch ports is in use at any time. Neither switch can detect that its partner switch is also connected to the same router redundancy group. Neither switch can detect that there are two different routers using the same MAC address on different ports. The switches therefore accept or send data regardless of which router is acting in the primary role.

You can conﬁgure router redundancy with only one hub and one port of one 281xx switch, but a single point of failure then exists.

117346-A Rev. A B-7

Appendix C

Worksheets for Conﬁguring Router Redundancy

These worksheets assume a router redundancy group of three routers, and can help you conﬁgure your own router redundancy group.

Table C-1. Group Mode Planning Worksheet

Planning Issue/Parameter Redundancy Group

Router Type All in group must be the same; for e xample, BCN, BLN,

ASN Hardware Conﬁguration

CPU and interface module type, slot and port locations of the backed-up interfaces must be the same

Software Conﬁguration Software version and loadable modules conﬁgured

must be the same Primary MAC Address for Backed-Up Interfaces

4. IP Addresses for Backed-Up Interfaces

4. Group ID

Automatic Role Switching Hello Timer Timeout Threshold Good Bid Count Bid Duration

117346-A Rev. A C-1

Configuring Interface and Router Redundancy

Table C-2. Resource Planning Worksheet

Planning Issue/Parameter Router A Router B Router C

Enable Status Update Ping Interval Ping Retry Count Ping Timeout IP Addresses for Resources

Table C-3. Member Mode Planning Worksheet

Parameter Router A Router B Router C

Member ID Priority to Become Primary Force Role Switch

C-2 117346-A Rev. A

Setting BofL Parameters

BofL parameters affect the speed of detecting failed interfaces. You set BofL parameters from the Edit CSMA/CD Parameters window in Site

Manager. From the Conﬁguration Manager window, the path is Circuits > Circuit List window > Lines window > Edit CSMA/CD Parameters window (F parameter descriptions that follow as guides when you edit these parameters.

Appendix D

BofL Parameters

Circuits > Edit

Edit > Circuit Deﬁnition window > Lines > Edit

igure D-1). Use the

117346-A Rev. A D-1

Configuring Interface and Router Redundancy

Figure D-1. Edit CSMA/CD Parameters Window

Parameter: BOFL Enable

Default: Enable

Options: Enable

Function: When set to Enable, the router sends Breath of Life polling messages

from this system to all systems on the local network.

Instructions: Set to Enable or Disable. We recommend that you enable BofL.

MIB Object ID: 1.3.6.1.4.1.18.3.4.1.1.59

D-2 117346-A Rev. A

| Disable

Parameter: BOFL Timeout

Default: 5 seconds

Options: 1 to 60 seconds

Function: Speciﬁes the time between transmissions of Breath of Life messages from

this Ethernet interface. Timeout occurs if ﬁve periods elapse without a successful BofL message transmission. When timeout occurs, the router disables and reenables this Ethernet interface.

This parameter is valid only if you set BofL Enable to Enable.

Instructions: Accept the default, or specify a new value up to 60 seconds.

MIB Object ID: 1.3.6.1.4.1.18.3.4.1.1.59

Parameter: BOFL Retries

Default: 5 (4 when the interface is conﬁgured for Router Redundancy)

Options: 1 to 5 retries

Function: Speciﬁes the number of BofL messages this interface can retransmit

before the router declares the circuit down.

BofL Parameters

Instructions: Either accept the default, or specify a lower value. Use this parameter in

conjunction with the BOFL Timeout Divisor and BOFL Timeout parameters to decrease the time it takes the router to declare an interface down.

MIB Object ID: 1.3.6.1.4.1.18.3.4.1.1.59

117346-A Rev. A D-3

Configuring Interface and Router Redundancy

Parameter: BOFL Timeout Divisor

Default: 1 (10 when the interface is conﬁgured for Router Redundancy)

Options: An integer 1 to 59, less than or equal to the value of the BOFL Timeout

parameter

Function: The BOFL Timeout parameter speciﬁes a time period between

transmissions of Breath of Life messages from this Ethernet interface. Beginning with Router Software Version 11.01, the actual time between BofL transmissions is the value of the BOFL Timeout parameter divided by the value of the BOFL T imeout Di visor parameter. When set to a value greater than 1, this parameter reduces the value of BOFL Timeout.

When you conﬁgure Router Redundancy on an interface, Site Manager automatically sets this parameter to reduce the time between BofL transmissions. If the circuit goes down, the interface reaches the BOFL Retries value sooner , thus reducing the time it takes the router to declare a circuit down.

Instructions: Increase the value of this parameter if you want line status to be detected

in less than 1-second intervals. For example, with the BOFL Timeout parameter set to 5 seconds and the

BOFL Timeout Divisor set to 10, the router sends a BofL message every 0.5 seconds (5 di vided by 10). W ith BOFL T imeout set to 5 seconds and the BOFL Timeout Divisor set to 1, transmissions occur every 5 seconds.

MIB Object ID: 1.3.6.1.4.1.18.3.4.1.1.60

D-4 117346-A Rev. A

Numbers

Index

100-Mb Ethernet, 3-2 10-Mb Ethernet, 3-2

active interface, deﬁned, 1-1 adding interfaces to a group, 4-6 AppleTalk, 3-2 applying a group conﬁguration ﬁle, 5-17 auto role switching, B-3 Automatic Role Switching parameter, 5-10, B-2

Bay Networks Press, xvi Bid Duration parameter, 5-11 bidding period, B-3 bidding process for router redundancy, 2-2 to 2-5 BOFL parameters

role change speed, 1-3, 2-6

BofL parameters, D-1

changing out of the primary role (router

redundancy), 2-6

conﬁguration examples for router redundancy,

B-1 to B-7

conﬁguration ﬁles

applying to routers, 5-17 creating, 5-2 sending to the routers, 5-22

conﬁguring

interface redundancy, 4-1 to 4-7 resources for redundant routers, 5-12 to 5-16 router redundancy, 5-1 to 5-23

requirements, 3-3

customer support

programs, xvi Technical Solutions Centers, xvii

dedicated secondary router, deﬁned, 2-1 deleting interfaces from a group, 4-6 designated primary interface, deﬁned, 1-1

Enable parameter (group), 5-6, 5-8 Enable parameter (member), 5-20 Enable Status Update parameter (resource), 5-15 enabling

interface redundancy, 4-1 router redundancy, 5-2

examples of router redundancy conﬁgurations,

B-1 to B-7

FDDI, 3-2 Force Role Switch parameter, 5-21

117346-A Rev. A Index-1

Good Bid Count parameter, 5-11 group conﬁguration ﬁles

applying, 5-17

creating, 5-2 group conﬁguration mode, 5-6 group global parameters

Automatic Role Switching, 5-10

Bid Duration, 5-11

Enable, 5-8

Good Bid Count, 5-11

Group ID, 5-9

Hello Timer, 5-10

Primary MAC Address, 5-9

Role Switch Delay Period, 5-12

Send PDU Enable, 5-9

Timeout Threshold, 5-11 Group ID parameter, 5-9

Hello Timer parameter, 5-10 hot standby, 1-3

LAN interfaces

100-Mb Ethernet, 3-2 10-Mb Ethernet, 3-2 FDDI, 3-2 Token Ring, 3-2

manual role switching, B-3 member global parameters

Enable, 5-20 Force Role Switch, 5-21 Member ID, 5-20

Priority, 5-21 Member ID parameter, 5-20 member mode, 5-17

network planning for redundancy services, 3-1,

C-1

implementation notes, 3-1 interface failure in router redundancy, 2-7 interface redundancy

adding or deleting interfaces, 4-6 combined with router redundancy, 3-3 conﬁguring, 4-1 to 4-7 hot standby, 1-3 overview, 1-1 priority rules, 1-2 protocols supported, 3-2 removing from a circuit, 4-7 switching rules, 1-2

warm standby, 1-4 IP, 3-2 IPX, 3-2

Index-2 117346-A Rev. A

one-shot auto role switching, B-3

parameter default settings, A-1 PDU ﬂow diagram, 2-2 to 2-5 PDUs, 2-2 Ping Interval parameter, 5-15 Ping Retry Count parameter, 5-15 Ping Timeout parameter, 5-16 planning your network for redundancy services,

3-1 Primary MAC Address parameter, 5-9 primary router

changing out of primary role, 2-6 deﬁned, 2-1

Priority parameter, 5-21 priority rules for interface redundancy, 1-2

protocol data units (PDUs)

deﬁned, 2-2 used in role bidding, 2-2 to 2-5

publications

ordering, xvi

redundancy protocol, 2-2 to 2-5 redundant interface, deﬁned, 1-1 removing interface redundancy from a circuit,

4-7 removing router redundancy from a circuit or a

router, 5-23 resource availability, 2-7 resource parameters

Enable Status Update, 5-15 Ping Interval, 5-15 Ping Retry Count, 5-15

Ping Timeout, 5-16 resources, conﬁguring, 5-12 to 5-16 Role Switch Delay Period parameter, 5-12 role switching, B-3 router redundancy

and wide area network (WAN) interfaces, B-5

bidding process, 2-2 to 2-5

combined with interface redundancy, 3-3

conﬁguration examples, B-1 to B-7

conﬁguring, 5-1 to 5-23

dedicated secondary router, 2-1

group global parameter descriptions, 5-8 to

5-12

member global parameters descriptions, 5-20

to 5-21 primary router, 2-1 protocols supported, 3-2 removing, 5-23 requirements, 3-3 resource parameter descriptions, 5-15 to 5-16 role changes, 2-6 worksheets, C-1

117346-A Rev. A Index-3

Send PDU Enable parameter, 5-6, 5-9 sending the conﬁguration ﬁles to the routers, 5-22 source route bridging, 3-2 spanning tree bridging, 3-2 switch on failure role switching, B-3 switching rules for interface redundancy, 1-2

Technical Solutions Centers, xvii template, group conﬁguration ﬁle, creating, 5-2 Timeout Threshold parameter, 5-11 Token Ring, 3-2

VINES, 3-2

warm standby, 1-4 wide area network (WAN) interfaces and router

redundancy, B-5

worksheets for router redundancy, C-1

Avaya Interface and Router Redundancy User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Figures

Tables

About This Guide

Before You Begin

Conventions

Acronyms

Ordering Bay Networks Publications

Bay Networks Customer Service

How to Get Help

Active Interface

Redundant Interfaces

Interface Roles

Determining the Active Interface

Determining Priority

Active Interface MAC Address

Primary Router

Dedicated Secondary Router

Redundancy Protocol

Role Change

Router Failure

Interface Failure

Resource Availability

Requirements

Planning Your Network

Protocols Supported

LAN Interfaces

Router Redundancy Requirements

Using Interface and Router Redundancy in Combination

Compatibility

Enabling Interface Redundancy

Adding and Deleting Interfaces within a Group

Removing Interface Redundancy from a Circuit

Enabling Router Redundancy

Router Redundancy Group Parameters

Router Redundancy Resource Parameters

Router Redundancy Member Global Parameters

Removing Router Redundancy

Example 1: Two Routers at the Same Site

Router Bootup

Possible Scenarios

Possible Complications

Example 2: Three Routers at the Same Site

Example 3: Router Redundancy with Wide Area Networks

Example 4: Router Redundancy with Ethernet Switches

Setting BofL Parameters

Index