Nortel Bay Command Console (BCC) Supplement Guide

Bay Command Gonsole Supplement

NORTET NETWORKS" One Federal Street Billerica, MA 01821 978 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 used to make any derivative work (such as translation or adaptation) without written permission from Bay Networks, Inc.

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

Trademarks are registered trademarks of Bay Networks, Inc. and are trademarks ofBay Networks, Inc. Other brand and product narnes are trademarks or registered trademarks of their respective holders.

NOTICE TO U. S. GOVERNMENT LICENSEES For Department of Defense RESTRICTED RIGHTS LEGEND Use, application or disclosure by the government is subject to restriction as set forth in subparagraph G)(l)(iil of the Rights in Technical Data and Computer Software Clause at DFARS 252.227-7013.

For All Other Executive Agencies NOTICE Notwithstanding any other license agreement that may pertain to, or accompany the delivery of this computer software, the rights of the Government regarding its use, reproduction, and disclosure are as set forth in the Commercial Computer Software Restricted Rights clause at FAR5Z.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 correct and will not be held liable for any damages that are a direct or indirect result of information facilitated 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 that do not create a spark, can cause damage. You should take all possible precautions to prevent ESD damage when working with printed circuit boards. Keep each board in its protective conductive bay until you are ready to install it. Before you touch a printed circuit board, be sure to put on a grounded antistatic wrist strap and leash to free yourself of static. Then place each printed circuit board on a grounded antistatic mat while setting its configuration. Ifyou lack a grounded 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 a grounded metal object before handling a printed circuit board, and place the board on its protective 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)......

Overview.. What is BCC?...... Phased Implementation............ Using the BCC..... Terminolory and Concepts............... About the BCC Configuration Hierarchy BCC Configuration...... Upgrading the BCC Help File Displaying Online He1p........... Commands Managing Objects...... Entering Commands Saving Configurations on a Workstation.............. Summary.. BLN-2 Configuration Example help tree Example BCC Quick Reference (ANIBN Routers)

............A-1 ........ A-1

................ A_.z ............ A-4

A-6 .. A-10

...............

............. A-18

..... A-ZO ............ A-32 ............ A-34 ......

A-38

........

A-40

................... A-42 ......

A-46

........... A-48

............ A-ST ............... A-21

lil

IV

Bay Command Gonsole

Appendix A Bay Command Gonsole (BCC)

Overview Description This appendix introduces the Bay Command Console (BCC), a single device command line management tool. Configuration tree structure, terms and concepts, help, and system commands necessary to perform basic device configuration are discussed.

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

o r . o

Describe the functionality of the BCC Describe platform requirements to run the BCC Use and understand BCC terms and concepts lJse BCC Version 4.05 (supported in BayRS Version 13.01) to configure all routers Use the help, show, ?, and info commands to view and navigate the BCC configuration 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 delete commands

BGC Appendix

A-1

Appendix

Bay Command Console (BCC)

What is BCC? BCC Definition The Bay Command Console (BCC) is a command-line interface for configuring Bay Networks devices. BCC is a superset of the Technician Interface (TI) that allows you to enter TI commands and scripts at the BCC command line prompt.

Configurable parameters are added to a tree hierarchy, which is identified for each 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 console connections, just as the current Technician Interface.

r

Basic configurations started in BCC can be extended using Site Manager and vice versa.

.

BCC functionality will expand over several releases, providing integrated subsystems (config, show, debug, log, decode, task-oriented help) for platform management.

. . .

BCC is not a GUl-based application.

o

BCC is not a replacement for Site Manager. The BCC includes commands to build, view, navigate, and modify the BCC configuration tree.

Context-sensitive prompts help facilitate tree navigation.

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

A-2

BCC Appendix

Appendix

What is BCC?

BCC Gonfiguration Example 128-128.224.0

E1l

Paris AN

S12

,To Chicago

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

BGC Appendix

A-3

Appendix

Bay Command Console (BCC)

Phased lmplementation The BCC is being delivered in phases. BCC Version 4.05 is supported in BayRS Version 13.01. BCC will provide a complete integrated environment focused at Bay Networks embedded management for all router platforms. BCC platform coverage and functionality will continue to be extended over several BCC releases.

Current Functions The BCC performs the following functions:

o . o

Provides basic IP configuration and help for all router platforms lJses existing unabbreviated TI show and system commands

Includes features: A shell with TCL-like scripting language

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

Ability to view and edit configuration files in ASCII format Uses abbreviated BCC object names

-

"minimum to distinguish"

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

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

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

Appendix

Bay Command Console (BCC)

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

o o

8

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

3

MB of free local memory space

It will provide partial support for the ANH-8 and ANH-I2. There are some limitations with these platforms. You cannot use BCC commands to configure the hub or the operation of ISDN, DCM, or CSU/DSU daughterboards in an ANH. Note Please refer to release notes from the Bay Networks Web site for current details about local memory requirements.

A-6

BCC Appendix

Appendix

Using the BCC

Supported Platforms:

AN

ARN ASN BLN

BLN-2 BCN

ANH (partial support) System 5000

Processors Needed:

Check release notes for processor local memory requirements; 16 MB recommended.

BGC Appendix

A-7

Appendix

Bay Command Console (BCC)

Supported Protocols and lnterfaces You can use BCC commands to configure the following global protocols:

o o . . o . o o

IP (including

access policies and static routes)

IPX ARP OSPF (including accept and announce policies)

BGP (including accept and announce policies) IGMP

RIP (including accept and announce policies) Telnet

Supported lnterface Protocols You can use BCC commands to configure the following interface protocols:

.IP

. .

ARP

o

IGMP

o

OSPF

. .

Bay Networks Standard Point-to-Point

o Router Discover (RDISC) o PPP (certain line parameters on$)

Frame Relay

.

RIP

ATM

Supported lnterfaces You can use BCC commands to configure the following interfaces:

o o o . o o

A-8

Console

Ethernet Token ring Synchronous

FDDI HSSI

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

Bay Command Console (BCC)

Appendix

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

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

Class-A class is a template for a configurable object (such as an Ethernet interface or IP on an interface). When you add a new object to the configuration of a network device, the BCC creates a copy (an instance) of the appropriate template. Instance-A customized copy of any class object defined in the configuration tree for a Bay Networks device. For example, you can create (add) an instance ofthe protocol IP to run on a specific interface type, slot, and connector in a Model BLN router. You customize an instance with unique values for its required attributes.

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

o o

slot and connector (describing the location of the interface)

bofl (describing one functional aspect of the interface)

Required Attributev-The minimum set of attributes for which the BCC requires you to specify values. For example, the required attributes for a physical 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 specify customized values, replacing any default values set by the system. For example, 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 to disabled. Instance ldentifier-Uniquely identifies a single instance of an object configured on a Bay Networks device. The instance ID consists typically of the name of an object, combined with the values you specify for its required attributes. For example, the instance ID for an Ethernet interface consists of etherneU / . For some objects, the BCC automatically appends other (internal) data to make each instance ID unique across the entire device configuration.

A-10

BCC Appendix

Terminology and Concepts

Appendix

Terminology ^+S^s.hffi.ffi.KR

* oo*@ + board + ethertret oip

# riP # osBf G neigbbor

# rd,isc # arp * ignp o autoneg fddi oip #riB

BGC Appendix

A-11

Bay Command Console (BCC)

Appendix

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

Context-Your working location within the BCC configuration tree. Just as a UNIX file system has a current working directory within which you can add, modify, or delete files, the BCC configuration system has a current working context, within which you can add configurable objects, or modify or delete configured objects. The BCC always displays a context-sensitive prompt, indicating your current working 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 of a network device (box-wide); for example, TCP, SNMP, FTP, TFTP, NTP, and TELNET. Some protocols, such as IP and OSPF have box-wide as well as interface-specific objects. For example, IP contains BGP and OSPF, which in turn contain other box-wide/globally configurable objects. When you add IP on an interface, the BCC automatically finds, adds, and enables the boxwide/global IP object with all default settings. The BCC can also enable any box-wide/global objects that derive required attribute values from existing interface-level objects. The root-level context, box, contains all boxwide/globally configurable objects.

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

SIot-A location as well as a physical and electrical means for attaching modules to logic and power connections internal to a network device. Each slot in a Bay Networks device typically accommodates a processor or interface module (board) of some t5pe.

Lin*(l)

A physical (and on some devices, logical) circuit identified typically by means of a slot, connector, media t5pe, and (where applicable, such as with TI/EI facilities) a channel number. (2) The lowest common denominator for identifying a packet data stream. A-12

BCC Appendix

Appendix

Terminology and Concepts

Terminology (continued) BCC Command Hierarchy-Example on Model BLN/BCN Router

lta.tr

it

i1i*i

lr.

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

lrr-,::rird-tilgt

Global.$ea*ieo*

t

____________t Lodierl intirtsc{ *?rri6rs

Hlrdlsrre irlrllartn rrr|'i@as

;L-------I

1 l,:rtr*

BCC Appendix

litlilcl it; rl)*,i,li ill{}rij.+i

A-13

Bay Command Console (BCC)

Appendix

Terminology (continued) Connector-:fhe physical and electrical means to interconnect an interface module 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 logical point of termination for data sent or received by a specific protocol or application. For example, a UNIX workstation receives syslog messages from a remote device at UDP logical port number 162.

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

Circuit-Sometimes used by the BCC configuration system to denote (1) A dedicated communication path; for example, a Permanent or Switched Virtual Circuit (PVC or SVC) established between two hosts over a packet- or cellswitched 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 for transporting a particular packet stream over a physical interface. Connection-(1) A path for reliable communication between two network entities. The path can be physical or logical and the entities can be hardware/ software systems or subsystems and/or subsystems attached to the network medium. (2) The path between two networking protocol modules that provides reliable packet stream delivery service. (3) A temporary or perrnanently "provisioned" path supporting end-to-end communication between two entities on a network. Dial connections and SVCs are examples of temporary connections. Leased-line connections and PVCs are examples of permanently provisioned connections. Protocotr-This is a configurable object that typically supports datalink-, network-, transport-, session-, application-, or managementJayer services on a network device. Protocols may provide services box-wide (across all interface slots), 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

Terminology and Concepts

Terminology (continued) BGG Command Hierarchy-Example on Model BLN/BCN Router

i lIC:r

Jr

iiF l.*l':,tsirt

lri r:i

!:lJ:#:fiJ lii)$t

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

Lrno

{FlErlar€ rerr,icoc

+ lir{

BCC Appendix

iii!,iJt:l. i:t rTr*i,!,t

*i1ti:i;j

A-15

Bay Command Console (BCC)

Appendix

Term inology (continued)

Network-(1) A protocol-specific address that identifies the physical segment or area 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 and software that enable them to exchange data and share resources over short or long 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 from any configuration context.

A-16

BCG Appendix

Terminology and Concepts

Appendix

Term inology (continued)

BCC Gommand Hierarchy-Example on Model BLN/BCN Router

&lnb.sl Scrnicts

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

i{ilrdl,rilr" Flct{rtim +tt'eie*

I

|

]t':dl:j

-{ I.J

BGG Appendix

!:f:t

l.+ii{,:i

r1li.

r'tlliii,! tili:!}jl.ilt1

A-17

Bay Command Console (BCC)

Appendix

About the BCC Configuration Hierarchy The contents of the object class hierarchy (configuration tree) for each Bay Networks device defines its set of configuration commands. The tree differs somewhat from device to device, but the tree for every device occupies some portion of the primary BCC Network Data Model. Within this model, you configure similar objects in similar ways. For example, you can always configure an Ethernet interface on a Bay Networks device with the command:

box#

ethernet /

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

Just as a file system has directories that contain other directories, the BCC configuration 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 hierarchy that starts from a root level (implicitly, the or object) and branches to many other (child) object levels.

A-18

BCC Appendix

About the BCC Configuration Hierarchy

Appendix

BCC Gonfiguration Hierarchy Example

--t --f net

Box-wide/g lobal objects I

BCG Appendix

nterface-s pecif ic objects

A-19

Bay Command Console (BCC)

Appendix

BCC Configuration Process There are five basic steps you must take to complete a router configuration With 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 physically configured on the box. Use the information learned from the show config command to assign ports to your map.

4. Use the BCC to configure the router. 5. View and confirm the new configuration

A-20

using the show contig command.

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 using show 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

Bay Command Console

(BCC)

Appendix

Step 1: ldentify the Topology Map The first step to configure a router using the BCC is to identify the topolory map. 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

BCC Configuration

Appendix

Step 1: ldentify the ToPologY MaP 128.128.224.O

Paris AN

BGG Appendix

lro Ghicago 200.10.20.0

A-23

Appendix

Bay Command Console (BCC)

Step 2: Start BCG Configuration Mode The steps outlined below illustrate how to

access

the BCC and begin a

configuration.

l.

Access the Technician Interface and login as

Manager or LJser.

After you start the BCC interface, the Manager login allows you to enter any system command. A Manager login also allows, by default, read-write access to the device configuration. The User login allows you to enter only user-level system commands and allows read-only access to the device configuration. 2.

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

3.

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

If you enter BCC configuration mode as Manager and want to change your privilege level for the current session, you can do so by entering the following 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 prompt ends with >, you have read-only privileges.

A-24

4.

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

5.

When you finish using the BCC, enter the exit command to return to the TI prompt.

BGG Appendix

BCC Configuration

Appendix

Step 2: Start BGG Gontiguration Mode

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

Bay Networks,

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# cxit bcc> exit [2 :1]

$

BGG Appendix

A-25

Bay Command Console

(BCC)

Appendix

Step 3: ldentify Resources on the Box The show config command automatlcally identifies the hardware by default. is also used to view configured objects and configured parameters on Bay Networks devices.

It

Using the information gathered from the results of the initial show config command, assign the ports to your map topolory. The current physical device configuration can be seen in the following example.

A-26

BGG Appendix

BCC Configuration

Appendix

Step 3: ldentify Resources on the Box bcc> configr box# sho!il coaf,ig box tlpe frerbln board sfot. 1

tlpe

srml-

back

board slot 2 tlpe esafnf back

board slot

tlpe

3

slmc

back

board slot

4

tlpe dst416

back

board slot 5 tlpe dtok back

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

back back box# 128.128.224.O

E1l Paris

s12

Chicago

Assign physical ports

BCG Appendix

A-27

Bay Command Console (BCC)

Appendix

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

Using BCC commands at the root-level you can configure an Ethernet interface on 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 and levels (context) used to build the configuration.

A-28

BCC Appendix

BCC Configuration

Appendix

Step 4: Use BCC to Configure the Router Command Sequence

bcc> config box# cE 1,17. ethernet /I/t#

ip 128 .L28.224.LO12O tp / ]-28 .1'28 .224.10 / 255 .255 .240. 0# rip rj-p/I28.128 .224.1-0#

Configuration Levels

Box (root level) box# et

1./1

Ethernet (slot 1, connector

1

ethernet/1/1#

LS, t,28 .L28.224.LO 120

IP (add ress 1 28.1 28.224.1

ip/L28 .L28 .224

]-

O

2255.255.240.0#

-L0

rip

/

mask 255,255.240.0) RIP

BGG Appendix

rip/t28.]-28.224.1'0+

A-29

Bay Command Console (BCC)

Appendix

Step 5: View and Verify Gonfiguration Using show config After configuring a router, use the show config command to view the result of your configuration. The example on the following page illustrates the new configuration of the router after entering configuration commands.

A-30

BCC Appendix

BCC Configuration

Appendix

Step 5: View and Verify Gonfiguration Using show config box# show config box tlpe an board slot 1 tlpe ansedst

back

tftp

d.efault-volume

1

default-volume

1

back

back

console portnum 1 prompt tltslott:11$ ) auto-manager-script automgr. bat auto-user-script autouser. bat

ftp

back

telnet client back

back

ethernet slot L connector 1 circuj-t-name EllJaris-sm ip address t28 .728 .224.L0 mask

server prompt {[PARIS:TN]$ ]

255 .255.240.

arp back

rip

back back back

ip

back back snmp

corununity 1abe1 public access read-write manag'er address 0.0,0,0 back

arp back

back back back

back

box#

rip

manager/public/

0.0.0.0

tcp

back back

serial slot 1 connector 2 circuit-name 52 l-_chicago bofl-timeout 15 clock-source internal internal - clock- speed clkl-mb

standard ip address 200.10 .20.20 mask 255.255.255.o arp back

rip

back back back

BCC Appendix

A-31

Bay Command Console (BCC)

Appendix

Upgrading the BCC Help File The following information updates instructions relating to the BCC Help file mentioned in Upgrading Routers to BayRS Version 13.xx. If you received a flash card with the BayRS 13.01 (BCC 4.05) image, it should also contain the BCC Help file. The BCC looks for this file as soon as you enter the first help command after booting the router using the new version 13.01 image.

If the bcc.help file is not already on the default volume in the router, you must transfer it from the BayRS Version 13.01 software CD to that volume. The BCC Help file on the BayRS software CD has the name bcc_help. When you transfer that file to the router, be sure to rename it as bcc.help. (The version 13.01 router software is not configured by default to recognize the file name bcc-help.) To use BCC online Help, you must transfer the bcc_help file onto the router's flash card, then rename the file to bcc.help. You can specify a new path name for this Help file, and then save this change to your existing configuration file as follows:

$ bcc bcc> config box#

help-f i le-na me

box# save config



:

4ile_name.

he Ip>l



is the slot number on which you < file_name.help>

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

< config_filename>

A-32

want to store the Help file.

is the router configuration file name.

BCG Appendix

Appendix

Upgnding the BCC Hetp Fite

Upgrading the BCC Hetp Fite

specifying a new path name for a Herp fire and saving the change

$ bcc bcc> config box# herpfire-name :l box# save config

BGC Appendix

A-33

Appendix

Bay Command Console (BCC)

Displaying Online Help The BCC supports the following online help and help-oriented features: Command

Help Feature

Get help on commands:

help help -more

Get an overview of Help-oriented command features. Get more detail of Help-oriented command features.

?

List command or command options you can enter.

? ?

help commands

help commands -more help Example: To get fulldetails about the save command, enter help save. help syntax

Display all BCC commands in alphabetical order (syntax).

Note: Object and parameter names that you enter as configuration commands are not in this list. (Refer to the ? and helo tree commands later in this table.) Display more detail on all BCC commands in alphabetical order (svntax and terse command descriotions). Get full details about a specific command

Get Help about symbols used to express BCC command svntax.

Get conliquration data (anv BCC context or command mode): Show the device configuration tree, as follows: List, in hierarchicalformat, all objects configurable in the device conf igu ration tree. List, in hierarchicalformat, all objects configurable within the context of a specific box-level , where is board, console, ip, ftp, snmp, telnet, ftp, tftp, ethernet, tokenring, hssi, sync, fddi, or virtual on an AN or BN router.

help tree

. o

show config []

Show in sourceable BCC syntax the existing configuration of the total device or a configured object you identify by its

help tree

BCC instance lD.

A-34

BCC Appendix

AppendixDisplayingonlineHelp

DisPlaYing Online HelP

Get helP on commands: helP

helP -more ?

helP commands helP commands -more

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

show config []

A-35 BCC APPendix

Bay Command Console (BCC)

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. ? Get command usage Help and list parameter of an object you can add or modify from vour current location. Get the current value for this parameter of the current object. ? Get legal, current, and default values for this parameter of the current obiect. Get legal, current, and default values for this parameter of a ? configured object you can access from your current working Example: context or level.

Box# ethernetl2ll bofl ? Current Value: enable Legal Value: {enable disable} Default Value: enable

info help parameters

Lisl values currently assigned to parameters of this object. Describe parameters of the current object.

help parameters ffhe is the sequence of objects between root level and the

Describe parameters of an object outside the current context.

desired context.)

Example: help parameters ip ospf Hint: Use the help tree command to determine lhe to the desired obiect.

has lso

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 command lines.

A-36

BCC Appendix

-

Displaying Online Help

Appendix

Displaying Online Help

Get configuration data (BCC configuration mode): ?

? ?

? info

help parameters help parameters has lso

Get help on a specific task: help learning-bcc help editing

BCC Appendix

Appendix

Bay Command Console (BCC)

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,elete CAUTION

Deleting an object at one level of the configuration tree causes the BCC to automatically delete any attributes or parameters of that object. For example, deleting an instance of IP on an interface also deletes 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

Appendix

Bay Command Console (BCC)

Entering Commands Minimum to Distinguish For command input, the BCC interface allows you to shorten existing object *et" for Ethernet. This is the "minimum to and attribute names; for example BCC. distinguish" feature of The following table compares the same command in "long hand" vs. "minimum to distinguish".

Minimum to Distinguish

Long Hand

ethernet slot 2 connector ip address 128 -1-28.192.10

1

et 2/l

mask

ip

128 .a28 .]-92 .L0

/20

25s.25s.240 -0

Entering Multiple Commands per Line To enter multiple commands in the same line, t5rpe a semicolon (;) wherever you would press return to terminate a command. For example, to configure RIP on ipl L.2.3.41255.0.0.0 on Ethernet 21 1, enter:

box# eE 2lLiip 1.2.3.418irLp rip/t.2.3.4ti Continuing a Command Line You can continue a command line by entering a backslash (\) character at the end of the current text line. The BCC treats characters on the next physical line as part of the same BCC logical command line.

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

A-40

internal;in

BCG Appendix

Appendix

Entering Commands

Entering Gommands Minimum to Distinguish Long Hand

Minimum to Distinguish

ethernet slot 2 connector L ip address L28.L28.1-92.10 mask 255.255.240

et ip

Multiple Gommand Lines box# eE

riP/t

.0

2/L 128 .128 .L92 .1,0 /20

21L;ip 1.2.3.418iri:n

-2 -3 -4#

Continuing a Command Line

box# ser 3lL;cL 531_Iondon;bofl-t 15;cl-ock-g interrral;in clklmb; stand.ard.; iB 200. 50 . 60 .2O 124 iriln

BCC Appendix

A-41

Appendix

Bay Command Console (BCC)

Saving Configurations on a Workstation Overview A unique feature with BCC is the ability to view and edit configuration files in ASCII format.

Saving Gonfigurations If you log into an AN or BN router from a workstation using Telnet or terminal emulation, you can use the native capabilities of the workstation to:

.

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

file

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 from which the BCC can read configuration and system commands. Note

If you create or edit ASCII files containing BCC commands, you must adhere to the BCC syntax requirements. For example, you must include any commands necessary to navigate to each level of the device configuration tree, and any commands necessary to add, modify, or delete objects 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 configuration of Bay Networks devices of the same type and hardware configuration

Note

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

442

BGC Appendix

Saving Configurations on a Workstation

Appendix

Saving Configurations on a Workstation

Binary 101001010101010 101010101010101 010101010010001 000001011110101 010101010101010 101010101010101 010101010101010 101010011111010 001010101010100 100100101010101

BGG Appendix

ASCII bcc>coalLgf

bo*l tbd coafLgr box tl'Ira frcrbla borld aLot 1 trE. arD.l brch

borrd rlot 2 tyttc .rrlaf, back

A-43

Bay Command Console (BCC)

Appendix

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

Warning

The source command makes immediate changes to the active device configuration. The syntax for the source command is as follows: source :

A'44

BCC Appendix

Appendix

Saving Configurations on a Workstation

Retrieving a Configuration

Binary 101001010101010 101010101010101 010101010010001 000001011110101 010101010101010 101010101010101 010101010101010 101010011111010 001010101010100 100100101010101

BGG Appendix

ASCil bce>soatigf

box* rhor confl,gr bo,l t!'Da lrarb].D bor.rd rlot

1

tlDa rr:!.1

bech

borrd rlot

2

tyta arafnl

brck

A-45

Bay Command Console (BCC)

Appendix

Summary Summary of BCC In this unit, you learned the following:

A-46

.

The BCC currently supports configuration and task-oriented help. Planned releases will include monitoring, debugging, system commands, and shell with scripting.

o r .

BCC is supported on all router platforms. BCC uses different terms and concepts than the TL How to use the BCC Version 4.05 to configure routers running BayRS Version 13.01.

BCC Appendix

Appendix

Summary

BCC ExamPles and Quick Reference Sheets

BGC Appendix

A'47

Appendix

Bay Command Console (BCC)

BLN-2 Configuration Example Using the IP network topology and information below, we will configure the Boston router (BLN-Z).

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

128.128.128.O

128.128.160.0

129.128.

129.128.192.O

Six 129:128.U24.O

200.50.60.0

200.40.50.0

200.30.40.0

.10 .10 .10 Sydney.to 200.70.80.0

System lnformation

. o r o o . o . o . A-48

System Name is Boston

Location is Billerica Contact is John Doe Circuitless IP address will be I28.L28.32.1 (virtual) Enable FTP Enable TFTP

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

BOFL timeout = 15 seconds, Internal Clock Speed = I Mb IJse abbreviated names when configuring objects

BCG Appendix

BLN-2 Configuration Example

Appendix

Start BGG and Run show config After identifying the topology map, your first steps are to start BCC and enter the 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 config * To list all system commands, tYPe 2 * To exit the BcC, t)4)e exiL bcc> config box# gbow configt box tlpe frerbln board slot ltlpe srml back Lroard

slot 2 tlpe esafnf

back

board sloL

3

tlpe slmc

back

board slot

4

tlPe dst416

back

board slot 5 tlpe dtok back

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

back back box#

BGC Appendix

A-49

Bay Command Console (BCC)

Appendix

The results of the first show config command give you the information needed to create a map of available ports and locations on the router. Use this information to assign physical ports to the logical topology. The charts below are drawn based on information gathered on the previous page:

SLOT TYPE DESCRIPTION 5 DTR DUAL TOKEN R|NG (4/16 Mb) 4 DST DUAL SYNC, SINGLE TOKEN 3 SYNC QUADSYNC 2 ESAF4 ETHERNETSYNCADV. FILTER 1 SMRL SYSTEM RESOURCE MODULE SLOT

lffiEN r-l

ITo-'ffi'Tl

1d6fi1-l ]c-dMr-l lEoM-T-]

lTbffiTI

lddMr-l ldoMt-'l

lddMr-1 lc-dMT-l

l6Mf-l

|ffifi--l lffil

lcoN-S'CI

A-50

BCG Appendix

BLN-2 Configuration Example

Appendix

Assign Ports The next step is to assign ports.

Assign 128.128.128.O

ysical ports

128.128.160.0

E21_sm 051_london

To Atlanta

S32_atlanta S31_london

200.20.30.0

200.50.60.0

200.60.70.0

To London

BGC Appendix

A-51

Appendix

Bay Command Console (BCC)

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 2lL ethernet,/2/I# Lnfo on box state enabled

circuit-name E21 boston slot 2 connector

sm

1

bofl enable bofl-timeout 5 hardware-f ilter disable transmit-gueue-length 0 receive-queue-length 0 bofl-retries 5 bofl-tmo-divisor 1 bofl-number 0 ethernet/2/t# bo:x box# ser 3lLicL S31_london;bof1-t 15;c1ock-s interaal;in c1klmb serial/3/1# standard;iXr 200.50 .60.20 l24rELDrs'er 3lL serial/3 /l# 5,nf,o on box

state enabl-ed circuit-name S31 london slot.3

connector

1

bofl enabled bofl-timeout

15

mtu 1500 promiscuous disabled clock-source internal internal-c1ock-speed clk1mb signal-rnode balanced rts-enabl-e disabled

burst-count enabled service 11c1 crc-size crcl6bit

hold-down-time 0 slmc-1ine-coding nrz remote- loopback-detect ion di sabled. external-c1ock-speed 54102

serial/3 /I#

bolx

box# eer 3l2ici S32_atlanta;bof1-t 15;clock-s interrral;in cIklnb serial/3 / 2# stsrldard;ip 20O.2O.3O -20 124;rip;ewc box# ser 3lIicL S34jaris;bof1-t 15;clock-s interrral;in clklmb serial- / 3 / 4# etandard; ip L28 . L28. 150 . L0 | 2O ; rjrr, i cwc box#

A-52

BCG Appendix

BLN-2 Configuration Example

Appendix

box# to 5ll,icL o51 bos_loadoniip 200.60.70.2O124;rip;to 5/1 tokenring/5/L# Lafo on box state enabfed circuit-name 051 bos london

sl-ot

5

connector speed

1

1-6Me9f

bofl-number

0

tokenrinq/5/\# botr box# to 5l2icL O52_boslraris;ip 128 .1"28.L28.1"O l20irip;cwc box# vici "circuitless xF";ip L28.L28.32.t12o;v virtual-# info on box

circuit-name {circuitless IP} wirtual# box Doetriftp;tftp;telnet box# syg bogton;loc billericaiconta'ilohn telnet# c1i;senr;promlr { IBOSTON:TN] $ ]box extra characters after close-brace server# I>romlr { IBOSTON:TN] $ ];cwc box#

BCC Appendix

A-53

Appendix

Bay Command Console (BCC)

View Completed Configuration After entering all the configuration information, view your completed configuration by entering the show config command a second time.

box# show coafigr box t14pe frerbLn contact John Doe

system-name boston

location billerica

board slot

1

tlpe srml

back

board slot 2 tyge esafnf back

board slot

3

tlpe slmc

back

board slot

4

t149e dst416

back

board slot 5 tlpe dtok back

console portnum 1 prompt { lSslott: l-l $

}

script automgr . bat auto-user-script autouser. bat auLo-manager-

back

ethernet slot 2 connector 1 circuit-name E2 1_boston-sm ip address 128 .L28 -L92 -L0 mask 255 .255.240.0 arp back

rip

back back back

ip

arp back

rip

back

tcp back back

serial- slot 3 connector 1 circuit-name 53 1_london bofl-timeout 15 clock-source internal internal-c1ock-speed clk1mb

A-54

BGG Appendix

BLN-2 Configuration Example

Appendix

standard

ip address 200.50.50.20 mask 255.255-255.0 arp back

rip

back back back back

serial slot 3 connector 2 circuit-name 53 2-atlanLa bofl-timeout 15 cLock-source internal internal-c1ock-speed clk1mb standard ip address arp

200 .20 .30

.20 mask

255 .255.255 . 0

back

rip

back back back back

serial slot 3 connector 4 circuit-name 53 4l>aris bofl-timeout 15 clock-source internal internal-clock-speed clkl-mb standard ip address arp

128

.L28.160.10 mask 255 -255 -240.0

back

rip

back back back back

tokenring slot 5 connecLor 1 circuit-name 05 1-bos-london ip address 200.60.70.20 mask 255.255.255.0 arp

back

rip

back back back

BGG Appendix

A-55

Bay Command Console (BCC)

tokenring slot 5 connector 2 circuit-name 052_bos3aris ip address I28.1,28.I28.1,0 mask arp back

Appendix

255

.255.240.0

rip

back back back

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

arp back back back

ftp

default,-volume

2

default-volume

2

back

tftp

back

telnet client back

server prompt tIBOSTON:TNI$ ]

back back back box#

box# sxit bcc>

A-56

BCC Appendix

help tree Example

Appendix

help tree Example bcc> help trce Router Configuration Tree shows every object that you can configure (but is not necessarily configTured at this time) on this d.evice. You can use this list as a map to help you navigate within the device configuration tree.

The following hierarchical fist

To view only a specific branch of the configuration tree, enLer help tree , where is any **box-1eve1** object, such as

etherneL, ip, or telnet

bcc> hefp tree Reading helpfile index. Please wait The entire configuration tree is board

,

done.

virtual ip ftp http ntp

ospf neighbor

peer

snmp

conununity nEnager

trap-entity trap-event tftp

console

telnet client

server

bri

leased-1ine ppp

line ip rip

ospf neighbor arp ismp

relay ipx rip sap

static-route

adjacent-hosL BGG Appendix

A-€7

Bay Command Console (BCC)

Appendix

static-service

route- filter server-network- f i lter

server-name- filter ipxwan

rip

sap

static-route

adj acent-host

static-service route-filter

server-network- f i lter

server-name- filter standard

ip

arp

rip

ospf neighbor

rdisc ismp

relay ipx rip sap

static-route

adj acent-host

static-service

route- filter server-network- f i I Ler server-name- f il-ter

backup-circuit

out-phone-number schedule

cal-1er-resolut ion frame-re1ay dlcmi

signalling lapf default-service pvc

svc-options

ip

rip

ospf neighbor arp igmp

relaY

ipx rip

sap

static-route

adj aeent-host

static-service route-filLer A-58

BCG Appendix

Appendix

help tree Exampte

server_network_ f i 1 ter

server_nerme_f

service

ilter

pvc

svc-options

ip

rip ospf neighbor arp ismp

relay ipx rip sap

static_route

adjacent_host

static_service route_filter server_network_ fi 1 ter

server_name_filter ipxwan *.io -r sap

static_route

adj acent_host

st,atic-service route_filter server_network_ f i 1 ter

server_name_

backup-circuit

filter

out_phone_number

channel

schedule cal_1er_resolution

dial

1oca1-phone-number

ethernet

ip

arp

rip

ospf neighbor

rdisc ismp

relay ipx rip sap

static-route

adjacent-host

static-service route-filter server-network_ f i 1 ter

server-nElme-f auto-negt BCC Appendix

iLter

A-59

Bay Command Console (BCC)

Appendix

seriaL ppp

line ip rip osPf

neighbor

arp ismp

relay ipx rip sap sap

static-route adjacent-host static-service route-filter server-network- f i 1 ter server-nELme-f ilter ipxwan

rip

sap

static-route

adjacent-host

static-service route-filter

server-network- fi 1 ter server-name- filter

backup-circuit

out-phone-number schedule

ca11er-resolution

standard

ip

arp

rip

ospf neighbor

rdisc igmp

relay ipx rip sap

st,atic-route

adjacent-host

static-service

rout.e-f ilter server-network- f i 1 ter server-name- filter

backup-circuit

out-phone-number schedule

ca11er-resolution

frame-re1ay A-60

BGC Appendix

help tree Example

Appendix

dlcmi

signalling lapf default-service pvc

svc-options

ip ,

rip

ospf neighbor arp ismp

relay ipx rip sap

static-route

adjacent-host

static-service

route- filter s erver-network- f i 1 ter

server-name-filter service pvc

svc-options

ip

rip osPf neighbor arp ismp

relay ipx rip sap

static-route

adjacent-host

static-service

route- filter server-network- f i I ter server-name-f il-ter ipxwan

rip

sap

static-route

adjacent-host

static-service route-filter

erver-network- f i 1 ter server-name- filter s

backup-circuit

out-phone-number schedule

dial hssi

ca11er-resolution

BGG Appendix

A-61

Bay Command Console (BCC)

Appendix

ppp

line ip rip ospf neighbor arp ismp

relay ipx rip sap

static-route

adjacent-host

static-service route-filter

server-network- f i 1 ter server-nameipxwan

filter

rip

sap

static-route

adjacent-host

static-service route-filter

s erver-network- f i 1 ter server-name- fi1 ter standard

ip

arp

rip

ospf neighbor

rdisc ismp

relay ipx rip sap

static-route

adjacent-host

static-service route-filter

server-network- f i 1 t.er

server-name- filter frame-re1ay dlcmi

signalling lapf default-service pvc

svc-options

ip

rip

ospf neighbor A-62

BGC Appendix

help tree Example

Appendix

arp ismp

relay ipx rip sap

statiq-route adjacent-host sfatic-service route- filter server-network- f i I ter server-name- filter service pvc

svc-options ip rip ospf neighbor arp ismp

relay ipx rip sap

static-route

adjacent-host

static-service route-filter

server-network- f i 1 ter

server-nameipxwan

filLer

rip

sap

static-route adjacent-host static-service route- filter

s erver-network- f i 1 ter server-name- filter

backup-circuit

out-phone-number schedule

ca11er-resolution token-ring ip arp

rip

ospf neighbor rd.isc ismp

relay ipx rip sap BGG Appendix

A-63

Bay Command Console (BCC)

Appendix

static-route

adjacent-host

fddi ip

static-service route-f i1t.er server-network- f i lter server-name- filter arp

rip

ospf neighbor

rdisc isrnp

relay ipx rip sap

sLatic-route

adjacent-host

static-service

route- filter server-network- f i1 ter server-name- filter mcel

logical-1ine ppp

line ip rip

ospf neighbor arp ismp

relay ipx rip sap

sLatic-route adjacent-host static-service route-filter server-network- fi 1 ter server-name- filter ipxwan

rip

sap

st,atic-route

adj acent-host

static-service

route- f i1t,er server-network- f i 1 ter server-name- filter

backup-circuit

out-phone-number schedule A-64

BCG Appendix

helptree Example

Appendix

ca1ler-resolution standard

ip

arp

rip

ospf neighbor

rdisc ismp

relay ipx rip sap

static-route

adjacent-host

static-service route-filter

server-network- f il-ter server-name- filter

backup-circuit

out-phone-number schedule

ca11er-resolution frame-re1-ay

dlcmi

signalling Lapf

default-service pvc

svc-options

ip

rip

ospf neighbor arp ismp

relay ipx rip sap

static-route

adjacent-host

static-service route-filter

server-network-

f

i 1 ter

server-name-filter service pvc

svc-options

ip

rip osPf neighbor arp ismp

relay

BGG Appendix

A-65

Bay Command Console (BCC)

Appendix

apx

rip sap

static-route

adj acent-host

static-service route-filter

server-network- f i 1 ter server-name- filter ipxwan

rip

sap

static-route

adjacent-host

static-service route-filter

server-network- f i 1 ter server-narne- filter

backup-circuit

out-phone-number schedule

pri dial

ca11er-resolution

1oca1-phone-number mctl-

logical-line ppp

line ip rip

ospf neighbor arp ismp

relay ipx rip sap

static-route

adjacent-host

static-service

route- filter server-networkserver-n€rme-f ipxwan

f

i 1 ter

ilter

rip sap

static-route

adjacent-host

static-service route-f il-ter server-network- f i1 ter server-name-f i1t,er backup-circuit out-phone-number A-66

BCC Appendix

Appendix

help tree Example

schedule

ca1ler-resolution standard

ip

arp

rip

osPf neighbor

rdisc ismp

relay ipx rip sap

static-route

adjacent-host

static-service route-filter

server-network- f i 1 ter server-narne- filter

backup-circuit

out-phone-number schedule

ca11er-resolution franne-re1ay

dlcmi

signalling lapf default-service pvc

svc-options

ip

rip

ospf neighbor arp ismp

relay ipx rip sap

static-route

adjacent-host

static-service route-filter

server -network- f i 1 ter server-name- filter

service pvc

svc-options

ip

rip ospf neighbor arp ismp

BGG Appendix

A-67

Bay Command Console (BCC)

Appendix

relay ipx rip sap

static-route

adjacent-host

static-service route-filter

server-network- f i 1 ter

server-name- filter ipxvan

rip

sap

static-route

adjacent-host

static-service route-filter

server-network- f i 1 ter

server-name-filter backup-circuit out-phone-number schedule

pri dial

cal1er-resolution

loca1-phone-number

isdn-switch backup-poo1

ip

backup-1ine

access-policy

network adjacent-host arp ismp

relay static-route bgp

peer

debug-control accept match

aggregator-as

aggregator-router as conmrunity

network

originating-as

peer modify inj ect announce match

inbound-as conununity egrp-as A-68

BGC Appendix

help tree Example

Appendix

egp-gateway egp-peer network

next-hop

ospf-router-id ospf-tag outbound-as outbound-Peer inbound-Peer

rip-gateway

rip-interface modify

advertise community

debug-control ospf area sulruIra.ry

accept match ase-tag network modify announce match

bgp-as bgP-next-hoP bgp-Peer egp-as egP-gatewaY

egp-peer network rip-gatewaY

rip-interface

modify

rip

advertise

accept maLch

network

rip-gateway

rip-interface

modify announce match

bgp-as bgp-next-hop bgp-peer egl.I)-as

egP-gatewaY

egp-peer

i-nbound-interface

network

ospf-router-id ospf-tag

outbound-interface

BGG Appendix

A-69

Bay Command Console (BCC)

Appendix

rip-gateway modify advertise

tcp ipx s tatic-netbios-route bcc>

A-70 BCC 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 DOS hierarchy of directories and files. The BCC configuration tree for a network device contains:

.

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

.

Parameters-Attributes or properties of an object; slot, and connector are attributes 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 to the tree. Every object occupies a specific level, or context, within the tree, as shown below.

[-

riP

I

ip address 1.2.3.4 mask 255.0.0.0

box# (root

f-ethernet

slot 2 connector

1

______1

level)

rnet Slot 2 connector 2 ip address 2.3.4.5 mask 255.0.0.0

Note The boldface labels in the figure are the actual BCC commands used to create this configuration.

BCC Appendix

A-71

Appendix

Bay Command Console (BCC)

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> prompt and wait for the box# configuration prompt.

o

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

o

As you navigate between levels of the configuration tree, the BCC prompt changes to show your current location. The BCC indicates the current location by displaying the unique identifier of the configured object at your current 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 access RIP on one of the Ethernet interfaces configured above, type at 2lL;in t .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 in either dotted-decimal notation (for example, 255.255.255.0) or in standard decimal notation (for example,24, representing the number of bits reserved for the network portion of the IP interface address). For example: ip address 1L.23.13.14 mask 255.0.0.0 (or) iB LL.23.t3.t4l2s5.O.O.O (or) ip address LL.23.13.14 mask A (or)

ip

o

11

.23.L3.L418

Entering any of these commands creates an object with the unique 13 .t4 1255. 0. 0. 0

identifier Lpl11..23.

o

The BCC responds with helpful prompts whenever you leave out information required to configure an object.

o

To move back one level closer to root (box#) level, type back; to move back to root level, type cwc. To exit from BCC configuration mode, type exit. To exit the BCC and return to 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 still in effect,

Enter all commands using lowercase letters. You can abbreviate gbject names or parameter names; however, the abbreviations must_be unique. For exampre, two objects, fddi and ftp, exist at the root lever or j.hg BCC configuration tree for a BN router. To ret the BCC know which of these ob;ectJyou want to configure, you must minimally enter either fd or ft at the box# prompt. A-72 BCC Appendix

Appendix

BCC Quick Reference (AN/BN Routers)

o

EGG APPendix

The BCC does not recognize abbreviated system commands (commands available in any BCC mode); for example, the BCC will not recognize sh as show.

A-73

Appendix

Bay Command Console (BCC)

Common BGG Gommands The table below contains common BCC commands.

System help (from any BCC prompt)

help

Describe BCC help features.

help commands

Provide a list of commands you can enter from any BCC prompt.

help

Describe in full detail a specific command.

?

Provide usage help with terse examples for a specific command.

?

List the narnes of all commands you can enter here. Note: Press the spacebar to scroll through Help screens.

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

Configuration help (configuration

List the names of all objects and

mode only)

parameters you can configure, and commands you can enter, at the current level. Get usage (command entry) help, and list the parameters of this configurable object. (Example: ip ?) help parameters

Show definitions for parameters of the current object.

?

List the current, legal, and default values for this parameter of the current object. (Ethernet example: bofFretries ?)

?

List the current,Iegal, and default values for aparameter of this configured object, specified by its BCC insta.r.J tO.

List values currently assigned to

parameters of the current object.

List, by BCC instance ID, any objects configured in the current context. BCC Appendix

Appendix

BCC Quick Reference (AN/BN Routers)

Category

BCC Gommand Syntax

Task

Navigation

back

Go back one level closer to root level of

the configuration tree.

Configuration status

bor prompt.

history list. history list.

Exit the BCC and return to the Technician Interface prompt.

BCC Appendix

A-75

Appendix

Bay Command Console (BCC)

Common BCC Operations The BCC indicates when configuration parameters have values that are required Sou must supply a value). Other parameters have derived or default values supplied by the system. Task

BCC Command Syntax

Configure a physical interface

< i nte

Configure a protocol

rface _ty pe >



...

Modify parameter values

..

Disable, enable, or delete an object

disable [I enable [I delete []

A-76

Examples ethernet slot 3 connector et 3/1

1

ip address 192.168.3.4 mask 255.255.255.0 ip 1 92. 1 68.3 .41255.255.2s5.0 ip address 192.168.3.4 mask24 ip 192.168.3.4124 cache-size 64 ca 64 ip/

1

.2.3.4 1255. 0. 0. 0# d isable

fddi/1 I 1 # disable ip|l.2.3.41255.0.0.0 ipl 1 .2.3.41255. 0.0. 0# enable fddil 1 11 # enable ip|l.2.3.41255.0.0.0 ipl 1 .2.3.41255. 0.0. 0# delete tddil 1 I 1 # delete ipll .2.3.41255.0.0.0

BGC Appendix