Part Number 305418-A Rev. 00
BCC™ Quick Reference
The BCC Configuration Tree
The BCC uses a hierarchical tree configuration model similar to the DOS hierarchy of directories and files. The BCC configuration tree
for a network device contains:
•
Objects --
Physical or logical entities you can configure. An Ethernet interface or a protocol is an object.
•
Parameters
-- Attributes of an object;
slot
and
connector
are parameters of the object
ethernet
. Parameters have
values
;
for example,
slot 4
is a parameter-value pair.
Starting at the root level, you build a BCC configuration by adding objects to the tree. Every object occupies a specific level, or
context
, within the tree, as shown below.
The boldface labels in the figure are the actual BCC commands used to create this configuration.
Configuration Tips
• Start a BCC configuration session by logging in to the Technician Interface as
Manager
. Next, enter
bcc
and wait for the
bcc>
prompt. Enter
config
at the
bcc>
prompt and wait for the
box#
or
stack#
configuration prompt.
• To learn what you can enter next on your current command line, enter the question mark (
?
) command.
• Configure interfaces first, then add protocols. When you enter BCC configuration commands, you immediately modify
device behavior.
• As you navigate between levels of the configuration tree, the BCC prompt changes to show your current location. The BCC
indicates the current location by displaying the unique identifier of the configured object at your current location, for
example:
ip/1.2.3.4/255.0.0.0
.
• To access any object, type the path to that object. For example, to access RIP on one of the Ethernet interfaces configured
above, type
eth 2/1;ip 1.2.3.4/255.0.0.0;rip.
(Note that the BCC interprets each semicolon [ ; ] as if you had pressed the
Return key to start a new command line.)
• When you add IP to an interface, the BCC accepts the mask value in either dotted-decimal notation (for example,
255.255.255.0) or in standard decimal notation (for example, 24, representing the number of bits reserved for the network
portion of the IP interface address). For example:
ip address 11.23.13.14 mask 255.0.0.0
(or)
ip 11.23.13.14/255.0.0.0
(or)
ip address 11.23.13.14 mask 8
(or)
ip 11.23.13.14/8
Entering any of these commands creates an object with the unique identifier
ip/11.23.13.14/255.0.0.0
• To move back one level closer to root (box#) level, enter
back
; to move back to root level, enter
box
(AN/ARN/BN) or
stack
(ASN/System 5000).
• To exit BCC configuration mode, type
exit
. To exit the BCC and return to the Technician Interface prompt, type
exit
again.
To log out of the router, type
logout
. If you exit and then reenter the BCC without rebooting, configuration changes that you
made during the last BCC session are still in effect.
• Enter all commands using lowercase letters.
• You can abbreviate object and parameter names; however, the abbreviations must be unique. For example, two objects,
fddi
and
ftp
, exist at the root level of the BCC configuration tree for a BN router. To let the BCC know which of these objects
you want to configure, you must minimally enter
fd
or
ft
at the root-level (
box#
or
stack#
) prompt.
• You can abbreviate system commands; for example, the BCC recognizes
sh
as
show
in contexts where there are no other
command, object, or parameter names starting with
sh
.
ethernet slot 2 connector 1
(AN/BN/ARN)
ethernet slot 2 connector 2
(AN/BN/ARN)
ip address 2.3.4.5 mask 255.0.0.0
r
i
p
ip address 1.2.3.4 mask 255.0.0.0
rip
(
AN/BN/ARN
)
(
ASN/System 5000)
box#
stack#
ethernet slot 1 module 2 connector 2
(
ASN/System 5000)
ethernet slot 2 module 2 connector 1
(
ASN/System 5000)
Part Number 305418-A Rev. 00
Common BCC Commands
Category BCC Command Syntax Task
System help
(from any BCC
prompt)
help
help commands
help
<command>
?
<command>
?
<command> <option>...<option>
?
Describe BCC help features.
Provide a list of commands you can enter from any BCC prompt.
Describe a specific command in full detail. (Example:
help dinfo
)
Answer the question, “What can I enter next?”
Show usage help or next-level options for this command.
(Example:
show ip ?
)
Show usage help including any flags and arguments available to limit or
specify output from this command. (Example:
show ip interfaces ?
)
Configuration
help
(configuration
mode only)
help tree -all
help tree
?
<object>
?
help
<
object
> (or)
help
<
parameter
>
<parameter>
?
<BCC_instance_id> <parameter>
?
Show, in hierarchical format, every object configurable on this device.
Show the hierarchy of every object configurable on this branch of the BCC
configuration tree (context-sensitive command).
List the names of all objects and parameters you can configure, and system
commands you can enter, at the current level.
Get usage (command entry) help, and list the parameters of this
configurable object. (Example:
ip ?
)
Show usage (configuration) and parameter help associated with this object
or parameter name. (Example:
help ip
or
help bofl)
List the current, legal (allowed), and default values for this parameter of the
current object. (Example:
bofl-retries ?
)
List the current, legal, and default values for a parameter of this configured
object, specified by BCC instance ID. (Example:
ethernet/2/1 bofl ?
)
info
lso
List values currently assigned to parameters of the current object.
List, by BCC instance ID, any objects configured in the current context.
Navigation
back
box
(for AN, ANH, ARN, BLN, BCN)
stack
(for ASN and System 5000)
pwc
Go back one level closer to root level of the configuration tree.
Go all the way back to root level from any level in the tree.
Display the current working context, starting from root level.
Configuration
status
show config
show config
<BCC_instance_ID>
Command Options
(combine to
customize
show config
output):
-compact
-recursive
-verbose
-all
-file
<filename>
Note:
In BCC configuration mode,
do not import (
source
) the
contents of a file saved using the
-compact
option. Output of the
-compact
command excludes
back
commands necesary for
correct configuration.
Show the configuration of the current object only.
Example:
show config
Show the configuration of the specified object.
Example:
show config ip/1.2.3.4/255.0.0.0
Show the configuration without navigation (
back
) commands.
Example:
show config -compact
Show any dependent objects configured on this (current or specified) object.
Examples:
show config -recursive
show config -compact -recursive
show config ip/1.2.3.4/255.0.0.0 -recursive
Show the configuration, including all configurable parameters, including
those set to a default value.
Examples:
show config -verbose
show config -recursive -verbose
show config ip/1.2.3.4/255.0.0.0 -recursive -verbose
Show the total device configuration.
Examples:
show config -all
show config -all -verbose
Save the output of this command (affected by command options) to a file.
Examples:
show config -file boston.config
show config -recursive -verbose -file boston.config
Part Number 305418-A Rev. 00
Common BCC Operations
The BCC indicates when configuration parameters have values that are required (you must supply a value). Other
parameters have derived or default values supplied by the system.
For details on how to specify
slot
,
module
, and
connector
on the different router platforms, refer to
Using the Bay
Command Console (BCC)
.
Common Interface Conventions
The following table describes the conventions for slot, module, and connector numbering on each router platform.
Other
commands
Up arrow key (or Control+p)
Down arrow key (or Control+n)
Recall the previous command from the history list.
Recall the next command from the history list.
exit
Exit configuration mode and return to the
bcc>
prompt.
Exit the BCC and return to the Technician Interface prompt.
Task BCC Command Syntax Examples
Configure a physical interface.
AN/ARN/BN:
ASN/System 5000:
See also
“Common Interface
Conventions” (below).
<interface_type> <slot> <connector>
<interface_type> <slot> <module> <connector>
ethernet slot 3 connector 1
eth 3/1
ethernet slot 1 module 1 connector 2
eth 1/1/2
Configure a global or
interface-level protocol:
<protocol> <required_parameter> <value>
...
ip address 192.168.3.4 mask 255.255.255.0
ip 192.168.3.4/255.255.255.0
ip address 192.168.3.4 mask 24
ip 192.168.3.4/24
Modify parameter values.
<parameter> <new_value>
...
cache-size 64
ca 64
Disable, enable, or delete the
current object (the object named
in the current prompt).
Disable, enable, or delete this
child of the current object (an
object configured below the
current object).
disable
enable
delete
disable
[
<BCC_instance_id>
]
enable
[
<BCC_instance_id>
]
delete
[
<BCC_instance_id>
]
ip/1.2.3.4/255.0.0.0#
disable
ip/1.2.3.4/255.0.0.0#
enable
ip/1.2.3.4/255.0.0.0#
delete
fddi/1/1#
disable ip/1.2.3.4/255.0.0.0
fddi/1/1#
enable ip/1.2.3.4/255.0.0.0
fddi/1/1#
delete ip/1.2.3.4/255.0.0.0
Platform Syntax
AN/ANH
<interface> <slot> <connector>
•
<interface>
= interface type: ethernet, token-ring, serial, etc.
•
<slot>
= 1 (AN/ANH is a one-slot device).
•
<connector>
numbering starts with connector 1.
Example:
ethernet slot 1 connector 3
This is an Ethernet interface configured on AN/ANH connector 3, which exists on an Ethernet adapter module.
(Connectors 1 and 2 are on the base module.)
ASN
<interface> <slot> <module> <connector>
•
<interface>
= interface type: ethernet, token-ring, serial, etc.
•
<slot_number>
= 1, 2, 3, or 4, depending on the setting of the module ID switch on each ASN.
•
<module>
numbering corresponds to net module numbering (1 through 4) on each ASN.
•
<connector>
numbering starts at 1 on each net module (per media type).
Example:
ethernet slot 2 module 3 connector 2
This is an Ethernet interface on connector 2 of net module 3, in ASN 2 of a stacked ASN configuration.
(continued)
Category BCC Command Syntax Task
Part Number 305418-A Rev. 00
ARN
<interface> <slot> <connector>
•
<interface>
= interface type: ethernet, token-ring, serial, etc.
•
<slot>
= 1 (The ARN is a single-slot device.)
•
<connector>
numbering depends on the port type (LAN or WAN). LAN connector numbering starts at 1 on
the base module, which contains only LAN ports, and continues in ascending order, starting with the first
LAN port on an ARN expansion module. (The ARN expansion module plugs into the ARN base module.)
WAN connector numbering starts with connector 1 on WAN adapter module 1, continues with connector 2
on WAN adapter module 2, and ascends sequentially with WAN connectors 3 through
n
on the ARN
expansion module.
Example:
ethernet slot 1 connector 2
This interface is configured on LAN connector 2, which exists physically on an Ethernet expansion module.
(Ethernet connector 1 is on the base module.)
Example:
serial slot 1 connector 3
This is a serial (WAN) interface configured on WAN connector 3, which exists physically on the ARN expansion
module.
BN
<interface> <slot> <connector>
•
<interface>
= interface type: ethernet, token-ring, serial, etc.
•
<slot>
= 2 through 5 (BLN) or 1 through 14 (BCN).
•
<connector>
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.
System 5000
<interface> <slot> <module> <connector>
•
<interface>
= interface type: ethernet, token-ring, serial, atm, etc.
•
<slot_number>
= 2 through 13 in a System 5000 chassis.
•
<module>
numbering corresponds to net module 1 or 2, which plugs into a System 5000 base module.
A System 5000 base module is always module 3.
•
<connector>
numbering starts at 1 on each net module. The base module always contains a connector 1,
which plugs into a System 5000 backplane (for example, Ethernet, token ring, or ATM backplane).
Example:
ethernet slot 2 module 2 connector 1
This is an Ethernet interface on connector 1 of the Ethernet net module (module 2) in slot 2.
atm slot 2 module 3 connector 1
This is an ATM interface on connector 1 of slot 2, a Model 5782 Virtual Network Router (VNR) base module
(module 3). Note that the VNR does not accommodate any net modules.
Platform Syntax
ARN0006A
Adapter modules
Expansion module
Base module
COM3 COM4 COM5
COM
U
D
DD
B1
B2
RLSD
Run
Boot
Fail
Pwr
RPS
Fan
Base
Adapter1
Adapter2
Expansion
DCM
PCMCIA
BayStack Advanced Remote Node
RLSD3
RLSD4
RLSD5
1
2
Serial
Serial
ISDN BRI
withNT1
Tx
Rx
Cl
10BaseT
AUI
Ethernet 1
/