nortel bay command console (bcc) supplement guide

Bay Command Gonsole

Supplement

NORTETNETWORKS"

One Federal StreetBillerica, MA 01821978 288-3460

February 1999

ESDOOO3

@ Copyright 1999 Bay Networks, Inc. AII rlghts reserved.

The material provided is protected in accordance with the United States Copyright Act of 1978,as amended. No part ofthis document may be reproduced in any form or by any means, or usedto make any derivative work (such as translation or adaptation) without written permission fromBay Networks, Inc.

Information presented in this document is subject to change without notice.

Trademarks

<AN, ASN, BCN, BLN, and BN> are registered trademarks of Bay Networks, Inc.<Bay Networks> and <BayStack> are trademarks ofBay Networks, Inc.

Other brand and product narnes are trademarks or registered trademarks of their respectiveholders.

NOTICE TO U. S. GOVERNMENT LICENSEESFor Department of DefenseRESTRICTED RIGHTS LEGEND

Use, application or disclosure by the government is subject to restriction as set forth insubparagraph G)(l)(iil of the Rights in Technical Data and Computer Software Clause at DFARS252.227-7013.

For All Other Executive AgenciesNOTICE

Notwithstanding any other license agreement that may pertain to, or accompany the delivery ofthis computer software, the rights of the Government regarding its use, reproduction, anddisclosure are as set forth in the Commercial Computer Software Restricted Rights clause atFAR5Z.Z27-19.

Bay Networks, Inc. has licensed this training material to the parties delivering this training.Bay Networks, Inc. does not certify that the information the delivering parties provide is correctand will not be held liable for any damages that are a direct or indirect result of informationfacilitated by this guide.

Bay Networks equipment uses electronic components that are sensitive to static electricity.Electrostatic discharge (ESD) from your clothing or other items around you, even at levels thatdo not create a spark, can cause damage. You should take all possible precautions to preventESD damage when working with printed circuit boards. Keep each board in its protectiveconductive bay until you are ready to install it. Before you touch a printed circuit board, be sureto put on a grounded antistatic wrist strap and leash to free yourself of static. Then place eachprinted circuit board on a grounded antistatic mat while setting its configuration. Ifyou lack agrounded antistatic wrist strap, leash, and mat, be careful to stand in one place when you work(so you do not generate static electricity by friction), free yourself of static by touching agrounded metal object before handling a printed circuit board, and place the board on itsprotective conductive bay while you check or set its configuration.

Printed in the U. S. A.

Document PAJ: AV0025 I IO-ISGBCC-D

Bay Gommand Console

Contents

Appendix A Bay Command Console (BCC)...... ............A-1Overview.. ........ A-1What is BCC?...... ................ A_.z

Phased Implementation............ ............ A-4Using the BCC..... ............... A-6Terminolory and Concepts............... .. A-10About the BCC Configuration Hierarchy ............. A-18BCC Configuration...... ..... A-ZO

Upgrading the BCC Help File ............ A-32Displaying Online He1p........... ............ A-34Commands Managing Objects...... ...... A-38Entering Commands ........ A-40Saving Configurations on a Workstation.............. ................... A-42Summary.. ...... A-46BLN-2 Configuration Example ........... A-48help tree Example ............ A-ST

BCC Quick Reference (ANIBN Routers) ............... A-21

lil

IV Bay Command Gonsole

Appendix ABay Command Gonsole (BCC)

Overview

DescriptionThis appendix introduces the Bay Command Console (BCC), a single devicecommand line management tool. Configuration tree structure, terms andconcepts, help, and system commands necessary to perform basic deviceconfiguration are discussed.

ObjectivesAfter completing this unit, you will be able to do the following:

o Describe the functionality of the BCC

r Describe platform requirements to run the BCC

. Use and understand BCC terms and concepts

o lJse BCC Version 4.05 (supported in BayRS Version 13.01) to configure allrouters

Use the help, show, ?, and info commands to view and navigate the BCCconfiguration tree

Describe and use the "minimum to distinguish" feature of the BCC

Save or retrieve ASCII configurations on a workstation

Manage configured objects using the enable, disable, and deletecommands

BGC Appendix A-1

Bay Command Console (BCC) Appendix

What is BCC?

BCC DefinitionThe Bay Command Console (BCC) is a command-line interface for configuringBay Networks devices.

BCC is a superset of the Technician Interface (TI) that allows you to enter TIcommands and scripts at the BCC command line prompt.

Configurable parameters are added to a tree hierarchy, which is identified foreach Bay Networks device, starting at the box or stack prompt.

BCC Features

The BCC has the following features:

. BCC makes real-time (dynamic) changes to a device configuration.

. The BCC interface is unlike the TI but encompasses its functionality.

. BCC provides platform management via telnet or local/remote consoleconnections, just as the current Technician Interface.

r Basic configurations started in BCC can be extended using Site Managerand vice versa.

. BCC functionality will expand over several releases, providing integratedsubsystems (config, show, debug, log, decode, task-oriented help) forplatform management.

. BCC is not a GUl-based application.

. BCC is not a replacement for Site Manager.

. The BCC includes commands to build, view, navigate, and modify the BCCconfiguration tree.

o Context-sensitive prompts help facilitate tree navigation.

BCC Configuration Example

The following page shows an example of a BCC configuration using the labtopology from the Router Installation and Basic Configuration (AV0030080),Router Configuration and Management (AV0030090), and Accelerated RouterConfiguration (AV0025 1 I 0) courses.

A-2 BCC Appendix

Appendix What is BCC?

BCC Gonfiguration Example

,To Chicago

bcc> coafigbox# et Llliei ntt_:laris_sniip 128 .L28.224.L0l20irip;cwcbox# eer Ll2icL 521_chieago;bofl-t 15;clo internal;in clk1.nb;serial / 1/ 2# standard;ip 2OO.10.20 .2O l2tiriB;cwcbox# tftp;ftB;teLnet;cigiBronp { TPARIS:TNI $ } ;cwcbox# snnBico publicia read,-rr*rite;ma 0.0.0.0manager/public/ 0 . 0 . 0 . 0#cwcbox# exitbcc> exitt1:11$

128-128.224.0

ParisE1l S12

AN

BGC Appendix A-3


Phased lmplementation

The BCC is being delivered in phases. BCC Version 4.05 is supported in BayRSVersion 13.01. BCC will provide a complete integrated environment focused atBay Networks embedded management for all router platforms.

BCC platform coverage and functionality will continue to be extended overseveral BCC releases.

Current FunctionsThe BCC performs the following functions:

o Provides basic IP configuration and help for all router platforms

. lJses existing unabbreviated TI show and system commands

o Includes features:

A shell with TCL-like scripting language

English-style, verb first command parser (e.g., disable <object>)

Ability to view and edit configuration files in ASCII format

Uses abbreviated BCC object names - "minimum to distinguish"

Future FunctionalityThe BCC will become a collection of tools to allow for effective monitoring,configuration, and debugging of a device, along with a set of commands thatguides users through device management.

Future releases are planned to expand the number of platforms, processors,hardware modules, protocols, services, infrastructure components, and featurescovered.

A-4 BCC Appendix

Appendix Phased lmplementation

Phased lmplementation

BayRS Version 13.01 supports:

Configuring

Task-oriented help

Monitoring

System commands

BCC Appendix A-5


Using the BCC

Supported Platforms

The BCC runs on all router platforms. As a soloist program, BCC will run oneither ARE or FRE/FRE-2 processor modules. Each processor must have:

o 8 MB of dynamic RAM (DRAM) (16 MB recommended)

o 3 MB of free local memory space

It will provide partial support for the ANH-8 and ANH-I2. There are somelimitations with these platforms. You cannot use BCC commands to configurethe hub or the operation of ISDN, DCM, or CSU/DSU daughterboards in anANH.

Note

Please refer to release notes from the Bay Networks Web site for currentdetails about local memory requirements.

BCC AppendixA-6

Appendix

Supported Platforms:

AN

Using the BCC

ARN

ASN

BLN

BLN-2

BCN

ANH (partial support)

System 5000

Processors Needed:

Check release notes for processor local memory requirements; 16 MBrecommended.

BGC Appendix A-7

Bay Command Console (BCC)

Supported Protocols and lnterfaces

You can use BCC commands to configure the following global protocols:

o IP (including access policies and static routes)

o IPX

. ARP

. OSPF (including accept and announce policies)

o BGP (including accept and announce policies)

. IGMP

o RIP (including accept and announce policies)

o Telnet

Supported lnterface Protocols

Appendix

You can use BCC commands to configure

.IPo IGMP

o OSPF

. Bay Networks Standard Point-to-Point

. Frame Relay

Supported lnterfaces

the following interface protocols:

. ARP

. RIP

o Router Discover (RDISC)

You can use BCC commands to configure the following interfaces:

o Console

o Ethernet

o Token ring

. Synchronous

o FDDI

o HSSI

o PPP (certain line parameters on$)

. ATM

A-8 BGC Appendix

Appendix Using the BCC

Supported Protocols and lnterfaces

. Global Protocols

IP, IPX, ARP, OSPF, BGP, IGMP, RIP, TCINET

. lnterface Protocols

lP, ARP, IGMP, RlP, OSPF, RDISC, Bay Standard,PPP

. lnterfaces

Console, Ethernet, Token Ring, Synchronous, FDDI,HSSI, Virtual (Circuitless lP), Frame Relay, ATM

BGC Appendix A-9


Terminology and Goncepts

The BCC defines certain networking terminology and concepts in a consistentway, so that you can configure and manage different devices in a consistentway. This section describes these terms and concepts as follows:

Object-A data structure representing a configurable physical or logical entitysuch as an Ethernet interface or a protocol on a network device. Everyconfigurable object belongs to a specific class that defines its characteristics.

Class-A class is a template for a configurable object (such as an Ethernetinterface or IP on an interface). When you add a new object to the configurationof a network device, the BCC creates a copy (an instance) of the appropriatetemplate.

Instance-A customized copy of any class object defined in the configurationtree for a Bay Networks device. For example, you can create (add) an instanceofthe protocol IP to run on a specific interface type, slot, and connector in aModel BLN router. You customize an instance with unique values for itsrequired attributes.

Attributes-Properties of a configurable object. For example, some attributes ofan Ethernet interface are

o slot and connector (describing the location of the interface)

o bofl (describing one functional aspect of the interface)

Required Attributev-The minimum set of attributes for which the BCCrequires you to specify values. For example, the required attributes for aphysical interface are slot and connector. The BCC sets all other ("optional")attributes of a configured object to system default values.

Optional Attributes-The set of attributes for which you can optionally specifycustomized values, replacing any default values set by the system. Forexample, an optional attribute of an Ethernet interface is bofl (Breath Of Life).The default value or setting for bofl is enabled; you can optionally change this todisabled.

Instance ldentifier-Uniquely identifies a single instance of an objectconfigured on a Bay Networks device. The instance ID consists typically of thename of an object, combined with the values you specify for its requiredattributes. For example, the instance ID for an Ethernet interface consists ofetherneU <slot>/ <connector>. For some objects, the BCC automatically appendsother (internal) data to make each instance ID unique across the entire deviceconfiguration.

A-10 BCC Appendix

Appendix

Terminology

^+S^s.h-ffi.ffi.KR* oo*@

+ board

+ ethertretoip

# riP# osBf

G neigbbor

# rd,isc

# arp

* ignpo autoneg

fddioip

#riB

Terminology and Concepts

BGC Appendix A-11


Terminology (continued)

Configuration Hierarchy--{lasses (templates for creating objects) exist withina tree hierarchy. Just as a file system has a root directory, subdirectores, andfiles, the BCC configuration system has a root level object (called "box" or"stack") and subordinate objeits (such as interfaces and protocols) that fan outfrom the root level in a tree hierarchy. The BCC configuration commandhierarchy varies according to the type of network device (for example, a router,hub, or switch), but the BCC includes commands that enable you to efficientlydiscover and navigate that hierarchy. The figure on the following page showsan example of the configuration hierarchy for BLN and BCN routers.

Context-Your working location within the BCC configuration tree. Just as aUNIX file system has a current working directory within which you can add,modify, or delete files, the BCC configuration system has a current workingcontext, within which you can add configurable objects, or modify or deleteconfigured objects.

The BCC always displays a context-sensitive prompt, indicating your currentworking context or location within the configuration hierarchy.

Bor-The chassis for a network device

Box-wide./Global Objects-4bjects that provide services uniformly to all slots ofa network device (box-wide); for example, TCP, SNMP, FTP, TFTP, NTP, andTELNET. Some protocols, such as IP and OSPF have box-wide as well asinterface-specific objects. For example, IP contains BGP and OSPF, which inturn contain other box-wide/globally configurable objects. When you add IP onan interface, the BCC automatically finds, adds, and enables the box-wide/global IP object with all default settings. The BCC can also enable anybox-wide/global objects that derive required attribute values from existinginterface-level objects. The root-level context, box, contains all box-wide/globally configurable objects.

Board--:fypically a logic or circuit board dedicated to a particular task, such asproviding central or distributed processing for a network device, or providingan interface to a specific network transmission medium. Each board typicallyresides in a slot in a network device. Some boards contain other boards such asan RMON probe or a Data Collection Module (DCM).

SIot-A location as well as a physical and electrical means for attachingmodules to logic and power connections internal to a network device. Each slotin a Bay Networks device typically accommodates a processor or interfacemodule (board) of some t5pe.

Lin*(l) A physical (and on some devices, logical) circuit identified typically bymeans of a slot, connector, media t5pe, and (where applicable, such as withTI/EI facilities) a channel number. (2) The lowest common denominator foridentifying a packet data stream.

A-12 BCC Appendix

Appendix


BCC Command Hierarchy-Example on Model BLN/BCN Router

Lodierl intirtsc{ *?rri6rs


Global.$ea*ieo* t____________t

Hlrdlsrre ;L--------irlrllartn rrr|'i@as I

1l,:rtr* litlilcl it; rl)*,i,li ill{}rij.+i

lta.tr i1i*i lr.

it t^tra;3.:;\rti,r{

lrr-,::rird-tilgt

BCC Appendix A-13



Connector-:fhe physical and electrical means to interconnect an interfacemodule in a network device directly or indirectly to a physical network medium.

Port--(l) See connector. (2) On a network device or a user endstation, a logicalpoint of termination for data sent or received by a specific protocol orapplication. For example, a UNIX workstation receives syslog messages from aremote device at UDP logical port number 162.

Interface-(1) A datalink/physical layer connection to a physical networktransmission medium. (2) Any packet stream of a particular type. The BCCidentifies each interface by combining its name (such as ethernet, token ring,fddi, sync, or hssi), a slot number (where the interface resides physically in thedevice chassis), and a connector number (on the module occupying thedesignated slot). Certain devices, such as ASN routers, extend this terminologyto include other objects necessary for identifying a specific interface. Aninterface includes media-specific driver software.

Circuit-Sometimes used by the BCC configuration system to denote (1) Adedicated communication path; for example, a Permanent or Switched VirtualCircuit (PVC or SVC) established between two hosts over a packet- or cell-switched network, or over a dial or leased-line connection. (See also connection.)(2) A specific packet stream processed by a network device. (3) A driver fortransporting a particular packet stream over a physical interface.

Connection-(1) A path for reliable communication between two networkentities. The path can be physical or logical and the entities can be hardware/software systems or subsystems and/or subsystems attached to the networkmedium. (2) The path between two networking protocol modules that providesreliable packet stream delivery service. (3) A temporary or perrnanently"provisioned" path supporting end-to-end communication between two entitieson a network. Dial connections and SVCs are examples of temporaryconnections. Leased-line connections and PVCs are examples of permanentlyprovisioned connections.

Protocotr-This is a configurable object that typically supports datalink-,network-, transport-, session-, application-, or managementJayer services on anetwork device. Protocols may provide services box-wide (across all interfaceslots), per slot (across all interface connectors on a specific slot), or per interface(across all logicaVvirtual circuits associated with a specific connector and slot).

A-14 BCC Appendix

Appendix


BGG Command Hierarchy-Example on Model BLN/BCN Router


Global Ssri,icce

Lsqi6{tr iFtrF{c# **r,!sia+s

Lrno{FlErlar€rerr,icoc

+lir{ iii!,iJt:l. i:t rTr*i,!,t *i1ti:i;j

i lIC:r Jr lri r:i iiF l.*l':,tsirt

!:lJ:#:fiJ lii)$t

BCC Appendix A-15


Term inology (continued)

Network-(1) A protocol-specific address that identifies the physical segment orarea where a specific station resides. (2) The network portion of an IP address.(3) A group of computers, terminals, and other devices and the hardware andsoftware that enable them to exchange data and share resources over short orlong distances. (4) A group of nodes that communicate using a conunon channel.A network can consist of any combination of LANs or WANs.

Stack-The root prompt for an ASN and System 5000.

System Commands-Enable you to perform system administration tasks fromany configuration context.

A-16 BCG Appendix

Appendix

Term inology (continued)

BCC Gommand Hierarchy-Example on Model BLN/BCN Router

Lt4li6si rBt*rt$€4r g?ari+e+

i{ilrdl,rilr" I

Flct{rtim +tt'eie* |


&lnb.sl Scrnicts

]t':dl:j

-{I.J !:f:t l.+ii{,:i r1li. r'tlliii,! tili:!}jl.ilt1

BGG Appendix A-17


About the BCC Configuration Hierarchy

The contents of the object class hierarchy (configuration tree) for each BayNetworks device defines its set of configuration commands. The tree differssomewhat from device to device, but the tree for every device occupies someportion of the primary BCC Network Data Model. Within this model, youconfigure similar objects in similar ways. For example, you can alwaysconfigure an Ethernet interface on a Bay Networks device with the command:

box# ethernet <slot>/<connector>

The BCC configuration hierarchy is similar to that of a UNIX or DOS filesystem, with its directories, subdirectories, and files.

Just as a file system has directories that contain other directories, the BCCconfiguration system has (parent) objects that contain other (child) objects.Each child object can in turn be a parent and contain other child objects.

All objects in the BCC configuration system likewise exist in a tree hierarchythat starts from a root level (implicitly, the <box> or <stack> object) andbranches to many other (child) object levels.

BCC AppendixA-18

Appendix

BCC Gonfiguration Hierarchy Example

net

About the BCC Configuration Hierarchy

--t--f

Box-wide/g lobal objects

I nterface-s pecif ic objects

BCG Appendix A-19


BCC Configuration

Process

There are five basic steps you must take to complete a router configurationWith BCC:

1. Identify the topolory map and physically configure the router.

2. Start the BCC configuration mode.

3. Run the show config command to identify the resources physicallyconfigured on the box. Use the information learned from the show configcommand to assign ports to your map.

4. Use the BCC to configure the router.

5. View and confirm the new configuration using the show contig command.

A-20 BGC Appendix

Appendix BCC Configuration

BGG Configuration Process

1. ldentify the topology map and system parameters

2. Start the BCC configuration mode

3. ldentify the resources physically configured on the box usingshow config and assign ports to your map

4. Use the BCC to configure the router

5. View and confirm the new configuration using show config

BCC Appendix A-21


Step 1: ldentify the Topology Map

The first step to configure a router using the BCC is to identify the topolorymap. This will give you the information you need to do the configuration.

The map on the following page is a sample topolory.

-

A-22 BCC APPendix

Appendix

Step 1: ldentify the ToPologY MaP

BCC Configuration

lro Ghicago

200.10.20.0

128.128.224.O

Paris

AN

BGG Appendix A-23


Step 2: Start BCG Configuration Mode

The steps outlined below illustrate how to access the BCC and begin aconfiguration.

Appendix

l. Access the Technician Interface and login as Manager or LJser.

After you start the BCC interface, the Manager login allows you to enterany system command. A Manager login also allows, by default, read-writeaccess to the device configuration. The User login allows you to enter onlyuser-level system commands and allows read-only access to the deviceconfiguration.

Start the BCC interface by entering bcc at the TI prompt.

Start the BCC configuration mode by entering config at the bcc> prompt.

If you enter BCC configuration mode as Manager and want to change yourprivilege level for the current session, you can do so by entering thefollowing commands:

For read-only, enter config -read-only

For read-write, enter config -read-write

Note

If the prompt ends with #, you have read-write privileges. If the promptends with >, you have read-only privileges.

4. When finished using the BCC configuration mode, enter the exit commandat any prompt to return to the bcc>.

5. When you finish using the BCC, enter the exit command to return to the TIprompt.

2.

3.

A-24 BGG Appendix

Appendix

Step 2: Start BGG Gontiguration Mode

Bay Networks, Inc. and its Licensors.copyrighL Lgg2, lgg3, 1-gg4, !g95, 1-996, Lgg7. A11 rights reserved'

Login: lfaaager

Welcome to the Backbone Technician Interface

12:Ll$ bcc

Welcome to BaY Command' Console!

* To enter configuration mode, tlpe config

* To list all system conmlands, type ?

* To exit the BCC, tYPe exit

bcc> configt

:

box# cxitbcc> exit[2 :1] $

BCC Configuration

BGG AppendixA-25


Step 3: ldentify Resources on the Box

The show config command automatlcally identifies the hardware by default. Itis also used to view configured objects and configured parameters on BayNetworks devices.

Using the information gathered from the results of the initial show configcommand, assign the ports to your map topolory.

The current physical device configuration can be seen in the following example.

A-26 BGG Appendix

Appendix

Step 3: ldentify Resources on the Box

bcc> configrbox# sho!il coaf,igbox tlpe frerbln

board sfot. 1

tlpe srml-backboard slot 2

tlpe esafnfbackboard slot 3

tlpe slmcbackboard slot 4

tlpe dst416backboard slot 5

tlpe dtokbackconsole portnum 1

prompt {[8slott:1-]$ ]auto-manager-script automgr . batauto-user-scriPt autouser.bat

backbackbox#

BCC Configuration

Chicago

128.128.224.O

Assign physical ports

ParisE1l s12

BCG Appendix A-27


Step 4: Use BCC to Configure the RouterYou can configure a Bay Networks device by defining physical-layer objectssuch as interfaces, then further building the configuration by adding otherobjects, such as protocols supported on the device.

Using BCC commands at the root-level you can configure an Ethernet interfaceon the box , IP on the Ethernet interface, and RIP on that instance of IP.

While configuring, you can access context-sensitive help.

The figure on the opposite page illustrates the sequence of commands andlevels (context) used to build the configuration.

A-28 BCC Appendix

Appendix

Step 4: Use BCC to Configure the Router

Command Sequence

bcc> configbox# cE 1,17.ethernet /I/t# ip 128 .L28.224.LO12Otp / ]-28 .1'28 .224.10 / 255 .255 .240. 0# riprj-p/I28.128 .224.1-0#

Configuration Levels

.L28.224.LO 120

ip/L28 .L28 .224 -L0 /255.255.240.0# rip

BCC Configuration

rip/t28.]-28.224.1'0+

Box(root level) box# et 1./1

Ethernet(slot 1, connector 1 ethernet/1/1# LS, t,28

IP(add ress 1 28.1 28.224.1 O

mask 255,255.240.0)

]-

2

RIP

BGG Appendix A-29


Step 5: View and Verify Gonfiguration Using show config

After configuring a router, use the show config command to view the result ofyour configuration.

The example on the following page illustrates the new configuration of therouter after entering configuration commands.

A-30 BCC Appendix

Appendix

Step 5: View and Verify Gonfiguration Using show config

box# show configbox tlpe an

board slot 1tlpe ansedst

backconsole portnum 1

prompt tltslott:11$ )auto-manager-script automgr. batauto-user-script autouser. bat

backethernet slot L connector 1

circuj-t-name EllJaris-smip address t28 .728 .224.L0 mask 255 .255.240.

arpbackripback

backbackip

arpbackripbacktcpback

backserial slot 1 connector 2

circuit-name 52 l-_chicagobofl-timeout 15clock-source internalinternal - clock- speed clkl-mb

standard

backtftp

d.efault-volume 1backftp

default-volume 1backtelnet

clientbackserver

prompt {[PARIS:TN]$ ]back

backsnmp

corununity 1abe1 publicaccess read-write

manag'er address 0.0,0,0back

backbackbackmanager/public/ 0 . 0 . 0 . 0

box#

BCC Configuration

ip address 200.10 .20.20 mask 255.255.255.oarpbackripback

backback

BCC Appendix A-31


Upgrading the BCC Help File

The following information updates instructions relating to the BCC Help filementioned in Upgrading Routers to BayRS Version 13.xx. If you received aflash card with the BayRS 13.01 (BCC 4.05) image, it should also contain theBCC Help file. The BCC looks for this file as soon as you enter the firsthelp <option> command after booting the router using the new version 13.01image.

If the bcc.help file is not already on the default volume in the router, you musttransfer it from the BayRS Version 13.01 software CD to that volume. TheBCC Help file on the BayRS software CD has the name bcc_help. When youtransfer that file to the router, be sure to rename it as bcc.help. (The version13.01 router software is not configured by default to recognize the file namebcc-help.)

To use BCC online Help, you must transfer the bcc_help file onto the router'sflash card, then rename the file to bcc.help.

You can specify a new path name for this Help file, and then save this changeto your existing configuration file as follows:

$ bcc

bcc> config

box# help-f i le-na me <s lot_n u mbe r> : 4ile_name. he I p>l

box# save config <config_filename>

<slot_numbe> is the slot number on which you want to store the Help file.

< file_name.help> is the Help file name (for example, bcc.help).

< config_filename> is the router configuration file name.

A-32 BCG Appendix

AppendixUpgnding the BCC Hetp Fite

Upgrading the BCC Hetp Fite

specifying a new path name for a Herp fire and savingthe change

$ bcc

bcc> config

box# herpfire-name <srot-number>:<fire_name. hetp>lbox# save config <config_filename>

BGC AppendixA-33


The BCC supports the following online help and help-oriented features:

Command Help Feature

Get help on commands:help Get an overview of Help-oriented command features.

help -more Get more detail of Help-oriented command features.

?

<command>?

<command> <ootions>?

List command or command options you can enter.

help commands Display all BCC commands in alphabetical order (syntax).

Note: Object and parameter names that you enter asconfiguration commands are not in this list. (Refer to the ? andhelo tree commands later in this table.)

help commands -more Display more detail on all BCC commands in alphabeticalorder (svntax and terse command descriotions).

help <command>Example: To get fulldetails aboutthesave command, enter help save.

Get full details about a specific command

help syntax Get Help about symbols used to express BCC commandsvntax.

Get conliquration data (anv BCC context or command mode):

help tree

help tree <object>

Show the device configuration tree, as follows:. List, in hierarchicalformat, all objects configurable in the

device conf igu ration tree.o List, in hierarchicalformat, all objects configurable within

the context of a specific box-level <object>, where<object> is board, console, ip, ftp, snmp, telnet, ftp, tftp,ethernet, tokenring, hssi, sync, fddi, or virtual on an AN orBN router.

show config[<BCC_instance_id>]

Show in sourceable BCC syntax the existing configurationof the total device or a configured object you identify by itsBCC instance lD.

Displaying Online Help

A-34 BCC Appendix

AppendixDisplayingonlineHelp

DisPlaYing Online HelP

Get helP on commands:

helP

helP -more

?

helP commands

helP commands -morehelP <command>

helP sYntax

Get configuration data (any BCC context or command mode):

helP tree

helP tree <object>

show config [<Bcc-instance-id>]

A-35BCC APPendix


Displaying Online Help (continued)

Command Help Feature

Get confiquration data (BCC confiquration mode onlv):2 List the names of objects, parameter, and commands you

can enter next.<object>? Get command usage Help and list parameter of an object you

can add or modify from vour current location.<parameter> Get the current value for this parameter of the current object.<parameter>? Get legal, current, and default values for this parameter of the

current obiect.<BCC_instance_lD><parameter>?Example:Box# ethernetl2ll bofl ?Current Value: enableLegal Value: {enable disable}Default Value: enable

Get legal, current, and default values for this parameter of aconfigured object you can access from your current workingcontext or level.

info Lisl values currently assigned to parameters of this object.

help parameters Describe parameters of the current object.

help parameters <pafh>

ffhe <pafh> is the sequence ofobjects between root level and thedesired context.)Example: help parameters ipospfHint: Use the help tree commandto determine lhe <path> to thedesired obiect.

Describe parameters of an object outside the current context.

haslso

List other objects currently configured at the next (branch)level of the confiquration tree for this device.

Get Help on a specific task:help learning-bcc Get Help about performing common BCC operations.

help editing Get Help about how to edit BCC commands and commandlines.

BCC AppendixA-36

- Appendix Displaying Online Help

Displaying Online Help

Get configuration data (BCC configuration mode):

?

<object> ?

<parameter>

<parameter> ?

<Bcc_instance_l D> <parameter> ?

info

help parameters

help parameters <path>

has

lso

Get help on a specific task:

help learning-bcc

help editing

BCC Appendix


Commands Managing Objects

The following commands manage objects.

enable Command

The enable command allows you to change the state of a configured object from"disabled" to "enabled".

ip/t.2 .3 .4/255 .255 .240 .0# earble

disable Gommand

The disable command allows you to change the state of a configured object from"enabled" to "disabled".

ip/t.2 -3 .4/255.255.240 .0* disalcle

delete Gommand

The delete command performs two functions:

. Removes an object you designate in the command line

box# d,elete iD 1,92.32.150. L1255.255.2L0.0

or

. Removes the object identified in the BCC context-sensitive prompt.

ip 792.32 . l-50 .L/255 .25s .240 .0# d,eleteCAUTION

Deleting an object at one level of the configuration tree causes theBCC to automatically delete any attributes or parameters of thatobject. For example, deleting an instance of IP on an interface alsodeletes any instance of protocols configured on the same interface,such as ARP, RIP, or OSPF.

A-38 BCC Appendix

Appendix Commands Managing Objects

Gommands Managing Objects

enable Command

:-p/1.2 .3 .4/255 .255 .240 .0# enable

disable Command

ip/ t.2 .3 .4/255 .255 .240 .0# disaJcle

delete Command

box# delete iB 192.32.150 .7.1255.255.24O.O

BCC Appendix A-39


Entering Commands

Minimum to DistinguishFor command input, the BCC interface allows you to shorten existing objectand attribute names; for example *et" for Ethernet. This is the "minimum todistinguish" feature of BCC.

The following table compares the same command in "long hand" vs. "minimumto distinguish".

Long Hand Minimum to Distinguish

ethernet slot 2 connector 1 et 2/lip address 128 -1-28.192.10 mask25s.25s.240 -0

ip 128 .a28 .]-92 .L0 /20

Entering Multiple Commands per Line

To enter multiple commands in the same line, t5rpe a semicolon (;) wherever youwould press return to terminate a command. For example, to configure RIP onipl L.2.3.41255.0.0.0 on Ethernet 21 1, enter:

box# eE 2lLiip 1.2.3.418irLprip/t.2.3.4ti

Continuing a Command Line

You can continue a command line by entering a backslash (\) character at theend of the current text line. The BCC treats characters on the next physicalline as part of the same BCC logical command line.

box# ec.r 3f7.tci Sgt_tondon;bofl-t 15;clock-s internal;inclkimb; standard i iO 2O0.50 .60 .2O l24irip

BCG AppendixA-40

Appendix Entering Commands

Entering Gommands

Minimum to Distinguish

Multiple Gommand Linesbox# eE 21L;ip 1.2.3.418iri:nriP/t -2 -3 -4#

Continuing a Command Linebox# ser 3lL;cL 531_Iondon;bofl-t 15;cl-ock-g interrral;inclklmb; stand.ard.; iB 200. 50 . 60 .2O 124 iriln

BCC Appendix

Long Hand Minimum to Distinguish

ethernet slot 2 connector L et 2/L

ip address L28.L28.1-92.10 mask 255.255.240 .0 ip 128 .128 .L92 .1,0 /20

A-41


Saving Configurations on a Workstation

OverviewA unique feature with BCC is the ability to view and edit configuration files inASCII format.

Saving GonfigurationsIf you log into an AN or BN router from a workstation using Telnet or terminalemulation, you can use the native capabilities of the workstation to:

. Save the output of any show config command from the screen to an ASCIIfile

o Save a sequence of manually entered BCC commands to an ASCII file

You can also use an ASCII text editor on a workstation to create a file fromwhich the BCC can read configuration and system commands.

Note

If you create or edit ASCII files containing BCC commands, you mustadhere to the BCC syntax requirements. For example, you must includeany commands necessary to navigate to each level of the deviceconfiguration tree, and any commands necessary to add, modify, or deleteobjects in the device configuration.

By saving BCC commands to an ASCII file, you can subsequently:

o Edit the commands offline

. Add comments to the file to describe details of the configuration

. Save the edited file for later use

. LJse the BCC source command to make changes to the active configurationof Bay Networks devices of the same type and hardware configuration

Note

If the BCC detects an error in the source file, it stops reading commandsinto the device configuration.

442 BGC Appendix

Appendix


Binary


ASCIIbcc>coalLgfbo*l tbd coafLgrbox tl'Ira frcrbla

borld aLot 1trE. arD.l

brchborrd rlot 2

tyttc .rrlaf,back

101001010101010101010101010101010101010010001000001011110101010101010101010101010101010101010101010101010101010011111010001010101010100100100101010101

BGG Appendix A-43


Retrieving a Gonfiguration

The source command is used to write (enter) BCC configuration and navigationcommands into the active device configuration. It merges new configrr.atio.tdata from a file with existing data in device memory.

Warning

The source command makes immediate changes to the activedevice configuration.

The syntax for the source command is as follows:

source <volume> : <filename>

A'44BCC Appendix

Appendix

Retrieving a Configuration

Binary


ASCil101001010101010101010101010101010101010010001000001011110101010101010101010101010101010101010101010101010101010011111010001010101010100100100101010101

bce>soatigfbox* rhor confl,grbo,l t!'Da lrarb].D

bor.rd rlot 1tlDa rr:!.1

bechborrd rlot 2

tyta arafnlbrck

BGG Appendix A-45


Summary

Summary of BCC

In this unit, you learned the following:

. The BCC currently supports configuration and task-oriented help. Plannedreleases will include monitoring, debugging, system commands, and shellwith scripting.

o BCC is supported on all router platforms.

r BCC uses different terms and concepts than the TL

. How to use the BCC Version 4.05 to configure routers running BayRSVersion 13.01.

Appendix

A-46 BCC Appendix

BCC ExamPles andQuick Reference Sheets

SummaryAppendix

A'47BGC Appendix


BLN-2 Configuration Example

Using the IP network topology and information below, we will configure theBoston router (BLN-Z).

Class "8" subnet mask = 255.255.240.0Class "C" subnet mask = 255.255.255.0

128.128.128.O 129.128.192.O

129:128.U24.O

200.30.40.0

200.70.80.0

System lnformation. System Name is Boston

o Location is Billerica

r Contact is John Doe

o Circuitless IP address will be I28.L28.32.1 (virtual)

o Enable FTP

. Enable TFTP

o Enable TELNET and set the telnet prompt to IBOSTON:TNI$

. Enable ARP and RIP

o BOFL timeout = 15 seconds, Internal Clock Speed = I Mb

. IJse abbreviated names when configuring objects

128.128.160.0 129.128.

Six

200.50.60.0 200.40.50.0

.10 .10

.10 Sydney.to

A-48 BCG Appendix

Appendix BLN-2 Configuration Example

Start BGG and Run show config

After identifying the topology map, your first steps are to start BCC and enterthe show config command to view what is on the router.

Bay Networks, fnc. and its Licensors.copyrighr 1992, ].993, 1994, 1995, 1-996, L997- A11 rights reserved.

Login: Manager

Welcome to the Backbone Tectrnician Interface

[2:1] $ bcc

Welcome to Bay Command Console!

* To enter configuration mode, tYPe

* To list all system commands, tYPe

* To exit the BcC, t)4)e exiL

bcc> configbox# gbow configtbox tlpe frerbln

board slot l-tlpe srml

backLroard slot 2

tlpe esafnfbackboard sloL 3


tlPe dst416backboard slot 5


prompt {ltslott:1]$ ]auto-manager-script automgr . batauto-user-scriPt autouser. bat

backbackbox#

BGC Appendix

config

2

A-49


The results of the first show config command give you the information neededto create a map of available ports and locations on the router. Use thisinformation to assign physical ports to the logical topology.

The charts below are drawn based on information gathered on the previouspage:

SLOT TYPE DESCRIPTION

5 DTR DUAL TOKEN R|NG (4/16 Mb)4 DST DUAL SYNC, SINGLE TOKEN3 SYNC QUADSYNC2 ESAF4 ETHERNETSYNCADV. FILTER1 SMRL SYSTEM RESOURCE MODULE

SLOT

lffiEN r-l

1d6fi1-l

lEoM-T-]

lddMr-1

lcoN-S'CI

]c-dMr-l

lddMr-l

lc-dMT-l

ITo-'ffi'Tl

ldoMt-'l

|ffifi--l

lTbffiTI

l6Mf-llffil

A-50 BCG Appendix

Appendix

Assign Ports

The next step is to assign ports.

To London


Assign ysical ports

To Atlanta

200.20.30.0

128.128.160.0

200.50.60.0

128.128.128.O

E21_sm S32_atlanta

051_london S31_london

200.60.70.0

BGC Appendix A-51


Configure the Router

Use the composite information to configure the router in BCC.

box# et 2l7.icL E21_boeton_smi Lgt L28.L28.L92.1,Ol2Oirilr,ieE 2lLethernet,/2/I# Lnfo

on boxstate enabledcircuit-name E21 boston smslot 2

connector 1bofl enablebofl-timeout 5

hardware-f ilter disabletransmit-gueue-length 0

receive-queue-length 0

bofl-retries 5

bofl-tmo-divisor 1bofl-number 0

ethernet/2/t# bo:xbox# ser 3lLicL S31_london;bof1-t 15;c1ock-s interaal;in c1klmbserial/3/1# standard;iXr 200.50 .60.20 l24rELDrs'er 3lLserial/3 /l# 5,nf,o

on boxstate enabl-edcircuit-name S31 londonslot.3connector 1bofl enabledbofl-timeout 15mtu 1500promiscuous disabledclock-source internalinternal-c1ock-speed clk1mbsignal-rnode balancedrts-enabl-e disabledburst-count enabledservice 11c1crc-size crcl6bithold-down-time 0

slmc-1ine-coding nrzremote- loopback-detect ion di sabled.external-c1ock-speed 54102

serial/3 /I# bolxbox# eer 3l2ici S32_atlanta;bof1-t 15;clock-s interrral;in cIklnbserial/3 / 2# stsrldard;ip 20O.2O.3O -20 124;rip;ewcbox# ser 3lIicL S34jaris;bof1-t 15;clock-s interrral;in clklmbserial- / 3 / 4# etandard; ip L28 . L28. 150 . L0 | 2O ; rjrr, i cwcbox#

Appendix

BCG AppendixA-52

Appendix

box# to 5ll,icL o51 bos_loadoniip 200.60.70.2O124;rip;to 5/1tokenring/5/L# Lafo

on boxstate enabfedcircuit-name 051 bos londonsl-ot 5

connector 1speed 1-6Me9f

bofl-number 0

tokenrinq/5/\# botrbox# to 5l2icL O52_boslraris;ip 128 .1"28.L28.1"O l20irip;cwcbox# vici "circuitless xF";ip L28.L28.32.t12o;vvirtual-# info

on boxcircuit-name {circuitless IP}

wirtual# boxbox# syg bogton;loc billericaiconta'ilohn Doetriftp;tftp;telnettelnet# c1i;senr;promlr { IBOSTON:TN] $ ]boxextra characters after close-braceserver# I>romlr { IBOSTON:TN] $ ];cwcbox#


BCC Appendix A-53


View Completed Configuration

After entering all the configuration information, view your completedconfiguration by entering the show config command a second time.

box# show coafigrbox t14pe frerbLn

contact John Doesystem-name bostonlocation billerica

board slot 1

tlpe srmlbackboard slot 2

tyge esafnfbackboard slot 3


t149e dst416backboard slot 5


prompt { lSslott: l-l $ }auLo-manager- script automgr . batauto-user-script autouser. bat

backethernet slot 2 connector 1

circuit-name E2 1_boston-smip address 128 .L28 -L92 -L0 mask 255 .255.240.0

arpbackripback

backbackip

arpbackripbacktcpback

backserial- slot 3 connector 1

circuit-name 53 1_londonbofl-timeout 15clock-source internalinternal-c1ock-speed clk1mb

Appendix

A-54 BGG Appendix

Appendix

standardip address 200.50.50.20 mask 255.255-255.0

arpbackripback

backback

backserial slot 3 connector 2

circuit-name 53 2-atlanLabofl-timeout 15cLock-source internalinternal-c1ock-speed clk1mb

standardip address 200 .20 .30 .20 mask 255 .255.255 . 0

arpbackripback

backback

back

serial slot 3 connector 4circuit-name 53 4l>arisbofl-timeout 15clock-source internalinternal-clock-speed clkl-mb

standardip address 128 .L28.160.10 mask 255 -255 -240.0

arpbackripback

backback

backtokenring slot 5 connecLor 1

circuit-name 05 1-bos-londonip address 200.60.70.20 mask 255.255.255.0

arpbackripback

backback


BGG Appendix A-55


tokenring slot 5 connector 2circuit-name 052_bos3aris

ip address I28.1,28.I28.1,0 mask 255 .255.240.0arpbackripback

backbackvirtual

circuit-name {circuitl-ess IP}ip address 128-I28.32.1- mask 255.255.240.0

arpback

backbackftp

default,-volume 2backtftp

default-volume 2backtelnet

clientbackserver

prompt tIBOSTON:TNI$ ]back

backbackbox#

box# sxitbcc>

Appendix

BCC AppendixA-56

Appendix help tree Example

help tree Example

bcc> help trce

Router Configuration Tree

The following hierarchical fist shows every object that you canconfigure (but is not necessarily configTured at this time) on thisd.evice. You can use this list as a map to help you navigate within thedevice configuration tree.

To view only a specific branch of the configuration tree, enLer helptree <object>, where <object> is any **box-1eve1** object, such asetherneL, ip, or telnet

bcc> hefp treeReading helpfile index.The entire configuration

boardvirtual

ipospf

neighborftphttpntp

peersnmp

conununitynEnager

trap-entitytrap-event

tftpconsoletelnet

clientserver

brileased-1ine

ppplineip

ripospf

neighborarpismp

relayipx

ripsapstatic-routeadjacent-hosL

BGG Appendix

Pleasetree is

, done.wait

A-€7


static-serviceroute- filterserver-network- f i lterserver-name- filter

ipxwanripsapstatic-routeadj acent-hoststatic-serviceroute-filterserver-network- f i lterserver-name- filter

standardip

arpripospf

neighborrdiscismp

relayipx

ripsapstatic-routeadj acent-hoststatic-serviceroute- filterserver-network- f i I Lerserver-name- f il-ter

backup-circuitout-phone-numberschedulecal-1er-resolut ion

frame-re1aydlcmisignallinglapfdefault-service

pvcsvc-optionsip

ripospf

neighborarpigmp

relaYipx

ripsapstatic-routeadj aeent-hoststatic-serviceroute-filLer

Appendix

BCG AppendixA-58

Appendix

server_network_ f i 1 terserver_nerme_f ilter

servicepvcsvc-optionsip

ripospf

neighborarpismp

relayipx

ripsapstatic_routeadjacent_hoststatic_serviceroute_filterserver_network_ fi 1 terserver_name_filter

ipxwan.io* -rsapstatic_routeadj acent_hostst,atic-serviceroute_filterserver_network_ f i 1 terserver_name_ filter

backup-circuitout_phone_numberschedulecal_1er_resolution

channeldial1oca1-phone-number

ethernetip

arpripospf

neighborrdiscismp

relayipx

ripsapstatic-routeadjacent-hoststatic-serviceroute-filterserver-network_ f i 1 terserver-nElme-f iLter

auto-negt

BCC Appendix

help tree Exampte

A-59


seriaLppp

lineip

riposPf

neighborarpismp

relayipx

ripsapsapstatic-routeadjacent-hoststatic-serviceroute-filterserver-network- f i 1 terserver-nELme-f ilter

ipxwanripsapstatic-routeadjacent-hoststatic-serviceroute-filterserver-network- fi 1 terserver-name- filter

backup-circuitout-phone-numberscheduleca11er-resolution

standardip

arpripospf

neighborrdiscigmp

relayipx

ripsap

st,atic-routeadjacent-hoststatic-servicerout.e-f ilterserver-network- f i 1 terserver-name- filter


frame-re1ayA-60

Appendix

BGC Appendix

Appendix

dlcmisignallinglapfdefault-service

pvcsvc-optionsip

, ripospf

neighborarpismp

relayipx

ripsapstatic-routeadjacent-hoststatic-serviceroute- filters erver-network- f i 1 terserver-name-filter


riposPf

neighborarpismp

relayipx

ripsapstatic-routeadjacent-hoststatic-serviceroute- filterserver-network- f i I terserver-name-f il-ter

ipxwanripsapstatic-routeadjacent-hoststatic-serviceroute-filters erver-network- f i 1 terserver-name- filter


dialhssi

BGG Appendix

help tree Example

A-61


ppplineip

ripospf

neighborarpismp

relayipx

ripsapstatic-routeadjacent-hoststatic-serviceroute-filterserver-network- f i 1 terserver-name- filter

ipxwanripsapstatic-routeadjacent-hoststatic-serviceroute-filters erver-network- f i 1 terserver-name- fi1 ter

standardip

arpripospf

neighborrdiscismp

relayipx

ripsapstatic-routeadjacent-hoststatic-serviceroute-filterserver-network- f i 1 t.erserver-name- filter

frame-re1aydlcmisignallinglapfdefault-service

pvcsvc-optionsip

ripospf

neighbor

Appendix

BGC AppendixA-62

Appendix

arpismp

relayipx

ripsapstatiq-routeadjacent-hostsfatic-serviceroute- filterserver-network- f i I terserver-name- filter


ripospf

neighborarpismp

relayipx

ripsapstatic-routeadjacent-hoststatic-serviceroute-filterserver-network- f i 1 terserver-name- filLer

ipxwanripsapstatic-routeadjacent-hoststatic-serviceroute- filters erver-network- f i 1 terserver-name- filter


token-ringip

arpripospf

neighborrd.iscismp

relayipx

ripsap

BGG Appendix

help tree Example

A-63


static-routeadjacent-hoststatic-serviceroute-f i1t.erserver-network- f i lterserver-name- filter

fddiip

arpripospf

neighborrdiscisrnp

relayipx

ripsapsLatic-routeadjacent-hoststatic-serviceroute- filterserver-network- f i1 terserver-name- filter

mcellogical-1ine

ppplineip

ripospf

neighborarpismp

relayipx

ripsapsLatic-routeadjacent-hoststatic-serviceroute-filterserver-network- fi 1 terserver-name- filter

ipxwanripsapst,atic-routeadj acent-hoststatic-serviceroute- f i1t,erserver-network- f i 1 terserver-name- filter

backup-circuitout-phone-numberschedule

A-64

Appendix

BCG Appendix

Appendix

ca1ler-resolutionstandard

iparpripospf

neighborrdiscismprelay

ipxripsapstatic-routeadjacent-hoststatic-serviceroute-filterserver-network- f il-terserver-name- filter


frame-re1-aydlcmisignallingLapfdefault-service

pvcsvc-optionsip

ripospf

neighborarpismp

relayipx

ripsapstatic-routeadjacent-hoststatic-serviceroute-filterserver-network- f i 1 terserver-name-filter


riposPf

neighborarpismp

relayBGG Appendix

helptree Example

A-65


apxripsapstatic-routeadj acent-hoststatic-serviceroute-filterserver-network- f i 1 terserver-name- filter

ipxwanripsapstatic-routeadjacent-hoststatic-serviceroute-filterserver-network- f i 1 terserver-narne- filter


pridial1oca1-phone-number

mctl-logical-line

ppplineip

ripospf

neighborarpismp

relayipx

ripsapstatic-routeadjacent-hoststatic-serviceroute- filterserver-network- f i 1 terserver-n€rme-f ilter

ipxwanripsapstatic-routeadjacent-hoststatic-serviceroute-f il-terserver-network- f i1 terserver-name-f i1t,er

backup-circuitout-phone-number

A-66

Appendix

BCC Appendix

Appendix

scheduleca1ler-resolution

standardip

arpriposPf

neighborrdiscismp

relayipx

ripsapstatic-routeadjacent-hoststatic-serviceroute-filterserver-network- f i 1 terserver-narne- filter


franne-re1aydlcmisignallinglapfdefault-service

pvcsvc-optionsip

ripospf

neighborarpismp

relayipx

ripsapstatic-routeadjacent-hoststatic-serviceroute-filterserver -network- f i 1 terserver-name- filter


ripospf

neighborarpismp

BGG Appendix

help tree Example

A-67


relayipx

ripsapstatic-routeadjacent-hoststatic-serviceroute-filterserver-network- f i 1 terserver-name- filter

ipxvanripsapstatic-routeadjacent-hoststatic-serviceroute-filterserver-network- f i 1 terserver-name-filter

backup-circuitout-phone-numberschedulecal1er-resolution

pridialloca1-phone-number

isdn-switchbackup-poo1

backup-1ineip

access-policynetwork

adjacent-hostarpismp

relaystatic-routebgp

peerdebug-control

acceptmatch

aggregator-asaggregator-routerasconmrunitynetworkoriginating-aspeer

modifyinj ect

announcematch

inbound-asconununityegrp-as

A-68

Appendix

BGC Appendix

Appendix help tree Example

egp-gatewayegp-peernetworknext-hopospf-router-idospf-tagoutbound-asoutbound-Peerinbound-Peerrip-gatewayrip-interface

modifyadvertisecommunity

debug-controlospf

areasulruIra.ry

acceptmatch

ase-tagnetwork

modifyannounce

matchbgp-asbgP-next-hoPbgp-Peeregp-asegP-gatewaYegp-peernetworkrip-gatewaYrip-interface

modifyadvertise

ripaccept

maLchnetworkrip-gatewayrip-interface

modifyannounce

matchbgp-asbgp-next-hopbgp-peeregl.I)-asegP-gatewaYegp-peeri-nbound-interfacenetworkospf-router-idospf-tagoutbound-interface

BGG Appendix A-69


rip-gatewaymodify

advertisetcp

ipxs tatic-netbios-route

bcc>

Appendix

A-70BCC Appendix

Appendix BCC Quick Reference (AN/BN Routers)

BCC Quick Reference (AN/BN Routers)

The BGC Configuration Tree

The BCC uses a hierarchical tree configuration model similar to the DOShierarchy of directories and files. The BCC configuration tree for a networkdevice contains:

. Objects-Physical or logical entities you can configure. An Ethernetinterface or a protocol is an object.

. Parameters-Attributes or properties of an object; slot, and connector areattributes of the object ethernet. Parameters also have values; for example,slot 4 is a parameter-value pair.

Starting at the root level, you build a BCC configuration by adding objects tothe tree. Every object occupies a specific level, or context, within the tree, asshown below.

[- riPI

ip address 1.2.3.4 mask 255.0.0.0

f-ethernet slot 2 connector 1

box# ______1

(root level) rnet Slot 2 connector 2

ip address

Note

The boldface labels in the figure are the actual BCC commands used tocreate this configuration.

2.3.4.5 mask 255.0.0.0

BCC Appendix A-71


Gonfiguration Tips. Start a BCC configuration session by logging in to the TI as Manager. Next,

enter bcc and wait for the bcc> prompt. Enter config at the bcc> promptand wait for the box# configuration prompt.

o Configure interfaces first, then add protocols. When you enter BCCconfiguration commands, you immediately modify device behavior.

o As you navigate between levels of the configuration tree, the BCC promptchanges to show your current location. The BCC indicates the currentlocation by displaying the unique identifier of the configured object at yourcurrent location, for exampl e: Lp / L92. 15 8 . 3 . 4 I 255 . 255 .2 55 . 0 .

o To access any object, tSpe the path to that object. For example, to accessRIP on one of the Ethernet interfaces configured above, type at 2lL;int .2 .3 .41255. O . O . 0; rip . (Note that the BCC interprets each semicolon[ ; ] as if you had pressed the Return key to start a new command line.)

. Whenever you add IP to an interface, the BCC accepts the mask value ineither dotted-decimal notation (for example, 255.255.255.0) or in standarddecimal notation (for example,24, representing the number of bits reservedfor the network portion of the IP interface address). For example: ipaddress 1L.23.13.14 mask 255.0.0.0 (or) iBLL.23.t3.t4l2s5.O.O.O (or) ip address LL.23.13.14 mask A (or)ip 11 .23.L3.L418

o Entering any of these commands creates an object with the uniqueidentifier Lpl11..23. 13 .t4 1255. 0. 0. 0

o The BCC responds with helpful prompts whenever you leave outinformation required to configure an object.

o To move back one level closer to root (box#) level, type back; to move back toroot level, type cwc.

To exit from BCC configuration mode, type exit. To exit the BCC and returnto the Technician Interface prompt, type exit again. To log out of the router,type logout. If you exit and then reenter the BCC without rebooting,configuration changes that you made during the last BCC session are stillin effect,

Enter all commands using lowercase letters.

You can abbreviate gbject names or parameter names; however, theabbreviations must_be unique. For exampre, two objects, fddi and ftp, existat the root lever or j.hg BCC configuration tree for a BN router. To ret theBCC know which of these ob;ectJyou want to configure, you mustminimally enter either fd or ft at the box# prompt.

A-72BCC Appendix


o The BCC does not recognize abbreviated system commands (commands

available in any BCC mode); for example, the BCC will not recognizesh as show.

EGG APPendix A-73


Common BGG Gommands

Appendix

Describe BCC help features.

Provide a list of commands you can enterfrom any BCC prompt.

Describe in full detail a specificcommand.

Provide usage help with terse examplesfor a specific command.

List the narnes of all commands you canenter here.

Note: Press the spacebar to scrollthrough Help screens.

help

help commands

help <command>

<command>?

?

System help(from anyBCC prompt)

help parameters

<parameter>?

<instance_id> <pa ramete r> ?

Show the BCC configuration tree. (List,in hierarchical format, every object youcan configure on this device.)

List the names of all objects andparameters you can configure, andcommands you can enter, at the currentlevel.

Get usage (command entry) help, and listthe parameters of this configurableobject. (Example: ip ?)

Show definitions for parameters of thecurrent object.

List the current, legal, and defaultvalues for this parameter of the currentobject. (Ethernet example: bofFretries ?)

List the current,Iegal, and defaultvalues for aparameter of this configuredobject, specified by its BCC insta.r.J tO.

Configurationhelp

(configurationmode only)

List values currently assigned toparameters of the current object.

List, by BCC instance ID, any objectsconfigured in the current context.

The table below contains common BCC commands.

BCC Appendix


Category BCC Gommand Syntax Task

Navigation back

bor</stacUcwc

pwc

Go back one level closer to root level ofthe configuration tree.

Go all the way back to root level fromany level in the tree.

Print the current working context,starting from root level.

Configurationstatus

show confi g [<instance_id>] Show the configuration of the totaldevice or a specific object, for example,show config or show configip|1.2.3.41255.0.0.0

Othercommands

Up arrow key(or Control+p)

Down arrow key(or Control+n)

Recall the previous command from thehistory list.

Recall the next command from thehistory list.

exit Exit configuration mode and return tothe bcc> prompt.

Exit the BCC and return to theTechnician Interface prompt.

BCC Appendix A-75


Common BCC Operations

The BCC indicates when configuration parameters have values that arerequired Sou must supply a value). Other parameters have derived or defaultvalues supplied by the system.

Task BCC Command Syntax Examples

Configure aphysical interface

< i nte rface _ty pe > <s I ot><connector>

ethernet slot 3 connector 1

et 3/1

Configure aprotocol

<p rotocol > <requ i redjaram><value>...

ip address 192.168.3.4 mask 255.255.255.0ip 1 92. 1 68.3 .41255.255.2s5.0ip address 192.168.3.4 mask24ip 192.168.3.4124

Modifyparameter values

<param> <new_value>.. cache-size 64ca 64

Disable, enable,or delete anobject

disable [<lD>Ienable [<lD>Idelete [<lD>]

ip/ 1 .2.3.4 1255. 0. 0. 0# d isablefddi/1 I 1 # disable ip|l.2.3.41255.0.0.0ipl 1 .2.3.41255. 0.0. 0# enablefddil 1 11 # enable ip|l.2.3.41255.0.0.0ipl 1 .2.3.41255. 0.0. 0# deletetddil 1 I 1 # delete ipll .2.3.41255.0.0.0

A-76BGC Appendix

nortel bay command console (bcc) supplement guide

Documents