Avaya Connecting ASN Routers to a Network User Manual

BayRS Version 14.00 Part No. 308652-14.00 Rev 00

September 1999 4401 Great America Parkway

Santa Clara, CA 95054

Connecting ASN Routers to a Network

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 a pplic a tions o f any products specifi ed in th is d ocum ent . The information in this document is proprietary to Nortel Networks NA Inc.

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

Trademarks

NORTEL NETWORKS is a trademark of Nortel Networks. Optivity is a registered trademark and ASN, BayRS, and BayStream are trademarks of Nortel Networ ks. Microsoft, MS, MS-DOS, Win32, Windows, and Windows NT are registered trademarks of Microsoft Co rporation. All other trademarks and registered trademarks are t he property of their respective owners.

Restricted Rights Legend

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

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

Statement of Conditions

In the interest of improvi ng internal design, operational func tion , a n d/o r re liability , No rtel Ne tworks NA Inc. re serv e s the right to make changes to the products described in this document without notice.

Nortel Networks NA 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 may be Copyright © 1988, Regents of the University 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 docu mentation, advertising materials, and other materials related to such distribution and use acknowledge that su ch 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 specific 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 containe d 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).

Nortel Networks NA Inc. Software License Agreement

NOTICE: Please carefully read this license agre ement before copying or using the accompanying software or installing the hardware unit with pre-enabled software (each of which is referred to as “Software” in this Agreement). BY COPYING OR USING THE SOFTWARE, YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS UNDER WHICH NORTEL NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept

308652-14.00 Rev 00

these terms and conditions, return the product, unused and in the original shipping container, within 30 days of purchase to obtain a credit for the full purchase price.

1. License Grant. Nortel Networks NA Inc. (“Nortel Networks”) grants the end user of the Software (“Licensee”) a personal, nonex clusive, nontransferable license: a) to use the Softw are eit her on a single compute r or, if applicable, on a single authorized device identified by host ID, for which it was originally acquired; b) to copy the Software solely for backup purposes in support of authorized use of t he Software; and c) to use and copy the associated user manual solely in support of authoriz ed use of th e Softwa re b y Licen see. Thi s license applies t o the So ftware o nly and d oes not extend to Nortel Networks Agent software or other Nortel Networks software products. Nortel Networks Agent software or other Nortel Networks software products are licensed for use under the terms of the applicable Nortel Networks NA 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 user manuals are protected und er copyright laws. Nortel Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including any revisions made by Nortel Networks or its licensors. The copyright notice must be reproduced and included with any copy of any portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use for any competitive analysis, reverse engineer, distribute, or create derivative works from the Software or user manuals or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer the Software or user manuals, in whole or in part. The Software and user manuals embody Nortel Networks’ and its licensors’ confidential and proprietary inte lle ctu al pro p erty. Licensee shall not sublicense, assign, or otherwise disclose to any third party the Software, or any information about the operation, design, performance, or implementation of the Software and user manuals that is confidential to Nortel Networks and its licensors; however, Licensee may grant permission to its consultants, subcontractors, a nd agents to use the Softw are at Licensee’s facility, provided they have agreed to use the Software only in accordance with the terms of this license.

3. Limited warranty . Nortel Networks warrants each item of Software, as delivered by Nortel Networks and properly installed and operated on Nortel Networks hardware or other equipment it is originally licensed for, to function substantially as described in its accompanying user manual during its warranty period, which begins on the date Software is first shipped to Licensee. If an y item of S oftware f ails to so function d uring its w arranty period, as the sole remedy Nortel Networks will at its discretion provide a suitable fix, patch, or workaround for the problem that may be included in a future Software release. Nortel Networks further warrants to Licensee that the media on which the Software is provided will be free from defec ts in materials and wo rkman ship under no rmal use for a peri od of 90 da ys from the date Software is first shipped to Licensee. Nortel Networks will replace defective media at no charge if it is returned to Nortel Netw orks during the warranty period along with proof of the date of ship ment. This warranty does not apply if the media has been damaged as a result of accident, misuse, or abuse. The Licensee assumes all responsibility for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained from the Software. Nortel Networks does not warrant a) that the functions contained in the software will meet the Licensee’s requirements, b) that the Software will operate in the hardware or software combinations that the Licensee may select, c) that the operation of the Software will be uninterrupted or error free, or d) that all defects in the operation of the Softw are will be corrected . Nortel Network s is not obligate d to remedy an y Software defect that cannot be reproduced with the latest Software release. These warranties do not apply to the Software if it has been (i) altered, except by Nortel Networks or in accordance with i ts instructions; (ii) used in conjunction with another vendor’s product, resulting in the de fect; or (iii) damage d by improper environment, abuse, misuse, accident, or negligence. THE FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITA T ION ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or altered files, data, or programs.

4. Limitation of liability. IN NO EVENT WILL NORTEL 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 DATA OR LOSS OF USE OR PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN IF NORTEL NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT

308652-14.00 Rev 00

iii

SHALL THE LIABILITY OF NORTEL NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT EXCEED THE PRICE PAID TO NORTEL NETWORKS FOR THE SOFTWARE LICENSE.

5. Government Licensees. This provision applies to a ll Softwa re and docum entation acquired d irectly or i ndirectly 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 th e use of any U.S. Government funds. The license to the U.S. Government is granted only with restricted rights, and use, duplication, or disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial Computer Software––Restricte d Rig hts cla u se o f FAR 52.227-19 and the limitations se t o ut in thi s 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 Department of Defense or their successors, whichever is applicable.

6. Use of Software in the European Community. This provision applies to all Software acquired for use within the European Community. If Licensee uses the Software within a country in the European Community, the Software Directive enacted by the Council of European Communities Directive dated 14 May, 1991, will apply to the examination of the Software to facilitate interoperability. Licensee agrees to notify Nortel Networks of any such intended examination of the Software an d may procure support and assistance from Nortel Networks.

7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to Nortel Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the Nortel Networks copyright; those restrictions relating to use and disclosure of Nortel Networks’ confidential information shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if Licensee fails to comply with any of the terms and conditions of the license. Upon termination for any reason, Licensee will immediat ely destroy or return to Nortel Networks the Software, user manuals, and all copies. Nortel 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, directly or indirectly, the Software or related technical data or information without first obtaining any required export licenses or other governmental approvals. Without limiting the foregoing, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that it will not, without first obtaining all export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or divert any such Software or technical data, or any direct product thereof, to any country to which such exports or re-exports are restricte d or em b argoed under United States export con tr o l la w s an d r egulations, or to an y national or resident of such restricted or embargoed countries; or (ii) provide the Software or related technical data or information to any military end user or for any military end use, including the design, development, or production of any chemical, nuclear, or biological weapons.

9. General. 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 Nortel Networks, 4401 Great America Par kwa y, P.O. Box 58185, Santa Clara, California 95054-8185.

LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN NORTEL 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 NORTEL NETWORKS UNLESS NORTEL NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT.

308652-14.00 Rev 00

Preface

Before You Begin .............................................................................................................xiii

Text Conventions .............................................................................................................xiii

Acronyms ........................... .......................... .......................... ......................... .................xiv

Related Publications ........................................................................................................ xv

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

Chapter 1 Selecting a Boot Configuration

Software Overview ..........................................................................................................1-1

Router Management Tools .......................................................................................1-2

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

Boot Configuration Options ......................................................................................1-2

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

Getting an IP Address ......................................................................................1-5

Getting the Software Image and Configuration Files .........................................1-9

Selecting the Startup Method .......................................................................................1-12

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

EZ-Install .........................................................................................................1-12

Netboot ............................................................................................................ 1-13

Local Boot ........................................................................................................1-13

Recommendations ............. .......................... ......................... .......................... . 1-13

Booting the Router Routinely .................................................................................1-14

Netboot ............................................................................................................ 1-14

Directed Netboot ..............................................................................................1-14

Local Boot ........................................................................................................1-15

Recommendations ............. .......................... ......................... .......................... . 1-15

308652-14.00 Rev 00

Completing a Network Boot Option .......................................................... ...... ....... .......1 -1 6

EZ-Install .. ................... ................... .................... ................... ................... ..............1-16

Netboot .... ................................................................ .............................................. 1-17

Directed Netboot ....................................................................................................1-19

Chapter 2 Setting Up a UNIX Boot Server

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

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

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

Setting Up BOOTPD to Run .....................................................................................2-2

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

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

Verifying Consistent BOOTP Service ................................................................2-8

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

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

Restricting TFTPD Access to a Specified Directory .................................................2-9

Creating Links ........................................................................................................2-10

Adding a TFTP User for an HP 9000 .....................................................................2-10

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

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

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

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

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

Chapter 3 Configuring Network Booting

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

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

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

Enabling Netboot or Directed Netboot ............................................................................3-4

Netboot and Directed Netboot Parameters ..............................................................3-6

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

Netboot Interface Parameters ......................................... ...... ...... ....... ...... ....... ...... .3-1 1

308652-14.00 Rev 00

Setting Up Routing Paths .............................................................................................3-15

Enabling Relay Interfaces ......................................................................................3-15

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

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

Creating a BOOTP Client Interface Table .....................................................................3-21

BOOTP Client Interface Parameters ......................................................................3-23

What to Do Next ...........................................................................................................3-24

Chapter 4 Setting Up an ASN as a Network Boot Client

Working with a Person at the ASN Site ..........................................................................4-1

Configuring the Router Boot Source ...............................................................................4-2

bconfig Command Format ........................................................................................4-2

bconfig Command Examples ...................................................................................4-3

Configuring the Netboot Interface ...................................................................................4-4

Configuring an IP Synchronous Interface ................................................................4-4

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

Enabling and Disabling Interfaces with ifconfig ........................................................4-7

ifconfig Command Examples ...................................................................................4-7

What to Do Next .............................................................................................................4-8

Appendix A Troubleshooting Network Boot Problems

Solving Startup Problems .............................................................................................. A-2

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

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

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

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

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

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

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

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

ASN Netboots, But Fails to Load Applications ........................................................ A-5

308652-14.00 Rev 00

vii

Identifying Remote Connectivity Problems .................................................................... A-6

Displaying Messages from the ASN ........................................................................ A-6

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

Using Packet Capture: Guidelines .......................................................................... A-7

Using a LAN Protocol Analyzer: Guidelines ............................................................ A-8

Resolving Connectivity Problems ...................... ....... ...... ....... ........................................ A-8

Displaying the ASN’s Parameter Settings ............................................................... A-9

Changing the ASN’s Parameter Settings .............................................................. A-10

Debugging the BOOTP Server .............................................................................. A-11

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

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

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

Quick Get Instructions .................................................................................... A-14

Technician Interface Instructions .................................................................... A-14

Upgrading Software ..................................................................................................... A-15

Appendix B Implementation Notes

Notes ............................................................................................................................. B-1

Hints .............................................................................................................................. B-2

Glossary Index

viii

308652-14.00 Rev 00

Figures

Figure 1-1. Getting an IP Address from a Nortel Networks Standard Circuit

or a Frame Relay PVC in Direct Access Mode ........................................1-7

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

Figure 1-3. Getting the Pathnames of the Software Image and

Configuration Files .................................................................................1-10

Figure 1-4. Getting the Startup Files ........................................................................1-11

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

Figure 3-1. Displaying the Netboot Interfaces Window ..............................................3-4

Figure 3-2. Edit Netboot Global Parameters Window .................................................3-5

Figure 3-3. Netboot Interfaces Window ............................. .........................................3-9

Figure 3-4. Netboot Interface Window .................. ...... ....... ...... ...... ....... ...... ....... .......3 -1 0

Figure 3-5. Displaying the BOOTP Relay Agent Interface Table ..............................3-17

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

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

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

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

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

308652-14.00 Rev 00

Tables

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

Table 1-2. Sample BOOTP Client Interface Table on Upstream Router ...................1-9

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

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

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

Table 2-4. Restricting TFTPD Access to One Directory ...........................................2-9

Table 3-1. Enabling BOOTP in a Sample Network .................................................3-16

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

Table 4-2. ifconfig Command Settings for a Synchronous Interface .........................4-5

Table 4-3. ifconfig Command Settings for an Ethernet Interface ..............................4-6

Table 4-4. ifconfig Settings to Enable and Disable Netboot Interfaces .....................4-7

Table A-1. BOOTP Messages ................................................................................ A-12

308652-14.00 Rev 00

This guide describes how to boot a Nortel Networks Access Stack Node (ASN™) router or BayStream

Before You Begi n

Before using this guide, you (or a person at the router site) must install the ASN hardware as described in Installing and Maintaining ASN Routers and BNX Platforms.

Preface

™

platform over a network interface to connect to a network.

Text Con ventions

This guide uses the following text conventions:

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

bold text

308652-14.00 Rev 00

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

Example: If the command syntax is:

ping

ip_address

ping 192.32.10.12

, you enter:

Indicates command names and options and text that you need to enter.

Example: Enter Example: Use the

show ip {alerts | routes

dinfo

command.

xiii

Connecting ASN Routers to a Network

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

screen text Indicates system output, for example, prompts and

titles, and variables in command syntax descriptions. Where a variable is two or mor e words, the words are connected by an underscore.

Example: If the command syntax is:

show at

valid_route

is one variable and you substitute one value

for it.

system messages.

Acronyms

Example:

Set Trap Monitor Filters

separator ( > ) Shows menu paths.

Example: Protocols > I P ide nti fies 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 enteri ng the command.

Example: If the command syntax is:

show ip {alerts | routes show ip alerts

}

show ip routes

This guide uses the following acronyms:

ARP Address Resolution Protocol ASN Access Stack Node BOOTP Bootstrap Protocol

, you enter either:

, but not both.

xiv

BOOTPD Boot Protocol Daemon BRI Basic Rate Interface DLCI data link connection identifier DLCMI data link control management interface

308652-14.00 Rev 00

Preface

GUI graphical user interface HDLC high-level data li nk control IP Internet P rotocol LMI Local Management Interface MIB management information base NMM network management module OSI Open Systems Interconnection PPP Point-to-Point Protocol PVC permanent virtual circuit RARP Reverse Address Resolution Protocol RFC Request for Comments SAM System Administration Manager SNMP Simple Network Management Protocol SPEX Stack Packet Exchange TCP/IP Transmission Control Protocol/Internet Protocol TELNET Telecommunications Network TFTP Trivial File Transfer Protocol TFTPD Trivial File Transfer Protocol Daemon

Related Publications

For more information about the ASN, refer to the following publications:

• Installing and Maintaining ASN Routers and BNX Platforms (Nortel Networks part number 109351-F)

Describes how to install the ASN and add or replace hardware. Provides instructions for completing a network boot option at the ASN site. Gives information to assist you in troubleshooting hardware problems.

• Quick-Starting Routers (Nortel Networks part number 308654-14.00) Read this manual for information on completing a local boot option (the

Quick-Start procedure) at the ASN site.

308652-14.00 Rev 00

Connecting ASN Routers to a Network

• Configuring and Mana ging Rout ers with Site Manager (Nortel Networks part number 308605-14.00)

Read this manual for information on configuring and managing an ASN after it is connected to the network.

• Troubleshooting Routers (Nortel Networks part number 308656-14.00) Describes how t o isol ate and solve problems associated with Nortel Networks

routers.

You can print selected technical manuals and release notes free, directly from the Internet. Go to support.baynetworks.com/library/tpubs/. Find the product for which you need documentation. Then locate the specific category and model or version for your hardw are or soft ware product . Usi ng Adobe Ac robat Re ader, you can open the manuals and releas e notes, search for the sections you ne ed, and print them on most standard printers. You can download Acrobat Reader free from the Adobe Systems Web site, www.adobe.com.

You can purchase selected documentation sets, CDs, and technical publications through the collateral catalog. The catalog is located on the World Wide Web at

support.baynetworks.com/catalog.html and is divided into sections arranged

alphabetically:

xvi

• The “CD ROMs” section lists available CDs.

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

• The “Technical Manuals” section lists available printed documentation sets.

308652-14.00 Rev 00

How to Get Help

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

If you purchased a Nort el Net wor ks s ervice pr ogram, c ontact one of the f ollowing Nortel Networks Technical Solutions Centers:

Technical Solutions Center Telephone Number

Billerica, MA 800-2LANWAN (800-252-6926) Santa Clara, CA 800-2LANWAN (800-252-6926) Valbonne, France 33-4-92-96-69-68 Sydney, Australia 61-2-9927-8800 Tokyo, Japan 81-3-5402-7041

Preface

308652-14.00 Rev 00

xvii

Chapter 1

Selecting a Boot Configuration

This chapter helps you sel ect a method for starti ng an ASN platfor ms, either at the initial startup of a new ASN or at boot time in day-to-day operations. Read the first section, “Software Overview process, and the four startup configuration options. Refer to one of the following sections for help in selecting a startup option:

• “Booting the Router for the First Time”

,” to learn about the router software, the boot

•“Booting the Router Routinely

The last section , “Co mpleting a Netw ork Boot Option take to complete each startup method.

Software Overview

Read this section for summary information about the ASN router software. It describes

• Tools available for configuring and managing an ASN

• Kernel and application files

• Boot configuration options

• Network boot process

ASN routers support major LAN and WAN protocols, and dialup services. As for all Nortel Networks routers, ASN software provides extensive MIB variable support, including Standard MIB II and the Nortel Networks proprietary MIB.

”

,” summarizes th e step s you

308652-14.00 Rev 00

1-1

Connecting ASN Routers to a Network

Router Management Tools

You configure and manage an ASN using

•The Technician Interface, a command- line interface which operates in router memory. You execute Technician Interface commands and scripts either from an attached console or from a remote console via a modem.

• Site Manager software, an SNMP-based application with a graphical user interface. You run Site Manage r at a w or kstat ion tha t i s connec ted, along wit h the router, to an IP network.

• Optivity application for administering and troubleshooting large, complex networks. The Optivity/RM package includes Site Manager, PathMan, and RouterMan software.

/RM (Router Management), a comprehensive network management

Router Software

Before it can operate, the ASN hardware needs to boot a software image. To bridge and route traffic, the ASN also needs a configuration file that is tailored to your network.

The router software imag e, asn.exe, comprises the following executable files:

•The krnl_asn.exe software image file, which contains the operating system kernel.

• Application files -- executable fil es needed to perform the func ti ons specified in the configuration file. All application files have .exe filename extensions. (For example, the router needs an ipx.exe executable file to run IPX.)

Boot Configuration Options

This section summarize s your opt ions for getting the ASN soft ware i mage f ile an d configuration files.

An ASN boots using one of four configured startup options. The differences among the four ASN sta rtup opt ions are based on whether the rout er retri ev es b oot and configuration files over the network or from local memory.

1-2

308652-14.00 Rev 00

Selecting a Boot Configura tio n

Getting a software image or configuration file over the network is called Netbooting. Getting a file from the file system stored in local Flash memory is called Local booting.

To initially start up the ASN, you can use one of these options:

• EZ-Install (the default)

• Netboot

• Local Boot

To start up the ASN after the initial configuration, you use one of these boot configuration options:

• Netboot

• Directed Netboot

• Local Boot

Table 1-1

summarizes the start up opt ions. The secti on tha t follows, “The Network

Boot Process,” describes what happens when you use each option.

Table 1-1. Summary of Boot Options

Source for Boot Option

EZ-Install Local

Software

Image

(Flash

memory)

Source for Config File Description and Requirements

Network (Synchronous

connection)

The default option. The 100BASE-T Hub boots from a software image in local memory, then transmits a request for its IP address and configuration file through an attached synchronous interface.

Next, a remote UNIX- or DOS-based workstation that is configured as a Boot Protocol (BOOTP) server downloads a customized configuration file; you save that configuration to Flash memory.

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

If EZ-Install fails, the router tries th e Local Boot pr ocedure.

(continued)

308652-14.00 Rev 00

1-3

Connecting ASN Routers to a Network

Table 1-1. Summary of Boot Options

Source for Boot Option

Netboot

Directed Netboot

Local Boot

Software

Image

Network

(Synchronous

or Ethernet

connection)

Network

(Synchronous

or Ethernet

connection)

Local

(Flash

memory)

Source for Config File Description and Requirements

Network (Synchronous

or Ethernet connection)

Network (Synchronous

or Ethernet connection)

Local (Flash

memory)

The 100BASE-T Hub obtains all startup files from a remote UNIX- or DOS-based workstation that is configured as a BOOTP server. (Getting these files individually, rather than getting the entire usage and prevents saturation of the router’s memory. )

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

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

UNIX- or DOS-based workstation that is configured as a Triv ial File Transfer Protocol (TFTP) server. You specify the IP address of the TFTP server and the pathname of the startup files before booting.

Requires a local console co nne cti on and a comm u ni cat ion s link over an HDLC, Frame Relay, or Ethernet interface.

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

The 100BASE-T Hub boots using a software router image and configuration file sto red in local memory.

During the initial startup, the ASN uses a generic startup configuration fil e. You customiz e the def ault confi guration file by assigning an IP address to an interface and running an installat ion script; this is called the

(continued)

asn.exe

The 100BASE-T Hub obtains all startup files from a remote

file, minimizes the cost of line

file, a local co nsole con nection an d

Quick-Start

procedure.

1-4

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

308652-14.00 Rev 00

The Network Boot Process

This section describes the boot process for the network boot options. For information on the Local Boot procedure, see Quick-Starting Routers.

The following occurs when the ASN boots over the network via EZ-Install, Netboot, or Directed Netboot:

The ASN boots a software image that resides on a local file system flash

asn.exe

card (

The local software image configures the ASN’s network interfaces to use IP.

The router determines its IP address.

The router obtains a software image file and/or configuration file by communicating with a configured BOOTP server on the IP network.

The router reboots, using the newly transferred image.

The router begins bridging and routing network traffic in accordance with the configuration file.

Selecting a Boot Configura tio n

The followi ng sections descri be ke y steps in t he process -- obtainin g an IP addre ss and downloading the image and configuration files -- in greater detail.

Getting an IP Address

The ASN gets its IP address from a central-point upstream router.

Note:

Standard protocol or a Frame Relay permanent virtual circuit (PVC) in direct or group access mode.

Obtaining the IP Address Manually (Netboot and Directed Netboot)

For Netboot and Directed Netboot, yo u c onfigure the ASN’s IP address manually. Chapter 3 describes how to use Site Manager to configure Netboot interfaces. Chapter 4 describes how to configure the IP address using the Technician Interface.

308652-14.00 Rev 00

The upstream router has either a circuit running Nortel Networks

1-5

Connecting ASN Routers to a Network

Obtaining the IP Address A utomatically (EZ-Install)

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

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

The ASN boots the

The ASN sends a BOOTP request to the upstream router for an IP

asn.exe

software image in local flash memory.

address and subnet mask.

The ASN issues the request through all synchronous 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:

• Nortel Networks Standard HDLC (high-level data link control) encapsulation

• Frame Relay Annex D

• Frame Relay Local Management Interface (LMI)

• Frame Relay Annex A

If the ASN does not receive a response it boots with the files in the local file system, as described in the “Local Boot

The first interface on the upstream router to receive the BOOTP request

” section later in this ch apter.

responds.

The upstream router calculates the IP address of the ASN’s synchronous interface.

How the upstream router calculates the IP address depends on its protocol configuration. See Step a if the upstream router circuit is running Nortel Networks Standard or is a Frame Relay permanent virtual circuit (PVC) in direct access mode. See Step b if it is a Frame Relay PVC in group access mode.

1-6

A PVC in direct access mode or a Nortel Networks Standard 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 that the upstream router calculates 192.32.1.2 as the bootin g router’s IP interface.

308652-14.00 Rev 00

Selecting a Boot Configura tio n

ASN router

BOOTP response with IP address

192.32.1.2

IP address 192.32.1.1

Key

BOOTP request BOOTP response

Upstream router

CAS0001A

Figure 1-1. Getting an IP Address from a Nortel Networks 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 addre ss by subtractin g 1. For example, if its interface is

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

A PVC in group access mode references its BOOTP client interface table to find an associated IP address for the booting router.

Note:

The BOOTP client interface table contains a data link connection identifier (DLCI) and IP address pair for each PVC. You use Site Manager to create this table when you follow the instructions in Chapter 3.

308652-14.00 Rev 00

1-7

Connecting ASN Routers to a Network

For example, in Figure 1-2, routers 1, 2, and 3 send BOOTP requests for IP addresses.

Circuit containing three (3) PVCs (DLCIs 31, 32, and 33 for virtual connections to routers 1, 2, and 3)

Key

Booting router 2Booting router 1 Booting router 3

Frame Relay

BOOTP request BOOTP response

Upstream router

CAS0002A

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

The upstream router receives the requests on PVCs 31, 32, and 33, respectively.

The upstream router refers to DLCI 31 in the BOOTP Client Interface Table (Table 1-2

), finds the IP address (192.32.16.17) associated with the DLCI, and sends a BOOTP response containing the IP address back to PVC 31.

The upstream router does the same for the other two circuits.

1-8

308652-14.00 Rev 00

Selecting a Boot Configura tio n

Table 1-2. Sample BOOTP Client Interface Table on Upstream Router

DLCI of Incoming BOOTP Request for IP Address Response

31 192.32.16.17 32 192.32.16.18 33 192.32.16.19

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

The ASN assigns the IP address and subnet mask to any synchronous interface that receives a BOOTP response.

The ASN stores these addresses, along with the address of the next-hop router, in RAM.

Getting the Software Image and Configuration Files

After it gets the IP addr es s, th e ASN obt ain s it s s oft ware image and conf ig ura ti on files as follows:

308652-14.00 Rev 00

The ASN sends a BOOTP request for the pathnames of a configuration file and software image file.

The ASN issues this request simultaneously through all synchronous and Ethernet interfaces that have IP addresses. It issues this request periodically through these ports for about 3 minutes, regardless of whether a cable is connected.

1-9

Connecting ASN Routers to a Network

A BOOTP server responds to the router’s request with the directory pathnames; the ASN stops sending BOOTP requests for the pathnames

(Figure 1-3)

The first ASN interface that processes the BOOTP response acts as the TFTP client in the remaining steps.

ASN router

Key

BOOTP request

BOOTP server

Pathnames

Corporate backbone

BOOTP response

CAS0003A

Figure 1-3. Getting the Pathnames of the Software Image and Configuration Files

The ASN sends a TFTP request for the configuration file.

The BOOTP server uses TFTP to transfer the configuration file

1-10

(Figure 1-4)

The ASN sends a TFTP request for the image file.

The BOOTP server uses TFTP to transfer the image file (Figure 1-4).

308652-14.00 Rev 00

Selecting a Boot Configura tio n

ASN router

1. Configuration file

2. Kernel

3. Application files

Corporate backbone

BOOTP server

Key

TFTP request TFTP response

CAS0004A

Figure 1-4. Getting the Startup Files

The router boots.

The router uses TFTP to get application files as it needs them.

The ASN can continue to request files, even after it begins bridging and routing traffic.

The router begins bridging and routing network traffic in accordance with the configuration file.

If a network boot fails, the ASN waits to be booted by a neighboring slot. (A single-slot A SN will inste ad attempt the Local Boot procedure.)

Note:

The ASN supports Netbooting over multiple slots. The first slot to

retrieve startup files forces the other slots to use those files.

308652-14.00 Rev 00

1-11

Connecting ASN Routers to a Network

Selecting the Startup Method

Use the information in the following sections to choose the boot method for both the initial startup of the ASN and fo r day-to-day operations. Refer to the la st section of this chapter, “Completing a Network Boot Option the steps for completing the method you choose.

Booting the Router for the First Time

You coordinate the A SN’s initial startup with a person at the route r s ite, who physically insta ll s and cables the ASN and initiates the des ir ed startup procedure. The manual Installing and Maintaining ASN Routers and BNX Platforms describes these tasks in detail.

Note:

To boot using any method, the asn.exe image must be on the local ASN

file system.

After you select the initial startup configuration (and set up the network as described in thi s guide), d irect t he person a t the rout er site to be gin th e approp riate startup option.

,” for a summary of

1-12

Note:

As an alterna tive to ano ther person performing the initial startup at the

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

EZ-Install

EZ-Install is the default option for a new ASN router. You can use EZ-Install for the initial startup if

• There is a communic ations l ink betwe en the ASN and an ups tream rout er o ver an HDLC or Frame Relay interface.

• A directory on a BOOTP server contains a customized configuration file for the ASN.

EZ-Install is the easie st opti on fo r the person a t the ASN si te to pe rf orm, s ince t he network automatically supplies the IP address and configuration file. This option does not require a router connection to a modem or console.

308652-14.00 Rev 00

+ 78 hidden pages

Avaya Connecting ASN Routers to a Network User Manual

Connecting ASN Routers to a Network

Contents

Figures

Tables

Before You Begi n

Preface

Text Con ventions

Acronyms

Related Publications

How to Get Help

Software Overview

Router Management Tools

Router Software

Boot Configuration Options

The Network Boot Process

Getting an IP Address

Getting the Software Image and Configuration Files

Selecting the Startup Method

Booting the Router for the First Time

EZ-Install