Avaya BayStack Remote Access User Manual

Configuring BayStack Remote Access

BayRS Version 13.0 0 Site Manager Software Version 7.00

Part No. 303516-A Rev 00 October 1998

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

and recomm endations in this docum ent are believed to be accurate and reliable, but are presented without express or implied warranty. U sers must take full respons ibility for their applications of any products specified in this do cum ent. 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 te rms of that license. A summary of the Soft w are License is include d in this docum ent.

Trademarks

ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FRE, LN, Optivity, PPX, and Bay Networks are registered trademar ks and Advanced Remote Node, ANH, ARN, ASN, BayRS, BaySecure, BayStack, BayStream, BCC, BCNX, BLNX, EZ Install, EZ Internetwork, EZ LAN, FN, IP AutoLearn, PathMan, RouterMan, SN, SPEX, Switch Node, System 5000, and the Bay Network s logo are trademarks of Bay Networks, Inc.

Microsoft , MS, MS-DOS, Win32, Windows, and Windows NT ar e registered trade m arks of Micro soft Corporation. 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 restrict ions 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 th at may pertain to, or accompany the delivery of, this computer software, the ri ghts of the Un ited States Gove rnment re garding 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 an y liability that may occur due to the use or applic ation of the product(s) or circuit layout(s) described herein.

Portions of the code in this software product may be Copyright © 1988, Regents of the University of California. All rights reserve d. Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this paragrap h are duplicated in all su ch forms and th at any docume ntation, adverti sing materials, and other materials related to such distribution and use acknowledge that such portions of the software were deve loped by th e U niversity of California, Berkeley. The nam e of the University may not be used to endorse or promote products derived from such portions of the software without specific prior written permission.

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

In additi on, the program and information contained herein are li censed only pursuant to a license agreement that contains restrictions on use and disclosu re (that may incorporate by refer ence certain limitations and not ices imposed by thir d pa rt ie s).

303516-A Rev 00

Bay Networks, Inc. Software License Agreement

NOTICE: Please carefully read this license agreement before copying or using the accompanying software or instal ling the hardware unit with pre-enabled software (e ach of which is referred to as “Softw are” in this Agreement). BY COPYING OR USING THE SOFTWARE, YOU ACCEPT 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 o riginal shipping container, within 30 days of purchas e to obtain a credit for the full purchase price.

1. License Grant. Bay Networks, Inc. (“Bay Networks”) gra nts the end user of the Software (“Lice nsee”) a personal, nonexcl usive, nontransferable license: a) to use the Software either on a single computer or, if applicable, on a single authori zed de vi ce ide ntified by host ID, fo r whi ch it was origi nal ly acq uired ; b) to cop y th e Softw ar e so le ly fo r bac kup purposes in support of authorized us e of the Software; and c) to us e and copy the associated user manual solely in support of authorized use of the Soft w are by Licensee. This li cense applies to the Software only and does not extend to Bay Networks Agent software or other Bay Networks softw are 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. The Software and us er m anuals are protected under copyright laws. Bay Networks and/or its licensors retain all title and ownership in both the Sof tware and user manuals, including any revis ions made by Bay Networks or its licensors. The copyright notice must be reproduced and included wi th any copy of any por tion of the Sof tw are or use r manua ls . Licens ee may not modif y, translate, dec ompi le , disas se mble , use for any compe ti ti v e an al ysis, r e v erse e ngi ne er , dis tr ib ute , o r c rea te der i vative work s f ro m the Softw are or u se r man ual s or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer the Softw are or user man uals, in whole or in part. The Software and user manual s em body Bay Networks’ and it s licenso rs’ confidential and proprietary intell ectual property. Licensee shall not sublicense, assign, or otherwise disclos e to any third party the Software, or any information about the operation, design, performance, or implementation of the Software and user manuals that is confidential to Bay Networ ks and its licensors; however, Licensee m ay grant permission to its consul tants, subcontractors, and agents to use the Software at Licensee’ s facility, provided they have agreed to use the Software only in accordance with the terms of this license.

3. Limited warranty. Bay Networks warrants each item of Software, as delivered by Bay Network s and properly installed and operated on Bay Networks hardware or other equipment it is originally licensed for, to function substantially as described in i ts accompanying user manual during its warranty period, wh ich begins on the date Softwar e is fi r st shi pped to Licen see . If any it em of Soft war e fai ls to so func ti on du ring i ts warr anty pe ri od, as t he so le remedy Bay Ne tworks will at its discretion provide a suitable fix, pat ch, or workaround for the problem tha t m ay be included in a future Software release. Bay Networks further warrants to Licensee that the media on which the Softwar e is provided will be fr ee from defects in materials and workmanship under normal use for a period of 90 days from the date Software is first shipped to Licensee. Bay Networks will replace defectiv e media at no charge if it is returned to Bay Netw orks during the warranty per iod along with proof of the date of shipmen t. This warran ty does not apply i f the media has been damaged as a result of acci dent, misuse, or abuse. The Licensee assumes all re sponsibility 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 cont ained in the software w ill meet the Licensee ’s requirements, b) that the Software will operate in the har dw are or software combinations that the Licensee may select, c) that th e operation of the Software will be uninterrupted or error free, or d) that all defects in the operati on of the Software wi ll be corrected. Bay Networks is not ob ligated to remedy any Software defect that cannot be repro duced with the latest Software release. Thes e warranties do not apply to the Sof tware if it has be en (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 im proper environm ent, 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 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of

303516-A Rev 00

iii

its own data and information and for maint aining adequate procedures apart from the Software to reconstruct lost or altered files, data, or programs.

4. Limitati on of liabili ty. IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DAT A 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 NETW ORKS FOR THE SOFTWARE LICENSE.

5. Governmen t L i c en s ees. This provisio n applies to all Software and documentation a cquired directly or indirectly 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, dupli cation, or disclos ure by the U.S. Gover n m ent is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial Computer So ftware––Restricted Rights clause of FAR 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 t he D e partment of Defense or their suc cessors, whiche ver is applicable.

6. Use of Software in the European Communi ty. This prov ision applies to all Software acquired for use within the European Comm unity. If Lice nsee uses the Software within a countr y in the European Community, the Software Directive enacted by the Counc il of European Communities Directive dated 14 May, 1991, w ill apply to the examination of the Software to facilitate interoperability. Licensee agrees to notify Bay Netw orks of any such intended examination of the Software and may procure support and assistance from Bay Networ ks.

7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the Bay Networks copyright; those r estrictions relating to use and disclosure of Bay N etworks’ confidential information shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if Licensee fails to co m ply with any of the terms and conditions of the license. Upon terminat ion 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. Licensee agrees not to export, direct ly or indirectly, the Software or related technical data or information without first obtaining any required export licenses or other governmental approvals. Without limiting the fore going, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that i t will not, without first obtaining all export licenses and appro vals required by the U.S. Government: (i) export, re-export, trans fer, or diver t any such Sof tware or technical data, or any direct product thereof, to any coun try to which such exports or re-exports are rest ricted or embargoed under United States ex port control laws a nd regulations, or to any national or resident of such rest ricted or embargoed countries; or (ii) provide the Software or related technical data or inf ormation to any military end user or for any military end use, i n cluding the design, development, or production of any chemical, nuclear, or biological weapons.

9. General. If any provision of this Agreement is held to be invalid or unenforceable by a court of competent 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 Bay Networks, Inc., 440 1 G reat America Parkway, P.O. Box 58185, Santa Clara, Californi a 95054-8185.

LICENSEE ACKNOW LEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FUR THER 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.

303516-A Rev 00

Preface

Before You Begin ............................................................................................................. xv

Text Conventions ..... ......................................................... ...............................................xvi

Acronyms ........................................................................................................................ x vi i

Bay Networks Technical Publications ..............................................................................xix

How to Get Help ..............................................................................................................xx

Chapter 1 Understanding Tools and Options

Network Configuration and Management T ools ............................................ ..... ....... ......1-1

BayStack Router Startup Procedure ............................................................ .......... ....... .1-2

Startup Files ........... .............. ....................................................................... .............1-2

Startup Options ........ ............... ....................................................................... ..........1-3

The Boot Process ..................................................................................................... 1-5

Netboot Process ........................ ....... .. .......... ....... .. .......... ....... ....... .. .......... ....... .1-5

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

Preparing for the Initial Startup ..................................................................................... 1 -13

Selecting the Initial Startup Option .........................................................................1-13

EZ-Install .........................................................................................................1-14

Local Boot ........................................................................................................1-14

Netboot ............................................................................................................1-15

Providing a Tailored Configuration File ..................................................................1-15

Selecting the Routine Startup Option ...........................................................................1-16

Recommendations .................................................................................................1-16

Netboot ...................................................................................................................1 -16

Directed Netb o ot ......................... ....................................................................... ....1-17

Local Boot ..............................................................................................................1-18

303516-A Rev 00

Steps for Completing Startup Options ..........................................................................1-18

EZ-Install ................................................................................................................ 1-19

Netboot ...................................................................................................................1 -20

Directed Netb o ot ......................... ....................................................................... ....1-21

Local Boot ..............................................................................................................1-22

Chapter 2 Setting Up a UNIX Boot Server

Setting Up a BootP Server .............................................................................................2-2

Setting Up BootP Sockets ........................................................................................2-2

Configuring BootPD .................................................................................................2-2

Copying BootPD on Sun Workstations .............................................................. 2-2

Setting Up BootPD to Run .................................................................................2-3

Setting Up BootPD to Respond to BayStack Routers .......................................2-3

Editing the bootptab File ....................................................................................2-4

Verifying Consistent BootP Service ...................................................................2-6

Setting Up a TFTP Server ..............................................................................................2-8

Setting Up TFTPD .................................................................................................... 2-8

Providing TFTP Acce ss to All Directories ..........................................................2-9

Restricting TFTP Access to Specified Directories .............................................2-9

Adding a TF TP User for an HP 9000 Workstation ...........................................2-10

Setting Up Static Routes to Next-Hop Routers ......................................................2-10

Editing the /etc/inetd.conf File ......................................................................... 2 -11

Verifying the Routes ........................................................................................2-11

Loading the Changes into Memor y ..................................................................2-11

What to Do Next ........................................................................................................... 2 -12

Chapter 3 Configuring Net boot Services with Site Manager

Preparing Configuration and Image Files .......................................................................3-2

Creating Configuration Files ..................................................................................... 3-2

Preparing an Image .................................................................................................3-5

Enabling Netboot or Directed Netboot . ........................................................................... 3-6

Adding a Netboot or Directed Netboot Interface .............................................................3-8

Configuring a Netboot or Directed Netboot Interface ..................................................... 3-9

303516-A Re v 00

Setting Up Routing Paths for Netboot ...........................................................................3-10

Enabling Router Interfaces ..................................................................................... 3 -10

Creating Bo otP Relay Agent Forwarding Tables ...................................................3-11

Creating the BootP Client Interface Table .....................................................................3 -13

Chapter 4 Configuring Netbo ot Client Servic e s

Using Netboot Configuration Commands .......................................................................4-2

Setting the Boot Configuration ........................................................................................4-3

Using the bconfig Command Format ...................................................................... .4-3

Examples of Using the bconfig Command ...............................................................4-4

Setting the Netboot Interface Configuration .................................................................... 4-5

Configuring a Serial Interface for Network Booting ..................................................4-5

Configuring an Ethernet Interface for Network Booting ............................................4-7

Configuring an ARN Token Ring Interface for Network Booting ...............................4-8

Enabling and Disabling Interfaces with the ifconfig Command ................................4-9

Examples of Using the ifconfig Command ...............................................................4-9

Verifying Your Configuration .........................................................................................4-10

What to Do Next ........................................................................................................... 4 -11

Chapter 5 Managing ANH Repeater Ports

Enabling and Disabling ANH Repeater Ports .................................................................5-2

Testing and Resetting ANH Repeater Ports . ..................................................................5-5

Appendix A Site Manag er Param et ers

Netboot and Directed Netboot Parameters ............................................................... .....A-2

Netboot Interface Parameters ........................................... .. .......... ....... ....... .. .......... .......A-4

BootP Relay Agent Interface Parameters ......................................................................A-7

BootP Client Interface Address Parameters ..................................................................A-8

Repeater Port Group Parameters ..................................... .. .......... ....... .. ....... .......... .......A-9

303516-A Rev 00

vii

Appendix B T roubleshooting Network Boot Problems

Solving Startup Problems ..............................................................................................B-1

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

Upstream Router Not Receiving BootP Req uests ............................................B-2

Upstream Router Not Sending BootP Responses ..................................... .......B-2

Router Fails to Netboot ........................................................................................... B-3

Upstream Router Not Receiving BootP Req uests ............................................B-3

Router Not Sending BootP Responses ............................................................B-4

BootP Server Not Sending BootP Responses ..................................................B-4

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

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

Identifying Remote Connectivity Problems .................................................................... B-8

Displaying Messages from the BayStack Router Console ......................................B-8

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

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

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

Resolving Connectivity Problems ................................................................................B-10

Displaying Parameter Settings .............................................................................. B-10

Debugging the BootP Server ................................................................................B-12

Verifying the BootP Ser ver Setup ..........................................................................B-14

Displaying the Bo otP Server IP Routes ................................................................ B-15

Displaying the Number of Packets Forwarded and Dropped .................................B-16

Quick Get Instructions ....................................................................................B-16

Technician Interface Instructions ....................................................................B-16

Maintaining the Router Software ................................................................................. B-17

Upgrading the Software Image .................................. ....... ....... ..... ....... ....... ....... ...B-17

Restoring a Local File System ..............................................................................B-18

Hints and Notes ............ .............. ....................................................................... ..........B-19

Setup Hints ............................................................................................................B-19

Implementation Notes ...........................................................................................B-20

viii

303516-A Re v 00

Appendix C Using the Quick-Start Local Boot Procedure

What Is Quick-Sta rt? .....................................................................................................C-2

Using the Worksheets ...................................................................................................C-2

Global Information Worksheet .................................................................................C-4

Router Protocol Worksheets ........................................................... ..... ....... ....... .....C-6

Wide Area Protocol Worksheets .............................................................................C-9

Running the Quick-Start Scr ipt ....................................................................................C-13

Index

303516-A Rev 00

Figures

Figure 1-1. Calculating an IP Address (Direct Access PVC or Standard PPP) ..........1-7

Figure 1-2. Requesting an IP Address from the BootP Server (Group Access PVC) 1-8

Figure 1-3. Obtaining the Path Names of the Ke rnel and Configuration Files ............ 1-9

Figure 1-4. Obtaining the Configuration F ile ............................................................1-10

Figure 1-5. Obtaining the Kernel File .......................................................................1-11

Figure 1-6. Establishing an IP Network In terface .....................................................1-12

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

Figure 3-1. Enabling BootP Relay in a Sample Network ..........................................3-10

Figure 5-1. 8-Port ANH Port Status Window ..............................................................5-3

Figure 5-2. 12-Port ANH Port Status Window ............................................................5-4

Figure C-1. Quick-Start IP Configuration Test ..........................................................C-16

303516-A Rev 00

Tables

Table 1-1. BayStack Router Star tup Files .................................................................1-3

Table 1-2. Summary of BayStack Router Startup Options .....................................1-4

Table 2-1. BootPD Tags for a Router Host Name ....................................................2-5

Table 2-2. BootPD Tags for a Kernel File Name ......................................................2-6

Table 2-3. Providing TFTP Access to All Directories ...............................................2-9

Table 2-4. Restricting TFTP Access to Specified Directories ..................................2-9

Table 3-1. Configuration Manager Module Names for AN and ANH ........................3-3

Table 3-2. BayStack ARN Base Module Configurations ........................................... 3-3

Table 3-3. BayStack ARN Expansion Module Configurations ..................................3-4

Table 3-4. BayStack ARN Adapter Module Configurations . .....................................3-4

Table 4-1. bconfig Command Options ................. ....... .......... ....... .. ....... .......... .. ......4-3

Table 4-2. ifconfig Command Options for a Serial Interface ....................................4-6

Table 4-3. ifconfig Command Options for an Ethernet Interface .............................4-7

Table 4-4. ifconfig Command Options for an ARN Token Ring Interface ................4-8

Table A-1. BootP Messages .................................................................................B-13

Table C-1. Quick-Start Commands ........................................................................C-15

303516-A Rev 00

xiii

This guide describes connecting a Bay Networks® BayStack™ Access Node (AN®), Access Node Hub (ANH™), or Advanced Remote Node™ (ARN™) router to a managed ne twork.

Before You Begin

Before using this guide, you (or the per son responsible at the router site) must install the BayStack rou ter ha rdware, as described in one of the following guides:

• Installing and Operating BayStack AN and ANH Systems

Preface

303516-A Rev 00

• Installing and Operating BayStack AN/DC and ANH-8/DC Systems

• Installing and Operating BayStack ARN Routers

• Installing and Operating BayStack ARN/DC Routers

Make sure tha t you are running the latest version of Bay Networks BayRS Site Manager software. For information about upgrading BayRS and Site Manager, see the upgr ading guide for your version of B ayRS.

™

and

Configuring BayStack Remote Access

Text Conventions

This guide use s the following text conventions:

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

description inside the brackets. Do not type the brackets when entering the command. Example: If the command syntax is:

bold text

<ip_address>

ping ping 192.32.10.12

Indicates text tha t you need to enter and command

, you enter:

names and options. Example: Enter

Example: Use the

show ip {alerts | routes

command.

dinfo

}

braces ({}) Indicate required elements in syntax descriptions

where there is more than one option. You must choose only one of the options. Do not type the braces when entering the command. Example: If the command syntax is:

, you must enter either:

show ip {alerts | routes show ip alerts or show ip routes

}

brackets ([ ]) Indicate optional elements in syntax descriptions. Do

not type the brackets when entering the command. Example: If the command syntax is:

, you can enter either:

show ip interfaces [-alerts show ip interfaces

]

show ip interfaces -alerts

xvi

ellipsis points (. . . ) Indicate that you repeat the last element of the

comman d as need ed . Example: If the command syntax is:

ethernet/2/1 ethernet/2/1

parameter> <value>

and as many parameter-value pairs as

] . . .

, you enter

needed.

303516-A Re v 00

Preface

italic text Indicates file and directory names, new terms, book

titles, and variables in command syntax descriptions. Where a variable is two or more words, the words are connected by an underscore. Example: If the command syntax is:

show at

valid_route

valid_route>

is one va riable and you subs titu te one value

for it.

screen text Indicates system output , fo r exa mple, prompts and

system messages. Example:

Set Ba y Netw orks Tr ap Mo nito r Fil ters

separator ( > ) Shows menu paths.

Example: Protocol s > IP identifies the IP option on the Protocols menu.

vertical line (

) Separates choices for command keywords and

arguments. Enter only one of the choices. Do not type the vertical line when entering the command. Example: If the command syntax is:

Acronyms

303516-A Rev 00

, you enter either:

show ip {alerts | rou tes show ip alerts

}

show ip routes

, but not both.

ANSI American National Standards Institute ARP Address Resolutio n Protocol AUI Attachment Unit In terface BofL Breath of Lif e BootP Bootstrap Protoco l BootPD Bootstrap Protoco l Daemon BRI Basic Rate Interface CCITT International Telegraph and Telephone Consultative

Committee (no w ITU-T)

CHAP Challenge Handshake Authentication Protocol

xvii

Configuring BayStack Remote Access

CSMA/CD carrier sense multiple access/collision detection DCE data communications equipment DLCI data link connection ide ntifier DLCMI Data Link Control Management Interface DSU/CSU data service unit/ch annel se rvice unit DTE data terminal equipment FTP File Transfe r Protocol HDLC high-le vel data link control IEEE I nstitute of Electrical and Electronics Engineers IP Internet Protocol IPX Internet Packe t Exchange ISDN Integra ted Services Digital Network ISO International Organization for Standardiza tion ITU-T International Telecommunications

Union–Telecommunications sector (formerly CCITT)

xviii

LAN local area networ k LMI L ocal Management Interface LQR Link Quality Reporting MAC media access c ontrol MAU media access unit MIB Management Information Base NBMA nonbroadcast multi- access OSI Open Systems Interconnection OSPF Ope n Shortest Path First (protocol) PAP Password Authenticatio n Protocol PCMCIA Personal Computer Memory Card Inter na tional

Association PPP Poin t-to-Point Protocol PVC permanent virtual c ircuit RARP Reverse Address Resolution Protocol

303516-A Re v 00

Preface

RFC Request for Comments RIP Routing Informati on Protocol RMON remote monitoring SAM Syste m Administration Manager SIMM single in-line memory module SMDS switched multimegabit data service SMIT System Management Interface Tool SNMP Simple Network Management Protocol STP shielded twisted pair TCP/IP T ransmission Control Protocol/Internet Protoco l Telnet Telecommunication network TFTP Trivial File Transfer Protocol TFTPD Trivial File Transfer Protocol Daemon UDP User Datagram Protocol WAN wide area network

Bay Netwo rks Technical Publicati o ns

You can now print Bay Networks technical manuals and release notes free, directly from the Int ernet. Go to support.bayn etworks.com/libr ary/tpubs/. Fi nd the Bay Networks product for which you need doc umenta tion. Then locate the specific category and model or version for your hardwa re or software product. Using Adobe Acrobat Reader, you can open the manuals and release notes, search for the sections you need, and print them on most standard printers. You can download Acrobat Reader free from the Adobe Systems Web site, www.adobe.com.

303516-A Rev 00

xix

Configuring BayStack Remote Access

You can purchase Bay Networks documentation sets, CDs, and selected technic al publications through the Bay Networks Collateral Catalog. The catalog is located on the World Wide Web at support.bayne tworks.com/catalog.html and is divided into sections arran ged alphabetically:

• The “CD RO Ms” section lists available CDs.

• The “Guides/Books” section lists books on technical topics.

• The “Technical Manuals” section lists available printed documentation sets. Make a note of the part num bers and prices of the items that you want to order.

Use the “Marketing Collateral Catalog description” link to place an order and to print the order form.

How to Get Help

For product assista nce, support contracts, or information about educational services, go to the following URL:

http://www.baynetworks.com/corporate/contacts/

Or telephone the Bay Networks Technical Solutions Center at: 800-2LANWAN

303516-A Re v 00

Chapter 1

Understanding Tools and Options

The AN/ANH and ARN families of routers (referred to as BayStack r out ers in t his guide) connect multiprotocol workgroups to corporate backbone networks. This chapter provide s an overview of the software and procedures for configur ing and managing BayStack router remote access.

T opic Page

Network Configuration and Management Tools BayStack Router Startup Procedure 1-2 Preparing for the I nit ial Startup 1-13 Selecting the Routine Startup Option 1-16 Steps for Completing Startup Options 1-18

Network Configuration and Management Tools

There are several tools available for configuring and managing BayStack routers:

• Graphical, SNMP-based network management tools within

™

Optivity Internetwork Optivit y Enterprise™ application suite :

-- Site Manager, a router management, configuration, and monitoring application

-- RouterMan

™

application

™

-- PathMan

, a diagnostic application for de termining the complete data

path between two networ k devices

, a component of the Bay Networks

, a real-time router performanc e and status reporting

1-1

303516-A Rev 00

1-1

Configuring BayStack Remote Access

• Router configuration and management tools included with BayRS:

-- T echnician Interface, a command-line interface that operates in router memory. Tec h nic ia n Int erfac e co mm ands and scripts provide real-time SNMP-based Management Information Base ( MIB) access from an attached or r emote (modem or Telnet) management console.

-- AN Monitor, a command-line interface to the BayStack router diagnostic firmware . You use the AN Monitor to confi gure AN, ANH, and ARN boot configurations.

This guide describes how to connect BayStack routers to a managed network using Site Manager, and how to set the startup configuration using the AN Monitor and Technician Interface.

BaySta ck Router Startup Procedure

The following sections describe the software files and configuration options involved in the BayStack router startup procedure:

• Startup Files

• Startup Options

Startup Files

1-2

Before it can operate, a router must boot a software image. The software image contains an operatin g-system kernel fil e that supports the router platform, plus a group of executable files tha t support the major networking protoc ols and dial-up services that the network requires. Booting the router is the process of installing and using the applicable software image files.

To bridge and route traffic, a route r also ne eds a configuration file that is tailored to the network. A configuration file is a binary system f ile that contains hardware and software configuration data.

303516-A Re v 00

Understanding Tools and Options

Bay Networks ship s the software image for a BayStack router on a PCMCIA flash memory card, along with a default con figuration file named config. The ARN software image is named arn.exe. The AN/ANH software image is named an.exe.

Table 1-1

describes the ex ecutable startup fi les contained in the AN/ANH and

ARN software im ages.

Table 1-1. BayStack Router Startup Files

Startup File Name Description

krnl_arn.exe krnl_an.exe

Application files Execu table files needed to perform the functions specified in the

String files Compressed ASCII files needed when you use the Bay Networks

Startup Options

A router obtai ns the software i mage and configuration files that you want it to use during startup.

Startup options allow a BayStack router to retrieve sta rtup files either over the network or f rom the file system stored in local flash memory. Obtaining startup files from the router file system is called local booting. Obtaining one or more startup files over the network is called network booting, or netbooting.

You use one of four boot options to complete a startup procedure. Table 1-2 summarizes these st artup options. “The Boot Process local and network booting works.

ARN operating-system kernel AN/ANH operatin g-system kernel

configur ation file. All appl ication files have extensions. (For example, the router needs an file to run IPX.)

Technician Interface to display the ev ent log or MIB object names. Groups of string f il es remain in compressed format until needed.

.exe

file-name

ipx.exe

executable

” on page 1-5 describes how

303516-A Rev 00

For initial sta rtup, the BayStack router is configured for a default option , but you can change the default (se e “Preparing for the Initial Startup

” on page 1-13). To select the startup option fo r routine operation, see “Selecting the Routine Sta rtup

Option” on page 1-16. To review the steps for conf iguring and completing a

startup option, see “Steps for Completing Startup Options” page 1-18.

1-3

Configuring BayStack Remote Access

Table 1-2 . Sum ma ry of BayStack Rout er Sta r t up Options

Boot Option

EZ-Install Local

Netboot Local

Directed Netboot

Local Boot Local Local The BayStack router boots from

Image File Source

(PCMCIA flash memory card)

or Network

Local or Network

Configurati on File Source Descri ption Requirements

Network (serial interface only)

Local or Network

The default option for ini tial startup. The BayStac k router boots the software image files in loc al flash memory, then obtains its configuration file from a remote workstation on a frame relay network that is configured as a Bootstrap Pro tocol (Bo otP) serv er . The BayStack router saves the configuration file to the flash memory card for future use.

The BayStack router obtains at least one startup file f rom a remote workstation that is configur ed as a BootP server .

The BayStack router obtains at least one startup file f rom a remote workstation that is configur ed as a Trivial File Transfer Protocol (TFTP) server. You must specif y the IP address of the TFT P server and the complete path to the startup file(s) before booting.

the software image and generic startup configuration files stored in flash memory. You create a customized configuration file by running the Quic k-Start script.

• Serial connection configured wi th t he high-level data link control (HDLC) or frame relay protocol

• BootP server that contains the configuration file

• Management console

• BootP server that contains at least one startup file

• Connection over a frame rela y or HDLC (serial or DSU/CSU), Ethernet, or token ring (ARN only) interface

• Management console

• TFTP server that contains at least one startup file

• Connection over a frame rela y or HDLC (serial or DSU/CSU), Ethernet, or token ring (ARN only) interface

• Management console

• Installed flash memory card that contai ns the startup files

1-4

303516-A Re v 00

The Boot Process

The following sections describe the boot process for the Local Boot and Netboot startup options:

Understanding Tools and Options

• Netboot Process

(EZ-Install, Netboot, or Directed Netboot)

• Local Boot Process

Netboot Process

When booting over the network using EZ-Install, Netboot, or Directed Netboot, the BayStack router complet es the following tasks:

Determines its IP address

Obtains the operating- system kernel file and/or configuration f ile by communicating with a conf igured BootP server on the IP networ k

Reboots, using the newly transferred kernel file

Obtains applicati on and string files ove r the network as it needs them

5. Begins bridging and routing traffic as specified in the configuration file The followin g sections describe in more detail the key steps in this process:

• Obtaining an IP Address Manually (Netboot or Directe d Net boot) or Obtaining an IP Address Automatically (EZ-Install)

• Obtaining the Kernel and Configuration Files

Obtaining an IP Address Manually (Netboot or Directed Netboot)

303516-A Rev 00

For Netboot and Directe d Netboo t, you c onfigure the IP address manually.

Chapter 3 describes how to use Site Manager to con figure n et boot int erfa ces . Chapter 4 describes how to conf igure netboot using the Technician Interface.

Obtaining an IP Address Automatically (EZ-Install)

During the EZ-Install process, the BayStack router obtains its IP address as follows:

When you turn on the BayStack router, it runs a set of diagnostic tests.

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

1-5

Configuring BayStack Remote Access

The BayStack router sends the BootP request through all serial ports at approximately the same time, using the following protocols:

• Bay Networks Standard Point-to-Point Protocol (PPP) using high-level

data link control (HDLC) encaps ulation

• Frame Relay Annex D

• Frame Relay Local Management Interface (LMI)

• Frame Relay Annex A

Note:

The upstream router must ha ve a circuit running Bay Networks

Standard PPP using HDLC or a frame relay permanent virtua l circuit (PVC).

If the BayStack route r does not rec ei v e a response to the fir st BootP request, it issues a second request.

If the BayStack router does not receive a response in approximately four minutes, it boots the image and configuration files in its local file system, as described in “Local Boot Process

The first inte rface on the upstream router to receive the BootP request responds.

” on page 1-12.

1-6

The upstream router obtains the IP address of the BayStack router’s serial interface . The protoc ol configuration of the upstream router determines whether it calculates or requests the IP address, a s follows:

-- A frame relay PVC in direct access mode or a Bay Networks Standard

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

For example, in Figure 1-1

, the upstream router’s interface address is

192.32.1.1. This means tha t the upstream router calculates 192.32.1.2 as the BayStack router’s IP address.

Note:

If the IP address plus 1 equals a broadcast address, the upstream router calculates the IP addr ess by subt racting 1. For ex ample, if the IP address of the upstream router’s interface is 7.255.255.254, the IP address of the BayStack router is 7. 255.255.253.

303516-A Re v 00

Understanding Tools and Options

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. Calculating an IP Address

(Direct Access PVC or Standard PPP)

-- A frame relay PVC in group access mode refers to its BootP client interface table to find an associated IP address for the BayStack router.

Note:

The BootP client interface table contains a data link connection identif ier (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 3

303516-A Rev 00

For example, in Figure 1-2, the BayStack router sends BootP requests for its IP address. The upstream rout er receives the reque st on PVC 31. The upstream router deter mines the DLCI, refers to DLCI 31 in the BootP client interface table, finds the IP address, and sends a BootP response containing the IP address back to PVC 31.

1-7

Configuring BayStack Remote Access

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. Requesting an IP Address from the BootP Server (Group Access PVC)

The upstream router sends the IP address and subnet mask to the BayStack router in a BootP response message.

The BayStack router assigns the IP address a nd subnet mask to any serial interface that receives a BootP response.

The BayStack router stores the se IP addresses, along with the IP address of the next-hop router, in RAM.

If more than one serial interface receive s a BootP response, the BayStack router assigns an IP address to each interface.

1-8

303516-A Re v 00

AN/ANH/ARN

Understanding Tools and Options

Obtaining the Kernel and Configuration File s

With a known IP address, the BayStack router can obtain its operating-system kernel and conf iguration files over the network. The procedure is the same for EZ-Install, Netboot, and Directed Netboot.

The BayStack router sends a BootP request for the path names of the startup files.

The BayStack router issues the request simultaneously through all seria l (COM), Ethernet, and toke n ring (ARN only) interfaces that have IP addresses. The BayStack router issues this request period ically for approximately thr ee minutes, regardless of whether a cable is connected.

A BootP server responds to the BaySt ack ro uter’s request with the directory path names (Figure 1-3).

Upstream router

Pathnames

Corporate backbone

BOOTP server

Key

BOOTP request BOOTP response

Figure 1-3. Obtaining the Path Nam es of the Kernel and Configuration Files

The first router interfac e that processes the BootP response acts as the TFTP client in the remaining ste ps.

The BayStack router stops sending BootP requests.

303516-A Rev 00

NPA0003A

1-9

Configuring BayStack Remote Access

The BayStack router sends a TFTP request for the configuration file.

The BootP server uses TFTP to transfer the configuration file (Figure 1-4).

AN/ANH/ARN

Configuration file

Corporate backbone

Upstream router

Key

TFTP request TFTP transfer

Figure 1-4. Obtaining the Configuration File

The BayStack router sends a TFTP request for the kernel file.

The BootP server uses TFTP to transfer the kernel file (Figure 1-5).

BOOTP server

BOOTP response

NPA0004A

1-10

303516-A Re v 00

+ 110 hidden pages

Avaya BayStack Remote Access User Manual

Configuring BayStack Remote Access

Contents

Figures

Tables

Before You Begin

Preface

Text Conventions

Acronyms

Bay Netwo rks Technical Publicati o ns

How to Get Help

Network Configuration and Management Tools

BaySta ck Router Startup Procedure

Startup Files

Startup Options

The Boot Process

Netboot Process