Avaya Remote Access User Manual

Conﬁguring Remote Access

Router Software Version 11.00 Rev. 4n Site Manager Sofware Version 5.00 Rev. 4n

Part No. 114084 Rev. A November 1996

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 take 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.

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.

Notice for All Other Executive Agencies

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.

Trademarks of Bay Networks, Inc.

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

Third-Party T rademarks

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

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).

114084 Rev. A

USA Requirements Only

Federal Communications Commission (FCC) Compliance Notice: Radio Frequency Notice

This equipment generates, uses, and can radiate radio-frequency energy. If you do not install and use this equipment according to the instruction manual, this product may interfere with radio communications. This product has been tested and found to comply with the limits for a Class A computing device, pursuant to Subpart J of Part 15 of FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Operating this equipment in a residential area is likely to interfere with radio communications; in which case, the user, at his/her own expense, must correct the interference.

Shielded-compliant cables must be used with this unit to ensure compliance with the Class A limits.

European Requirements Only

EN 55 022 Declaration of Conformance

This is to certify that the Bay Networks products in this book are shielded against the generation of radio interference in accordance with the application of Council Directive 89/336/EEC, Article 4a. Conformity is declared by the application of EN 55 022:1987 Class A (CISPR 22:1985/BS 6527:1988).

This is a Class A product. In a domestic en vironment this product may cause radio interference in which case the user may be required to take adequate measures.

EN 55 022 Declaration of Conformance

114084 Rev. A

iii

Japan/Nippon Requirements Only

Voluntary Control Council for Interference (VCCI) Statement

This equipment is in the 1st category (information equipment to be used in commercial and/or industrial areas) and conforms to the standards set by the Voluntary Control Council for Interference by Data Processing Equipment and Electronic Ofﬁce Machines that are aimed at preventing radio interference in commercial and/or industrial areas.

Consequently, when this equipment is used in a residential area or in an adjacent area thereto, radio interference may be caused to equipment such as radios and TV receivers.

Compliance with the applicable regulations is dependent upon the use of shielded cables. The user is responsible for procuring the appropriate cables. Read instructions for correct handling.

114084 Rev. A

Canada Requirements Only

Canada CS-03 Rules and Regulations

Note:

The Canadian Department of Communications label identiﬁes certiﬁed equipment. The certiﬁcation means that the equipment meets certain telecommunications network protective operations and safety requirements. The Department does not guarantee the equipment will operate to the user's satisfaction.

Before installing this equipment, users should ensure that it is permissible to be connected to the facilities of the local telecommunications company. The equipment must also be installed using an acceptable method of connection. In some cases, the company's inside wiring associated with a single line individual service may be extended by means of a certiﬁed connector assembly (telephone extension cord). The customer should be aware that compliance with the above conditions may not prevent the degradation of service in some situations.

Repairs to certiﬁed equipment should be made by an authorized Canadian maintenance facility designated by the supplier. Any repairs or alterations made by the user to this equipment or equipment malfunctions, may give the telecommunications company cause to request the user to disconnect the equipment.

Users should ensure for their own protection that the electrical ground connections of the power utility, telephone lines and internal metallic water pipe system, if present, are connected together. This precaution may be particularly important in rural areas.

Caution:

inspection authority, or electrician, as appropriate.

Canada CS-03 — Règles et règlements

Note:

qu’il respecte certaines exigences de sécurité et de fonctionnement visant les réseaux de télécommunications. Le ministère ne garantit pas que l’appareillage fonctionnera à la satisfaction de l’utilisateur.

Avant d’installer l’appareillage, s’assurer qu’il peut être branché aux installations du service de télécommunications local. L’appareillage doit aussi être raccordé selon des méthodes acceptées. Dans certains cas, le câblage interne du service de télécommunications utilisé pour une ligne individuelle peut être allongé au moyen d’un connecteur certiﬁé (prolongateur téléphonique). Le client doit toutefois prendre note qu’une telle installation n’assure pas un service parfait en tout temps.

Les réparations de l’appareillage certiﬁé devraient être conﬁées à un service d’entretien canadien désigné par le fournisseur. En cas de réparation ou de modiﬁcation effectuées par l’utilisateur ou de mauvais fonctionnement de l’appareillage, le service de télécommunications peut demander le débranchment de l’appareillage.

Pour leur propre sécurité, les utilisateurs devraient s’assurer que les mises à la terre des lignes de distribution d’électricité, des lignes téléphoniques et de la tuyauterie métallique interne sont raccordées ensemble. Cette mesure de sécurité est particulièrement importante en milieu rural.

Attention:

aux pouvoirs de réglementation en cause ou à un électricien, selon le cas.

Users should not attempt to make such connections themselves, but should contact the appropriate electric

L’étiquette du ministère des Communications du Canada indique que l’appareillage est certiﬁé, c’est-à-dire

Les utilisateurs ne doivent pas procéder à ces raccordements eux-mêmes mais doivent plutôt faire appel

114084 Rev. A

Canada Requirements Only

(continued)

D. O. C. Explanatory Notes: Equipment Attachment Limitations

The Canadian Department of Communications label identiﬁes certiﬁed equipment. This certiﬁcation meets certain telecommunication network protective, operational and safety requirements. The department does not guarantee the equipment will operate to the users satisfaction.

Before installing the equipment, users should ensure that it is permissible to be connected to the facilities of the local telecommunications company. The equipment must also be installed using an acceptable method of connection. In some cases, the company’s inside wiring associated with a single line indi vidual service may be e xtended by means of a certiﬁed connector assembly (telephone extension cord). The customer should be aware that compliance with the above condition may not prevent degradation of service in some situations.

Repairs to certiﬁed equipment should be made by an authorized Canadian maintenance facility designated by the supplier. Any repairs or alterations made by the user to this equipment, or equipment malfunctions, may give the telecommunications company cause to request the user to disconnect the equipment.

Caution:

inspection authority, or electrician, as appropriate.

Users should not attempt to make such connections themselves, but should contact the appropriate electrical

Notes explicatives du ministère des Communications: limites visant les accessoires

L’étiquette du ministère des Communications du Canada indique que l’appareillage est certiﬁé, c’est-à-dire qu’il respecte certaines exigences de sécurité et de fonctionnement visant les réseaux de télécommunications. Le ministère ne garantit pas que l’appareillage fonctionnera à la satisfaction de l’utilisateur.

Attention:

aux pouvoirs de réglementation en cause ou à un électricien, selon le cas.

Les utilisateurs ne doivent pas procéder à ces raccordements eux-mêmes mais doivent plutôt faire appel

114084 Rev. A

Canada Requirements Only

(continued)

Canadian Department of Communications Radio Interference Regulations

This digital apparatus (Access Feeder Node, Access Link Node, Access Node, Access Stack Node, Backbone Concentrator Node, Backbone Concentrator Node Switch, Backbone Link Node, Backbone Link Node Switch, Concentrator Node, Feeder Node, Link Node) does not exceed the Class A limits for radio-noise emissions from digital apparatus as set out in the Radio Interference Regulations of the Canadian Department of Communications.

Réglement sur le brouillage radioélectrique du ministère des Communications

Cet appareil numérique (Access Feeder Node, Access Link Node, Access Node, Access Stack Node, Backbone Concentrator Node, Backbone Concentrator Node Switch, Backbone Link Node, Backbone Link Node Switch, Concentrator Node, Feeder Node, Link Node) respecte les limites de bruits radioélectriques visant les appareils numériques de classe A prescrites dans le Réglement sur le brouillage radioélectrique du ministère des Communications du Canada.

114084 Rev. A

vii

T1 Service Compliance Statements

T1 Service

NOTE: This T1 Service notice applies to you onl

(MCT1) Link Module (which provides an internal CSU).

This equipment complies with Part 68 of FCC Rules. Please note the following:

1. You are required to request T1 service from the telephone company before you connect the CSU to a T1 network.

When you request T1 service, you must provide the telephone company with the following data:

• The Facility Interface Code Provide the telephone company with both codes below: — 04DU9-B (1.544 MB D4 framing format)

— 04DU9-C (1.544 MB ESF format) The telephone company will select the code it has available.

• The Service Order Code: 6.0F

• The required USOC jack: RJ48C

• The make, model number, and FCC Registration number of the CSU.

2. Your telephone company may make changes to its facilities, equipment, operations, or procedures that could affect the proper functioning of your equipment. The telephone company will notify you in advance of such changes to give you an opportunity to maintain uninterrupted telephone service.

3. If your CSU causes harm to the telephone network, the telephone company may temporarily discontinue your service. If possible, they will notify you in advance, but if advance notice is not practical, you will be notiﬁed as soon as possible and will be informed of your right to ﬁle a complaint with the FCC.

4. If you experience trouble with the CSU, please contact Bay Networks Technical Response Center in your area for service or repairs. Repairs should be performed only by service personnel authorized by Bay Networks, Inc.

United States 1-800-2LAN-WAN Valbonne, France (33) 92-96-69-68 Sydney , Australia (61) 2-9927-8880 Tokyo, Japan (81) 3-5402-7041

5. You are required to notify the telephone company when you disconnect the CSU from the network and when you disconnect the BCNX or BLNX from the network.

y if you have received a single or dual port Multi-Channel T1

viii

114084 Rev. A

Bay Networks Software License

Note:

This is Bay Networks basic license document. In the absence of a software license agreement specifying varying terms, this license — or the license included with the particular product — shall govern licensee’s use of Bay Networks software.

This Software License shall govern the licensing of all software provided to licensee by Bay Networks (“Software”). Bay Networks will provide licensee with Software in machine-readable form and related documentation (“Documentation”). The Software provided under this license is proprietary to Bay Networks and to third parties from whom Bay Networks has acquired license rights. Bay Networks will not grant any Software license whatsoev er , either explicitly or implicitly, except by acceptance of an order for either Software or for a Bay Networks product (“Equipment”) that is packaged with Software. Each such license is subject to the following restrictions:

1. Upon delivery of the Software, Bay Networks grants to licensee a personal, nontransferable, none xclusiv e license to use the Software with the Equipment with which or for which it was originally acquired, including use at any of licensee’s facilities to which the Equipment may be transferred, for the useful life of the Equipment unless earlier terminated by default or cancellation. Use of the Software shall be limited to such Equipment and to such facility. Software which is licensed for use on hardware not offered by Bay Networks is not subject to restricted use on any Equipment, however, unless otherwise speciﬁed on the Documentation, each licensed copy of such Software may only be installed on one hardware item at any time.

2. Licensee may use the Software with backup Equipment only if the Equipment with which or for which it was acquired is inoperative.

3. Licensee may make a single copy of the Software (but not ﬁrmware) for safekeeping (archives) or backup purposes.

4. Licensee may modify Software (but not ﬁrmware), or combine it with other software, subject to the provision that those portions of the resulting software which incorporate Software are subject to the restrictions of this license. Licensee shall not make the resulting software available for use by any third party.

5. Neither title nor ownership to Software passes to licensee.

6. Licensee shall not provide, or otherwise make available, any Software, in whole or in part, in any form, to any third party. Third parties do not include consultants, subcontractors, or agents of licensee who have licensee’s permission to use the Software at licensee’s facility, and who have agreed in writing to use the Software only in accordance with the restrictions of this license.

7. Third-party owners from whom Bay Networks has acquired license rights to software that is incorporated into Bay Networks products shall have the right to enforce the provisions of this license against licensee.

8. Licensee shall not remove or obscure any copyright, patent, trademark, trade secret, or similar intellectual property or restricted rights notice within or afﬁxed to any Software and shall reproduce and afﬁx such notice on any backup copy of Software or copies of software resulting from modiﬁcation or combination performed by licensee as permitted by this license.

114084 Rev. A

Bay Networks Software License

9. Licensee shall not reverse assemble, reverse compile, or in any way reverse engineer the Software. [Note: For licensees in the European Community, the Softw are Directiv e dated 14 May 1991 (as may be amended from time to time) shall apply for interoperability purposes. Licensee must notify Bay Networks in writing of any such intended examination of the Software and Bay Networks may provide review and assistance.]

10. Notwithstanding any foregoing terms to the contrary, if licensee licenses the Bay Networks product “Site Manager,” licensee may duplicate and install the Site Manager product as speciﬁed in the Documentation. This right is granted solely as necessary for use of Site Manager on hardware installed with licensee’s network.

11. This license will automatically terminate upon improper handling of Software, such as by disclosure, or Bay Networks may terminate this license by written notice to licensee if licensee fails to comply with any of the material provisions of this license and fails to cure such failure within thirty (30) days after the receipt of written notice from Bay Networks. Upon termination of this license, licensee shall discontinue all use of the Software and return the Software and Documentation, including all copies, to Bay Networks.

12. Licensee’s obligations under this license shall survive expiration or termination of this license.

(continued)

114084 Rev. A

About This Guide

Before You Begin .............................................................................................................xxi

Where to Find AN, ANH, or ARN Information .................................................................xxii

Conventions ................................................................................................................... xxiii

Acronyms .......................................................................................................................xxiv

Ordering Bay Networks Publications ..............................................................................xxv

Technical Support and Online Services

Bay Networks Customer Service .................................................................................xxviii

Bay Networks Information Services ...............................................................................xxix

World Wide Web ......................................................................................................xxix

Customer Service FTP ............................................................................................xxix

Support Source CD ..................................................................................................xxx

CompuServe ............................................................................................................xxx

InfoFACTS ...............................................................................................................xxxi

How to Get Help ......................................................................................................xxxi

Chapter 1 Understanding Tools and Options

Software Management Tools ..........................................................................................1-1

Router Software ..............................................................................................................1-2

Boot Conﬁguration Options ............................................................................................1-3

The Boot Process ...........................................................................................................1-6

Network Boot ...........................................................................................................1-6

Getting an IP Address .......................................................................................1-6

Getting Kernel Image and Conﬁguration Files .................................................1-10

Local Boot ..............................................................................................................1-12

Conﬁguring the Initial IP Interface ..........................................................................1-13

114084 Rev. A

Chapter 2 Selecting the Boot Conﬁguration

Booting the Router for the First Time ..............................................................................2-1

EZ-Install .................................................................................................................. 2-2

Netboot .....................................................................................................................2-2

Local Boot ................................................................................................................2-3

Recommendations ...................................................................................................2-3

Booting the Router Routinely ..........................................................................................2-3

Netboot .....................................................................................................................2-3

Directed Netboot ......................................................................................................2-4

Local Boot ................................................................................................................2-5

Recommendations ...................................................................................................2-5

Completing a Startup Option ..........................................................................................2-6

EZ-Install .................................................................................................................. 2-6

Netboot .....................................................................................................................2-7

Directed Netboot ......................................................................................................2-8

Local Boot ................................................................................................................2-9

Chapter 3 Setting Up a UNIX Boot Server

Setting Up a BOOTP Server ...........................................................................................3-2

Copying the BOOTPD Program on Sun Workstations .............................................3-2

Setting Up BOOTP Sockets .....................................................................................3-2

Setting Up BOOTPD to Run .....................................................................................3-3

Setting Up BOOTPD to Respond to Routers ...........................................................3-3

Editing the bootptab File ....................................................................................3-4

Verifying Consistent BOOTP Service ................................................................3-9

Setting Up a TFTP Server ..............................................................................................3-9

Providing TFTPD Access to the Root Directory .......................................................3-9

Restricting TFTPD Access to a Speciﬁed Directory ...............................................3-10

Adding a TFTP User for an HP 9000 .....................................................................3-11

Setting Up Static Routes to Next-Hop Routers ......................................................3-11

Editing the inetd.conf File ................................................................................3-12

Verifying the Routes ........................................................................................3-12

Loading the Changes into Memory ..................................................................3-12

What to Do Next ...........................................................................................................3-13

xii

114084 Rev. A

Chapter 4 Conﬁguring Network Booting

Preparing Conﬁguration and Image Files .......................................................................4-2

Creating Conﬁguration Files .....................................................................................4-2

Preparing an Image .................................................................................................4-6

Enabling Netboot or Directed Netboot from Site Manager .............................................4-7

Netboot and Directed Netboot Parameters ..............................................................4-8

Conﬁguring a Netboot or Directed Netboot Interface ...................................................4-11

Netboot Interface Parameters ................................................................................4-14

Setting Up Routing Paths for Netboot ...........................................................................4-16

Enabling Router Interfaces .....................................................................................4-16

Creating BOOTP Relay Agent Forwarding Tables ..................................................4-17

BOOTP Relay Agent Interface Parameters ............................................................4-20

Creating the BOOTP Client Interface Table ..................................................................4-21

BOOTP Client Interface Parameters ......................................................................4-23

Chapter 5 Conﬁguring the Router as a Network Boot Client

Working with a Person at the AN/ANH/ARN Site ...........................................................5-2

Conﬁguring the Router Boot Source ...............................................................................5-2

bconﬁg Command Format ........................................................................................5-2

bconﬁg Command Examples ...................................................................................5-3

Conﬁguring the Netboot Interface ...................................................................................5-4

Conﬁguring an IP Synchronous Interface for Network Booting ................................5-4

Conﬁguring an Ethernet Interface for Network Booting ............................................5-6

Conﬁguring a Token Ring Interface for Network Booting ..........................................5-6

Enabling and Disabling Interfaces with ifconﬁg ........................................................5-7

ifconﬁg Command Examples ...................................................................................5-8

V erifying Y our Conﬁguration ............................................................................................5-9

What to Do Next ...........................................................................................................5-10

Chapter 6 Managing ANH Repeater Ports

Enabling and Disabling ANH Repeater Ports .................................................................6-1

Testing and Resetting ANH Repeater Ports ...................................................................6-4

Repeater Port Group Parameter Descriptions .........................................................6-5

114084 Rev. A

xiii

Chapter 7 Conﬁguring a Data Collection Module

Ethernet DCM and RMON Overview ..............................................................................7-1

Remote Network Monitoring (RMON) ......................................................................7-2

The RMON Groups ..................................................................................................7-3

Ethernet Statistics Group ...................................................................................7-3

History Control Group and Ethernet History Group ...........................................7-4

Host Group ........................................................................................................7-4

HostTopN Group ................................................................................................7-4

Matrix Group ......................................................................................................7-4

Filter Group ........................................................................................................7-4

Packet Capture Group .......................................................................................7-5

Alarm Group ......................................................................................................7-5

Event Group .......................................................................................................7-5

For More Information about RMON ..........................................................................7-5

Enabling a DCM Using Site Manager .............................................................................7-6

DCM Global Parameter Descriptions .......................................................................7-7

Managing the DCM Using Site Manager ......................................................................7-11

Activating the DCM ................................................................................................7-12

Disabling the DCM .................................................................................................7-12

Booting the DCM ....................................................................................................7-13

Changing the DCM Conﬁguration Parameters .......................................................7-13

Deleting the DCM Software Subsystem .................................................................7-14

Managing the DCM Using the Technician Interface ......................................................7-15

Changing DCM Conﬁguration Parameters .............................................................7-15

RMON Implementation Notes .......................................................................................7-16

RMON Applications ................................................................................................7-17

RMON Memory Use ...............................................................................................7-18

Interoperability Issues and Memory Use for RMON Groups ..................................7-18

Statistics Group ...............................................................................................7-19

History Group ..................................................................................................7-19

Host Group ......................................................................................................7-20

HostTopN Group ..............................................................................................7-21

Matrix Group ....................................................................................................7-21

Filter and Capture Groups ...............................................................................7-22

xiv

114084 Rev. A

Alarm and Event Group ...................................................................................7-23

Appendix A Troubleshooting Network Boot Problems

Solving Startup Problems .............................................................................................. A-1

Router Fails to Get IP Address ............................................................................... A-2

Upstream Router Not Receiving BOOTP Requests ......................................... A-2

Upstream Router Not Sending BOOTP Responses ......................................... A-2

Router Fails to Netboot ........................................................................................... A-3

Upstream Router Not Receiving BOOTP Requests ......................................... A-3

Router Not Sending BOOTP Responses .......................................................... A-4

BOOTP Server Not Sending BOOTP Responses ............................................ A-4

Router Fails to Perform Directed Netboot ............................................................... A-5

Router Netboots, but Fails to Load Applications ..................................................... A-5

Identifying Remote Connectivity Problems .................................................................... A-8

Displaying Messages from the AN/ANH/ARN Console ........................................... A-8

Displaying Statistics and Error Messages ............................................................... A-8

Guidelines for Using Packet Capture ...................................................................... A-9

Guidelines for Using a LAN Protocol Analyzer ........................................................ A-9

Resolving Connectivity Problems ................................................................................ A-10

Displaying Parameter Settings .............................................................................. A-10

Debugging the BOOTP Server .............................................................................. A-12

Verifying the BOOTP Server Setup ....................................................................... A-13

Displaying the BOOTP Server’s IP Routes ........................................................... A-15

Displaying the Number of Packets Forwarded and Dropped ................................ A-15

Quick Get Instructions .................................................................................... A-16

Technician Interface Instructions .................................................................... A-16

Maintaining the Router Software ................................................................................. A-16

Upgrading the Software Image ............................................................................. A-17

Restoring a Local File System .............................................................................. A-17

Appendix B Using the Local Boot Procedure

What Is Quick-Start? ..................................................................................................... B-1

Using the Worksheets .................................................................................................... B-2

Global Information Worksheet ................................................................................. B-3

114084 Rev. A

Router Protocol Worksheets ................................................................................... B-6

Wide Area Protocol Worksheets ........................................................................... B-10

Running the Quick-Start Script .................................................................................... B-14

Appendix C Implementation Notes

Hints .............................................................................................................................. C-1

Notes ............................................................................................................................. C-2

Network Conﬁguration Options ......................................................................................C-3

Ensuring Ethernet Network Compliance .................................................................C-3

Network Path Containing Three Repeaters ...................................................... C-4

Network Path Containing Four Repeaters ........................................................C-4

Conﬁguring a Single ANH .......................................................................................C-4

Conﬁguring Multiple Hubs .......................................................................................C-6

Conﬁguring an AUI Port .......................................................................................... C-7

Connecting the AUI Port to a Fiber Optic Backbone .........................................C-8

Connecting the AUI Port to a Coaxial Backbone ..............................................C-9

Index

xvi

114084 Rev. A

Figures

Figure 1-1. Getting an IP Address from a Bay Networks Standard Circuit or a Frame Relay

PVC in Direct Access Mode 1-8

Figure 1-2. Getting an Address from a PVC in Group Access Mode .........................1-9

Figure 1-3. Getting the Pathnames of the Kernel and Conﬁguration Files ...............1-10

Figure 1-4. Getting the Conﬁguration File ................................................................1-11

Figure 1-5. Getting the Kernel ..................................................................................1-12

Figure 1-6. Establishing an IP Network Interface .....................................................1-13

Figure 3-1. Sample bootptab File ...............................................................................3-8

Figure 4-1. Edit Netboot Global Parameters Window .................................................4-7

Figure 4-2. Netboot Interfaces Window ....................................................................4-11

Figure 4-3. Netboot Interface Window ......................................................................4-12

Figure 4-4. Netboot Interfaces Window ....................................................................4-13

Figure 4-5. Enabling BOOTP in a Sample Network .................................................4-16

Figure 4-6. BOOTP Relay Agent Interface Table Window ........................................4-18

Figure 4-7. BOOTP Relay Agent Forwarding Table Window ....................................4-19

Figure 4-8. BOOTP Addresses Window ...................................................................4-19

Figure 4-9. BOOTP Client Interface Table Window ..................................................4-22

Figure 4-10. BOOTP Client Interface Address Window ..............................................4-22

Figure 6-1. 8-Port ANH Port Status Window ..............................................................6-2

Figure 6-2. 12-Port ANH Port Status Window ............................................................6-3

Figure 6-3. Group Parameters Window ......................................................................6-4

Figure 7-1. Edit Base Module DCM Parameters Window ..........................................7-6

Figure 7-2. Edit Base Module DCM Parameters Window ........................................7-13

Figure B-1. Starting the IP Interface Test ................................................................. B-16

Figure C-1. Typical Single-ANH Conﬁguration ...........................................................C-5

Figure C-2. Connecting the ANH with Other Hubs ....................................................C-7

Figure C-3. Connecting Two ANH Systems Using 10Base-FL Transceivers ..............C-8

Figure C-4. Connecting ANH Systems through a Coaxial Backbone ........................C-9

114084 Rev. A

xvii

Tables

Table 1-1. Summary of Boot Options ........................................................................1-4

Table 3-1. BOOTPD Tags for a Router Hostname ....................................................3-5

Table 3-2. BOOTPD Tags for a Boot Image Name ...................................................3-6

Table 3-3. Providing TFTPD Access to Root and All Subdirectories ......................3-10

Table 3-4. Restricting TFTPD Access to One Directory ..........................................3-10

Table 4-1. BayStack AN Conﬁgurations ....................................................................4-3

Table 4-2. BayStack ANH Conﬁgurations .................................................................4-4

Table 4-3. BayStack ARN Base Module Conﬁgurations ...........................................4-5

Table 4-4. BayStack ARN Expansion Module Conﬁgurations ...................................4-5

Table 4-5. BayStack ARN Adapter Module Conﬁgurations .......................................4-5

Table 5-1. bconﬁg Command Settings ......................................................................5-3

Table 5-2. ifconﬁg Command Settings for a Synchronous Interface .........................5-5

Table 5-3. ifconﬁg Command Settings for an Ethernet Interface ..............................5-6

Table 5-4. ifconﬁg Command Settings for a Token Ring Interface ............................5-7

Table 5-5. ifconﬁg Settings to Enable and Disable Netboot Interfaces .....................5-8

Table 7-1. DRAM and RMON Memory Size ...........................................................7-18

Table 7-2. Maximum Number of Hosts ...................................................................7-20

Table 7-3. Default Size for Capture Buffer ..............................................................7-22

Table A-1. BOOTP Messages ................................................................................ A-13

Table B-1. Quick-Start/Power-Start Commands ..................................................... B-15

Table C-1. IEEE 802.3 Maximum Segment Links ....................................................C-4

114084 Rev. A

xix

About This Guide

Read this guide if you are responsible for connecting a Bay Networks™ BayStack™ Access Node (AN®), Access Node Hub (ANH™), or Advanced Remote Node (ARN™) router to a managed network.

This guide offers

• An overview of AN, ANH, and ARN software (Chapter 1)

• A description of network booting (Chapter 2)

• Instructions for setting up a UNIX (Chapter 3)

• Instructions for conﬁguring Site Manager to support network booting (Chapter 4)

• Instructions for conﬁguring the router for network booting (Chapter 5)

• Instructions for managing ANH repeater ports (Chapter 6)

• Instructions for conﬁguring an Ethernet Data Collection Module (DCM) for RMON statistics gathering (Chapter 7)

• Troubleshooting guidelines and procedures (Appendix A)

• Worksheets for completing the installation procedure (Appendix B)

• Implementation hints and notes (Appendix C)

workstation as a BOOTP server

Before Y ou Begin

Before using this guide, you (or a person at the router site) must install the router, or hardware and network connections, as described in one of the following guides:

• Installing and Operating BayStack AN and ANH Systems

• Installing and Operating BayStack ARN Routers

114084 Rev. A

xxi

Configuring Remote Access

Where to Find AN, ANH, or ARN Information

Use this guide in conjunction with other Bay Networks documentation to set up and manage AN, ANH, and ARN systems. Refer to the following when looking for speciﬁc information.

For Information on This Look Here

Installing BayStack AN or ANH hardware

Installing BayStack Advanced Remote Node hardware

Learning about AN, ANH, and ARN software and the four startup/boot options

Choosing a startup option for the router Chapter 2 in this guide Setting up a UNIX workstation as a

BOOTP server to support a network boot option

Conﬁguring Site Manager to support a network boot option

What to do at the AN/ANH/ARN site to support a network boot option

Conﬁguring a Data Collection Module Chapter 7 in this guide Preparing for the Quick-Start (local boot)

procedure Completing any of the four startup

options at the AN/ANH/ARN site

Conﬁguring and managing an AN/ANH/ARN after it is connected to the network

Reconﬁguring AN/ANH/ARN netboot interfaces

Considerations for setting up an AN/ANH/ARN

Resolving problems with the network boot process

Troubleshooting all other problems

Installing and Operating BayStack AN and ANH Systems

Installing and Operating BayStack ARN Routers

Chapter 1 in this guide

Chapter 3 in this guide

Chapter 4 in this guide

Chapter 5 in this guide

Appendix B in this guide

Installing and Operating BayStack AN and ANH Systems ARN Routers

Conﬁguring Routers and BNX Platforms

Chapter 5 in this guide

Appendix C in this guide

Appendix A in this guide

Troubleshooting Routers

Installing and Operating BayStack

and

Managing Routers

xxii

114084 Rev. A

Conventions

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

About This Guide

description inside the brackets. Do not type the brackets when entering the command.

ping

Example: if command syntax is you enter

ping 192.32.10.12

<ip_address>

bold text

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

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

brackets ([ ]) Indicate optional elements. You can choose none, one,

or all of the options.

ellipsis points Horizontal (. . .) and vertical ellipsis points indicate

()

omitted information.

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. 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

screen text

Indicates data that appears on the screen. Example:

Set Bay Networks Trap Monitor Filters

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

show at routes show at routes

114084 Rev. A

nets

, you enter either

show at nets

, but not both.

xxiii

Configuring Remote Access

Acronyms

ANSI American National Standards Institute ARP Address Resolution Protocol AUI Attachment Unit Interface BOFL Breath of Life BOOTP Bootstrap Protocol BOOTPD Boot Protocol Daemon BRI Basic Rate Interface CHAP Challenge Handshake Authentication Protocol DCE data communications equipment DCM Data Collection Module DLCI data link connection identiﬁer DLCMI Data Link Control Management Interface DTE data terminal equipment FTP File Transfer Protocol HDLC high-level data link control IEEE Institute of Electrical and Electronic Engineers IP Internet Protocol IPX Internet Packet Exchange ISDN Integrated Services Digital Network LMI Local Management Interface LQR Link Quality Reporting MAC media access control MAU media access unit MIB management information base MTU maximum transmission unit NBMA nonbroadcast multi-access NMM network management module OSPF Open Shortest Path First Protocol P AP Password Authentication Protocol PPP Point-to-Point Protocol PVC permanent virtual circuit RARP Reverse Address Resolution Protocol

xxiv

114084 Rev. A

RFC Request for Comments RIP Routing Information Protocol RMON remote monitoring SAM System Administration Manager SMDS switched multimegabit data service SMIT System Management Interface Tool SNMP Simple Network Management Protocol TCP/IP Transmission Control Protocol/Internet Protocol Telnet Telecommunication Network TFTP Trivial File Transfer Protocol TFTPD Trivial File Transfer Protocol Daemon UDP User Datagram Protocol UTP unshielded twisted-pair

Ordering Bay Networks Publications

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

About This Guide

™

at the following

114084 Rev. A

• Telephone - U.S./Canada 1-888-4BAYPRESS

• Telephone - International 1-510-490-4752

• Fax 1-510-498-2609 You can also use these numbers to request a free catalog of Bay Networks Press

product publications.

xxv

Technical Support and Online Services

To ensure comprehensive network support to our customers and partners worldwide, Bay Networks Customer Service has Technical Response Centers in key locations around the globe:

• Billerica, Massachusetts

• Santa Clara, California

• Sydney, Australia

• Tokyo, Japan

• Valbonne, France The Technical Response Centers are connected via a redundant Frame Relay

Network to a Common Problem Resolution system, enabling them to transmit and share information, and to provide live, around-the-clock support 365 days a year.

Bay Networks Information Services complement the Bay Networks Service program portfolio by giving customers and partners access to the most current technical and support information through a choice of access/retrieval means. These include the World W ide Web, CompuServ e, Support Source CD, Customer Support FTP, and InfoFACTS document fax service.

114084 Rev. A xxvii

Configuring Remote Access

Bay Networks Customer Service

If you purchased your Bay Networks product from a distributor or authorized reseller, contact that distributor’s or reseller’s technical support staf f for assistance with installation, conﬁguration, troubleshooting, or integration issues.

Customers can also purchase direct support from Bay Networks through a variety of service programs. As part of our PhonePlus™ program, Bay Netw orks Service sets the industry standard, with 24-hour, 7-days-a-week telephone support available worldwide at no extra cost. Our complete range of contract and noncontract services also includes equipment staging and integration, installation support, on-site services, and replacement parts delivery -- within approximately 4 hours.

To purchase any of the Bay Networks support programs, or if you have questions on program features, use the following numbers:

Region Telephone Number Fax Number

United States and Canada

1-800-2LANWAN; enter Express Routing Code (ERC) 290 when prompted

(508) 670-8766

(508) 436-8880 (direct) Europe (33) 92-968-300 (33) 92-968-301 Asia/Paciﬁc Region (612) 9927-8800 (612) 9927-8811 Latin America (407) 997-1713 (407) 997-1714

In addition, you can receive information on support programs from your local Bay Networks ﬁeld sales ofﬁce, or purchase Bay Networks support directly from your authorized partner.

xxviii 114084 Rev. A

Bay Networks Information Services

Bay Networks Information Services provide up-to-date support information as a ﬁrst-line resource for network administration, expansion, and maintenance. This information is available from a variety of sources.

W orld Wide Web

The Bay Networks Customer Support Web Server offers a diverse library of technical documents, software agents, and other important technical information to Bay Networks customers and partners.

A special beneﬁt for contracted customers and resellers is the ability to access the Web Server to perform Case Management. This feature enables your support staff to interact directly with the network experts in our worldwide Technical Response Centers. A registered contact with a valid Site ID can

• View a listing of support cases and determine the current status of any open case. Case history data includes severity designation, and telephone, e-mail, or other logs associated with the case.

Technical Support and Online Services

• Customize the listing of cases according to a variety of criteria, including date, severity, status, and case ID.

• Log notes to existing open cases.

• Create new cases for rapid, efﬁcient handling of noncritical network situations.

• Communicate directly via e-mail with the speciﬁc technical resources assigned to your case.

The Bay Networks URL is http://www.baynetworks.com. Customer Service is a menu item on that home page.

Customer Service FTP

Accessible via URL ftp://support.baynetworks.com (134.177.3.26), this site combines and organizes support ﬁles and documentation from across the Bay Networks product suite, including switching products from our Centillion™

and Xylogics site lets you quickly locate information on any of your Bay Networks products.

114084 Rev. A xxix

business units. Central management and sponsorship of this FTP

Configuring Remote Access

Support Source CD

This CD-ROM -- sent quarterly to all contracted customers -- is a complete Bay Networks Service troubleshooting knowledge database with an intelligent text search engine.

The Support Source CD contains extracts from our problem-tracking database; information from the Bay Networks Forum on CompuServe; comprehensive technical documentation, such as Customer Support Bulletins, Release Notes, software patches and ﬁxes; and complete information on all Bay Networks Service programs.

You can run a single version on Macintosh Windows 3.1, Windows 95, Windows NT, DOS, or UNIX computing platforms. A Web links feature enables you to go directly from the CD to various Bay Networks Web pages.

CompuServe

For assistance with noncritical network support issues, Bay Networks Information Services maintain an active forum on CompuServe, a global bulletin-board system. This forum provides ﬁle services, technology conferences, and a message section to get assistance from other users.

The message section is monitored by Bay Networks engineers, who provide assistance wherever possible. Customers and resellers holding Bay Networks service contracts also have access to special libraries for advanced levels of support documentation and software. To take advantage of CompuServe’ s recently enhanced menu options, the Bay Networks Forum has been re-engineered to allow links to our Web sites and FTP sites.

We recommend the use of CompuServe Information Manager software to access these Bay Networks Information Services resources. To open an account and receive a local dial-up number in the United States, call CompuServe at 1-800-524-3388. Outside the United States, call 1-614-529-1349, or your nearest CompuServe ofﬁce. Ask for Representative No. 591. When you are on line with your CompuServe account, you can reach us with the command

xxx 114084 Rev. A

GO BAYNET.

InfoFACTS

InfoFACTS is the Bay Networks free 24-hour fax-on-demand service. This automated system has libraries of technical and product documents designed to help you manage and troubleshoot your Bay Networks products. The system responds to a fax from the caller or to a third party within minutes of being accessed.

To use InfoFACTS in the United States or Canada, call toll-free 1-800-786-3228. Outside North America, toll calls can be made to 1-408-764-1002. In Europe, toll-free numbers are also available for contacting both InfoFACTS and CompuServe. Please check our Web page for the listing in your country.

How to Get Help

Use the following numbers to reach your Bay Networks Technical Response Center:

Technical Response Center Telephone Number Fax Number

Billerica, MA 1-800-2LANWAN (508) 670-8765 Santa Clara, CA 1-800-2LANWAN (408) 764-1188 Valbonne, France (33) 92-968-968 (33) 92-966-998 Sydney, Australia (612) 9927-8800 (612) 9927-8811 Tokyo, Japan (81) 3-5402-0180 (81) 3-5402-0173

Technical Support and Online Services

114084 Rev. A xxxi

Chapter 1

Understanding Tools and Options

The Bay Networks BayStack ARN and AN families of routers connect multiprotocol workgroups to corporate backbone networks. This chapter provides an overview of the software tools and options for conﬁguring remote access. The chapter includes information about the following:

• Software management tools

• Router software

• Boot conﬁguration options

• Boot process

Software Management Tools

You conﬁgure and manage an AN, ANH, or ARN using

• The graphical, SNMP-based router management tools within Optivity Internetwork™, a component of the Bay Networks Optivity Enterprise™ application suite:

-- Site Manager, a router management, conﬁguration, and monitoring

application.

-- RouterMan™, a real-time router performance and status reporting

appplication.

-- PathMan™, a diagnostic application for determining the complete data

path between any two network devices.

• The Technician Interface, a terminal-based command-line interface that operates in router memory. Technician Interface commands and scripts provide real-time SNMP-based MIB access from an attached or remote (modem or Telnet) console connection.

114084 Rev. A 1-1

Configuring Remote Access

• A ﬁrmware diagnostics monitor with a command-line interface. You use the AN/ANH/ARN monitor to conﬁgure the router’s boot conﬁguration.

This manual describes how to conﬁgure the router’s boot conﬁguration using the Diagnostic Monitor and Technician Interface, and how to connect remote access systems to a managed network using Site Manager.

Router Software

Before it can operate, the AN, ANH, or ARN hardware must boot a software image. The software image is a group of executable ﬁles that operate the protocols

that the network requires. The AN/ANH software image is called an.exe. The ARN software image is called arn.exe. The software image comprises the following executable startup ﬁles:

•A krnl_an.exe ﬁle (for the AN/ANH) or krnl_arn.exe (for the ARN) that contains the operating system kernel.

• Application ﬁles -- executable ﬁles needed to perform the functions speciﬁed in the conﬁguration ﬁle. All application ﬁles have .exe ﬁlename extensions. (For example, the router needs an ipx.exe executable ﬁle to run IPX.)

• String ﬁles -- compressed ASCII ﬁles needed when you use the Technician Interface to display the event log or management information base (MIB) object names. Groups of string ﬁles remain in compressed format within the an.exe or arn.exe ﬁle until needed.

To bridge and route trafﬁc, the AN, ANH, or ARN also needs a conﬁguration ﬁle that is tailored to your network. A conﬁguration ﬁle is a binary system ﬁle that contains hardware and software conﬁguration data. The default conﬁguration ﬁle is named conﬁg.

1-2 114084 Rev. A

Boot Conﬁguration Options

This section summarizes your options for getting the AN, ANH, or ARN software image and conﬁguration ﬁles.

Note: If you plan to use the Quick2Conﬁg™ software to conﬁgure the AN or

ANH, see Conﬁguring Your Router Using the Quick2Conﬁg Tool. Quick2Conﬁg is a Microsoft Windows-based application that you can use to create or modify router conﬁguration ﬁles.

An AN/ANH/ARN boots using one of four conﬁgured startup options. The differences among the four startup options are based on whether the router retrieves software image and conﬁguration ﬁles over the network or from local memory.

Getting a software image or conﬁguration ﬁle over the network is called Netbooting. Getting a ﬁle from the ﬁle system stored in local Flash memory is called Local booting.

Understanding Tools and Options

To initially start up the AN, ANH, or ARN, you use one of these boot conﬁguration options:

• EZ-Install (the default)

• Netboot

• Local Boot

To start up the AN, ANH, or ARN after the initial conﬁguration, you use one of these options:

• Netboot

• Directed Netboot

• Local Boot

114084 Rev. A 1-3

Configuring Remote Access

Table 1-1 summarizes the four startup options. The next section, “The Boot Process,” describes how each option works.

Table 1-1. Summary of Boot Options

Source for Boot Option

Software

Image

Source for conﬁg File Description and Requirements

EZ-Install Local

(Flash memory)

Netboot Network

(Serial,

Ethernet, or

Token Ring*

connection)

Network (Serial

connection)

Network (Serial,

Ethernet, or Token Ring* connection)

The default option. The router boots from a software image in local memory, and then transmits a request for its IP address and conﬁguration ﬁle through an attached serial interface.

Next, a remote UNIX- or DOS-based workstation that is conﬁgured as a Boot Protocol (BOOTP) server downloads a customized conﬁguration ﬁle; you save that conﬁguration to Flash memory.

Requires a communications link over an HDLC or Frame Relay interface.

If EZ-Install fails, the router tries the Local Boot procedure. The router obtains all startup ﬁles from a remote UNIX- or

DOS-based workstation that is conﬁgured as a BOOTP server. (Getting these ﬁles individually, rather than getting the entire usage and prevents saturation of the router’s memory.)

Requires a local file (for the ARN), a local console connection, and a communications link over an HDLC , F r ame Rela y, Ethernet, or (for the ARN)Token Ring* interface.

If Netboot fails, the router tries the Local Boot procedure.

an.exe

arn.exe

file, minimizes the cost of line

an.exe

ﬁle (for the AN or ANH) or

arn.exe

(continued)

1-4 114084 Rev. A

Understanding Tools and Options

Table 1-1. Summary of Boot Options

Source for Boot Option

Directed Netboot

Local Boot

Software

Image

Network

(Serial,

Ethernet, or

Token Ring*

connection)

Local

(Flash memory)

Source for conﬁg File Description and Requirements

Network (Serial,

Ethernet, or Token Ring* connection)

Local (Flash memory)

(continued)

The router obtains all startup ﬁles from a remote UNIX- or DOS-based workstation that is conﬁgured as a Trivial File Transfer Protocol (TFTP) server. You specify the IP address of the TFTP server and the pathname of the startup ﬁles before booting.

Requires a local file (for the ARN), a local console connection, and a communications link over an HDLC , F r ame Rela y, Ethernet, or Token Ring* interface.

If Directed Netboot cannot retrieve the appropriate ﬁles, the router attempts normal Netboot. If this fails, the router tries Local Boot.

The router boots using a software router image and conﬁguration ﬁle stored in local memory.

During the initial startup, the router uses a generic startup conﬁguration ﬁle. You customize the default conﬁguration ﬁle by assigning an IP address to an interface and running an installation script; this is called the procedure.

an.exe

ﬁle (for the AN or ANH) or

Quick-Start

arn.exe

Quick-Start requires a local console and an active IP network connection.

*. You can use the Netboot and Directed Netboot procedure on a Token Ring interface on the ARN only.

114084 Rev. A 1-5

Configuring Remote Access

The Boot Process

An AN, ANH, or ARN boots using its conﬁgured startup option. The default conﬁguration is EZ-Install.

(If an initial boot attempt fails on an AN or ANH, the router attempts to boot once using a different option. If both boot attempts fail, you must troubleshoot the problem and reboot the router as described in Appendix A. If an initial boot attempt fails on an ARN, the router ﬁrst tries to local boot, and then netboot. The ARN continues attempts to local boot and netboot until it successfully boots.)

The following sections describe the boot process for network and local boot options.

Network Boot

When booting over the network using EZ-Install, Netboot, or Directed Netboot, the router essentially

1. Powers on.

2. Determines its IP address.

3. Obtains a software kernel ﬁle and/or conﬁguration ﬁle by communicating with a conﬁgured BOOTP server on the IP network.

4. Reboots, using the newly transferred image.

5. Gets application and string ﬁles over the network as it needs them.

6. Begins bridging and routing network trafﬁc in accordance with the conﬁguration ﬁle.

The following sections describe in more detail the key steps in this process: obtaining an IP address and downloading the image and conﬁguration ﬁles.

Getting an IP Address

For Netboot and Directed Netboot, you conﬁgure the IP address manually. Chapter 4 describes how to use Site Manager to conﬁgure Netboot interfaces. Chapter 5 describes how to conﬁgure the netboot interfaces using the Technician Interface.

1-6 114084 Rev. A

Understanding Tools and Options

During the EZ-Install process, the router obtains its address automatically, as described next.

1. When you power on the router, it runs a set of diagnostic tests.

2. The router sends a BOOTP request to the upstream router for an IP address and subnet mask.

Note: The upstream router must have a circuit running Bay Networks

Standard Point-to-Point Protocol (PPP) using HDLC or a Frame Relay permanent virtual circuit (PVC).

The AN, ANH, or ARN issues the request through all serial ports at about the same time, even if cables are not connected to these ports. Each port successively tries the following protocols until it receives a response:

• Bay Networks Standard PPP using HDLC (high-level data link control)

encapsulation

• Frame Relay Annex D

• Frame Relay Local Management Interface (LMI)

• Frame Relay Annex A The AN, ANH, or ARN makes tw o attempts for each protocol ov er each serial

interface. If one does not receive a response in approximately 4 minutes, the router boots the image and conﬁguration ﬁle in its local ﬁle system, as described in the next section, “Local Boot

.”

3. The ﬁrst interface on the upstream router to receive the BOOTP request responds.

4. The upstream router calculates the IP address of the AN/ANH’s serial interface.

The upstream router calculates the IP address based on its protocol conﬁguration. See Step a if the upstream router circuit is running Bay Networks Standard or is a Frame Relay PVC in direct access mode. See Step b if it is a Frame Relay PVC in group access mode.

a. A PVC in direct access mode or a Bay Networks Standard interface

calculates the IP address by adding 1 to the IP address of the interface that received the request.

114084 Rev. A 1-7

Configuring Remote Access

For example, in Figure 1-1 the upstream router’s interface address is

192.32.1.1. This means that the upstream router calculates 192.32.1.2 as the booting router’s IP interface.

AN/ANH/ARN router

BOOTP request

Upstream router

IP address 192.32.1.1

BOOTP response with IP address 192.32.1.2

NPA0001A

Figure 1-1. Getting an IP Address from a Bay Netw orks Standard Circuit

or a Frame Relay PVC in Direct Access Mode

Note: If the IP address plus 1 equals a broadcast address, the upstream router

calculates the IP address by subtracting 1. For example, if its interface is

7.255.255.254, the IP interface for the booting router is 7.255.255.253.

b. A PVC in group access mode references its BOOTP client interface table

to ﬁnd an associated IP address for the booting router.

Note: The BOOTP client interface table contains a data link connection

identiﬁer (DLCI) and IP address pair for each PVC. You use Site Manager to create this table when you follow the instructions for setting up routing paths in Chapter 4.

1-8 114084 Rev. A

Understanding Tools and Options

For example, in Figure 1-2, an AN/ANH/ARN router sends BOOTP requests for its IP address. The upstream router receives the request on PVC 31. The upstream router determines the DLCI, refers to DLCI 31 in the BOOTP client interface table, ﬁnds the IP address, and sends a BOOTP response containing the IP address back to PVC 31.

AN/ANH/ARN

Circuit containing PVC 31, 32, 33 (for virtual connections to the three routers)

Key

BOOTP request BOOTP response

Booting router 2 Booting router 3

PVC 32

PVC 31

Frame Relay

Upstream router

PVC 33

BOOTP Client Interface Table:

DLCI 31 192.32.1.2

DLCI 32 192.32.1.3 DLCI 33 192.32.1.4

NPA0002A

Figure 1-2. Getting an Address from a PVC in Group Access Mode

5. The upstream router sends the IP address and subnet mask to the AN/ANH/ARN in a BOOTP response message.

6. The AN/ANH/ARN assigns the IP address and subnet mask to any serial interface that receives a BOOTP response.

7. The AN/ANH/ARN stores these addresses, along with the address of the next-hop router, in RAM.

114084 Rev. A 1-9

Configuring Remote Access

If both serial interfaces receive BOOTP responses, the AN/ANH/ARN assigns the respective IP addresses to each interface.

Getting Kernel Image and Conﬁguration Files

With a known IP address, the AN/ANH/ARN can get image and conﬁguration ﬁles.

1. The AN/ANH/ARN sends a BOOTP request for the pathnames of a conﬁguration ﬁle and image kernel.

The router issues the request simultaneously through all serial (COM), Ethernet, and Token Ring (ARN only) interfaces that have IP addresses. It issues this request periodically for about 3 minutes, regardless of whether a cable is connected.

2. A BOOTP server responds to the router’s request with the directory pathnames (F

AN/ANH/ARN

igure 1-3).

Upstream router

Pathnames

Corporate backbone

BOOTP server

Key

BOOTP request BOOTP response

NPA0003A

Figure 1-3. Getting the Pathnames of the Kernel and Conﬁguration Files

The ﬁrst router interface that processes the BOOTP response acts as the TFTP client in the remaining steps.

1-10 114084 Rev. A

Understanding Tools and Options

3. The AN/ANH/ARN stops sending BOOTP requests.

4. The AN/ANH/ARN sends a TFTP request for the conﬁguration ﬁle.

5. The BOOTP server uses TFTP to transfer the conﬁguration ﬁle (F

AN/ANH/ARN

Configuration file

Corporate backbone

Upstream router

Key

TFTP request TFTP transfer

Figure 1-4. Getting the Conﬁguration File

BOOTP response

igure 1-4).

BOOTP server

NPA0004A

6. The AN/ANH/ARN sends a TFTP request for the image kernel ﬁle.

7. The BOOTP server uses TFTP to transfer the image kernel ﬁle (F

114084 Rev. A 1-11

igure 1-5).

Configuring Remote Access

AN/ANH/ARN

Kernel

Corporate backbone

Key

Local Boot

Upstream router

TFTP request TFTP transfer

BOOTP server

NPA0005A

Figure 1-5. Getting the Kernel

8. The AN/ANH/ARN boots the kernel.

9. The AN/ANH/ARN uses TFTP to get application and string ﬁles as it needs them.

10. The router begins bridging and routing network trafﬁc in accordance with the conﬁguration ﬁle.

The AN/ANH/ARN can continue to request ﬁles, e v en after it begins bridging and routing trafﬁc.

If a failure occurs in Steps 1 through 8, the router attempts to boot locally.

When the AN, ANH, or ARN boots locally, it reads the kernel file, application ﬁles, and string ﬁles that are embedded within a local software image file (an.exe for the AN/ANH or arn.exe for the ARN).

1-12 114084 Rev. A

Understanding Tools and Options

When you use Local Boot as the initial boot option, you boot a default (generic) conﬁguration ﬁle. You must then run the installation script to customize the default conﬁguration ﬁle.

Running the installation script establishes an IP network interface between the AN/ANH/ARN and a Site Manager management workstation (F

igure 1-6). To

make this connection, you use a Technician Interface command.

IP address = 192.32.10.12

Corporate IP network

Site Manager

workstation

ASCII console or PC

Console port

AN/ANH/ARN

Ethernet port

IP address = 192.32.156.7 Subnet mask = 255.255.255.0

NPA0006A.EPS

Figure 1-6. Establishing an IP Network Interface

Conﬁguring the Initial IP Interface

Appendix B brieﬂy describes the procedure for customizing the default conﬁguration ﬁle, provides worksheets for preparing to run the procedure, and explains how to begin the installation script.

114084 Rev. A 1-13

Chapter 2

Selecting the Boot Conﬁguration

This chapter provides information to help you select the boot method for both the initial startup of the router and for day-to-day startup operations.

Note: To learn about the boot process and startup options, see Chapter 1.

First, refer to one of the following sections for help selecting the startup option:

•“Booting the Router f

•“Booting the Router Routinel

Then refer to the section, “Completing a Star steps.

or the First Time”

y”

tup Option,” for a summary of your

Booting the Router for the First Time

You coordinate the initial startup with a person at the AN/ANH/ARN site, who physically installs and cables the router and initiates the desired startup procedure. The hardware installation manual (Installing and Operating BayStack AN and ANH Systems or Installing and Operating BayStack ARN Routers) explains these tasks in detail.

114084 Rev. A 2-1

Configuring Remote Access

After you select the initial startup conﬁguration and set up the network (as described in this guide), you instruct the person at the router site to begin the appropriate startup option.

Note: As an alternative to another person performing the initial startup at the

remote site, you can perform these tasks using a modem connection.

EZ-Install

You can use EZ-Install for the initial startup if

• There is a communications link between the AN/ANH/ARN and an upstream router over an HDLC or Frame Relay interface.

• A directory on a BOOTP server contains a customized conﬁguration ﬁle for the AN/ANH/ARN.

EZ-Install is the default option for a new router. It is the easiest option for the person at the AN/ANH/ARN site to perform, because the network automatically supplies the IP address and conﬁguration ﬁle.

Netboot

You can use Netboot if

• The AN/ANH/ARN has a communications link to an upstream router over an Ethernet, HDLC, Frame Relay, or Token Ring (ARN only) interface.

• You establish a local console or modem connection with the AN/ANH/ARN.

• A directory on a BOOTP server contains the software image ﬁle (krnl_an.exe for the AN/ANH or krnl_arn.exe for the ARN) and a network conﬁguration ﬁle customized for the router.

• You conﬁgure an IP address for the router’s boot interface.

Netboot takes longer than EZ-Install, but minimizes the cost of line usage and the saturation of the router’s memory.

2-2 114084 Rev. A