Bay Technical Associates BayStack ARN Routers none User Manual

Page 1
Installing and Operating BayStack ARN Routers
Router Software Version 11.00 Rev. 4n Site Manager Software Version 5.00 Rev. 4n
Part No. 114200 Rev. A November 1996
Page 2
4401 Great America Parkway 8 Federal Street Santa Clara, CA 95054 Billerica, MA 01821
Copyright © 1988–1996 Bay Networks, Inc.
All rights reserved. Printed in the USA. November 1996. The information in this document is subject to change without notice. The statements, configurations, technical data,
and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty . Users must take full responsibility for their applications of an y products specified in this document. The information in this document is proprietary to Bay Networks, Inc.
The software described in this document is furnished under a license agreement and may only be used in accordance with the terms of that license. A summary of the Software License is included in this document.
Restricted Rights Legend
Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.
Notice for All Other Executive Agencies
Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.
Trademarks of Bay Networks, Inc.
ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FN, FRE, GAME, LN, Optivity, PPX, SynOptics, SynOptics Communications, Wellfleet and the Wellfleet logo are registered trademarks and ANH, ARN, ASN, Bay•SIS, BayStack, BCNX, BLNX, EZ Install, EZ Internetwork, EZ LAN, PathMan, PhonePlus, Quick2Config, RouterMan, SPEX, Bay Networks, Bay Networks Press, the Bay Networks logo and the SynOptics logo are trademarks of Bay Networks, Inc.
Third-Party T rademarks
All other trademarks and registered trademarks are the property of their respective owners.
Statement of Conditions
In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the right to make changes to the products described in this document without notice.
Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein.
Portions of the code in this software product are Copyright © 1988, Regents of the Univ ersity of California. All rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that such portions of the software were developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from such portions of the software without specific prior written permission.
SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
In addition, the program and information 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).
ii
114200 Rev. A
Page 3
USA Requirements Only
Federal Communications Commission (FCC) Compliance Notice: Radio Frequency Notice
This equipment generates, uses, and can radiate radio-frequency energy. If you do not install and use this equipment according to the instruction manual, this product may interfere with radio communications. This product has been tested and found to comply with the limits for a Class A computing device, pursuant to Subpart J of Part 15 of FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Operating this equipment in a residential area is likely to interfere with radio communications; in which case, the user, at his/her own expense, must correct the interference.
Shielded-compliant cables must be used with this unit to ensure compliance with the Class A limits.
European Requirements Only
EN 55 022 Declaration of Conformance
This is to certify that the Bay Networks products in this book are shielded against the generation of radio interference in accordance with the application of Council Directive 89/336/EEC, Article 4a. Conformity is declared by the application of EN 55 022:1987 Class A (CISPR 22:1985/BS 6527:1988).
This is a Class A product. In a domestic en vironment this product may cause radio interference in which case the user may be required to take adequate measures.
EN 55 022 Declaration of Conformance
This is to certify that the Bay Networks products in this book are shielded against the generation of radio interference in accordance with the application of Council Directive 89/336/EEC, Article 4a. Conformity is declared by the application of EN 55 022:1987 Class B (CISPR 22:1985/BS 6527:1988).
114200 Rev. A
iii
Page 4
Japan/Nippon Requirements Only
Voluntary Control Council for Interference (VCCI) Statement
Voluntary Control Council for Interference (VCCI) Statement
This equipment is in the 1st category (information equipment to be used in commercial and/or industrial areas) and conforms to the standards set by the Voluntary Control Council for Interference by Data Processing Equipment and Electronic Office Machines that are aimed at preventing radio interference in commercial and/or industrial areas.
Consequently, when this equipment is used in a residential area or in an adjacent area thereto, radio interference may be caused to equipment such as radios and TV receivers.
Compliance with the applicable regulations is dependent upon the use of shielded cables. The user is responsible for procuring the appropriate cables. Read instructions for correct handling.
iv
114200 Rev. A
Page 5
Canada Requirements Only
Canada CS-03 Rules and Regulations
Note:
The Canadian Department of Communications label identifies certified equipment. The certification means that the equipment meets certain telecommunications network protective operations and safety requirements. The Department does not guarantee the equipment will operate to the user's satisfaction.
Before installing this equipment, users should ensure that it is permissible to be connected to the facilities of the local telecommunications company. The equipment must also be installed using an acceptable method of connection. In some cases, the company's inside wiring associated with a single line individual service may be extended by means of a certified connector assembly (telephone extension cord). The customer should be aware that compliance with the above conditions may not prevent the degradation of service in some situations.
Repairs to certified equipment should be made by an authorized Canadian maintenance facility designated by the supplier. Any repairs or alterations made by the user to this equipment or equipment malfunctions, may give the telecommunications company cause to request the user to disconnect the equipment.
Users should ensure for their own protection that the electrical ground connections of the power utility, telephone lines and internal metallic water pipe system, if present, are connected together. This precaution may be particularly important in rural areas.
Caution:
inspection authority, or electrician, as appropriate.
Canada CS-03 -- Règles et règlements
Note:
qu’il respecte certaines exigences de sécurité et de fonctionnement visant les réseaux de télécommunications. Le ministère ne garantit pas que l’appareillage fonctionnera à la satisfaction de l’utilisateur.
Avant d’installer l’appareillage, s’assurer qu’il peut être branché aux installations du service de télécommunications local. L’appareillage doit aussi être raccordé selon des méthodes acceptées. Dans certains cas, le câblage interne du service de télécommunications utilisé pour une ligne individuelle peut être allongé au moyen d’un connecteur certifié (prolongateur téléphonique). Le client doit toutefois prendre note qu’une telle installation n’assure pas un service parfait en tout temps.
Les réparations de l’appareillage certifié devraient être confiées à un service d’entretien canadien désigné par le fournisseur. En cas de réparation ou de modification effectuées par l’utilisateur ou de mauvais fonctionnement de l’appareillage, le service de télécommunications peut demander le débranchment de l’appareillage.
Pour leur propre sécurité, les utilisateurs devraient s’assurer que les mises à la terre des lignes de distribution d’électricité, des lignes téléphoniques et de la tuyauterie métallique interne sont raccordées ensemble. Cette mesure de sécurité est particulièrement importante en milieu rural.
Attention:
aux pouvoirs de réglementation en cause ou à un électricien, selon le cas.
Users should not attempt to make such connections themselves, but should contact the appropriate electric
L’étiquette du ministère des Communications du Canada indique que l’appareillage est certifié, c’est-à-dire
Les utilisateurs ne doivent pas procéder à ces raccordements eux-mêmes mais doivent plutôt faire appel
114200 Rev. A
v
Page 6
Canada Requirements Only
(continued)
D. O. C. Explanatory Notes: Equipment Attachment Limitations
The Canadian Department of Communications label identifies certified equipment. This certification meets certain telecommunication network protective, operational and safety requirements. The department does not guarantee the equipment will operate to the users satisfaction.
Before installing the equipment, users should ensure that it is permissible to be connected to the facilities of the local telecommunications company. The equipment must also be installed using an acceptable method of connection. In some cases, the company’s inside wiring associated with a single line indi vidual service may be e xtended by means of a certified connector assembly (telephone extension cord). The customer should be aware that compliance with the above condition may not prevent degradation of service in some situations.
Repairs to certified equipment should be made by an authorized Canadian maintenance facility designated by the supplier. Any repairs or alterations made by the user to this equipment, or equipment malfunctions, may give the telecommunications company cause to request the user to disconnect the equipment.
Users should ensure for their own protection that the electrical ground connections of the power utility, telephone lines and internal metallic water pipe system, if present, are connected together. This precaution may be particularly important in rural areas.
Caution:
inspection authority, or electrician, as appropriate.
Users should not attempt to make such connections themselves, but should contact the appropriate electrical
Notes explicatives du ministère des Communications: limites visant les accessoires
L’étiquette du ministère des Communications du Canada indique que l’appareillage est certifié, c’est-à-dire qu’il respecte certaines exigences de sécurité et de fonctionnement visant les réseaux de télécommunications. Le ministère ne garantit pas que l’appareillage fonctionnera à la satisfaction de l’utilisateur.
Avant d’installer l’appareillage, s’assurer qu’il peut être branché aux installations du service de télécommunications local. L’appareillage doit aussi être raccordé selon des méthodes acceptées. Dans certains cas, le câblage interne du service de télécommunications utilisé pour une ligne individuelle peut être allongé au moyen d’un connecteur certifié (prolongateur téléphonique). Le client doit toutefois prendre note qu’une telle installation n’assure pas un service parfait en tout temps.
Les réparations de l’appareillage certifié devraient être confiées à un service d’entretien canadien désigné par le fournisseur. En cas de réparation ou de modification effectuées par l’utilisateur ou de mauvais fonctionnement de l’appareillage, le service de télécommunications peut demander le débranchment de l’appareillage.
Pour leur propre sécurité, les utilisateurs devraient s’assurer que les mises à la terre des lignes de distribution d’électricité, des lignes téléphoniques et de la tuyauterie métallique interne sont raccordées ensemble. Cette mesure de sécurité est particulièrement importante en milieu rural.
Attention:
aux pouvoirs de réglementation en cause ou à un électricien, selon le cas.
Les utilisateurs ne doivent pas procéder à ces raccordements eux-mêmes mais doivent plutôt faire appel
vi
114200 Rev. A
Page 7
Canada Requirements Only
(continued)
Canadian Department of Communications Radio Interference Regulations
This digital apparatus (Access Feeder Node, Access Link Node, Access Node, Access Stack Node, Backbone Concentrator Node, Backbone Concentrator Node Switch, Backbone Link Node, Backbone Link Node Switch, Concentrator Node, Feeder Node, Link Node) does not exceed the Class A limits for radio-noise emissions from digital apparatus as set out in the Radio Interference Regulations of the Canadian Department of Communications.
Réglement sur le brouillage radioélectrique du ministère des Communications
Cet appareil numérique (Access Feeder Node, Access Link Node, Access Node, Access Stack Node, Backbone Concentrator Node, Backbone Concentrator Node Switch, Backbone Link Node, Backbone Link Node Switch, Concentrator Node, Feeder Node, Link Node) respecte les limites de bruits radioélectriques visant les appareils numériques de classe A prescrites dans le Réglement sur le brouillage radioélectrique du ministère des Communications du Canada.
114200 Rev. A
vii
Page 8
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 specified 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 firmware) for safekeeping (archives) or backup purposes.
4. Licensee may modify Software (but not firmware), 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 affixed to any Software and shall reproduce and affix such notice on any backup copy of Software or copies of software resulting from modification or combination performed by licensee as permitted by this license.
viii
114200 Rev. A
Page 9
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 specified 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)
114200 Rev. A
ix
Page 10
Page 11

Contents

About This Guide
Before You Begin .............................................................................................................xxi
Conventions .....................................................................................................................xxi
Acronyms ........................................................................................................................xxii
Ordering Bay Networks Publications .............................................................................xxiv
Technical Support and Online Services
Bay Networks Customer Service ...................................................................................xxvi
Bay Networks Information Services ..............................................................................xxvii
World Wide Web .....................................................................................................xxvii
Customer Service FTP ...........................................................................................xxvii
Support Source CD ............................................................................................... xxviii
CompuServe ......................................................................................................... xxviii
InfoFACTS ...............................................................................................................xxix
How to Get Help ......................................................................................................xxix
Chapter 1 Installing the BayStack Advanced Remote Node
Preparing to Install the ARN ...........................................................................................1-2
Verifying Shipment Contents ....................................................................................1-2
Supplying Equipment ...............................................................................................1-4
Cables ................................................................................................................1-4
Service Console ................................................................................................1-4
Mounting Hardware ...........................................................................................1-4
Verifying Site Requirements .....................................................................................1-5
Installing the ARN ...........................................................................................................1-5
Positioning the ARN on a Flat Surface .....................................................................1-5
Rack-Mounting the ARN ..........................................................................................1-6
Understanding the ARN Module Locations ....................................................................1-9
Connecting Communications Cables ...........................................................................1-10
114200 Rev. A
xi
Page 12
Connecting to an Ethernet Interface ......................................................................1-10
Connecting to an AUI Interface ........................................................................1-11
Connecting to a 10Base-T Interface ................................................................1-12
Connecting to a Token Ring Interface ....................................................................1-13
Connecting to an STP Token Ring Interface ....................................................1-13
Connecting to a UTP Token Ring Interface ......................................................1-14
Connecting to a Serial Interface .............................................................................1-15
Connecting to an ISDN Interface ...........................................................................1-17
Connecting to a DSU/CSU Interface ......................................................................1-18
Connecting to a V.34 Modem Interface ..................................................................1-19
Connecting a Management Console ............................................................................1-20
Connecting a Terminal Console .............................................................................1-21
Connecting a PC Console ......................................................................................1-22
Connecting a Modem ...................................................................................................1-24
Connecting to the Back-Panel Modem Port ...........................................................1-24
Connecting to a V.34 Modem Module ....................................................................1-26
Connecting the Power Cable ........................................................................................1-27
Installing the Flash Memory Card .................................................................................1-28
Where to Go Next .........................................................................................................1-29
Chapter 2 Starting the ARN
Software Installation .......................................................................................................2-1
Understanding the ARN Boot Options ............................................................................2-2
Starting the ARN for the First Time .................................................................................2-4
Using EZ-Install ..............................................................................................................2-5
Using Netboot, Directed Netboot, or Local Boot .............................................................2-6
Interrupting the Boot Process ..................................................................................2-6
Logging in to the Command Line Software ..............................................................2-7
Continuing with Netboot ...........................................................................................2-8
Continuing with Directed Netboot ...........................................................................2-11
Continuing with Local Boot (the Quick-Start Procedure) .......................................2-15
Where to Go Next .........................................................................................................2-17
xii
114200 Rev. A
Page 13
Chapter 3 Operating the ARN
LED Descriptions ............................................................................................................3-2
Base Module LEDs ..................................................................................................3-2
Diagnostic LEDs ................................................................................................3-2
Ethernet LEDs ...................................................................................................3-4
Token Ring LEDs ...............................................................................................3-4
Expansion Module LEDs ..........................................................................................3-5
Ethernet LEDs ...................................................................................................3-5
Token Ring LEDs ...............................................................................................3-5
Serial LEDs ........................................................................................................3-6
Adapter Module LEDs ..............................................................................................3-6
Serial LED .........................................................................................................3-6
ISDN BRI LEDs (S/T or U Interfaces) ................................................................3-7
DSU/CSU LEDs .................................................................................................3-7
V.34 Modem LEDs .............................................................................................3-8
Back-Panel LEDs .....................................................................................................3-8
Ensuring a Successful Installation ..................................................................................3-9
Powering On and Off the ARN ......................................................................................3-10
Resetting the ARN ........................................................................................................3-11
Removing a Flash Memory Card ..................................................................................3-12
Protecting Memory Card Files ......................................................................................3-13
Where to Go Next .........................................................................................................3-14
Appendix A Configuring the ARN for Netboot and Directed Netboot
Using the ifconfig Command ......................................................................................... A-1
Configuring an IP Serial or DSU/CSU Interface for Netbooting .............................. A-2
Configuring an Ethernet Interface for Network Booting ........................................... A-4
Configuring a Token Ring Interface for Network Booting ......................................... A-5
Enabling and Disabling Interfaces with ifconfig ....................................................... A-6
ifconfig Command Examples .................................................................................. A-6
Using the bconfig Command ......................................................................................... A-7
bconfig Command Format ....................................................................................... A-7
bconfig Command Examples .................................................................................. A-8
V erifying Y our Configuration ........................................................................................... A-8
114200 Rev. A
xiii
Page 14
Appendix B Using Local Boot (the Quick-Start Procedure)
Understanding Quick-Start Connector Names and Numbers ........................................ B-2
Filling Out the Worksheets ............................................................................................. B-3
Global Information Worksheet ................................................................................. B-4
Router Protocol Worksheets ................................................................................... B-7
Wide Area Protocol Worksheets ........................................................................... B-11
Running the Quick-Start Script .................................................................................... B-15
Appendix C Technical Specifications
Physical Specifications .................................................................................................. C-1
Electrical Specifications .................................................................................................C-2
Environmental Specifications ........................................................................................C-2
Hardware Communications Options ..............................................................................C-3
Ethernet Attachment Unit Interface (AUI) ................................................................C-5
Ethernet 10Base-T Interface ................................................................................... C-6
Token Ring STP Interface ....................................................................................... C-7
Token Ring UTP Interface ....................................................................................... C-8
Serial Interfaces ...................................................................................................... C-8
ISDN BRI U Interface ............................................................................................ C-10
ISDN BRI S/T Interface ......................................................................................... C-11
56/64K DSU/CSU Interface ...................................................................................C-12
RJ-11 Interface (for V.34 Modem) ......................................................................... C-13
Local Console Connections ..................................................................................C-13
Service Modem Connections ................................................................................ C-14
Appendix D Requirements for European Operation
ARN Ethernet Base Model Safety Status ...................................................................... D-1
ARN Token Ring Base Model Safety Status .................................................................. D-2
ARN Expansion Modules Safety Status ........................................................................ D-2
Synchronous Cabling Requirements ............................................................................. D-3
Serial Adapter Module Requirements ............................................................................D-7
ISDN BRI Adapter Module Requirements ..................................................................... D-8
xiv
114200 Rev. A
Page 15
Power Requirements for ISDN BRI and Serial Adapter Modules ..................................D-9
Clearance and Creepage Distances for ISDN BRI and Serial Adapter Modules ..........D-9
Index
114200 Rev. A
xv
Page 16
Page 17

Figures

Figure 1-1. Accessories in the ARN Shipping Container ...........................................1-3
Figure 1-2. Attaching Flange Brackets to Rack-Mount the ARN ................................1-7
Figure 1-3. Installing the ARN in an Electronic Enclosure Rack ................................1-8
Figure 1-4. ARN Module Locations ............................................................................1-9
Figure 1-5. Connecting an AUI Cable .......................................................................1-11
Figure 1-6. Connecting a 10Base-T Ethernet Cable ................................................1-12
Figure 1-7. Connecting a Token Ring STP Cable .....................................................1-13
Figure 1-8. Connecting Token Ring UTP Cables ......................................................1-14
Figure 1-9. Connecting Serial Cables to an Expansion Module ...............................1-15
Figure 1-10. Connecting a Serial Cable to a Serial Adapter Module .........................1-16
Figure 1-11. Connecting an ISDN BRI Cable .............................................................1-17
Figure 1-12. Connecting a DSU/CSU Cable ..............................................................1-18
Figure 1-13. Connecting an RJ-11Cable ....................................................................1-20
Figure 1-14. Attaching the Null Modem Adapter ........................................................1-21
Figure 1-15. Connecting a Terminal Console to an ARN ...........................................1-22
Figure 1-16. Connecting a PC Console to an ARN ....................................................1-23
Figure 1-17. Connecting a Modem to an ARN ...........................................................1-25
Figure 1-18. Connecting the Power Cable .................................................................1-27
Figure 1-19. Flash Memory Card ...............................................................................1-28
Figure 1-20. Inserting the Flash Memory Card in the ARN Receptacle .....................1-29
Figure 2-1. Verifying the Interface Configuration ........................................................2-9
Figure 2-2. Verifying Directed Netboot Configuration ...............................................2-13
Figure 3-1. ARN Base Module Diagnostic LEDs ........................................................3-2
Figure 3-2. ARN Power Switch .................................................................................3-10
Figure 3-3. ARN Reset Button ..................................................................................3-11
Figure 3-4. Removing an ARN Flash Memory Card ................................................3-12
Figure 3-5. Memory Card Read/Write Protect Switch ..............................................3-13
Figure B-1. ARN Module Locations ........................................................................... B-2
Figure B-2. Starting the IP Interface Test ................................................................. B-17
114200 Rev. A
xvii
Page 18
Figure D-1. Cable 7837 (V.28 Compliant) ..................................................................D-3
Figure D-2. Cable 7220 (V.35 Compliant) ..................................................................D-4
Figure D-3. Cable 7224 (X.21 Compliant) ..................................................................D-6
Figure D-4. Clearance and Creepage Distances for ISDN BRI and
Serial Adapter Modules ........................................................................ D-10
xviii
114200 Rev. A
Page 19

Tables

Table 1-1. Installation Space Requirements .............................................................1-5
Table 1-2. V.34 Modem Adapter Module Defaults ..................................................1-19
Table 1-3. Console Parameters ..............................................................................1-21
Table 1-4. External Modem Parameters .................................................................1-24
Table 1-5. Back-Panel V.34 Modem Defaults ..........................................................1-26
Table 2-1. Summary of Initial Startup Options ..........................................................2-2
Table 2-2. Your ifconfig Command -- Netboot ...........................................................2-8
Table 2-3. Your ifconfig Command -- Directed Netboot ..........................................2-11
Table 2-4. Your bconfig Commands ........................................................................2-12
Table 3-1. Base Module Diagnostic LEDs ................................................................3-3
Table 3-2. Base Module Ethernet LEDs ...................................................................3-4
Table 3-3. Base Module Token Ring LEDs ...............................................................3-4
Table 3-4. Expansion Module Ethernet LEDs ...........................................................3-5
Table 3-5. Expansion Module Token Ring LEDs .......................................................3-5
Table 3-6. Expansion Module Serial LEDs ...............................................................3-6
Table 3-7. Serial LED ................................................................................................3-6
Table 3-8. ISDN BRI LEDs ........................................................................................3-7
Table 3-9. DSU/CSU LEDs .......................................................................................3-7
Table 3-10. V.34 Modem LEDs ...................................................................................3-8
Table 3-11. Boot Status LEDs .....................................................................................3-9
Table A-1. ifconfig Command Settings for a COM Interface .....................................A-2
Table A-2. ifconfig Command Settings for an Ethernet Interface ............................. A-4
Table A-3. ifconfig Command Settings for a Token Ring Interface ........................... A-5
Table A-4. ifconfig Settings to Enable and Disable Netboot Interfaces .................... A-6
Table A-5. bconfig Command Settings ..................................................................... A-7
Table B-1. Quick-Start Connector Names and Numbers ......................................... B-2
Table B-2. Quick-Start Commands ........................................................................ B-16
Table C-1. ARN Wall Outlet Requirements ...............................................................C-2
Table C-2. Network Interfaces Available on ARNs ................................................... C-4
114200 Rev. A
xix
Page 20
Table C-3. AUI Pin Assignments ..............................................................................C-5
Table C-4. 10Base-T Interface Pin Assignments ......................................................C-6
Table C-5. Token Ring STP Interface Pin Assignments ........................................... C-7
Table C-6. Token Ring UTP Interface Pin Assignments ...........................................C-8
Table C-7. Serial Interface Pin Assignments ............................................................ C-9
Table C-8. ISDN BRI U Interface Pin Assignments ................................................ C-10
Table C-9. ISDN BRI S/T Interface Pin Assignments ............................................. C-11
Table C-10. DSU/CSU Interface Pin Assignments ................................................... C-12
Table C-11. V.34 Interface Pin Assignments ............................................................ C-13
Table C-12. Local Console Port DB-9 Pin Assignments ...........................................C-14
Table C-13. Service Modem Port DB-9 Pin Assignments ........................................C-15
Table D-1. Safety Status (Order Nos. CV1001001, CV1001002, CV1001003,
CV1001004, CV1001005) ....................................................................... D-1
Table D-2. Safety Status (Order Nos. CV1101001, CV1101002, CV1101003,
CV1101004, CV1101005) ....................................................................... D-2
Table D-3. Safety Status (Order Nos. CV0004011, CV0004012, CV0004013,
CV0004014, CV0004015) ....................................................................... D-2
Table D-4. WAN Interface (Order No. 7837) .............................................................D-3
Table D-5. V.35 Interface (Order No. 7220) ..............................................................D-5
Table D-6. X.21 Interface (Order No. 7224) ..............................................................D-6
Table D-7. Safety Status (Order No. CV0004001) ....................................................D-7
Table D-8. ISDN BRI Safety Status (Order No. CV0004002) ................................... D-8
Table D-9. ISDN Connector Pinouts .........................................................................D-8
Table D-10. ISDN BRI Power Requirements .............................................................. D-9
Table D-11. Clearance and Creepage Distances for ISDN BRI and
Serial Adapter Modules ........................................................................ D-10
xx
114200 Rev. A
Page 21

About This Guide

This guide explains how to install, start, and operate a BayStack™ Advanced Remote Node™ (ARN™) router, including instructions to
Physically install the ARN
Attach communications equipment
Connect the ARN to the network using one of the software configuration options
Use the ARN operator switches and interpret LED displays

Before Y ou Begin

Before using this guide, you must coordinate with the network administrator for the ARN that you are installing.

Conventions

angle brackets (< >) Indicate that you choose the text to enter based on the
bold text
brackets ([ ]) Indicate optional elements. You can choose none, one,
114200 Rev. A
description inside the brackets. Do not type the brackets when entering the command.
ping
Example: if command syntax is you enter
Indicates text that you need to enter command names in text. Example: Use the
or all of the options.
ping 192.32.10.12
dinfo
command.
<ip_address>
,
xxi
Page 22
Installing and Operating BayStack ARN Routers

Acronyms

italic text
Indicates variable values in command syntax descriptions, new terms, file and directory names, and
book titles. quotation marks (“ ”) Indicate the title of a chapter or section within a book. separator ( > ) Separates menu and option names in instructions and
internal pin-to-pin wire connections.
Example: Protocols > AppleTalk identifies the
AppleTalk option in the Protocols menu.
Example: Pin 7 > 19 > 20
screen text
Indicates data that appears on the screen.
Example:
Set Bay Networks Trap Monitor Filters
vertical line (|) Indicates that you enter only one of the parts of the
command. The vertical line separates choices. Do not
type the vertical line when entering the command.
Example: If the command syntax is
show at routes
show at routes
nets
|
, you enter either
show at nets
or
, but not both.
xxii
ANSI American National Standards Institute AUI Attachment Unit Interface BootP Bootstrap Protocol BRI Basic Rate Interface CCITT (now ITU-T) CSMA/CD carrier sense multiple access with collision detection CSU channel service unit CTS clear to send DCD data carrier detect DCE data communications equipment DCM Data Collection Module DLCMI Data Link Control Management Interface DSR data set ready DSU data service unit
114200 Rev. A
Page 23
About This Guide
DTE data terminal equipment DTR data terminal ready EIA Electronic Industries Association GUI graphical user interface HDLC high-level data link control IEEE Institute of Electrical and Electronic Engineers IP Internet Protocol ISDN Integrated Services Digital Network ISO International Organization for Standardization ITU-T International T elecommunications Union–Telecommunications LED light-emitting diode LMI Local Management Interface MAC media access control MAU media access unit NBMA nonbroadcast multi-access NEMA National Electrical Manufacturers Association NVFS Nonvolatile File System OSI Open Systems Interconnection OSPF Open Shortest Path First Protocol PCMCIA Personal Computer Memory Card International Association PPP Point-to-Point Protocol RIP Routing Information Protocol RLSD received line signal detection RTS request to send SMDS switched multimegabit data service SNMP Simple Network Management Protocol SQE signal quality error STP shielded twisted-pair TCP/IP Transmission Control Protocol/Internet Protocol TELNET Telecommunication Network TFTP Trivial File Transfer Protocol TPE twisted-pair Ethernet UTP unshielded twisted-pair
114200 Rev. A
xxiii
Page 24
Installing and Operating BayStack ARN Routers

Ordering Bay Networks Publications

To purchase additional copies of this document or other Bay Networks publications, order by part number from the Bay Networks Press telephone or fax numbers:
• Telephone - U.S./Canada 1-888-4BAYPRESS
• Telephone - International 1-510-490-4752
• Fax 1-510-498-2609 You can also use these numbers to request a free catalog of Bay Networks Press
product publications.
at the following
xxiv
114200 Rev. A
Page 25

Technical Support and Online Services

To ensure comprehensive network support to our customers and partners worldwide, Bay Networks Customer Service has Technical Response Centers in key locations around the globe:
Billerica, Massachusetts
Santa Clara, California
Sydney, Australia
Tokyo, Japan
Valbonne, France
114200 Rev. A
The Technical Response Centers are connected via a redundant Frame Relay Network to a Common Problem Resolution system, enabling them to transmit and share information, and to provide live, around-the-clock support 365 days a year.
Bay Networks Information Services complement the Bay Networks Service program portfolio by giving customers and partners access to the most current technical and support information through a choice of access/retrieval means. These include the World W ide Web, CompuServ e, Support Source CD, Customer Support FTP, and InfoFACTS document fax service.
xxv
Page 26
Installing and Operating BayStack ARN Routers

Bay Networks Customer Service

If you purchased your Bay Networks product from a distributor or authorized reseller, contact that distributor’s or reseller’s technical support staf f for assistance with installation, configuration, troubleshooting, or integration issues.
Customers can also purchase direct support from Bay Networks through a variety of service programs. As part of our PhonePlus™ program, Bay Netw orks Service sets the industry standard, with 24-hour, 7-days-a-week telephone support available worldwide at no extra cost. Our complete range of contract and noncontract services also includes equipment staging and integration, installation support, on-site services, and replacement parts delivery -- within approximately 4 hours.
To purchase any of the Bay Networks support programs, or if you have questions on program features, use the following numbers:
Region Telephone Number Fax Number
United States and Canada
1-800-2LANWAN; enter Express Routing Code (ERC) 290 when prompted
(508) 670-8766
xxvi
(508) 436-8880 (direct) Europe (33) 92-968-300 (33) 92-968-301 Asia/Pacific Region (612) 9927-8800 (612) 9927-8811 Latin America (407) 997-1713 (407) 997-1714
In addition, you can receive information on support programs from your local Bay Networks field sales office, or purchase Bay Networks support directly from your authorized partner.
114200 Rev. A
Page 27

Bay Networks Information Services

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

W orld Wide Web

The Bay Networks Customer Support Web Server offers a diverse library of technical documents, software agents, and other important technical information to Bay Networks customers and partners.
A special benefit for contracted customers and resellers is the ability to access the Web Server to perform Case Management. This feature enables your support staff to interact directly with the network experts in our worldwide Technical Response Centers. A registered contact with a valid Site ID can
View a listing of support cases and determine the current status of any open case. Case history data includes severity designation, and telephone, e-mail, or other logs associated with the case.
Technical Support and Online Services
Customize the listing of cases according to a variety of criteria, including date, severity, status, and case ID.
Log notes to existing open cases.
Create new cases for rapid, efficient handling of noncritical network situations.
Communicate directly via e-mail with the specific technical resources assigned to your case.
The Bay Networks URL is menu item on that home page.

Customer Service FTP

Accessible via URL combines and organizes support files and documentation from across the Bay Networks product suite, including switching products from our Centillion™ and Xylogics site lets you quickly locate information on any of your Bay Networks products.
114200 Rev. A
®
http://www.baynetworks.com
ftp://support.baynetworks.com
. Customer Service is a
(134.177.3.26), this site
business units. Central management and sponsorship of this FTP
xxvii
Page 28
Installing and Operating BayStack ARN Routers

Support Source CD

This CD-ROM -- sent quarterly to all contracted customers -- is a complete Bay Networks Service troubleshooting knowledge database with an intelligent text search engine.
The Support Source CD contains extracts from our problem-tracking database; information from the Bay Networks Forum on CompuServe; comprehensive technical documentation, such as Customer Support Bulletins, Release Notes, software patches and fixes; and complete information on all Bay Networks Service programs.
You can run a single version on Macintosh Windows 3.1, Windows 95, Windows NT, DOS, or UNIX computing platforms. A Web links feature enables you to go directly from the CD to various Bay Networks Web pages.

CompuServe

For assistance with noncritical network support issues, Bay Networks Information Services maintain an active forum on CompuServe, a global bulletin-board system. This forum provides file services, technology conferences, and a message section to get assistance from other users.
xxviii
The message section is monitored by Bay Networks engineers, who provide assistance wherever possible. Customers and resellers holding Bay Networks service contracts also have access to special libraries for advanced levels of support documentation and software. To take advantage of CompuServe’ s recently enhanced menu options, the Bay Networks Forum has been re-engineered to allow links to our Web sites and FTP sites.
We recommend the use of CompuServe Information Manager software to access these Bay Networks Information Services resources. To open an account and receive a local dial-up number in the United States, call CompuServe at 1-800-524-3388. Outside of the United States, call 1-614-529-1349, or your nearest CompuServe office. Ask for Representative No. 591. When you’re on line with your CompuServe account, you can reach us with the command GO BAYNET.
114200 Rev. A
Page 29

InfoFACTS

InfoFACTS is the Bay Networks free 24-hour fax-on-demand service. This automated system has libraries of technical and product documents designed to help you manage and troubleshoot your Bay Networks products. The system responds to a fax from the caller or to a third party within minutes of being accessed.
To use InfoFACTS in the United States or Canada, call toll-free 1-800-786-3228. Outside of North America, toll calls can be made to 1-408-764-1002. In Europe, toll-free numbers are also available for contacting both InfoFACTS and CompuServe. Please check our Web page for the listing in your country.

How to Get Help

Use the following numbers to reach your Bay Networks Technical Response Center:
Technical Response Center Telephone Number Fax Number
Billerica, MA 1-800-2LANWAN (508) 670-8765 Santa Clara, CA 1-800-2LANWAN (408) 764-1188 Valbonne, France (33) 92-968-968 (33) 92-966-998 Sydney, Australia (612) 9927-8800 (612) 9927-8811 Tokyo, Japan (81) 3-5402-0180 (81) 3-5402-0173
Technical Support and Online Services
114200 Rev. A xxix
Page 30
Page 31
Chapter 1
Installing the BayStack Advanced Remote Node
This chapter describes how to install the BayStack ARN. Topics include the following:
Preparing to install the ARN
Installing the ARN
Connecting communication cables
Connecting a management console
Connecting a modem
Connecting the power cable
Installing the Flash memory card
Note: The installation instructions in this chapter assume that wiring is
already installed on the premises using common cable system practices. Your exact installation procedure may differ slightly, depending on your particular cable system.
114200 Rev. A 1-1
Page 32
Installing and Operating BayStack ARN Routers

Preparing to Install the ARN

Verify the following before beginning the installation, as explained in the sections that follow:
Your shipment is complete and undamaged.
You have the proper equipment and tools.
Your installation site meets physical, electrical, and environmental requirements.
You have the communications devices and the cabling that you need to attach to the ARN.

Verifying Shipment Contents

We strongly suggest that you inspect all items for shipping damage. If you detect any damage, do not install the ARN. Call the Bay Networks Technical Response Center in your area, as described in “About This Guide.”
In addition to the ARN and this manual, your shipping container should contain several other hardware accessory items. Verify that the items in the shipping container match those on the packing list.
Note: You can find the packing list affixed to the shipping container.
Refer to the following checklist when verifying the contents of the shipping container:
__ One power cable for connecting the ARN to a wall outlet. __ One cable kit (Order No. 110310) for connecting an optional local console or
modem. The console/modem cable kit contains one 15-foot AT standard molded serial cable (with DB-9 receptacle to DB-25 plug connectors) and one null modem crossover adapter (with DB-25 to DB-25 receptacle connectors).
__ Two flange brackets and eight #6 flathead screws. __ Four #10 cagenut screws and washers for rack-mounting the ARN. __ Four rubber feet (for table-top operation).
1-2 114200 Rev. A
Page 33
Installing the BayStack Advanced Remote Node
Figure 1-1 illustrates the ARN shipping accessories.
Power cable
Console/modem cable (DB-9 receptacle to DB-25 plug cable)
DB-25 receptacle null modem adapter
Two flange brackets
Eight #6 flathead screws
Four cagenuts
Four #10 cagenut screws and washers
Four rubber feet
ARN0048A
Figure 1-1. Accessories in the ARN Shipping Container
114200 Rev. A 1-3
Page 34
Installing and Operating BayStack ARN Routers

Supplying Equipment

You may need items that are not part of the ARN accessory package. Before installing the ARN hardware, ensure that you have all the cables, tools, and other equipment that you need.
Cables
Unless they were specifically ordered, the cables necessary for your network configuration are not part of the ARN accessory package. If you do not have the proper cables, contact your network administrator or see the Cable Guide for
Routers and BNX Platforms.
Service Console
You can attach an optional VT-100 console (or equiv alent) to the ARN to monitor the results of startup diagnostics and perform manual boot configurations. Or you can attach any AT-compatible modem to allow remote dial-in access to diagnostics and configuration.
Note: To use the Netboot, Directed Netboot, or Local Boot configuration
options (see Chapter 3), you must have a local terminal connected the first time the ARN powers up.
Mounting Hardware
To rack-mount the ARN, you need a Phillips screwdriver and an electronic enclosure rack that meets the following specifications:
Heavy-duty steel construction
Electronic Industries Association (EIA) standard hole-spacing
Width of 19 in. (48.26 cm) and depth of 24 in. (60.96 cm)
If the rack does not have threaded rail holes, you must use cagenuts (see
igure 1-1) to use with the cagenut screws.
F
1-4 114200 Rev. A
Page 35

Verifying Site Requirements

The installation site must provide a certain amount of free space around the ARN to dissipate heat, as detailed in T
Table 1-1. Installation Space Requirements
Width Depth (minimum) Depth (for servicing)
22.5 in. (57.2 cm) 15 in. (38.1 cm) 25 in. (63.5 cm)
In addition, the installation site must meet the electrical and environmental specifications listed in Appendix C.
Caution: You must use grounded electrical power outlets with the ARN.

Installing the ARN

Installing the BayStack Advanced Remote Node
able 1-1.
Once you are ready to install the ARN in its final location, you can
Position the ARN on a flat, sturdy, horizontal surface.
Mount the ARN in an electronic enclosure rack.

Positioning the ARN on a Flat Surface

When positioning the ARN on a flat surface, make sure that the surface is
Large enough for the ARN to operate properly
Sturdy enough to support the combined weight of the ARN and any cables that you connect
We recommend that you place the self-adhesive, rubber feet on the bottom of the ARN chassis (shipped with the ARN). These feet not only protect the surface on which you position the ARN, they provide added friction against the weight of any cables that you attach to the device.
114200 Rev. A 1-5
Page 36
Installing and Operating BayStack ARN Routers

Rack-Mounting the ARN

For this procedure, you need
Four #10 cagenut screws and washers (shipped with the ARN)
Two flange brackets and eight #6 flathead screws (shipped with the ARN)
A Phillips screwdriver
An electronic enclosure rack
Note: If the rack does not have threaded rail holes, you must supply and attach
four cagenuts.
To rack-mount the ARN:
1. Attach a flange bracket to both sides of the ARN.
On each side of the chassis:
a. Align the holes in the longer end of the flange bracket with the
mounting holes near the front panel of the ARN (F
igure 1-2).
b. Insert a #6 flathead screw through each hole and into the ARN. c. Tighten the four screws with a Phillips screwdriver.
1-6 114200 Rev. A
Page 37
Installing the BayStack Advanced Remote Node
RLSD3
RLSD4
RLSD5
Base
Pwr
Run
Adapter1
RPS
Boot
Adapter2
Fan
Fail
Screws (8 places)
Expansion
DCM
PCMCIA
BayStack Advanced Remote Node
Tx
B1
B2
DD
ISDN BRI
withNT1
1
2
RLSD
Rx
Cl
Alternative bracket position (2 places)
ARN0004A
Figure 1-2. Attaching Flange Brackets to Rack-Mount the ARN
Align the holes in the shorter end of the flange bracket with the holes in
2.
the front vertical supports of the rack (F
114200 Rev. A 1-7
igure 1-3).
Page 38
Installing and Operating BayStack ARN Routers
U
D
1
2
B1
ISDN BRI
DD
B2
withNT1
COM
RLSD
Serial
10BaseT
Tx
Rx
Cl
Ethernet 2
10BaseT
Tx
Rx
Cl
Ethernet 1
Cagenut screw (4 places)
Rail without threaded holes
RLSD3
AUI
AUI
COM3 COM4 COM5
RLSD4
RLSD5
Run
Pwr
Base
Expansion
Boot
RPS
Adapter1
DCM
Fail
Fan
Adapter2
PCMCIA
Serial
BayStack Advanced Remote Node
Use cagenut
ARN0005A
Figure 1-3. Installing the ARN in an Electronic Enclosure Rack
Insert a cagenut screw through each bracket hole and into the
3.
corresponding holes in the rack.
4. Tighten each cagenut screw with a Phillips screwdriver.
1-8 114200 Rev. A
Page 39
Installing the BayStack Advanced Remote Node

Understanding the ARN Module Locations

The ARN is designed to scale to your needs. In addition to either an Ethernet or token ring base module, the ARN can contain an optional expansion module and up to two adapter modules (F
igure 1-4).
Adapter modules
U
D
1
2
ISDN BRI
withNT1
RLSD
B1
DD
B2
COM
Serial
STP
RCVR
NSRT
WFLT
Token Ring 2
UTP
10BaseT
Tx
Rx
Cl
Ethernet 1
Figure 1-4. ARN Module Locations
The ARN is available in the following base module configurations:
One Ethernet AUI and Ethernet 10Base-T interface
One Token Ring interface (STP only)
The ARN supports the following expansion modules:
One Ethernet AUI and Ethernet 10Base-T interface
One Token Ring interface (STP and UTP)
Three serial interfaces
One Ethernet AUI and Ethernet 10Base-T interface and three serial interfaces
One Token Ring interface (STP and UTP) and three serial interfaces
Expansion module
RLSD3
RLSD4
RLSD5
AUI
Run
Boot
Fail
COM3 COM4 COM5
Serial
Pwr
Base
Expansion
RPS
Adapter1
DCM
Fan
Adapter2
PCMCIA
Base module
BayStack Advanced Remote Node
ARN0006A
Note: The Ethernet base and expansion modules can also contain an optional
data collection module (DCM). The DCM gathers Ethernet statistics for a remote monitoring (RMON) utility. Your network administrator can refer to Configuring Remote Access for additional information about how to enable and use the DCM.
114200 Rev. A 1-9
Page 40
Installing and Operating BayStack ARN Routers
The ARN also supports up to two of the following adapter modules:
Single serial interface
Single ISDN BRI S/T interface
Single ISDN BRI U interface
Single V.34 modem adapter interface
Single 56/64K DSU/CSU interface

Connecting Communications Cables

Gather the communications equipment and cabling that you will attach to the ARN. If you do not have the proper cables, contact your network administrator or see the Cable Guide for Routers and BNX Platforms.
Note: Refer to Appendix C, later in this manual, for ARN cable interface
descriptions.

Connecting to an Ethernet Interface

You can connect an Ethernet cable to any ARN base or expansion module that contains an Ethernet interface option. Each Ethernet interface option offers two Ethernet interface types -- an AUI transceiver interface or a 10Base-T interface.
Note: You can use only one Ethernet interface on an ARN base or expansion
module at any time. For example, you can connect to either the AUI transceiver interface or the 10Base-T interface on a base module, but you cannot use both interfaces at the same time.
1-10 114200 Rev. A
Page 41
Installing the BayStack Advanced Remote Node
Connecting to an AUI Interface
To connect an Ethernet AUI transceiver cable to an AUI interface:
Caution: Connecting the ARN AUI interface directly to the AUI interface on
an Ethernet station violates IEEE 802.3 standards. The AUI interface is designed only for connection to a transceiver.
1. Connect an Ethernet AUI drop cable to the interface labeled AUI
igure 1-5).
(F
The cable must have a 15-position D-SUB receptacle.
Expansion module AUI interface
Base module AUI interface
U
D
1
2
ISDN BRI
withNT1
RLSD
B1
DD
B2
COM
Serial
10BaseT
Tx
Rx
Cl
10BaseT
Tx
Rx
Cl
To Ethernet transceiver
Ethernet 2
Ethernet 1
Figure 1-5. Connecting an AUI Cable
Secure the AUI cable using the slide lock on the interface.
2.
3. Connect the other end of the cable to an Ethernet transceiver.
AUI
AUI
RLSD3
RLSD4
RLSD5
Run
Boot
Diag
COM3 COM4 COM5
Serial
Pwr
Base
Expansion
RPS
Adapter1
DCM
Fan
Adapter2
PCMCIA
BayStack Advanced Remote Node
Ethernet AUI drop cable
ARN0063A
114200 Rev. A 1-11
Page 42
Installing and Operating BayStack ARN Routers
Connecting to a 10Base-T Interface
To connect an unshielded twisted-pair (UTP) cable to the base module or expansion module 10Base-T interface, insert the UTP jack into the RJ-45 interface, as shown in F
igure 1-6.
Expansion module 10Base-T interface
Base module 10Base-T interface
U
D
1
2
ISDN BRI
withNT1
RLSD
B1
DD
B2
COM
Serial
To Ethernet network
10BaseT
Tx
Rx
Cl
10BaseT
Tx
Rx
Cl
AUI
Ethernet 2
AUI
Ethernet 1
RLSD3
RLSD4
RLSD5
Run
Pwr
Boot
RPS
Diag
Fan
Ethernet 10Base-T cables
Figure 1-6. Connecting a 10Base-T Ethernet Cable
COM3 COM4 COM5
Serial
Base
Expansion
Adapter1
DCM
Adapter2
PCMCIA
BayStack Advanced Remote Node
ARN0062A
1-12 114200 Rev. A
Page 43
Installing the BayStack Advanced Remote Node

Connecting to a Token Ring Interface

You can connect a token ring cable to any ARN base module or expansion module that contains a token ring interface option. Each of these interface options offers two token ring interface types -- an STP interface or a UTP interface.
Note: You can use only one token ring interface on an ARN base or expansion
module at any time. For example, you can connect to either the STP interface or the UTP interface on a base module, but you cannot use both interfaces at the same time.
Connecting to an STP Token Ring Interface
To connect a token ring STP cable to the base module or expansion module token ring interface:
1. Attach the 9-pin D-SUB plug to the token ring STP interface (Figure 1-7).
Expansion module STP interface
Base module STP interface
U
D
1
2
ISDN BRI
withNT1
RLSD
B1
DD
B2
COM
Serial
STP
STP
Token Ring 1
RCVR
NSRT
WFLT
Token Ring 2
RCVR
NSRT
WFLT
UTP
RLSD3
RLSD4
RLSD5
Run
Boot
Fail
COM3 COM4 COM5
Serial
Pwr
Base
Expansion
RPS
Adapter1
DCM
Fan
Adapter2
PCMCIA
BayStack Advanced Remote Node
Token Ring STP cables
To Token Ring network
ARN0068A
Figure 1-7. Connecting a Token Ring STP Cable
Secure the token ring cable using the capture screws.
2.
114200 Rev. A 1-13
Page 44
Installing and Operating BayStack ARN Routers
Connecting to a UTP Token Ring Interface
T o connect a Token Ring UTP cable to the expansion module token ring interface, insert the RJ-45 connector into the UTP interface, as shown in F
igure 1-8.
Expansion module UTP interface
U
D
1
2
ISDN BRI
withNT1
RLSD
B1
DD
B2
COM
Serial
STP
Token Ring 2
STP
Token Ring 1
RCVR
NSRT
WFLT
RCVR
NSRT
WFLT
To Token Ring network
UTP
RLSD3
RLSD4
RLSD5
Run
Boot
Fail
Token Ring UTP cables
Figure 1-8. Connecting Token Ring UTP Cables
COM3 COM4 COM5
Serial
Pwr
Base
Expansion
RPS
Adapter1
DCM
Fan
Adapter2
PCMCIA
BayStack Advanced Remote Node
ARN0069A
1-14 114200 Rev. A
Page 45

Connecting to a Serial Interface

The ARN supports up to five serial interfaces. You can connect
Up to three, 44-pin serial cables to an ARN that contains an Ethernet/tri-serial, Token Ring/tri-serial, or Tri-Serial expansion module
One, 44-pin serial cable to each Serial adapter module (the ARN can support two)
To connect to a serial interface:
1. Locate the RS-232, RS-422, RS-530, V.28, V.35, or X.21 interface cable.
See the Cable Guide for Routers and BNX Platforms.
Note: The Cable Guide for Routers and BNX Platforms refers to serial cables
that transmit synchronous data as “synchronous” cables.
2. Connect the cable to a serial interface.
Installing the BayStack Advanced Remote Node
The serial interfaces on an ARN expansion module are labeled COM3, COM4, or COM5 (F
U
D
1
2
ISDN BRI
withNT1
RLSD
B1
DD
B2
COM
Serial
Figure 1-9. Connecting Serial Cables to an Expansion Module
Tx
Rx
Cl
Tx
Rx
Cl
10BaseT
10BaseT
igure 1-9).
AUI
Ethernet 2
AUI
Ethernet 1
RLSD3
RLSD4
RLSD5
Run
Boot
Fail
To RS-232, RS-422, RS-530, V.35, or X.21 interface
COM3 COM4 COM5
Pwr
Base
Expansion
RPS
Adapter1
DCM
Fan
Adapter2
PCMCIA
Serial
BayStack Advanced Remote Node
ARN0067A
114200 Rev. A 1-15
Page 46
Installing and Operating BayStack ARN Routers
1
2
Tx
Rx
Cl
Tx
Rx
Cl
10BaseT
Ethernet 1
10BaseT
Ethernet 2
On an ARN adapter module, the serial interface is labeled COM
igure 1-10).
(F
U
ISDN BRI
RLSD
withNT1
D
B1
DD
B2
COM
To RS-232, RS-422, RS-530, V.35, or X.21 interface
ARN0066A
Figure 1-10. Connecting a Serial Cable to a Serial Adapter Module
Secure the cable to the interface using the capture screws on the cable.
3.
4. Connect the remote end of each cable to the appropriate communications
equipment.
1-16 114200 Rev. A
Page 47
1
2
Tx
Rx
Cl
Tx
Rx
Cl
10BaseT
Ethernet 1
10BaseT
Ethernet 2

Connecting to an ISDN Interface

You can connect an ISDN cable to any ARN that contains an ISDN BRI S/T or U adapter module.
To connect to an ISDN BRI interface:
1. Insert the ISDN cable into the ISDN BRI interface (Figure 1-11).
Installing the BayStack Advanced Remote Node
RLSD
U
ISDN BRI
To ISDN switch
withNT1
D
B1
DD
B2
COM
Serial
ARN0064A
Figure 1-11. Connecting an ISDN BRI Cable
Connect the other end of the cable to the ISDN communications device.
2.
114200 Rev. A 1-17
Page 48
Installing and Operating BayStack ARN Routers
DDS
TxD
RxD CDTest
1
2
56K/64K
DSU/CSU
Tx
Rx
Cl
Tx
Rx
Cl
10BaseT
Ethernet 1
10BaseT
Ethernet 2
COM
RLSD
Serial

Connecting to a DSU/CSU Interface

You can connect a DSU/CSU cable to any ARN that contains a DSU/CSU adapter module.
To connect to a DSU/CSU interface:
1. Insert the DSU/CSU cable connector into the DSU/CSU interface labeled
DDS (F
igure 1-12).
To digital line wall jack
ARN0065A
Figure 1-12. Connecting a DSU/CSU Cable
Connect the other end of the cable to a digital line (for example, a digital
2.
line wall jack that connects to an office channel unit [OCU]).
1-18 114200 Rev. A
Page 49
Installing the BayStack Advanced Remote Node

Connecting to a V.34 Modem Interface

You can connect an RJ-11 telephone cable to any ARN that contains a V.34 modem adapter module.
Note: The default settings for the front-panel V.34 modem adapter module
differ from the default settings for the back-panel V.34 modem. Refer to “Connecting to a V.34 Modem Module” earlier in this chapter for information about the V.34 modem adapter and its default settings.
Table 1-2 provides the default settings for the V.34 modem adapter module.
Table 1-2. V.34 Modem Adapter Module Defaults
Modem Signal/Parameter Value
Clear To Send (CTS) On Data Terminal Ready (DTR) Depends on the modem type. Set the modem to
Data Carrier Detect (DCD) or RLSD On while carrier is present (the ARN uses DCD to
Data Set Ready (DSR) On Ready to Send (RTS) Ignore Synchronous/Asynchronous Mode Asynchronous AutoAnswer Set on
Local Character Echo Off Supervisory Functions Off Baud Rate 28800 Data Bits 8 Stop Bits 1 Parity None
answer incoming calls when DTR is active.
detect modem connect and disconnect).
n
rings with DTR active (n must be greater
than 0).
114200 Rev. A 1-19
Page 50
Installing and Operating BayStack ARN Routers
COM
Telco
Tx
Rx
RLSD
DTR
RLSD
Serial
V.34 Modem
Tx
Rx
Cl
Tx
Rx
Cl
1
1
Console
Modem
Modem
TxRxRLSD
DTR
To connect to a V.34 modem interface:
1. Insert the RJ-11 telephone cable into the V.34 modem interface labeled
Telco (F
igure 1-13).
Front-panel V.34 Modem Interface
To RJ-11 telephone receptacle
ARN0071A
To RJ-11 telephone receptacle
Figure 1-13. Connecting an RJ-11Cable
Connect the other end of the cable to an analog telephone line (for
2.
example, the telephone wall receptacle).

Connecting a Management Console

Use the back-panel console port to connect an ASCII-based terminal or a personal
computer terminal emulator to the ARN.
Back-panel V.34 Modem Interface
ARN0072A
Using a local terminal, you can monitor the results of startup diagnostics and set the boot configuration. Using an attached modem, you can allow remote dial-in access to diagnostics.
Note: To use the Netboot, Directed Netboot, or Local Boot software
configuration options, you must connect a console the first time you power up the ARN, as described in Chapter 3.
1-20 114200 Rev. A
Page 51

Connecting a Terminal Console

You need both pieces in the ARN console/modem cable kit (Order No. 110310) to connect a terminal console:
Order No. 110307 serial console/modem cable (with 9-pin receptacle to 25-pin plug connectors)
Order No. 110308 null modem crossover adapter (with two 25-pin receptacle connectors)
Once you have the appropriate equipment, complete the following steps:
1. Power on and configure the console, using the parameters in Table 1-3.
Refer to the console user manual for instructions.
Table 1-3. Console Parameters
Parameter Value
Baud Rate 9600 Data Bits 8 Stop Bits 1 Parity None
Installing the BayStack Advanced Remote Node
2. Power off the console.
3. Attach the null modem crossover adapter to the 25-pin cable connector.
4. Insert the screw on the cable connector into the receptacle on the adapter
connector and tighten the screw (F
Console cable
Rotate to tighten screw
Screw receptacle
igure 1-14).
Null modem adapter
AN0010A
Figure 1-14. Attaching the Null Modem Adapter
114200 Rev. A 1-21
Page 52
Installing and Operating BayStack ARN Routers
5. Attach the 25-pin receptacle connector on the combined cable and
adapter to the console host connector (F
igure 1-15).
U
L
100-240~
1.2A
50-60Hz
Redundant Power
U
L
Figure 1-15. Connecting a Terminal Console to an ARN
Insert the 9-pin receptacle end of the console cable into the ARN console
6.
port connector.
The console is now connected to the ARN.

Connecting a PC Console

You need both pieces in the ARN console/modem cable kit to connect a PC:
Order No. 110307 serial console/modem cable (with 9-pin receptacle to 25-pin plug connectors)
COMM
Modem
20 mA PR
KB
Console cable plus null modem adapter
ARN0058A
Order No. 110308 null modem crossover adapter (with two 25-pin receptacle connectors)
You also need another standard AT serial cable with a 25-pin plug connector. Once you have the correct equipment, complete the following steps:
1. Power on and configure the PC console, using the parameters in
able 1-3 and instructions in the console user manual.
T
1-22 114200 Rev. A
Page 53
Installing the BayStack Advanced Remote Node
Power off the PC console.
2.
3. Insert the 9-pin receptacle end of the console cable into the console port
igure 1-16).
(F
4. Attach the null modem crossover adapter to the other end of the console
cable (refer to F
U
L
100-240~
1.2A
50-60Hz
Redundant Power
U
L
igure 1-14).
Modem
PC cable
Null modem adapter
Console cable
ARN0056A
Figure 1-16. Connecting a PC Console to an ARN
Attach the 25-pin receptacle end of the cable-plus-adapter to the PC
5.
console cable 25-pin plug connector.
6. Connect the complete cable unit to the communications port at the back
of the PC (F
114200 Rev. A 1-23
igure 1-16).
Page 54
Installing and Operating BayStack ARN Routers

Connecting a Modem

You can connect a modem to the ARN using the back-panel modem port or you can connect a telephone line directly to an optional, back-panel V.34 modem adapter module.
Note: To use the Netboot, Directed Netboot, or Local Boot software
configuration options, you must connect a console the first time you power up the ARN. Refer to Chapter 3 for details.
A modem provides remote access to the ARN for a system administrator. We recommend that you connect a modem in case the ARN experiences system problems.

Connecting to the Back-Panel Modem Port

To connect a modem to the ARN back panel, you need an AT (or Hayes) compatible modem and the Order No. 110307 modem cable that came in the ARN console/modem cable kit.
Note: Do not use the Order No. 110308 null modem crossover adapter in the
ARN cable kit to connect to a modem.
Complete the following steps:
1. Configure the modem, using the parameters in Table 1-4.
Table 1-4. External Modem Parameters
Modem Signal/Parameter Value
Clear To Send (CTS) On Data Terminal Ready (DTR) Set to answer all incoming calls. Data Carrier Detect (DCD) or RLSD On while carrier is present (the ARN uses DCD to
detect modem connect and disconnect). Data Set Ready (DSR) On Ready to Send (RTS) Ignored
(continued)
1-24 114200 Rev. A
Page 55
Installing the BayStack Advanced Remote Node
Table 1-4. External Modem Parameters
(continued)
Modem Signal/Parameter Value
Synchronous/Asynchronous Mode Asynchronous AutoAnswer Answer on 2 rings with DTR active. Local Character Echo Off Supervisory Functions Off Baud Rate 9600 Data Bits 8 Stop Bits 1 Parity None
Refer to the modem user guide for instructions.
2. Power off the modem.
3. Insert the 9-pin receptacle end of the modem cable into the front-panel
console port (F
igure 1-17).
PHONE
DIAL
NMS DTE
(LEASE
(LEASED)
DWR
3810
3810
U
L
100-240~
1.2A 50-60Hz
Redundant Power
U
L
Console
Modem cable
ARN0057A
Figure 1-17. Connecting a Modem to an ARN
Insert the 25-pin plug at the other end of the modem cable into the
4.
modem RS-232 data communications port
114200 Rev. A 1-25
.
Page 56
Installing and Operating BayStack ARN Routers

Connecting to a V.34 Modem Module

If your ARN contains an optional, back-panel V.34 modem module, you need only connect the telephone line to the V.34 interface for access to the router.
Note: The default settings for the back-panel V.34 modem differ from the
default settings for the front-panel V.34 modem adapter module. Refer to “Connecting to a V.34 Modem Interface” earlier in this chapter for information about the V.34 modem adapter and its default settings.
Table 1-5 provides the default settings for the back-panel V.34 modem adapter.
Table 1-5. Back-Panel V.34 Modem Defaults
Modem Signal/Parameter Value
Clear To Send (CTS) On Data Terminal Ready (DTR) Set to answer all incoming calls. Data Carrier Detect (DCD) or RLSD On while carrier is present (the ARN uses DCD to
Data Set Ready (DSR) On Ready to Send (RTS) Ignored Synchronous/Asynchronous Mode Asynchronous AutoAnswer Answer on 2 rings with DTR active. Local Character Echo Off Supervisory Functions Off Baud Rate 9600 Data Bits 8 Stop Bits 1 Parity None
detect modem connect and disconnect).
Note: Physically connecting to either a front-panel or back-panel V.34 modem
interface is essentially the same. Refer to “Connecting to a V.34 Modem Interface” earlier in this chapter for details.
1-26 114200 Rev. A
Page 57

Connecting the Power Cable

Complete these steps to connect the power cable:
1. Connect the power cable to the power connector on the ARN back panel
igure 1-18).
(F
Danger: Be sure that the power switch is in the OFF (0) position before you
connect the power cable.
Installing the BayStack Advanced Remote Node
Power cable
100-240~
1.2A
50-60Hz
Redundant power supply cable
U
L
Redundant Power
U
L
ARN0017A
Figure 1-18. Connecting the Power Cable
Connect the remote end of the power cable to a grounded outlet.
2.
Note: For information about connecting a redundant power supply to the
ARN, refer to your redundant power supply documentation.
114200 Rev. A 1-27
Page 58
Installing and Operating BayStack ARN Routers

Installing the Flash Memory Card

A PCMCIA Flash memory card (Figure 1-19) provides storage capability for the Nonvolatile File System (NVFS) in the ARN. When you remove a formatted memory card, the NVFS automatically removes access to the card. When you insert and format a card or insert an already formatted card, the NVFS automatically provides access.
INSERT
AN0060A
Figure 1-19. Flash Memory Card
Before starting the ARN, install the Flash memory card supplied with the router by following these steps:
1. Position the card with the label facing up and the INSERT arrow
pointing toward the card receptacle.
2. Insert the card into the receptacle.
F
igure 1-20 shows how to insert the Flash memory card in an ARN.
3. Gently push the card until it fits snugly into place.
If the card is new, and you did not obtain it from Bay Networks, you must format the card before attempting to write to it. You can format the card using Site Manager software or the
format command available with the Bay Networks
Technician Interface. (Refer to Using Technician Interface Software for instructions.)
1-28 114200 Rev. A
Page 59
Installing the BayStack Advanced Remote Node
U
L
100-240~
1.2A
50-60Hz
U
L
Redundant Power
Figure 1-20. Inserting the Flash Memory Card in the ARN Receptacle

Where to Go Next

Use the following table to determine where you want to go next.
For information about Go to
Starting the ARN Chapter 2 Operating the ARN Chapter 3 Configuring the ARN for Netboot and Directed
Netboot Using Local Boot (the Quick-Start Procedure) Appendix B ARN Technical Specifications Appendix C
Appendix A
Console Modem
ARN0018A
114200 Rev. A 1-29
Page 60
Page 61
Chapter 2
Starting the ARN
The first time you start the ARN, you complete an important software configuration process -- you provide the ARN with the files it needs to operate over the network. This chapter discusses the need for these specific startup files, what methods you can use to ensure that the router installs and uses the appropriate files, and how to use each of these installation methods.
Note: Coordinate the initial startup of the ARN with your network
administrator. This person refers to Configuring Remote Access to determine which software configuration option is best for your site and for instructions on setting up a boot server.

Software Installation

Before it can operate, the ARN hardware must install two startup files -- a software image and a configuration file.
The software image is a group of executable files that operate the protocols that the network requires. The process of installing and using this image is called booting. The software image that the ARN uses is called arn.exe.
To bridge and route traffic, the ARN also needs a configuration file that is tailored to the network. A configuration file is a binary system file that contains hardware and software configuration data. The default configuration file is named config. Bay Networks ships the executable and default configuration files on PCMCIA Flash cards.
114200 Rev. A 2-1
Page 62
Installing and Operating BayStack ARN Routers
You must complete an initial startup procedure to obtain the executable and default configuration files and connect the ARN to the network. Getting a file o ver the network is called network booting, or netbooting. Getting a file from the ARN file system, stored in Flash memory, is called local booting.
Caution: The ARN must contain a Flash memory card if you plan to obtain
any startup files through the local boot procedure. If you attempt to local boot the ARN without the Flash memory card inserted, the router does not operate. Refer to “Installing the Flash Memory Card” in Chapter 1 for instructions.

Understanding the ARN Boot Options

You use one of four boot options to complete software installation: EZ-Install, Netboot, Directed Netboot, or Local Boot. T the sections that follow provide steps for completing each option.
Table 2-1. Summary of Initial Startup Options
Source for Boot Option
Source for Image file
Configuration
File Description and Requirements
able 2-1 summarizes the four options;
EZ-Install Local Network
(serial interface
only)
Netboot* Local
or Network
Local
or
Network
The default option. The ARN boots from local Flash memory, then obtains its configuration file from a remote workstation that is configured as a Boot Protocol (BootP) server. The ARN saves the configuration to the Flash memory
This option requires a High-Level Data Link Control (HDLC) or Frame Relay serial connection.
The ARN locates and obtains at least one startup file from a remote workstation that is configured as a BootP server.
This option requires a communications connection over an HDLC, Frame Relay, Ethernet, token ring, or DSU/CSU interface, and a local console connection.
.
(continued)
2-2 114200 Rev. A
Page 63
Starting the ARN
Table 2-1. Summary of Initial Startup Options
Source for Boot Option
Directed Netboot†
Local Boot Local Local The ARN boots from a local software image and generic
*. The ARN supports netboot over serial, Ethernet, token ring, and DSU/CSU interfaces only. †. The ARN supports directed netboot over serial, Ethernet, token ring, and DSU/CSU interfaces only.
Source for Image file
Local or Network
Configuration
File Description and Requirements
Local
or
Network
The ARN obtains at least one startup file from a remote workstation that is configured as a Trivial File Transfer Protocol (TFTP) server. You must specify the IP address of the TFTP server and the complete path to the startup files before booting.
This option requires a communications connection over an HDLC, Frame Relay, Ethernet, token ring, or DSU/CSU interface, and a local console connection.
startup configuration file. You create a customized configuration file by running the Quick-Start script.
This option requires a local console connection.
(continued)
114200 Rev. A 2-3
Page 64
Installing and Operating BayStack ARN Routers

Starting the ARN for the First Time

The ARN f actory defaults are set to find the configuration and image files from the following locations:
Configuration file -- over the network
Image file -- on the local PCMCIA Flash memory card These default settings work with the default EZ-Install procedure. The first time you power on an ARN, the router steps through its diagnostic tests
and then attempts to boot over all of its serial (COM) interfaces using EZ-Install. If your network administrator has configured the network for the EZ-Install
procedure, the router boots using its local image and obtains its configuration file over the network. Your network administrator can then connect to the ARN and manage it remotely. Refer to the next section, “Using EZ-Install,” for more information.
If your network administrator does not configure the network for EZ-Install, the ARN cannot obtain its configuration file from the network, and the EZ-Install procedure fails. The ARN then attempts to boot locally with the configuration file that resides on its Flash memory card. Refer to “Using Netboot, Directed Netboot, or Local Boot” for more information.
If both the EZ-Install and local boot attempts fail, the EZ-Install and local boot processes repeat until one of the following occurs:
The ARN boots successfully.
You interrupt the boot process to enter the ARN monitor.
You turn off the ARN. The following sections describe how to use each of the different boot options for
the ARN.
2-4 114200 Rev. A
Page 65

Using EZ-Install

EZ-Install is the default installation option. This option requires that your network administrator has set up the network so that you can start the EZ-Install procedure. In addition, this option requires that you
Install a Flash memory card.
Connect at least one serial (COM) interface to the network. Refer to Chapter 1 for instructions on how to perform any of these tasks.
Note: If your ARN does not have a COM interface, you must configure the
ARN using netboot or directed netboot over an Ethernet, token ring, or DSU/CSU interface, or local boot the ARN and run the Quick-Start script. Go to the next section, “Using Netboot, Directed Netboot, or Local Boot,” for more information.
To use EZ-Install:
1. Press the power switch on the ARN back panel to the ON position.
Starting the ARN
The ARN comes on and activates EZ-Install.
Note: If you power on the ARN before the network administrator is ready,
restart the ARN by pressing the reset button on the rear panel. See Chapter 3 for more information on resetting the ARN.
2. Ensure that the ARN boots correctly.
When the ARN boots, its LEDs flash in a particular order. See Chapter 3 for information on checking the ARN front-panel LEDs to ensure that the installation was successful and that the router is operating properly.
114200 Rev. A 2-5
Page 66
Installing and Operating BayStack ARN Routers

Using Netboot, Directed Netboot, or Local Boot

You must use a command line interface that accesses the router software when you netboot or local boot the ARN. To use a command line interface, you can
Wait for the ARN to local boot (that is, wait for the router to fail EZ-Install and then attempt to boot using its local configuration file). After the ARN boots locally, you can log in to the Technician Interface and redefine the boot process.
Interrupt the boot process using a break sequence and log in to the ARN monitor to redefine the boot process.
Using the netboot, directed netboot, or local boot options requires that you
Connect any necessary communications cables to access the network.
Connect a management console.
Connect the ARN power cable.
Install a Flash memory card.
Refer to Chapter 1 for instructions on how to perform these tasks.

Interrupting the Boot Process

Interrupting the boot process automatically starts the ARN monitor. Using the ARN monitor allows you to bypass the EZ-Install procedure.
Note: Before you power on the ARN, make sure that you have installed the
router and connected the necessary management console equipment (refer to Chapter 1 for instructions).
To interrupt the boot process:
1. Press the power switch on the ARN back panel to the On position.
As the router powers on, your console displays the ARN diagnostic tests. After successfully completing these tests, the router begins the EZ-Install procedure and attempts to boot over the network.
2-6 114200 Rev. A
Page 67
While the router is running the EZ-Install procedure, issue a break
2.
sequence from the management console.
The ARN monitor login prompt appears.
Note: Be sure to issue a break sequence before the boot process completes.
Break sequences can vary, depending on the console equipment type. Some console terminals have specific break keys on their keyboards; other management terminals require a specific key sequence to issue a break (for example,
Cntrl-C or ~ #). Refer to your console terminal or terminal emulator
documentation for the break sequence specific to your console equipment.

Logging in to the Command Line Software

Regardless of the command line software used -- ARN monitor or Technician Interface -- the procedures are identical from the login prompt.
To log in to the command line:
1. Type the following command at the login prompt and press the Return
key:
Starting the ARN
Manager
Note the use of an uppercase “M.” The T echnician Interf ace or ARN monitor command line prompt appears. You
are now using a command line interface to the router.
2. To use the netboot, directed netboot, or the local boot option, go to one of
the following sections that describes the procedure you want to use:
Continuing with Netboot
Continuing with Directed Netboot
Continuing with Local Boot
114200 Rev. A 2-7
Page 68
Installing and Operating BayStack ARN Routers

Continuing with Netboot

Note: Continuing with the netboot option requires that you have already
logged in to the Technician Interface or ARN monitor command line software. Refer to the previous section, “Logging in to the Command Line Software,” for instructions.
You must have at least one serial, Ethernet, or token ring interface connected to the network to use the netboot option. Before you start the netboot procedure, ask your network administrator to
Verify that the network is set up for the netboot procedure.
Provide you with the interface configuration command (
ifconfig) to use in
Step 4.
Note: Refer to Appendix A for more information about the ifconfig command.
ifconfig command configures the parameters necessary to load the software
The image and configuration files from a remote server over the network. Write the command in T
Table 2-2. Your ifconfig Command -- Netboot
ifconfig
able 2-2 for your reference.
You can use the ARN Monitor, Technician Interface, or Site Manager to perform netboot. However, this guide assumes that you are using either the ARN monitor or the Technician Interface. To manage the ARN from a remote site, refer to Configuring Remote Access.
2-8 114200 Rev. A
Page 69
Starting the ARN
To use the netboot option:
1. Enter the ifconfig command (refer to Table 2-2) at the command line
prompt and press the Return key.
The following is a sample command:
ifconfig com1 9.0.0.2 255.0.0.0 9.0.0.3
Refer to Appendix A for more information about the ifconfig command.
2. Enter the following command and press the Return key to verify the
configuration you specified in Step 1:
getcfg
The getcfg command shows the source -- either local or network -- of the boot image and the network configuration file. It also shows the interface configuration that you specified using the
ifconfig command.
Verify the interface configuration, as shown in F
$ getcfg
Boot Options
boot image = local boot config = network
Netboot Parameters:
MAU1...None XCVR2..None COM1...IP=9.0.0.2, Mask=255.0.0.0, Next Hop=9.0.0.3 COM2...EZ-Install COM3...EZ-Install COM4...EZ-Install COM5...EZ-Install
igure 2-1.
Figure 2-1. Verifying the Interface Configuration
ARN0079A
114200 Rev. A 2-9
Page 70
Installing and Operating BayStack ARN Routers
If getcfg displays the correct information, continue to the next step. Otherwise, reenter the correct administrator if you need assistance.
3. Enter the following command and press the Return key to boot the ARN:
boot
Your console displays messages indicating the progress of the netboot procedure.
Note: If the ARN cannot find a software image or configuration file using the
netboot procedure, it attempts to local boot once. If both attempts fail, the ARN continues to netboot and local boot until it boots successfully. If the ARN remains in this loop, refer to “Interrupting the Boot Process” earlier in this chapter.
4. Ensure that the ARN boots correctly.
When the ARN boots, its LEDs flash in a particular order. See Chapter 3 for information on checking the ARN front-panel LEDs to ensure that the installation was successful and that the router is operating properly.
ifconfig command. Contact your network
Contact your network administrator to verify that the ARN is now connected to the network. Your network administrator can refer to Configuring Remote Access to troubleshoot any problems.
Contact your local Bay Networks Technical Response Center if you need additional assistance.
After connecting the ARN to the netw ork, you can replace the local console with a modem connection to enable remote dial-in access.
2-10 114200 Rev. A
Page 71

Continuing with Directed Netboot

Note: Continuing with the directed netboot option requires that you have
already logged in to the Technician Interface or ARN monitor command line software. Refer to the previous section, “Logging in to the Command Line Software,” for instructions.
You must have at least one serial, DSU/CSU, Ethernet, or token ring interface connected to the network to use the directed netboot option. Before you start the directed netboot procedure, ask your network administrator to
Verify that the network is set up so that you can start the directed netboot procedure.
Provide you with the ifconfig command to use in Step 1.
Starting the ARN
Provide you with the boot option configuration commands (
bconfig) to use in
Step 2.
Note: Refer to Appendix A for more information about the ifconfig and
bconfig commands.
ifconfig command configures the parameters necessary to load the software
The image and configuration files from a remote server over the network. Write the command in T
Table 2-3. Your ifconfig Command -- Directed Netboot
ifconfig
able 2-3 for your reference.
114200 Rev. A 2-11
Page 72
Installing and Operating BayStack ARN Routers
The bconfig commands let you specify the location of a startup file. To use directed netboot, the location must includes the following information:
The source of the image and configuration files (local or network)
The address of the TFTP server
The full directory path description locating the files on the TFTP server
Write the commands in T
Table 2-4. Your bconfig Commands
bconfig image bconfig config
able 2-4 for your reference.
You can use the ARN monitor, Technician Interface, or Site Manager to perform directed netboot. However, this guide assumes that you are using either the ARN monitor or the Technician Interface. To manage the ARN from a remote site, refer to Configuring Remote Access.
To use the directed netboot feature:
1. Enter the ifconfig command (refer to Table 2-3) at the command line
prompt and press the Return key.
The following is a sample command:
ifconfig com1 9.0.0.2 255.0.0.0 9.0.0.3
Refer to Appendix A for more information about the ifconfig command.
2. Enter the bconfig commands (refer to Table 2-4) at the command line
prompt and press the Return key.
You must enter one
bconfig command to specify the location of the software
image, and another to specify the location of the configuration file. The following are sample commands:
bconfig image network 192.32.5.8 /usr/arnstartup/krnl_arn.exe bconfig config network 192.32.5.8 /usr/arnstartup/config
Refer to Appendix A for more information about the bconfig command.
2-12 114200 Rev. A
Page 73
Starting the ARN
Type the following command and press the Return key to verify the
3.
configuration you specified in Step 3:
getcfg
The getcfg command shows the location of the boot image and the network configuration file, the interface configuration that you specified using the
ifconfig command, as well as the TFTP server information and file paths that
you specified using the
bconfig commands.
Verify the interface configuration, as shown in F
$ getcfg
Boot Options boot image = network boot config = network host IP address = 192.32.5.8 image pathname = "/usr/arnstartup/krnl_arn.exe" config pathname = "/usr/arnstartup/config"
Netboot Parameters:
MAU1...None XCVR2..None COM1...IP=9.0.0.2, Mask=255.0.0.0, Next Hop=9.0.0.3 COM2...EZ-Install (disabled) COM3...EZ-Install (disabled) COM4...EZ-Install (disabled) COM5...EZ-Install (disabled)
igure 2-2.
Figure 2-2. Verifying Directed Netboot Configuration
ARN0080A
If getcfg displays the correct information, continue to Step 4. Otherwise, reenter the correct
ifconfig and bconfig commands. Contact your network
administrator if you need assistance.
4. Type the following command and press the Return key to boot the ARN:
boot
114200 Rev. A 2-13
Page 74
Installing and Operating BayStack ARN Routers
Note: If the ARN cannot find a software image or configuration file using the
directed netboot procedure, it attempts to netboot once. If the netboot procedure fails, the ARN tries to local boot once. If all three boot attempts fail, the ARN continues to try directed netboot, netboot, and local boot until it boots successfully. If the ARN remains in this loop, refer to “Interrupting the Boot Process” earlier in this chapter.
5. Ensure that the ARN boots correctly.
When the ARN boots, its LEDs flash in a particular order. See Chapter 3 for information on checking the ARN front-panel LEDs to ensure that the installation was successful and that the router is operating properly.
Contact your network administrator to verify that the ARN is now connected to the network. Your network administrator can refer to Configuring Remote Access to troubleshoot any problems.
Contact your local Bay Networks Technical Response Center if you need additional assistance.
After connecting the ARN to the netw ork, you can replace the console connection with a modem connection to enable remote dial-in access.
2-14 114200 Rev. A
Page 75

Continuing with Local Boot (the Quick-Start Procedure)

Note: Continuing with the local boot option requires that you have already
logged in to the Technician Interface or ARN monitor command line software. Refer to the previous section, “Logging in to the Command Line Software,” for instructions.
You can use either the ARN monitor or the Technician Interface to configure the ARN to local boot. However, you must use the Technician Interface to run the Quick-Start script.
Before starting the local boot procedure, ask your network administrator to assist you in completing the Quick-Start worksheets in Appendix B.
To use the local boot feature:
1. At the command line prompt, type the following command and press the
Return key to configure the ARN to use its local config file:
bconfig config local
Starting the ARN
Note: The default setting for finding the software image is local; you do not
have to change this setting for the local boot option.
Type the following command and press the Return key to boot the ARN:
2.
boot
Note: If the ARN tries to local boot and cannot find a software image or
configuration file, it attempts to netboot once. If both attempts fail, the ARN continues to local boot and netboot until it boots successfully. If the ARN remains in this loop, refer to “Interrupting the Boot Process” earlier in this chapter.
114200 Rev. A 2-15
Page 76
Installing and Operating BayStack ARN Routers
3. Ensure that the ARN boots correctly.
When the ARN boots, its LEDs flash in a particular order. See Chapter 3 for information on checking the ARN front-panel LEDs to ensure that the installation was successful and that the router is operating properly.
After the ARN boots using its local softw are image and configuration file, the Technician Interface login prompt appears.
4. Type the following command at the login prompt and press the Return
key:
Manager
Note the use of an uppercase “M.” The Technician Interface prompt (
Note: To check the contents of the router local file system on the installed
Flash memory card, type
dir and press the Return key. The arn.exe software
$) appears.
image, config file, and inst_arn.bat file should appear among the files listed.
5. Enter the following command and press the Return key to run the
Quick-Start script:
run inst_arn.bat
The Quick-Start script begins running.
6. Using your completed Quick-Start worksheet from Appendix B, enter the
appropriate network information as the prompts appear.
The ARN uses this information to configure interfaces to the network. Refer to Appendix B for sample Quick-Start screen output and for
information on using Quick-Start commands.
7. Choose whether you want to configure another module/port.
Entering interface prompt. Entering
n stops the Quick-Start script and returns you to the Technician
y allows you to configure another module/port.
Once the install script completes, the ARN starts bridging and routing traffic.
Contact your network administrator to verify that the ARN is now connected to the network. Your network administrator can refer to Configuring Remote Access to troubleshoot any problems.
2-16 114200 Rev. A
Page 77
Contact your local Bay Networks Technical Response Center if you need additional assistance.
After configuring the ARN network interface, you can replace the console connection with a modem connection to enable remote dial-in access.

Where to Go Next

Use the following table to determine where you want to go next.
For information about Go to
Installing the ARN Chapter 1 Operating the ARN Chapter 3 Configuring the ARN for Netboot and Directed
Netboot Using Local Boot (the Quick-Start Procedure) Appendix B ARN Technical Specifications Appendix C
Starting the ARN
Appendix A
114200 Rev. A 2-17
Page 78
Page 79
Chapter 3
Operating the ARN
This chapter describes how to
Locate and understand the function of base module LEDs
Use the expansion module and adapter module LEDs to check the status of various interfaces
Ensure a successful installation using the base module LEDs
Power on and off the ARN
Reset the ARN
Remove a Flash memory card
Protect the files on the Flash memory card
114200 Rev. A 3-1
Page 80
Installing and Operating BayStack ARN Routers
Run
Boot
Fail
Pwr
RPS
Fan
Base
Adapter1
Adapter2
Expansion
DCM
PCMCIA
AUI

LED Descriptions

LEDs on the ARN front and back panels pro vide information about how the ARN is operating. The following sections describe the LEDs on the ARN base modules, expansion modules, adapter modules, and the ARN back panel.

Base Module LEDs

The ARN base module LEDs include diagnostic LEDs and either Ethernet or token ring interface LEDs.
Diagnostic LEDs
The base module diagnostic LEDs (F itself. All of these LEDs light briefly when you plug the ARN into the wall outlet and turn on the power switch.
U
D
1
2
ISDN BRI
withNT1
RLSD
B1
DD
B2
COM
Serial
Figure 3-1. ARN Base Module Diagnostic LEDs
10BaseT
Tx
Rx
Cl
10BaseT
Tx
Rx
Cl
AUI
Ethernet 2
AUI
Ethernet 1
RLSD3
RLSD4
RLSD5
Run
Boot
Fail
igure 3-1) indicate the status of the ARN
COM3 COM4 COM5
Serial
Pwr
Base
Expansion
RPS
Adapter1
DCM
Fan
Adapter2
PCMCIA
BayStack Advanced Remote Node
ARN0059A
3-2 114200 Rev. A
Page 81
Operating the ARN
Table 3-1 describes the base module diagnostic LEDs.
Table 3-1. Base Module Diagnostic LEDs
LED Meaning
Run Flashes for 1 to 3 minutes, indicating that diagnostic tests are
running. When it lights again and remains on, the ARN is operational.
Boot Lights for 1 to 3 minutes, indicating that diagnostic tests were
successful and the ARN is booting. Fail Lights again and remains on when diagnostic failure occurs. Pwr Lights and remains on when the ARN is on and receiving
power. RPS Lights and remains on when the redundant power supply
(optional) is operating. Fan Lights and remains on when the ARN cooling fan is operating. Base Lights and remains on when the base module is operating
properly . Flashes slowly to indicate that the module is running
its diagnostic tests. Flashes rapidly to indicate that the module
failed its diagnostic tests. Adapter1 Lights and remains on when adapter module #1 is operating
properly . Flashes slowly to indicate that the module is running
its diagnostic tests. Flashes rapidly to indicate that the module
failed its diagnostic tests. Adapter2 Lights and remains on when adapter module #2 is operating
properly . Flashes slowly to indicate that the module is running
its diagnostic tests. Flashes rapidly to indicate that the module
failed its diagnostic tests. Expansion Lights and remains on when an expansion module is installed
and operating properly. Flashes slowly to indicate that the
module is running its diagnostic tests. Flashes rapidly to
indicate that the module failed its diagnostic tests. DCM Lights and remains on when an RMON DCM is installed and
operating properly. Flashes slowly to indicate that the module
is running its diagnostic tests. Flashes rapidly to indicate that
the module failed its diagnostic tests. PCMCIA Lights and remains on when the ARN contains a flash
memory card in its PCMCIA slot.
114200 Rev. A 3-3
Page 82
Installing and Operating BayStack ARN Routers
Ethernet LEDs
able 3-2 describes the base module Ethernet LEDs.
T
Table 3-2. Base Module Ethernet LEDs
LED Meaning
Tx (Transmit)
Rx (Receive)
Cl (Collision)
Lights when the Ethernet interface transmits data.
Lights when the Ethernet interface receives data.
Lights when the Ethernet interface detects a collision.
Token Ring LEDs
able 3-3 describes the base module token ring LEDs.
T
Table 3-3. Base Module Token Ring LEDs
LED Meaning
RCVR (Receiver)
NSRT (Insert)
WFLT (Wire Fault)
Lights when the interface is connected to the network.
Lights when you insert the ARN into the token ring network.
Lights when the token ring hardware detects a wire fault
condition.
3-4 114200 Rev. A
Page 83

Expansion Module LEDs

An ARN expansion module can contain Ethernet, token ring, or serial interface LEDs.
Ethernet LEDs
able 3-4 describes the expansion module Ethernet LEDs.
T
Table 3-4. Expansion Module Ethernet LEDs
LED Meaning
Operating the ARN
Tx (Transmit)
Rx (Receive)
Cl (Collision)
Lights when the interface is transmitting data over the
network.
Lights when the interface is receiving data from the network.
Lights when the interface detects a collision on the network.
Token Ring LEDs
able 3-5 describes the expansion module token ring LEDs.
T
Table 3-5. Expansion Module Token Ring LEDs
LED Meaning
RCVR (Receiver)
NSRT (Insert)
WFLT (Wire Fault)
Lights when the interface is connected to the network.
Lights when you insert the ARN into the Token Ring network.
Lights when the Token Ring hardware detects a wire fault
condition.
114200 Rev. A 3-5
Page 84
Installing and Operating BayStack ARN Routers
Serial LEDs
able 3-6 describes the expansion module serial interface LEDs.
T
Table 3-6. Expansion Module Serial LEDs
LED Meaning
RLSD3 (Received Line Signal Detection 3)
RLSD4 (Received Line Signal Detection 4)
RLSD5 (Received Line Signal Detection 5)

Adapter Module LEDs

An ARN adapter module can contain serial, ISDN, DSU/CSU, or V.34 modem LEDs.
Serial LED
able 3-7 describes the serial adapter module LED.
T
Table 3-7. Serial LED
LED Meaning
RLSD (Received Line Signal Detection)
Lights when Received Line Signal Detection is active on
COM 3.
Lights when Received Line Signal Detection is active on
COM 4.
Lights when Received Line Signal Detection is active on
COM 5.
Lights when Received Line Signal Detection is active on the
serial interface.
3-6 114200 Rev. A
Page 85
Operating the ARN
ISDN BRI LEDs (S/T or U Interfaces)
able 3-8 describes the ISDN adapter module LEDs.
T
Table 3-8. ISDN BRI LEDs
LED Meaning S/T Interface
Unlabeled LED Lights when the ARN is using the D-channel.
U Interface
D (D-channel; 16-KB Management Channel)
DD (Data Detect)
B1 (B-Channel #1; 64-KB Data Channel)
B2 (B-Channel #2; 64-KB Data Channel)
Lights when the ARN is using the D-channel.
Lights when the interface detects connection to an external
device (that is, a switch).
Lights when the ARN is using B-channel #1.
Lights when the ARN is using B-channel #2.
DSU/CSU LEDs
T
able 3-9 describes the DSU/CSU adapter module LEDs.
Table 3-9. DSU/CSU LEDs
LED Meaning
TxD (Transmit Data)
RxD (Receive Data)
CD (Carrier Detect)
Test Lights when the interface is in test or loopback mode.
Lights when the interface transmits data over the network.
Lights when the interface receives data from the network.
Lights when the interface detects a connection to another
device.
114200 Rev. A 3-7
Page 86
Installing and Operating BayStack ARN Routers
V.34 Modem LEDs
able 3-10 describes the V.34 modem adapter module LEDs.
T
Table 3-10. V.34 Modem LEDs
LED Meaning
TX (Transmit)
RX (Receive)
RLSD (Received Line Signal Detection)
DTR (Data T erminal Ready)

Back-Panel LEDs

The ARN back-panel allows for an optional V.34 Modem Adapter module. Refer to the previous section, “V.34 Modem LEDs,” for more information about these LEDs.
Lights when the interface transmits data over the network.
Lights when the interface receives data from the network.
Lights when the modem activates.
Lights when the interface is ready to transmit data.
3-8 114200 Rev. A
Page 87

Ensuring a Successful Installation

After connecting the ARN to the netw ork, you can ensure a successful installation by checking the diagnostic LEDs on the front panel of the base module (refer to
igure 3-1).
F
When you power on the ARN, the following sequence of front panel LED activity should occur:
All base module LEDs light momentarily; this tests that the LEDs are operational.
The Run, Boot, and Fail LEDs count through a short, initial startup sequence.
The Pwr (power) LED lights and remains on.
The Run LED begins flashing and continues to flash until the ARN completes all diagnostic tests.
As the diagnostic procedure tests each module, the LED representing that module flashes slowly. If the module passes its diagnostic test, the LED remains on. If the module fails its diagnostic test, the Fail LED remains on and the module LED flashes rapidly.
Operating the ARN
After completing the diagnostic testing procedure, the boot process begins. The Run and Boot LEDs indicate the boot status as shown in T
Table 3-11. Boot Status LEDs
Boot Status Run LED Boot LED
Local Boot Off On Netboot (attempting) Off Flashing Netboot (downloading) Flashing On Interrupted (using ARN monitor) Flashing Flashing
able 3-11.
After the boot process completes, the Run LED lights and the Boot LED turns off, indicating that the ARN is operational.
If the LEDs on the ARN light in this sequence, your installation is successful. Contact your network administrator to verify that the ARN is now connected to the network.
114200 Rev. A 3-9
Page 88
Installing and Operating BayStack ARN Routers
If the LEDs do not light in this sequence, your network administrator can refer to Configuring Remote Access to help troubleshoot the problem.
Note: If the ARN does not contain an expansion module, an adapter module, a
redundant power supply, a data collection module, or a Flash card, the LEDs associated with these components remain off.
If you need additional assistance, contact your local Bay Networks Technical Response Center.

Powering On and Off the ARN

The ARN power switch is located on the back panel (Figure 3-2). To power on an ARN, press the power switch to the ON position (1). To power off the ARN, press the power switch to the OFF position (0).
Note: To ensure a complete po wer cycle, we recommend that you w ait at least
4 seconds between powering off the ARN and powering it back on.
Power switch
U
L
100-240~
1.2A
50-60Hz
U
L
Redundant Power
Console Modem
ARN0019A
Figure 3-2. ARN Power Switch
3-10 114200 Rev. A
Page 89

Resetting the ARN

The Reset button is set inside the ARN back panel and resides next to the Flash card slot, as shown in Figure 3-3.
U
L
100-240~
1.2A
50-60Hz
U
L
Operating the ARN
Redundant Power
Console Modem
Figure 3-3. ARN Reset Button
To press the Reset button, insert a small pointed object (for example, a paper clip) into the Reset button hole.
You can use the Reset button to reboot the ARN hardware without cycling power,
as follows:
•To warm-boot the ARN (no diagnostic tests run), press the Reset button for less than 5 seconds.
•To cold-boot the ARN (diagnostic tests run), press the Reset button for more than 5 seconds.
Note: If you reset the ARN while it is running its diagnostic tests, the LEDs
remain in the state they were in when you pressed the Reset button. You must cycle power on the ARN to reset the LEDs.
Reset button
ARN0052A
114200 Rev. A 3-11
Page 90
Installing and Operating BayStack ARN Routers

Removing a Flash Memory Card

To remove a memory card from an ARN:
1. Press the Eject button next to the card receptacle on the back panel.
2. Pull the memory card out of the card receptacle.
See F
igure 3-4.
Caution: Do not remo v e the Flash memory card while the router is operating.
Removing the memory card interferes with current networking operations.
U
L
Redundant Power
100-240~
1.2A
50-60Hz
U
L
Console Modem
2
1
ARN0053A
Figure 3-4. Removing an ARN Flash Memory Card
To insert another memory card into the receptacle, refer to “Installing the Flash Memory Card” in Chapter 2.
When you remove a formatted memory card, the NVFS automatically removes access to the card. When you insert and format a card or insert an already formatted card, the NVFS automatically provides access.
3-12 114200 Rev. A
Page 91

Protecting Memory Card Files

Bay Networks ships each memory card with its Read/Write Protect switch in the unprotected position (F and saving your configuration, you may want to write-protect the memory card for backup purposes.
Note: You typically do not operate the ARN with a write-protected memory
card. We recommend making a copy of your configuration on another memory card, write-protecting the card, and storing it in a safe place.
To change memory card protection, complete the following steps:
1. Remove the memory card as described in the previous section.
2. Adjust the read-write protect switch, which is located on the edge
opposite the INSERT arrow of the memory card (F
igure 3-5). After successfully loading the configuration file
Operating the ARN
igure 3-5).
Unprotected
Protected
6948
Figure 3-5. Memory Card Read/Write Protect Switch
Reinsert the memory card into the card receptacle.
3.
114200 Rev. A 3-13
Page 92
Installing and Operating BayStack ARN Routers

Where to Go Next

Use the following table to determine where you want to go next.
For information about Go to
Installing the ARN Chapter 1 Starting the ARN Chapter 2 Configuring the ARN for Netboot and Directed
Netboot Using Local Boot (the Quick-Start Procedure) Appendix B ARN Technical Specifications Appendix C
Appendix A
3-14 114200 Rev. A
Page 93
Appendix A
Configuring the ARN for Netboot and
Directed Netboot
The following commands configure the ARN for netboot and directed netboot:
Use the i network. You need this information to complete the procedure in “Continuing with Netboot” in Chapter 2.
Use the software image and configuration file. You need this information to complete the procedure in “Continuing with Directed Netboot” in Chapter 2.
Contact your network administrator for additional assistance in determining the appropriate at your site. (Your network administrator has information on these commands in Configuring Remote Access.)
fconfig command to configure the router initial IP interface to the
bconfig command to specify the location and name of the ARN
ifconfig command and bconfig commands that you need for the ARN
Using the ifconfig Command
A router interface cannot communicate in an IP network without an IP address. Because an ARN netboots over one of its serial, DSU/CSU, Ethernet, or Token Ring links, the netboot interface must have a valid IP address.
You use the
Configure the router’s initial IP interface to the network. (The initial IP interface should be a serial interface if you are using EZ-Install.) You also use the same procedure to configure other serial interfaces for the netbooting procedure.
ifconfig command to do the following:
Configure Ethernet or token ring interfaces for the netbooting procedure.
114200 Rev. A A-1
Page 94
Installing and Operating BayStack ARN Routers
Enable or disable netbooting on an interface.
The following sections describe each use of the
ifconfig command.
Configuring an IP Serial or DSU/CSU Interface for Netbooting
Configure a serial or DSU/CSU (COM) interface to the IP network using the following interface configuration command:
ifconfig [
hop address>
The synchronous options variable indicates some combination of the following settings:
-d | -fr [-annexd | -lmi | -annexa] | -int_clk]
[
Note: Make sure to separate command options with spaces.
T
able A-1 describes the ifconfig command arguments for configuring a COM
interface.
Table A-1. ifconfig Command Settings for a COM Interface
synchronous options] <interface> [<IP address> <subnet mask> [<next
]]
Setting Description
Default Setting
-d Resets the router IP interface settings to the default values. This
setting tries four W AN configur ations in the f ollowing order until it finds the correct type for the router connection to the network:
1. Bay Networks HDLC encapsulation (also referred to as Bay Networks Standard Point-to-Point) with external clocking
2. Frame Relay Annex D
3. Frame Relay LMI
4. Frame Relay Annex A
(continued)
A-2 114200 Rev. A
Page 95
Configuring the ARN for Netboot and Directed Netboot
Table A-1. ifconfig Command Settings for a COM Interface
Setting Description
Frame Relay Settings
-fr Configures the router COM interface as a Frame Relay connection.
With this setting, use one of the following options to specify a DLCMI setting: -annexd, -annexa, or -lmi.
-annexd
-annexa
-lmi
-int_clk Sets the serial interface to internal clocking at 1.25 MB/s. If y ou do not
<interface>
<IP address>
<subnet mask>
<next hop address>
When one of these options is used with the -fr setting, it specifies a DLCMI setting. Use the same setting as the network to which the router’s Frame Relay interface is connected. The default setting for Frame Relay is -annexd.
Internal Clocking Setting
specify this setting, the router defaults to external clocking.
IP Connector Setting
Specifies the IP connector you are configuring. Use the format com<
port #
>.
IP Address Settings
Specifies the IP address of the interface you set with Provide this address in dotted decimal notation.
Specifies the IP subnet mask of the interface you set with Provide this address in dotted decimal notation.
Specifies the IP address of the next-hop router. Provide this address in dotted decimal notation. Specify this address only if there are intermediate routers between the router and the BootP server.
(continued)
<interface>
<interface>
.
.
114200 Rev. A A-3
Page 96
Installing and Operating BayStack ARN Routers
Configuring an Ethernet Interface for Network Booting
To configure an ARN Ethernet interface for network booting, use the following command format:
ifconfig [-d]
<interface> [<IP address> <subnet mask> [<next hop address>
]]
Table A-2 describes the ifconfig command arguments for configuring the router’s
Ethernet interface.
Table A-2. ifconfig Command Settings for an Ethernet Interface
Setting Description
Default Setting
-d Resets the router IP interface settings to the default values. Resetting
an Ethernet interface makes it inactive in the network booting process. (The output of the getcfg command shows the default as None.)
IP Connector Setting
<interface>
<IP address>
<subnet mask>
<next hop address>
Specifies the IP connector you are configuring. Use the format xcvr<
port
#>.
IP Address Settings
Specifies the IP address of the interface you set with Provide this address in dotted decimal notation.
Specifies the IP subnet mask of the interface you set with Provide this address in dotted decimal notation.
Specifies the IP address of the next-hop router. Provide this address in dotted decimal notation. Specify this address only if there are intermediate routers between the router and the BootP server.
<interface>
<interface>
.
.
A-4 114200 Rev. A
Page 97
Configuring the ARN for Netboot and Directed Netboot
Configuring a Token Ring Interface for Network Booting
To configure an ARN token ring interface for network booting, use the following command format:
ifconfig [-d] [ -r<
address>
]]
speed
> ]
<interface> [<IP address> <subnet mask> [<next hop
Table A-3 describes the ifconfig command arguments for configuring the router
token ring interface.
Table A-3. ifconfig Command Settings for a Token Ring Interface
Setting Description
Default Setting
-d Resets the router IP interface settings to the default values. Resetting
a Token Ring interface makes it inactive in the network booting process. (The output of the getcfg command shows the default as None.)
IP Connector Setting
-r
<speed>
<interface>
<IP address>
<subnet mask>
<next hop address>
Specifies the speed of the Token Ring interface. Enter either 16 or 4 (Mb/s). The default is 16 Mb/s.
Specifies the IP connector you are configuring. Use the format mau<
port
#>.
IP Address Settings
Specifies the IP address of the interface you set with Provide this address in dotted decimal notation.
Specifies the IP subnet mask of the interface you set with Provide this address in dotted decimal notation.
Specifies the IP address of the next-hop router. Provide this address in dotted decimal notation. Specify this address only if there are intermediate routers between the router and the BootP server.
<interface>
<interface>
.
.
114200 Rev. A A-5
Page 98
Installing and Operating BayStack ARN Routers
Enabling and Disabling Interfaces with ifconfig
To enable or disable an ARN interface for the network boot process, use the following command formats:
ifconfig -disable ifconfig -enable
<interface>
<interface>
Table A-4 describes the ifconfig command arguments for enabling and disabling
interfaces for network booting.
Table A-4. ifconfig Settings to Enable and Disable Netboot Interfaces
Setting Description
<
interface>
Specifies the IP connector you are enabling or disabling for network
booting. Use one of the following formats:
xcvr com mau
ifconfig Command Examples
1. Configure the current interface for the default Netboot procedure.
ifconfig -d
2. Specify the IP address and subnet mask of the base module Ethernet interface.
ifconfig xcvr1 21.3.5.62 255.255.255.0
<port #> <port #> <port #>
3. Specify the IP address and subnet mask of the expansion module Ethernet interface.
ifconfig xcvr2 21.3.5.61 255.255.255.0
4. Configure the IP address and Frame Relay DLCMI of the third serial interface on the expansion module.
ifconfig com3 21.3.5.62 -fr -annexa
5. Specify the IP address and subnet mask of the base module token ring interface.
ifconfig mau1 21.3.4.77 255.255.255.0
A-6 114200 Rev. A
Page 99
Configuring the ARN for Netboot and Directed Netboot
Using the bconfig Command
To use netboot, you use the bconfig command to specify that the ARN configuration file or software image resides on the network. To use directed netboot, you use the the full pathname to the software image and configuration file. To use local boot, you use the
bconfig command to specify that the configuration file and software
image both reside on the local file system (that is, the PCMCIA Flash card).
bconfig Command Format
To configure an interface for netboot, use the following format for the bconfig command:
bconfig -d [image | config]
To configure an interface for directed netboot, use the following format:
bconfig command to specify the IP address of the server and
bconfig [image | config] [local | network [
You must use the
bconfig command twice: once to specify the location of the
<TFTP host> <TFTP pathname>
software image, and again to specify the location of the configuration file. Refer to T
Table A-5. bconfig Command Settings
Option Description
image Indicates the router’s software image. config Indicates the router’s configuration file. local Indicates that the specified file (image or config) resides in the router’s local file system. network Indicates that the specified file (image or config) resides on a remote file system.
<TFTP host>
<TFTP pathname>
-d Reverts to the default values for the software image or configuration file and nullifies any
Specifies the IP address of the TFTP server. If both the software image and configuration file are on the network, both files must reside on the same host.
Specifies the complete pathname of the remote software image or configuration file.
previously specified IP address and pathname for the file, thus disabling directed netboot.
able A-5 for a complete description of the bconfig command.
]]
114200 Rev. A A-7
Page 100
Installing and Operating BayStack ARN Routers
bconfig Command Examples
1. Configure the default netboot procedure -- use a local image file and look for the configuration file over the network using BootP.
bconfig -d image (or bconfig image local) bconfig -d config (or bconfig config network)
2. Use netboot for both the boot image and configuration file.
bconfig image network bconfig config network
3. Use a local configuration file and directed netboot for the boot image file.
bconfig image network 21.3.5.62 /usr/mykernel.exe bconfig config local
4. Use a local boot image file and directed netboot for the configuration file.
bconfig image local bconfig config network 21.3.5.62 /usr/arnstartup/config
5. Use directed netboot for both the boot image and configuration file.
bconfig image network 21.3.5.62 /usr/mykernel.exe bconfig config network 21.3.5.62 /usr/arnstartup/config
Verifying Your Configuration
You can use the getcfg command to verify
Whether the router is set to boot using a local or remote software image
Whether the router is set to configure using a local or remote configuration file
The configuration of any serial, DSU/CSU, Ethernet, and token ring connectors
Enter the following command to display the ARN startup options:
getcfg
A-8 114200 Rev. A
Loading...