Brocade, Brocade Assurance, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, MLX, NetIron, SAN Health, ServerIron,
TurboIron, VCS, and VDX are registered trademarks, and AnyIO, Brocade One, CloudPlex, Effortless Networking, ICX, NET Health,
OpenScript, and The Effortless Network are trademarks of Brocade Communications Systems, Inc., in the United States and/or in
other countries. Other brands, products, or service names mentioned may be trademarks of their respective owners.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning
any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to
this document at any time, without notice, and assumes no responsibility for its use. This informational document describes
features that may not be currently available. Contact a Brocade sales office for information on feature and product availability.
Export of technical data contained in this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with
respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that
accompany it.
The product described by this document may contain “open source” software covered by the GNU General Public License or other
open source license agreements. To find out which open source software is included in Brocade products, view the licensing
terms applicable to the open source software, and obtain a copy of the programming source code, please visit
http://www.brocade.com/support/oscd.
Brocade Communications Systems, Incorporated
Corporate and Latin American Headquarters
Brocade Communications Systems, Inc.
130 Holger Way
San Jose, CA 95134
Tel: 1-408-333-8000
Fax: 1-408-333-8101
E-mail: info@brocade.com
European Headquarters
Brocade Communications Switzerland Sàrl
Centre Swissair
Tour B - 4è me étage
29, Route de l'Aéroport
Case Postale 105
CH-1215 Genève 15
Switzerland
Tel: +41 22 799 5640
Fax: +41 22 799 5641
E-mail: emea-info@brocade.com
Asia-Pacific Headquarters
Brocade Communications Systems China HK, Ltd.
No. 1 Guanghua Road
Chao Yang District
Units 2718 and 2818
Beijing 100020, China
Tel: +8610 6588 8888
Fax: +8610 6588 9999
E-mail: china-info@brocade.com
Asia-Pacific Headquarters
Brocade Communications Systems Co., Ltd. (Shenzhen WFOE)
Citic Plaza
No. 233 Tian He Road North
Unit 1308 – 13th Floor
Guangzhou, China
Tel: +8620 3891 2000
Fax: +8620 3891 2111
E-mail: china-info@brocade.com
The following table describes the features introduced in R2.1.0.x.
EnhancementDescription
Supports SFTP file transferAdded information about using SFTP for file transfer. See “copy” on page 67 and
“Copying Files via FTP/SFTP/TFTP or HTTP” on page 653.
Supports additional privacy
encryption methods for
SNMPv3
Supports configuration of
LACP timeout
Added AES128, AES192 and AES256 privacy encryption methods for SNMPv3.
Refer to “snmp-server user” on page 117, “Configuring Local SNMPv3 Users” on
page 940, and “Configuring Remote SNMPv3 Users” on page 942.
The LACP timeout the switch waits for the next LACPDU can be configured to a
long or short interval. Refer to “lacp timeout” on page 296 and “Configuring a
Dynamic Trunk” on page 698.
Summary of enhancements for Brocade R2.0.2.10
The following table describes the features introduced in R2.0.2.10.
EnhancementDescription
Supports adjusting the system
clock for summer time
SNMP trap manager can be
configured with IPv4 or IPv6
address
IP address for a Layer 3
interface can be configured
with a network prefix
Action and Shutdown Interval
were added to the web page
for Loopback Detection
Web page for displaying ACL
statistics was re-designed
New options were added to
the web configuration page for
ERPS domains
Added configuration pages and CLI commands for adjusting the system clock for
the summer time offset. See the relevant commands starting on page 96 and
“Configuring Summer Time” on page 665.
SNMP trap managers can now be configured with IPv4 or IPv6 address. Refer to
“snmp-server host” on page 113 and “Specifying Trap Managers” on page 944.
The IP address for a Layer 3 interface can be configured with a network prefix in
the CLI. Refer to “ip address” on page 590
Action and Shutdown Interval were added to the web page for Loopback
Detection. Refer to “Configuring Loopback Detection” on page 761.
Configuration fields were modified, and a button to clear the hit counter was
added to the web page for displaying ACL statistics. Refer to “Showing ACL
Hardware Counters” on page 875.
Non-ERPS Device Protection and CFM Port MEP fields were added to the web
configuration page for ERPS domains. Refer to “ERPS Ring Configuration” on
page 964.
...Repeat the previous element, for example “member[,member...]”
valueFixed values following arguments are printed in plain font. For example,
--show WWN
|Boolean. Elements are exclusive. Example:
Notes
The following notice statements are used in this manual.
A note provides a tip, guidance, or advice, emphasizes important information, or provides a
reference to related information.
An Attention statement indicates potential damage to hardware or data.
Trademark references
This document may contain references to the trademarks of the following corporations. These
trademarks are the properties of their respective companies and corporations.
These references are made for informational purposes only.
CorporationReferenced Trademarks and Products
--show -mode egress | ingress
Microsoft CorporationInternet Explorer
Mozilla CorporationMozilla Firefox
Related publications
The following Brocade documents supplement the information in this guide and can be located at
For the latest edition of these documents, which contain the most up-to-date information, see
Product Manuals at http://www.brocade.com/ethernetproducts.
To contact Technical Support, go to http://www.brocade.com/services-support/index.page for the
latest e-mail and telephone contact information.
Document feedback
Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and
completeness of this document. However, if you find an error or an omission, or you think that a
topic needs further development, we want to hear from you. Forward your feedback to:
documentation@brocade.com
Provide the title and version number of the document and as much detail as possible about your
comment, including the topic heading and page number and your suggestions for improvement.
This section provides an overview of the switch, and introduces some basic concepts about
network switches. It also describes the basic settings required to access the management
interface, and includes the following chapters:
This switch provides a broad range of features for Layer 2 switching. It includes a management
agent that allows you to configure the features listed in this manual. The default configuration can
be used for most of the features provided by this switch. However, there are many options that you
should configure to maximize the switch’s performance for your particular network environment.
Throttling for broadcast, multicast, unknown unicast storms
Random Early Detection
1K L2 multicast groups
Supported to ensure wire-speed switching while eliminating bad frames
Trees (MSTP)
voice VLANs, and QinQ tunnel
Differentiated Services Code Point (DSCP)
Used to discover basic information about neighboring devices
Connectivity monitoring using continuity check messages, fault verification through
loop back messages, and fault isolation by examining end-to-end connections
(IEEE 802.1ag)
(G.8032)
Description of Software Features
The switch provides a wide range of advanced performance enhancing features. Flow control
eliminates the loss of packets due to bottlenecks caused by port saturation. Broadcast storm
suppression prevents broadcast traffic storms from engulfing the network. Untagged (port-based),
tagged, and protocol-based VLANs, plus support for automatic GVRP VLAN registration provide
traffic security and efficient use of network bandwidth. CoS priority queueing ensures the minimum
delay for moving real-time multimedia data across the network. While multicast filtering provides
support for real-time network applications.
Some of the management features are briefly described below.
You can save the current configuration settings to a file on the management station (using the web
interface) or an FTP/SFTP/TFTP server (using the web or console interface), and later download
this file to restore the switch configuration settings.
53-1002581-01
Description of Software Features
AuthenticationThis switch authenticates management access via the console port, Telnet, or a web browser. User
names and passwords can be configured locally or can be verified via a remote authentication
server (i.e., RADIUS or TACACS+). Port-based authentication is also supported via the IEEE 802.1X
protocol. This protocol uses Extensible Authentication Protocol over LANs (EAPOL) to request user
credentials from the 802.1X client, and then uses the EAP between the switch and the
authentication server to verify the client’s right to access the network via an authentication server
(i.e., RADIUS or TACACS+ server).
Other authentication options include HTTPS for secure management access via the web, SSH for
secure management access over a Telnet-equivalent connection, SNMP Version 3, IP address
filtering for SNMP/Telnet/web management access. MAC address filtering and IP source guard also
provide authenticated port access. While DHCP snooping is provided to prevent malicious attacks
from insecure ports.
1
Access Control
Lists
Port
Configuration
Rate LimitingThis feature controls the maximum rate for traffic transmitted or received on an interface. Rate
Port MirroringThe switch can unobtrusively mirror traffic from any port to a monitor port. You can then attach a
Port TrunkingPorts can be combined into an aggregate connection. Trunks can be manually set up or
ACLs provide packet filtering for IP frames (based on address, protocol, TCP/UDP port number or
TCP control code) or any frames (based on MAC address or Ethernet type). ACLs can by used to
improve performance by blocking unnecessary network traffic or to implement security controls by
restricting access to specific network resources or protocols.
You can manually configure the speed, duplex mode, and flow control used on specific ports, or use
auto-negotiation to detect the connection settings used by the attached device. Use full-duplex
mode on ports whenever possible to double the throughput of switch connections. Flow control
should also be enabled to control network traffic during periods of congestion and prevent the loss
of packets when port buffer thresholds are exceeded. The switch supports flow control based on
the IEEE 802.3x standard (now incorporated in IEEE 802.3-2002).
limiting is configured on interfaces at the edge of a network to limit traffic into or out of the
network. Packets that exceed the acceptable amount of traffic are dropped.
protocol analyzer or RMON probe to this port to perform traffic analysis and verify connection
integrity.
dynamically configured using Link Aggregation Control Protocol (LACP – IEEE 802.3-2005). The
additional ports dramatically increase the throughput across any connection, and provide
redundancy by taking over the load if a port in the trunk should fail. The switch supports up to 12
trunks.
Storm ControlBroadcast, multicast and unknown unicast storm suppression prevents traffic from overwhelming
the network.When enabled on a port, the level of broadcast traffic passing through the port is
restricted. If broadcast traffic rises above a pre-defined threshold, it will be throttled until the level
falls back beneath the threshold.
MAC AddressesA static address can be assigned to a specific interface on this switch. Static addresses are bound
to the assigned interface and will not be moved. When a static address is seen on another
interface, the address will be ignored and will not be written to the address table. Static addresses
can be used to provide network security by restricting access for a known host to a specific port.
Access to insecure ports can be controlled using DHCP Snooping which filters ingress traffic based
on static IP addresses and addresses stored in the DHCP Snooping table. Traffic can also be
restricted to specific source IP addresses or source IP/MAC address pairs based on static entries
or entries stored in the DHCP Snooping table.
The switch supports IEEE 802.1D transparent bridging. The address table facilitates data switching
by learning addresses, and then filtering or forwarding traffic based on this information.
The switch copies each frame into its memory before forwarding them to another port. This ensures
that all frames are a standard Ethernet size and have been verified for accuracy with the cyclic
redundancy check (CRC). This prevents bad frames from entering the network and wasting
bandwidth.
To avoid dropping frames on congested ports, the switch provides 4 Mbits for frame buffering. This
buffer can queue packets awaiting transmission on congested networks.
The switch supports these spanning tree protocols:
• Spanning Tree Protocol (STP, IEEE 802.1D) – This protocol provides loop detection. When there
are multiple physical paths between segments, this protocol will choose a single path and
disable all others to ensure that only one route exists between any two stations on the network.
This prevents the creation of network loops. However, if the chosen path should fail for any
reason, an alternate path will be activated to maintain the connection.
• Rapid Spanning Tree Protocol (RSTP, IEEE 802.1w) – This protocol reduces the convergence
time for network topology changes to about 3 to 5 seconds, compared to 30 seconds or more
for the older IEEE 802.1D STP standard. It is intended as a complete replacement for STP, but
can still interoperate with switches running the older standard by automatically reconfiguring
ports to STP-compliant mode if they detect STP protocol messages from attached devices.
• Multiple Spanning Tree Protocol (MSTP, IEEE 802.1s) – This protocol is a direct extension of
RSTP. It can provide an independent spanning tree for different VLANs. It simplifies network
management, provides for even faster convergence than RSTP by limiting the size of each
region, and prevents VLAN members from being segmented from the rest of the group (as
sometimes occurs with IEEE 802.1D STP).
Connectivity
Fault
Management
Virtual LANsThe switch supports up to 4093 VLANs. A Virtual LAN is a collection of network nodes that share
The switch provides connectivity fault monitoring for end-to-end connections within a designated
service area by using continuity check messages which can detect faults in maintenance points,
fault verification through loop back messages, and fault isolation with link trace messages.
the same collision domain regardless of their physical location or connection point in the network.
The switch supports tagged VLANs based on the IEEE 802.1Q standard. Members of VLAN groups
can be dynamically learned via GVRP, or ports can be manually assigned to a specific set of VLANs.
This allows the switch to restrict traffic to the VLAN groups to which a user has been assigned. By
segmenting your network into VLANs, you can:
• Eliminate broadcast storms which severely degrade performance in a flat network.
• Simplify network management for node changes/moves by remotely configuring VLAN
membership for any port, rather than having to manually change the network connection.
• Provide data security by restricting all traffic to the originating VLAN, except where a
connection is explicitly defined via the switch's routing service.
• Use private VLANs to restrict traffic to pass only between data ports and the uplink ports,
thereby isolating adjacent ports within the same VLAN, and allowing you to limit the total
number of VLANs that need to be configured.
• Use protocol VLANs to restrict traffic to specified interfaces based on protocol type.
1
IEEE 802.1Q
Tunneling (QinQ)
Traffic
Prioritization
Quality of
Service
This feature is designed for service providers carrying traffic for multiple customers across their
networks. QinQ tunneling is used to maintain customer-specific VLAN and Layer 2 protocol
configurations even when different customers use the same internal VLAN IDs. This is
accomplished by inserting Service Provider VLAN (SPVLAN) tags into the customer’s frames when
they enter the service provider’s network, and then stripping the tags when the frames leave the
network.
This switch prioritizes each packet based on the required level of service, using eight priority
queues with strict priority, Weighted Round Robin (WRR), or a combination of strict and weighted
queuing. It uses IEEE 802.1p and 802.1Q tags to prioritize incoming traffic based on input from the
end-station application. These functions can
delay-sensitive data and best-effort data.
This switch also supports several common methods of prioritizing layer 3/4 traffic to meet
application requirements. Traffic can be prioritized based on the priority bits in the IP frame’s Type
of Service (ToS) octet using DSCP or IP Precedence. When these services are enabled, the priorities
are mapped to a Class of Service value by the switch, and the traffic then sent to the corresponding
output queue.
Differentiated Services (DiffServ) provides policy-based management mechanisms used for
prioritizing network resources to meet the requirements of specific traffic types on a per-hop basis.
Each packet is classified upon entry into the network based on access lists, IP Precedence or DSCP
values, or VLAN lists. Using access lists allows you select traffic based on Layer 2, Layer 3, or Layer
4 information contained in each packet. Based on network policies, different kinds of traffic can be
marked for different kinds of forwarding.
Specific multicast traffic can be assigned to its own VLAN to ensure that it does not interfere with
normal network traffic and to guarantee real-time delivery by setting the required priority level for
the designated VLAN. The switch uses IGMP Snooping and Query to manage multicast group
registration. It also supports Multicast VLAN Registration (MVR) which allows common multicast
traffic, such as television channels, to be transmitted across a single network-wide multicast VLAN
shared by hosts residing in other standard or private VLAN groups, while preserving security and
data isolation for normal traffic.
LLDP is used to discover basic information about neighboring devices within the local broadcast
domain. LLDP is a Layer 2 protocol that advertises information about the sending device and
collects information gathered from neighboring network nodes it discovers.
Advertised information is represented in Type Length Value (TLV) format according to the IEEE
802.1ab standard, and can include details such as device identification, capabilities and
configuration settings. Media Endpoint Discovery (LLDP-MED) is an extension of LLDP intended for
managing endpoint devices such as Voice over IP phones and network switches. The LLDP-MED
TLVs advertise information such as network policy, power, inventory, and device location details.
The LLDP and LLDP-MED information can be used by SNMP applications to simplify
troubleshooting, enhance network management, and maintain an accurate network topology.
System Defaults
1
Ethernet Ring
Protection
Switching
ERPS can be used to increase the availability and robustness of Ethernet rings, such as those used
in Metropolitan Area Networks (MAN). ERPS provides Layer 2 loop avoidance and fast
reconvergence in Layer 2 ring topologies, supporting up to 255 nodes in the ring structure. It can
also function with IEEE 802.1ag to support link monitoring when non-participating devices exist
within the Ethernet ring.
IP RoutingThe switch provides Layer 3 IP routing. To maintain a high rate of throughput, the switch forwards
all traffic passing within the same segment, and routes only traffic that passes between different
subnetworks. The wire-speed routing provided by this switch lets you easily link network segments
or VLANs together without having to deal with the bottlenecks or configuration hassles normally
associated with conventional routers.
Static Routing – Traffic is automatically routed between any IP interfaces configured on the switch.
Routing to statically configured hosts or subnet addresses is provided based on next-hop entries
specified in the static routing table.
System Defaults
The switch’s system defaults are provided in the configuration file “Factory_Default_Config.cfg.” To
reset the switch defaults, this file should be set as the startup configuration file.
The following table lists some of the basic system defaults.
The switch includes a built-in network management agent. The agent offers a variety of
management options, including SNMP, RMON and a web-based interface. A PC may also be
connected directly to the switch for configuration and monitoring via a command line interface
(CLI).
Chapter
2Initial Switch Configuration
An IPv 4 address for this switch is obtained via DHCP by default. To change this add ress, see “Setting
an IP Address” on page 14.
Configuration Options
The switch’s HTTP web agent allows you to configure switch parameters, monitor port connections,
and display statistics using a standard web browser such as Internet Explorer 6.x or above, and
Mozilla Firefox 3.6.2/4/5. The switch’s web management interface can be accessed from any
computer attached to the network.
The CLI program can be accessed by a direct connection to the RS-232 serial console port on the
switch, or remotely by a Telnet connection over the network.
The switch’s management agent also supports SNMP (Simple Network Management Protocol). This
SNMP agent permits the switch to be managed from any system in the network using network
management software.
The switch’s web interface, console interface, and SNMP agent allow you to perform the following
management functions:
• Configure the bandwidth of any port by limiting input or output rates
• Control port access through IEEE 802.1X security or static address filtering
• Filter packets using Access Control Lists (ACLs)
• Configure up to 4093 IEEE 802.1Q VLANs
• Enable GVRP automatic VLAN registration
• Configure IGMP multicast filtering
• Upload and download system firmware or configuration files via HTTP (using the web interface)
or FTP/TFTP (using the command line or web interface)
• Configure Spanning Tree parameters
• Configure Class of Service (CoS) priority queuing
• Configure static or LACP trunks (up to 6)
• Enable port mirroring
• Set storm control on any port for excessive broadcast, multicast, or unknown unicast traffic
• Display system information and statistics
Required Connections
The switch provides an RS-232 serial port that enables a connection to a PC or terminal for
monitoring and configuring the switch. A null-modem console cable is provided with the switch.
Attach a VT100-compatible terminal, or a PC running a terminal emulation program to the switch.
You can use the console cable provided with this package, or use a null-modem cable that
complies with the wiring assignments shown in the Installation Guide.
To connect a terminal to the console port, complete the following steps:
1. Connect the console cable to the serial port on a terminal, or a PC running terminal emulation
software, and tighten the captive retaining screws on the DB-9 connector.
2. Connect the other end of the cable to the RS-232 serial port on the switch.
3. Make sure the terminal emulation software is set as follows:
• Select the appropriate serial port (COM port 1 or COM port 2).
• Set the baud rate to 9600 bps.
• Set the data format to 8 data bits, 1 stop bit, and no parity.
• Set flow control to none.
• Set the emulation mode to VT100.
• When using HyperTerminal, select Terminal keys, not Windows keys.
Once you have set up the terminal correctly, the console login screen will be displayed.
For a description of how to use the CLI, see “Using the Command Line Interface” on page 27. For a
list of all the CLI commands and detailed information on using the CLI, refer to “CLI Command
Prior to accessing the switch’s onboard agent via a network connection, you must first configure it
with a valid IP address, subnet mask, and default gateway using a console connection, or DHCP
protocol.
An IPv4 address for this switch is obtained via DHCP by default. To manually configure this address
or enable dynamic address assignment via DHCP, see “Setting an IP Address” on page 14.
This switch supports four Telnet sessions or four SSH sessions.
After configuring the switch’s IP parameters, you can access the onboard configuration program
from anywhere within the attached network. The onboard configuration program can be accessed
using Telnet from any computer attached to the network. The switch can also be managed by any
computer using a web browser (Internet Explorer 6.x or above, or Mozilla Firefox 3.6.2/4/5), or
from a network computer using SNMP network management software.
The onboard program only provides access to basic configuration functions. To access the full
range of SNMP management functions, you must use SNMP-based network management
software.
The switch also includes a Craft port on the front panel which provides a secure management
connection that is isolated from all other ports on the switch. This interface is not configured with
an IP address by default, but may be manually configured with an IPv4 or IPv6 address as described
in the following sections. The Craft port can only be configured through the command line interface,
and is specified with the name “craft” in the commands used to configure its IP address.
Basic Configuration
Console Connection
The CLI program provides two different command levels — normal access level (Normal Exec) and
privileged access level (Privileged Exec). The commands available at the Normal Exec level are a
limited subset of those available at the Privileged Exec level and allow you to only display
information and use basic utilities. To fully configure the switch parameters, you must access the
CLI at the Privileged Exec level.
Access to both CLI levels are controlled by user names and passwords. The switch has a default
user name and password for each level. To log into the CLI at the Privileged Exec level using the
default user name and password, perform these steps:
1. To initiate your console connection, press <Enter>. The “User Access Verification” procedure
starts.
2. At the User Name prompt, enter “admin.”
3. At the Password prompt, also enter “admin.” (The password characters are not displayed on
the console screen.)
4. The session is opened and the CLI displays the “Console#” prompt indicating you have access
at the Privileged Exec level.
If this is your first time to log into the CLI program, you should define new passwords for both
default user names using the “username” command, record them and put them in a safe place.
Passwords can consist of up to 32 alphanumeric characters and are case sensitive. To prevent
unauthorized access to the switch, set the passwords as follows:
1. Open the console interface with the default user name and password “admin” to access the
Privileged Exec level.
2. Type “configure” and press <Enter>.
3. Type “username guest password 0 password,” for the Normal Exec level, where password is
your new password. Press <Enter>.
4. Type “username admin password 0 password,” for the Privileged Exec level, where password is
your new password. Press <Enter>.
Username: admin
Password:
CLI session with the BR6910 is opened.
To end the CLI session, enter [Exit].
You must establish IP address information for the switch to obtain management access through
the network. This can be done in either of the following ways:
• Manual — You have to input the information, including IP address and subnet mask. If your
management station is not in the same IP subnet as the switch, you will also need to specify
the default gateway router.
• Dynamic — The switch can send IPv4 configuration requests to BOOTP or DHCP address
allocation servers on the network, or can automatically generate a unique IPv6 host address
based on the local subnet address prefix received in router advertisement messages. An IPv6
link local address for use in a local network can also be dynamically generated as described in
“Obtaining an IPv6 Address” on page 18.
The current software does not support DHCP for IPv6, so an IPv6 global unicast address for use in
a network containing more than one subnet can only be manually configured as described in
“Assigning an IPv6 Address” on page 15.
Manual Configuration
You can manually assign an IP address to the switch. You may also need to specify a default
gateway that resides between this device and management stations that exist on another network
segment. Valid IPv4 addresses consist of four decimal numbers, 0 to 255, separated by periods.
Anything outside this format will not be accepted by the CLI program.
The IPv4 address for this switch is obtained via DHCP by default.
Assigning an IPv4 Address
Before you can assign an IP address to the switch, you must obtain the following information from
your network administrator:
2
• IP address for the switch
• Network mask for this network
• Default gateway for the network
To assign an IPv4 address to the switch, complete the following steps
1. From the Global Configuration mode prompt, type “interface vlan 1” to access the
interface-configuration mode. Press <Enter>.
2. Type “ip address ip-address netmask” or “ip address ip-address/prefix-length,” where
“ip-address” is the switch IP address, “netmask” is the network mask for the network, and
“prefix-length” indicates how many contiguous bits (from the left) of the address comprise the
network portion of the address. Press <Enter>.
3. Type “exit” to return to the global configuration mode prompt. Press <Enter>.
4. To set the IP address of the default gateway for the network to which the switch belongs, type
“ip default-gateway gateway,” where “gateway” is the IP address of the default gateway. Press
<Enter>.
This section describes how to configure a “link local” address for connectivity within the local
subnet only, and also how to configure a “global unicast” address, including a network prefix for
use on a multi-segment network and the host portion of the address.
An IPv6 prefix or address must be formatted according to RFC 2373 “IPv6 Addressing
Architecture,” using 8 colon-separated 16-bit hexadecimal values. One double colon may be used
to indicate the appropriate number of zeros required to fill the undefined fields. For detailed
information on the other ways to assign IPv6 addresses, see “Setting the Switch’s IP Address (IP
Version 6)” on page 1016.
Link Local Address — All link-local addresses must be configured with a prefix in the range of
FE80~FEBF. Remember that this address type makes the switch accessible over IPv6 for all
devices attached to the same local subnet only. Also, if the switch detects that the address you
configured conflicts with that in use by another device on the subnet, it will stop using the address
in question, and automatically generate a link local address that does not conflict with any other
devices on the local subnet.
To configure an IPv6 link local address for the switch, complete the following steps:
1. From the Global Configuration mode prompt, type “interface vlan 1” to access the
interface-configuration mode. Press <Enter>.
2. Type “ipv6 address” followed by up to 8 colon-separated 16-bit hexadecimal values for the
ipv6-address similar to that shown in the example, followed by the “link-local” command
parameter. Then press <Enter>.
Console(config)#interface vlan 1
Console(config-if)#ipv6 address FE80::260:3EFF:FE11:6700 link-local
Console(config-if)#ipv6 enable
Console(config-if)#end
Console#show ipv6 interface
VLAN 1 is up
IPv6 is enabled.
Link-local address:
FE80::260:3EFF:FE11:6700/64
Global unicast address(es):
(None)
Joined group address(es):
FF02::1:FF11:6700
FF02::1
IPv6 link MTU is 1500 bytes
ND DAD is enabled, number of DAD attempts: 3.
ND retransmit interval is 1000 milliseconds
ND advertised retransmit interval is 0 milliseconds
ND reachable time is 30000 milliseconds
ND advertised reachable time is 0 milliseconds
Console#
Address for Multi-segment Network — Before you can assign an IPv6 address to the switch that will
be used to connect to a multi-segment network, you must obtain the following information from
your network administrator:
• Prefix for this network
• IP address for the switch
• Default gateway for the network
For networks that encompass several different subnets, you must define the full address, including
a network prefix and the host address for the switch. You can specify either the full IPv6 address, or
the IPv6 address and prefix length. The prefix length for an IPv6 network is the number of bits (from
the left) of the prefix that form the network address, and is expressed as a decimal number. For
example, all IPv6 addresses that start with the first byte of 73 (hexadecimal) could be expressed as
73:0:0:0:0:0:0:0/8 or 73::/8.
To generate an IPv6 global unicast address for the switch, complete the following steps:
1. From the global configuration mode prompt, type “interface vlan 1” to access the
interface-configuration mode. Press <Enter>.
2. From the interface prompt, type “ipv6 address ipv6-address” or “ipv6 address
ipv6-address/prefix-length,” where “prefix-length” indicates the address bits used to form the
network portion of the address. (The network address starts from the left of the prefix and
should encompass some of the ipv6-address bits.) The remaining bits are assigned to the host
interface. Press <Enter>.
3. Type “exit” to return to the global configuration mode prompt. Press <Enter>.
4. To set the IP address of the IPv6 default gateway for the network to which the switch belongs,
type “ipv6 default-gateway gateway,” where “gateway” is the IPv6 address of the default
gateway. Press <Enter>.
Console(config)#interface vlan 1
Console(config-if)#ipv6 address 2001:DB8:2222:7272::/64
Console(config-if)#exit
Console(config)#ipv6 default-gateway 2001:DB8:2222:7272::254
Console(config)end
Console#show ipv6 interface
VLAN 1 is up
IPv6 is enabled.
Link-local address:
FE80::260:3EFF:FE11:6700/64
Global unicast address(es):
2001:DB8:2222:7272::/64, subnet is 2001:DB8:2222:7272::/64
Joined group address(es):
FF02::1:FF00:0
FF02::1:FF11:6700
FF02::1
IPv6 link MTU is 1500 bytes
ND DAD is enabled, number of DAD attempts: 3.
ND retransmit interval is 1000 milliseconds
ND advertised retransmit interval is 0 milliseconds
ND reachable time is 30000 milliseconds
ND advertised reachable time is 0 milliseconds
If you select the “bootp” or “dhcp” option, the system will immediately start broadcasting service
requests. IP will be enabled but will not function until a BOOTP or DHCP reply has been received.
Requests are broadcast every few minutes using exponential backoff until IP configuration
information is obtained from a BOOTP or DHCP server. BOOTP and DHCP values can include the IP
address, subnet mask, and default gateway. If the DHCP/BOOTP server is slow to respond, you may
need to use the “ip dhcp restart client” command to re-start broadcasting service requests.
Note that the “ip dhcp restart client” command can also be used to start broadcasting service
requests for all VLANs configured to obtain address assignments through BOOTP or DHCP. It may
be necessary to use this command when DHCP is configured on a VLAN, and the member ports
which were previously shut down are now enabled.
If the “bootp” or “dhcp” option is saved to the startup-config file (step 6), then the switch will start
broadcasting service requests as soon as it is powered on.
To automatically configure the switch by communicating with BOOTP or DHCP address allocation
servers on the network, complete the following steps:
1. From the Global Configuration mode prompt, type “interface vlan 1” to access the
interface-configuration mode. Press <Enter>.
2. At the interface-configuration mode prompt, use one of the following commands:
• To obtain IP settings via DHCP, type “ip address dhcp” and press <Enter>.
• To obtain IP settings via BOOTP, type “ip address bootp” and press <Enter>.
3. Type “end” to return to the Privileged Exec mode. Press <Enter>.
4. Wait a few minutes, and then check the IP configuration settings by typing the “show ip
interface” command. Press <Enter>.
5. Then save your configuration changes by typing “copy running-config startup-config.” Enter the
startup file name and press <Enter>.
Console(config)#interface vlan 1
Console(config-if)#ip address dhcp
Console(config-if)#end
Console#show ip interface
VLAN 1 is Administrative Up - Link Up
Address is 00-E0-0C-00-00-FB
Index: 1001, MTU: 1500
Address Mode is DHCP
IP Address: 192.168.0.2 Mask: 255.255.255.0
Console#copy running-config startup-config
Startup configuration file name []: startup
\Write to FLASH Programming.
\Write to FLASH finish.
Success.
Obtaining an IPv6 Address
Link Local Address — There are several ways to configure IPv6 addresses. The simplest method is
to automatically generate a “link local” address (identified by an address prefix of FE80). This
address type makes the switch accessible over IPv6 for all devices attached to the same local
subnet.
To generate an IPv6 link local address for the switch, complete the following steps:
1. From the Global Configuration mode prompt, type “interface vlan 1” to access the
interface-configuration mode. Press <Enter>.
2. Type “ipv6 enable” and press <Enter>.
Console(config)#interface vlan 1
Console(config-if)#ipv6 enable
Console(config-if)#end
Console#show ipv6 interface
VLAN 1 is up
IPv6 is enabled.
Link-local address:
FE80::260:3EFF:FE11:6700/64
Global unicast address(es):
2001:DB8:2222:7272::/64, subnet is 2001:DB8:2222:7272::/64
Joined group address(es):
FF02::1:FF00:0
FF02::1:FF11:6700
FF02::1
IPv6 link MTU is 1500 bytes
ND DAD is enabled, number of DAD attempts: 3.
ND retransmit interval is 1000 milliseconds
ND advertised retransmit interval is 0 milliseconds
ND reachable time is 30000 milliseconds
ND advertised reachable time is 0 milliseconds
Console#
Address for Multi-segment Network — To generate an IPv6 address that can be used in a network
containing more than one subnet, the switch can be configured to automatically generate a unique
host address based on the local subnet address prefix received in router advertisement messages.
(DHCP for IPv6 will also be supported in future software releases.)
To dynamically generate an IPv6 host address for the switch, complete the following steps:
1. From the Global Configuration mode prompt, type “interface vlan 1” to access the
interface-configuration mode. Press <Enter>.
2. From the interface prompt, type “ipv6 address autoconfig” and press <Enter>.
3. Type “ipv6 enable” and press <Enter> to enable IPv6 on an interface that has not been
configured with an explicit IPv6 address.
Console(config)#interface vlan 1
Console(config-if)#ipv6 address autoconfig
Console(config-if)#ipv6 enable
Console(config-if)#end
Console#show ipv6 interface
VLAN 1 is up
IPv6 is enabled.
Link-local address:
FE80::260:3EFF:FE11:6700/64
Global unicast address(es):
2001:DB8:2222:7272::/64, subnet is 2001:DB8:2222:7272::/64
Joined group address(es):
FF02::1:FF00:0
FF02::1:FF11:6700
FF02::1
IPv6 link MTU is 1500 bytes
ND DAD is enabled, number of DAD attempts: 3.
ND retransmit interval is 1000 milliseconds
ND advertised retransmit interval is 0 milliseconds
ND reachable time is 30000 milliseconds
ND advertised reachable time is 0 milliseconds
Console#
Downloading Configuration File Referenced by DHCP Server
Information passed on to the switch from a DHCP server may also include a configuration file to be
downloaded and the TFTP servers where that file can be accessed. If the Factory Default
Configuration file is used to provision the switch at startup, in addition to requesting IP
configuration settings from the DHCP server, it will also ask for the name of a bootup configuration
file and TFTP servers where that file is stored.
If the switch receives information that allows it to download the remote bootup file, it will save this
file to a local buffer, and then restart the provision process.
Note the following DHCP client behavior:
• The bootup configuration file received from a TFTP server is stored on the switch with the
original file name. If this file name already exists in the switch, the file is overwritten.
• If the name of the bootup configuration file is the same as the Factory Default Configuration
file, the download procedure will be terminated, and the switch will not send any further DHCP
client requests.
• If the switch fails to download the bootup configuration file based on information passed by the
DHCP server, it will not send any further DHCP client requests.
• If the switch does not receive a DHCP response prior to completing the bootup process, it will
continue to send a DHCP client request once a minute. These requests will only be terminated
if the switch’s address is manually configured, but will resume if the address mode is set back
to DHCP.
To successfully transmit a bootup configuration file to the switch the DHCP daemon (using a Linux
based system for this example) must be configured with the following information:
• Options 60, 66 and 67 statements can be added to the daemon’s configuration file.
TABLE 3Options 60, 66 and 67 Statements
Statement
Option
KeywordParameter
60vendor-class-identifiera string indicating the vendor class identifier
66tftp-server-namea string indicating the tftp server name
67bootfile-namea string indicating the bootfile name
• By default, DHCP option 66/67 parameters are not carried in a DHCP server reply. To ask for a
DHCP reply with option 66/67 information, the DHCP client request sent by this switch
includes a “parameter request list” asking for this information. Besides, the client request also
includes a “vendor class identifier” that allows the DHCP server to identify the device, and
select the appropriate configuration file for download. This information is included in Option 55
and 124.
TABLE 4Options 55 and 124 Statements
Option
KeywordParameter
55dhcp-parameter-request-lista list of parameters, separated by ','
124vendor-class-identifiera string indicating the vendor class identifier
Statement
The following configuration examples are provided for a Linux-based DHCP daemon (dhcpd.conf
file). The server will reply with Options 66/67 encapsulated in Option 43. Note that in the “Vendor
class one” section, if the DHCP request packet's vendor class identifier matches that specified in
this file, the server will send Option 43 encapsulating Option 66 and 67 in the DHCP reply packet.
In the “Vendor class two” section, the server will always send Option 66 and 67 to tell switch to
download the “test2” configuration file from server 192.168.255.101.
class "Option66,67_1" { #DHCP Option 60 Vendor class one
match if option vendor-class-identifier = "es020000.cfg";
#option 43
option vendor-class-information code 43 = encapsulate dynamicProvision;
#option 66 encapsulated in option 43
option vendor-class-information.tftp-server-name "192.168.255.100";
#option 67 encapsulated in option 43
option vendor-class-information.bootfile-name "test1"
}
class "Option66,67_2" {#DHCP Option 60 Vendor class two
match if option vendor-class-identifier = "es020000.cfg";
option tftp-server-name "192.168.255.101";
option bootfile-name "test2";
}
2
Use “es020000.cfg” for the vendor-class-identifier in the dhcpd.conf file.
Enabling SNMP Management Access
The switch can be configured to accept management commands from Simple Network
Management Protocol (SNMP) applications. You can configure the switch to respond to SNMP
requests or generate SNMP traps.
When SNMP management stations send requests to the switch (either to return information or to
set a parameter), the switch provides the requested data or sets the specified parameter. The
switch can also be configured to send information to SNMP managers (without being requested by
the managers) through trap messages, which inform the manager that certain events have
occurred.
The switch includes an SNMP agent that supports SNMP version 1, 2c, and 3 clients. To provide
management access for version 1 or 2c clients, you must specify a community string. The switch
provides a default MIB View (i.e., an SNMPv3 construct) for the default “public” community string
that provides read access to the entire MIB tree, and a default view for the “private” community
string that provides read/write access to the entire MIB tree. However, you may assign new views to
version 1 or 2c community strings that suit your specific security requirements (see “Setting
SNMPv3 Views” on page 934).
Community Strings (for SNMP version 1 and 2c clients)
Community strings are used to control management access to SNMP version 1 and 2c stations, as
well as to authorize SNMP stations to receive trap messages from the switch. You therefore need to
assign community strings to specified users, and set the access level.
The default strings are:
• public - with read-only access. Authorized management stations are only able to retrieve MIB
• private - with read/write access. Authorized management stations are able to both retrieve and
modify MIB objects.
To prevent unauthorized access to the switch from SNMP version 1 or 2c clients, it is
recommended that you change the default community strings.
To configure a community string, complete the following steps:
1. From the Privileged Exec level global configuration mode prompt, type “snmp-server
community stringmode,” where “string” is the community access string and “mode” is rw
(read/write) or ro (read only). Press <Enter>. (Note that the default mode is read only.)
2. To remove an existing string, simply type “no snmp-server community string,” where “string” is
the community access string to remove. Press <Enter>.
Console(config)#snmp-server community admin rw
Console(config)#snmp-server community private
Console(config)#
If you do not intend to support access to SNMP version 1 and 2c clients, we recommend that you
delete both of the default community strings. If there are no community strings, then SNMP
management access from SNMP v1 and v2c clients is disabled.
Trap Receivers
You can also specify SNMP stations that are to receive traps from the switch. To configure a trap
receiver, use the “snmp-server host” command. From the Privileged Exec level global configuration
mode prompt, type:
“snmp-server host host-address community-string
[version {1 | 2c | 3 {auth | noauth | priv}}]”
where “host-address” is the IP address for the trap receiver, “community-string” specifies access
rights for a version 1/2c host, or is the user name of a version 3 host, “version” indicates the SNMP
client version, and “auth | noauth | priv” means that authentication, no authentication, or
authentication and privacy is used for v3 clients. Then press <Enter>. For a more detailed
description of these parameters, see “snmp-server host” on page 113. The following example
creates a trap host for each type of SNMP client.
Console(config)#snmp-server host 10.1.19.23 batman
Console(config)#snmp-server host 10.1.19.98 robin version 2c
Console(config)#snmp-server host 10.1.19.34 barbie version 3 auth
Console(config)#
Configuring Access for SNMP Version 3 Clients
To configure management access for SNMPv3 clients, you need to first create a view that defines
the portions of MIB that the client can read or write, assign the view to a group, and then assign the
user to a group. The following example creates one view called “mib-2” that includes the entire
MIB-2 tree branch, and then another view that includes the IEEE 802.1d bridge MIB. It assigns
these respective read and read/write views to a group call “r&d” and specifies group
authentication via MD5 or SHA. In the last step, it assigns a v3 user to this group, indicating that
MD5 will be used for authentication, provides the password “greenpeace” for authentication, and
the password “einstien” for encryption.
Console(config)#snmp-server view mib-2 1.3.6.1.2.1 included
Console(config)#snmp-server view 802.1d 1.3.6.1.2.1.17 included
Console(config)#snmp-server group r&d v3 auth read mib-2 write 802.1d
Console(config)#snmp-server user steve group r&d v3 auth md5 greenpeace priv des56
einstien
Console(config)#
For a more detailed explanation on how to configure the switch for access from SNMP v3 clients,
refer to “Simple Network Management Protocol” on page 929, or refer to the specific CLI
commands for SNMP starting on page 107.
Managing System Files
The switch’s flash memory supports three types of system files that can be managed by the CLI
program, web interface, or SNMP. The switch’s file system allows files to be uploaded and
downloaded, copied, deleted, and set as a start-up file.
The types of files are:
• Configuration — This file type stores system configuration information and is created when
configuration settings are saved. Saved configuration files can be selected as a system
start-up file or can be uploaded via FTP/TFTP to a server for backup. The file named
“Factory_Default_Config.cfg” contains all the system default settings and cannot be deleted
from the system. If the system is booted with the factory default settings, the switch will also
create a file named “startup1.cfg” that contains system settings for switch initialization,
including information about the unit identifier, and MAC address for the switch. The
configuration settings from the factory defaults configuration file are copied to this file, which
is then used to boot the switch. See “Saving or Restoring Configuration Settings” on page 23
for more information.
• Operation Code — System software that is executed after boot-up, also known as run-time
code. This code runs the switch operations and provides the CLI and web management
interfaces. See “Managing System Files” on page 653 for more information.
• Diagnostic Code — Software that is run during system boot-up, also known as POST (Power On
Self-Test).
Managing System Files
2
Due to the size limit of the flash memory, the switch supports only two operation code files.
However, you can have as many diagnostic code files and configuration files as available flash
memory space allows. The switch has a total of 32 Mbytes of flash memory for system files.
In the system flash memory, one file of each type must be set as the start-up file. During a system
boot, the diagnostic and operation code files set as the start-up file are run, and then the start-up
configuration file is loaded.
Note that configuration files should be downloaded using a file name that reflects the contents or
usage of the file settings. If you download directly to the running-config, the system will reboot, and
the settings will have to be copied from the running-config to a permanent file.
Saving or Restoring Configuration Settings
Configuration commands only modify the running configuration file and are not saved when the
switch is rebooted. To save all your configuration changes in nonvolatile storage, you must copy the
running configuration file to the start-up configuration file using the “copy” command.
New startup configuration files must have a name specified. File names on the switch are
case-sensitive, can be from 1 to 31 characters, must not contain slashes (\ or /), and the leading
letter of the file name must not be a period (.). (Valid characters: A-Z, a-z, 0-9, “.”, “-”, “_”)
There can be more than one user-defined configuration file saved in the switch’s flash memory, but
only one is designated as the “startup” file that is loaded when the switch boots. The copy
running-config startup-config command always sets the new file as the startup file. To select a
previously saved configuration file, use the boot system config:<filename> command.
The maximum number of saved configuration files depends on available flash memory. The
amount of available flash memory can be checked by using the dir command.
To save the current configuration settings, enter the following command:
1. From the Privileged Exec mode prompt, type “copy running-config startup-config” and press
<Enter>.
2. Enter the name of the start-up file. Press <Enter>.
Console#copy running-config startup-config
Startup configuration file name []: startup
\Write to FLASH Programming.
\Write to FLASH finish.
Success.
Console#
To restore configuration settings from a backup server, enter the following command:
1. From the Privileged Exec mode prompt, type “copy tftp startup-config” and press <Enter>.
2. Enter the address of the TFTP server. Press <Enter>.
3. Enter the name of the startup file stored on the server. Press <Enter>.
4. Enter the name for the startup file on the switch. Press <Enter>.
Console#copy file startup-config
Console#copy tftp startup-config
TFTP server IP address: 192.168.0.4
Source configuration file name: startup-rd.cfg
Startup configuration file name [startup1.cfg]:
This section provides a detailed description of the Command Line Interface, along with examples
for all of the commands, and includes the following chapters:
When accessing the management interface for the switch over a direct connection to the server’s
console port, or via a Telnet or Secure Shell connection (SSH), the switch can be managed by
entering command keywords and parameters at the prompt. Using the switch's command-line
interface (CLI) is very similar to entering commands on a UNIX system.
Chapter
3Using the Command Line Interface
Console Connection
To access the switch through the console port, perform these steps:
1. At the console prompt, enter the user name and password. (The default user names are
“admin” and “guest” with corresponding passwords of “admin” and “guest.”) When the
administrator user name and password is entered, the CLI displays the “Console#” prompt and
enters privileged access mode (i.e., Privileged Exec). But when the guest user name and
password is entered, the CLI displays the “Console>” prompt and enters normal access mode
(i.e., Normal Exec).
2. Enter the necessary commands to complete your desired tasks.
3. When finished, exit the session with the “quit” or “exit” command.
After connecting to the system through the console port, the login screen displays:
User Access Verification
Username: admin
Password:
CLI session with the BR6910 is opened.
To end the CLI session, enter [Exit].
Console#
Telnet Connection
Telnet operates over the IP transport protocol. In this environment, your management station and
any network device you want to manage over the network must have a valid IP address. Valid IP
addresses consist of four numbers, 0 to 255, separated by periods. Each address consists of a
network portion and host portion. For example, the IP address assigned to this switch, 10.1.0.1,
consists of a network portion (10.1.0) and a host portion (1).
The IP address for this switch is obtained via DHCP by default.
To access the switch through a Telnet session, you must first set the IP address for the Master unit,
and set the default gateway if you are managing the switch from a different IP subnet. For example,
If your corporate network is connected to another network outside your office or to the Internet, you
need to apply for a registered IP address. However, if you are attached to an isolated network, then
you can use any IP address that matches the network segment to which you are attached.
After you configure the switch with an IP address, you can open a Telnet session by performing
these steps:
1. From the remote host, enter the Telnet command and the IP address of the device you want to
access.
2. At the prompt, enter the user name and system password. The CLI will display the “Vty-n#”
prompt for the administrator to show that you are using privileged access mode (i.e., Privileged
Exec), or “Vty-n>” for the guest to show that you are using normal access mode (i.e., Normal
Exec), where n indicates the number of the current Telnet session.
3. Enter the necessary commands to complete your desired tasks.
4. When finished, exit the session with the “quit” or “exit” command.
After entering the Telnet command, the login screen displays:
Username: admin
Password:
CLI session with the BR6910 is opened.
To end the CLI session, enter [Exit].
Vty-0#
You can open up to four sessions to the device via Telnet.
Entering Commands
This section describes how to enter CLI commands.
Keywords and Arguments
A CLI command is a series of keywords and arguments. Keywords identify a command, and
arguments specify configuration parameters. For example, in the command “show interfaces
status ethernet 1/5,” show interfaces and status are keywords, ethernet is an argument that
specifies the interface type, and 1/5 specifies the unit/port.
• To enter a simple command, enter the command keyword.
• To enter multiple commands, enter each command in the required order. For example, to
enable Privileged Exec command mode, and display the startup configuration, enter:
Console>enable
Console#show startup-config
• To enter commands that require parameters, enter the required parameters after the
command keyword. For example, to set a password for the administrator, enter:
Console(config)#username admin password 0 smith
Minimum Abbreviation
The CLI will accept a minimum number of characters that uniquely identify a command. For
example, the command “configure” can be entered as con. If an entry is ambiguous, the system
will prompt for further input.
Command Completion
If you terminate input with a Tab key, the CLI will print the remaining characters of a partial keyword
up to the point of ambiguity. In the “logging history” example, typing log followed by a tab will result
in printing the command up to “logging.”
Getting Help on Commands
You can display a brief description of the help system by entering the help command. You can also
display command syntax by using the “?” character to list keywords or parameters.
Showing Commands
If you enter a “?” at the command prompt, the system will display the first level of keywords or
command groups. You can also display a list of valid keywords for a specific command. For
example, the command “system ?” displays a list of possible system commands:
Console#show ?
access-group Access groups
access-list Access lists
accounting Uses an accounting list with this name
alarm-status Show alarm status
arp Information of ARP cache
authorization Enables EXEC accounting
auto-traffic-control Auto traffic control information
banner Banner info
bridge-ext Bridge extension information
cable-diagnostics Shows the information of cable diagnostics
calendar Date and time information
class-map Displays class maps
dns DNS information
dot1q-tunnel dot1q-tunnel
dot1x 802.1X content
efm Ethernet First Mile feature
erps Displays ERPS configuration
ethernet Specifies the ethernet
garp GARP properties
gvrp GVRP interface information
history Shows history information
hosts Host information
interfaces Shows interface information
ip IP information
ipv6 IPv6 information
l2protocol-tunnel Layer 2 protocol tunneling configuration
lacp LACP statistics
line TTY line information
lldp LLDP
log Log records
logging Logging setting
loop Shows the information of loopback
mac MAC access list
mac-address-table Configuration of the address table
mac-vlan MAC-based VLAN information
management Shows management information
memory Memory utilization
mvr multicast vlan registration
mvr6 IPv6 Multicast VLAN registration
network-access Shows the entries of the secure port.
nlm Show notification log
policy-map Displays policy maps
port Port characteristics
port-channel Port channel information
power-save Shows the power saving information
process Device process
protocol-vlan Protocol-VLAN information
public-key Public key information
qos Quality of Service
queue Priority queue information
radius-server RADIUS server information
reload Shows the reload settings
rmon Remote Monitoring Protocol
rspan Display status of the current RSPAN configuration
running-config Information on the running configuration
sflow Shows the sflow information
snmp Simple Network Management Protocol configuration and
statistics
sntp Simple Network Time Protocol configuration
spanning-tree Spanning-tree configuration
ssh Secure shell server connections
startup-config Startup system configuration
subnet-vlan IP subnet-based VLAN information
system System information
tacacs-server TACACS server information
tech-support Technical information
time-range Time range
traffic-segmentation Traffic segmentation information
upgrade Shows upgrade information
users Information about users logged in
version System hardware and software versions
vlan Shows virtual LAN settings
vlan-translation VLAN translation information
voice Shows the voice VLAN information
web-auth Shows web authentication configuration
Console#show
The command “show interfaces ?” will display the following information:
Console#show interfaces ?
brief Shows brief interface description
counters Interface counters information
history Historical sample of interface counters information
protocol-vlan Protocol-VLAN information
status Shows interface status
subnet-vlan IP subnet-based VLAN information
switchport Shows interface switchport information
transceiver Interface of transceiver information
Console#
Show commands which display more than one page of information (e.g., show running-config)
pause and require you to press the [Space] bar to continue displaying one more page, the [Enter]
key to display one more line, or the [a] key to display the rest of the information without stopping.
You can press any other key to terminate the display.
3
Partial Keyword Lookup
If you terminate a partial keyword with a question mark, alternatives that match the initial letters
are provided. (Remember not to leave a space between the command and question mark.) For
example “s?” shows all the keywords starting with “s.”
Console#show s?
sflow snmp sntp spanning-tree ssh
startup-config subnet-vlan system
Console#show s
Negating the Effect of Commands
For many configuration commands you can enter the prefix keyword “no” to cancel the effect of a
command or reset the configuration to the default value. For example, the logging command will
log system messages to a host server. To disable logging, specify the no logging command. This
guide describes the negation effect for all applicable commands.
Using Command History
The CLI maintains a history of commands that have been entered. You can scroll back through the
history of commands by pressing the up arrow key. Any command displayed in the history list can
be executed again, or first modified and then executed.
Using the show history command displays a longer list of recently executed commands.
The command set is divided into Exec and Configuration classes. Exec commands generally display
information on system status or clear statistical counters. Configuration commands, on the other
hand, modify interface parameters or enable certain switching functions. These classes are further
divided into different modes. Available commands depend on the selected mode. You can always
enter a question mark “?” at the prompt to display a list of the commands available for the current
mode. The command classes and associated modes are displayed in the following table:
TABLE 5General Command Modes
ClassMode
ExecNormal
Privileged
ConfigurationGlobal
*You must be in Privileged Exec mode to access the Global configuration mode.
You must be in Global Configuration mode to access any of the other configuration modes.
*
Access Control List
CFM
Class Map
ERPS
IGMP Profile
Interface
Line
Multiple Spanning Tree
Policy Map
Time Range
VLAN Database
Exec Commands
When you open a new console session on the switch with the user name and password “guest,” the
system enters the Normal Exec command mode (or guest mode), displaying the “Console>”
command prompt. Only a limited number of the commands are available in this mode. You can
access all commands only from the Privileged Exec command mode (or administrator mode). To
access Privilege Exec mode, open a new console session with the user name and password
“admin.” The system will now display the “Console#” command prompt. You can also enter
Privileged Exec mode from within Normal Exec mode, by entering the enable command, followed by
the privileged level password “super.”
To enter Privileged Exec mode, enter the following user names and passwords:
Username: admin
Password: [admin login password]
CLI session with the BR6910 is opened.
To end the CLI session, enter [Exit].
Configuration commands are privileged level commands used to modify switch settings. These
commands modify the running configuration only and are not saved when the switch is rebooted.
To store the running configuration in non-volatile storage, use the copy running-config
startup-config command.
The configuration commands are organized into different modes:
• Global Configuration - These commands modify the system level configuration, and include
commands such as hostname and snmp-server community.
• Access Control List Configuration - These commands are used for packet filtering.
verification through loopback messages, and fault isolation by examining end-to-end
connections between Provider Edge devices or between Customer Edge devices.
• Class Map Configuration - Creates a DiffServ class map for a specified traffic type.
• ERPS Configuration – These commands configure Ethernet Ring Protection Switching for
increased availability of Ethernet rings commonly used in service provider networks.
• IGMP Profile - Sets a profile group and enters IGMP filter profile configuration mode.
• Interface Configuration - These commands modify the port configuration such as speed-duplex
and negotiation.
• Line Configuration - These commands modify the console port and Telnet configuration, and
include command such as parity and databits.
• Multiple Spanning Tree Configuration - These commands configure settings for the selected
multiple spanning tree instance.
• Policy Map Configuration - Creates a DiffServ policy map for multiple interfaces.
• Time Range - Sets a time range for use by other functions, such as Access Control Lists.
• VLAN Configuration - Includes the command to create VLAN groups.
To enter the Global Configuration mode, enter the command configure in Privileged Exec mode.
The system prompt will change to “Console(config)#” which gives you access privilege to all Global
Configuration commands.
To enter the other modes, at the configuration prompt type one of the following commands. Use the
exit or end command to return to the Privileged Exec mode.
For example, you can use the following commands to enter interface configuration mode, and then
return to Privileged Exec mode
Console(config)#interface ethernet 1/5
.
.
.
Console(config-if)#exit
Console(config)#
Command Line Processing
Commands are not case sensitive. You can abbreviate commands and parameters as long as they
contain enough letters to differentiate them from any other currently available commands or
parameters. You can use the Tab key to complete partial commands, or enter a partial command
followed by the “?” character to display a list of possible matches. You can also use the following
editing keystrokes for command-line processing:
TABLE 7Keystroke Commands
KeystrokeFunction
Ctrl-AShifts cursor to start of command line.
Ctrl-BShifts cursor to the lef t one character.
Ctrl-CTerminates the current task and displays the command prompt.
Ctrl-EShifts cursor to end of command line.
Ctrl-FShifts cursor to the right one character.
Ctrl-KDeletes all characters from the cursor to the end of the line.
Ctrl-NEnters the next command line in the history buffer.
Ctrl-PEnters the last command.
Ctrl-RRepeats current command line on a new line.
Ctrl-U Deletes from the cursor to the beginning of the line.
Ctrl-W Deletes the last word typed.
Esc-BMoves the cursor back one word.
Esc-DDeletes from the cursor to the end of the word.
Esc-FMoves the cursor forward one word.
Delete key or
backspace key
Erases a mistake when entering a command.
Showing Status Information
There are various “show” commands which display configuration settings or the status of specified
processes. Many of these commands will not display any information unless the switch is properly
configured, and in some cases the interface to which a command applies is up.
For example, if a static router port is configured, the corresponding show command will not display
any information unless IGMP snooping is enabled, and the link for the static router port is up.
Console#configure
Console(config)#ip igmp snooping vlan 1 mrouter ethernet 1/11
Console(config)#end
Console#show ip igmp snooping mrouter
VLAN M'cast Router Ports Type
---- ------------------- -------
Console#configure
Console(config)#ip igmp snooping
Console(config)#end
Console#show ip igmp snooping mrouter
VLAN M'cast Router Ports Type
---- ------------------- -------
1 Eth 1/11 Static
Console#
CLI Command Groups
The system commands can be broken down into the functional groups shown below.
TABLE 8Command Group Index
Command GroupDescriptionPage
General Basic commands for entering privileged access mode, restarting the
System Management Display and setting of system information, basic modes of operation,
39
system, or quitting the CLI
47
maximum frame size, file management, console port and telnet settings,
system logs, SMTP alerts, and the system clock
Activates authentication failure traps; configures community access
strings, and trap receivers
107
Remote MonitoringSupports statistics, history, alarm and event groups127
Flow SamplingSamples traffic flows, and forwards data to designated collector135
User Authentication Configures user names and passwords, logon access using local or
141
remote authentication, management access through the web server,
Telnet server and Secure Shell; as well as port security, IEEE 802.1X port
access control, and restricted access based on specified IP addresses
General Security MeasuresSegregates traffic for clients attached to common data ports; and
193
prevents unauthorized access by configuring valid static or dynamic
addresses, web authentication, MAC address authentication, filtering
DHCP requests and replies, and discarding invalid ARP responses
Access Control ListProvides filtering for IPv4 frames (based on address, protocol, TCP/UDP
239
port number or TCP control code), IPv6 frames (based on address or
DSCP traffic class), or non-IP frames (based on MAC address or Ethernet
type)
Interface Configures the connection parameters for all Ethernet ports, aggregated
261
links, and VLANs
Link AggregationStatically groups multiple ports into a single logical trunk; configures Link
289
Aggregation Control Protocol for port trunks
Mirror Port Mirrors data to another port for analysis without affecting the data
Rate LimitControls the maximum rate for traffic transmitted or received on
Automatic Traffic Control Configures bounding thresholds for broadcast and multicast
Address Table Configures the address table for filtering specified addresses,
Spanning Tree Configures Spanning Tree settings for the switch 333
ERPSConfigures Ethernet Ring Protection Switching for increased
VLANsConfigures VLAN settings, and defines port membership for VLAN
Class of Service Sets port priority for untagged frames, selects strict priority or
Quality of ServiceConfigures Differentiated Services 431
Multicast FilteringConfigures IGMP multicast filtering, query, profile, and proxy
Link Layer Discovery
Protocol
Connectivity Fault
Management
passing through or the performance of the monitored port
a port
storms which can be used to trigger configured rate limits or to
shut down a port
displays current entries, clears the table, or sets the aging time
availability of Ethernet rings commonly used in service provider
networks
groups; also enables or configures private VLANs, protocol VLANs,
voice VLANs, and QinQ tunneling
weighted round robin, relative weight for each priority queue, also
sets priority for DSCP
parameters; specifies ports attached to a multicast router; also
configures multicast VLAN registration
Configures LLDP settings to enable information discovery about
neighbor devices
Configures connectivity monitoring using continuity check
messages, fault verification through loopback messages, and
fault isolation by examining end-to-end connections between
Provider Edge devices or between Customer Edge devices
This command restarts the system at a specified time, after a specified delay, or at a periodic
interval. You can reboot the system immediately, or you can configure the switch to reset after a
specified amount of time. Use the cancel option to remove a configured setting.
Syntax
reload {at hour minute [{month day | day month} [year]] |
in {hour hours | minute minutes | hour hours minute minutes} |
regularity hour minute [period {daily
regularity]}
|
weekly day-of-week
reload at - A specified time at which to reload the switch.
hour - The hour at which to reload. (Range: 0-23)
minute - The minute at which to reload. (Range: 0-59)
month - The month at which to reload. (january ... december)
|
monthly day
}] |
cancel [at | in |
day - The day of the month at which to reload. (Range: 1-31)
year - The year at which to reload. (Range: 2001-2050)
reload in - An interval after which to reload the switch.
hours - The number of hours, combined with the minutes, before the switch resets.
(Range: 0-576)
minutes - The number of minutes, combined with the hours, before the switch resets.
(Range: 0-59)
reload
hour - The hour at which to reload. (Range: 0-23)
minute - The minute at which to reload. (Range: 0-59)
day-of-week - Day of the week at which to reload.
(Range: monday ... saturday)
day
reload cancel - Cancels the specified reload option.
Default Setting
None
Command Mode
regularity
- Day of the month at which to reload. (Range: 1-31)
- A periodic interval at which to reload the switch.
• Any combination of reload options may be specified. If the same option is re-specified, the
previous setting will be overwritten.
• When the system is restarted, it will always run the Power-On Self-Test. It will also retain all
configuration information stored in non-volatile memory by the copyrunning-config
startup-config command (See “copy” on page 67).
Example
This example shows how to reset the switch after 30 minutes:
Console(config)#reload in minute 30
***
*** --- Rebooting at January 1 02:10:43 2007 --***
Are you sure to reboot the system at the specified time? <y/n>
This command activates Privileged Exec mode. In privileged mode, additional commands are
available, and certain commands display additional information. See “Understanding Command
Modes” on page 32.
Syntax
enable [level]
level - Privilege level to log into the device.
The device has two predefined privilege levels: 0: Normal Exec, 15: Privileged Exec. Enter
level 15 to access Privileged Exec mode.
Default Setting
Level 15
Command Mode
Normal Exec
Command Usage
• “super” is the default password required to change the command mode from Normal Exec to
Privileged Exec. (To set this password, see the enable password command.)
• The “#” character is appended to the end of the prompt to indicate that the system is in
The ! command repeats commands from the Execution command history buffer when you are in
Normal Exec or Privileged Exec Mode, and commands from the Configuration command history
buffer when you are in any of the configuration modes. In this example, the !2 command repeats
the second command in the Execution history buffer (config).
Console#!2
Console#config
Console(config)#
This command activates Global Configuration mode. You must enter this mode to modify any
settings on the switch. You must also enter Global Configuration mode prior to enabling some of
the other configuration modes, such as Interface Configuration, Line Configuration, and VLAN
Database Configuration. See “Understanding Command Modes” on page 32.
Default Setting
None
Command Mode
Privileged Exec
disable
Example
Console#configure
Console(config)#
Related Commands
end (44)
This command returns to Normal Exec mode from privileged mode. In normal access mode, you
can only display basic information on the switch's configuration or Ethernet statistics. To gain
access to all commands, you must use the privileged mode. See “Understanding Command
Modes” on page 32.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
The “>” character is appended to the end of the prompt to indicate that the system is in normal
access mode.
When the system is restarted, it will always run the Power-On Self-Test. It will also retain all
configuration information stored in non-volatile memory by the copy running-config startup-config
command.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
show reload
end
This command resets the entire system.
Example
This example shows how to reset the switch:
Console#reload
System will be restarted, continue <y/n>? y
This command displays the current reload settings, and the time at which next scheduled reload
will take place.
Command Mode
Privileged Exec
Example
Console#show reload
Reloading switch in time: 0 hours 29 minutes.
The switch will be rebooted at January 1 02:11:50 2001.
Remaining Time: 0 days, 0 hours, 29 minutes, 52 seconds.
Console#
The system management commands are used to control system logs, passwords, user names,
management options, and display or configure a variety of other system information.
TABLE 10System Management Commands
Command GroupFunction
Device DesignationConfigures information that uniquely identifies this switch
Banner InformationConfigures administrative contact, device identification and location
System StatusDisplays system configuration, active managers, and version information
Frame SizeEnables support for jumbo frames
File ManagementManages code image or switch configuration files
LineSets communication parameters for the serial port, including baud rate and
console time-out
Event LoggingControls logging of error messages
SMTP AlertsConfigures SMTP email alerts
Time (System Clock)Sets the system clock automatically via NTP/SNTP server or manually
Time RangeSets a time range for use by other functions, such as Access Control Lists
Device Designation
This section describes commands used to configure information that uniquely identifies the switch.
TABLE 11Device Designation Commands
CommandFunctionMode
hostnameSpecifies the host name for the switchGC
snmp-server contactSets the system contact stringGC
snmp-server locationSets the system location string GC
hostname
This command specifies or modifies the host name for this device. Use the no form to restore the
default host name.
Syntax
hostname name
no hostname
name - The name of this host. (Maximum length: 255 characters)
These commands are used to configure and manage administrative information about the switch,
its exact data center location, details of the electrical and network circuits that supply the switch,
as well as contact information for the network administrator and system manager. This information
is only available via the CLI and is automatically displayed before login as soon as a console or
telnet connection has been established.
TABLE 12Banner Commands
CommandFunctionMode
banner configureConfigures the banner information that is displayed before loginGC
banner configure companyConfigures the Company information that is displayed by bannerGC
banner configure
dc-power-info
banner configure
department
banner configure
equipment-info
banner configure
equipment-location
banner configure ip-lanConfigures the IP and LAN information that is displayed by bannerGC
banner configure lp-number Configures the LP Number information that is displayed by bannerGC
banner configure
manager-info
banner configure muxConfigures the MUX information that is displayed by bannerGC
banner configure noteConfigures miscellaneous information that is displayed by banner
show bannerDisplays all banner informationNE, PE
Configures the DC Power information that is displayed by bannerGC
Configures the Department information that is displayed by bannerGC
Configures the Equipment information that is displayed by bannerGC
Configures the Equipment Location information that is displayed by
banner
Configures the Manager contact information that is displayed by
banner
This command is used to interactively specify administrative information for this device.
Syntax
banner configure
Default Setting
None
Command Mode
Global Configuration
Command Usage
The administrator can batch-input all details for the switch with one command. When the
administrator finishes typing the company name and presses the enter key, the script prompts for
the next piece of information, and so on, until all information has been entered. Pressing enter
without inputting information at any prompt during the script’s operation will leave the field empty.
Spaces can be used during script mode because pressing the enter key signifies the end of data
input. The delete and left-arrow keys terminate the script. The use of the backspace key during
script mode is not supported. If, for example, a mistake is made in the company name, it can be
corrected with the banner configure company command.
Example
Console(config)#banner configure
Company: Brocade
Responsible department: R&D Dept
Name and telephone to Contact the management people
Manager1 name: Sr. Network Admin
phone number: 123-555-1212
Manager2 name: Jr. Network Admin
phone number: 123-555-1213
Manager3 name: Night-shift Net Admin / Janitor
phone number: 123-555-1214
The physical location of the equipment.
City and street address: 12 Straight St. Motown, Zimbabwe
Information about this equipment:
Manufacturer: Brocade
ID: 123_unique_id_number
Floor: 2
Row: 7
Rack: 29
Shelf in this rack: 8
Information about DC power supply.
Floor: 2
Row: 7
Rack: 25
Electrical circuit: : ec-177743209-xb
Number of LP:12
Position of the equipment in the MUX:1/23
IP LAN:192.168.1.1
Note: This is a random note about this managed switch and can contain
This command is used to configure company information displayed in the banner. Use the no form
to remove the company name from the banner display.
Syntax
Default Setting
None
Command Mode
Global Configuration
Command Usage
Input strings cannot contain spaces. The banner configure company command interprets spaces
as data input boundaries. The use of underscores ( _ ) or other unobtrusive non-letter characters is
suggested for situations where white space is necessary for clarity.
banner configure company name
no banner configure company
name - The name of the company. (Maximum length: 32 characters)
Example
Console(config)#banner configure company Big-Ben
Console(config)#
banner configure dc-power-info
This command is use to configure DC power information displayed in the banner. Use the no form
to restore the default setting.