
Using the Bay Command Console (BCC™)
1-4
117383-B Rev. 00
Optional parameters -- The set of parameters for which you can optionally
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 system default value of
5 (5 retries), but you can change
this to another numeric value.
BCC instance identifier -- Uniquely identifies a single instance of an object
configured on a Bay Networks device. The BCC instance ID consists typically of
the name of an 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/1.
For some objects, the BCC automatically appends an internally generated number
to ensure 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 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.
Configuration hierarchy -- Classes (templates for creating objects) exist within a
tree hierarchy. Just as a file system has a root directory, subdirectores, and files,
the BCC configuration system has a root-level object (“box” or “stack”) and
branch objects such as interfaces and protocols fan out from root level in a tree
hierarchy. (The root level object for AN/ANH, ARN, and BN platforms is “box”;
the root-level object for ASN and System 5000 platforms is “stack”.)
The BCC configuration command hierarchy varies according to the type of
network device (for example, a particular type of router, hub, or switch). However,
BCC commands, such as
?, help tree, and back, enable you to efficiently
discover and navigate the configuration hierarchy. (You can view the configuration
hierarchy by entering the
help tree -all command at any BCC prompt.)
Kommentare zu diesen Handbüchern