Avaya BCC Reference guide

  • Hello! I am an AI chatbot trained to assist you with the Avaya BCC Reference guide. I’ve already reviewed the document and can help you find the information you need or explain it in simple terms. Just ask your questions, and providing more details will help me assist you more effectively!
Part Number 117402-A Rev. A
BCC™ Quick Reference (AN/BN Routers)
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 or properties of an object;
slot
and
connector
are attributes of the object
ethernet
.
Parameters also have
values
; for example,
slot 4
is a parameter-value pair.
Starting at the root level, you build a BCC configuration by adding objects to the tree. Every object occupies a specific
level, or
context
, within the tree, as shown below.
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#
configuration prompt.
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/192.168.3.4/255.255.255.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.)
Whenever you add IP to an interface, the BCC accepts the mask value in either dotted-decimal notation (for
example, 255.255.255.0) or in standard decimal notation (for example, 24, representing the number of bits
reserved for the network portion of the IP interface address). For example:
ip address 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
The BCC responds with helpful prompts whenever you leave out information required to configure an object.
To move back one level closer to root (box#) level, type
back
; to move back to root level, type
box.
To exit from BCC configuration mode, type
exit
. To exit the BCC and return to the Technician Interface prompt,
type
exit
again. To log out of the router, type
logout
. If you exit and then reenter the BCC without rebooting,
configuration changes that you made during the last BCC session are still in effect.
Enter all commands using lowercase letters.
You can abbreviate object names or 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 either
fd
or
ft
at the
box#
prompt.
The BCC does not recognize abbreviated system commands (commands available in any BCC mode); for
example, the BCC will not recognize
sh
as
show
.
(root level)
ethernet slot 2 connector 1
ethernet slot 2 connector 2
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
box#
Part Number 117402-A Rev. A
Common BCC Commands
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.
Category BCC Command Syntax Task
System help
(from any
BCC prompt)
help
help commands
help
<command>
<command>
?
?
Describe BCC help features.
Provide a list of commands you can enter from any BCC prompt.
Describe in full detail a specific command.
Provide usage help with terse examples for a specific command.
List the names of all commands you can enter here.
Note:
Press the spacebar to scroll through Help screens.
Configuration
help
(configuration
mode only)
help tree
?
<object>
?
help parameters
<parameter>
?
<instance_id> <parameter>
?
Show the BCC configuration tree. (List, in hierarchical format,
every object you can configure on this device.)
List the names of all objects and parameters you can configure,
and commands you can enter, at the current level.
Get usage (command entry) help, and list the parameters of this
configurable object. (Example:
ip ?
)
Show definitions for parameters of the current object.
List the current, legal, and default values for this parameter of the
current object. (Ethernet example:
bofl-retries ?
)
List the current, legal, and default values for a parameter of this
configured object, specified by its BCC instance ID.
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
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 [
<instance_id>
]
Show the configuration of the total device or a specific object,
for example,
show config
or
show config ip/1.2.3.4/255.0.0.0
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
<interface_type> <slot> <connector>
ethernet slot 3 connector 1
eth 3/1
Configure a
protocol
<protocol> <required_param> <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
<param> <new_value>
...
cache-size 64
ca 64
Disable, enable, or
delete an object
disable [
<ID>
]
enable [
<ID>
]
delete [
<ID>
]
ip/1.2.3.4/255.0.0.0#
disable
fddi/1/1#
disable ip/1.2.3.4/255.0.0.0
ip/1.2.3.4/255.0.0.0#
enable
fddi/1/1#
enable ip/1.2.3.4/255.0.0.0
ip/1.2.3.4/255.0.0.0#
delete
fddi/1/1#
delete ip/1.2.3.4/255.0.0.0
/