Avaya Bay Command Console Users Manual V13.10, Using The (BCC)
2015-06-01
: Avaya Avaya-Bay-Command-Console-Users-Manual-734925 avaya-bay-command-console-users-manual-734925 avaya pdf
Open the PDF directly: View PDF 
.
Page Count: 130
Using the Bay Command
Console (BCC)
BayRS Version 13.10
Site Manager Software Version 7.10
BCC Version 4.10
Part No. 117383-C Rev. 00
November 1998
4401 Great America Parkway
Santa Clara, CA 95054
8 Federal Street
Billerica, MA 01821
Copyright © 1998 Bay Networks, Inc.
All rights reserved. Printed in the USA. November 1998.
The information in this document is subject to change without notice. The statements, configurations, technical data,
and recommendations in this document are believed to be accurate and reliable, but are presented without express or
implied warranty. Users must take full responsibility for their applications of any products specified in this document.
The information in this document is proprietary to Bay Networks, Inc.
The software described in this document is furnished under a license agreement and may only be used in accordance
with the terms of that license. A summary of the Software License is included in this document.
Trademarks
ACE®, AN®, BCN®, BLN®, BN®, FRE®, Optivity®, PPX®, Quick2Config®, and Bay Networks® are registered
trademarks and Advanced Remote Node™, ANH™, ARN™, ASN™, BayRS™, BaySecure™, BayStack™, BCC™,
SPEX™, System 5000™, and the Bay Networks logo are trademarks of Bay Networks, Inc.
Microsoft®, MS®, MS-DOS®, Win32®, Windows®, and Windows NT® are registered trademarks of Microsoft
Corporation.
All other trademarks and registered trademarks are the property of their respective owners.
Restricted Rights Legend
Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.
Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer
software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in
the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.
Statement of Conditions
In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the
right to make changes to the products described in this document without notice.
Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or
circuit layout(s) described herein.
Portions of the code in this software product may be Copyright © 1988, Regents of the University of California. All
rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the
above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising
materials, and other materials related to such distribution and use acknowledge that such portions of the software were
developed by the University of California, Berkeley. The name of the University may not be used to endorse or
promote products derived from such portions of the software without specific prior written permission.
SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
In addition, the program and information contained herein are licensed only pursuant to a license agreement that
contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed
by third parties).
ii
117383-C Rev. 00
Bay Networks, Inc. Software License Agreement
NOTICE: Please carefully read this license agreement before copying or using the accompanying software or
installing the hardware unit with pre-enabled software (each of which is referred to as “Software” in this Agreement).
BY COPYING OR USING THE SOFTWARE, YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF
THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS
UNDER WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these
terms and conditions, return the product, unused and in the original shipping container, within 30 days of purchase to
obtain a credit for the full purchase price.
1. License Grant. Bay Networks, Inc. (“Bay Networks”) grants the end user of the Software (“Licensee”) a personal,
nonexclusive, nontransferable license: a) to use the Software either on a single computer or, if applicable, on a single
authorized device identified by host ID, for which it was originally acquired; b) to copy the Software solely for backup
purposes in support of authorized use of the Software; and c) to use and copy the associated user manual solely in
support of authorized use of the Software by Licensee. This license applies to the Software only and does not extend
to Bay Networks Agent software or other Bay Networks software products. Bay Networks Agent software or other
Bay Networks software products are licensed for use under the terms of the applicable Bay Networks, Inc. Software
License Agreement that accompanies such software and upon payment by the end user of the applicable license fees
for such software.
2. Restrictions on use; reservation of rights. The Software and user manuals are protected under copyright laws.
Bay Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including any
revisions made by Bay Networks or its licensors. The copyright notice must be reproduced and included with any
copy of any portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use
for any competitive analysis, reverse engineer, distribute, or create derivative works from the Software or user manuals
or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer
the Software or user manuals, in whole or in part. The Software and user manuals embody Bay Networks’ and its
licensors’ confidential and proprietary intellectual property. Licensee shall not sublicense, assign, or otherwise
disclose to any third party the Software, or any information about the operation, design, performance, or
implementation of the Software and user manuals that is confidential to Bay Networks and its licensors; however,
Licensee may grant permission to its consultants, subcontractors, and agents to use the Software at Licensee’s facility,
provided they have agreed to use the Software only in accordance with the terms of this license.
3. Limited warranty. Bay Networks warrants each item of Software, as delivered by Bay Networks and properly
installed and operated on Bay Networks hardware or other equipment it is originally licensed for, to function
substantially as described in its accompanying user manual during its warranty period, which begins on the date
Software is first shipped to Licensee. If any item of Software fails to so function during its warranty period, as the sole
remedy Bay Networks will at its discretion provide a suitable fix, patch, or workaround for the problem that may be
included in a future Software release. Bay Networks further warrants to Licensee that the media on which the
Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days
from the date Software is first shipped to Licensee. Bay Networks will replace defective media at no charge if it is
returned to Bay Networks during the warranty period along with proof of the date of shipment. This warranty does not
apply if the media has been damaged as a result of accident, misuse, or abuse. The Licensee assumes all responsibility
for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained
from the Software. Bay Networks does not warrant a) that the functions contained in the software will meet the
Licensee’s requirements, b) that the Software will operate in the hardware or software combinations that the Licensee
may select, c) that the operation of the Software will be uninterrupted or error free, or d) that all defects in the
operation of the Software will be corrected. Bay Networks is not obligated to remedy any Software defect that cannot
be reproduced with the latest Software release. These warranties do not apply to the Software if it has been (i) altered,
except by Bay Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’s product,
resulting in the defect; or (iii) damaged by improper environment, abuse, misuse, accident, or negligence. THE
FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL
OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of
117383-C Rev. 00
iii
its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or
altered files, data, or programs.
4. Limitation of liability. IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY
COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR
PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN
IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT
SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT
EXCEED THE PRICE PAID TO BAY NETWORKS FOR THE SOFTWARE LICENSE.
5. Government Licensees. This provision applies to all Software and documentation acquired directly or indirectly
by or on behalf of the United States Government. The Software and documentation are commercial products, licensed
on the open market at market prices, and were developed entirely at private expense and without the use of any U.S.
Government funds. The license to the U.S. Government is granted only with restricted rights, and use, duplication, or
disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial
Computer Software––Restricted Rights clause of FAR 52.227-19 and the limitations set out in this license for civilian
agencies, and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS
252.227-7013, for agencies of the Department of Defense or their successors, whichever is applicable.
6. Use of Software in the European Community. This provision applies to all Software acquired for use within the
European Community. If Licensee uses the Software within a country in the European Community, the Software
Directive enacted by the Council of European Communities Directive dated 14 May, 1991, will apply to the
examination of the Software to facilitate interoperability. Licensee agrees to notify Bay Networks of any such
intended examination of the Software and may procure support and assistance from Bay Networks.
7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to
Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the
Bay Networks copyright; those restrictions relating to use and disclosure of Bay Networks’ confidential information
shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if
Licensee fails to comply with any of the terms and conditions of the license. Upon termination for any reason,
Licensee will immediately destroy or return to Bay Networks the Software, user manuals, and all copies. Bay
Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license.
8. Export and Re-export. Licensee agrees not to export, directly or indirectly, the Software or related technical data
or information without first obtaining any required export licenses or other governmental approvals. Without limiting
the foregoing, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that it will not, without first
obtaining all export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or divert
any such Software or technical data, or any direct product thereof, to any country to which such exports or re-exports
are restricted or embargoed under United States export control laws and regulations, or to any national or resident of
such restricted or embargoed countries; or (ii) provide the Software or related technical data or information to any
military end user or for any military end use, including the design, development, or production of any chemical,
nuclear, or biological weapons.
9. General. If any provision of this Agreement is held to be invalid or unenforceable by a court of competent
jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement
will be governed by the laws of the state of California.
Should you have any questions concerning this Agreement, contact Bay Networks, Inc., 4401 Great America Parkway,
P.O. Box 58185, Santa Clara, California 95054-8185.
LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND
AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS
AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN BAY NETWORKS AND
LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND
COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS
AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST BAY
NETWORKS UNLESS BAY NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN
EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT.
iv
117383-C Rev. 00
Contents
Preface
Before You Begin .............................................................................................................xiii
Text Conventions .............................................................................................................xiv
Acronyms .........................................................................................................................xvi
Related Publications .......................................................................................................xvii
How to Get Help .............................................................................................................xvii
Chapter 1
Overview of the BCC
Platform Requirements ...................................................................................................1-2
Number of BCC Sessions ...............................................................................................1-2
Multi-User Access ...........................................................................................................1-2
Terminology and Concepts .............................................................................................1-3
Configuration Hierarchy ............................................................................................1-3
Configuration Context ..............................................................................................1-5
Objects and Instances ..............................................................................................1-6
BCC Instance Identifier ......................................................................................1-7
Global (Box-Wide) Objects ................................................................................1-7
Physical Device Objects ....................................................................................1-8
Parameters .............................................................................................................1-10
Required ..........................................................................................................1-10
Derived ............................................................................................................1-10
Optional ...........................................................................................................1-10
117383-C Rev. 00
v
Chapter 2
Getting Started with the BCC
Entering and Exiting the BCC Interface ..........................................................................2-1
Displaying Your Location in Configuration Mode ............................................................2-3
Navigating in Configuration Mode ...................................................................................2-3
Navigating with the back Command .........................................................................2-3
Navigating with Configuration Commands ...............................................................2-4
Moving Back One or More Levels ......................................................................2-4
Moving Back to Root Level ................................................................................2-5
Moving Forward One or More Levels .................................................................2-5
Moving to Any Context in the Device Configuration ...........................................2-6
Displaying Configuration Data ........................................................................................2-8
Displaying Current/Active Configuration Data ..........................................................2-8
Displaying Configured Objects ........................................................................2-10
Displaying Configured Parameter Values ........................................................2-16
Displaying Configuration Choices ..........................................................................2-20
Displaying the Total Device Configuration Tree (All Available Choices) ...........2-21
Displaying Choices Available from the Current Context ..................................2-22
Displaying Choices Available at All Subcontext Levels ....................................2-22
Displaying Parameter Definitions ...........................................................................2-23
Saving Displayed Configuration Data .....................................................................2-26
Displaying Help on System Commands .......................................................................2-26
Displaying Help on Show Commands ..........................................................................2-26
Chapter 3
Entering Commands and Using Command Files
Entering Commands .......................................................................................................3-1
Using Command Abbreviations ................................................................................3-2
Recalling Commands ...............................................................................................3-2
Editing Command Lines ...........................................................................................3-3
Entering Multiple Commands on a Line ...................................................................3-4
Continuing a Command Line ....................................................................................3-4
System Commands ........................................................................................................3-5
vi
117383-C Rev. 00
Configuration Command Syntax .....................................................................................3-5
Command Syntax Requirements .............................................................................3-6
Using Basic (Full) Syntax .........................................................................................3-6
Using Default Syntax ................................................................................................3-7
Using Abbreviated Syntax ........................................................................................3-8
Specifying Parameter Values ...................................................................................3-9
Required, Derived, and Other Parameters ........................................................3-9
Specifying Multiple Parameter-Value Pairs ........................................................3-9
Specifying Multiple Values for One Parameter ................................................3-10
Specifying Name or String Values ...................................................................3-10
Disabling, Reenabling, and Deleting a Configured Object .....................................3-11
Creating and Using BCC Files ......................................................................................3-12
Saving Commands and Displays to a File on a Workstation ..................................3-12
Saving Configuration Commands to a File on a Bay Networks Device ..................3-13
Adding Comments to a Command File ..................................................................3-13
Importing Configuration Commands from a File ....................................................3-14
Saving the Active Configuration as a Bootable File ...............................................3-14
Chapter 4
Tutorial: Configuring a Bay Networks Router
Creating and Modifying a Device Configuration .............................................................4-1
Disabling a Configured Object ......................................................................................4-15
Enabling a Configured Object .......................................................................................4-16
Deleting a Configured Object .......................................................................................4-17
Appendix A
Multi-User Access
Multiuser Access Login .................................................................................................. A-2
Configuring Multiuser Access ........................................................................................ A-2
Configuring Access ................................................................................................. A-3
Configuring User ..................................................................................................... A-4
Configuring Group ................................................................................................... A-4
Configuring Audit ..................................................................................................... A-5
117383-C Rev. 00
vii
Appendix B
System Commands
Appendix C
TCL Support
Appendix D
System show Commands
show access .................................................................................................................. D-2
show console ................................................................................................................. D-4
show hardware .............................................................................................................. D-7
show interface ................................................................................................................ D-9
show process ............................................................................................................... D-10
show system ................................................................................................................ D-13
Appendix E
Syntax for Module Location
Index
viii
117383-C Rev. 00
Figures
Figure 1-1.
The Technician Interface and the BCC Interface .....................................1-1
Figure 1-2.
Sample BCC Configuration ......................................................................1-4
Figure 1-3.
Configuring IP and RIP on an Ethernet Interface ....................................1-5
Figure 1-4.
Location or Context in Configuration Mode ..............................................1-6
Figure 2-1.
Moving Away from Root Level ..................................................................2-6
Figure 2-2.
Navigating to an Object in the Configuration ...........................................2-7
Figure 2-3.
Navigating with the BCC Recursive Search Feature ...............................2-8
Figure 2-4.
Objects You Can Configure at the Next (Subcontext) Level ...................2-22
Figure 4-1.
Sample BCC Configuration (BCN Router) ...............................................4-3
Figure 4-2.
Typical BCC Configuration Cycle .............................................................4-4
Figure 4-3.
Configurable Multiuser Access Objects .................................................. A-2
117383-C Rev. 00
ix
Tables
Table 2-1.
Help for BCC System Commands .........................................................2-26
Table 3-1.
Keystrokes for Editing BCC Command Lines ...........................................3-3
Table 3-2.
BCC Commands for Disabling, Reenabling, and Deleting .....................3-11
Table 4-1.
Access Parameter Options .................................................................... A-3
Table 4-2.
User Parameter Options ......................................................................... A-4
Table 4-3.
Group Parameter Options ....................................................................... A-5
Table 4-4.
Audit Parameter Options ......................................................................... A-5
Table B-1.
System Commands ................................................................................ B-2
Table E-1.
Syntax for Specifying Module Location per Device ................................ E-1
117383-C Rev. 00
xi
Preface
The BCC is a command-line interface for configuring Bay Networks devices. If
you are responsible for configuring and managing Bay Networks®
AN®, ANH™, ARN™, ASN™, BN® (BCN® and BLN®), or System 5000™ routers,
read this guide to learn how to use the Bay Command Console (BCC™).
Before You Begin
This guide is intended for users who have some experience supporting a
multivendor internetworking system. You should be able to perform network
device configuration, maintenance, and troubleshooting.
Because the BCC makes real-time changes to device configuration, Bay Networks
recommends that you first learn about BCC behavior on a device not connected to
your production network.
Make sure that you are running the latest version of Bay Networks BayRS ™. See
the release and upgrading publications for information on how to upgrade to the
latest version.
117383-C Rev. 00
xiii
Using the Bay Command Console (BCC)
Text Conventions
This guide uses the following text conventions:
angle brackets (< >)
Indicate that you choose the text to enter based on the
description inside the brackets. Do not type the
brackets when entering the command.
Example: If the command syntax is:
ping , you enter:
ping 192.32.10.12
bold text
Indicates command names and options and text that
you need to enter.
Example: Enter show ip {alerts | routes}.
Example: Use the dinfo command.
braces ({})
Indicate required elements in syntax descriptions
where there is more than one option. You must choose
only one of the options. Unless explicitly instructed to
do so, do not type the braces when entering the
command.
Example: If the command syntax is:
show ip {alerts | routes}, you must enter either:
show ip alerts or show ip routes, but not both.
If the command sets a parameter value consisting of
multiple elements, you must type the braces as part of
the command if instructed to do so.
Example:
severity-mask {fault warning info}
brackets ([ ])
Indicate optional elements in syntax descriptions. Do
not type the brackets when entering the command.
Example: If the command syntax is:
show ip interfaces [-alerts], you can enter either:
show ip interfaces or show ip interfaces -alerts.
xiv
117383-C Rev. 00
Preface
ellipsis points (. . . )
Indicate that you repeat the last element of the
command as needed.
Example: If the command syntax is:
ethernet/2/1 [ ] . . . , you enter
ethernet/2/1 and as many parameter-value pairs as
needed.
italic text
Indicates file and directory names, new terms, book
titles, and variables in command syntax descriptions.
Where a variable is two or more words, the words are
connected by an underscore.
Example: If the command syntax is:
show at
valid_route is one variable and you substitute one value
for it.
screen text
Indicates system output, for example, prompts and
system messages.
Example: Set Bay Networks Trap Monitor Filters
separator ( > )
Shows menu paths.
Example: Protocols > IP identifies the IP option on the
Protocols menu.
vertical line ( | )
Separates choices for command keywords and
arguments. Enter only one of the choices. Do not type
the vertical line when entering the command.
Example: If the command syntax is:
show ip {alerts | routes}, you enter either:
show ip alerts or show ip routes, but not both.
117383-C Rev. 00
xv
Using the Bay Command Console (BCC)
Acronyms
This guide uses the following acronyms:
xvi
ARP
Address Resolution Protocol
ATM
asynchronous transfer mode
BCC
Bay Command Console
DCM
data collection module
DRAM
dynamic random access memory
IP
Internet Protocol
IPX
Internetwork Packet Exchange
LAN
local area network
MAC
media access control
OSPF
Open Shortest Path First
RIP
Routing Information Protocol
SNMP
Simple Network Management Protocol
SRM-L
system resource module-link
TCP/IP
Transmission Control Protocol/Internet Protocol
TFTP
Trivial File Transfer Protocol
WAN
wide area network
ARP
Address Resolution Protocol
ATM
asynchronous transfer mode
DCM
data collection module
DRAM
dynamic random access memory
IP
Internet Protocol
117383-C Rev. 00
Preface
Related Publications
For more information about using the BCC to configure or monitor (show)
behavior of a specific BayRS service, refer to the latest edition of the Task Map.
You can now print Bay Networks technical manuals and release notes free,
directly from the Internet. Go to support.baynetworks.com/library/tpubs/. Find the
Bay Networks product for which you need documentation. Then locate the
specific category and model or version for your hardware or software product.
Using Adobe Acrobat Reader, you can open the manuals and release notes, search
for the sections you need, and print them on most standard printers. You can
download Acrobat Reader free from the Adobe Systems Web site,
www.adobe.com.
You can purchase Bay Networks documentation sets, CDs, and selected technical
publications through the Bay Networks Collateral Catalog. The catalog is located
on the World Wide Web at support.baynetworks.com/catalog.html and is divided
into sections arranged alphabetically:
•
The “CD ROMs” section lists available CDs.
•
The “Guides/Books” section lists books on technical topics.
•
The “Technical Manuals” section lists available printed documentation sets.
Make a note of the part numbers and prices of the items that you want to order.
Use the “Marketing Collateral Catalog description” link to place an order and to
print the order form.
How to Get Help
For product assistance, support contracts, information about educational services,
and the telephone numbers of our global support offices, go to the following URL:
http://www.baynetworks.com/corporate/contacts/
In the United States and Canada, you can dial 800-2LANWAN for assistance.
117383-C Rev. 00
xvii
Chapter 1
Overview of the BCC
The BCC is a command-line interface for configuring Bay Networks devices.
After logging on to a device, you access the BCC by entering the bcc command at
the Technician Interface prompt (Figure 1-1).
Technician
Interface
Login
Access
the BCC
BCC
BCC0001B
Figure 1-1.
117383-C Rev. 00
The Technician Interface and the BCC Interface
1-1
Using the Bay Command Console (BCC)
From the bcc> prompt, you can:
•
Execute any system command not classified as “Technician Interface only”
(see Appendix B, “System Commands”).
•
Execute configuration commands to perform tasks such as creating or deleting
IP interfaces on the router. Enter BCC configuration mode by entering the
config command at the bcc> prompt.
Note: For a list of services you can configure using the BCC, see the Release
Notes. You can obtain a complete hierarchical listing of all objects
configurable on a device by entering the help tree -all command at any BCC
prompt.
Platform Requirements
The BCC runs on AN, ANH, ARN, ASN , System 5000, and BN platforms
including ARE, FRE®, and FRE-2 processor modules. Each slot must have:
•
16 MB of dynamic RAM (DRAM)
•
2 MB of free memory space available when you start the BCC
If you try to start the BCC with insufficient DRAM or free memory on a slot, the
BCC returns an error message. In that case, use Site Manager instead of the BCC.
Number of BCC Sessions
You can open one BCC session per slot in read-write (configuration) mode. Other
users can open additional BCC sessions in read-only (nonconfiguration) mode on
the same slot, depending on available memory. Each BCC session is mutually
exclusive. If you make a change during a BCC session in read-write mode, this
change does not appear in other BCC sessions.
Multi-User Access
Previous versions of the BCC allowed only two login levels: Manager and User.
With multi-user access, multiple users (each with a distinct user name and
password), can access the router simultaneously.
1-2
117383-C Rev. 00
Overview of the BCC
Multi-user access allows you to:
•
Add multiple user names, passwords, and access privileges to the router.
•
Manage the distribution of user names, passwords, and access privileges from
the BCC.
•
View event logs showing each BCC command issued and the user responsible
for issuing the command.
For more information on how to configure and use Multi-User Access features,
refer to Appendix A, “Multi-User Access.”
Terminology and Concepts
This section describes key terms and concepts of the BCC interface.
Configuration Hierarchy
The BCC configuration hierarchy begins at a root-level object, called box for
AN/ANH, ARN, and BN platforms, and stack for ASN and System 5000
platforms. Under the root-level object are branch objects such as interfaces and
protocols that fan out from root level in a tree hierarchy.
You use the help tree -all and show config -all commands to display the
configuration hierarchy of a Bay Networks router.
•
The help tree -all command displays the hierarchy of every object you can
configure. (These are the configuration choices you can make. These are not
objects already configured.)
•
The show config -all command displays the hierarchy of objects you have
actually configured.
Figure 1-2 illustrates a sample BCC configuration for an AN, BN, or ARN router.
117383-C Rev. 00
1-3
Using the Bay Command Console (BCC)
box
(root)
ospf
(protocol)
ip
(protocol)
arp
(protocol)
rip
(protocol)
snmp
(protocol)
telnet
(protocol)
tftp
(protocol)
BOX-WIDE/GLOBAL OBJECTS
(Services supported on all slots)
INTERFACE-SPECIFIC OBJECTS
(Services supported on a specific slot)
ospf/1.2.3.4
(protocol)
ethernet/2/1
(interface)
ip/1.2.3.4/255.0.0.0
(protocol)
ethernet/2/2
(interface)
arp/1.2.3.4/1
(protocol)
serial/3/1
(interface)
BCC0012C
Figure 1-2.
1-4
Sample BCC Configuration
117383-C Rev. 00
Overview of the BCC
You use BCC commands to create new objects and to modify or delete objects in
an existing configuration hierarchy. You begin at root level in BCC configuration
mode and navigate to objects in the device configuration tree.
For example, on a BLN router, you can use BCC commands to add a new physical
interface (such as Ethernet) on box, add IP to the Ethernet interface, and then add
RIP to IP on that interface. Figure 1-3 shows the sequence of commands necessary
to build this configuration.
box
box# ethernet/2/1
Ethernet
Slot 2
Connection 1
ethernet/2/1# ip address 1.2.3.4 mask 255.0.0.0
IP
Address 1.2.3.4
Mask 255.0.0.0
ip/1.2.3.4/255.0.0.0# rip
rip/1.2.3.4
rip/1.2.3.4#
BCC0017A
Figure 1-3.
Configuring IP and RIP on an Ethernet Interface
Configuration Context
Your working location within the BCC configuration tree is referred to as the
context. Just as a UNIX file system has a current working directory within which
you can add, modify, or delete files, the BCC configuration tree has a current
working context, within which you can add, modify, disable, reenable, or delete
objects.
117383-C Rev. 00
1-5
Using the Bay Command Console (BCC)
The BCC understands the context of an object in terms of its location along a path
that begins at the root level of the device configuration tree. Each semicolon in the
path marks a transition from one level to the next branch level in the device
configuration tree. The semicolon is also equivalent to a Return key entered at the
end of a command, effectively starting a new command line.
For example, if you configure an IP interface (address 1.2.3.4, mask 255.0.0.0) on
ethernet/2/1 of a BLN router, the BCC understands its location as
box; ethernet/2/1; ip/1.2.3.4/255.0.0.0 (Figure 1-4.).
box
box# ethernet/2/1
ethernet/2/1
ethernet/2/1# ip address 1.2.3.4 mask 255.0.0.0
ip/1.2.3.4/255.0.0.0
ip/1.2.3.4/255.0.0.0#
BCC0017B
Figure 1-4.
Location or Context in Configuration Mode
Objects and Instances
In BCC terminology, configurable entities are referred to as objects of a particular
class, each of which constitutes an instance.
•
1-6
An object is a configurable physical or logical entity such as a physical
interface or a protocol on an interface. Every configurable object belongs to a
specific class that defines its characteristics.
117383-C Rev. 00
Overview of the BCC
•
A class is a template for a configurable object (such as Ethernet or the
protocol IP). When you add a new object to the configuration of a device, the
BCC creates a copy (an instance) of the appropriate template.
•
An instance is an object uniquely identifiable within the total device
configuration. Each instance is identified by its BCC instance identifier.
BCC Instance Identifier
A BCC instance identifier uniquely identifies a single instance of an object
configured on a device. The BCC instance ID consists typically of the name of the
object, combined with the values you specify for its required parameters. For
example, the BCC instance ID for an Ethernet interface on a BN platform consists
of ethernet/slot/connector, as in ethernet/2/1; the BCC instance ID for an
Ethernet interface on an ASN platform consists of
ethernet/slot/module/connector, as in ethernet/1/2/2.
For some objects, the BCC automatically appends an internally generated number
to ensure the uniqueness of the BCC instance ID. For example, the BCC creates
an instance ID for ARP on IP based on the object name (arp), plus the address of
the underlying IP interface (1.2.3.4), plus an internally generated integer, resulting
in an ID such as arp/1.2.3.4/1.
In other rare cases, a configurable object may also have required parameters that
do not become part of its BCC instance ID. For example, the global OSPF object
has a required router-id parameter that does not become part of the instance ID.
(Many such required parameters end in “-id,” such as global-id and router-id.)
Each object has its own requirements for unique instance identification within the
total device configuration.
Global (Box-Wide) Objects
Global (or box-wide) objects provide services uniformly to all slots of a network
device. Examples include global IP, BGP, TCP, SNMP, FTP, TFTP, and Telnet.
Some protocols, such as IP, RIP, and OSPF, have global and interface-level
objects.
117383-C Rev. 00
1-7
Using the Bay Command Console (BCC)
Physical Device Objects
The following sections provide BCC terms for the physical device.
Box and Stack
The BCC uses the term box or stack to identify the root level of the BCC
configuration tree for a Bay Networks device. Every box or stack object has a type
parameter. The value assigned to the type parameter identifies the type of Bay
Networks device chassis:
type Value
Router Model
an
AN/ANH
arn
ARN
asn
ASN
freln
BLN
frecn
BCN
sys5000
System 5000
Board
The BCC uses the term board to identify any logic or circuit board in a Bay
Networks device. Each board typically occupies a slot in a network device. On
some Bay Networks products, one board may contain another board such as an
RMON data collection module (DCM). All board objects have a type parameter
that identifies its hardware type. For example, “qenf” is the value of the type
parameter for a Quad Ethernet with Hardware Filters board.
Note: For board descriptions based on the literal value of the type parameter
for any board object, see the Release Notes.
1-8
117383-C Rev. 00
Overview of the BCC
Module
The BCC uses the term module to identify network media-specific I/O modules
(for Ethernet, Token Ring, etc.). Each module has one or more connectors for
attachment to a physical network transmission medium.
Slot
The BCC uses the term slot to identify the location, as well as a physical and
electrical means, for attaching boards to logic and power connections available on
the device chassis. Note the following:
•
Multislot devices such as the BLN or BCN router accommodate a system
module (SRM-L) in one slot, and one link module in each remaining slot.
•
Single-slot devices such as the AN, ANH, ASN, and ARN routers
accommodate one base module (slot 1), which may be augmented by one or
two adapter modules, and one expansion module.
Connector
The BCC uses the term connector to identify the physical and electrical means to
interconnect a network device (slot or module) directly or indirectly to a physical
network transmission medium.
Line
The BCC uses the term line to identify the physical (and in some cases, logical)
circuit identified typically by means of a slot, connector, interface type (ethernet,
sync, fddi, and so on), and, where applicable, a channel number (such as with
T1/E1 interface types).
Port
The BCC uses the term port to identify an interface object defined by its type (for
example, an Ethernet port) and location (slot and connector) within a network
device. On a network device, a port is also a logical point of termination for data
sent or received by a specific protocol or application.
117383-C Rev. 00
1-9
Using the Bay Command Console (BCC)
Interface
The BCC uses the term interface to identify circuitry and digital logic associated
with the interconnection between a physical network medium (such as Ethernet)
and a higher-layer protocol entity (such as IP).
Note: A logical interface is an addressable entity for originating and
terminating connections across an IP network.
Parameters
A parameter is an attribute (or property) of a configurable object. Parameters can
be classified as one of the following:
•
Required
•
Derived
•
Optional
Required
For any BCC object, required parameters are a minimum set of parameters for
which the BCC requires you to supply values. For example, the required
parameters of a physical port are slot and connector.
Derived
Derived parameters are parameters for which the BCC supplies a value. For
example, a derived parameter of the global OSPF object is router-id. In this case,
the BCC derives a value for router-id from the address of the first IP interface
configured on the device.
Optional
Optional parameters are parameters for which you can specify customized values,
replacing any default values set by the system. For example, an optional parameter
of an Ethernet interface is bofl-retries. This parameter normally has a default
value of 5 (5 retries), but you can change this to another numeric value.
1-10
117383-C Rev. 00
Chapter 2
Getting Started with the BCC
This chapter provides information about the following topics:
Topic
Page
Entering and Exiting the BCC Interface
2-1
Displaying Your Location in Configuration Mode
2-3
Navigating in Configuration Mode
2-3
Displaying Configuration Data
2-8
Displaying Help on System Commands
2-26
Entering and Exiting the BCC Interface
To access the BCC interface on a Bay Networks router:
1.
Open a Technician Interface session with the target router.
For detailed information about opening a Technician Interface session, see
Using Technician Interface Software.
2.
Enter the Manager or User command at the Login prompt that appears
on your Telnet or console display.
The Manager login allows you to enter any system command and allows
read-write access to the device configuration. The User login allows you to
enter only user-level system command and allows read-only access to the
device configuration.
117383-C Rev. 00
2-1
Using the Bay Command Console (BCC)
3.
Enter bcc at the Technician Interface prompt.
Router1> bcc
Welcome to Bay Command Console!
* To enter configuration mode, type config
* To list all system commands, type ?
* To exit the BCC, type exit
bcc>
4.
Start BCC configuration mode by entering config at the bcc> prompt.
bcc>
box#
config
You enter configuration mode at the root (box) level of the BCC configuration
tree. The prompt ends with a pound symbol (#) if you have read-write
privileges (Manager only), or with a greater than symbol (>) if you have
read-only privileges (Manager or User).
If you enter BCC configuration mode as Manager and want to change your
privilege level for the current session from read-write to read-only, enter
config -read-only. To change Manager privileges back to read-write, enter
config -read-write. You cannot change your privilege level from read-only to
read-write if you logged in as User.
Caution: When you enter BCC configuration commands with read-write
privileges, you immediately modify the device configuration.
5.
When you finish using BCC configuration mode, enter the exit command
at any prompt.
box#
bcc>
6.
exit
When you finish using the BCC, enter the exit command at the bcc>
prompt.
bcc> exit
Router1>
Exiting the BCC returns you to the Technician Interface prompt.
2-2
117383-C Rev. 00
Getting Started with the BCC
For more detailed information about Technician Interface access, login, or logout
procedures, see Using Technician Interface Software.
Displaying Your Location in Configuration Mode
In configuration mode, the BCC displays a context-sensitive prompt. The prompt
identifies the configured object at your current working location within the
configuration hierarchy. For example, after logging in to a BLN router as
Manager, then configuring or navigating to the Ethernet interface on slot 2
connector 1, the BCC displays the following prompt:
ethernet/2/1#
To display the complete path from root level to your current level in the device
configuration tree, enter the pwc (print working context) command.
Example:
rip/192.168.125.34# pwc
box; ethernet/2/1; ip/192.168.125.34/255.255.255.224; rip/192.168.125.34;
The pwc command displays the BCC instance identifier of each configured object
in the path.
Navigating in Configuration Mode
You can navigate from one object to another in BCC configuration mode by using:
•
The back command
•
Configuration commands
Navigating with the back Command
In BCC configuration mode, use the back command to move a specific number of
levels back toward root level. The syntax for the back command is as follows:
back [ ]
Entering the back command with no argument moves you back one level closer to
root level.
117383-C Rev. 00
2-3
Using the Bay Command Console (BCC)
Example:
rip/192.168.125.34# back
ip/192.168.125.34/255.255.255.224# back
ethernet/2/1#
Entering the back command with an integer moves you from your current
working location, back toward root, the number of levels you specify.
Example:
rip/192.168.125.34# back 2
ethernet/2/1#
In this example, the back 2 command moves you from the current working
location (rip/192.168.125.34), back two levels to ethernet/2/1 (with
ip/192.168.125.34/255.255.255.224 as the intervening level).
Note: If you enter an integer value that exceeds the actual number of levels
back to root (box or stack) level, the BCC returns to root level.
Navigating with Configuration Commands
Using BCC configuration commands, you can:
•
Move back to a previous level.
•
Move back to root level.
•
Move forward to the next level.
•
Move from your current level to any other level in the device configuration
tree.
Moving Back One or More Levels
To move from your current working level back one or more levels closer to root
level of the device configuration tree, you can enter the full BCC instance ID of
the desired object, as follows:
Example (go back one level):
rip/192.168.125.34# ip/192.168.125.34/255.255.255.224
ip/192.168.125.34/255.255.255.224#
2-4
117383-C Rev. 00
Getting Started with the BCC
Example (go back two levels):
rip/192.168.155.151#
ethernet/2/1#
ethernet/2/1
In the second example, the BCC searches back toward root until it finds a context
or level where the object you specified (in this case, ethernet/2/1) exists in the
router configuration tree. The BCC enters the context of this object, and the
prompt displays your new location.
Moving Back to Root Level
You can move back to root level in configuration mode by entering the name of
the object at that level.
For an AN, ANH, ARN, or BN router, enter:
ip/1.2.3.4#
box#
box
For an ASN or System 5000 router, enter:
ip/1.2.3.4#
stack#
stack
Moving Forward One or More Levels
To move from your current working level to the next configured level (Figure 2-1),
enter the BCC instance ID of the desired object, as follows:
Example:
box# ethernet/2/1
ethernet/2/1# ip/1.2.3.4/255.0.0.0
ip/1.2.3.4/255.0.0.0# rip
rip/1.2.3.4#
Notice that a slash character (/) joins the name and any required parameter values
to make a BCC instance ID for any configured object.
117383-C Rev. 00
2-5
Using the Bay Command Console (BCC)
box
box# eth 2/1
(Starting
context)
ethernet/2/1
ethernet/2/1# ip/1.2.3.4/255.0.0.0
ip/1.2.3.4/255.0.0.0
ip/1.2.3.4/255.0.0.0# rip
rip/1.2.3.4
(Ending
context)
rip/1.2.3.4#
BCC0014B
Figure 2-1.
Moving Away from Root Level
Moving to Any Context in the Device Configuration
To navigate to any configured object, you can specify a full, or absolute, path from
root (box or stack) level at any prompt. When you enter a path, specify the BCC
instance identifier of each object.
Example:
To move from ip/192.168.33.66/255.255.255.0 (on ethernet/2/1) to rip/1.2.3.4 on
ethernet/2/2 (Figure 2-2), enter the following command:
ip/192.168.33.66/255.255.255.0# box;ethernet/2/2;ip/1.2.3.4/255.0.0.0;rip
rip/1.2.3.4#
2-6
117383-C Rev. 00
Getting Started with the BCC
(Starting context)
ethernet/2/1
ip/192.168.33.66/255.255.255.0
box
ethernet/2/2
rip
ip/1.2.3.4/255.0.0.0
(Ending context)
BCC0009B
Figure 2-2.
Navigating to an Object in the Configuration
The BCC can automatically search backward (recursively) toward root level until
it finds a level where the object you specify first in the command line exists in the
device configuration tree.
Example:
To move from ip/192.168.33.66/255.255.255.0 on ethernet/2/1 to rip/1.2.3.4 on
ethernet/2/2, enter the following command:
ip/192.168.33.66/255.255.255.0#
rip/1.2.3.4#
ethernet/2/2;ip/1.2.3.4/255.0.0.0;rip
In this example, the BCC searches backward to find ethernet/2/2 (specified first in
the command line), and then moves sequentially to the other locations
(ip/1.2.3.4/255.0.0.0 and rip) specified next in the command line.
117383-C Rev. 00
2-7
Using the Bay Command Console (BCC)
(Starting context)
ip/192.168.33.66/255.255.255.0
ethernet/2/1
box
ethernet/2/2
rip
ip/1.2.3.4/255.0.0.0
(Ending context)
BCC0009C
Figure 2-3.
Navigating with the BCC Recursive Search Feature
Displaying Configuration Data
There are several BCC help commands that let you:
•
Display information on objects in the active (actual) device configuration.
•
Display information on objects that you can add to the current configuration.
These are ? and help tree [-all].
Displaying Current/Active Configuration Data
With the show config and lso commands, you can display:
•
The current device configuration
•
The operating parameters of each configured object
•
The values set for the parameters of each configured object
The optional arguments you add to these commands depend on what you want to
see, as follows:
2-8
117383-C Rev. 00
Getting Started with the BCC
Command
Task
show config
Show the configuration of the current object only. (Entered
without any command -