Avaya Bay Command Console BCC User Manual

Using the Bay Command Console (BCC)

BayRS Version 13.00 Site Manager Software Version 7.00

BCC Version 4.05

Part No. 303562-A Rev. 00 October 1998

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

and recomm endations 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 appli cations of any products s pecified 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 te rms of that license. A summary of the S oftware License is included in this document.

Trademarks

ACE, AN, BCN, BLN, BN, FRE, Optivi ty, PPX, Quick2Config, and Bay Networks are registered trademarks and Advanced Remote Node, ANH, ARN, ASN, BayRS, BaySecure, BayS tack, BCC, SPEX, System 5000, and the Bay Networks logo are trademarks of Bay Networks, Inc.

Microsoft , MS, MS-DOS, Win32, Windows, and W indows NT are r egistered tr ademarks of Microsoft Corporation. All other trademarks and registered trademarks are the property of their respective owners.

Restricted Rights Legend

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

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

Statement of Conditions

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

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

Portions of the code in this software product may be Copyright © 1988, Regents of the University of California. All rights reserved. Red istribution and use in source and binary forms of such portions are permit ted, 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 deve loped by the Uni versity 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 IMPLIE D WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

In additi on, the program and information contained herein are lice nsed only pursuant to a license agreement that contains restrictions on use and discl osure (that may incorporate by reference certain limitations and notices imposed by thir d pa rt ie s).

303562-A Rev. 00

Bay Networks, Inc. Software License Agreement

NOTICE: Please carefully read this license agreement before copying or using the accompanying software or instal ling the hardware unit w ith pre-enabled software (each of w hich is referred to as “Software” in this Agree m ent). BY COPYING OR USING THE SOFTWARE, YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS A GREEM ENT ARE THE ONLY TERMS UNDER WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these terms and conditions, return the product, unused and in the original shipping container, within 30 days of purchase to obtain a credit for the full purchase price.

1. License Grant. Bay Networks, Inc. (“Bay Networ ks”) grants the end user of the Softwar e (“Licensee”) a personal, nonexcl usive, nontransferab le license: a) t o use the Software either on a singl e com puter or, if applicable, on a single authori zed de vi ce ide ntified by hos t ID, fo r whi ch it wa s ori gi nal ly acq uir ed ; b) to cop y th e Sof tw ar e so lely f or bac kup purposes in support of author ized use of the Software; and c) to use and copy the associated user manual solely i n support of authorized use of the Software by Licensee. This license applies to the Software only and does not extend to Bay Networks Agent softw are or other Bay Networks softw are products. Bay Networks Agent software or other Bay Networks software products are licensed for use under the terms of the applicable Bay Networks, Inc. Software License Agreement that accompanies such software and upon payment by the end user of the applicable licen se fees for such software.

2. Restrictions on use; reservation of rights. The Software and user manuals are protected under copyr ight laws. Bay Networks and/or its licensors retai n all title and ownership in bot h the Software and user manuals, including any revis ions made by Bay Networks or its li censors. The copyright noti ce m ust be reproduced and included with any copy of any por tion of the Sof tw are or use r manua ls . Licens ee may not modif y, trans late , dec ompi le, di sas semb le, use for any compe ti ti v e an al ysis, r e v erse e ngi ne er , dis tr ib ute , o r c rea te der i vativ e w ork s fro m th e Sof twa re or u se r man ual s or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer the Softw are or user manual s, in whole or in part. The Software and user manuals embody Bay Networks’ and its licenso rs’ confident ial and proprietary intellectual property. Licensee shall not sublicense, assign, or other w ise disclos e to any third pa rty the Software, or any information abou t the operation, design, performance, or implementation of the Software and us er manuals that is confidential to Bay Networks and its li censors; how ever, Licensee m ay grant permission to its consul tants, subcontractors , and agents to use the Software at License e’s facility, provided they have agreed to use the Software only in accordance with the term s of this license.

3. Limited warranty. Bay Networks warrants each item of Softwa re, as delivered by Bay Networks and properly installed and operated on Bay Networks har dw are or other equipment it is ori ginally licensed for, to function substantially as descri bed in its accomp anying user manual during its warranty period, which begi ns on the date Softwar e is fi r st shi pped to Licen see . If any it em of Soft war e fai ls to so func ti on du ring i ts warr anty pe ri od, as t he so le remedy Bay Ne tworks will at its discretion provide a suitable fi x, patch, or workaround for the problem that may be included in a future Software release. Bay Networks further warrants to Licensee that the media o n which the Softwar e is provided will be free from defects in materials and workmans hip under norm al use for a period of 90 days from the date Software is first shi pped to Licensee. B ay Networks will replace defectiv e media at no charge if it is returned to Bay Networks during the warrant y period along with proof of the date of shipment. This w arranty d oes not apply i f the media has been d amaged as a result of accident, misuse, or abuse. The Licens ee assumes all responsibility for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained from the Software. Bay Ne tworks does not warrant a) tha t the functions contained in the software will meet the Licensee ’s requirements, b) that the Sof tware will operate in the hardware or software comb inations that the License e may select, c) that the operation of the Software will b e uninterrupted or error free, or d) that all defects in the operati on of the Softw are will be corrected. Bay Networks i s not obligated to remedy any Software defect that cannot be repro duced with the latest Software release. These warranties do not apply to the Software if it has been (i) altered, except by Bay Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’s product, resulting in the defect; or (iii) damaged by improper environment, abuse, mi suse, accident, or negligence. THE FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR I MPLIED, INCLUDI NG WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A P ARTICULAR PURPOSE. Licensee is responsible for the security of

303562-A Rev. 00

iii

its own data and inform ation and for mai ntaining adequate procedures apart from the Software t o reconstruct lost or altered files, data, or programs.

4. Limitation of liability. IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT EXCEED THE PRICE PAID TO BAY NETWORKS FOR THE SOFTWARE LICENSE.

5. Government L i c en s ees. This provision applies to all Software and documentation acquired directly or indirectly by or on behalf of the United States Government. The Software and documentation are commercial products, licensed on the open market at market p rices, and were developed ent irely at pri vate expense and without the use of any U.S. Government funds. The license to the U. S. Governmen t is granted only with restricted rights, and use, duplica tion, or disclos ure by the U.S. Go vernment is subject to the restrictions set forth in subparagraph (c)(1) of the Comm ercial Computer So ftware––Restricted Rights clause of FAR 52.227-19 and the limitations set out in this license for c ivilian agencies , and subparagra ph (c)(1)(ii) of the Rights in Technical Data a nd C om p uter Software clause of DFARS

252.227-7013, for agencies of the Department of Defen se or their successors, whichever is applicable.

6. Use of Software in the European Communit y. This pr ovision applies to all Software acquired for use within the European Comm unity. If Licensee uses the Software within a country in the European Com mu n ity, t he Software Directive enacted by the Council of European Communities Directive dated 14 May , 1991, will apply to the examination of the Softw are to facili tate interoperability. Licensee agrees to notify Bay Networks of any such intended examination of the Software and may procure support and assis tance from Bay Networks.

7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the Bay Networks copyright; those restrictions relating to use and discl osure of Bay Networ ks’ confidential information shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if Licensee fails to comply with any of the terms and conditions of the license. Upon termination for any reason, Licensee will immediately destroy or return to Bay Networks the Software, user manuals, and all copies. Bay Networks is not liable to Licensee for damages in any form so lely by reason of the terminati on of this license.

8. Export and Re-export. License e agrees not to export, directly or indirectly, the Software or related technical data or information without first obtaining any required export licenses or other governmental approvals. Without limiting the fore going, Licensee, on behalf of itself and its subsidiari es and affiliates, agrees that it wil l not, without first obtaining all export licenses and appr ovals required by the U.S. Governmen t: (i) export, re-export, transfer, or divert any such Sof tware or technical data, or an y direct product thereof, to any country to whi ch such exports or re-exports are rest ricted or embargoed under United States ex port control laws and regu lations, or to any national or resident of such rest ricted or embargoed countr ies; or (ii) provide the Software or related technical data or infor mation to any military end user or for any m ilitary end use, including the design, development, or production of any chemical, nuclear, or biological weapons.

9. General. If any provision of this Agreement is held to be invalid or unenforceable by a court of competent jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement will be governed by the laws of the state of California.

Should you have any quest ions concerning this Agreement, contact Bay Networks, Inc., 4401 Great America Parkway, P.O. Box 58185, Santa Clara, California 95054-8185.

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

303562-A Rev. 00

Preface

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

Text Convent io n s . .................. ......................................................... .................................xiv

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

Bay Networks Technical Publications ..............................................................................xvi

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

Chapter 1 Overview of the BCC

Platf o rm Requir e men ts ....................................................... ............................................1-2

Number of BCC Sessions ...............................................................................................1-2

Terminology and Concepts ................................................................................... ..........1-3

Configuration Hierarchy ............................................................................................1-3

Context .....................................................................................................................1-5

Objects, Classes, and Insta nces ........................................................ ......................1-6

BCC Instance Identifier ....................... ..... ..... .. ..... .. ..... ..... .. ..... .. ..... .. ..... ..... .. ..... .1-7

Global (Box-Wide) Objects ................................................................................1-7

Physical Device Objects ....................................................................................1-8

Parameters ............................................................................................................. 1-10

Required Parameters .......................... ..... ....... ....... ..... ....... ....... ....... ..... ....... ....1-10

Derived Parameters .........................................................................................1-10

Optional Parameters ........................................................................................1 -10

Chapter 2 Getting Started with the BCC

Entering and Exiting the BCC Interface ..........................................................................2-1

Displaying Context .......... ......................................................... .......................................2-3

Navigating in Configuration Mode .............................. ....... ....... ....... ..... ....... .. .......... ....... .2-3

Navigating with the back Command .................................. ..... .. ..... ..... .... ..... ..... .. ..... .2-3

Navigating with Configuration Commands ...............................................................2-4

303562-A Rev. 00

Moving Back One or More Levels ...................................................................... 2-4

Moving Back to Root Level ................................................................................2-5

Moving Forward One or More Levels .................................................................2-5

Moving to Any Context in the Device Configuration ...........................................2-6

Displaying Configuration Data ........................................................................................2-8

Displaying the Total Device Configuration ................................................................2-8

Displaying the Configuration of One Object ........................................................... 2 -10

Using Online Help .........................................................................................................2-11

Help Commands ....................................................................................................2-11

Help Command Examples ..................................................................................... 2 -13

Chapter 3 Entering Commands and Using Command Files

Entering Commands .......................................................................................................3-1

Using Command Abbreviations ................................................................................3-2

Recalling Commands ...............................................................................................3-2

Editing Command Lines ...........................................................................................3-3

Entering Multiple Commands on a Line ....................... .......... ....... .. ....... .......... ....... .3-4

Continuing a Command Line ....................................................................................3-4

System Commands ................................................................. ....... ....... ..... ....... ....... ......3-5

Configuration Command Syntax .....................................................................................3-5

Command Syntax Requi r e men ts ................................................................... ..........3-5

Using Basic (Full) Syntax .........................................................................................3-6

Using Default Syntax ................................................................................................3-7

Using Abbreviated Syntax ........................................................................................3-7

Specifyin g Parameter Values ...... ................... ......................................................... .3-8

Required, Derived, and Other Parameters ........................................................3-8

Specifying Multiple Parameter-Value Pairs ........................................................ 3-8

Disabling, Reenabling, and Deleting a Configured Object .....................................3-10

Creating and Using BCC Command Files ....................................................................3-10

Saving Commands to a File ...................................................................................3-11

Adding Comments to a Command File ..................................................................3-11

Entering Configuration Commands from a File ......................................................3-12

Saving the Active Configuration as a Bootable Binary File ....................................3 -12

303562-A Rev. 00

Chapter 4 Tutorial: Configuring a Network Device

Creating and Modifying a Device Configuration .............................................................4-1

Disabling a Configured Object ......................................................................................4-15

Enabling a Configured Object .......................................................................................4-16

Deleting a Configured Object .......................................................................................4-17

Appendix A System Commands

Appendix B TCL Support

Appendix C System show Commands

show console .................................................................................................................C-2

show hardware ..............................................................................................................C-5

show process .................................................................................................................C-7

show system ................................................................................................................C-10

Appendix D Syntax for Module Location

Index

303562-A Rev. 00

vii

Figures

Figure 1-1. The Technician Interface and the BCC Interface .....................................1-1

Figure 1 -2. Sample BCC Configuration ......................................................................1-4

Figure 1-3. Configuring IP and RIP on an Ethe rnet In te r face ......... ...........................1-5

Figure 1-4. Configuring IP and RIP on an Ethe rnet In te r face ......... ...........................1-6

Figure 2 -1. Moving Away from Root Level ..................................................................2-6

Figure 2-2. Navigating to an Object in the Configuration ...........................................2-7

Figure 2-3. Navigating with the BCC Recursive Search Feature ...............................2-8

Figure 2-4. Objects You Can Configure at the Next Level ........................................2-15

Figure 4-1. Sample BCC Configuration (BCN Router) ...............................................4-3

Figure 4-2. Typical BCC Configuration Cycle .............................................................4-4

303562-A Rev. 00

Tables

Table 2-1. BCC Help Commands ........................................................................... 2 -11

Table 3-1. Keystrokes for Editing BCC Command Lines ........................................... 3-3

Table 3-2. BCC Commands ....................................................................................3-10

Table A-1. System Commands ................................................................................ A-2

Table D-1. Syntax for Specifying Module Location per Device ................................D-1

303562-A Rev. 00

The BCC is a command-line interface for configuring Bay Networks devices. If you are responsible for configuring and managing Bay Networks® AN®, ANH™, ARN™, ASN™, BN® (BCN® and BLN®), or System 5000™ routers, read this guide to learn how to use the Bay Command Console (BCC™).

Before You Begin

This guide is intended for users who have some experience supporting a multivendor internetworking system. You should be able to perform network device configuration, maintenance, and troubleshooting.

Preface

303562-A Rev. 00

Because the BCC make s real -time c hanges to de vi ce c onf igura tion, B ay Networ ks recommends that you first le arn about BCC behavior on a devi ce not connected to your production netw ork.

xiii

Using the Bay Command Console (BCC)

Text Conventions

This guide uses the following text conventions:

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

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

<ip_address>

ping ping 192.32.10.12

you enter:

bold text

Indicates text tha t you need to enter and command names and options. Example: Enter

Example: Use the

show ip {alerts | routes

command.

dinfo

}

braces ({}) Indicate required elements in syntax descriptions

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

show ip {alerts show ip alerts or show ip routes

routes

, you must enter either:

}

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

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

, you can enter either:

show ip interfaces [-alerts show ip interfaces

]

show ip interfaces -alerts

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

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

xiv

ethernet/2/1 ethernet/2/1

needed.

parameter> <value>

] . . .

, you enter

and as many parameter-value pairs as

303562-A Rev. 00

Preface

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

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

show at <

valid_route

valid_route>

is one va riable and you subs titu te one value

for it.

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

system messages. Example:

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

vertical line ( | ) Separates choices for command keywords and

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

show ip {alerts | rou tes} show ip alerts

show ip routes

, you enter either:

, but not both.

303562-A Rev. 00

Using the Bay Command Console (BCC)

Acronyms

ARP Address Resolution Protocol ATM asynchronous transfer mode DCM data collection modul e DRAM dynamic random access memory IP Internet Protocol IPX Internetwork Packet Exchange LAN local area network MAC media access control OSPF Open Shorte st Path Fi rst RIP Routing Information Protocol SNMP Simple Network Management Protocol SRM-L system resource module- link TCP/IP Transmission Control Protoc ol/Internet Protocol TFTP Trivial File Transfer Protocol WAN wide area network

Bay Netwo rks Technical Publications

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

xvi

303562-A Rev. 00

You can purchase Bay Networks documentation sets, CDs, and selected te ch nical publications through the Bay Networks Collateral Catalog. The catalog is loc ated on the World Wide Web at support.baynetworks.com/catalog.html and is divided into sections arran ged alpha betically:

• The “CD ROMs” section lists available CDs.

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

• The “Technical Manuals” section li sts available print ed documentation sets. Make a note of the part numbers and prices of the items that you want to order.

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

How to Get Help

For product assista nce, support contracts, or informati on abou t educational services, go to the following URL:

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

Preface

303562-A Rev. 00

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

xvii

Chapter 1

Overview of the BCC

The BCC is a command-line interface for configuring Bay Networks devices. After logging on to a de vi ce, you access the BCC by ente ring the the Technician Interface prompt (Figure 1-1

Technician

Interface

command at

bcc

Figure 1-1. The Technician Interface and the BCC Interface

Access the BCC

BCC

BCC0001B

303562-A Rev. 00

1-1

Using the Bay Command Console (BCC)

From the

prompt, you can:

bcc>

• Execute any system command not classified as “Te chnician Interface only” (see Appendix A, “

• Execute configur ation commands to perfor m tasks such as creating or deletin g IP interfaces on the router. Enter BCC configuration mode by entering the

config

command at the bcc> prompt.

Note:

For a list of services you can configure using the BCC, see the Release

Notes. You can obtain a complete hierarchical listing of all object s

configurable on a device by entering the prompt.

Platform Requirements

The BCC runs on AN, ANH, ARN, ASN , System 5000, and BN platforms including ARE, FRE

• 16 MB of dynamic RAM (DRAM)

• 2 MB of free memory space available when you start the BCC

System Commands”).

help tree -all

, and FRE-2 processor modules. Each slot must have:

command at any BCC

If you try to start the BCC with insufficient DRAM or free memory on a slot, the BCC returns an error message. In that case, use Site Manager instead of the BCC.

Number of BCC Sessions

You can open one BCC session per slot in read-write (configur ation) mode. Other users can open additional BCC sessions in read-only (nonconfiguration) mode on the same slot, depending on available memory. Each BCC session is mutually exclusi ve. If you make a change during a BCC session in read-write mode, this change does not appear in other BCC sessions.

1-2

303562-A Rev. 00

Terminology and Concepts

This section describes key terms and concepts of the BCC interface.

Configuration Hierarchy

The BCC configuration hierarchy begins at a root-level object, called box for AN/ANH, ARN, and BN platforms, and stack for ASN and System 5000 platforms. Under the root- level object are branch obje cts such as interfaces and protocols that fan out from the root level in a tree hierarchy.

Overview of the BCC

You use the

help tree -all

and

show config -all

commands to display the

configura tion hierarchy of a Bay Networks route r.

• The

help tre e -all

command displays the hierarchy of every object you can

configure .

• The

show config -all

command displays the hierarchy of objects you have

configured.

Figure 1-2

illustrates a sample BCC conf igur ation for an AN, BN, or ARN router.

• Box contains the global ob jects IP, SNMP, T e lnet, and TFTP, plus the physical interface objects ethernet/2/1, ethernet/2/2, and serial/3/1.

• Global IP contains the global obje cts ARP, RIP, and OSPF.

303562-A Rev. 00

1-3

Using the Bay Command Console (BCC)

box

(root)

ospf

(protocol)

snmp

(protocol)

telnet

(protocol)

tftp

(protocol)

INTERFACE-SPECIFIC OBJECTS

(Services supported on a specific slot)

ethernet/2/1

(interface)

ethernet/2/2

(interface)

arp

(protocol)

rip

(protocol)

BOX-WIDE/GLOBAL OBJECTS (Services supported on all slots)

ip/1.2.3.4/255.0.0.0

(protocol)

ospf/1.2.3.4

(protocol)

arp/1.2.3.4/1

(protocol)

1-4

serial/3/1

(interface)

BCC0012C

Figure 1-2. Sample BCC Configuration

303562-A Rev. 00

Overview of the BCC

You use BCC commands to create new objects and to modify or delete objects in an existing conf iguration hierarchy. You begin at root level in BCC configur at ion mode and navigate to objects in the device configuration tree.

For example , on a BLN router, you can use BCC commands to add a ne w physi cal interface (such as Ether net) on box, add IP to the Ethernet interface, and then add RIP to IP on that inte rface . Figure 1-3

shows the sequence of commands

necessary to build this configuration.

box

box# ethernet/2/1

Ethernet

Slot 2

Connection 1

ethernet/2/1# ip address 1.2.3.4 mask 255.0.0.0

Address 1.2.3.4

Mask 255.0.0.0

Context

303562-A Rev. 00

ip/1.2.3.4/255.0.0.0# rip

rip/1.2.3.4

rip/1.2.3.4#

BCC0017A

Figure 1-3. Configuring IP and RIP on an Eth ernet Interface

Your working location within the BCC configuration tree is referred to as the context. Just as a UNIX file system has a current working directory within which you can add, modify, or delete files, the BCC configuration tree has a current working context, within which you can add, modify, disa ble, reenable, or delete objects.

1-5

Using the Bay Command Console (BCC)

The BCC underst ands the context of an object in terms of its loc ation along a path that begins at the root le v el of th e devic e conf igu rati on tree. Each semic olon in the path marks a transition from one level to the next branch level in the device configura tion tree. The semicolon is also equivalent to a Return key entered at the end of a command, effectively starting a new command line.

For example, if you conf ig ure an IP interface (address 1.2.3.4, mask 255.0.0.0) on ethernet/2/1 of a BLN router, the BCC understands its location as box; ethernet/2/1; ip/1.2.3.4/255.0.0.0 (Figure 1-4.

box

box# ethernet/2/1

ethernet/2/1

ethernet/2/1# ip address 1.2.3.4 mask 255.0.0.0

ip/1.2.3.4/255.0.0.0

ip/1.2.3.4/255.0.0.0#

Figure 1-4. Configuring IP and RIP on an Eth ernet Interface

Objects, Classes, and Instances

In BCC terminology, configurabl e entities are referred to as objects of a pa rticular class, each of which constitutes an insta nce.

•An object is a configur abl e physical or logical entity such as a physical interface or a pr otocol on an interface. Every configur ab le object belongs to a specific class that defines its characteristics.

•A class is a template for a configurable object (such as Ethernet or the protocol IP). When you add a new object to the configuration of a device, the BCC creates a copy (an instance) of the ap propriate template.

1-6

BCC0017B

303562-A Rev. 00

Overview of the BCC

• An instance is an object uniquely identifiable within the total device configura tion. Each instance is identified by its BCC instance identifier.

BCC Instance Identifier

A BCC instance identif ier uniquely identifies a single instance of an object configure d on a devic e. The BCC inst ance ID consi sts typi call y of the name of the object, combined with the values you specify for its required parameters. For example, the BCC instance ID for an Ethernet interface on a BN platform consists of

ethernet/

<slot>/<connector>, as in

ethernet/2/1

For some objects, the BCC automatically appends an internally generated number to ensure the uniqueness of the BCC instance ID. For example, the BCC creates an instance ID for ARP on IP based on the object name (arp), plus the address of the underlying I P interface (1.2.3.4), plus an internally generate d inte ger, resulting in an ID such as

arp/1.2.3.4/1

In other rare c ases , a con figu rabl e obj ec t m ay also have requi red p aram et er s th at do not become part of its BCC instance ID. For e xample, the global OSPF object has a required router-id parameter that doe s not become part of the instance ID. (Many such required parameters end in “-id,” such as global-id and router-id.)

303562-A Rev. 00

Each object has its own requirements for unique instance identification within the total devi ce configuration.

Global (Box-Wide) Objects

Global (or box-wide) objects provide services uniformly to all slots of a network device. Examples include global IP, BGP, TCP, SNMP, FTP, TFTP, and Telnet. Some protocols, such as IP, RIP, and OSPF, have global and int erface-level objects.

1-7

Using the Bay Command Console (BCC)

Physical Device Objects

The followin g sections provide BCC terms for the physical device.

Box

The BCC uses the term box to identify the chassis for a Bay Networks nonstackable device. Every box has a type parameter; the value assigned to the type parameter identifies the type of Bay Networks device. For example, the type parameter has the value “an” for an AN router and the value “frecn” for a BCN router with a FRE controller module.

Board

The BCC uses the term board or module to identify any logic or circuit board in a Bay Networks devic e. Each board typically occupies a slot in a network device. On some Bay Networks products, one board may contain another board such as an RMON data collection module (DCM). All board objec ts have a type parameter that identifies the module type. For example, “qenf” is the value of the type parameter for a Quad Ethernet with hardware filters module.

1-8

For module desc riptions based on the literal value of the type parameter

Note:

for any board object, see the Release Notes.

Slot

The BCC uses the term slot to identify the location, as well as a physic al and electrical means, for attaching modules to logic and power connections available on the device chass is.

• Multislot de vices such as the BLN or BCN router accommodate one system (SRM-L) or link (interface) module per slot.

• Single-slot de vic es such as the AN, ASN, and ARN router s accommodate one base module (in slot 1), one or two adapter modu les, and one expansion module.

303562-A Rev. 00

Overview of the BCC

Connector

The BCC uses the term connector to identify the physical and electrical means to interconnect a networ k device directly or indirectly to a physical layer transmission medium.

Line

The BCC uses the term line to identify the physical (and in some cases, logical) circuit identi fied typically by means of a slot, connecto r, interface type (et hernet, sync, fddi, and so on), and, where applicable, a channel number (such as with T1/E1 interface types).

Port

The BCC uses the term port to identify an interface object defined by its type (for example, an Ethernet port) and location (slot and connector) within a network device. On a network device, a port is also a logical point of termina tion for data sent or received by a specific protocol or application.

Interface

303562-A Rev. 00

The BCC uses the term interface to identify circuitry and digital logic associated with the interconnect ion be tween a physical network medium (such as Ethernet) and a higher-la yer protocol entity (such as IP).

Note:

A logical interfa ce is an addressable entity for originating and

terminating connections across an IP network.

1-9

Using the Bay Command Console (BCC)

Parameters

A parameter is an attribute (or property) of a configurable object. Parameters can be classif ied as one of the following:

• Required

• Derived

• Optional

Required Parameters

For any BCC object, required parameters are a minimum set of parameters for which the BCC requires you to supply va lue s. For example, the required parameters of a physical por t are slot and connector.

Derived Parameters

Derived parameters are parameters for which the BCC supplies a value. For example, a derived parameter of the global OSPF object is router-id. In this c ase, the BCC deriv es a value for router-id from the address of the first IP interface configured on the device.

1-10

Optional Parameters

Optional parameters are parameters for which you can specify customized values, replacing any defa ult values set by the syste m. For example, an optional parameter of an Ethernet interface is bofl-retries. This parameter normally has a default value of 5 (5 retries) , but you can change this to another numeric value .

303562-A Rev. 00

Chapter 2

Getting Started with the BCC

This chapter provides information about the following topics:

Topic Page

Entering and Exiting the BCC Interface Displaying Context 2-3 Navigating in Configu ration Mode 2-3 Displaying Configu ration Data 2-8 Using Online Help 2-11

Entering and Exiting the BCC Interface

To access the BCC interface on a Bay Networks router:

Open a Technician Interface session with the target router.

For detailed inf ormation about opening a Technician Interface session, see Using Technician Interface Software.

Enter the

Manager

your Telnet or console display.

The Manager login allows you to enter any system command and allows read-write access to the device configuration. The User login allows you to enter only user-level system command and allows read-only access to the device configuration.

command at the

User

prompt that appears on

2-1

303562-A Rev. 00

2-1

Using the Bay Command Console (BCC)

Enter

Router1> bcc

Welcome to Bay Command Console!

* To enter configuration mode, type config

* To list all system commands, type ?

* To exit the BCC, type exit

bcc>

Start BCC configuration mode by entering

bcc> config box#

at the Technician Interface prompt.

bcc

config

at the

bcc>

prompt.

You enter configuration mode at the roo t (box) level of the BCC conf igura tion tree. The prom pt ends with a pound symbol (#) if you ha ve read-write privileges (Manager only), or with a greater than symbol (>) if you have read-only privileges (Manager or User).

If you enter BCC configuration mode as Manager and want to change your privilege level for the current session from read-write to read-only, enter

config -read-only config -read-write

. To change Manager privileges back to read-write, enter

. You cannot change your privi lege level from read-only to

read-write if you logged in as User.

2-2

Caution:

When you enter BCC configuration commands with read-write

privileges, you immediately modify the device configuration.

When you f inish using BCC configuration mode, enter the

command

exit

at any prompt.

box# exit bcc>

When you finish using the BCC, enter the

command at the

exit

bcc>

prompt.

bcc> exit Router1>

Exiting the BCC returns you to the Technician Inte rface prompt.

For more detailed information about Technician Interface access, login, or logout procedures, see Using Technician Interface Software.

303562-A Rev. 00

+ 74 hidden pages

Avaya Bay Command Console BCC User Manual

Using the Bay Command Console (BCC)

Contents

Figures

Tables

Before You Begin

Preface

Text Conventions

Acronyms

Bay Netwo rks Technical Publications

How to Get Help

Platform Requirements

Number of BCC Sessions

Terminology and Concepts

Configuration Hierarchy

Context

Objects, Classes, and Instances

BCC Instance Identifier

Global (Box-Wide) Objects

Physical Device Objects

Parameters

Required Parameters

Derived Parameters

Optional Parameters

Entering and Exiting the BCC Interface