Avaya Quick-Starting Routes User Manual

Quick-Starting Routers

BayRS Version 13.00 Site Manager Software Version 7.00 BCC Version 4.05

Part No. 303553-A Rev 00 October 1998

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

and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Bay Networks, Inc.

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

Trademarks

AN, BCN, BLN, BN, FRE, Optivity, PPX, and Bay Networks are registered trademarks and Advanced Remote Node, ANH, ARN, ASN, BayRS, BaySecure, BayStack, BayStream, BCC, Nautica, SPEX, System 5000, and the Bay Networks logo are trademarks of Bay Networks, Inc.

Microsoft, MS, MS-DOS, Win32, Windows, and Windows NT are registered trademarks of Microsoft 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 restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

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

Statement of Conditions

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

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

Portions of the code in this software product 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 thi s paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and u se acknowledge that suc h 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 MERCHANT ABILIT Y AND FITNESS FOR A PARTICULAR PURPOSE.

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

303553-A Rev 00

Bay Networks, Inc. Software License Agreement

NOTICE: Please carefully read this license agreement before copying or u s in g the accompanying software or installing the hardware un it with pre-enabled software (each of which is re ferred to as “So ftwa re” i n this Ag re eme nt) . 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 accep t 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. Bay Networks, Inc. (“Bay Networks”) grants the end user of the Software (“Licensee”) a personal, nonexclusive, nontransferable license: a) to use the Software eith er on a single computer 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 aut horized use of the Software; and c) to use and copy the associated user manual solely in support of auth orized use of th e So ftware by Lic ensee. This lic ense ap plies to th e Softwa re only and do es no t extend to Bay Networks A gent software or other Bay Netw orks software products. Bay Networks Agent so f tware or other Bay Networks software products are licensed for use under the terms of the applicable Bay Networ ks, 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 pro t ected under copyright laws. Bay Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including any revisions made by Bay Networks or its licensors. The copyright notice must be reproduced and included with any copy of any portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use for any competitive analysis, reverse engineer, distribute, or create derivative works from the Software or user manuals or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer the Software or user manuals, in whole or in part. The Software and user manuals embody Bay Networks’ and its licensors’ confidential and proprietary intellectual property. Licensee shall not sublicense, assign, or otherwise disclose to any third party the Software, or any informatio n about the operation, design, perfor mance, or implementation of the Software and user manuals that is confidential to Bay Networks and its licensors; however, Licensee may grant permission to its consultan ts, subcon tractors, and agents to use th e 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 Networks and properly installed and operated on Bay Networks hardware or other equipment it is originally licensed for, to function substantially as described i n i ts accompanying user manual durin g i ts warranty period, which begins on the date Software is first shipped to Licensee. If any item of Software fail s to so fu nction during its warranty perio d, as the sole remedy Bay Networks w il l at its discretion provide a suitable fix, patch, or workaround for the problem that may be included in a future Software release. Bay Networks further warrants to Licensee that the media on which the Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days from the date Software is first shipped to Licensee. Bay Networks will replace defective media at no charge if it is returned to Bay Networks during the warranty period along with proof of the date of shipment. This warranty does not apply if the media has been dama ged as a re sult of ac cident, mi suse, or abuse. The Lic ensee assumes a ll responsibilit y for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained from the Software. Bay Networks does not warrant a) that the functions contained in the software will meet the Licensee’ s re q uirem ents, b) t hat th e So ftware will o pera te in th e hardwa re o r software c omb inations that the Licensee may select, c) that the operation of the Software will be uninterrupted or error free, or d) that all defects in the operation of the Software will be corrected. Bay Networks is not obligated to remedy any Software defect that cannot be reproduced with the la test S oftware rele ase. The se warrantie s d o n ot app ly to th e So ftware if it ha s b een (i ) a ltere d, except by Bay Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’s product, resulting in the defect; or (iii) damaged by improper environment, abuse, misuse, accident, or negligence. THE FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of

303553-A Rev 00

iii

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 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 DATA OR LOSS OF USE OR PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT EXCEED THE PRICE PAID TO BAY NETWORKS FOR THE SOFTWARE LICENSE.

5. Government Licensees. This provision applies to all Software and documentation acquired 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 en tirely at private expense and without the use of any U.S. Government funds. The license to the U.S. Gove rnm ent is gr anted o nly with restric te d rights, and use, du p lic ation , or disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial Computer Software––Restricted Ri gh ts cla use o f FAR 52.227-19 and the limit ation s se t o ut in th is lic e nse fo r civ ilia n 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 succes sors, 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 interope rabilit y. Licensee agrees to notify Bay Networks of any such intended examination of the Software and may procure support and assistance from Bay Networks.

7. Term and termination. 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 restrictions relating to use and disclosure of Bay 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 immediately destroy or return to Bay Networks the So ftware, user manuals, and all copi es. 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, directly or indirectly, the Software or related technical data or information without first o btain ing a ny req ui red exp ort li cen ses o r other gov ernm e nt al a p pro vals. 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 , tr ansfer, or divert any such Software or te ch ni ca l da ta , or an y di r ect pro du c t the r eof , to any co un try to whi ch su ch ex po rt s or re-e xp orts are restricted or em b argoed under United Sta te s exp ort c on trol laws and regulations, 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 Bay Networks, Inc., 4401 Great America Parkway, P.O. Box 581 85, Santa Clara, California 95054-81 85.

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

303553-A Rev 00

Contents

Preface

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

ASN Terminology .............................................................................................................xiv

Text Conventions .............................................................................................................xiv

Acronyms ........................... .......................... .......................... ......................... .................xvi

Bay Networks Technical Publications .............................................................................xvii

How to Get Help ............................................................................................................xviii

Chapter 1 Overview of Quick-Start

Chapter 2 Preparing the Router for Quick-Start

Connecting a PC or Terminal Console ...........................................................................2-2

Connecting a PC ......................................................................................................2-2

Connecting a Terminal Console ...............................................................................2-3

Connecting to the IP Network .........................................................................................2-4

Logging On to the Technician Interface ..........................................................................2-5

Using Technician Interface Commands ..........................................................................2-6

Reviewing the Installation Files ......................................................................................2-8

Booting with the ti.cfg File ........ ....... ...... ....... ...... ....... ....................................................2-10

Chapter 3 Preparing Your Network Information

Using the Quick-Start Worksheet ...................................................................................3-2

Using the Quick-Start ATM Worksheet ...........................................................................3-7

Using the Quick-Start Worksheet for WAN Protocols ...................................................3-12

303553-A Rev 00

Chapter 4 Using the Installation Script to Quick-Start a Router

Quick-Start Troubleshooting ...........................................................................................4-4

Chapter 5 Using the BCC to Quick-Start a Router

Overview of the BCC ......................................................................................................5-2

Essential BCC Commands .............................................................................................5-4

Quick-Starting Your Router with the BCC .......................................................................5-5

Quick-Start Troubleshooting with the BCC ...................................................................5-13

Chapter 6 Completing the Router Configuration

Selecting a Configuration T ool ........................................................................................6-1

Completing the Configuration Procedure .......................................................................6-2

Communicating with the Router Remotely .....................................................................6-3

Telnet Connections ...................................................................................................6-3

Out-Of-Band Connections ........................................................................................6-3

Router Memory Card Distribution ............................................................................6-4

Chapter 7 Securing the Router

Assigning a Password to the Technician Interface ..........................................................7-2

Securing New Routers with the BCC or the Installation Script .......................................7-3

Setting Global IP Access Policies with the BCC .............................................................7-3

Restricting Read/Write Access with SNMP Communities ..............................................7-3

Setting Secure Mode ......................................................................................................7-4

Specifying Secure Mode ..........................................................................................7-5

Authentication Failure Traps ...........................................................................................7-6

Assigning SecurID to Telnet Connections .......................................................................7-6

Turning Off FTP and Telnet on the Router ......................................................................7-6

Using the Image Builder to Remove Services ................................................................7-6

Restricting Access to the HTTP Server ..........................................................................7-7

Configuring Data Encryption Services ............................................................................7-7

Configuring RADIUS .......................................................................................................7-8

Installing BaySecure FireWall-1 ................... ...... ....... ...... ....... ...... ...... .............................7-8

303553-A Rev 00

Chapter 8 Installing Site Manager on a PC

System Requirements ................................. ...... ....... ...... ....... ...... ...... ....... ...... ................8-1

Updating TCP/IP, Network Adapters, and Drivers ..........................................................8-2

Preparing the Network Control Panel .......................................................................8-3

Testing TCP/IP .........................................................................................................8-3

Loading and Starting Site Manager Software .................................................................8-4

Chapter 9 Installing Site Manager on a Workstation Running Windows NT

System Requirements ................................. ...... ....... ...... ....... ...... ...... ....... ...... ................9-1

Preparing the Network Control Panel .............................................................................9-2

Testing TCP/IP ................................................................................................................9-2

Loading and Starting Site Manager Software .................................................................9-3

Chapter 10 Installing Site Manager on a SPARCstation

System Requirements ................................. ...... ....... ...... ....... ...... ...... ....... ...... ..............10-2

Setting Up the SPARCstation .......................................................................................10-2

Loading Site Manager Software ...................................................................................10-3

Mounting a CD-ROM Drive on SunOS and Solaris ................................................10-3

Installing the Software .................... ....................................... ...... ....... ...... ....... ...... .10-4

Unmounting the CD-ROM Drive .............................................................................10-4

Setting Up Site Manager User Accounts ......................................................................10-5

Verifying Site Manager Installation ...............................................................................10-6

Starting Site Manager ...................................................................................................10-6

Starting Site Manager from SunNet Manager ........................................................10-8

Starting Site Manager from OpenView ..................................................................10-9

Chapter 11 Installing Site Manager on an IBM Workstation

System Requirements ................................. ...... ....... ...... ....... ...... ...... ....... ...... ..............11-2

Loading Site Manager Software ...................................................................................11-2

Mounting a CD-ROM Drive ................... ...... ....... ...... ....... .......................................1 1-3

Installing the Software .................... ....................................... ...... ....... ...... ....... ...... .11-3

Unmounting the CD-ROM Drive .............................................................................11-4

303553-A Rev 00

vii

Setting Up Site Manager User Accounts ......................................................................11-4

Verifying Site Manager Installation ...............................................................................11-5

Starting Site Manager ...................................................................................................11-6

Starting Site Manager from NetView for AIX ..........................................................11-7

Chapter 12 Installing Site Manager on an HP 9000 Workstation

System Requirements ................................. ...... ....... ...... ....... ...... ...... ....... ...... ..............12-2

Loading Site Manager Software ...................................................................................12-2

Mounting a CD-ROM Drive ................... ...... ....... ...... ....... .......................................1 2-3

Installing the Software .................... ....................................... ...... ....... ...... ....... ...... .12-3

Unmounting the CD-ROM Drive .............................................................................12-4

Setting Up Site Manager User Accounts ......................................................................12-4

Verifying Site Manager Installation ...............................................................................12-5

Starting Site Manager ...................................................................................................12-6

Starting Site Manager from OpenView ..................................................................12-7

Appendix A Sample Installation Script

Appendix B Sample ATM Installation Script

Index

viii

303553-A Rev 00

Figures

Figure 3-1. Network Example for the Quick-Start Worksheet ....................................3-3

Figure 3-2. Network Example for the Quick-Start ATM Worksheet ............................3-8

Figure 5-1. Configuring IP and RIP on an Ethernet Interface ....................................5-3

Figure 8-1. Site Manager Window ..............................................................................8-5

Figure 9-1. Site Manager Window ..............................................................................9-5

Figure 10-1. Site Manager Window ............................................................................10-7

Figure 10-2. Starting a Site Manager Session from SunNet Manager .......................10-8

Figure 10-3. Starting a Site Manager Session from OpenView .................................10-9

Figure 11-1. Site Manager Window ............................................................................11-7

Figure 11-2. Starting a Site Manager Session from NetView .....................................11-8

Figure 12-1. Site Manager Window ............................................................................12-7

Figure 12-2. Starting a Site Manager Session from OpenView .................................12-8

303553-A Rev 00

Table 2-1. Initial Router Connectors to the IP Network .............................................2-4

Table 2-2. Basic Technician Interface Commands ....................................................2-7

Table 2-3. Quick-Start Installation Files ....................................................................2-9

Table 2-4. Router Software Images ......................................................................2-10

Table 3-1. Quick-Start Worksheet ............................................................................3-4

Table 3-2. Quick-Start ATM Worksheet ....................................................................3-9

Table 3-3. Quick-Start Worksheet for WAN Protocols ...........................................3-12

Table 4-1. Installation Script Commands ..................................................................4-2

Table 5-1. Essential BCC System and Navigation Commands ................................5-4

Tables

303553-A Rev 00

Preface

If you are responsi ble for ac ti v atin g a Bay Netw orks® router on an IP net wo rk, t his guide can help you to configure the router’s initial network interface. When you complete the Q uick-Start i nstallation p rocedure, the router will actively route IP traffic on your network.

You can use the Quick-Start installation script or the

™

(BCC

)

to configure the initial IP interface over Ethernet on Bay Networks routers running BayRS the BCC

and the Quick-Start installation script to quick-start a router

This guide also provides information about securing your router and instructions for installing the Site Manager configuration tool on a PC or workstation.

The procedures in this gui de are int ended primarily for ne w i nst allations, but they are also used in the upgrade procedure. Before using this book as part of an upgrade, see the upgrade guide.

Before You Begi n

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

• Install the router (refer to the installation guide that came with your router):

-- Installing and Maintaining BN Routers

-- Installing and Maintaining ASN Routers

-- Installing and Operating BayStack AN and ANH Routers

-- Installing and Operating BayStack ARN Routers

Bay Command Console

™

In this guide, you will find instructions for using both

303553-A Rev 00

-- Quick Installation and Reference for the System 5000 Net Modules

• Review the Read Me First and Release Notes documents for any changes to

the Quick- Start instructions.

xiii

Quick-Starting Routers

Following are other considerations for using Quick-Start:

• The Quick-Start procedure does not apply to the Nautica

see Nautica documentation for all instructions.

• For specific booting and installation script procedures for BayStack

Node (AN (ARN

• For Access Stack Node (ASN

ASN Routers to a Network. For ASN local booting requirements, such as using the its local configuration file, see Installing and Maintaining ASN Routers.

ASN Terminology

ASN routers use unique terminology to identify the location of their connectors. Four ASN nodes can be stacked together as a single router. You assign a slot number to each node using a dial on its rear panel. Each slot has four module positions where the net modules reside. You identify connector position by first specifying the slot and module number s. F or mor e informa tion, see Installing and Maintaining ASN Routers.

™

series of routers;

™

), Access Node Hub (ANH™), and Advanced Remote Node

™

) routers, see Configuring BayStack Remote Access.

™

) network booting info rmation, see Co nnecting

bconfig config local and boot commands to allow the ASN to use

Access

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

xiv

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 text that you need to enter and command names and options. Example: Enter

show ip {alerts | routes

Example: Use the

dinfo

command.

}

303553-A Rev 00

Preface

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:

show ip {alerts | routes}, you must enter either: 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:

show ip interfaces [-alerts], you can enter either: show ip interfaces or show ip interfaces -alerts

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

command as needed. Example: If the command syntax is:

ethernet/2/1 [< ethernet/2/1 and as many parameter-value pairs as

parameter> <value>

] . . ., you enter

needed.

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 variable and you substitute one value

for it.

screen text Indicates system output, for example, prompts and

system messages. Example:

Set Bay Networks Trap Monitor Filters

303553-A Rev 00

Quick-Starting Routers

separator ( > ) Shows menu paths.

Example: Protocols > I P ide nti fies the IP option on the Protocols menu.

Acronyms

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:

show ip {alerts | routes show ip alerts

}

, you enter either:

show ip routes

, but not both.

BootP Bootstrap Protocol FDDI Fiber Distributed Data Interface FTP File Transfer Protocol HTTP Hypertext Transfer Protocol IP Internet P rotocol ISO International Organization for Standardization ITU-T International Telecommunication Union -

Telecommunication Standardization Sector (forme rly CCITT)

xvi

LAN local area network MAC media access control NIC network interface card NVFS nonvolatile file system OSPF Open Shortest Path First (protocol) PPP Point-to-Point Protocol PVC permanent virtual circuit QENET Quad Ethernet link module RIP Routing Information Protocol

303553-A Rev 00

SNMP Simple Network Management Protocol SRM System Resource Module SRM-L System Resource Module-Link TCP/IP Transmission Control Protocol/Internet Protocol TFTP Trivial File Transfer Protocol WAN wide area network

Bay Networks Technical Publications

You can now print Bay Networks technical manuals and release notes free, directly from the Internet. Go to support.baynetwork s.com/libr a ry/tpubs/ . Fi nd the Bay Networks product for which you need documentation. Then locate the specific category and model or ve rsion for your hardware or software product. Using Adobe Acrobat Re ader, you can open the manuals and rel ease n otes, searc h 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.

Preface

303553-A Rev 00

You can purchase Bay Networks documentation sets, CDs, and selected technical publications through the Bay Networks Collateral Catalog. The catalog is located on the World Wide Web at support.baynetworks.com/catalog.html and is divided into sections arranged alphabetically:

• 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. Make a note of the part numbers 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.

xvii

Quick-Starting Routers

How to Get Help

For product assistance, 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

xviii

303553-A Rev 00

Chapter 1

Overview of Quick-Start

The Quick-Start procedure boots your router locally and configures its initial interface to an IP network. To complete the Quick-Start procedure, follow these steps:

Connect a PC or ASCII console to the router.

Connect a PC or a terminal to the router’s console port to access the Technician Interface (Chapter 2)

Connect the router to the IP network.

303553-A Rev 00

Connect a cable between the router and the IP network (Chapter 2)

Establish a Technician Interface session.

Use the Technician Interface to run the installation script or to start the BC C

(Chapter 2)

Boot the router with the

(Chapter 2)

Prepare your network information using the appropriate works heet (Chapter 3).

Decide whether to quick-start the router with:

• The installation script (install.bat) The installation script starts all supported routers. Run the installation

script as described in Chapter 4, “

Quick-Star t a Router.”

• BCC commands You can also quick-start the rout er us ing BCC commands for an in it ia l IP

connection over Ethernet (Chapter 5).

ti.cfg

file to prepare it for Quick-Start

Using the In stallation Script to

1-1

Quick-Starting Routers

Complete your configuration.

Review the general procedure (Chapter 6)

you need to follow to complete the

router’s configuration using one or more of the following Bay Networ ks tools:

• Bay Command Console

•Site Manager

• NETarchitect

• Technician Interface

• HTTP Server

Secure your router.

Review the security mechanisms you can implement for your router (Chapter 7).

Install Site Manager.

If you choose Site Manager as your configuration tool, this guide provides installation instructions. Follow the instructions in the appropriate ch apter to install Site Manager soft ware on one of the following platfo rms:

• PC running Windows

• Workstation running Windows NT

95 (Chapter 8)

(Chapter 9)

• SPARCstation (Chapter 10)

1-2

• IBM workstation (Chapter 11)

•HP

9000 workstation (Chapter 12)

303553-A Rev 00

Chapter 2

Preparing the Router for Quick-Start

To prepare your router for the Quick-Start installation, yo u make the router’s physical connections, access the router’s command-line interface, and boot with the proper installation file.

This chapter contains the following topics:

Topic Page

Connecting a PC or Terminal Console 2-2 Connecting to the IP Network 2-4 Logging On to the Technician Interface 2-5 Using Technician Interface Commands 2-6 Reviewing the Installation Files 2-8 Booting with the ti.cfg File 2-10

303553-A Rev 00

2-1

Quick-Starting Routers

Connecting a PC or Terminal Console

You make a local terminal conn ect ion to your router, using a terminal program on a PC or a terminal console, to access the router’s Technician Interface. At the Technician Interface prompt, you enter the commands for the Quick-Start procedure.

Connecting a PC

To connect a PC to the router:

Set the communications parameters in your terminal-emulation program.

For example, to set the HyperTerminal program that comes with Microsoft Windows

b. c.

95:

From the Start Menu, choose Programs > Accessories > HyperTerminal.

Double-click on Hypertrm.exe. In the Connection Description window, enter a name for the

connection and choose an icon for the terminal program to display.

2-2

Click on OK.

In the Phone Number window, scroll through the Connect Using Box and choose the COM port with the cable connection to the router.

This procedure sets up the terminal program to make a direct connection, instead of a phone connection.

Click on OK.

Choose Settings

Configure the port settings for your COM port as follows:

Communications.

• Bits per second = 9600

• Data bits = 8

• Parity = none

• Stop bits = 1

• Flow control = Xon/Xoff

303553-A Rev 00

Preparing the Router for Quick-Start

Click on OK.

Choose Files

Choose the Terminal Keys option for the Function, arrow, and ctrl

Properties > Settings.

keys option.

This enables Windows 95 to use terminal keyboard combinations when running the installation script.

Note:

If you set this function to Windows keys, you will not be able to use keyboard combinations such as [Control]-C when running the installation script.

Click on OK.

Choose File

Connect the cable from the console port of the router to the COM port

Save to save your settings.

you selected in the terminal emulation program.

See the installation guide that came with your router for the specific cable requirements for your router.

Turn on the router to complete the internal diagnostics and startup.

When the router boots, the screen displays the Technician Interface

prompt. You are now ready to enter Technician Interface commands (see

“

Logging On to the Technician Interface on page 2-5).

Connecting a Terminal Console

To connect a terminal console (terminal) to the router:

Set the operating parameters of the terminal console as follows:

• Baud rate = 9600

• Stop bits = 1

• Parity = none

• Data bits = 8

303553-A Rev 00

2-3

Quick-Starting Routers

Connect the cable from the terminal console to the console port of the router.

See the installation guide that came with your router for the specific cable requirements for your router. For example, for the Backbone Concentrator Node (BCN console port of the System Resource Module-Link (SRM-L) in slot 7.

Turn on the router to complete the internal diagnostics and startup.

), you insert the male end of the cable (Order No. 7525) into the

When the router boots, the screen displays the Technician Interface prompt. You are now ready to enter Technician Interface commands (see

“

Logging On to the Technician Interface on page 2-5).

Connecting to the IP Ne twork

When you obtained your router, you also received a cable to connect the router to your IP network.

To connect the cable from the router to the IP network:

Connect the cable to a router connector.

Table 2-1

router to the IP network.

Table 2-1. Initial Router Connectors to the IP Network

Bay Networks Router Default Connector

ASN Any connector on any net modu le, excluding the

BayStack AN, ANH, and ARN See the installation guide. BLN, BCN First connector on the first link module (slot 2) System 5000

lists the standard connectors (also called ports) for connecting the

™

net modules See the ins tallation guide.

Stack Packet Exchange (SPEX

™

) module

2-4

You can configure any connector on a router for the initial IP connection by specifying the slot and connector when you quick-start the router with the installation script (Chapter 4)

or the BCC (Chapter 5).

303553-A Rev 00

For information about the location of the connector on your router, see the installation guide that came with your router.

Connect the cable to the network connector.

The network connection depends on your LAN or WAN configuration. For general information about cables, see the Cable Guide.

Logging On to the Technician Interface

When you connect to a Bay Networks router and establish a terminal session, the Technician Interface command-line interface provided with every Bay Networks router.

You use the Technician Interface to:

• View the router’s file system.

• Run the Quick-Start installation script.

• Access the BCC.

Preparing the Router for Quick-Start

• Enter commands to manage your router and its MIB variables. To log on to the Technician Interface, enter:

Manager

The Technician Interface displays a prompt consisting of the slot where the Technician Interface is running, followed by the

prompt, for example:

To log off the Technician Interface, enter:

logout

303553-A Rev 00

2-5

Quick-Starting Routers

Using Technician Interface Commands

To complete the Quick-Start procedure, you must enter several Technician Interface commands. Table 2-2 commands you will need. You can also use the Help system to view available commands.

Technician Interface commands, passwords, and file names are case-sensitive. You must press the Return key to execute a Technician Interface command.

To display all Technician Interface commands in a brief table, enter:

help help

To display all Technician Interface commands and their associated syntax requiremen ts, enter:

help

Use this command when you know the command’s function, but do not know the command name or its syntax. Enter the scrolling.

provides a list of the basic Technician Interface

more on

more off

partition ping -ip

save

tftp type

<IP_address>

Changes the active volume Reallocates file space o n a memory card Copies a file fro m one v ol ume to anot her or to the same

volume Deletes a file from a volume Displays the vol ume number, status, and space f or each

volume Displays all files on a volume Erases any existing files on a volume and formats the

volume Enables the more mode; pauses the display and

prompts you to continue when a screen fills Disables the more mode; the screen scrolls

automatically withou t prompting you Partitions file system media into two volumes Pings an IP address (for example, 192.

IP network Saves the current software configuration, aliases, or

events to a file Transfers a file to or from the router Displays the contents of a file

xx.xxx.xx

) on an

303553-A Rev 00

2-7

Quick-Starting Routers

Reviewing the Installation Files

Your router stores its files on memory cards. The nonvolatile file system (NVFS) running in the router reads and writes to the memory cards for file storage. After establishing a Technician Interface session, you are ready to display the Quick-Start installation files and verify that they are available.

To display and verify the installation files:

Find the memory card location.

Identify the volume where the router’s memory card (volume) resides by entering:

dinfo

The Technician Interface displays a table showing the memory card’s volume number and memory statistics. The v olume number is equi v alent to the slot on the router. BCN and Backbone Link Node (BLN multiple memory cards---one memory card per slot.

Display the names of the files in the volume by entering:

) routers can contain

2-8

dir

<slot_number>

slot_number

is the slot location of the memory card. Include the colon (:) after

the slot number. For example, enter:

dir 2:

TBLN>

Volume in drive 2: is Directory of 2:

File Name Size Date Day Time

--------------------------------------------------------bn.exe 3513155 01/10/98 Mon. 10:03:45 config 132 01/10/98 Mon. 10:03:45 ti.cfg 132 01/10/98 Mon. 10:03:45 install.bat 204323 01/10/98 Mon. 10:03:45 debug.al 12319 01/10/98 Mon. 10:03:45 bcc.help 165960 01/10/98 Mon. 10:03:45

8388608 bytes - Total size 4492587 bytes - Available free space 945812 bytes - Contiguous free space

303553-A Rev 00

Preparing the Router for Quick-Start

Note the available free space on the router volume.

You should always make sure you have enough space on the volume to hold any new files you create or copy.

In the following steps, you verify that the correct router software, configuration, and installation files are available. These steps may not be necessary for new routers with the files already installed, although they will help you become familiar with your router’s files.

Verif y that the directory lists the Quick-Start installation files shown in

Table 2-3

Table 2-3. Quick-Start Installation Files

File Name*

bn.exe

Bootable router software image

config debug.al install.bat ti.cfg bcc.help

* All router files must belong to the same software version. Other files may be in the

directory. Router file names ma y v ary slightly; for e xample, System 5000 net modules use

ti_5000.cfg

the

Verify that all router files belong to the same software version.

file.

File Type

(see Table 2-4 Default configuration file Alias file Quick-Start installation script file Initial configuration file BCC Help file

for other router images)

For example, you should not use a Version 12.00 install.bat script with BayRS Version 13.00 files.

303553-A Rev 00

2-9

Quick-Starting Routers

Verify that the directory holds the correct software image for your router (Table 2-4

Table 2-4. Router Software Images

Router Software Image

AN and ANH* ARN* ASN* BCN BLN System 5000 net modules

* See the Quick-Start restrictions for these routers in the Preface.

Booting with the ti.cfg File

To prepare new routers for initial configuration, you first boot the router with the ti.cfg file. The ti.cfg file is an init ial conf igur ation f ile con taining onl y the mi nimal information needed to boot the router. You then run the installation script or use BCC commands to add configuration information about your first IP interface.

When you complete the Quick-Start procedure, you save your new configuration information to a file called startup.cfg. Do not edit the ti.cfg file or overwrite it with another configuration file.

If the installation fails, you must reboot the router with ti .cfg before retrying th e Quick-Start procedure. You also should boot with the ti.cfg file if:

an.exe arn.exe asn.exe bn.exe bn.exe s5000.exe

2-10

• The router is currently booted from a configuration file other than ti.cfg and

you want to reconfigure the router from scratch.

• You change the initial IP connector (port) that you use to communicate with

the configuration workstation.

303553-A Rev 00

Preparing the Router for Quick-Start

To boot the router using the ti.cfg file:

Enter the following command:

boot

<slot_number>:<image_file> <slot_number>

:ti.cfg

slot_number image_file

identifies the slot where the files reside on the router and

is the software image for your router (see Table 2-4).

For example, enter:

boot 2:bn.exe 2:ti.cfg

The router boots and executes its startup procedure.

Establish a new Technician Interface session by entering:

Manager

In Chapter 3, “Preparing Your Network Information,” you will collect and record the network i nformation needed to complete the Quick-Star t procedure.

303553-A Rev 00

2-11

Chapter 3

Preparing Your Network Information

This chapter provides a series of worksheets to help you collect the information you will need to quick-start the router using either the installation script or BCC commands. This chapter provides the following information:

Topic Page

Using the Quick-Start Worksheet 3-2 Using the Quick-Start ATM Worksheet 3-7 Using the Quick-Start Worksheet for WAN Protocols 3-12

303553-A Rev 00

Whether you use the installation script or BCC commands, you quick-start the router as follows:

Select an interface and supply information about its connector and circuit.

Configure IP on the interface.

Enable these global communication services (optional):

•SNMP

• TFTP

• FTP

•Telnet

• HTTP Server

Save the configuration file as startup.cfg.

Test the initial configuration by pinging the workstation you will use to continue the configuration.

3-1

Quick-Starting Routers

Many BCC commands and installation script prompts provide default values. Accept the defa ult v alue s unless you ha v e a rea son to mak e a c hange. You can skip optional steps and steps that do not apply to your network.

Using the Quick-Start Worksheet

The Quick-Start Worksheet (Table 3-1) provides a summary of the information you need to complete the Quick-Start procedure. The information can be applied to either the installation script or BCC commands.

Most customers configure the ir initial IP in terface on Ethernet. The Quick-Start Worksheet assumes an Ethernet interface in the connector and circuit fields. For interfaces other than Ethernet, substitute the appropriate connector and circuit information and complete the rest of the worksheet beginning with the IP Configuration sec ti on.

For other interfaces, see the appropriate configuration guide for more information about connector and circuit requirements:

• Configuring Ethernet, FDDI, and Token Ring Services

• Configuring WAN Line Services

3-2

If you plan to use the Quick-Start procedure to configure an ATM interface, go to “Using the Quick-Start ATM Worksheet Quick-Start procedure to configure an interface (such as synchronous) that supports a WAN protocol, see “Using the Quick-Start Worksheet for WAN

Protocols” on page 3-12. Figure 3-1

Quick-Star t Worksheet. See Appendix A, “ example of the script execution.

shows a sample Ethernet network used in the examples in the

” on page 3-7. If you plan to use the

Sample Installation Script,” for an

303553-A Rev 00

Preparing Your Network Information

Connect a PC or terminal console locally to the router to access the T echnician Interface and run the installation

install.bat,

script, or the BCC.

Bay Networks router

Connect to the console port in slot 1 of a BLN or ASN or in slot 7 of a BCN.

Corporate IP network

The workstation on the network where you will manage the router remotely, using Site Manager, the BCC, or another configuration tool

Connect the router to the IP network with a QENET link module in slot 2 using XCVR1 (Ethernet connector 1)

IP address = 192.168.125.34 Subnet mask = 255.255.255.0

303553-A Rev 00

IP address = 192.32.20.12

QS0005C

Figure 3-1. Network Example for the Quick-Start Worksheet

3-3

Quick-Starting Routers

Table 3-1. Quick-Start Worksheet

Network Information Example Your Information Physical Connector Information

Number of the slot holding the link module for the first network interface

For the ASN, also provide the module number (for

Note:

example, module 1). Number of the connector (port) on the link module Ethernet connector 1

Circuit Infor mation

Circuit name (default is provided )

Substitu te circuit information for in terfaces other

Note:

than Ethernet.

IP Configuration

IP address of this initial interface (Advanced user s onl y: interfaces.)

Subnet mask of this initial interface 255.255.255.0 If this interface resides on the same local ar ea network

(LAN) as the workstation you will use t o connect to the router, you have completed the initial IP configuration. Proceed to add global services.

If the workstation resides on a different network, add an IP routing protocol first.

install.bat

supports unnumbered

Slot 2 (QE/NF link module)

(XCVR1)

E21

192.168.125.34

IP Routing Protocol Information

Choose an IP routing protocol if the configuration workstation is located on another network:

•RIP

• OSPF

• Static Route See the following sections for details on the IP routing

protocol you choose to configure.

3-4

RIP

(continued)

303553-A Rev 00

Preparing Your Network Information

Table 3-1. Quick-Start Worksheet

Network Information Example Your Information RIP Configuration

Should RIP listen to the default route to the network or subnet where the workstation is located?

OSPF Configuration

OSPF router IP address (if different from this interface) 192.32.156.7 OSPF area address 0.0.0.0 Should you enable Simple Password Authentication? No MTU size for OSPF packets (Default, Ethernet Size,

User-defined MTU) OSPF interface type

(Broadcast, NBMA, Point to Point, Point to MultiPoint)

If there is an existing OSPF configuration on the

Note:

network, you must set matching values for the interface type, Hello Interval, and Dead Interval.

Hello interval (in seconds) 10 (default) Router dead interval (in seconds) 40 (default) Router priority 1 (default) Poll interval 120 (default) If you are configuring OSPF neighbors, add the IP

address for each neighbor.

Neighbors are defined only if the OSP F interface

Note:

type is NBMA. Sample format: 192.32.156.8

(continued)

Yes

Default

Broadcast (default)

Static Route Configuration

Destination network 192.32.90.1 Destination network mask 255.255.255.0 Next-hop ad dress that i s in the sam e subnet a s the initi al

IP interface

303553-A Rev 00

192.32.4.99

(continued)

3-5

Quick-Starting Routers

Table 3-1. Quick-Start Worksheet

Network Information Example Your Information Global Services Information

These steps set communication services globally for all the interfaces on the router. You can increase router security by restricting SNMP communities, FTP, and Telnet. See Chapter 7, “

Enable SNMP Community Management? Yes For each SN MP commun ity, decide whether it is p ublic or

private, its read-write access, and IP address of the manager.

Enable TFTP? Yes Default volume where TFTP transactions will take place 2 Enable FTP? Yes Default volume where FTP transactions will take place 2 Enable Telnet? Yes Enable Telnet client? Yes Enable Telnet server? Yes Enable the HTTP (Web) server? Provides embedded Web tools on the router to view

device information.

(continued)

Securing the Router.”

public, read-only,

192.32.20.12

Yes

Workstation Information

IP address of the workstation you will use to configure the router

3-6

192.32.20.12

303553-A Rev 00

Using the Quick-Start ATM Worksheet

The Quick-Start installation scri pt allows you to configure initia l routing services for the ATM Routing Engine link module in Bay Networks routers. You can then use Site Manager to refine your configuration.

Use the Quick-Start installation script to add ATM to the router by:

• Defining the physical link

• Defining an ATM service record

• Creating an ATM circuit

• Adding the initial virtual circuit to the service record (PVCs only)

• Enabling the IP protocol on the ATM service record The Quick-Start ATM Worksheet (Table 3-2) contains only the ATM connector,

circuit, and service record information. After you specify the ATM interface, the Quick-Start script prompts you for the same information found in Table 3-1 beginning with the IP Configuration section.

Preparing Your Network Information

303553-A Rev 00

Figure 3-2

shows a sample ATM network used in the examples in the ATM

Quick-Star t Worksheet. See Appendix B, “

Sample ATM Installation Script,” for an exampl e of the script

execution. For more information about the parameters set in the script, see Configuring ATM

Services.

3-7

Quick-Starting Routers

Connect a PC or ASCll console locally to the router to access the T echnician Interface and run the installation script,

The console port connector is in slot 1 of a BLN or ASN or in slot 7 of a BCN.

Local Bay Networks router connects to an ATM network from the ATM Routing Engine link module in slot 2 using an ATMC-OC3MM connector. You configure a service record type using the script and then run IP over the connection. IP address = 192.168.125.34 Subnet mask = 255.255.255.0

install.bat.

Remote Bay Networks edge device (for example, a router or switch) on the ATM network with a connection to the IP network containing the workstation that you will use to manage the router you are configuring.

ATM network

Corporate IP network

Workstation where you will manage the router remotely, using Site Manager or another configuration tool. IP address = 192.32.10.12

Figure 3-2. Network Example for the Quick-Start ATM Worksheet

3-8

QS0016A

303553-A Rev 00

Preparing Your Network Information

Table 3-2. Quick-Start ATM Worksheet

Network Information Example Your Information ATM Physical Link Information

Slot number of the link module 4 (ATMC_OC3MM) Connector number [1]: 1 (ATM1)

Choosing a Service Record Type

Enter ATM Service Record Type [1]:

1. ATM PVC

2. ATM LAN Emulation

3. ATM Logical IP Subnet Continue with the information for your service record

type.

PVC Service Record Type

Enter encapsulation type [1]:

1. LLC/SNAP (RFC 1483)

2. NLPID (RFC 1490) For VPI, enter a number from 0 to 255.

The VPI (virtual path identifier) number o f the initial PVC identifies the virtual path of the PVC. The VPI is part of the cell header. The header can contain a maximu m of 8 VPI bits. This bit range allows for path identifiers from 0 through 255.

For VCI, enter a valid number in these ranges:

- ARE module in a BLN/BCN router: 32 - 65535

- Model 5780 ATM VNR in a Model 5000AH chassis:

130 - 2047

- Model 5782 ATM VNR in a Model 5000BH chassis:

130 - 2047 The VCI (virtual channel identifier) number of the initial PVC identifies the virtual channel portion of the PVC. The VCI is part of the cell header and has a length of 16 bits.

1 (ATM PVC)

2 (NLPID (RFC 1490))

200

(continued)

303553-A Rev 00

3-9

Quick-Starting Routers

Table 3-2. Quick-Start ATM Worksheet

Network Information Example Your Information

Enter circuit name: (The script recommends a default name.)

LAN Emulation Service Record Type

Signaling Version [1]:

1. UNI3.0

2. UNI3.1 Do you want A u to Gene ratio n of the ATM address? (y/n)

[y]: If you choose A uto Gener ation, rou ter software will use a

combination of the MAC address and the network prefix obtained from the server to generate a unique ATM address.

If you do not choose Auto Generation, enter a 7-byte User Part (Mandatory) and a 13-byte Net Prefix (Optional) to be combined into a 20-byte ATM address.

Enter User Part (Mandatory), 7 bytes: Enter Net Prefix (Optional), 13 bytes:

Choose the Emulated LAN Name.

(continued)

ATMSR_1404101.3

2 (UNI3.1)

12345677654321 3900000000000000000 0000000

AAA

Press Return to accept the default ELAN name or type the name of a previously configured ELAN for this LAN Emulation client to join.

Choose Emulated LAN Type [1]

1. Unspecified

2. IEEE8023

3. IEEE8025

Enter circuit name. (The script recommends a default name.)

3-10

3 (IEEE8025)

ATMSR_1404101.5

(continued)

303553-A Rev 00

Preparing Your Network Information

Table 3-2. Quick-Start ATM Worksheet

Network Information Example Your Information Logical IP Service Record Type

Signaling Version [1]:

1. UNI3.0

2. UNI3.1 Do you want A u to Gene ratio n of the ATM address? (y/n)

[y]: If you choose A uto Gener ation, rou ter software will use a combination of the MAC address and the network prefix obtained from the server to generate a unique ATM address.

If you do not choose Auto Generation, enter a 7-byte User Part (Mandatory) and a 13-byte Net Prefix (Optional) to be combined into a 20-byte ATM address.

Enter User Part (Mandatory), 7 bytes: Enter Net Prefix (Optional), 13 bytes:

Choose the ATM ARP Mode.

-Client Mode [Default]

-Server Mode

(continued)

1 (UNI3.0)

12345677654321 3900000000000000000 0000000

If you choose the default (Client Mode), you must enter the ARP Server ATM Address.

Would you like to accept Client Mode for ATM ARP? (y/n) [y]:

Enter ARP Server ATM Address in hexadecimal format, omitting leading 0x/0X.

Enter Network Prefix (Mandatory), 13 bytes: Enter User Part (Mandatory), 7 bytes:

Refer to Table 3-1

303553-A Rev 00

, the Quick-Start Worksheet, to continue the initial configuration.

Yes

3900000000000000000 0000000 11111111111111

3-11

Quick-Starting Routers

Using the Quick -S tart Worksheet fo r WAN Protoc o ls

Use the Quick-Start Worksheet for WAN Protocols (Table 3-3) to record the information you will need to enable frame relay, PPP, or SMDS using the installation scr ipt. (Us ing the scr ipt to ena bl e WAN protocols is recommended for experienced users only.) Normally you implement these protocols using Site Manager or another configuration tool. The script prompts for a WAN protocol if you select a connector that supports WAN protocols, for example, synchronous.

For more information about the WAN protocol parameters, see these guides:

• Configuring Frame Relay Services

• Configuring PPP Services

• Configuring SMDS

Table 3-3. Quick-Start Worksheet for WAN Protocols

Network Information Example Your Information WAN Information

Advanced users can use the Quick-Start script to initially configure frame relay, PPP, or SMDS. See the configuration guides for more information about the parameters.

Frame Relay Information

(To enable frame relay on a synchronous connector on this initial IP interface) Enable frame relay on the interface? Yes

Management protocol that communicates with the frame relay network

DLCI addressing types ADDR Q.922 Frame relay address field length 2 bytes Frame relay PVC ID 30

3-12

LMI

(continued)

303553-A Rev 00

Preparing Your Network Information

Table 3-3. Quick-Start Worksheet for WAN Protocols

Network Information Example Your Information PPP Information

(To enable PPP on a synchronous connector on this initial IP interface) Enable PPP on the interface? Yes

IP address of peer connection 192.32.4.2 Enable PPP Echo protocol? Yes Number of seconds between transmission of echo

requests Acceptable loss of Echo -Repl y packets 3 Enable local authentication protocol? Yes Local PAP ID for this interface 192.32.4.1 Local PAP password (optional) lpwd Authentication protocol enabled on remote peer? Yes Remote peer PAP password rpwd Enable Link Quality Reporting (LQR) protocol? Yes Enable use of remote peer’s LQR timer? Yes Minimum acceptable percentage of inbound packets 90 Minimum acceptable percentage of outbound packets 90

(continued)

SMDS Information

(To enable SMDS on a synchronous connector on this initial IP interface) Enable SMDS on the interface? Yes

Individual address C1617555433FFFF Group address E16175556667FFFF ARP address E16175550000FFFF

303553-A Rev 00

3-13

Chapter 4

Using the Installation Script

to Quick-Start a Router

The install.bat script establishes an initial IP network interface on the router so that your router can communicate with the workstation from which you will manage the router.

The script prompts you to enter the network information that dynamically configures the init ial IP interf ace. (Se e Appe ndix A You configure subsequent interfaces with Site Manager, the BCC, or another router configuration tool.

for a sample script e x ecuti on.)

303553-A Rev 00

Note:

You can use either the BCC or the in stall.bat scri pt to est ablish an initial IP interface. For information about using the BCC, see Chapter 5, “

BCC to Quick-Start a Router.”

Following are important points to remember about running the script:

• You must boot the router with the ti.cfg file before running the script.

• Do not overwrite the ti.cfg file.

• Save your initial configuration file as startup.cfg.

• After the script completes successfully, do not reboot your router.

• If the script fails, see “

• If you must rerun the script, first reboot the router with the ti.cfg file.

• Immediately after running the script, secure your router. For more

information, see Chapter 7, “

Quick-Start Tr oubleshooting” on page 4-4.

Securing the Router.”

Using the

4-1

Quick-Starting Routers

Before you start the script, review Table 4-1 for the commands you use to run the script.

Table 4-1. Installation Script Commands

Script Action Your Input Result

Accept the default value. Press [Return]. Accept the default value that the script displays in

Repeat a step to make a correction.

Exit the Quick-Start installation script.

brackets, for example,

Press [Control]-C. The script displays this prompt:

Terminate script y/n?

Enter you can reenter the information.

Press [Control]-C. The script displays this prompt:

Terminate script y/n?

Enter y to terminate the script and return to the Technician Interface prompt. Before rerunning the Quick-Start installation sc ript, reboot the route r using the

to return to the beginning of the step so that

ti.cfg

file.

[E21]

After booting the router with the ti.cfg file and establishing a new Technician Interface session, you are ready to run the install.bat installation script.

4-2

To run the script:

Access the volume where the installation files reside by entering:

<volume_number>

Include the colon (:) after the volume number. For example, enter

Start the installation script by enterin g:

run install

cd 2:

Many steps in the installation s cr ipt provide def aul t values you s hould accept. Some steps are optional for your network requirements.

Refer to your Quick-Sta rt worksheet (see Chapter 3

) as you respond to the

prompts.

Select a slot and connector on the router.

Configure IP on the interface.

303553-A Rev 00

Using the Installation Script to Quick-Start a Router

Enable global servic es for:

•SNMP

• TFTP

• FTP

•Telnet

• HTTP Server

Note: You can enable the HTTP Serv er on the ro ute r to acce ss embed ded Web

tools to view device information. For more information, see Managing Your Network Using the HTTP Server.

Review the configuration.

The script displays a summary of the newly configured IP interface.

Save the configuration file as

startup.cfg.

Accept the default name, startup.cfg. You save this initial IP configuration to the file to maintain a permanent copy for the next time you reboot the router.

Do not save your configuration file as ti.cfg. That file should remain in its original, unconfi gur ed state.

Do not save your file as config. Use that file name only after you have fully tested a configuration file. The router uses config as the default boot file and will automatically boot with it if another fi le is not specified.

Test the initial IP interface.

The router tests the IP interface configuration by pinging its own interface. If successful, it prompts you for t he IP address o f the w orkst ation you will use to configure the router and attempts to ping it.

If the ping test is not suc cessful, the ca use may be netw ork prob lems that ha v e nothing to do with the Quick-Start installation. To troubleshoot the network problems, you can leave the ping test by typing Q. See “

Quick-Start

Troubleshooting” on page 4-4 for more information.

If the ping test is successful, the initial IP interface is enabled and the script displays this message:

Quick-Start Installation Completed

303553-A Rev 00

The Technician Interface prompt appears.

4-3

Quick-Starting Routers

You now have a configuration file named startup.cfg on the router volume that contains your initial interface. The configuration is active in the router’s memory.

Caution:

Do not reboot the router after succ essfully completing the Quick-Start procedure. By default, the router reboots with the file named config, not the startup. cfg fi le you just c reated. See Chapter 6, “

Router Configuration,” for instructions on testing the startup.cfg file before

you save it as config.

Bay Networks recommends that you immediately secure your router to prevent unauthorized access. See Chapter 7, “

Quick-Start T roubleshooting

If the router cannot ping the workstation during the Quick-Start procedure, check the following:

• If the router was able to ping its own interface, and the script prompted you

for the interface of the workstation, you probably have a successful installation. To be sure, continue with the remaining checks.

• Check the physical connections.

• If the workstation is a PC, a supported TCP/IP stack must be running for a

successful ping. See Chapter 8, “ information about TCP/IP stacks, adapters, and drivers.

Completing the

Securing the Router,” for information.

Installing Site Manager on a PC,” for

4-4

• Verify the IP address of the router. Enter the

show ip ci r cuit s

command at the Technician In ter face prompt to ma k e sure that the ph ysi cal interface is u p and that the IP address is correct. For more information about the

show

command,

see Using Technician Interface Scripts.

• Verify the IP address and subnet mask address of the configuration workstation.

303553-A Rev 00

Using the Installation Script to Quick-Start a Router

• If the workstation is on a di fferent network, verify that routing is ac tive. Enter the

show ip routes command at the Technician Interface prompt to examine

the routing table and verify that there is a route or a default route to the network where the workstation is located. For more information about the

show command, see Using Technician Interface Scripts.

Note:

If the installation failed and you must rerun the script, first reboot the

router with th e ti.cfg file.

303553-A Rev 00

4-5

Chapter 5

Using the BCC to Quick-Start a Router

The Bay Command Console (BCC) is a command-line interface to your Bay Networks router. You can configure and manage your routers using BCC commands. This chapter tells you how to use the BCC to quick-start a router and produce an initial configuration file called startup.cfg. Refer to the following topics:

Topic Page

Overview of the BCC 5-2 Essential BCC Commands 5-4 Quick-Starting Your Router with the BCC 5-5 Quick-Start Troubleshooting with the BCC 5-13

303553-A Rev 00

Note:

You can use either the install.bat script or the BCC to establis h an init ial IP interface. For information about using the script, see Chapter 4, “

Installation Script to Quick-Start a Router.”

See “

Using the Quick-Start Worksheet on page 3-2 to collect the ne twork

information you will need to quick-start the router with BCC commands. Immediately after quick-starting with the BCC, secure your router.

For information, see Chapter 7, “ This chapter provides only the information needed to create an initial interface.

You can continue the configuration with the BCC or another configuration tool, such as Site Manager.

Securing the Router.”

Using the

5-1

Quick-Starting Routers

Overview of the BCC

You access the BCC by ente ring

bcc

at the Technician Interface p rompt. The bcc > prompt appears, from which you can run any BCC or Technician Interface command. You enter configuration mode by entering

config

The BCC views the router as a hierarchy of objects and parameters you can configure either globally for the whole router or individually for each interface. The BCC always display s a prompt that i ndicates your cur rent worki ng context (or location) within the hierarchy.

You start from the root level (at the box# or stack# prompt) and define each interface and its protocols. To quick-start a router, you configure one Ethernet interface, add the IP protocol, and add a routing protocol if the workstation is located on a different LAN than the router (Figure 5-1

). Next, you add some global services that apply uniformly to all slots of a router: SNMP, FTP, TFTP, Telnet, and the HTTP Server.

For more information about the BCC, see:

• Using the Bay Command Console (BCC)

• BCC Quick Reference

• Release Notes

5-2

303553-A Rev 00

Using the BCC to Quick-Start a Router

box

box# ethernet/2/1

ethernet/2/1

ethernet/2/1# ip address 192.168.125.34 mask 255.255.255.0

(address 192.168.125.34 mask 255.255.255.0)

ip/192.168.125.34/255.255.255.0# rip

RIP

rip/192.168.125.34#

BCC0017B

Figure 5-1. Configuring IP and RIP on an Ethernet Interface

303553-A Rev 00

5-3

Quick-Starting Routers

Essential BCC Commands

Table 5-1 lists the essential BCC commands you need to use BCC Help, change

your location, view what you can configure, and review what you added.

Table 5-1. Essential BCC System and Navigation Commands

Category BCC Command Task

System Help

Configuration mode Help

Navigation

Configuration mode

Configuration status

help ?

help tree [-all] info

lso back

pwc

box or stack config

show config -all

List the system commands you can enter. List BCC Help features.

List the names of all objects, param et ers, and commands at this level.

Show the configuration syntax and list the parameters of an object you can configure from the current level.

Display values for this pa rameter of the current object. Show the BCC co nfiguration structure.

List values assigned to parameters of this object. Show objects configured at the next (branch) level.

Go back one level. Show full context, starting from root level. Return to the top level of router configuration.

Enter configuration mode.

Show the total device configuration in BCC syntax.

Other commands

5-4

[Control]+p [Control]+n

exit

Recall pre vious or ne x t comm and from the comm and his tory list.

Exit configuration mode; enter Technician Interface prompt.

again to return to the

exit

303553-A Rev 00

Using the BCC to Quick-Start a Router

Quick-Starting Your Router with the BCC

The following procedure provides a sequence of commands you can use to quick-start your BN or AN router on an Ethernet network. Before beginning this procedure you need to:

• Learn the basic BCC commands listed in Table 5-1

• Complete the steps in Chapter 2, “

Preparing the Router for Quick-Start,”

including booting the router with the ti.cfg file.

• For BayStack routers, review the local boot procedure and slot and connector

information in Configuring BayStack Remote Access. By default, the BayStack router is configured to boot over the network. To quick-start a BayStack router with the BCC, you must first change the default boot to loc al mode with the

bconfig config local

command.

To quick-start your router:

Log on to the Technician Interface as Manager.

Mounting new volume... Device label: Directory: 2: New Present Working Directory: 2:

Start the BCC interface by entering

Manager

Welcome to the Backbone Technician Interface

bcc

303553-A Rev 00

[2:1]$

Welcome to Bay Command Console!

* To enter configuration mode, type config

* To list all system commands, type ?

* To exit the BCC, type exit

bcc>

bcc

5-5

Quick-Starting Routers

Start BCC configuration mode by entering

bcc> config box#

Check the hardware configuration of the router.

box# show config box type freln (BLN router with a FRE controller)

board slot 1

type srml back

board slot 2

type qenf (Quad Ethernet link module in slot 2) back

board slot 3

type wffddi2m (Multimode FDDI link module in slot 3) back

board slot 4

type sync (Synchronous link module in slot 4)

back board slot 5

type dtok (Dual token ring link module in slot 5) back

back console portnum 1 (Console connected to port 1) prompt {[%slot%:1]$ } auto-manager-script automgr.bat auto-user-script autouser.bat back

back

(System Resource Module in slot 1)

config

at the

bcc>

prompt.

5-6

Configure a port on the router for the initial interface by adding an interface type of Ether net on a slot wi th an appr opriate board and adding its first connector.

box# ethernet slot

connector

Use the slot and connector number for your router. For example, enter:

box# ethernet slot 2 connector 1

303553-A Rev 00

Using the BCC to Quick-Start a Router

Add IP to this port by entering its IP address and subnet mask.

ethernet/2/1# ip address

<ip_address>

mask

<mask_value>

For example, enter:

ethernet/2/1# ip address 192.168.125.34 mask 255.255.255.0 ip/192.168.125.34/255.255.255.0#

The BCC automatically enables ARP on this interf ac e and adds IP gl oball y to this router.

If your workstation is on the same LAN as the router, go to step 10

. If your workstation is not on the same LAN as the router, add one of the following routing protocols:

•RIP

• OSPF

• Static Route

To add RIP as the routing protocol for this IP port, enter:

ip/192.168.125.34/255.255.255.0# rip

Go to step 10.

To add OSPF as the routing protocol for this IP port:

Add an OSPF area.

303553-A Rev 00

ip/192.168.125.34/255.255.255.0# ospf area

For example, enter:

ip/192.168.125.34/255.255.255.0# ospf area 0.0.0.0 ospf/192.168.125.34#

View the default values assigned to this OSPF area.

ospf/192.168.125.34# info

on ip/192.168.125.34/255.255.255.0 state enabled area 0.0.0.0 authentication {} type broadcast priority 1 transit-delay 1 retransmission-interval 5 hello-interval 10 dead-interval 40 poll-interval 120

5-7

Quick-Starting Routers

metric 1 mtu 1

The type, hello-interval, and dead-interval parameters must match those of your network. To change these default values, you first need to learn more about the BCC before proce eding. Refer to Table 5-1

on page 5-4 to learn about the Help and navigation commands. Use the parameter Help command (example:

type ?) to view the values you can assign and any

further parameters you need to configure. See Using the Bay Command Console (BCC) for more information.

If the OSPF router ID is the same as the IP address of the first route r port, go to step 10

If the OSPF router ID is different from the IP address of this first router port, return to root (box) level to change the OSPF router ID as a global parameter.

ospf/192.168.125.34# box box#

Move to global IP by entering:

box# ip ip#

5-8

Move to global OSPF by entering:

box# ospf ip/ospf#

Change the OSPF router ID by entering:

ip/ospf# router-id

<ip_address>

For example, enter:

ip/ospf# router-id 192.168.125.10

Go to step 10.

To add a static route to this IP port:

Return to the root (box) level to con figure the static route globally.

ip/192.168.125.34/255.255.255.10# box

Move to global IP by entering:

box# ip

303553-A Rev 00

Using the BCC to Quick-Start a Router

Add a static route and the next hop by entering:

ip# static-route address

next-hop-address

<ip_address>

mask

<mask_value>

For example, enter:

ip# static-route address 192.168.124.10

mask 255.255.255.0 next-hop-address 192.168.125.35

static-route/192.168.124.10/255.255.255.0/192.168.125.35#

10.

Return to root (box) level to configure global system services that affect all slots, such as SNMP, FTP, Telnet, TFTP, and the HTTP Server.

current_level

11.

Add SNMP globally to the router by entering:

box# snmp snmp#

12.

Specify an SNMP community name, fo r example, “public.”

snmp# community public community/public#

13.

Define the access level you want for the port for router security.

># box

By default, access is read-only. If you want access to be read-write, enter:

community/public# access read-write

14.

Define the workstation that will be the SNMP manage r for t he router by entering:

303553-A Rev 00

community/public# manager

ip_address

is the address of the workstation that will be the SNMP manager.

<ip_address>

(An address of 0.0.0.0 allows any workstation to be the manager.) For example, enter:

community/public# manager 192.32.20.12 manager/public/192.32.20.12#

15.

Return to root (box) level.

manager/public/192.32.20.12# box

16.

Configure Telnet from the root level by entering:

box# telnet

5-9

Quick-Starting Routers

17.

Add the Telnet client.

telnet# client client#

18.

Go back one level by enterin g:

client# back telnet#

19.

Add the Telnet server.

telnet# server

20.

Return to root (box) level.

telnet# box

21.

Add TFTP to the router from the root level.

box# tftp

22.

Return to root (box) level.

tftp# box

23.

Add FTP to the router from the root level.

box#

ftp

5-10

24.

Return to root (box) level.

ftp# box

25.

Add the HTTP S erver to the router from the root level.

box# http

26.

Return to root (box) level.

http# box

27.

Save your initial configuration file to the router’s volume as

box# save config

:startup.cfg

For example, enter:

box# save config 2:startup.cfg

Save the configuration as a file other than config until you can test the configuration file.

startup.cfg

303553-A Rev 00

Using the BCC to Quick-Start a Router

28.

Test the initial IP interface by pinging the router’s own interface.

box# ping

<ip_address>

For example, enter:

box# ping 192.168.125.34

29.

Test the initial IP interface by pinging the workstation where you use the BCC or other configuration tool.

box# ping

<ip_address>

For example, enter:

box# ping 192.32.20.12

If either ping is unsuccessful, see “Quick-Start Troubleshooting with the

BCC” on page 5-13.

30.

Review your initial router configuration by entering:

box# show config -all

This command shows the total device configuration in terms of BCC syntax (commands and data), and returns you to the current context.

For example, enter:

box# show config -all box type freln

board slot 1

type srml back board slot 2 type qenf back board slot 3 type wffddi2m back board slot 4 type sync back board slot 5 type dtok back ethernet slot 2 connector 1 circuit-name E21

303553-A Rev 00

5-11

Quick-Starting Routers

ip address 192.168.125.34 mask 255.255.255.0 arp back rip back back back ip tcp back arp back rip back back ftp default-volume 2 back snmp community label public access read-write manager address 192.32.20.12 back back back tftp default-volume 2 back console portnum 1 prompt {[%slot%:1]$ } auto-manager-script automgr.bat auto-user-script autouser.bat back telnet client back server back back back box#

5-12

31.

Exit BCC configuration mode by entering the prompt.

box# exit bcc>

exit

command at any

303553-A Rev 00

Using the BCC to Quick-Start a Router

32.

When you finish using the BCC, enter the

exit

prompt.

bcc> exit [2:1]$

Exiting the BCC returns you to the Technician Interface prompt. You now have a configuration file named startup.cfg on the router volume that

contains your initial interface. The configuration is active in the router’s memory.

Caution:

Router Configuration,” for instructions on testing the startup.cfg file before

you save it as config.

Bay Networks recommends that you immediately secure your router to prevent unauthorized access. See Chapter 7, “

Securing the Router,” for information.

Quick-Start Troubleshootin g with the BCC

If the router cannot ping the workstation during the Quick-Start procedure, check the following:

command at the

Completing the

bcc>

303553-A Rev 00

• The network could be slow or disabled, or the ping test timed out. Continue

checking the other items.

• Check the physical connections.

• If the workstation is a PC, a supported TCP/IP stack must be running for a

successful ping. See Chapter 8, “

Installing Site Manager on a PC,” for

information about TCP/IP stacks, adapters, and drivers.

• Verify the IP address of the router. Enter the

show ip ci r cuit s command at the

Technician In ter face prompt to ma k e sure that the ph ysi cal interface is u p and that the IP address is correct. For more information about the

show command,

see Using Technician Interface Scripts.

• Verify the IP address and subnet mask address of the configuration

workstation.

5-13

Quick-Starting Routers

• If the workstation is on a di fferent network, verify that routing is ac tive. Enter

the the routing table and verify that there is a route or a default route to the network where the workstation is located. For more information about the

show command, see Using Technician Interface Scripts.

Note:

router with th e ti.cfg file.

show ip routes command at the Technician Interface prompt to examine

If the installation failed and you must rerun the script, first reboot the

5-14

303553-A Rev 00

Chapter 6

Completing the Router Configuration

This chapter provides an overview of the tools and procedures you can use to complete the router’s configuration. Refer to the following topics:

Topic Page

Selecting a Configuration Tool 6-1 Completing the Configuration Procedure 6-2 Communicating with the Router Remotely 6-3

Selecting a Configuration Tool

Bay Networks provides the following tools for configuring your router. See the Release Notes for information about the platforms, interfaces, and protocols that each tool supports.

• The BCC

The BCC is a command-line interface for configuration. You can enhance your Quick-Start conf igur ation wit h the BCC for the support ed inter fa ces and protocols. Configuration files created with the BCC can be modified with other tools, but first make sure that you save the BCC configuration as a binary file.

For more information, see Using the Bay Command Console (BCC).

•Site Manager

Site Manager is a graphical user interface for configuration. If you need to install Site Manager, see the installation chapter for your workstation later in this book (Chapters 8 through 12).

303553-A Rev 00

6-1

Quick-Starting Routers

For information about using Site Manager, see Configuring and Managing Routers with Site Manager.

• NETarchitect

NETarchitect integrates Site Manage r’s Configuration Manager tool with File Manager to help you store, distribute, and boot multiple router files.

For more information, see Configuring and Maintaining Networks with the NETarchitect System in the Optivity

• Technician Interface

The Technician Interface is a command-line interface for managing routers and setting MIB values. (BCC commands are gradually replacing Technician Interface functions.)

For more information, see Using Technician Interface Software.

• HTTP Server

The HTTP Server provides embedded Web tools on the router to view device information. It also pro vides some configuration functions like port dis abling. You enable the HTTP Server on the router from install.bat, Site Manager, or the BCC.

documentation set.

For more information, see M anaging Your Network Using the HTTP Server.

Completing the Configuration Procedure

The Quick-Start procedure creates a configuration file named startup.cfg on the router. The initial configuration is active in the router’s memory.

You use a configuration to ol to add prot ocols and por ts to the init ial conf i guration. After testing the new configuration, you save it as config, the router’s default configuration file.

Note:

Be sure to create and test a new config file as soon as you complete the Quick-Start procedure. By default the router boots with config unless you specify another file. It is important that you always keep a working, tested file named config to ensure that the router operates correctly.

6-2

303553-A Rev 00

Completing the Router Configurat io n

The following outlines the general procedure for modifying the initial configuration with your chosen tool:

Make a backup copy of the

Modify the

Save the modified configuration as a test file, for example,

Boot the router with the test configuration file.

Verify that the router’s new configuration works correctly.

Save the verified configuration file as

startup.cfg

file using the configuration tool.

file by adding interfaces and protocols.

config.

Always save a copy of the current config file before you overwrite it.

Communicating with the Router Remotely

In addition to the network connections you make to the router with tools such as Site Manager, you can also communicate with the router remotely using:

• Telnet connections

• Out-of-band connections

• Memory card distribution

Telnet Connections

test.cfg

You can manage a router from a remote workstation by establishing a Telnet connection and using the router’s Technician Interface and the BCC. See Using Technician Interface Software for information about establishing a Telnet session.

Out-Of-Band Connections

As a backup method of reaching the Technician Interface and the BCC, you can also access the router remotely thr ough t he modem port. This c onnection is called a remote out-of-band connection. Out-of-band refers to the fact that it is not dependent on a network connection, so that you can still communicate with your router even if the ne twork is down.

See Using Technician Interface Software for information about modem connections and your installation guide for information abut connecting modems.

303553-A Rev 00

6-3

Quick-Starting Routers

Router Memory Card Distribution

You can also distribute files to the router on memory cards. Some network managers modify router files at a central location, save them to a memory card, and then distribute the card to a remote of fice. Be sure to rea d the safety warn ing s in the router’s installation guide before changing memory cards.

6-4

303553-A Rev 00

Chapter 7

Securing the Router

Bay Networks recommends that you immediately secure your router to prevent unauthorized access. This chapter provides an overview of the security features and services you can use:

Topic Page

Assigning a Password to the Technician Interface 7-2 Securing New Routers with the BCC or the Installation Script 7-3 Setting Global IP Access Policies with the BCC 7-3 Restricting Read/Write Ac cess with SNMP Communit ies 7-3 Setting Secure Mode 7-4 Authentication Failure Traps 7-6 Assigning SecurID to Telnet Connections 7-6 Turning Off FTP and Telnet on the Router 7-6 Using the Image Builder to Remove Services 7-6 Restricting Access to the HTTP Server 7-7 Configuring Data Encryption Services 7-7 Configuring RADIUS 7-8 Installing BaySecure FireWall-1 7-8

303553-A Rev 00

7-1

Quick-Starting Routers

Assigning a Password to the Technician Interface

The Technician Interface provides local and remote access to your router’s file system. You should immediately add a security password for the administrator of the router’s Technician Interface.

Enter the password command for a manager:

password Manager

The console displays the following message:

Changing password for Manager Old password:

Because there is no old password, press the R eturn key.

New Password:

Enter the new password.

The password can have from 0 to 16 alphanumeric characters.

Reenter your p assword at t he prompt.

Retype new password:

7-2

The console displays the following message:

Manager password changed

See Using Technician Inter fac e Sof t ware for instructions on settin g pas swords for users and additional information.

303553-A Rev 00

Securing the Router

Securing New Routers with the BCC or the Installation Script

Although you can quick-s tart rou ters usi ng either th e BCC or the inst all.bat script, the BCC provides an operational advantage if you have security concerns.

By default, the BCC adds read-only access to the router. You must explicitly configure write access. After you quick-start the router, you can immediately use the BCC to change the global IP access policies and secure the router.

The install.bat script adds read-write access by default. You must then establish a Site Manager (or other configuration tool) session before you can add additional security for IP services.

See “Setting Global IP Access Policies with the BCC” and “Restricting Read/Write Access with SNMP Communities” for additional information.

Setting Global IP Access Policies with the BCC

The BCC allows you to create global IP access policies for routers that control access to specific IP services, including Telnet, FTP, TFTP, NTP, and SNMP.

You define a policy and its actions by setting BCC parameters. See the appendix “Configuring IP Global Access Policies” in Configuring IP Utilities for more information.

Restricting Read/Write Access with SNMP Communities

You can use either Site Manager or the BCC to c ontrol SNMP ac cess to the router. You should restrict read/write access to the router as soon as possible by reconfiguring the SNMP communities.

When you add SNMP with the BCC, access is defined by default as read-only. You should immediately add managers to control any write access you explicitly add.

303553-A Rev 00

7-3

Quick-Starting Routers

By default, the Quick-Start installation script (install.bat) creates a read/write SNMP c ommunity n amed “publi c” with a wildcar d manager ( 0.0.0.0) that allows universal read/write access. Bay Networks strongly recommends that you use Site Manager or BCC commands to:

Reconfigure the “public” community as read-only for universal access.

Create a read/write community with a unique name (for example, EASTBAY) and a manager list containing the IP addresses of the workstations that need read/write access to the router.

See Configuring SNMP, BootP, DHCP, and RARP Services for more information about configuring SNMP. See Using the Bay Command Console (BCC) for information about BCC commands.

Setting Secure Mode

Bay Networks routers have an optional security mechanism, called secure mode, that uses an encryption al gor it hm to pr event unauthorized SNMP SET requests to the MIB variabl es of the router .

In secure mode, when Site Manager issues the first SET request within an application, you must ente r a key to allo w Site Manager to opera te in secure mode. A Site Manager SET request to the router includes the encrypted value of a counter. When the agent on the router receives the SET request, it compares the encrypted value with the value of its own counter plus 1. If the two counters match, the agent considers the SET request authe ntic, incremen ts the counter by 2, stores it in encrypted form in the MIB, and sends it back to Site Manager.

7-4

Secure mode protects against these security violations:

• Message str eam modif icati on, in which an i ntruder reorder s, delays, or re plays

SET requests to specify unauthorized management settings

• Masquerade operations, in which an intru der assumes th e IP address of an

authorized user to specify unauthorized management settings

303553-A Rev 00

Secure mode does not protect against the following security violations, which are beyond the scope of this proprietary interim security system:

• Modification of information, in which an intruder intercepts a packet,

modifies its contents, and reinserts it into the message stream before the agent’s counter increments

• Disclosure, in which an intruder observes which variables are being set Enabling the security mecha ni sm only minimal l y affects router performance. The

security mechanism has no effect on the ability of Site Manager, or of any SNMP network manager, to monitor the router by performing GET, GET-NEXT, or trap functions.

Specifying Secure Mode

To set the router to secure mode:

Set up private, read-write SNMP communities for your router using Site Manager.

You cannot use public communities with secure mode. See

“

Restricting Read/Write Access with SNMP Communities” on page 7-3

for instructions on changing SNMP communities.

Securing the Router

303553-A Rev 00

Using the Technician Interface on the router, enter the following command:

wfsnmpmode 3 3

indicates that the router should operate using the proprietary security

mechanism.

Specify a password key for the encryption algorithm to use when it encrypts the security counters by entering the following command:

wfsnmpkey

key

is the string of ASCII charac ters th at you sele ct to mak e up th e en crypt ion

<key>

code for this router. The key can have up to six characters. The encryption algorithm uses the attributes of the key (size, range, and value) in the encryption process.

T o turn off secure mode and revert to the default SNMP community security mode (called trivial mode), enter the following Technician Interface command:

wfsnmpmode 1

7-5

Quick-Starting Routers

Authentication Failure Traps

The router generates an authentication failure trap when it receives an SNMP message from an SNMP manager f alsel y claiming to be in a pa rticula r community or specifying an unknown community.

To enable the authentication fail ure tr ap fe ature on the rout er, configure an SNMP community manager to receive the trap. (See Configuring SNMP, BootP, DHCP, and RARP Services.)

Assigning SecurID to Telnet Connections

You can enable password protection for your Telnet connections to the router using SecurID services. See Using Technician Interface Software for information about enabling SecurID services.

Turning Off FTP and Telnet on the Router

If you have local access to your router or do not need network access to maintain your router, consider turning off FTP and Telnet. Your router will be more secure without network access and will require less memory and processing overhead.

You can turn these services off using the BCC or Site Manager. See Configuring IP Utilities for instructions.

Using the Image Builder to Remove Services

The Image B uilder tool provided with Site Manager allows you to modify the router software image. You can use the Image Builder tool to remove unwanted services and protocols, such as FTP, from the router. See Configuri ng and Managing R outers with Site Manager for more information.

7-6

303553-A Rev 00

Restricting Access to the HTTP Server

The HTTP Server u ses the fol lo wing Technician Interfa ce logins and pass words t o restrict access:

• The Manager login all ows access to all service s. To sign on as Manager on the

HTTP Server, you must first add a password for Manager using the Technician Interface (see “Assigning a Password to the Technician Interface on page 7-2

• The User login prohibits access to the SNMP community page and prevents

changes to the ports and protocols on the router. A password is not required.

Configuring Data Encryption Services

Bay Networks data encryption services enable you to protect sensitive traffic on your network. Encryption prevents unauthorized persons from reading, changing, or replaying data that travels between Bay Networks routers.

Data encryption services include:

Securing the Router

”

303553-A Rev 00

• Software-based enc ryption for PPP de dicated links f or the BN, AN, ARN, and

ASN routers; System 5000 router modules; and all serial interfaces. This includes encryption on multiline and multilink.

• Software-based encryption for frame relay circuits that have one permanent

virtual circuit (PVC) per service record. This include encryption on multiline.

• Encryption configurable on a line or circuit basis.

• Encryption with or without data compression. You can configure PPP dial backup for a frame relay circuit that uses data

encryption. Be aware, however, that if the primary circuit fails, data that travels over the backup circuit is unencrypted.

See Configuring Da ta Encr ypt ion Servi ces for more information.

7-7

Quick-Starting Routers

Configuring RADIUS

Remote Authentication Dial-In User Service (RADIUS) defines a method of centralizing authentication and accounting information for networks with many remote dial-in users. By placing authentication and accounting functions in one central location, you can improve security and better manage large networks.

In a network using RADIUS, the router is the RADIUS client. The client is the connection point between remote users and a RADIUS server. The server has the information that it needs to identify remote users and to keep accounting information for each call.

For more information, see Configuring RADIUS.

Installing BaySecure FireWall-1

For additional network security, Bay Networks provides BaySecure™ FireWall-1 software. This software integrates the Check Point FireWall-1 network security engine from Check Point Softw are Technologies Ltd into the Bay Networks rout er software to create a security system that provides fully secure, antispoofing communication for all Internet applications and services. For more information, see Configuring BaySecure FireWall-1.

7-8

To purchase or learn more about BaySecure FireWall-1 software, call Bay Networks Sales at 1-800-8-BAYNET.

303553-A Rev 00

Chapter 8

Installing Site Manager on a PC

Site Manager is a graphical user interface for router configuration and management over an IP network. To install Site Manager on a PC running Windows 95, review the following topics:

Topic Page

System Requirements 8-1 Updating TCP/IP, Network Adapters, and Drivers 8-2 Loading and Starting Site Manager Software 8-4

System Requirements

To run Site Mana ger, your PC must meet the following hardwa re and software requirements:

• 486 PC (Pentium PC recommended)

• Microsoft Windows 95

• 16 MB of RAM (minimum)

• 60 MB of free disk space

• Microsoft TCP/IP for Windows 95 and compatible network adapters and

driver

• CD-ROM drive

• VGA monitor (SuperVGA monitor recommended)

303553-A Rev 00

8-1

Quick-Starting Routers

Updating TCP/IP, Network Adapters, and Drivers

Site Manager Version 7.00 for Windows 95 requires the Microsoft TCP/IP protocol stack provided with Windows 95 and a compatible network adapter and driver.

If you purchased a PC with Windows 95 and a network adapter installed, most likely you have the correct TCP/IP protocol stack, network adapter, and driver. Go to “

If you need to upgrade from Windows 3.1 to Windows 95, first uninstall any existing 16-bit TCP/IP stack, such as Distinct TCP/IP Run Time. Otherwise, Windows 95 will install that stack instead of the Microsoft TCP/IP protocol stack.

If you already upgraded from Windows 3.1 to Windows 95 and the upgrade kept an existing 16-bit TCP/IP stack, such as Distinct TCP/IP Run Time, you must uninstall the 16-bit TCP/IP stack before adding the Microsoft TCP/IP protocol stack.

To uninstall a 16-bit TCP/IP stack, refer to the TCP/IP provider’s documentation and support for help in removing the stack’s path statements, services file, and WINSOCK.DLL files dated prior to July 11, 1995 (the date of the WINSOCK.DLL file installed by Windows 95).

Testing TCP/IP” on page 8-3.

8-2

To add or update a protocol, network adapter, or driver, refer to the appropriate documentation and support from Microsoft and the adapter manufacturer. Protocol and driver updates are added from the Network option of the Control Panel. New network adapters and their drivers are added from the Add New Hardware option of the Control Panel.

Windows 95 attempts to match a driver to the network adapter installed on your PC. If Windows 95 cannot match a compatible driver, you need to update the driv er. Contact the adapter manuf act ure r for the l ates t drivers. Microsoft and other Windows 95 Web sites may also have updated drivers.

Refer to Microsoft Windows 95 Resource Kit for additio nal technical information about these issues. A hard copy is available from Microsoft Press.

303553-A Rev 00

Preparing the Network Control Panel

In addition to obtaining the supported TCP/IP protocol, network adapters, and drivers, you need to configure the Network option of the Control Panel with the required information for your network.

Choose Control Panels > Network > TCP/IP > Properties to display the TCP/IP properties menu, which contains tab windows for the following information:

•IP address

• WINS configuration

• Gateway

• Bindings

• Advanced

• DNS configuration Refer to your Windows 95 Help or documentation for information about setting

the parameters in these windows.

Installing Site Manager on a PC

Testing TCP/IP

Before installing Site Manager, send a ping request to the rou ter to mak e sure your computer’s TCP/IP function is running.

303553-A Rev 00

From the Start Menu, choose Programs > MS-DOS Prompt. Enter the following command to ping your router:

ping

<ip_address>

ip_address

is the IP address of your router.

Messages appear at the prompt indicating whether replies were received. Replies verify that your Microsoft TCP/IP protocol stack is functional.

8-3

Quick-Starting Routers

Loading and Starting Site Manager Softwar e

Caution:

If you are reinstalling Site Manager, be aware that the installation will overwrite the c:\windows\siteman.ini file. If you are installing multiple versions of Site Manager on the same PC, make a copy of this file and later edit the new file to include the information about the other versions.

To install Site Manager software from a CD:

Insert the Bay Networks Site Manager CD into your CD-ROM drive.

Access the Run window by choosing Run from the Start menu.

Type the CD-ROM drive, path, and executable file:

<CD-ROM_drive>

:\ms_win\setup.exe

The D: drive is usually the CD-ROM drive.

Click on OK.

You can also use the Browse button, Windows Explorer, or My Computer to select the CD-ROM drive and the path to the ms_win directory and then click on setup.exe.

The installation script prompts you for the directory in which you want to install Site Manager.

Enter the directo ry in which to inst all Site Man ager, or accept the default,

c:\WF

8-4

The Site Manager files are installed in the chosen directory. When the installation is finished, the following prompt appears:

Create windows program group/items automatically?

To add Site Manager as a selection on the Start > Programs menu, click on Yes.

This option allows you to start Site Manager after installation by choosing Start > Programs > Site Manager > PC_Site Manager.

If you do not want Site Manager to appear as a selection on the Start > Programs menu, click on No.

The following prompt appears:

Do you want to start Site Manager now?

303553-A Rev 00

Installing Site Manager on a PC

Click on Yes at the prompt to start Site Manager.

The Router Connection Options window opens.

Enter the IP address and SNMP communit y of the initia l rout er interf ace that you created during the Quick-Start procedure.

Click on OK to display the main Site Manager window (Figure 8-1).

After you successfully install and start Site Manager, see Configuring and Managing R outers with Site Manager for more information.

Figure 8-1. Site Manager Window

303553-A Rev 00

8-5

Chapter 9

Installing Site Manager

on a Workstation Running Windows NT

Site Manager is a graphical user interface for router configuration and management ov er an IP networ k. To install Site Manager on a worksta tion running Windows NT, review the following topics:

Topic Page

System Requirements 9-1 Preparing the Network Control Panel 9-2 Testing TCP/IP 9-2 Loading and Starting Site Manager Software 9-3

System Requirements

Site Manager for the Windows NT operating system runs in 16-bit mode. Your workstation must meet the following hardware and software requirements:

• 486/100 workstation (Pentium workstation recommended)

• Microsoft Wi ndows NT Version 4.0

• 16 MB of RAM (minimum)

• 60 MB of free disk space

• TCP/IP Protocol and compatible network adapters and driver

• CD-ROM drive

• VGA monitor (SuperVGA monitor recommended)

303553-A Rev 00

9-1

Quick-Starting Routers

Preparing the Network Control Panel

You need to configure the Network option of the Control Panel with the required information for your network. Refer to Windows NT Help and documentation or commercial publication s suc h as Microsoft Windows NT Resource Kit if you need technical information about setting the Network options.

For the TCP/IP Protocol option, you need to set the following information:

•IP address

• DNS

• WINS address

• Routing

Testing TCP/IP

Before installing Site Manager, send a ping request to the rou ter to mak e sure your computer’s TCP/IP function is running.

From the Start Menu, choose Programs > MS-DOS Prompt.

9-2

Enter the following command to ping your router:

ping

<ip_address>

ip_address

is the IP address of your router.

Messages appear at the prompt indicating whether replies were received. Replies verify that your Microsoft TCP/IP protocol stack is functional.

303553-A Rev 00

Installing Site Manager on a Workstation Running Windows NT

Loading and Starting Site Manager Softwar e

Caution:

If you are reinstalling Site Manager, be aware that the installation will overwrite the c:\windows\siteman.ini file. If you are installing multiple versions of Sit e Manager on the same workst ation, ma ke a cop y of this fil e and later edit the new file to include the information about the other versions.

To install Site Manager software from a CD:

Insert the Bay Networks Site Manager CD into your CD-ROM drive.

Access the Run window by choosing Run from the Start menu.

Type the CD-ROM drive, path, and executable file:

<CD-ROM drive>

:\ms_win\setup.exe

The D: drive is usually the CD-ROM drive.

Click on OK.

You can also use the Browse button, Windows Explorer, or My Computer to select the CD-ROM drive and the path to the ms_win directory and then click on setup.exe.

If the TCP/IP services file is not located in the default directory, (C:\WINNT\system32\drivers\etc), the installation script prompts you for the directory.

303553-A Rev 00

If prompted to do so, enter the path to the directory where the TCP/IP services file is located.

Note:

The TCP/IP services file is different from the services.exe file.

The installation script prompts you for the directory in which you want to install Site Manager.

Enter the directo ry in which to inst all Site Man ager, or accept the default,

c:\WF

The Site Manager files are installed in the chosen directory. When the installation is finished, the following prompt appears:

Create windows program group/items automatically?

9-3

Quick-Starting Routers

To add Site Manager as a selection on the Start > Programs menu, click on Yes.

This option allows you to start Site Manager after installation by choosing Start > Programs > Site Manager > PC_Site Manager.

If you do not want Site Manager to appear as a selection on the Start > Programs menu, click on No.

The following prompt appears:

Do you want to start Site Manager now?

Click on Yes at the prompt to start Site Manager.

The Router Connection Options window opens.

Enter the IP address and SNMP communit y of the initia l rout er interf ace that you created during the Quick-Start procedure.

10.

Click on OK to display the main Site Manager window (Figure 9-1).

After you successfully install and start Site Manager, see Configuring and Managing R outers with Site Manager for more information.

9-4

303553-A Rev 00

Installing Site Manager on a Workstation Running Windows NT

Figure 9-1. Site Manager Window

303553-A Rev 00

9-5

Chapter 10

Installing Site Manager on a SPARCstation

Site Manager is a graphical user interface for router configuration and management over an IP network. To install Site Manager on a SPARCstation, review the following topics:

Topic Page

System Requirements 10-2 Setting Up the SPARCstation 10-2 Loading Site Manager Software 10-3 Setting Up Site Manager User Accounts 10-5 Verifying Site Manager Installation 10-6 Starting Site Manager 10-6

303553-A Rev 00

10-1

Quick-Starting Routers

System Requirements

To run Site Manager, your SPARCstation must meet the following hardware and software requirements:

• Supported workstations:

-- SPARCstation 10, 20

-- UltraSPARC

• Supported operating systems:

-- SunOS 4.1.4

-- Solaris 2.5.1 and 2.6

• Window environment for Solaris:

-- CDE 1.0.1

-- OpenWindows 3.5

• 32 MB of RAM (64 MB recommended)

• 100 MB of disk space

• 32 MB of swap space

• Network adapter appropriate for your network

• CD-ROM drive

Setting Up the SPARCstation

Before you load Site Manager software on your SPARCstation, do the following:

10-2

Edit the following lines at the bottom of the file:

snmp161/udp snmp-trap162/udp

You can use any text editor to edi t the file. Th e first line associates the serv ic e name associates the service name

Save

/etc/services

with UDP port number 161 on this host device. The second line

snmp

/etc/services

system file (on each host device) to include the

and exit from the text editor.

snmp-trap

su root

with UDP port number 162.

303553-A Rev 00

Installing Site Manager on a SPARCstation

Loading Site Manager Softwar e

Load Site Manager software on the SPARCstation as follows:

• Mount a CD-ROM dri ve.

• Install the software.

• Unmount the drive.

Note:

The command for mounting the CD-ROM drive va ries depending on your system, for example, the number of CD-ROM drives. If the suggested mount command fails, consult your operating system documentation.

Mounting a CD-ROM Drive on SunOS and Solaris

To mount a CD-ROM drive:

Insert the appropriate CD and drive tray into the CD-ROM drive.

303553-A Rev 00

At the password prompt, enter your root password.

If a subdirectory or file system does not already exist for the CD, create one by entering:

mkdir /cdrom

Mount the CD-ROM drive.

• For SunOS, enter:

mount -r -t hsfs /dev/

sr0

is the CD-ROM drive’s address.

sr0

/cdrom

• For Solaris, the Vo lume Manager au tomatically moun ts the CD onto /cdrom/release_1300_700. If the CD does not automatically mount, stop the vold daemon and manually mount the drive.

Display the daemon’s process ID by entering:

ps -ef | grep vold

If there is a process running for the

kill

<process_id>

vold

daemon, enter:

10-3

Quick-Starting Routers

Mount the CD-ROM drive by entering:

mount -F hsfs -o ro /dev/dsk/

c0t6d0s0

Installing the Software

To install Site Manager software:

As root, change to the CD-ROM mountpoint.

cd /cdrom

If you use Solaris and are running the vold daemon, enter:

cd /cdrom/release_1300_700

Run the script to load Site Manager software by entering:

. /install.sh

The installation process does the following:

• Lists the directories that contain enough space to install Site Manager. You can then specify the directory you want to use.

• Executes the Site Manager installation script, WFSM_INSTALL.

When the installation is finished, your workstation displays the message:

c0t6d0s0

is the CD-ROM drive’s address.

/cdrom

Site Manager Installation Complete.

Additional messages about your SPARCstation environment may appear.

Unmounting the CD-ROM Drive

To unmount a CD-ROM drive, enter:

cd / umount /cdrom

For CDs automatically mounted on a CD-ROM drive, enter:

cd / eject cdrom

10-4

303553-A Rev 00

Installing Site Manager on a SPARCstation

Setting Up Site Manager User Ac counts

To set up individual Site Manager users on the SPARCstation:

Press [Control]-d to exit the root account.

If this is the first time you installed Site Manager, create the directory in which to install the Site Manager Image Builder application by entering:

mkdir $HOME/.builder_dir

Edit the user account s etup file as follows:

• If you use the C shell (csh) or clones, add the follow ing lines to .cshrc:

set path = ($path /usr/wf/bin) setenv WF_SMPATH /usr/wf setenv SMTERM X setenv SM_CONFIGS setenv BUILDER_DIR $HOME/.builder_dir

<directory_where_config_files_are_stored>

303553-A Rev 00

Note:

If the shell variable path is already set in some other line of the .cshrc

file, add these new lines immediately after the last

set path line.

• If you use the Bourne shell (sh) or clones, add the following lines to .profile:

PATH=$PATH:/usr/wf/bin WF_SMPATH=/usr/wf SMTERM=X SM_CONFIGS= BUILDER_DIR=$HOME/builder_dir export WF_SMPATH SMTERM SM_CONFIGS BUILDER_DIR

Log out of the user account.

<directory_where_config_files_are_stored>

Repeat steps 1 through 5 for ea ch user acc oun t that nee ds to run Sit e Manag er.

10-5

Quick-Starting Routers

Verifying Site Manager Installation

To verify the Site Manager installation and environment:

Start the window environment (CDE or OpenWindows).

Verify the Site Manager installation by entering:

wfchkinst

If the installation was successful, the workstation displays the message:

Installation is complete and correct!

Verify the Site Manager environment by entering:

wfchkenv

If the environment is correctly configured, the workstation displays the message:

Your environment seems to have been set up correctly.

Repeat steps 1 through 4 for each user account that has Site Manager installed.

Note:

If your environment variables are incorrect, you receive an error

message to reset the variables.

Starting Sit e Manager

To start the Site Manager application:

Start the window environment, for example, CDE.

Change to a dir ec tor y wi th read/write priv il ege s whe re Site Manager ca n save configuration and other files.

For example, the following command changes to the directory /home/siteman/config_files:

cd /home/siteman/config_files

10-6

303553-A Rev 00

Installing Site Manager on a SPARCstation

Activate Site Manager by entering the following command:

wfsm -a

router_IP_address

<router_IP_address>

is the IP add ress of the r outer’s initial interface.

For example, the following command starts Site Manager and connects to a router with the IP address 192.168.125.34:

wfsm -a 192.168.125.34 &

The Site Manager window opens (Figure 10-1).

Figure 10-1. Site Manager Window

After you successfully install and start Site Manager, see Configuring and Managing R outers with Site Manager for more information.

303553-A Rev 00

10-7

Quick-Starting Routers

Starting Site Manager from SunNet Manager

After you install Site Manager on a workstation running SunNet Manager or Domain Manager, you must exit SunNet Manager or Domain Manager and run

snm -i

the the schema in SunNet Manager or Domain Manager.

To start a Site Manager session on a workstation running SunNet Manager or Domain Manager:

Edit View OptionsLocate

File Monitor Test AdministerTools

command from the command line to in tegr ate Site Manager and update

Open a view containing the icon of a router that you want to configure using Site Manager.

Click on the icon of the router you want to configure. From the Tools menu, choose Site Manager (Figure 10-2).

The Site Manager window opens.

IP Internet

MIB Application Builder: SNMP... MIB Browser: SNMP... Graph Collected Data: SNMP Data Collection & Thresholds: SNMP... Filter Editor... Site Manager Failing Resource Display... Mail... Print...

Help

Site Manager... Configuration (dynamic)... Statistics Manager... Trap Monitor... Remote Files Manager... Event Files... Update Symbols...

U.2844.4

10-8

Figure 10-2. Starting a Site Manager Session from SunNet Manager

303553-A Rev 00

Starting Site Manager from OpenView

Read this section if you plan to install or are currently running the HP OpenView application on your SPARCstation.

After you install Site Manager on a workstation running HP OpenView, exit HP OpenView and enter Manager with the OpenView application and to update the symbols. Do this instead of using the Updat e Symbols option on t he OpenView Site Manager menu.

To start a Site Manager session from the IP Internet window menu bar in OpenView:

Open a view containing the icon of the router that you want to configure using Site Manager.

The IP Internet window opens with a map of your internetwork.

Click on the icon of the router you want to configure.

From the Tools menu, choose Site Manager (Figure 10-3).

The Site Manager window opens with a list of tools.

ovw -fields

Installing Site Manager on a SPARCstation

at the comman d line to integrate Site

303553-A Rev 00

If the Site Manager tools are dimmed, delete the router from OpenView so that it can be rediscovered.

IP Internet

Edit View OptionsLocate

File Monitor Test AdministerTools

MIB Application Builder: SNMP... MIB Browser: SNMP... Graph Collected Data: SNMP Data Collection & Thresholds: SNMP... Filter Editor... Site Manager Failing Resource Display... Mail... Print...

Site Manager... Configuration (dynamic)... Statistics Manager... Trap Monitor... Remote Files Manager... Event Files... Update Symbols...

Figure 10-3. Starting a Site Manager Session from OpenView

Help

U.2844.4

10-9

Quick-Starting Routers

If you install OpenView after you install Site Manager software, follow these steps to integrate Site Manager with the OpenView application.

Change to the

Reexecute the Site Manager installation script by entering:

. / WFSM_INSTALL

/usr/wf

directory.

Follow these steps any time you reinstall OpenView.

10-10

303553-A Rev 00

Avaya Quick-Starting Routes User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual