Avaya Quick-Starting Routers and BNX Platforms User Manual

Download

Quick-Starting Routers and

BNX Platforms

Router Software Version 10.0

Site Manager Software Version 4.0

Software Version BNX 6.0

Site Manager Software Version BNX 6.0

Part No. 112933 Rev. A

January 1996

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

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 speciﬁed in this document. The information in this document is proprietary to Bay Networks, Inc.

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

Restricted Rights Legend

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

Notice for All Other Executive Agencies

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

Trademarks of Bay Networks, Inc.

ACE, AFN, BCN, BLN, BN, CN, FRE, LN, Optivity, SynOptics, SynOptics Communications, Wellﬂeet and the Wellﬂeet logo are registered trademarks and AN, ANH, ASN, BaySIS, BayStack, BCNX, BLNX, BNX, EZ Internetwork, EZ LAN, FN, PathMan, PhonePlus, PPX, Quick2Conﬁg, RouterMan, SPEX, Bay Networks, Bay Networks Press, the Bay Networks logo and the SynOptics logo are trademarks of Bay Networks, Inc.

Third-Party T rademarks

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

Statement of Conditions

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

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

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

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

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

Bay Networks Software License

Note:

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

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

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

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

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

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

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

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

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

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

4401 Great America Parkway, Santa Clara, CA 95054

8 Federal Street, Billerica, MA 01821

Bay Networks, Inc.

Bay Networks Software License

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

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

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

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

(continued)

4401 Great America Parkway, Santa Clara, CA 95054

8 Federal Street, Billerica, MA 01821

Bay Networks, Inc.

Contents

About This Guide

Audience ..........................................................................................................................xiii

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

Bay Networks Customer Support ....................................................................................xiv

CompuServe .............................................................................................................xiv

InfoFACTS .................................................................................................................xv

World Wide Web ........................................................................................................ xv

How to Get Help ..............................................................................................................xvi

Conventions .....................................................................................................................xvi

Ordering Bay Networks Publications ..............................................................................xvii

Acronyms ........................................................................................................................xvii

Chapter 1 Overview of Quick-Start

Chapter 2 Filling Out the Network Information Worksheet

Chapter 3 Connecting a PC or ASCII Console

Connecting a PC ............................................................................................................3-1

Connecting an ASCII Console ........................................................................................3-2

Chapter 4 Connecting to the IP Network

Chapter 5 Establishing a Technician Interface Session

Chapter 6 Running the Quick-Start Installation Script

Understanding the Router or BNX Platform’s File System .............................................6-1

Reviewing the Installation Files ......................................................................................6-2

Booting with the ti.cfg File ...............................................................................................6-4

Running the Quick-Start Installation Script .....................................................................6-5

Quick-Start T roub leshooting .....................................................................................6-9

Assigning a Password ..................................................................................................6-10

Exiting the Technician Interface ....................................................................................6-10

Chapter 7 Installing Site Manager on a PC

Reviewing System Requirements ...................................................................................7-1

Installing Distinct TCP/IP ................................................................................................7-2

Preparing Information for the Distinct Installation ....................................................7-3

Preparing Serial Number and Key-Code Information ........................................7-3

Preparing Network Interface Card and Driver Information .................................7-4

Preparing Network Conﬁguration Information ...................................................7-5

Installing the Distinct Software .................................................................................7-6

Testing Distinct TCP/IP .............................................................................................7-8

Loading the Site Manager Software ...............................................................................7-9

Creating a Windows Group ....................................................................................7-11

Adding a Well-Known Service for TFTP .................................................................7-11

Starting Up Site Manager .............................................................................................7-12

Chapter 8 Installing Site Manager on a SPARCstation

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

Setting Up the SPARCstation .........................................................................................8-2

Loading the Site Manager Software ...............................................................................8-2

Adding Site Manager User Accounts ..............................................................................8-3

Verifying Site Manager Installation .................................................................................8-5

Starting Up Site Manager ...............................................................................................8-5

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

Starting Site Manager from OpenView ....................................................................8-8

Chapter 9 Installing Site Manager on an RS/6000

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

Loading Motif ..................................................................................................................9-2

Loading the Site Manager Software ...............................................................................9-3

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

Verifying Site Manager Installation .................................................................................9-5

Starting Up Site Manager ...............................................................................................9-5

Starting Site Manager from NetView/6000 ...............................................................9-7

Chapter 10 Installing Site Manager on an HP 9000

Reviewing System Requirements .................................................................................10-1

Loading the Site Manager Software .............................................................................10-2

Adding Site Manager User Accounts ............................................................................10-3

Verifying Site Manager Installation ...............................................................................10-4

Starting Up Site Manager .............................................................................................10-4

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

Chapter 11 Creating a Pilot Conﬁguration File

Connecting to the Router or BNX Platform ...................................................................11-4

Using Remote Mode .....................................................................................................11-5

Conﬁguring the Pilot IP Interface ..................................................................................11-7

Adding a Circuit on a Connector ............................................................................11-7

Enabling the IP Protocol .......................................................................................11-10

Saving the Pilot Conﬁguration File .......................................................................11-12

Rebooting with the Pilot Conﬁguration File ..........................................................11-13

Enhancing the Pilot Conﬁguration File .................................................................11-15

Securing the Router or BNX Platform .........................................................................11-15

Restricting Read/Write Access ............................................................................11-15

Setting Secure Mode ............................................................................................11-16

Specifying Secure Mode ................................................................................11-17

Appendix A Sample Install.bat Script

Appendix B Sample TCP/IP Stack and NIC Driver Installation

Index

vii

Figures

Figure 2-1. Sample Network Used In Worksheet Examples ......................................2-2

Figure 5-1. Technician Interface Screen .....................................................................5-1

Figure 6-1. Sample NVFS dinfo Display .....................................................................6-2

Figure 6-2. Sample Installation Files ..........................................................................6-3

Figure 6-3. Beginning of the Quick-Start Installation ..................................................6-7

Figure 6-4. Summary Information for a Quick-Start Installation .................................6-8

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

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

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

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

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

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

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

Figure 10-2. Starting a Site Manager Session from OpenView .................................10-7

Figure 11-1. Sample Pilot Conﬁguration ....................................................................11-3

Figure 11-2. Site Manager Window ............................................................................11-4

Figure 11-3. Naming the Conﬁguration File ...............................................................11-5

Figure 11-4. Conﬁguration Manager Window .............................................................11-6

Figure 11-5. Add Circuit Window ................................................................................11-8

Figure 11-6. Site Manager Default Circuit Name .......................................................11-9

Figure 11-7. Select IP in the Protocols Window .......................................................11-11

Figure 11-8. IP Conﬁguration Window ......................................................................11-11

Figure 11-9. Save Conﬁguration File Window ..........................................................11-13

Figure 11-10. Sample Boot Router Window ...............................................................11-14

Tables

Table 1-1. Routers with Quick-Start Procedures ......................................................1-1

Table 2-1. Network Information Worksheet ...............................................................2-3

Table 4-1. Initial Connection Port to the IP Network .................................................4-1

Table 6-1. Quick-Start Installation Files ....................................................................6-3

Table 6-2. Router or BNX Platform Software Images ...............................................6-4

Table 6-3. Quick-Start Installation Script Commands ...............................................6-6

Table 7-1. Distinct Serial Numbers and Key Codes ..................................................7-3

Table 7-2. Distinct Conﬁguration Worksheet .............................................................7-5

Table 11-1. Circuit-type Designators in Default Circuit Names .................................11-9

About This Guide

If you are responsible for activating a router or BNX platform on your IP network, this guide can help you complete the Quick-Start installation procedure to

• Conﬁgure the initial IP network interface

• Install Site Manager on your workstation or PC You use Site Manager to remotely conﬁgure and manage routers and BNX

platforms over the network.

• Use Site Manager to create a pilot conﬁguration

When you ﬁnish the procedure, the router or BNX platform will actively route IP trafﬁc on your network.

Audience

Note:

Use this guide for first-time installations. For upgrades, use only those

sections of this guide that are referred to in the appropriate upgrade guide:

• Upgrading Routers from Version 5 to Version 10.0

• Upgrading Routers from Version 7-9.xx to Version 10.0

• BNX 6.0 Release Notes

Written for system and network managers, this guide describes how to initially conﬁgure your Bay Networks router or BNX platform on the IP network and install Site Manager on your hardware platform. This guide does not apply to

routers. It covers local Quick-Start procedures for the ASN™ router. For

AN™ ASN network booting information, refer to

Platforms to a Network

Connecting ASN Routers and BNX

xiii

Quick-Starting Routers and BNX Platforms

Before Y ou Begin

Before using this guide, you must install the router. Refer to the installation manual that came with your router for instructions. Also, review the Read Me First and Release Notes documents for changes to the Quick Start instructions.

Bay Networks Customer Support

Bay Networks provides live telephone technical support to our distributors, resellers, and service-contracted customers from two U.S. and three international support centers. If you have purchased your Bay Networks product from a distributor or authorized reseller, contact the technical support staff of that distributor or reseller for assistance with installation, conﬁguration, troubleshooting, or integration issues.

Customers also have the option of purchasing direct support from Bay Networks through a variety of service programs. The programs include priority access telephone support, on-site engineering assistance, software subscription, hardware replacement, and other programs designed to protect your investment.

To purchase any of these support programs, including PhonePlus™ for 24-hour telephone technical support, call 1-800-2LANWAN. Outside the U.S. and Canada, call (408) 764-1000. You can also receive information on support programs from your local Bay Networks ﬁeld sales ofﬁce, or purchase Bay Networks support directly from your reseller. Bay Networks provides several methods of receiving support and information on a nonpriority basis through the following automated systems.

CompuServe

xiv

Bay Networks maintains an active forum on CompuServ e. All you need to join us online is a computer, a modem, and a CompuServe account. We also recommend using the CompuServe Information Manager software, available from CompuServe.

The Bay Networks forum contains libraries of technical and product documents designed to help you manage and troubleshoot your Bay Networks products. Software agents and patches are available, and the message boards are monitored by technical staff and can be a source for problem solving and shared experiences.

InfoFACTS

About This Guide

Customers and resellers holding Bay Networks service contracts can visit the special libraries to acquire advanced levels of support documentation and software.

To open an account and receive a local dial-up number, call CompuServe at 1-800-524-3388 and ask for Representative No. 591.

• In the United Kingdom, call Freephone 0800-289378.

• In Germany, call 0130-37-32.

• In Europe (except for the United Kingdom and Germany), call (44) 272-760681.

• Outside the U.S., Canada, and Europe, call (614) 529-1349 and ask for Representative No. 591, or consult your listings for an ofﬁce near you.

Once you are online, you can reach our forum by typing the command GO BAYNETWORKS at any ! prompt.

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

W orld Wide Web

The World Wide Web (WWW) is a global information system for ﬁle distribution and online document viewing via the Internet. You need a direct connection to the Internet and a Web Browser (such as Mosaic or Netscape).

Bay Networks maintains a WWW Home Page that you can access at http:// www.baynetworks.com. One of the menu items on the Home Page is the Customer Support Web Server, which offers technical documents, software agents, and an E-mail capability for communicating with our technical support engineers.

Quick-Starting Routers and BNX Platforms

How to Get Help

For additional information or advice, contact the Bay Networks Technical Response Center in your area:

United States 1-800-2LAN-WAN Valbonne, France (33) 92-966-968 Sydney, Australia (61) 2-903-5800 Tokyo, Japan (81) 3-328-005

Conventions

This section describes the conventions used in this guide: angle brackets (< >) Indicate that you choose the text to enter based on the

arrow character (➔) Separates menu and option names in instructions.

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

192.32.10.12

Example: Protocols

<ip_address>

➔

AppleTalk identiﬁes the

, you enter

ping

AppleTalk option in the Protocols menu.

ping

xvi

bold text

italic text

Indicates text that you need to enter and command

dinfo

names in text. Example: Use the

command.

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

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

screen text

Indicates data that appears on the screen. Example:

Bay Networks Trap Monitor Filters

Set

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

command. The vertical line separates choices. Do not type the vertical line when entering the command.

Example: If the command syntax is

show at routes show at routes

nets

, you enter either

show at nets

, but not both.

Ordering Bay Networks Publications

To purchase additional copies of this document or other Bay Networks publications, order by part number from Bay Networks Press™ at the following numbers. You may also request a free catalog of Bay Networks Press product publications.

Phone: 1-800-845-9523 FAX - U.S./Canada: 1-800-582-8000 FAX - International: 1-916-939-1010

Acronyms

AFN Access Feeder Node ALN ASN Access Stack Node BCN Backbone Connector Node BLN Backbone Link Node BOOTP Bootstrap Protocol CN Concentrator Node FTP File Transfer Protocol FDDI Fiber Distributed Data Interface LN Link Node NIC network interface card NVFS Non-Volatile File System OSI Open Systems Interconnection QENET Quad Ethernet Link Module RIP Routing Information Protocol RISC Reduced Instruction Set Chip SNMP Simple Network Management Protocol TCP/IP Transmission Control Protocol/Internet Protocol TFTP Trivial File Transfer Protocol

Access Link Node

About This Guide

xvii

Chapter 1

Overview of Quick-Start

This manual describes the Quick-Start procedure to locally boot your router or BNX platform and initially conﬁgure it on the IP network. To complete the QuickStart procedure, you follow these steps:

Complete Quick-Start prerequisites.

Complete the following prerequisites before you begin the Quick-Start procedure.

Review whether Quick-Start procedures apply to your product.

Table 1-1 shows the Bay Networks routers with Quick-Start procedures covered in this manual. This manual does not apply to AN routers. AN routers have similar Local Boot procedures that are covered in their administrative manuals.

Table 1-1. Routers with Quick-Start Procedures

Bay Networks Router or BNX Platform

Access Feeder Node (AFN®) Access Link Node (ALN) Access Stack Node (ASN) Backbone Concentrator Node (BCN®) Backbone Link Node (BLN®)

Concentrator Node (CN Link Node (LN®)

)

1-1

Quick-Starting Routers and BNX Platforms

Review Release Notes.

Review the release notes in this version’s documentation for new information about installation and conﬁguration.

Install the router or BNX platform.

Install the router or BNX platform at your site. Refer to the installation manual that came with the router.

Understand ASN terminology.

To Quick-Start an ASN, you need to understand some ASN terminology. Certain terms have different meanings for the ASN than for other Bay Networks routers or BNX platforms.

Each ASN unit is a separate node. You can connect as many as 4 nodes together into an ASN stack. Site Manager treats the combined nodes in an ASN stack as a single router.

The networking hardware modules in an ASN are called net modules. (In other Bay Networks routers and BNX platforms, these are link modules.) In an ASN, the term slot refers to the main processor module in each ASN node. (For Bay Networks routers and BNX platforms other than the ASN, the slot is where the link module resides.) Each ASN slot contains one to four net modules.

1-2

When you conﬁgure the ASN (or ASN stack), you identify the location of a net module by specifying:

slot

• The

that contains the net module and

module position

where the net module resides

The ASN slot ID identiﬁes the slot number. You set the slot ID using the slot ID dial on the rear panel of each ASN node. The modules positions are numbered 1 through 4 in each slot. For more information, refer to

Installing and Maintaining ASN Routers and BNX Platforms

Fill out the Network Information Worksheet.

Complete the Network Information Worksheet (Chapter 2) to assemble the information you need to Quick-Start the router or BNX platform (for example, the IP address and subnet mask of the router’s initial IP network interface).

Overview of Quick-Start

Connect a PC or ASCII console to the router.

Connect a PC or a terminal to the router’s or BNX platform’s console port to view the Technician Interface (Chapter 3).

Connect to the IP network.

Connect a cable between the router or BNX platform and the IP network (Chapter 4).

Establish a Technician Interface session.

Use the T echnician Interface, Bay Netw ork’ s command-line interface, to enter commands to run the Quick-Start installation script on the router (Chapter 5).

Run the Quick-Start installation script.

Run Quick-Start to establish an initial IP network interface between the router or BNX platform and the workstation from which you’ll manage the router (Chapter 6).

Install Site Manager.

Install the Bay Networks Site Manager program on a PC or workstation located on the IP network. Site Manager uses Simple Network Management Protocol (SNMP) and Trivial File Transfer Protocol (TFTP) to communicate with the router or BNX platform so you can remotely conﬁgure and manage the router.

Follow the instructions in the appropriate chapter to install the Site Manager software on a

— PC (Chapter 7) — SPARCstation (Chapter 8) — RS/6000 (Chapter 9) —HP

Note:

9000 (Chapter 10)

BNX Site Manager does not run on the HP 9000 workstation.

1-3

Quick-Starting Routers and BNX Platforms

Use Site Manager to create a pilot conﬁguration.

Once you’ve installed Site Manager on a workstation, you can conﬁgure the router or BNX platform remotely by

— Creating a simple pilot conﬁguration ﬁle — Transferring the conﬁguration ﬁle to the router — Booting the router with pilot conﬁguration Creating the pilot conﬁguration ﬁle (Chapter 11) completes the Quick-Start

procedure described in this manual. To reﬁne your conﬁguration ﬁle to meet your speciﬁc network needs, refer to

Conﬁguring Routers or Conﬁguring Customer Access and Trunks (BNX Software)

and the appropriate protocol conﬁguration manuals.

1-4

Chapter 2

Filling Out the Network Information Worksheet

You ﬁll out a Network Information Worksheet to refer to when you perform the Quick-Start installation script ( Appendix A for a sample installation script.)

The installation script prompts you for network information to connect the router or BNX platform to the IP network. The worksheet contains space for the adv ance information you will need when running

Use only the portions of the worksheet that apply to your network requirements. For example, if you are not enabling OSPF on the IP interface, pass over any questions that pertain to OSPF.

Many steps in the installation script suggest default values. Accept the default values unless you have a reason to make a change.

install.bat

) as described in Chapter 6. (See

install.bat

Some steps are optional for your network requirements. For example, local PAP passwords are optional with PPP. Also, if you don’t run optional features such as FTP or Telnet, your router will be more secure and use less memory and processing overhead.

The examples on the Network Information Worksheet reﬂect information from the sample network in Figure 2-1.

Note:

Contact your network administrator for assistance in selecting

™

worksheet options. AN and ANH

routers are not covered by this worksheet.

2-1

Quick-Starting Routers and BNX Platforms

Connect a PC or ASCII console locally to view the Technician Interface and run the Quick-Start installation script,

install.bat

Bay Networks router or BNX platform

Console port in Slot 1 of AFN, FN, LN, ALN, CN, BLN, or ASN or in Slot 7 of BCN

Connect the router or BNX platform to the IP network. This router connects from a

QENET Link Module in Slot 2 using XCVR1 (Ethernet Connector 1)

IP = 192.168.125.34 Subnet Mask = 255.255.255.0

Corporate IP network

2-2

Use a Site Manager workstation to manage the router or BNX platform remotely.

IP Address= 192.32.10.12

Figure 2-1. Sample Network Used In Worksheet Examples

Filling Out the Network Information Worksheet

Table 2-1. Network Information Worksheet

Requested Information Example Your Information Physical Connector Information

Enter the slot number containing the link module that provides the initial IP network interface (this module can reside in any slot that is designated for link module support).

Note: You also provide the module number for the ASN (example - Module1).

2 QE/NF

Number of the connector (port) providing the initial IP network interface.

Circuit Information

Enter the number of the circuit name. 1. E21

IP Interface Conﬁguration Information

IP address of this initial network interface. (Advanced users only – interfaces.)

Subnet mask address of this initial network interface (in dotted decimal notation).

Does this interface connect to the same local area network (LAN) as the Site Manager workstation?

IP Routing Protocol Information

IP Routing Protocol to conﬁgure to manage this router remotely. This is necessary only if you answered No to the previous question.

See the following sections for details on the IP Routing Protocol you choose to conﬁgure.

RIP Conﬁguration Information

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

install.bat

supports unnumbered

1. XCVR1

192.168.125.34

255.255.255.0

RIP

Yes

(continued)

2-3

Quick-Starting Routers and BNX Platforms

Table 2-1. Network Information Worksheet

Requested Information Example Your Information OSPF Conﬁguration Information

OSPF Router IP Address. 192.32.156.7 OSPF Area Address. 0.0.0.0 Enable Simple Password Authentication? No MTU size for OSPF packets (Default, Ethernet Size,

User-deﬁned MTU). OSPF interface type (Broadcast, NBMA, or Point to

Point, Point to Multipoint, Point to Multipoint [std]). Note: Match to the interface type. The interface type,

Hello Interval, and Dead Interval must match the current OSPF conﬁguration of the network.

Hello interval (in seconds). 10 Router dead interval (in seconds). 40 Router priority. 1 Poll interval. 20 If you are conﬁguring OSPF neighbors, what is the IP

address for each neighbor? Note: Neighbors are deﬁned only if the OSPF interface

type is NBMA.

(continued)

Default

Broadcast

Not applicable. Sample format:

192.32.156.8

192.32.156.9

Static Route to Site Manager Conﬁguration Information

Destination network. 192.32.90.0 Destination network mask. 255.255.255.0 Next-hop address that is in the same subnet as the initial

IP interface.

Miscellaneous Information

Set SNMP Community Management? No Default volume where TFTP transactions will take place. 2 Enable FTP? Yes Default volume where FTP transactions will take place. 2 Enable TELNET? No

192.32.4.99

2-4

(continued)

Filling Out the Network Information Worksheet

Table 2-1. Network Information Worksheet

Requested Information Example Your Information Site Manager Workstation Information

IP address of the workstation on which the Site Manager software will be installed. This information is requested when the installation is tested at the end of the procedure.

WAN Information

The following information about enabling Frame Relay, PPP, and SMDS from the installation script is for experienced users only. Normally these protocols are implemented from Site Manager on an additional interface.

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 ﬁeld length. 2 bytes Frame Relay PVC ID. 30

(continued)

192.32.10.12

LMI

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

(continued)

2-5

Quick-Starting Routers and BNX Platforms

Table 2-1. Network Information Worksheet

Requested Information Example Your Information

Enable use of remote peer’s LQR timer? Yes Minimum acceptable percentage of inbound packets. 90 Minimum acceptable percentage of outbound packets. 90

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

(continued)

2-6

You connect to the router or BNX platform locally, with a PC or ASCII console, so you can run the Technician Interface and start the Quick-Start procedure.

Connecting a PC

Connect your PC to the router or BNX platform as follows:

1. Set the communications parameters in the Terminal program that comes

with Microsoft Windows or other terminal-emulation program.

a. From W indows, open the Terminal program in the Accessories gr oup. b. Double-click on the Terminal icon.

Chapter 3

Connecting a PC or ASCII Console

c. Select Settings➔Terminal Emulation. d. Click on the DEC VT100 (ANSI) option and click on OK. e. Select Settings➔Communications. f. Set the communications options as follows:

— Baud rate = 9600 — Data bits = 8 — Stop bits = 1 — Parity = none — Flow control = Xon/Xoff

g. Click on the COM port you want to connect to the router or BNX

platform, and click on OK.

COM ports usually have a 9-pin female or a 25-pin female connection.

3-1

Quick-Starting Routers and BNX Platforms

Select Settings➔Terminal Preferences.

h. i. Turn off the Use Function, Arrow, and Control Keys for Windows

default option so that you can use keyboard combinations when running the installation script.

Note: If you do not deselect the button for Use Function, Arrow, and

Control Keys for Windows, you will not be able to use keyboard

combinations such as Control-C when running the installation script.

j. Select File➔Sa ve As. k. Type the name of a new ﬁle in which to store the communications

settings, and click on OK.

l. Select File➔Open. m. Select the ﬁle you just named and click on OK.

2. Connect the cable from the console port of the router or BNX platf orm to

the COM port you selected in the terminal emulation program.

BCN, BLN, CN, and LN routers have a 25-pin male console port. ASN and AFN routers have a 9-pin male console port. Refer to the installation book that came with your router or BNX platform for more information.

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

When the router or BNX platform boots, the screen displays the Technician Interface

Note: While you can run the Technician Interface with a local connection, to

manage the router or BNX platform with Site Manager on a PC, you must connect the PC to the IP network.

Connecting an ASCII Console

Connect an ASCII console (terminal) to the router or BNX platform as follows:

1. Set the operating parameters of the ASCII console as follows:

• Baud rate = 9600

• Stop bits = 1

• Parity = none

• Data bits = 8

3-2

Connecting a PC or ASCII Console

2. Connect the cable from the ASCII console to the router or BNX platf orm.

BCN, BLN, CN, and LN routers have a 25-pin male console port. ASN and AFN routers have a 9-pin male console port. Refer to the installation guide that came with your router or BNX platform for more information.

3. Power on the router or BNX platform to complete the internal

diagnostics and startup.

When the router or BNX platform boots, the screen displays the Technician Interface

3-3

Chapter 4

Connecting to the IP Network

When you ordered your router or BNX platform, you also ordered a cable to connect the router or BNX platform to the IP network. Connect it using the following procedure:

1. Connect the cable to your router or BNX platform.

Table 4-1 gives the standard ports (also called connectors) for initially connecting the router or BNX platform to the IP network.

Table 4-1. Initial Connection Port to the IP Network

Bay Networks Router or BNX Platform

AFN/ES XCVR1 port AFN/TS MAU1 port ASN Any port on any net module, excluding the Stack

FN, ALN, LN, CN, BLN, BCN First port on the ﬁrst link module (Slot 2 except

Default Connection Port

Packet Exchange (SPX) Module

BCN)

You can conﬁgure any port on a router or BNX platform for the initial IP connection by modifying the connection port in the Quick-Start installation script described in Chapter 6.

For information on the location of the port on your router or BNX platform, refer to the installation manual that came with your router or BNX platform.

2. Connect the cable to the IP network.

The connection depends upon your LAN or WAN conﬁguration.

4-1

Quick-Starting Routers and BNX Platforms

For general information about cables, refer to Cable Guide for Routers and BNX Platforms.

4-2

Chapter 5

Establishing a Technician Interface Session

Use the Technician Interface, the router or BNX platform’s command-line interface, to enter commands to run the Quick-Start program. Establish a Technician Interface session as follows:

1. At the Login prompt, enter

Manager

Note: The Technician Interface is case-sensitive; that is, the command

Manager is not the same as manager.

The screen displays the slot where the Technician Interface is running, followed by the $ prompt, showing that you are logged in (Figure 5-1).

Technician Interface running on Slot 2, Console Port 1

Figure 5-1. Technician Interface Screen

> Login: Manager

> Welcome to the Backbone Technician Interface

[2:1]$

5-1

Quick-Starting Routers and BNX Platforms

For AFN, ASN, BLN, or BCN routers or BNX platforms, proceed to

Chapter 6 to run the installation script.

3. For ALN, FN, LN, or CN routers, perform the steps below. a. Enter the backplane command:

backplane

<router_type>

<router_type> is FN, LN, or CN. If you have an ALN, use LN as your <router_type>.

Example

backplane LN

Boot the router by entering

boot

You must boot the router after issuing the backplane command.

c. Log in again as Manager when the Login prompt appears. d. Proceed to Chapter 6 to run the installation script.

5-2

Chapter 6

Running the Quick-Start Installation Script

Run the Quick-Start installation script to establish an initial IP network interface between the router or BNX platform and the Site Manager workstation from which you’ll manage the router or BNX platform.

To create the initial IP interface you need to

• Understand the router or BNX platform’s ﬁle system.

• Review the Quick-Start installation ﬁles.

• Boot the router or BNX platform with the ti.cfg ﬁle (a special booting ﬁle that initializes the router or BNX platform without pre-existing conﬁguration).

• Run the Quick-Start installation script (install.bat) once, to conﬁgure the initial interface.

The Quick-Start installation script prompts you to enter the network information that dynamically conﬁgures the initial IP interface. You conﬁgure subsequent interfaces with Site Manager, Quick2Conﬁg, or other router management software.

Understanding the Router or BNX Platform’s File System

Your router or BNX platform stores installation ﬁles on memory cards. The NonVolatile File System (NVFS) running in the router or BNX platform reads and writes to the memory cards for ﬁle storage. Some older models also have disk drives with the Disk Operating System (DOS), but installation ﬁles for this release are not distributed on disks. Call the Bay Networks Technical Response Center for information on updating to a memory card system.

6-1

Quick-Starting Routers and BNX Platforms

Reviewing the Installation Files

After establishing the Technician Interface session, you are ready to display the Quick-Start installation ﬁles and verify that they are available:

1. Find the memory card location.

Identify the slot where the router or BNX platform’s memory card (volume) resides by typing

dinfo

The Technician Interface interface displays a table showing the memory card’s slot and memory statistics (Figure 6-1). BCNs and BLNs may contain multiple memory cards — 1 memory card per slot.

$ dinfo

VOL STATE TOTAL SIZE FREE SPACE CONTIG FREE SPACE

6-2

2: FORMATTED 4194304 1458420 1458420

The volume resides in the slot indicated.

Figure 6-1. Sample NVFS dinfo Display

Display the names of the ﬁles in the volume (Figure 6-2) by typing

dir

<slot_number>

<slot number> is the memory card’s slot. Include the colon (:) after the slot

number as part of the command string

Running the Quick-Start Installation Script

$ dir 2: Volume in volume 2: is Directory of 2:

File Name Size Date Day Time

-----------------------------------------------------config 7132 11/11/94 Fri. 15:42:01 bn.exe 2644489 01/25/95 Wed. 08:22:19 install.bat 147222 01/31/95 Tues. 08:52:34

ti.cfg 184 01/31/95 Tues. 14:59:33 debug.al 12568 01/31/95 Tues. 15:00:17 freboot.exe 173040 01/31/95 Tues. 15:00:21 frediag.exe 230405 01/31/95 Tues. 15:00:49

Figure 6-2. Sample Installation Files

Verify that the directory lists the Quick-Start installation ﬁles shown in

Table 6-1 or their equivalents.

Table 6-1. Quick-Start Installation Files

Filename File T ype

ﬁle_name.ex e

ace.out conﬁg debug.al install.bat ti.cfg

Note: Other ﬁles may be in the directory.

(example –

bn.exe

)

The bootable router or BNX platform software image (see Table 6-2)

Conﬁguration ﬁle Alias ﬁle Installation script ﬁle Initial conﬁguration ﬁle

6-3

Quick-Starting Routers and BNX Platforms

Verify that the directory holds the correct softwar e image f or y our router

or BNX platform (Table 6-2).

Table 6-2. Router or BNX Platform Software Images

Router Software

Router

Image Runs On

AFN ASN BLN BCN BNX AN

CN, FN, LN (VME)

If your installation ﬁles or software image are not available, contact the Bay Networks Technical Response Center.

Booting with the ti.cfg File

You initialize the router or BNX platform once with the ti.cfg ﬁle. The ti.cfg ﬁle is a special ﬁle that boots the router or BNX platform without conﬁguration. You then run the installation script to create an initial conﬁguration. Never change the ti.cfg file or overwrite it with another conﬁguration ﬁle.

afn.exe asn.exe bn.exe bn.exe bnx.exe an.exe

ace.out

Memory card Memory card Memory card Memory card Memory Card Memory card and

Flash Single Inline Memory Modules (SIMMs)

Memory card

6-4

(Booting a new router or BNX platform uses the ti.cfg ﬁle by default. Performing this step veriﬁes that you are using the correct conﬁguration ﬁle.)

A normal, successful installation requires booting with the ti.cfg ﬁle only once, but under the following conditions you must reboot again with ti.cfg before running the Quick-Start installation script:

• The router or BNX platform is currently booted from a conﬁguration ﬁle other than ti.cfg.

• You terminate the installation script.

Running the Quick-Start Installation Script

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

To boot the router or BNX platform using the ti.cfg ﬁle:

1. Enter the following command:

boot

<slot_number>:<image_ﬁle> <slot_number>

:ti.cfg

<slot_number>

platform and

identiﬁes where the volume resides on the router or BNX

<image_ﬁle>

is the software image for your router or BNX

platform (refer to Table 6-2).

Example:

boot 2:bn.exe 2:ti.cfg

The router or BNX platform boots and runs through its startup procedure.

2. Establish a new Technician Interface session.

See Chapter 5 for instructions.

Running the Quick-Start Installation Script

After booting the router or BNX platform with the ti.cfg ﬁle and establishing a new Technician Interface session, you are ready to run the Quick-Start installation script (install.bat).

Note: Use install.bat once to conﬁgure the initial interface only. To conﬁgure

other interfaces, use Site Manager, Quick2Conﬁg, or other router management software to create new conﬁgurations, as described in Chapter 11.

6-5

Quick-Starting Routers and BNX Platforms

To run the script:

1. Review Table 6-3 for the commands you use to run the script.

Table 6-3. Quick-Start Installation Script Commands

To Do the Following Action Result

Accept a default value

Repeat a step (for example, if you make a mistake)

Quit out of the Quick-Start installation script

Press Return Your terminal displays default values in

brackets; for example, [E21].

Press Control-c When prompted Terminate script y/n?,

type n. The Technician Interface returns to the beginning of the step so you can reenter the information.

Press Control-c When prompted Terminate script y/n?,

type y. The Quick-Start script terminates and returns to the Technician Interface prompt. Reboot the router or BNX platform using the Quick-Start installation script.

ti.cfg

ﬁle before rerunning the

2. Change to the slot where the router’s memory card resides by entering

<slot_number>

Include the colon (:) after the slot number as part of the command string.

3. Start the script by entering

run install

The Quick-Start installation script begins.

6-6

Running the Quick-Start Installation Script

#### # # # # # #### ##### # # ## ### # # ### # # # # # # ## # # # # # # # # # # # # #### # # # # # # ### # # # # # # ### ## ### # # ##### # # ## # # # # # # # # # # # # # #### # # # # # #### # # # ## # # # # ###

### # # ### ## # # ### ##### # ### ##### # # # # # # # # # # # # # # # # # # # # # ## ### ### # # # ### # # # # # # # # # # # # ##### # # # ### #### ### ## # # ### # # # # # # #

Figure 6-3. Beginning of the Quick-Start Installation

Enter the network information as you are prompted.

Refer to your Network Information Worksheet as you proceed through the script. See Appendix A for a sample script. The script prompts you to enter information for

— The physical connector — IP interface conﬁguration — IP routing protocol — TFTP and FTP default volumes — Telnet (optional) — Site Manager workstation address Many steps in the installation script suggest default values you should accept.

Some steps are optional for your network requirements. The script displays a summary of the newly conﬁgured IP interface

(Figure 6-4), and then prompts you to save the conﬁguration to a ﬁle.

6-7

Quick-Starting Routers and BNX Platforms

Configuration Summary

---------------------

Link Module: QE/NF Connector: 1 Slot: 2 Circuit Name: E21 IP address: 192.168.125.34 IP subnetwork mask: 255.255.255.0 Routing Protocol: RIP Default Rt. Listen: YES TFTP Default Volume: 2: FTP Default Volume: 2: TI TELNET: No

Press [RETURN] to continue:

Figure 6-4. Summary Information for a Quick-Start Installation

6-8

Note: If you terminate the installation script, reboot the router or BNX

platform using the ti.cfg ﬁle before you rerun the Quick-Start installation script.

Save the conﬁguration ﬁle as startup.cfg.

Accept the default name of startup.cfg. You save this initial IP conﬁguration to the ﬁle to maintain a permanent copy. If you do not save the conﬁguration to a ﬁle, you will lose it the next time you reboot the router or BNX platform.

The router or BNX platform then tests the IP interface conﬁguration by “pinging” its own interface. If successful, it prompts you for the IP address of the Site Manager workstation.

6. Enter the IP address of the Site Manager workstation.

The router or BNX platform pings the Site Manager workstation. If the ping is successful, the initial IP interface is enabled and the script displays this message:

Quick-Start Installation Completed

The Technician Interface prompt appears and you have completed the QuickStart procedure. Don’t reboot the router or BNX platform after successfully completing this procedure.

Note: Boot with the ti.cfg ﬁle and run install.bat once to conﬁgure the initial

interface only. To conﬁgure other interfaces, use Site Manager, Quick2Conﬁg, or other router management software to create new conﬁgurations, as described in Chapter 11.

Quick-Start T roubleshooting

If the router or BNX platform cannot ping the Site Manager workstation during the Quick-Start installation:

— Check the physical connections. — If the Site Manager workstation is a PC, Distinct or other networking

software must be running for a successful ping. (See Chapter 7 for Distinct installation instructions.) You can skip the ping test by typing Q and later verify that the PC is communicating with the router.

Running the Quick-Start Installation Script

— Verify the IP address of the router or BNX platform. Use the

circuits command in the Technician Interface to make sure that the

show ip

physical interface is up and that the IP address is correct. For more information about the

show command, refer to Using Technician

Interface Scripts.

— Verify the IP address and subnetwork mask address of the Site Manager

PC or workstation.

— V erify that routing is working, if the w orkstation is on a different netw ork.

Use the show ip routes command in the Technician Interface to examine the routing table and verify that there is a route or a default route to the network where the Site Manager workstation is located. For more information about the

show command, refer to Using Technician

Interface Scripts.

6-9

Quick-Starting Routers and BNX Platforms

Assigning a Password

If you want to assign a security password to the Technician Interface before logging out of the Technician Interface, see Using Technician Interface Software for instructions.

Exiting the Technician Interface

To exit the Technician Interface interface, type logout at the prompt. If you used an ASCII console to establish a Technician Interface session, you can

now disconnect it from the router or BNX platform. If you used terminal emulation to establish a Technician Interface session, select File➔Exit.

After you install Site Manager, you use the Technician Interface primarily as a backup interface if Site Manager becomes unavailable.

6-10

Installing Site Manager on a PC

Use Site Manager to remotely conﬁgure and manage the router or BNX platform over the IP network. You install Site Manager on a PC in this order:

• Review system requirements

• Install Distinct TCP/IP or equivalent WINSOCK-compatible TCP/IP stack

• Load the Site Manager software

• Start up Site Manager

Reviewing System Requirements

Site Manager or Site Manager BNX for the PC requires the following to run:

Chapter 7

• A 386 PC with at least 8 MB of RAM and at least 32 MB of free disk space. (We recommend a 486 PC with at least 8 MB of RAM.)

• A CD-R OM dri ve — if you intend to load the Site Manager softw are from CD rather than disks.

• A VGA monitor. (We recommend a SuperVGA monitor.)

• DOS 5.0 or later.

• Microsoft Windows 3.1 or later.

• A network interface card (NIC) with a driver type of Packet, Network Driver Interface Speciﬁcation (NDIS), or Novell Open Data Link Interface (ODI).

• The supplied Distinct TCP/IP for Microsoft Windows, Version 3.31 or any WINSOCK-compatible TCP/IP stack, including NetManage Chameleon, Novell’s LAN Workplace, and FTP Software’s PC/TCP for Windows.

7-1

Quick-Starting Routers and BNX Platforms

Installing Distinct TCP/IP

Site Manager on the PC uses a WINSOCK-compatible TCP/IP stack to communicate across the IP network. If you already have an installed TCP/IP stack, you can use it with Site Manager. If not, Bay Networks supplies Distinct TCP/IP for Microsoft Windows, a Distinct Corporation application, with Site Manager. Appendix B provides an example of a successful Distinct installation.

You install TCP/IP or its equivalent by

• Preparing information for — Serial number and key code — Network interface card and driver — Network conﬁguration

• Loading the Distinct software

• Testing Distinct

This section provides the general guidelines for installing Distinct TCP/IP. For detailed instructions about the Distinct product, refer to Distinct TCP/IP for Microsoft Windows Run Time Installation and Conﬁguration Guide, the Distinct Corporation documentation supplied with Site Manager. Also check the Bay Networks Read Me First documentation for changes to the installation instructions.

7-2

The use of Distinct’s TCP/IP Run Time software is subject to the Distinct Software License Agreement. Each Distinct License Agreement allows you to install Distinct on up to 15 PCs per IP subnet. We recommend installing and conﬁguring Distinct’s TCP/IP Run Time software successfully on one PC before you install it on additional systems.

Only the Distinct features required for Site Manager — TFTP and Ping — are operational. To obtain a complete version of Distinct, contact the Distinct Corporation at 408-366-8933.

If you use another WINSOCK-compatible TCP/IP stack, consult its documentation for installation requirements. After installation, proceed to the section “Starting Up Site Manager” later in this chapter.

Preparing Information for the Distinct Installation

The Distinct installation prompts you to provide

• Serial number and key-code information

• Network interface card and driver information

• Network conﬁguration information

Preparing Serial Number and Key-Code Information

You must initialize the software at installation time by entering a serial number and a key code. There is a serial number associated with each copy of the softw are licensed. You must use a different serial number for each computer on which you install the software.

Table 7-1. Distinct Serial Numbers and Key Codes

Serial No. Key Code

R00WELLF00 F6-73-F2 R00WELLF01 00-53-46 R00WELLF02 EA-B3-00 R00WELLF03 F4-93-BC R00WELLF04 9E-F3-D5 R00WELLF05 88-D3-1E R00WELLF06 92-33-F1 R00WELLF07 BC-13-60 R00WELLF08 A6-73-20 R00WELLF09 B0-53-E6 R00WELLF10 FF-53-5C R00WELLF11 09-33-43 R00WELLF12 F3-93-73 R00WELLF13 FD-73-37 R00WELLF14 A7-D3-17

Installing Site Manager on a PC

7-3

Quick-Starting Routers and BNX Platforms

Preparing Network Interface Card and Driver Information

The Distinct installation process prompts you for the network interface card installed on your PC, the card driver, and the driver type you want to use. Driver types are

• NDIS

• ODI

• Packet

Normally, driver types NDIS and ODI involve less conﬁguration than the Packet type.

Distinct and other applications include standard card drivers with their software. An incorrect or outdated driver generates an error message such as Bind Failed upon reboot. If this happens, verify from the network interface card documentation that you selected the right card model, driver, and driver type. Try using the driver supplied on disk with the card or contact the card manufacturer (via FTP) for the latest update to the driver.

If Distinct doesn’t support your driver, refer to the section “Configuring the System for Your Own Ethernet or Token Ring Driver” in Chapter 2 of the Distinct TCP/IP for Microsoft Windows manual.

7-4

If you have a laptop PC and are using a Xircom Pocket Ethernet Adapter to fulﬁll the NIC system requirement, we recommend selecting the “NDIS Driver over Ethernet” procedure in Chapter 2 of the Distinct manual.

Depending on your network interface card, you may also be prompted to change information about

• Hardware interrupt

• I/O base address

• Memory address

• Transceiver

Accept the defaults for this information unless you have a reason for making a change.

Preparing Network Conﬁguration Information

Use the worksheet in Table 7-2 to prepare the information Distinct TCP/IP needs to know about the conﬁguration of your network. A minimum network conﬁguration includes

• The gateway to this subnet

• Your host PC

• Any other hosts on this subnet

The installation process prompts you for this conﬁguration information.

Table 7-2. Distinct Conﬁguration Worksheet

Information Default Your Information LAN

System Name Internet Address Subnet Address Default Gateway

Domain

Domain Name Primary Server Alternate Server

Serial

Client Name <none> Server Name <none> Type: SLIP or PPP <not enabled> Compression <disabled> State <disabled> Scripts <none> Com Port (if SLIP or PPP) 1 Parameters (if SLIP or PPP) 9600,N,8,1

Installing Site Manager on a PC

7-5

Quick-Starting Routers and BNX Platforms

Installing the Distinct Software

You can install Distinct software from the Site Manager CD or from a disk.

From CDs

To load Distinct from the Site Manager CD:

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

2. Double-click on the File Manager icon.

3. Click on the CD-ROM drive icon in the File Manager window.

4. Click on the Distinct icon in the top-level directory.

5. Double-click on the setup.exe utility to start the program.

The Distinct installation process prompts you for path and directory information. Accept the def ault suggestions unless you ha ve reason to change.

The process then prompts you for the information you prepared in the previous sections about

• Serial number and key code

7-6

• Network interface card and driver

• Network conﬁguration For speciﬁc questions about the Distinct conﬁguration process, refer to the

Distinct TCP/IP for Microsoft Windows Run Time Installation and Conﬁguration Guide. Also refer to the sample installation in Appendix B.

6. At the end of the Distinct installation, accept the prompt to reboot the

PC.

You reboot the PC to load the TCP/IP stack and set up the environment variables.

7. Enter Windows. The Distinct Group window is open on the desktop.

8. Proceed to the section “Testing Distinct TCP/IP” and test the Distinct

TCP/IP conﬁguration before installing Site Manager.

Installing Site Manager on a PC

From disks

To load Distinct from a disk:

1. Insert the Distinct TCP/IP disk into the disk drive.

2. Select File➔Run.

3. Enter the following in the Command Line box to install the Distinct TCP/

IP Run Time software:

<drive>

setup

<drive> speciﬁes the drive (for example, A or B) in which you inserted the Distinct TCP/IP Run Time disk.

The Distinct installation process prompts you for path and directory information for installing the software. Accept the default suggestions unless you have reason to change.

The process then prompts you for the information you prepared in the previous sections about

• Serial number and key code

• Network interface card and driver

• Network conﬁguration For speciﬁc questions about the Distinct conﬁguration process, refer to the

Distinct TCP/IP for Microsoft Windows Run Time Installation and Conﬁguration Guide. Also refer to the sample installation in Appendix B.

4. At the end of the Distinct installation accept the prompt to reboot the PC.

You reboot the PC to load the TCP/IP stack and set up the environment variables.

5. Enter Windows. The Distinct Group window is open on the desktop.

6. Proceed to the section “Testing Distinct TCP/IP”and test the Distinct

TCP/IP conﬁguration before installing Site Manager.

7-7

Quick-Starting Routers and BNX Platforms

Testing Distinct TCP/IP

Use the Distinct ping function to send an echo request to the router or BNX platform after installing and conﬁguring Distinct TCP/IP. This procedure tests the functionality of your network and your Distinct conﬁguration.

Perform the test as follows:

1. From the Program Manager window, double-click on the Distinct icon.

2. Double-click on the Ping icon.

The Distinct TCP/IP Ping window appears.

3. Select Host in the menu bar.

4. Enter the name or address of the host in the Host box.

5. Click on Select.

6. Select the Start option in the menu bar.

The display indicates the number of requests transmitted and replies received. If both are increasing, your network and your Distinct conﬁguration are functional.

7-8

7. Select the Stop option in the menu bar to terminate the test.

The Distinct TCP/IP Ping window appears.

8. Select Exit in the menu bar.

Distinct TCP/IP must be successfully loaded before installing Site Manager . If the installation is unsuccessful, review Appendix C, “Trouble Shooting,” in Distinct TCP/IP for Microsoft Windows Run Time Installation and Conﬁguration Guide.

Loading the Site Manager Software

After you install Distinct or other Windows Sockets-supported TCP/IP stack, you’re ready to load the Site Manager software.

Note: If your PC uses the IBM Token Ring Adapter driver, you must install

the IBM LAN Support driver package before installing Site Manager.

Caution: If you are reinstalling Site Manager, be aware that the installation

will overwrite the c:\windows\siteman.ini ﬁle. If you are installing multiple versions of Site Manager on the same PC, make a copy of this file and later edit the new ﬁle with the information about the other versions.

Site Manager software is distributed on CDs and disks. The following section describes the installation procedures for both types of media. It assumes that Windows is running.

From CDs:

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

Installing Site Manager on a PC

2. Double-click on the File Manager icon.

3. Click on the CD-ROM drive icon in the File Manager window.

4. Click on the ms_win directory.

5. Double-click on the setup.exe utility.

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

6. Enter the directory in which to install Site Manager, or accept the

default, c:\WF.

The Site Manager ﬁles install in the chosen directory. When the installation completes, the following prompt appears:

Create windows program group/items automatically?

7. To allow Site Manager to automatically create a Windo ws group, click on

Yes.

If you want to manually create a Windows group, click on No. You can manually create a Windows group later as speciﬁed in the section “Creating a Windows Group.” Then proceed to the section “Starting Up Site Manager.”

7-9

Quick-Starting Routers and BNX Platforms

Click on “Yes” at the prompt to start Site Manager.

The following prompt appears:

Do you want to start Site Manager now?

Select Yes to start Site Manager. Select No to return to Windows.

From disks:

Insert the PC Site Manager disk 1 into the disk drive.

2. Select File➔Run.

3. Type the following in the Command Line box to install the Site Manager

software:

<drive>

:\setup

speciﬁes the drive (for example, A or B) in which you inserted the

PC Site Manager disk 1. Install the remaining disks as you are prompted.

Note: The set of disks shipped with Site Manager includes disks with scripts

for the Technician Interface feature. You don’t have to install them until you need them. Refer to Using Technician Interface Scripts for more information.

The Site Manager ﬁles install in the chosen directory . When the installation is complete, the following prompt appears:

Create windows program group/items automatically?

4. To allow Site Manager to automatically create a Windo ws group, click on

Yes.

5. Click on “Yes” at the prompt to start Site Manager.

The following prompt appears:

Do you want to start Site Manager now?

7-10

Select Yes to start Site Manager. Select No to return to Windows.

Creating a Windows Group

The following example sho ws you how to create a sample W indows group for the Site Manager executable software. (You only need to do this if you chose to manually create a Windows program group.)

1. Create a Program Object: a. Select File➔New.

The New Program Object window appears.

b. Select the Program Group option and click on OK.

The Program Group Properties window appears.

c. Enter Site Manager in the Description box.

Installing Site Manager on a PC

d. Enter e. Click on OK.

2. Create a Program Item: a. Select File➔New.

WF in the Group File box.

The Program Item window appears with Program Item selected.

b. Click on OK. c. Enter PC/Site Manager in the Description box. d. Enter c:\WF\wfsm.exe in the Command box. e. Enter c:\WF\config in the Working Directory box. f. Click on OK.

Adding a Well-Known Service for TFTP

If you want to add a well-known service like TFTP, you have to edit the services ﬁle provided with the Distinct or equivalent TCP/IP stack. The services ﬁle provides the post number and type of service.

7-11

Quick-Starting Routers and BNX Platforms

Add a well-known service to the services ﬁle for TFTP as follows:

1. Change to the directory where the services ﬁle resides.

Some protocol stacks store the services ﬁle in the same directory as the protocol software. For Distinct, the services ﬁle resides in the etc directory.

2. At the DOS prompt, type

cd c:\etc

Enter the following command to edit the services ﬁle:

edit services

The services ﬁle appears.

4. Verify that the following lines are present or insert them:

tftp 69/udp snmp 161/udp snmp-trap 162/udp

Press Alt-f to display the File menu, type x to exit, and type y to save the

changes.

Note: All TCP/IP stacks use a services stack. For example, Chameleon uses

\net\netmanag\services. The location of the services stack may vary with your IP package.

Starting Up Site Manager

Start up the Site Manager application from Windows as follows:

1. Select the Site Manager program group.

2. Double-click on the PC/Site Manager icon.

The Site Manager window appears (Figure 7-1). After you have successfully installed and started up Site Manager, proceed to

Chapter 11 to create a pilot conﬁguration ﬁle.

7-12

Installing Site Manager on a PC

Figure 7-1. Site Manager Window

7-13

Chapter 8

Installing Site Manager on a SPARCstation

You use Site Manager to remotely conﬁgure and manage the router or BNX platform over the IP network. You install Site Manager on a SPARCstation in the following order:

• Review system requirements

• Set up the SPARCstation

• Load the Site Manager software

• Add Site Manager user accounts

• Verify Site Manager installation

• Start up Site Manager

Reviewing System Requirements

The SPARCstation Site Manager or Site Manager BNX requires the following to run:

• Sun Microsystems Sun4 SPARCstation equipped with an Ethernet, Token Ring, or FDDI network adapter

• CD-ROM drive

• Sun OpenWindows 3.0 or later, or MIT X11 Window System 4.0 or later

• SunOS 4.1 or later, or Solaris 2.3 or later

• At least 16 MB of RAM; at least 55 MB of free disk space; and at least 32 MB of swap space

8-1

Quick-Starting Routers and BNX Platforms

Setting Up the SPARCstation

Before you load the Site Manager software on your SPARCstation:

1. Log in to the SPARCstation as root (or su root).

2. Edit the /etc/services system ﬁle (on each host device) to include the

following lines at the bottom of the ﬁle:

snmp161/udp snmp-trap162/udp

You can use any text editor to edit the ﬁle. The ﬁrst line associates the service name snmp with UDP Port number 161 on this host device. The second line associates the service name snmp-trap with UDP Port number 162.

3. Save /etc/services, and exit from the text editor.

Loading the Site Manager Software

Load the Site Manager software on the SPARCstation as follows:

1. Insert the Site Manager CD into your CD-ROM drive.

2. If you have not already created a CD-ROM mountpoint, log in as root

and create a root-level directory. For example, enter

mkdir /cdrom

Mount the CD-ROM drive as follows:

Note: On SunOS, enter

mount -r -t hsfs /dev/

<device-number> is the device number assigned to the CD-ROM drive (example – sr0).

Example

mount -r -t hsfs /dev/sr0 /cdrom

On Solaris, enter

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

<device_number> is the device number assigned to the CD-ROM drive (example – c0t6d0s0).

8-2

<device_number>

/cdrom

Installing Site Manager on a SPARCstation

Example

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

Note: If you use Solaris and you are running the vold daemon, the CD-ROM

will automatically mount as /cdrom/release_1000_400 rather than /cdrom.

Change to the CD-ROM mountpoint by entering

cd /cdrom

or, if you use Solaris and are running the vold daemon, by entering

cd /cdrom/release_1000_400

for a router or, for a BNX platform, entering

cd /cdrom/release_600

Run the script to load the Site Manager software by entering

. / INSTALL.SH

Type the command in all uppercase letters. The installation process — Lists the directories that contain enough space to install Site Manager.

You can then specify which directory you want to use. — Executes the Site Manager installation script, WFSM_INSTALL. When the installation is ﬁnished, your workstation displays the message

Site Manager Installation Complete.

Additional messages about your SPARCstation environment may appear.

6. Press Control-d to exit the root account.

Adding Site Manager User Accounts

Set up individual Site Manager users on the SPARCstation as follows:

1. Log in to the user’s account.

Note: For BNX, skip Step 2 because BNX does not support Image Builder.

8-3

Quick-Starting Routers and BNX Platforms

If this is the ﬁrst time you’ve installed Site Manager, create the directory

in which to install the Site Manager’s image builder application by entering

mkdir $HOME/.builder_dir

Edit the user’s account setup ﬁle on C and Bourne shells as follows:

• If you use csh or clones, add the following lines to .cshrc:

Note: For BNX, do not include the last line about BUIDER_DIR.

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

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

ﬁle, then add these new lines immediately after the last

set path line.

8-4

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

.proﬁle:

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

Note: For BNX, do not include the BUILDER_DIR line and the references to

BUILDER_DIR in the last line.

4. Log out of the user’s account.

Repeat Steps 1 through 4 for each user who wants to run Site Manager.

Verifying Site Manager Installation

Verify the Site Manager installation and environment as follows:

1. Log in to the user’s account.

2. Open your windows environment (X Windows or OpenWindows).

3. Verify the Site Manager installation by entering

wfchkinst

After installation is veriﬁed, the workstation displays the message

Installation is complete and correct!

4. Verify the Site Manager environment by entering

wfchkenv

After the environment is veriﬁed, the workstation displays the message

Your environment seems to have been set up correctly.

Installing Site Manager on a SPARCstation

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

Note: If your environment variables are incorrect, you’ll receive an error

message to reset the variables.

Starting Up Site Manager

Start up the Site Manager application as follows:

1. Log in to a user account that has been set up for Site Manager operation.

2. Open your windows environment (X Windows or OpenWindows).

3. Change to the directory where you want to store conﬁguration ﬁles.

The following sample command changes to the directory /home/siteman/conﬁg_ﬁles:

cd /home/siteman/conﬁg_ﬁles

8-5

Quick-Starting Routers and BNX Platforms

Activate Site Manager by entering the following command:

wfsm -a

<router_IP_address >

<router_IP_address> is the IP address of the router or BNX platform’s initial IP network interface you conﬁgured in Chapter 6.

Example

wfsm -a 192.168.125.34 &

The Site Manager window appears (Figure 8-1).

Figure 8-1. Site Manager Window

8-6

Installing Site Manager on a SPARCstation

After you have successfully installed and started up Site Manager, proceed to Chapter 11 to create a pilot conﬁguration ﬁle.

Starting Site Manager from SunNet Manager

To start a Site Manager session on a platform running SunNet Manager:

1. Open a view containing the icon of a router or BNX platform that you

want to conﬁgure using Site Manager.

2. Click on the icon of the router or BNX platform you want to conﬁgure.

3. From the Tools menu, choose Tools, then drag right and choose Site

Manager (Figure 8-2).

The Site Manager window appears.

SunNet Manager Console: baynet

File

View Edit Requests Tools Goto:

SN-192.168.1.0

SN-192.168.2.64

Props...

SN-192.168.7.0

192.1

SN-192.168.1.0

192.168.7.2

Quick Dump Send Request... Send Predefined Set Request Alarm Reports... Tools Glyph State Show Subviews Properties... Connect Change Type...

SN-192.168.6.66

SN-192.32.83.4

SN-192.168.3.64

Add to Node Name DB... RouterMan wf Configuration Manager wf Events Manager wf File Manager wf Site Mgr wf Statistic Manager Telnet

U.3246.1

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

8-7

Quick-Starting Routers and BNX Platforms

Starting Site Manager from OpenView

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

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

1. Change to the /usr/wf directory.

2. Re-execute the Site Manager script by entering

. / WFSM_INSTALL

In the future, follow these steps any time you reinstall OpenView. To start a Site Manager session from the IP Internet window menu bar in

OpenView, follow these steps:

1. Open a view containing the icon of the router or BNX platform that you

want to conﬁgure using Site Manager.

2. Click on the icon of the router or BNX platform you want to conﬁgure.

The IP Internet window opens (Figure 8-3).

8-8

3. Choose Site Manager from the Tools menu, as shown in Figure 8-3.

A list of options available from Site Manager appears.

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 SynOptics Application Failing Resource Display... Mail... Print...

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

Installing Site Manager on a SPARCstation

Help

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

8-9

Chapter 9

Installing Site Manager on an RS/6000

You use Site Manager to remotely conﬁgure and manage the router or BNX platform on an IP network. You install Site Manager on an RS/6000 workstation in the following order:

• Review system requirements

• Load Motif

• Load the Site Manager software

• Add Site Manager user accounts

• Verify Site Manager installation

• Start up Site Manager

Reviewing System Requirements

The RS/6000 Site Manager or Site Manager BNX requires the following to run:

• IBM RISC System/6000 equipped with either an IBM Ethernet High-Performance network adapter or an IBM Token Ring High-Performance network adapter

• IBM AIX Version 3.2.4 or later

• X11 Release 5 or later

Note: When ordering an IBM RS/6000 or an upgrade of the IBM AIX, request

X11 Release 5. Site Manager does not run with earlier versions of X11.

9-1

Quick-Starting Routers and BNX Platforms

• Motif 1.1.4 or later (see the following section, “Loading Motif.”)

•

CD-ROM drive

• 16 MB of RAM (minimum)

• 50 MB of free disk space (minimum)

• 64 MB of swap space (minimum – use 96 MB of swap space with the NetView/6000 application)

Loading Motif

NetVie w/6000 Versions 2.1 and earlier require Motif Version 1.1.4. However , X11 Release 5 typically ships with Motif Version 1.2 as the default. Therefore, if you are using NetView/6000 Version 2.1, and you are running a later version of Motif (such as 1.2), then you must use the instructions that follow to switch the currently installed version of Motif to Motif Version 1.1.4. This allows Site Manager and NetView/6000 Version 2.1 to operate.

Switch to Motif 1.1.4 as follows:

1. Enter the following AIX commands:

9-2

/usr/lpp/X11rte/set_symlinks.Motif1.1

/usr/lpp/X11dev/set_symlinks.Motif1.1

Restart NetView/6000.

To switch back to Motif 1.2:

a. Enter the following AIX commands:

/usr/lpp/X11rte/set_symlinks.Motif1.2 /usr/lpp/X11dev/set_symlinks.Motif1.2

Restart NetView/6000.

Note: The services (network services) directory supplied with the operating

system should be complete. If the snmp or snmp-trap ﬁles are missing, contact your system administrator.

Loading the Site Manager Software

Load the Site Manager software on the RS/6000 as follows:

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

2. If you have not already created a CD-ROM mountpoint, log in as root

and create a root-level directory. For example, enter

mkdir /cdrom

To mount the CD-ROM drive, enter

Installing Site Manager on an RS/6000

mount -o ro -v cdrfs /dev/

<device_number>

/cdrom

<device_number> is the number of the device assigned to the CD-ROM dri v e (Example – cd0).

Example

mount -o ro -v cdrfs /dev/cd0 /cdrom

Change to the CD-ROM mountpoint by entering

cd /cdrom

Run the script to load the Site Manager software by typing

. /install.sh

Type the command in all lowercase letters. The installation process — Lists the directories that contain enough space to install Site Manager.

You can accept the default or specify which directory you want to use. — Executes the Site Manager installation script, WFSM_INSTALL. When the installation is ﬁnished, your workstation displays the message

Site Manager Installation Complete.

6. Press Control-d to exit the root account.

9-3

Quick-Starting Routers and BNX Platforms

Setting Up Site Manager User Accounts

Set up individual Site Manager users on the RS/6000 as follows:

1. Log in to the user’s account.

Note: For BNX, skip Step 2 because BNX does not support Image Builder.

2. Create the directory f or the Site Manager’s image builder application by

entering

mkdir $HOME/.builder_dir

Edit the user’s account setup ﬁle as follows for C and Bourne shells:

• If you use csh or clones, then add the following lines to .cshrc:

Note: For BNX, do not include the last line about BUIDER_DIR.

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

9-4

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

ﬁle, then add these new lines immediately after the last

set path line.

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

.proﬁle:

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

Note: For BNX, do not include the BUILDER_DIR line and the references to

BUILDER_DIR in the last line.

4. Log out of the user’s account.

Repeat Steps 1 through 4 for each user who wants to run Site Manager.

Verifying Site Manager Installation

Verify the Site Manager installation and environment as follows:

1. Log in to the user’s account.

2. Start up the X Windows environment.

3. Verify the Site Manager installation by entering

wfchkinst

After installation is veriﬁed, the workstation displays the message

Installation is complete and correct!

4. Verify the Site Manager environment by entering

wfchkenv

After the environment is veriﬁed, the workstation displays the message

Your environment seems to have been set up correctly.

Installing Site Manager on an RS/6000

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

Starting Up Site Manager

Start up the Site Manager application on an RS/6000 as follows:

1. Log in to a user account that has been set up for Site Manager operation.

2. Start up the X Window environment.

3. Change to a directory where you want to store conﬁguration ﬁles.

Example

The following sample command changes to the directory /home/siteman/conﬁg_ﬁles:

cd /home/siteman/conﬁg_ﬁles

9-5

Quick-Starting Routers and BNX Platforms

Activate Site Manager by entering the following command:

wfsm -a

router_IP_address> is the IP address of the router or BNX platform’s initial

<router_IP_address>

IP network interface. A sample command is as follows:

wfsm -a 192.168.125.34 &

The Site Manager window appears (Figure 9-1). After you have successfully installed and started up Site Manager, proceed to

Chapter 11 to create a pilot conﬁguration.

Figure 9-1. Site Manager Window

9-6

Starting Site Manager from NetView/6000

Read this section if you plan on installing or are currently running the NetView/6000 application on your RS/6000 workstation.

If you install NetView/6000 on your RS/6000 after you install the Site Manager software, follow these steps to integrate Site Manager with the NetView/6000 application:

1. Change to the /usr/wf directory.

2. Re-execute the Site Manager script by entering

. / WFSM_INSTALL

In the future, follow these steps any time you reinstall NetView/6000. To start a Site Manager session from the IP Internet window menu bar in

NetView:

1. Open a view containing the icon of the router or BNX platform that you

want to conﬁgure using Site Manager.

2. The IP Internet window appears with a map of your Internet.

Installing Site Manager on an RS/6000

3. Click on the icon of the router or BNX platform you want to conﬁgure.

4. Choose Site Manager from the Tools menu shown in Figure 9-2.

A list of options available from Site Manager appears.

9-7

Quick-Starting Routers and BNX Platforms

IP Internet

Edit View OptionsLocate

File Monitor Test AdministerTools

Figure 9-2. Starting a Site Manager Session from NetView

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

Help

9-8

Chapter 10

Installing Site Manager on an HP 9000

Use Site Manager to remotely conﬁgure and manage the router on the IP network. You install Site Manager on an HP 9000 workstation in this order:

• Review system requirements

• Load the Site Manager software

• Add Site Manager User Accounts

• Verify Site Manager Installation

• Start up Site Manager

Note: BNX Site Manager does not run on the HP 9000 workstation.

Reviewing System Requirements

The HP 9000 Site Manager requires the following to run:

• HP Precision Architecture System (HP 9000/7xx or HP 9000/8xx) equipped with an Ethernet network adapter or a Token Ring network adapter

• HP-UX 9.01 or later releases

• X11 Release 5 or later

• Motif Version 1.2 or later

• 16 MB of RAM (minimum)

• 65 MB of free disk space (minimum)

10-1

Quick-Starting Routers and BNX Platforms

• 32 MB of swap space (minimum)

• CD-ROM drive

Note: The services (network services) directory supplied with the operating

system should be complete. If the snmp or snmp-trap ﬁles are missing, contact your system administrator.

Loading the Site Manager Software

Load the Site Manager software on the HP 9000 as follows:

1. Insert the Site Manager CD into your CD_ROM drive.

2. If you have not already created a CD-ROM mountpoint, log in as root

and create a root-level directory. For example, enter

mkdir /cdrom

Mount the CD-ROM drive by entering

mount -r -o ro -t cdfs /dev/dsk/

<device_number>

/cdrom

<device_number> is the number of the device assigned to the CD-ROM dri v e (Example –

c201d2s0).

Example

mount -r -o ro -t cdfs /dev/dsk/c201d2s0 /cdrom

Change to the CD-ROM mountpoint by entering

cd /cdrom

Run the script to load the Site Manager software by typing

. / “INSTALL.SH;1”

Type the command in all uppercase letters. The installation process — Lists the directories that contain enough space to install Site Manager.

Accept the default or specify which directory you want to use. — Executes the Site Manager installation script, WFSM_INSTALL. When the installation is ﬁnished, your workstation displays the message:

Site Manager Installation Complete.

10-2

Note: If you get the message OvwDbInit failed, OpenView is not installed.

See the section “Starting Site Manager from OpenView” for information.

6. Press Control-d to exit the root account.

Adding Site Manager User Accounts

Set up individual Site Manager users on the HP 9000 as follows:

1. Log in to the user’s account.

2. Create the directory f or the Site Manager’s image builder application by

entering

mkdir $HOME/.builder_dir

Edit the user’s account setup ﬁle using a C or Bourne shell as follows:

• If you use csh or clones, then add the following 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

Installing Site Manager on an HP 9000

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

ﬁle, then add these new lines immediately after the last

set path line.

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

.proﬁle:

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’s account.

Repeat Steps 1 through 4 for each user who wants to run the Site Manager application.

10-3

Quick-Starting Routers and BNX Platforms

Verifying Site Manager Installation

Verify the Site Manager installation and environment as follows:

1. Log in to the user’s account.

2. If it is not already started, start up the HP VUE or X Window

environment.

3. Verify the Site Manager installation by entering

wfchkinst

After installation is veriﬁed, the workstation displays the message

Installation is complete and correct!

4. Verify the Site Manager environment by entering

wfchkenv

After the environment is veriﬁed, the workstation displays the message

Your environment seems to have been set up correctly.

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

Starting Up Site Manager

Start up the Site Manager application as follows:

1. Log in to a user account that has been set up for Site Manager operation.

2. If it is not already started, start up the HP VUE or X Window

environment.

3. Change to a directory in which you want to store conﬁguration ﬁles.

Example

The following command changes to the directory /home/siteman/conﬁg_ﬁles:

cd /home/siteman/conﬁg_ﬁles

Activate Site Manager by entering the following command:

wfsm -a

<router_IP_address> is the IP address of the router’s initial IP network interface, which you conﬁgured in Chapter 6.

10-4

<router_IP_address >

Installing Site Manager on an HP 9000

Example

wfsm -a 192.168.125.34 &

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

After you have successfully installed and started up Site Manager, proceed to Chapter 11 to create a pilot conﬁguration.

Figure 10-1. Site Manager Window

10-5

Quick-Starting Routers and BNX Platforms

Starting Site Manager from OpenView

Read this section if you run the HP OpenView application on your HP 9000 workstation.

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

1. Change to the /usr/wf directory.

2. Re-execute the Site Manager script by entering

. / WFSM_INSTALL

In the future, follow these steps any time you reinstall OpenView. To start a Site Manager session from the IP Internet window menu bar in

OpenView:

1. Open a view containing the icon of the router that you want to conﬁgure

using Site Manager.

2. Click on the icon of the router you want to conﬁgure.

The IP Internet window opens (Figure 10-2).

10-6

3. Choose Site Manager from the Tools menu, as shown in Figure 10-2.

A list of options available from Site Manager appears.

IP Internet

)...

Edit View OptionsLocate

File Monitor Test AdministerTools

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

Installing Site Manager on an HP 9000

Help

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

10-7

Chapter 11

Creating a Pilot Conﬁguration File

In this chapter you use Site Manager to create a second IP interface on a router or BNX platform and save it as a new conﬁguration ﬁle, pilot.cfg. In the process of creating this simple pilot conﬁguration you learn to use several Site Manager conﬁguration features.

You use Site Manager to create a pilot conﬁguration for the router or BNX platform in this order:

• Connect to the router or BNX platform

• Use remote mode to create a conﬁguration ﬁle

• Conﬁgure the pilot IP interface — Add a circuit on a connector — Enable the IP protocol — Save the pilot conﬁguration ﬁle — Reboot the router or BNX platform with the pilot conﬁguration ﬁle — Enhance the pilot conﬁguration ﬁle

11-1

Quick-Starting Routers and BNX Platforms

This chapter also introduces how to secure the router or BNX platform by

• Restricting read/write access

• Setting the router or BNX platform to Secure mode

Note: Accept the Site Manager default parameter settings as you create this

pilot conﬁguration ﬁle. Later, you can edit the parameters to meet your speciﬁc network needs using the instructions in Conﬁguring Routers or Conﬁguring Customer Access and Trunks (BNX Software) and in the protocol conﬁguration manuals.

All examples in this chapter reﬂect the sample pilot conﬁguration shown in Figure 11-1. Circuit E21 with IP Address 192.168.125.34 is the initial interface created with the Technician Interface. Circuit E22 with an IP address of

192.1.182.1 is the pilot IP interface you’ll create with Site Manager . The router or

BNX platform in Figure 11-1 contains a single memory card (volume), located in Slot 2.

11-2

Creating a Pilot Configuration File

IP Address =

192.32.10.12

Corporate IP network

IP Address =

192.168.125.34

Interface E22

E21

Router or BNX platform

E22

IP Configuration Information IP Address = 192.1.182.1

Subnet Mask = 255.255.255.0 Broadcast Address = 192.1.182.255

Figure 11-1. Sample Pilot Conﬁguration

Site Manager workstation

IP Address =

192.1.182.2

IP workstation

11-3

Quick-Starting Routers and BNX Platforms

Connecting to the Router or BNX Platform

After you install Site Manager on your workstation, the initial Site Manager window appears (Figure 11-2). You select many of the major Site Manager menus and features from this screen.

The Site Manager window displays the IP address of the interface and system record information. To edit the system information, select the Platform ➔Edit System Information option (see Conﬁguring Routers or Conﬁguring Customer Access and Trunks (BNX Software) for details).

Figure 11-2. Site Manager Window

11-4

When you are managing additional routers or BNX platforms from this workstation, you can connect to them from the initial Site Manager window by selecting Options➔Router Connections (see Conﬁguring Routers or Conﬁguring Customer Access and Trunks (BNX Software) for more information).

Using Remote Mode

Site Manager offers three operating modes for conﬁguring the router or BNX platform: remote, local, and dynamic. For the pilot conﬁguration, use remote mode.

1. Select Tools➔Conﬁguration Manager➔Remote File.

The Edit Remote Conﬁguration File window appears (Figure 11-3). Site Manager retrieves the ﬁle information from the router and displays it in this window. The Volume button on the right side of the screen identiﬁes the volume on which the conﬁguration ﬁle will be stored.

Creating a Pilot Configuration File

Figure 11-3. Naming the Conﬁguration File

11-5

Quick-Starting Routers and BNX Platforms

Usually, the volume is the number of the slot containing the memory card (except LNs and CNs that have two cards on a slot, or DOS drives). To access other memory cards residing in different slots:

a. Select the button showing the current volume and hold the mouse

button down.

A menu displays the NVFS volumes.

b. Select the slot of the volume that you want and release the mouse

button.

The volume you selected appears. In a DOS ﬁle system, the default volume is A.

2. Select your initial conﬁguration ﬁle, startup.cfg, and click on Open.

If you named the initial conﬁguration ﬁle something other than startup.cfg, select that ﬁle instead.

In remote mode, Site Manager queries the router or BNX platform and displays its hardware conﬁguration in the Conﬁguration Manager window (Figure 11-4).

Figure 11-4. Conﬁguration Manager Window

11-6

The router or BNX platform model determines the number of slots in the window. Figure 11-4 shows 5 slots because the example is for a BLN. The window numbers each slot and identiﬁes the module in each slot as well as the type and position of the connectors (or ports) on the module.

Note: The position of the slot numbers in the Conﬁguration Manager window

corresponds to that in the router or BNX platform. For the ASN, the module numbering in the Conﬁguration Manager window repr esents that on the r outer or BNX platform. In the ASN, modules are the locations where the net modules reside.

Conﬁguring the Pilot IP Interface

Next, conﬁgure a pilot IP interface for the router or BNX platform as follows:

— Add a circuit on a connector — Enable the IP protocol — Save the pilot conﬁguration ﬁle — Reboot with the pilot conﬁguration ﬁle

Creating a Pilot Configuration File

— Enhance the pilot conﬁguration ﬁle

Adding a Circuit on a Connector

1. Select the Circuits➔Add Circuit option from the Conﬁguration Manager

window (refer to Figure 11-4).

The Add Circuit window appears (Figure 11-5). This window displays the connectors for each link module or net module installed in the router or BNX platform. The model determines the number of slots (or in the case of the ASN, the number of modules) shown in the window. Figure 11-5 shows 5 slots for a BLN.

11-7

Quick-Starting Routers and BNX Platforms

Figure 11-5. Add Circuit Window

11-8

Click on one of the available connectors.

After you click on a connector, Site Manager names the circuit that interfaces with this connector in the Circuit Name box. The default circuit name identiﬁes the type of circuit and the location of the connector (Figure 11-6).

Creating a Pilot Configuration File

Type of circuit (E = Ethernet)

Circuit Name:

Slot (or ASN module)

where connector resides

E22

Connector position on link module

or net module

Figure 11-6. Site Manager Default Circuit Name

Note: We recommend that you follow the default circuit-naming conventions,

so that circuit types and locations are represented consistently.

Table 11-1 lists the default circuit types.

Table 11-1. Circuit-type Designators in Default Circuit Names

Letter Designator Connector Type

AATM E Ethernet E1 E1 F FDDI H HSSI MCE1 MCE1 MCT1 MCT1 O Token Ring S Synchronous T1 T1

11-9

Quick-Starting Routers and BNX Platforms

If you choose not to follow the conventions, enter a circuit name. Circuit names have a 15-character limit and must consist of alphabetical, numeric, underline, and slash characters. Do not enter spaces in circuit names. Circuit names are case-sensitive.

3. Click on OK to save the circuit.

You must save each circuit after you associate it with a connector. If the link module or net module has hardware ﬁlters, the following message

appears:

circuit? Click on OK to enable hardware filters. Otherwise, click on

Do you want to enable Hardware Filters on this

Cancel.

Enabling the IP Protocol

After you save the circuit, Site Manager displays the Select Protocols window (Figure 11-7). You enable the circuit with bridging and routing protocols from this window.

Note: The Select Protocols window differs slightly, depending on the circuit

type. If appropriate, you may be prompted to select a WAN protocol. See

Conﬁguring Routers or Conﬁguring Customer Access and Trunks (BNX Software) for more information.

11-10

Creating a Pilot Configuration File

Figure 11-7. Select IP in the Protocols Window

Select the IP option and click on OK.

The IP Conﬁguration window appears (Figure 11-8).

Figure 11-8. IP Conﬁguration Window

11-11

Quick-Starting Routers and BNX Platforms

Enter the following information for the new IP interface:

— IP Address (Example – 191.1.182.1) — Subnet Mask (Example – 255.255.255.0) — Transmit Broadcast Address (Accepting the default of 0.0.0.0 calculates

the actual address)

You can ignore the Unnumbered Associated Address parameter for now (see

Conﬁguring Routers or Conﬁguring Customer Access and Trunks (BNX Software) for information).

3. Click on OK.

The Conﬁguration Manager (Figure 11-4) appears again with the connector box highlighted to indicate that the circuit has been conﬁgured. Later, when you create a complete conﬁguration ﬁle, you add circuits and select protocols for all circuits on the router or BNX platform.

Saving the Pilot Conﬁguration File

From the Conﬁguration Manager window, you save the conﬁguration you just created to a ﬁle.

11-12

Note: Site Manager does not create a conﬁguration ﬁle until you save the

conﬁguration information you speciﬁed.

Creating a Pilot Configuration File

1. Select the File➔Save As option.

The Save Conﬁguration File window appears (Figure 11-9). This window displays the name startup.cfg —which is the ﬁle you retrieved earlier in the procedure.

Figure 11-9. Save Conﬁguration File Window

Delete the text displayed in the Enter ﬁle name box.

3. Enter the name pilot.cfg, then click on Save.

Site Manager generates a conﬁguration ﬁle, transfers it to the router or BNX platform (via TFTP), and saves it to the file system with the name pilot.cfg. Site Manager stores the ﬁle remotely on the router or BNX platform, because Site Manager is operating in Remote mode.

4. Click on OK when the File Saved pop-up window appears.

5. Select the File➔Exit option to exit the Conﬁguration Manager window.

You are returned to the initial Site Manager window.

Rebooting with the Pilot Conﬁguration File

After you save the pilot conﬁguration ﬁle, implement the conﬁguration by rebooting the router or BNX platform.

To reboot the router or BNX platform, from the Site Manager window (refer to Figure 11-2):

1. Select Administration➔Boot Router.

11-13

Quick-Starting Routers and BNX Platforms

The Boot Router window appears (Figure 11-10). The default volume is displayed next to the boot image ﬁle (example: bn.exe) and conﬁguration ﬁle (conﬁg). The default volume is the ﬁrst available NVFS (indicated by slot number) or it is the DOS ﬁle system (indicated by the disk drive designator A). If your boot or conﬁguration ﬁle is located on a different volume, you can click on the volume number to change it.

Figure 11-10. Sample Boot Router Window

Replace the text displayed in the Conﬁguration box with the name of

your conﬁguration ﬁle, pilot.cfg.

11-14

3. Click on Boot.

You’ll receive a conﬁrmation asking if you want to proceed with the boot.

4. Click on OK.

Note: The software image and conﬁguration ﬁle revert to their respective

default volumes and ﬁlenames (example: bn.exe and conﬁg) after every boot unless you specify a different conﬁguration ﬁle when you boot. To change the default conﬁguration ﬁle to use your newly created ﬁle, use the Copy option to back up conﬁg, the old default ﬁle, to a new ﬁlename. Then use the Copy option again to overwrite the original conﬁg file with the new pilot.cfg file.

Once you have successfully rebooted the router or BNX platform with the pilot conﬁguration, the Quick-Start procedure is complete. The router or BNX platform is now operating on the network with two IP interfaces conﬁgured.

Avaya Quick-Starting Routers and BNX Platforms User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

About This Guide

Audience

Before Y ou Begin

Bay Networks Customer Support

CompuServe

InfoFACTS

W orld Wide Web

How to Get Help

Conventions

Ordering Bay Networks Publications

Acronyms

Connecting a PC

Connecting an ASCII Console

Reviewing the Installation Files

Booting with the ti.cfg File

Running the Quick-Start Installation Script

Quick-Start T roubleshooting

Assigning a Password

Exiting the Technician Interface

Reviewing System Requirements

Installing Distinct TCP/IP

Preparing Serial Number and Key-Code Information

Installing the Distinct Software

Testing Distinct TCP/IP

Loading the Site Manager Software

Creating a Windows Group

Adding a Well-Known Service for TFTP

Starting Up Site Manager

Reviewing System Requirements

Setting Up the SPARCstation

Loading the Site Manager Software

Adding Site Manager User Accounts

Verifying Site Manager Installation

Starting Up Site Manager

Starting Site Manager from SunNet Manager

Starting Site Manager from OpenView

Reviewing System Requirements

Loading Motif

Loading the Site Manager Software

Setting Up Site Manager User Accounts

Verifying Site Manager Installation

Starting Up Site Manager

Starting Site Manager from NetView/6000

Reviewing System Requirements

Loading the Site Manager Software

Adding Site Manager User Accounts

Verifying Site Manager Installation

Starting Up Site Manager

Starting Site Manager from OpenView

Connecting to the Router or BNX Platform

Using Remote Mode

Adding a Circuit on a Connector

Enabling the IP Protocol