Using the Bay Command Console (BCC) BayRS Version 13.20 Site Manager Software Version 7.20 BCC Version 4.20 Part No.
Bay Networks, Inc. 4401 Great America Parkway Santa Clara, CA 95054 Copyright © 1999 Bay Networks, Inc. All rights reserved. Printed in the USA. April 1999. 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.
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.
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.
Contents Preface Before You Begin .............................................................................................................xiii Text Conventions .............................................................................................................xiv Acronyms .........................................................................................................................xvi Related Publications ..............................................................................
Navigating with Configuration Commands ...............................................................2-5 Moving Back One or More Levels ......................................................................2-5 Moving Back to Root Level ................................................................................2-5 Moving Forward One or More Levels .................................................................2-6 Moving to Any Context in the Device Configuration ......................................
Parameter Range Validation ............................................................................3-10 Specifying Name or String Values ...................................................................3-11 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 .........................
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 ........................
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 .......................................
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-12 Table A-1. Access Parameter Options ..................................................................... A-5 Table A-2. User Parameter Options ............................................................
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.
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.
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.
Using the Bay Command Console (BCC) Acronyms This guide uses the following acronyms: ARP Address Resolution Protocol ATM asynchronous transfer mode BCC Bay Command Console BofL Breath of Life DCM data collection module DRAM dynamic random access memory IP Internet Protocol IPX Internetwork Packet Exchange LAN local area network MAC media access control NVRAM nonvolatile random access memory OSPF Open Shortest Path First RIP Routing Information Protocol SNMP Simple Network Managem
Preface 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.
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.
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.
Overview of the BCC Multilevel 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 multilevel access features, refer to Appendix A, “Multilevel Access.
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.
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.
Using the Bay Command Console (BCC) The BCC displays 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.
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.
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.
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.
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.
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 Displaying Help on show Commands 2-26 Entering and Exiting the BCC Interface To access the BCC interface on a Bay Networks router: 1.
Using the Bay Command Console (BCC) The Manager login allows you to enter any system command and allows read-write access to the device configuration. The Operator login allows you to enter only operator-level system commands and allows limited 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.
Getting Started with the BCC 6. 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. 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.
Using the Bay Command Console (BCC) 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 [ ] n is the number of levels. Entering the back command with no argument moves you back one level closer to root level. Example: rip/192.168.125.34# back ip/192.168.125.34/255.255.255.
Getting Started with the BCC 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.
Using the Bay Command Console (BCC) 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.
Getting Started with the BCC 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# (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.
Using the Bay Command Console (BCC) 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. (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.
Getting Started with the BCC The optional arguments you add to these commands depend on what you want to see, as follows: Command Task show config Show the configuration of the current object only. (Entered without any command -
Using the Bay Command Console (BCC) Note: The show config command does not display the values of parameters currently set to their default values unless you use the -verbose argument.
Getting Started with the BCC • The total device configuration tree (active configuration only) • The IDs of all configured objects • The active configuration in compact format Displaying the Current Object To display the configuration of the current object, minus any dependent objects configured on the same branch, use the show config command.
Using the Bay Command Console (BCC) Example: box# show config ip/192.168.125.34/255.255.255.224 -r ip address 192.168.125.34 mask 255.255.255.224 broadcast 192.168.125.32 arp back rip back back Displaying Objects at the Next Subcontext Level To display by BCC instance identifier any objects configured at the next subcontext level accessible from your current location in configuration mode, use the lso or lso -list (lso -l) commands.
Getting Started with the BCC Example: box# eth 2/1 ethernet/2/1# show config -r ethernet slot 2 connector 1 circuit-name E21-alpha ip address 192.168.125.34 mask 255.255.255.224 broadcast 192.168.125.32 arp back rip back back back Output of the show config -r command includes any back commands necessary for navigation back from the current context to the prior context. Note: If you enter show config -r at root level in configuration mode, the BCC displays the same output as show config -all.
Using the Bay Command Console (BCC) prompt {"%slot%:"} auto-manager-script automgr.bat auto-user-script autouser.bat back ethernet slot 13 connector 1 circuit-name E131 ip address 192.168.133.114 mask 255.255.255.224 arp back rip back back back . . . . . . . . . Note: The BCC displays the same output as show config -all when you enter show config -recursive at root level in configuration mode.
Getting Started with the BCC box; snmp; community/public; manager/public/0.0.0.0 manager/public/192.32.241.36 box; snmp; community/public; manager/public/0.0.0.0; box; snmp; community/public; manager/public/192.32.241.36; . . . . . . . . . Example (from an IP interface on ethernet/2/1): ip/192.168.125.34/255.255.255.224# lso -r arp/192.168.125.34/1 rip/192.168.125.34 box; ethernet/2/1; ip/192.168.125.34/255.255.255.224; arp/192.168.125.34/1; box; ethernet/2/1; ip/192.168.125.34/255.255.255.224; rip/192.
Using the Bay Command Console (BCC) board slot 1 type srml board slot 2 type qenf board slot 3 type wffddi2m board slot 5 type dtok ftp default-volume 2 snmp lock-address 255.255.255.255 community label public . . . . . . . . .
Getting Started with the BCC To display the most detailed information on values for the same parameter, use the ? command: ethernet/2/1# bofl-timeout ? Current Value: 5 Legal Values: Default Value: 5 To display the value assigned to any parameter of an object configured at the next subcontext level, first obtain a list objects configured at the next subcontext level: ethernet/2/1# lso ip/192.168.125.34/255.255.255.
Using the Bay Command Console (BCC) Example (using the show config -verbose command): ethernet/2/1# show config -v ethernet slot 2 connector 1 circuit-name E21-alpha state enabled bofl enable bofl-timeout 5 hardware-filter disable transmit-queue-length 0 receive-queue-length 0 bofl-retries 5 bofl-tmo-divisor 1 From any configuration context, use the following command to display all parameter values associated with an object anywhere in the active device configuration: show config -verbos
Getting Started with the BCC show config [] -recursive -verbose or: show config [] -r -v Example: Display parameters of an object configured at the next subcontext level, relative to your current location in the device configuration tree.
Using the Bay Command Console (BCC) Example: Display parameters associated with all objects configured on ip/192.168.125.34/255.255.255.224: box# show config ip/192.168.125.34/255.255.255.224 -r -v ip address 192.168.125.34 mask 255.255.255.224 state enabled assocaddr 0.0.0.0 cost 1 . . . . . . arp state enabled back rip state enabled supply enabled . . . . . . . . .
Getting Started with the BCC Displaying the Total Device Configuration Tree (All Available Choices) To display, from any BCC prompt, every object you can choose to add to the current device configuration, use the help tree -all command. Example (BCN router): box# help tree -all The entire configuration tree is: board virtual ip ospf neighbor ftp http ntp peer snmp community manager trap-entity trap-event tftp console telnet client server atm atm-interface signaling timers signaling-vc ilmi ilmi-vc sscop .
Using the Bay Command Console (BCC) Displaying Choices Available from the Current Context To list the names of all objects and parameters you can access from the current context in configuration mode, enter the ? command. Example: ip/192.168.125.34/255.255.255.
Getting Started with the BCC Example: ethernet/2/1# help tree The configuration tree below this context is: ip arp rip ospf neighbor rdisc igmp relay ipx rip sap static-route adjacent-host static-service route-filter server-network-filter server-name-filter auto-neg Entering the help tree command at root level (box or stack) is the same as entering the help tree -all command from any configuration context.
Using the Bay Command Console (BCC) Example: ethernet/2/1# help ethernet Usage: "ethernet slot connector " Or: "ethernet /" ethernet Parameters: _________________________________________________________________ state Indicates the administrative state of this object (enabled or disabled). bofl Allows breath-of-life polls to be disabled. bofl-retries Specifies the BOFL Retry Count. . . . . . . . . .
Getting Started with the BCC This happens when you enter help ip: ethernet/13/1# help ip "help ip" is ambiguous. Copy and re-enter one of the following commands: help atm classical-ip-service ip help atm lec-service ip help atm lec-service ipx help atm pvc-service ip help atm pvc-service ipx help box ip help box ipx help demand-pool demand-circuit frame-relay default-service ip help demand-pool demand-circuit frame-relay default-service ipx . . . . . . . . .
Using the Bay Command Console (BCC) If you want to display the definition for a specific parameter of the current object only, enter help . (By default, the BCC displays the entire list of parameter definitions for the current object.) Saving Displayed Configuration Data For more information on using the show config -file command to save configuration data to a file, refer to “Saving Configuration Commands to a File on a Bay Networks Device” on page 3-14.
Getting Started with the BCC keyword is a subcommand that further specifies what aspect of object_name you want to see, such as show ip routes. Many show commands have multiple keyword levels, such as show frame-relay stats lapf errors. -filter is a command option that limits show command output to a specific subset or filtered view of the total information available.
Using the Bay Command Console (BCC) • To display every -filter and filter_argument available for a specific show command, insert the ? where filters and their arguments would appear after any keywords in the command line. Example: bcc> show frame-relay congestion ? show frame-relay congestion [-state ][-interface ][-service ] [-dlci ] Usage Notes: • Use the show command to display routing, configuration, interface, and statistical data from the Management Information Base (MIB).
Chapter 3 Entering Commands and Using Command Files This chapter provides information about the following topics: Topic Page Entering Commands 3-1 System Commands 3-5 Configuration Command Syntax 3-5 Creating and Using BCC Files 3-12 Entering Commands This section contains information about: 117383-D Rev 00 • Using Command Abbreviations • Recalling Commands • Editing Command Lines • Entering Multiple Commands on a Line • Continuing a Command Line 3-1
Using the Bay Command Console (BCC) Using Command Abbreviations When you enter BCC commands in configuration mode, you can shorten object and parameter names (for example, eth = ethernet). You must enter a sufficient number of characters for the BCC to recognize that name uniquely.
Entering Commands and Using Command Files Editing Command Lines Table describes the keystrokes you can use to edit BCC command lines. Table 3-1.
Using the Bay Command Console (BCC) Entering Multiple Commands on a Line To enter multiple commands on the same line, type a semicolon (;) wherever you would press [Return] to terminate a command. Example: Configure ethernet/2/1 from root, then configure ip/1.2.3.4/255.0.0.0 on ethernet/2/1 and RIP on ip/1.2.3.4/255.0.0.0, as follows: box# ethernet/2/1;ip 1.2.3.4/255.0.0.0;rip rip/1.2.3.
Entering Commands and Using Command Files Note: If you inadvertently type one of the opening symbols and see an underscore (_) prompt, just type the corresponding closing symbol to restore the normal (#) prompt in BCC configuration mode. System Commands The BCC supports all system commands described in Appendix B.
Using the Bay Command Console (BCC) Command Syntax Requirements BCC syntax consists of object names, parameter names and values, and various types of punctuation: • All object and parameter names appear as one word (hyphenated where necessary) in the BCC command line. • Parameters have either a single value or multiple values enclosed in braces {x y z} in the command line. You can accept the default value or supply a value for each parameter associated with a configurable object.
Entering Commands and Using Command Files required_parameter and value are required to add a new object, or to navigate to an existing object, in the device configuration. Any object may have one or more required parameters. For example, to add an Ethernet interface to an AN/ANH, ARN, or BN router, enter at root (box#) level: ethernet slot connector To add an Ethernet interface to an ASN or System 5000 router, enter: ethernet slot module
Using the Bay Command Console (BCC) The following commands are equivalent.
Entering Commands and Using Command Files Specifying Parameter Values You must specify each parameter value in the form of a parameter-value pair. Each pair is a command argument pertaining to the object named first in the command line. For example, the following command changes the Breath of Life (BofL) timeout interval to 4 seconds on ethernet/1/1: box# ethernet/1/1 bofl-timeout 4 bofl-timeout 4 is the parameter-value pair.
Using the Bay Command Console (BCC) Example: In the following example, you specify multiple parameter-value pairs on each command line. ethernet 2/1# ip address 1.2.3.4 mask 255.255.255.0 redirects off ip.1.2.3.4/255.255.255.0# ospf area 2.3.4.54 hello-interval 5 ospf/1.2.3.4# Specifying Multiple Values for One Parameter Some BCC configuration parameters accept multiple values simultaneously.
Entering Commands and Using Command Files If you try to enter a value outside of the legal value range for the mtu parameter, the BCC displays an error message to notify you of the problem: classical-ip-service/dallas# mtu 12000 For data type ‘int’: Bad input value: value ‘12000’ out of range Legal values: RANGE(0-9188) Specifying Name or String Values Many BCC configuration parameters accept an alphanumeric string value.
Using the Bay Command Console (BCC) Table 3-2. BCC Commands for Disabling, Reenabling, and Deleting Enter: To Perform the Following Function: disable Change the state of a configured object to disabled: ip/1.2.3.4/255.0.0.0# disable You can alternatively assign the value “disabled” to the state parameter : ip/1.2.3.4/255.0.0.0# state disabled enable Change the state of a configured object to enabled: ip/1.2.3.4/255.0.0.
Entering Commands and Using Command Files You can also save TCL scripting commands to a file, use the source command to read the file into device memory, and then run the script by entering an associated command name. For information on TCL scripting commands supported by the BCC interface, see Appendix C, “TCL Support.
Using the Bay Command Console (BCC) Saving Configuration Commands to a File on a Bay Networks Device You can save the output of any show config command to a file on a Bay Networks device. Output you save to a file using the show config -file command does not also appear on the console device. You can later use the BCC source command to import (merge) configuration data from a file into the active device configuration.
Entering Commands and Using Command Files When you finish editing the file, save it on your workstation or PC. The comments are for reference only. Comments do not appear in the output of any show config command. Importing Configuration Commands from a File When you are logged in to the BCC as Manager, you can use the source command in configuration mode to read BCC configuration and navigation commands from a designated ASCII source file into the active device configuration.
Chapter 4 Tutorial: Configuring a Bay Networks Router This chapter provides a tutorial that guides you through the initial configuration of a Bay Networks router using the BCC.
Using the Bay Command Console (BCC) 6. Exit BCC configuration mode, exit the BCC to the Technician Interface, and log out of the device. You may find it helpful to first diagram what you want to configure in terms of the BCC configuration tree or hierarchy for the device. Refer to the following sample router configuration. Sample Router Configuration The following example shows a sequence of commands you can use to configure a BCN router on a network.
Tutorial: Configuring a Bay Networks Router • Serial interface in slot 5 • Dual token ring interface in slot 9 • FDDI interface in slot 11 Figure 4-1. fddi/11/1 ethernet/13/4 ip telnet arp server ip arp ethernet/13/3 ethernet/13/2 ethernet/13/1 token-ring/9/2 token-ring/9/1 serial/5/1 box rip Global Services snmp rip tftp ftp community “public” manager 0.0.0.
Using the Bay Command Console (BCC) START/ CONTINUE Enter the name of any changed parameter to verify its new assigned value. Current prompt Enter ? for a list of objects and parameters configurable in this context of the configuration tree. Where necessary, enter the name of any parameter with a new value, for example: bofl disabled. Enter info to check parameter values assigned to the new (current) object. Enter the name of the next object you want to configure. (for example, ethernet).
Tutorial: Configuring a Bay Networks Router To create the sample configuration shown in Figure 4-1 using BCC commands: 1. Log on to the router as Manager, so that you can modify the device configuration. Bay Networks, Inc. and its Licensors. Copyright 1992, 1993, 1994, 1995, 1996, 1997, 1998. All rights reserved. Login: Manager Mounting new volume... Device label: Directory: 2: New Present Working Directory: 2: Welcome to the Backbone Technician Interface Router1> 2.
Using the Bay Command Console (BCC) 4. Check the hardware configuration of the router.
Tutorial: Configuring a Bay Networks Router 6. Check to see what you can configure (subcontexts and parameters) at this level. ethernet/13/1# ? Sub-Contexts: auto-neg ip ipx Parameters in Current Context: bofl circuit-name bofl-retries connector bofl-timeout hardware-filter bofl-tmo-divisor on receive-queue-length slot state transmit-queue-length System Commands: To list all system commands, type "help commands". For detailed help on a specific command, type "help ".
Using the Bay Command Console (BCC) 7. Add IP (address 192.168.133.114) to ethernet/13/1. ethernet/13/1# ip 192.168.133.114 Usage: "ip address mask " Or: "ip /" Required parameter "mask" was not specified for ip. The error message appears because the BCC requires you to enter a mask value whenever you create an IP interface.
Tutorial: Configuring a Bay Networks Router 9. Change the subnet mask to 255.255.255.224. ip/192.168.133.114/255.255.255.0# mask 255.255.255.224 "mask" parameter may not be modified ip/192.168.133.114/255.255.255.0# You cannot modify any parameter values included in the BCC instance ID of a configured object, in this case, ip/192.168.133.114/255.255.255.0.
Using the Bay Command Console (BCC) 12. Return to root (box) level to configure global system services. rip/192.168.133.114# box box# 13. Check which global services and interfaces you can configure at this level.
Tutorial: Configuring a Bay Networks Router 16. Check what you can configure next at this level. box# snmp snmp# ? Sub-Contexts: community trap-entity trap-event Parameters in Current Context: authentication-traps lock-timeout lock on lock-address scope-delimiter state type-of-service System Commands: To list all system commands, type "help commands". For detailed help on a specific command, type "help ".
Using the Bay Command Console (BCC) 19. Check the values currently assigned to parameters of this SNMP community. community/public# info on snmp label public access read-only scope-type {} 20. To allow network management applications (such as Site Manager) to modify the device configuration, change the value of the access parameter to read-write. community/public# access read-write community/public# 21. Define an SNMP manager for the router.
Tutorial: Configuring a Bay Networks Router 25. Check the values currently assigned to parameters of TFTP. tftp# info on box state enabled default-volume 2 retry-timeout 5 close-timeout 25 retry-count 5 26. Change the default volume number for TFTP to 5. tftp# def 5 tftp# 27. Verify the change to the default volume number. tftp# def default-volume 5 28. Add FTP globally to the router.
Using the Bay Command Console (BCC) 30. Check values currently assigned to parameters of FTP. ftp# info on box state enabled default-volume 2 login-retries 3 idle-timeout 900 max-sessions 3 tcp-window-size 60000 31. Change the default volume number to 5. ftp# def 5 ftp# 32. Verify the change to the default volume number. ftp# def default-volume 5 33. Recheck the total device configuration.
Tutorial: Configuring a Bay Networks Router 34. Return to root level. ftp# box box# 35. Save the file using a name other than config until you can test the configuration. box# save config startup.cfg 36. Test the intial IP interface. box# ping 192.168.133.114 IP ping: 192.168.133.114 is alive (size = 16 bytes) 37. Ensure that the initial IP interface connects to another device on the network. box# ping 192.168.133.97 IP ping: 192.168.133.97 is alive (size = 16 bytes) 38.
Using the Bay Command Console (BCC) 3. Verify that you disabled RIP. rip/1.2.3.4# state state disabled rip/1.2.3.4# You can also disable an object from its parent context, using the following syntax: disable Example: ip/1.2.3.4/255.0.0.0# ip/1.2.3.4/255.0.0.0# disable rip/1.2.3.4 Using this method, you remain in the current context after disabling the branch object.
Tutorial: Configuring a Bay Networks Router Example: ip/1.2.3.4/255.0.0.0# ip/1.2.3.4/255.0.0.0# enable rip/1.2.3.4 Using this method, you remain in the current context after enabling the branch object. Deleting a Configured Object Because of the tree hierarchy, objects on higher branches of the tree depend on the state (and existence) of objects closer to the root of the tree. Deleting an object also deletes anything configured on that object.
Using the Bay Command Console (BCC) You can also delete an object by entering the following command from its parent context: delete Example: ip/1.2.3.4/255.0.0.0# ip/1.2.3.4/255.0.0.0# delete rip/1.2.3.4 Using this method, you remain in the current context after deleting the branch object.
Appendix A Multilevel Access The Technician Interface provides, by default, two user logins: Manager and User, stored in nonvolatile RAM (NVRAM). 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 commands and allows read-only access to the device configuration.
Using the Bay Command Console (BCC) Multilevel Access Login To access a Bay Networks router using this feature, enter your login ID at the Login prompt, and enter your password at the Password prompt on your Telnet or console display: Login: Password: The Technician Interface prompt appears, enabling you to subsequently enter the bcc command to start the BCC interface. How Access is Granted Multilevel access grants access to a device by checking for a recognized name/ password pair.
Multilevel Access Access Privileges A user’s privilege level determines the system commands a user can execute. In addition to the existing manager and user privilege levels, a third level, that of operator, has been added. A manager privilege level account allows you to enter any system command and allows read-write access to the device configuration. An operator privilege level account allows you to execute most system commands, and allows limited access to the device configuration.
Using the Bay Command Console (BCC) Sharing Access Profiles To share user access profiles configured on one router across multiple routers: 1. Navigate in BCC configuration mode to a multilevel access context that you want to replicate on another router. 2. From the desired context, enter the following command: show config -recursive -file 3. Transfer the file from the local router to a target router. 4. Log on to the target router and enter BCC configuration mode. 5.
Multilevel Access box access users user groups group audit BCC0025A Figure A-1. Configurable Multilevel Access Objects Configuring Access The access object lets you set the minimum and maximum character string lengths for user and group names and passwords. You can also enable or disable the configuration of accounts from the access prompt.
Using the Bay Command Console (BCC) Table A-1.
Multilevel Access Table A-2.
Using the Bay Command Console (BCC) Configuring Audit The audit log includes the name of the command, the name of the user that issued the command, and a timestamp for all commands of the privilege level you specify. You can disable this feature by setting the parameter state to disabled. To configure audit, navigate to the audit prompt (for example: stack; access; audit) and enter values (or accept the default values) for the following parameters (Table A-4): Table A-4.
Multilevel Access BCC Lock Messages Multilevel access includes messages that identify which user has exclusive read-write access to the device configuration. The additional lock messages take the generic form: read-write mode in use by from {console | }, use -force to override. Example: read-write mode in use by testuser1 from 192.168.133.99, use -force to override This message appears when a user in BCC config mode is logged in using a Telnet session.
Using the Bay Command Console (BCC) This message appears when a Site Manager user attempts to open a dynamic configuration session on the same box with a BCC user currently in configuration mode. The user login and the string 255.255.255.255 indicate to the Site Manager user that this is a BCC session. Example: Snmp Error: Setting File System Action. This message appears when a Site Manager user attempts to use File Manager to transfer a file to or from a router that has a BCC user in configuration mode.
Appendix B System Commands The BCC supports the system commands listed in Table B-1. For more detailed information about any command that works from the Technician Interface as well as the BCC prompt: 117383-D Rev 00 • Enter help at any BCC prompt (for example, help save). • See Using Technician Interface Software.
Using the Bay Command Console (BCC) Table B-1. System Commands Login/Access Privileges Command Purpose Manager Operator User ? List the names of objects, parameters, and system commands you can enter next. ✔ ✔ ✔ ? Display syntax usage Help for .
System Commands Table B-1. System Commands (continued) Login/Access Privileges Command Purpose Manager compact : Compact existing files into a contiguous address space on a volume, and compact all unused space into a single contiguous block of free space for new files on the same volume. ✔ config [-read-write|-read-only] Enter BCC configuration mode.
Using the Bay Command Console (BCC) Table B-1. System Commands (continued) Login/Access Privileges Manager Operator User date [] [] Display or update the system time and time zone. [{+|-}] ✔ ✔ ✔ delete Delete the file from the specified volume. ✔ Delete the object described in the current prompt, or delete the object known by the specified and configured previously from the current level.
System Commands Table B-1. System Commands (continued) Login/Access Privileges Command Purpose Display network boot parameters. (Display the current parameter settings (Technician Interface, AN routers used to determine the source of image only) and configuration files. ) getcfg Manager Operator User ✔ ✔ ✔ help Display an overview of BCC Help-oriented features. ✔ ✔ ✔ help Display detailed Help on a specific command.
Using the Bay Command Console (BCC) Table B-1. System Commands (continued) Login/Access Privileges Command Purpose Manager Operator User help [ | -all] The help command, entered without arguments at the Technician Interface prompt, displays an alphabetical list of all commands with syntax only. The list excludes commands available only in BCC mode. ✔ ✔ ✔ Display the command history list or, for the Technician Interface only, recall command number from the history list.
System Commands Table B-1. System Commands (continued) Login/Access Privileges Command Purpose Manager Operator User log [:] [-d] [-t
Using the Bay Command Console (BCC) Table B-1. System Commands (continued) Login/Access Privileges Command Purpose Manager Operator User mset {|} .{|} .{} {} Modify (set) the values of data objects in the device MIB. ✔ ✔ partition {create|delete} [:] Create or delete a partition on existing file system media. ✔ ✔ ✔ password Manager Change the password of the Manager account. ✔ password User Change the password of the User account.
System Commands Table B-1. System Commands (continued) Login/Access Privileges Command Purpose Manager Operator User restart [] Restart the GAME image on the specified slot. If the slot ID argument is absent, the GAME image restarts on all slots. ✔ rm : Remove (delete) the file from the specified volume. ✔ save {config | aliases | log} : Store the current configuration, alias list, or system event.
Using the Bay Command Console (BCC) Table B-1. System Commands (continued) Login/Access Privileges Command Purpose Manager Operator User telnet [-d] [-e ] [ []] Communicate with other hosts supporting the Telnet protocol. ✔ ✔ ✔ Send files to, or retrieve files from, other hosts supporting TFTP. ✔ type [-x] : Display the contents of the designated file in ASCII or HEX (-x) format. ✔ ✔ ✔ xmodem {rb | sb} [y l w | p | n] ...
Appendix C TCL Support The BCC supports the following subset of Tool Command Language (TCL) scripting commands on the router platform: • append • for • lrange • switch • break • foreach • lreplace • unset • case • gets • lsearch • uplevel • catch • global • lsort • upvar • close • if • open • while • concat • incr • proc • continue • interp • puts • eof • join • rename • error • lappend • return • eval • lindex • set • exit • linsert
Appendix D System show Commands This appendix describes the following BCC system show commands. Topic Page show access D-2 show console D-4 show hardware D-7 show interface D-9 show process D-10 show system D-13 Note: For information about the show config command, see “Displaying Configuration Data” on page 2-8.
Using the Bay Command Console (BCC) show access The show access
System show Commands lock Displays information about the lock status of the user currently in configuration mode. The table includes the following information: Slot Device number of the slot being accessed. Lock User User currently in configuration mode. From Originating IP address or console. Port Port from which this user is accessing the device. Idle Time Time elapsed time since the last command was issued. users Displays information about each active user’s profile.
Using the Bay Command Console (BCC) show console The show console
System show Commands Parity Serial port’s current parity setting. Stop Bits Number of stop bits in the serial port’s configuration. Modem Enable Configuration of modem control, as follows: • Disabled - Port is directly connected to a device, such as a dummy terminal or a terminal server. • Enabled - Port is attached to a modem and modem leads are enabled. Lines/Screen Number of lines that the serial port displays before displaying the more prompt.
Using the Bay Command Console (BCC) Manager’s AutoScript Name of the script to run when the Manager account logs in to the router. If the script name does not contain a volume specifier, the system searches the volumes listed in “Initial Search Path.” User’s AutoScript Name of the script to run when the User account logs in to the router. If the script name does not contain a volume specifier, the system searches the volumes listed in “Initial Search Path.
System show Commands show hardware The show hardware
Using the Bay Command Console (BCC) memory [] Displays memory configuration and capacity information about all slots or a specific slot. The table includes the following information: Slot Slot number. Local Memory Total memory capacity in megabytes of the processor on the slot. Global Memory Current memory configuration in megabytes of the processor on the slot. Total Memory Total local and global memory in megabytes. proms Displays PROM information for all slots.
System show Commands show interface The show interface command displays information about all media-specific interfaces configured on the device. This command has only one option, summary. summary Displays high-level information about each media-specific interface. To see greater detail, use a show command, such as show ethernet
Using the Bay Command Console (BCC) show process The show process
System show Commands cpu [detail | total] Displays the CPU usage in hundredths of seconds and the percentage of total CPU time used by all processes on the router. detail Displays details about CPU usage for all processes. total Displays only CPU statistics totals. Note: For information about how to obtain a list of available processes, see the show process list command. The table includes the following information: Name The name of the process. Slot Slot number.
Using the Bay Command Console (BCC) memory [detail | total] Displays the number of bytes and the percentage of memory used by all processes on the router. detail Displays details about the amount of memory used by each process running on the router. total Displays only memory usage totals. The table includes the following information: D-12 Name The name of the process (if you specify the detail option). Slot Slot number. Used Number of memory bytes used by each process.
System show Commands show system The show system
Using the Bay Command Console (BCC) information Displays general system information (system name, contact, node location, image data, MIB version, and total uptime since last cold boot). memory Displays the global memory usage for all active slots in the system. Memory usage is not as volatile as buffer usage, so a low free percentage may indicate that you need more memory. The table includes the following information: Slot Slot number. Total Total number of memory (DRAM) bytes available on each slot.
System show Commands tasks Displays the number of tasks scheduled to run on all slots. This number is highly volatile and a large In Queue value does not necessarily indicate a problem. The table includes the following information: 117383-D Rev 00 Slot Slot number. Total Total number of tasks running on each slot. In_Queue Number of tasks scheduled to run. % in Queue Percentage of tasks scheduled to run.
Appendix E Syntax for Module Location Table E-1 lists the syntax for specifying the physical location of a module for each Bay Networks device that the BCC supports. Table E-1. Syntax for Specifying Module Location per Device Platform Syntax AN/ANH • = interface type: ethernet, token-ring, serial, etc. • = 1 (AN/ANH is a one-slot device). • numbering starts with connector 1.
Using the Bay Command Console (BCC) Table E-1. Syntax for Specifying Module Location per Device (continued) Platform Syntax ARN • = interface type: ethernet, token-ring, serial, etc. • = 1 (The ARN is a 1-slot device.) • numbering depends on the port type (LAN or WAN). LAN connector numbering starts at 1 on the base module, which contains only LAN ports.
Syntax for Module Location Table E-1. Syntax for Specifying Module Location per Device (continued) Platform Syntax BN • = interface type: ethernet, token-ring, serial, etc. • = 2 through 5 (BLN) or 1 through 14 (BCN). • numbering starts with connector 1 on each slot (per media type). Example: ethernet slot 8 connector 3 This is an Ethernet interface configured on connector 3 of slot 8 of a BCN router.
Appendix F BN Console Slot Election The BCC console slot election feature allows you to specify slots eligible to run the router console interface. From a list of slots that you specify, the software elects the slot with the greatest amount of available free memory. This feature helps ensure that the BCC has enough startup and runtime memory to operate. This feature currently applies only to multislot router platforms (BCN and BLN).
Using the Bay Command Console (BCC) Using the BCC to Customize Console Slot Election To limit the choice of slots considered by the console slot election routine: 1. Log on to the router. 2. Start the BCC. 3. Enter BCC configuration mode. 4. Check the current value of the console-slot-mask parameter used to configure the console slot election feature. box# console-slot-mask console-slot-mask {1 2 3 4 5 6 7 8 9 10 11 12 13 14} Each number represents a router slot. 5.
BN Console Slot Election 4. Enter the following command: console-slot-mask none If you want to permanently disable the console slot election feature, save this new configuration to a file. To reenable the console slot election routine at any time, start the BCC, enter configuration mode, and enter any BN slot numbers or all as the console-slot-mask parameter value.
Index A continuing, 3-4 editing, 3-3 entering, 3-1 Help, 2-26 pwc, 2-3 show console, D-4 show hardware, D-7 show process, D-10 show system, D-13 source, 3-15 system, B-1 acronyms, xvi B backplane hardware, D-7 BCC accessing, 2-1 command files, 3-12 commands entering, 3-1 show, D-1 system, B-1 configuration cycle, 4-4 defined, 1-1 Help, 2-26, B-5 platform requirements, 1-2 terminology and concepts, 1-6 BCC console slot election customizing, F-2 disabling, F-2 error message, F-3 reenabling, F-2 board, defi
E privileges, A-3 profiles, A-4 security, A-3 user object, A-6 editing commands, 3-3 educational services, xvii enable command, 3-12, 4-16 entering the BCC, 2-1 N G navigating using configuration commands, 2-5 using the back command, 2-4 global objects, defined, 1-7 O H objects defined, 1-6 deleting, 4-17 disabling, 4-15 enabling, 4-16 exiting the BCC, 2-1 hardware information, D-7 Help commands, 2-26, B-5 history buffer, 3-2 online Help, BCC, 2-26 I optional parameters, defined, 1-10 image,
S saving configuration commands, 3-13 serial port configuration, D-4 error statistics, D-6 show commands access, D-2 console, D-4 hardware, D-7 process, D-10 system, D-13 tcp, D-2 slot, defined, 1-9 slots, hardware, D-8 source command, 3-15 specifying a path, 2-6, 2-7 statistics, console, D-6 support, Bay Networks, xvii syntax configuration commands, 3-6, E-1 system information, D-14 T TCL support, C-1 technical publications, xvi technical support, xvii Technician Interface, 2-1 text conventions, xiv U Us
