Nortel Bay Command Console (BCC) Supplement Guide

Bay

_{Command Gonsole}

Supplement

NORTET

NETWORKS"

One Federal Street

Billerica, MA 01821 978 288-3460

February 1999

@ 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

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

Contents

Appendix

A Bay Command Console

(BCC)...

...A-1

Overview..

... A-1

What is

BCC?...

_{... A_.z}

Phased

Implementation...

... A-4

Using the

BCC...

... A-6

Terminolory and

Concepts...

.. A-10

About the BCC Configuration

Hierarchy

... A-18

BCC

Configuration...

_... A-ZO

Upgrading the BCC Help

File

... A-32

Displaying Online

He1p...

... A-34

Commands Managing

Objects...

... A-38

Entering

Commands

... A-40

Saving Configurations on a

Workstation...

_{... A-42}

Summary..

... A-46

BLN-2 Configuration

Example

... A-48

help tree

Example

... A-ST

BCC Quick Reference (ANIBN

Routers)

... A-21

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

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

Bay Command Console (BCC) Appendix

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.

.

BCC is not a replacement for Site Manager.

.

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

configuration tree.

o

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.

Appendix What is BCC?

BCC

Gonfiguration

Example

,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$

128-128.224.0

Paris

E1l

S12

AN

BGC Appendix A-3

Bay Command Console (BCC) Appendix

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

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

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.

Appendix Phased lmplementation

Phased lmplementation

BayRS

Version 13.01

supports:

Configuring

Task-oriented

help

Monitoring

System

commands

Bay Command Console (BCC) Appendix

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

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

BCC Appendix A-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 MB

recommended.

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

.IP

o

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

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

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

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 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 <slot>/ <connector>. For some objects, the BCC automatically appends

other (internal) data to make each instance ID unique across the entire device

configuration.

Appendix

Terminology

^+S^s.h-ffi.ffi.KR

*

_oo*@

+

board

+

ethertret

oip

#

riP

#

osBf

G

neigbbor

#

rd,isc

#

arp

*

ignp

o

_autoneg

fddi

oip

#riB

Terminology and Concepts

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

box-wide/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

box-wide/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.

Appendix

Terminology

(continued)

BCC Command

Hierarchy-Example

on Model BLN/BCN Router

Lodierl intirtsc{ *?rri6rs

Terminology and Concepts

Global.$ea*ieo* t

____________t

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

1

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

lta.tr i1i*i lr.

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

lrr-,::rird-tilgt

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 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 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).

Appendix

Terminology

(continued)

BGG Command

Hierarchy-Example

on

Model BLN/BCN Router

Terminology and Concepts

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

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.

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

Terminology and Concepts

&lnb.sl Scrnicts

]t':dl:j

-{

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

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 <slot>/<connector>

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 <box> or <stack> object) and branches to many other (child) object levels.

BCC Appendix A-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

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 using the show contig command.

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

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.

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

Bay Command Console (BCC)

Step 2:

Start

BCG

Configuration

Mode

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

configuration.

Appendix

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.

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

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. 2.

3.

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#

cxit

bcc>

exit

[2 :1] $ BCC Configuration 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.

It

is also used to view configured objects and configured parameters on Bay Networks devices.

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.

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

3

tlpe

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# BCC Configuration Chicago 128.128.224.O

Assign physical ports

Paris

E1l

s12

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.

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

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.

Appendix

Step 5: View and Verify

Gonfiguration

Using show

config

box# show config

box tlpe an board slot 1 tlpe ansedst back console portnum 1 prompt _tltslott:11$ )

auto-manager-script automgr. bat

auto-user-script autouser. bat

back

ethernet slot L connector 1 circuj-t-name EllJaris-sm ip address t28 .728 .224.L0 mask 255 .255.240. arp back rip back back back ip arp back rip back 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 back tftp d.efault-volume 1 back ftp default-volume 1 back telnet client back server prompt {[PARIS:TN]$ ] back back snmp

corununity 1abe1 public access read-write manag'er address 0.0,0,0 back back back back manager/public/ 0 . 0 . 0 . 0 box# BCC Configuration

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 <option> 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 <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.

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

_{<srot-number>:<fire_name.}

_hetp>l

box#

save

config

<config_filename>

BGC Appendix

Bay Command Console (BCC) Appendix

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 as

configuration commands are not in this list. (Refer to the ? and helo tree commands later in this table.)

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

help <command>

Example: To get _fulldetails about the

save command, enter help save.

Get full details about a specific command

help syntax Get Help about symbols used to express BCC command svntax.

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 or BN router.

show config

[<BCC_instance_id>]

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

BCC instance lD.

Displaying Online

Help

AppendixDisplayingonlineHelp

DisPlaYing Online HelP

Get

helP

on commands:

helP

helP

-more

?

helP

commands

helP

commands

_-more

helP <command>

helP sYntax

Get

configuration

data (any

BCC

context

or

command

mode):

helP

tree

helP

tree

<object>

show config

[<Bcc-instance-id>]

A-35

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.

<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: enable

Legal Value: {enable disable} Default Value: enable

Get legal, current, and default values for this parameter of a

configured object you can access from your current working context 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 of objects between root level and the desired context.)

Example: help parameters ip ospf

Hint: Use the help tree command to determine lhe <path> to the desired obiect.

Describe parameters of an object outside the current context.

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.

BCC Appendix A-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

Bay Command Console (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,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.

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

Bay Command Console (BCC) Appendix

Entering

Commands

Minimum

to

Distinguish

For command input, the BCC interface allows you to shorten existing object and attribute names; for example *et" for Ethernet. This is the "minimum to distinguish" feature of BCC.

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

to distinguish".

Long Hand Minimum to Distinguish

ethernet

slot 2

connector 1

et 2/l

ip

address 128 -1-28.192.10 mask

25s.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 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

internal;in

clkimb;

standard i

iO

2O0.50 .60 .2O

l24irip

BCG Appendix A-40

Appendix Entering Commands

Entering Gommands Minimum

to

Distinguish

Multiple Gommand Lines

box#

eE

21L;ip 1.2.3.418iri:n

riP/t

-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

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

Bay Command Console (BCC) Appendix

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.

Appendix

Saving

Configurations

on a

Workstation

Binary

Saving Configurations on a Workstation

ASCII

bcc>coalLgf

bo*l tbd coafLgr box tl'Ira frcrbla

borld aLot 1 trE. arD.l brch borrd rlot 2 tyttc .rrlaf, back 101001010101010 101010101010101 010101010010001 000001011110101 010101010101010 101010101010101 010101010101010 101010011111010 001010101010100 100100101010101 BGG Appendix 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 <volume> : <filename>

A'44

Appendix

Retrieving

a

Configuration

Binary

Saving Configurations on a Workstation

ASCil

101001010101010 101010101010101 010101010010001 000001011110101 010101010101010 101010101010101 010101010101010 101010011111010 001010101010100 100100101010101 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 BGG Appendix A-45

Bay Command Console (BCC)

Summary

Summary

of

BCC

In this unit, you learned the following:

.

The BCC currently supports configuration and task-oriented help. Planned releases

will

include monitoring, debugging, system commands, and shell

with 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 BayRS

Version 13.01.

Appendix

BCC ExamPles and

Quick

Reference Sheets

Summary Appendix

A'47

Bay Command Console (BCC) Appendix

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

*

To

list all

system commands, tYPe

*

_To

_{exit the}

BcC, t)4)e exiL bcc>

config

box# gbow _configt

box

tlpe frerbln

board

slot

l-tlpe

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

config

2 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

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

lffil

A-50 _{BCG Appendix}

Appendix

Assign

Ports

The next step is to assign ports.

To London

BLN-2 Configuration Example

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

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

sm

slot

2

connector 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#

Appendix

BCG Appendix A-52

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 1

speed 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

box# syg

bogton;loc billericaiconta'ilohn

Doetriftp;tftp;telnet

telnet#

c1i;senr;promlr

{ IBOSTON:TN]

$

]box

extra

characters

after

close-brace server# I>romlr { IBOSTON:TN]

$

];cwc box#

BLN-2 Configuration Example

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

_$

}

auLo-manager-

script

automgr . bat

auto-user-script

autouser. bat

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 Appendix A-54 BGG Appendix

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 200 .20 .30 .20 mask 255 .255.255 . 0 arp 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 128 .L28.160.10 mask 255 -255 -240.0 arp 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 BLN-2 Configuration Example 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 255 .255.240.0 arp back

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 back

tftp

default-volume

2 back

telnet

client

back server

prompt

tIBOSTON:TNI$ ] back back back box# box#

sxit

bcc> Appendix BCC Appendix A-56

Appendix help tree Example

help tree

Example

bcc>

help trce

Router

Configuration

Tree

The

following hierarchical fist

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.

To

view

only a specific

branch

of the configuration tree,

enLer help

tree

<object>,

where

<object>

is

any

**box-1eve1**

object,

such as

etherneL, ip, or telnet

bcc>

hefp

tree

Reading

helpfile

index. The

entire

configuration

board

virtual

ip

ospf neighbor

ftp

http

ntp

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 Please

tree is

wait

, done.

Bay Command Console (BCC)

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

Appendix BCG Appendix A-58

Appendix server_network_ _{f i 1}

_ter

server_nerme_f

_ilter

service 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_

_filter

backup-circuit

out_phone_number schedule cal_1er_resolution channel

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

_iLter

auto-negt BCC Appendix

help tree Exampte

Bay Command Console (BCC) 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 Appendix BGC Appendix

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

s erver-network- f i 1

ter

server-name-

filter

backup-circuit

out-phone-number schedule

ca11er-resolution

dial

hssi

BGG Appendix

help tree Example

Bay Command Console (BCC) 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-name-

filter

ipxwan

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 Appendix BGC Appendix A-62

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

filLer

ipxwan

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

help tree Example

Bay Command Console (BCC)

static-route

adjacent-host

static-service

route-f i1t.er

server-network- f i

lter

server-name-

filter

fddi

ip

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 Appendix BCG Appendix

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 helptree Example A-65

Bay Command Console (BCC) 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

ca11er-resolution

pri

dial

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-network- f i 1

ter

server-n€rme-f

ilter

ipxwan

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 Appendix BCC Appendix

Appendix 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

help tree Example

Bay Command Console (BCC)

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

cal1er-resolution

pri

dial

loca1-phone-number

isdn-switch

backup-poo1 backup-1ine

ip

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 Appendix BGC Appendix

Appendix help tree Example 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

advertise

rip

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) rip-gateway modify advertise tcp ipx s tatic-netbios-route bcc> Appendix A-70 BCC Appendix