From SMC’s Tiger line of feature-rich workgroup LAN solutions
38 Tesla
Irvine, CA 92618
Phone: (949) 679-8000
June 2005
Pub. # 149100023600A
Information furnished by SMC Networks, Inc. (SMC) is believed to be
accurate and reliable. However, no responsibility is assumed by SMC for its
use, nor for any infringements of patents or other rights of third parties
which may result from its use. No license is granted by implication or
otherwise under any patent or patent rights of SMC. SMC reserves the
right to change specifications at any time without notice.
SMC is a registered trademark; and EZ Switch, TigerStack and TigerSwitch are trademarks of SMC
Networks, Inc. Other product and company names are trademarks or registered trademarks of their
respective holders.
L
IMITED
Limited Warranty Statement: SMC Networks, Inc. (“SMC”) warrants its products to be
free from defects in workmanship and materials, under normal use and service, for the
applicable warranty term. All SMC products carry a standard 90-day limited warranty from
the date of purchase from SMC or its Authorized Reseller. SMC may, at its own discretion,
repair or replace any product not operating as warranted with a similar or functionally
equivalent product, during the applicable warranty term. SMC will endeavor to repair or
replace any product returned under warranty within 30 days of receipt of the product.
The standard limited warranty can be upgraded to a Limited Lifetime* warranty by registering
new products within 30 days of purchase from SMC or its Authorized Reseller. Registration
can be accomplished via the enclosed product registration card or online via the SMC Web
site. Failure to register will not affect the standard limited warranty. The Limited Lifetime
warranty covers a product during the Life of that Product, which is defined as the period of
time during which the product is an “Active” SMC product. A product is considered to be
“Active” while it is listed on the current SMC price list. As new technologies emerge, older
technologies become obsolete and SMC will, at its discretion, replace an older product in its
product line with one that incorporates these newer technologies. At that point, the obsolete
product is discontinued and is no longer an “Active” SMC product. A list of discontinued
products with their respective dates of discontinuance can be found at:
http://www.smc.com/index.cfm?action=customer_service_warranty.
All products that are replaced become the property of SMC. Replacement products may be
either new or reconditioned. Any replaced or repaired product carries either a 30-day limited
warranty or the remainder of the initial warranty, whichever is longer. SMC is not responsible
for any custom software or firmware, configuration information, or memory data of
Customer contained in, stored on, or integrated with any products returned to SMC pursuant
to any warranty. Products returned to SMC should have any customer-installed accessory or
add-on components, such as expansion modules, removed prior to returning the product for
replacement. SMC is not responsible for these items if they are returned with the product.
Customers must contact SMC for a Return Material Authorization number prior to returning
any product to SMC. Proof of purchase may be required. Any product returned to SMC
without a valid Return Material Authorization (RMA) number clearly marked on the outside
of the package will be returned to customer at customer’s expense. For warranty claims within
North America, please call our toll-free customer support number at (800) 762-4968.
Customers are responsible for all shipping charges from their facility to SMC. SMC is
responsible for return shipping charges from SMC to customer.
W
ARRANTY
v
WARRANTIES EXCLUSIVE: IF AN SMC PRODUCT DOES NOT OPERATE AS
WARRANTED ABOVE, CUSTOMER’S SOLE REMEDY SHALL BE REPAIR OR
REPLACEMENT OF THE PRODUCT IN QUESTION, AT SMC’S OPTION. THE
FOREGOING WARRANTIES AND REMEDIES ARE EXCLUSIVE AND ARE IN
LIEU OF ALL OTHER WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED,
EITHER IN FACT OR BY OPERATION OF LAW, STATUTORY OR OTHERWISE,
INCLUDING WARRANTIES OR CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE. SMC NEITHER ASSUMES NOR
AUTHORIZES ANY OTHER PERSON TO ASSUME FOR IT ANY OTHER
LIABILITY IN CONNECTION WITH THE SALE, INSTALLATION,
MAINTENANCE OR USE OF ITS PRODUCTS. SMC SHALL NOT BE LIABLE
UNDER THIS WARRANTY IF ITS TESTING AND EXAMINATION DISCLOSE THE
ALLEGED DEFECT IN THE PRODUCT DOES NOT EXIST OR WAS CAUSED BY
CUSTOMER’S OR ANY THIRD PERSON’S MISUSE, NEGLECT, IMPROPER
INSTALLATION OR TESTING, UNAUTHORIZED ATTEMPTS TO REPAIR, OR
ANY OTHER CAUSE BEYOND THE RANGE OF THE INTENDED USE, OR BY
ACCIDENT, FIRE, LIGHTNING, OR OTHER HAZARD.
LIMITATION OF LIABILITY: IN NO EVENT, WHETHER BASED IN CONTRACT
OR TORT (INCLUDING NEGLIGENCE), SHALL SMC BE LIABLE FOR
INCIDENTAL, CONSEQUENTIAL, INDIRECT, SPECIAL, OR PUNITIVE
DAMAGES OF ANY KIND, OR FOR LOSS OF REVENUE, LOSS OF BUSINESS, OR
OTHER FINANCIAL LOSS ARISING OUT OF OR IN CONNECTION WITH THE
SALE, INSTALLATION, MAINTENANCE, USE, PERFORMANCE, FAILURE, OR
INTERRUPTION OF ITS PRODUCTS, EVEN IF SMC OR ITS AUTHORIZED
RESELLER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
SOME STATES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES
OR THE LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES FOR
CONSUMER PRODUCTS, SO THE ABOVE LIMITATIONS AND EXCLUSIONS
MAY NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL
RIGHTS, WHICH MAY VARY FROM STATE TO STATE. NOTHING IN THIS
WARRANTY SHALL BE TAKEN TO AFFECT YOUR STATUTORY RIGHTS.
* SMC will provide warranty service for one year following discontinuance from the active
SMC price list. Under the limited lifetime warranty, internal and external power supplies, fans,
and cables are covered by a standard one-year warranty from date of purchase.
This switch provides a broad range of features for Layer 2 switching and
Layer 3 routing. 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.
1
Key Features
Table 1-1 Key Features
FeatureDescription
Configuration
Backup and
Restore
AuthenticationConsole, Telnet, web – User name / password, RADIUS, TACACS+
Access Control
Lists
DHCP Client,
Relay and Server
DNS ServerSupported
Port Configuration Speed and duplex mode
Rate LimitingInput and output rate limiting per port
Backup to TFTP server
Web – SSL/HTTPS; Telnet – SSH
SNMP v1/2c – Community strings
SNMP version 3 – MD5 or SHA password
Port – IEEE 802.1X, MAC address filtering
Supports up to 32 IP or MAC ACLs
Supported
1-1
KEY F
EATURES
Table 1-1 Key Features (Continued)
FeatureDescription
Port MirroringOne or more ports mirrored to single analysis port
Port TrunkingSupports up to 32 trunks using either static or dynamic trunking
(LACP)
Broadcast Storm
Control
Address TableUp to 16K MAC addresses in forwarding table, 1024 static MAC
IEEE 802.1D
Bridge
Store-and-Forward
Switching
Spanning Tree
Algorithm
Virtual LANsUp to 255 using IEEE 802.1Q, port-based, protocol-based, or private
Traffic
Prioritization
Qualify of Service Supports Differentiated Services (DiffServ)
Router
Redundancy
IP RoutingRouting Information Protocol (RIP), Open Shortest Path First
ARPStatic and dynamic address configuration, proxy ARP
Multicast Filtering Supports IGMP snooping and query for Layer 2, and IGMP for
Supported
addresses;
Up to 8K IP entries in ARP cache, 64K IP entries in routing table,
256 static IP routes
Supports dynamic data switching and addresses learning
Supported to ensure wire-speed switching while eliminating bad
frames
Supports standard STP, Rapid Spanning Tree Protocol (RSTP), and
Multiple Spanning Trees (MSTP)
VLANs
Default port priority, traffic class map, queue scheduling, IP
Precedence, or Differentiated Services Code Point (DSCP), and
TCP/UDP Port
Router backup is provided with the Virtual Router Redundancy
Protocol (VRRP)
(OSPF), static routes
Layer 3
1-2
Description of Software Features
The switch provides a wide range of advanced performance enhancing
features. 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 and
routing provides support for real-time network applications. Some of the
management features are briefly described below.
Configuration Backup and Restore – You can save the current
configuration settings to a file on a TFTP server, and later download this
file to restore the switch configuration settings.
Authentication – This switch authenticates management access via the
console port, Telnet or 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 server).
I
NTRODUCTION
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/web/Telnet management access, and MAC address filtering for
port access.
Access Control Lists – 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
1-3
D
ESCRIPTION OF SOFTWARE FEATURES
or to implement security controls by restricting access to specific network
resources or protocols.
DHCP Server and DHCP Relay – A DHCP server is provided to assign
IP addresses to host devices. Since DHCP uses a broadcast mechanism, a
DHCP server and its client must physically reside on the same subnet.
Since it is not practical to have a DHCP server on every subnet, DHCP
Relay is also supported to allow dynamic configuration of local clients
from a DHCP server located in a different network.
Port Configuration – You can manually configure the speed and duplex
mode used on specific ports, or use auto-negotiation to detect the
connection settings used by the attached device. Use the full-duplex mode
on ports whenever possible to double the throughput of switch
connections.
Rate Limiting – This feature controls the maximum rate for traffic
transmitted or received on an interface. Rate limiting is configured on
interfaces at the edge of a network to limit traffic into or out of the
network. Traffic that falls within the rate limit is transmitted, while packets
that exceed the acceptable amount of traffic are dropped.
Port Mirroring – The switch can unobtrusively mirror traffic from any
port to a monitor port. You can then attach a protocol analyzer or RMON
probe to this port to perform traffic analysis and verify connection
integrity.
Port Trunking – Ports can be combined into an aggregate connection.
Trunks can be manually set up or dynamically configured using IEEE
802.3-2002 (formerly IEEE 802.3ad) Link Aggregation Control Protocol
(LACP). 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 32 trunks.
1-4
I
NTRODUCTION
Broadcast Storm Control – Broadcast suppression prevents broadcast
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.
Static Addresses – A 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.
IEEE 802.1D Bridge – 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
address table supports up to 16K addresses.
Store-and-Forward Switching – 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 SMC8724ML3 and
SMC8748ML3 provide 2 MB and 4 MB, respectively, for frame buffering.
This buffer can queue packets awaiting transmission on congested
networks.
1-5
D
ESCRIPTION OF SOFTWARE FEATURES
Spanning Tree Algorithm – The switch supports these spanning tree
protocols:
Spanning Tree Protocol (STP, IEEE 802.1D) – This protocol provides
loop detection and recovery by allowing two or more redundant
connections to be created between a pair of LAN segments. 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).
Virtual LANs – The switch supports up to 255 VLANs. A Virtual LAN is
a collection of network nodes that share 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
1-6
I
NTRODUCTION
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.
Traffic Prioritization – This switch prioritizes each packet based on the
required level of service, using eight priority queues with strict or Weighted
Round Robin 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 be used to provide independent priorities for 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 or the
number of the TCP/UDP port. 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.
IP Routing – The 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
1-7
D
ESCRIPTION OF SOFTWARE FEATURES
easily link network segments or VLANs together without having to deal
with the bottlenecks or configuration hassles normally associated with
conventional routers.
Routing for unicast traffic is supported with the Routing Information
Protocol (RIP) and the Open Shortest Path First (OSPF) protocol.
RIP – This protocol uses a distance-vector approach to routing. Routes are
determined on the basis of minimizing the distance vector, or hop count,
which serves as a rough estimate of transmission cost.
OSPF – This approach uses a link state routing protocol to generate a
shortest-path tree, then builds up its routing table based on this tree. OSPF
produces a more stable network because the participating routers act on
network changes predictably and simultaneously, converging on the best
route more quickly than RIP.
Router Redundancy – The Virtual Router Redundancy Protocol (VRRP)
uses a virtual IP address to support a primary router and multiple backup
routers. The backups can be configured to take over the workload if the
master fails or to load share the traffic. The primary goal of this protocol is
to allow a host device which has been configured with a fixed gateway to
maintain network connectivity in case the primary gateway goes down.
Address Resolution Protocol – The switch uses ARP and Proxy ARP to
convert between IP addresses and MAC (i.e., hardware) addresses. This
switch supports conventional ARP, which locates the MAC address
corresponding to a given IP address. This allows the switch to use IP
addresses for routing decisions and the corresponding MAC addresses to
forward packets from one hop to the next. You can configure either static
or dynamic entries in the ARP cache.
Proxy ARP allows hosts that do not support routing to determine the
MAC address of a device on another network or subnet. When a host
sends an ARP request for a remote network, the switch checks to see if it
has the best route. If it does, it sends its own MAC address to the host. The
host then sends traffic for the remote destination via the switch, which
uses its own routing table to reach the destination on the other network.
1-8
Quality of Service – 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.
Multicast Filtering – 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 at Layer 2
and IGMP at Layer 3 to manage multicast group registration.
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 (page 3-32).
I
NTRODUCTION
The following table lists some of the basic system defaults.
SMTP Email Alerts Event HandlerEnabled (but no server defined)
SNTP Clock SynchronizationDisabled
Table 1-2 System Defaults (Continued)
IP address
IP Address0.0.0.0
Subnet Mask255.0.0.0
Default Gateway0.0.0.0
DHCPClient: Enabled
DNSServer: Disabled
BOOTPDisabled
ARP
OSPFDisabled
VRRPDisabled
IGMP (Layer 3)Disabled
Messages LoggedLevels 0-7 (all)
Messages Logged to Flash Levels 0-3
Relay: Disabled
Server: Disabled
Enabled
Cache Timeout: 20 minutes
Proxy: Disabled
Querier: Disabled
*There are interoperability problems between Flow Control and Head-of-Line (HOL) blocking for
the switch ASIC; Flow Control is therefore not supported for this switch.
1-12
C
HAPTER
I
NITIAL
C
ONFIGURATION
Connecting to the Switch
Configuration Options
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).
Note: The IP address for this switch is obtained via DHCP by default.
To change this address, see “Setting an IP Address” on page 2-10.
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 Netscape Navigator version 6.2 and higher or Microsoft
IE version 5.0 and higher. The switch’s web management interface can be
accessed from any computer attached to the network.
2
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 such as HP OpenView.
2-1
C
ONNECTING TO THE SWITCH
The switch’s web interface, CLI configuration program, and SNMP agent
allow you to perform the following management functions:
•Set user names and passwords
•Set an IP interface for any VLAN
•Configure SNMP parameters
•Enable/disable any port
•Set the speed/duplex mode for any port
•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 255 IEEE 802.1Q VLANs
•Enable GVRP automatic VLAN registration
•Configure IP routing for unicast traffic
•Configure router redundancy
•Configure IGMP multicast filtering
•Upload and download system firmware via TFTP
•Upload and download switch configuration files via TFTP
•Configure Spanning Tree parameters
•Configure Class of Service (CoS) priority queuing
•Configure up to 6 static or LACP trunks per switch, up to 32 per stack
•Enable port mirroring
•Set broadcast storm control on any port
•Display system information and statistics
•Configure any stack unit through the same IP address
2-2
I
NITIAL CONFIGURATION
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.
Note: When configuring a stack, connect to the console port on the
Master unit.
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 to any of the following baud rates: 9600, 19200, 38400, 57600,
115200 (Note: Set to 9600 baud if want to view all the system
initialization messages.).
•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.
2-3
C
ONNECTING TO THE SWITCH
Notes: 1. When using HyperTerminal with Microsoft® Windows® 2000,
make sure that you have Windows 2000 Service Pack 2 or later
installed. Windows 2000 Service Pack 2 fixes the problem of
arrow keys not functioning in HyperTerminal’s VT100
emulation. See www.microsoft.com for information on
Windows 2000 service packs.
2. Refer to “Line Commands” on page 4-14 for a complete
description of console configuration options.
3. 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 4-1. For a list of all the CLI commands and detailed
information on using the CLI, refer to “Command Groups” on page 4-12.
Remote Connections
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, DHCP or BOOTP protocol.
The IP address for this switch is obtained via DHCP by default. To
manually configure this address or enable dynamic address assignment via
DHCP or BOOTP, see “Setting an IP Address” on page 2-10.
Notes: 1. This switch supports four concurrent Telnet/SSH sessions.
2. Each VLAN group can be assigned its own IP interface
address (page 2-10). You can manage the stack via any IP
interface in the stack. In other words, the Master unit does not
have to include an active port member of a VLAN interface
used for management access.
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
2-4
I
NITIAL CONFIGURATION
computer using a web browser (Internet Explorer 5.0 or above, or
Netscape Navigator 6.2 or above), or from a network computer using
SNMP network management software.
Note: 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.
Stack Operations
Up to eight 24-port or 48-port Gigabit switches can be stacked together as
described in the Installation Guide. One unit in the stack acts as the Master
for configuration tasks and firmware upgrade. All of the other units
function in Slave mode, but can automatically take over management of
the stack if the Master unit fails.
To configure any unit in the stack, first verify the unit number from the
front panel of the switch, and then select the appropriate unit number
from the web or console management interface.
Selecting the Stack Master
Note the following points about unit numbering:
•When the stack is initially powered on, the Master unit is designated as
unit 1 for a ring topology. For a line topology, the stack is simply
numbered from top to bottom, with the first unit in the stack
designated at unit 1. This unit identification number appears on the
Stack Unit ID LED on the front panel of the switch. It can also be
selected on the front panel graphic of the web interface, or from the
CLI.
•If more than one stack Master is selected using the Master/Slave push
button on the switch’s front panel, the system will select the unit with
the lowest MAC address as the Master.
2-5
S
TACK OPERATIONS
•If the Master unit fails and another unit takes over control of the stack,
the unit numbering will not change.
•If a unit in the stack fails or is removed from the stack, the unit
numbers will not change. This means that when you replace a unit in
the stack, the original configuration for the failed unit will be restored
to the replacement unit.
•If a unit is removed from the stack and later reattached to the stack, it
will retain the original unit number obtained during stacking.
•If a unit is removed from the stack, and powered up as a stand-alone
unit, it will also retain the original unit number obtained during
stacking.
Selecting the Backup Unit
Once the Master unit finishes booting up, the Slave unit with the lowest
MAC address will be selected from the stack as the primary backup unit.
The stack Master immediately downloads all configuration information to
the backup unit, and continues to update the backup unit with information
about any subsequent configuration changes made to any unit in the stack.
If the Master unit fails or is powered off, the backup unit will take control
of the stack without any loss of configuration settings.
The Slave unit with the lowest MAC address is selected as the Backup unit.
If you want to ensure a logical fail over to next unit down in the stack,
place the Slave unit with the lowest MAC address directly beneath the
Master unit in the stack.
Recovering from Stack Failure or Topology Change
When a link or unit in the stack fails, a trap message is sent and a failure
event is logged. The stack will be rebooted after any system failure or
topology change. It takes two to three minutes to for the stack to reboot. If
the Master unit fails, the backup unit will take over operations as the new
Master unit, reboot the stack, and then select another backup unit after the
stack finishes rebooting. Also note that powering down a unit or inserting
2-6
I
NITIAL CONFIGURATION
a new unit in the stack will cause the stack to reboot. If a unit is removed
from the stack (due to a power down or failure) or a new unit added to the
stack, the original unit IDs are not affected after rebooting, and a new unit
is assigned the lowest available unit ID.
Broken Link for Line and Wrap-around Topologies
All units in the stack must be connected via stacking cable. You can
connect the units in a simple cascade configuration from the top to the
bottom unit. Using this kind of line topology, if any link or unit in the stack
fails, the stack will be broken in two. The Stack Link LED on the unit that
is no longer receiving traffic from the next unit up or down in the stack
will begin flashing to indicate that the stack link is broken.
When the stack fails, a Master unit is selected from the two stack segments,
either the unit with the Master button depressed, or the unit with the
lowest MAC address if the Master button is not depressed on any unit. The
stack reboots and resumes operations. However, note that the IP address
will be the same for any common VLANs (with active port connections)
that appear in both of the new stack segments. To resolve the conflicting
IP addresses, you should manually replace the failed link or unit as soon as
possible. If you are using a wrap-around stack topology, a single point of
failure in the stack will not cause the stack to fail. It would take two or
more points of failure to break the stack apart.
Note: If a stack breaks apart, the IP address will be the same for any
common VLANs (with active port connections) that appear in
both stack segments.
Resilient IP Interface for Management Access
The stack functions as one integral system for management and
configuration purposes. You can therefore manage the stack through any
IP interface configured on the stack. The Master unit does not even have
to include an active port member in the VLAN interface used for
management access. However, if the unit to which you normally connect
for management access fails, and there are no active port members on the
2-7
B
ASIC CONFIGURATION
other units within this VLAN interface, then this IP address will no longer
be available. To retain a constant IP address for management access across
fail over events, you should include port members on several units within
the primary VLAN used for stack management.
Resilient Configuration
If a unit in the stack fails, the unit numbers will not change. This means
that when you replace a unit in the stack, the original configuration for the
failed unit will be restored to the replacement unit. This applies to both the
Master and Slave units.
Renumbering the Stack
The startup configuration file maps configuration settings to each switch
in the stack based on the unit identification number. If the units are no
longer numbered sequentially after several topology changes or failures,
you can reset the unit numbers using the “Renumbering” command in the
web interface or CLI. Just remember to save the new configuration settings
to a startup configuration file prior to powering off the stack Master.
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.
Note: You can only access the console interface through the Master unit
in the stack.
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
2-8
I
NITIAL CONFIGURATION
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 Username 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.
Setting Passwords
Note: 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 8 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 SMC8748ML3 is opened.
To end the CLI session, enter [Exit].
You must establish IP address information for the stack 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 stack’s master unit, you will also need to specify the default gateway
router.
Dynamic — The switch sends IP configuration requests to BOOTP or
DHCP address allocation servers on the network.
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 (if routing is not enabled
on this switch). Valid IP addresses consist of four decimal numbers, 0 to
255, separated by periods. Anything outside this format will not be
accepted by the CLI program.
Note: The IP address for this switch is obtained via DHCP by default.
Before you can assign an IP address to the switch, you must obtain the
following information from your network administrator:
•IP address for the switch
•Default gateway for the network
•Network mask for this network
To assign an IP address to the switch, complete the following steps:
1. From the Privileged Exec level global configuration mode prompt,
type “interface vlan 1” to access the interface-configuration mode.
Press <Enter>.
2. Type “ip address ip-address netmask,” where “ip-address” is the switch
IP address and “netmask” is the network mask for the network. Press
<Enter>.
2-10
I
NITIAL CONFIGURATION
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>.
If you select the “bootp” or “dhcp” option, IP will be enabled but will not
function until a BOOTP or DHCP reply has been received. You therefore
need to use the “ip dhcp restart client” command to start broadcasting
service requests. Requests will be sent periodically in an effort to obtain IP
configuration information. (BOOTP and DHCP values can include the IP
address, subnet mask, and default gateway.)
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>.
2-11
B
ASIC CONFIGURATION
3. Type “end” to return to the Privileged Exec mode. Press <Enter>.
4. Type “ip dhcp restart client” to begin broadcasting service requests.
Press <Enter>.
5. Wait a few minutes, and then check the IP configuration settings by
typing the “show ip interface” command. Press <Enter>.
6. 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#ip dhcp restart client
Console#show ip interface
IP address and netmask: 192.168.1.54 255.255.255.0 on VLAN 1,
and address mode: User specified.
Console#copy running-config startup-config
Startup configuration file name []: startup
\Write to FLASH Programming.
\Write to FLASH finish.
Success.
Enabling SNMP Management Access
The switch can be configured to accept management commands from
Simple Network Management Protocol (SNMP) applications such as HP
OpenView. You can configure the switch to (1) respond to SNMP requests
or (2) 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
2-12
I
NITIAL CONFIGURATION
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
page 3-72).
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 objects.
•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 string mode,” 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)#
2-13
B
ASIC CONFIGURATION
Note: 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 4-143. 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
2-14
I
NITIAL CONFIGURATION
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 mib-2 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 3-50, or refer to the specific CLI commands for SNMP starting on
page 4-139.
Saving 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.
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#
2-15
M
ANAGING SYSTEM FILES
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 three 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 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 master unit will also create a file named
“startup1.cfg” that contains system settings for stack initialization,
including information about the unit identifier, MAC address, and
installed module type for each unit the stack. The configuration
settings from the factory defaults configuration file are copied to this
file, which is then used to boot the stack. See “Saving or Restoring
Configuration Settings” on page 3-22 for more information. See
“Saving or Restoring Configuration Settings” on page 3-30 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
Firmware” on page 3-27 for more information.
•Diagnostic Code — Software that is run during system boot-up, also
known as POST (Power On Self-Test).
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.
2-16
I
NITIAL CONFIGURATION
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.
2-17
M
ANAGING SYSTEM FILES
2-18
C
HAPTER
C
ONFIGURING THE
S
WITCH
Using the Web Interface
This switch provides an embedded HTTP web agent. Using a web browser
you can configure the switch and view statistics to monitor network
activity. The web agent can be accessed by any computer on the network
using a standard web browser (Internet Explorer 5.0 or above, or Netscape
Navigator 6.2 or above).
Note: You can also use the Command Line Interface (CLI) to manage
the switch over a serial connection to the console port or via
Telnet.For more information on using the CLI, refer to Chapter 4
“Command Line Interface.”
Prior to accessing the switch from a web browser, be sure you have first
performed the following tasks:
1. Configure the switch with a valid IP address, subnet mask, and default
gateway using an out-of-band serial connection, BOOTP or DHCP
protocol. (See“Setting an IP Address” on page 2-10.)
2. Set user names and passwords using an out-of-band serial connection.
Access to the web agent is controlled by the same user names and
passwords as the onboard configuration program. (See “Setting
Passwords” on page 2-9.)
3. After you enter a user name and password, you will have access to the
system configuration program.
3
3-1
C
ONFIGURING THE SWITCH
Notes: 1. You are allowed three attempts to enter the correct password;
on the third failed attempt the current connection is
terminated.
2. If you log into the web interface as guest (Normal Exec level),
you can view the configuration settings or change the guest
password. If you log in as “admin” (Privileged Exec level), you
can change the settings on any page.
3. If the path between your management station and this switch
does not pass through any device that uses the Spanning Tree
Algorithm, then you can set the switch port attached to your
management station to fast forwarding (i.e., enable Admin
Edge Port) to improve the switch’s response time to
management commands issued through the web interface. See
“Configuring Interface Settings” on page 3-170.
3-2
N
AVIGATING THE WEB BROWSER INTERFACE
Navigating the Web Browser Interface
To access the web-browser interface you must first enter a user name and
password. The administrator has Read/Write access to all configuration
parameters and statistics. The default user name and password for the
administrator is “admin.”
Home Page
When your web browser connects with the switch’s web agent, the home
page is displayed as shown below. The home page displays the Main Menu
on the left side of the screen and System Information on the right side.
The Main Menu links are used to navigate to other menus, and display
configuration parameters and statistics.
Figure 3-1 Home Page
Note: The examples in this chapter are based on the SMC8724ML3.
Other than the number of fixed ports, there are no major
differences between the SMC8724ML3 and SMC8748ML3.
3-3
C
ONFIGURING THE SWITCH
Configuration Options
Configurable parameters have a dialog box or a drop-down list. Once a
configuration change has been made on a page, be sure to click on the
Apply button to confirm the new setting. The following table summarizes
the web page configuration buttons.
Table 3-1 Web Page Configuration Buttons
ButtonAction
ApplySets specified values to the system.
RevertCancels specified values and restores current values
prior to pressing “Apply.”
HelpLinks directly to web help.
Notes: 1. To ensure proper screen refresh, be sure that Internet Explorer
5.x is configured as follows: Under the menu “Tools / Internet
Options / General / Temporary Internet Files / Settings,” the
setting for item “Check for newer versions of stored pages”
should be “Every visit to the page.”
2. When using Internet Explorer 5.0, you may have to manually
refresh the screen after making configuration changes by
pressing the browser’s refresh button.
Panel Display
The web agent displays an image of the switch’s ports. The Mode can be
set to display different information for the ports, including Active (i.e., up
or down), Duplex (i.e., half or full duplex), or Flow Control
1
. Clicking on
the image of a port opens the Port Configuration page as described on
page 3-122.
Figure 3-2 Front Panel Indicators
1. There are interoperability problems between Flow Control and Head-of-Line (HOL) blocking for the
switch ASIC; Flow Control is therefore not supported for this switch.
3-4
N
AVIGATING THE WEB BROWSER INTERFACE
Main Menu
Using the onboard web agent, you can define system parameters, manage
and control the switch, and all its ports, or monitor network conditions.
The following table briefly describes the selections available from this
program.
Table 3-2 Switch Main Menu
MenuDescriptionPage
System3-15
System InformationProvides basic system description, including
contact information
Switch InformationShows the number of ports, hardware/
firmware version numbers, and power status
Bridge ExtensionShows the bridge extension parameters3-19
Jumbo FramesEnables support for jumbo frames3-21
File Management3-27
Copy OperationAllows the transfer and copying files3-27
DeleteAllows deletion of files from the flash
memory
Set StartupSets the startup file3-27
Line3-34
ConsoleSets console port connection parameters3-34
TelnetSets Telnet connection parameters3-36
Log
Logs Sends error messages to a logging process
System Logs Stores and displays error messages
Remote Logs Configures the logging of messages to a
remote logging process
SMTPSends an SMTP client message to a
participating server
RenumberingRenumbers the units in the stack3-46
ResetRestarts the switch3-47
3-15
3-17
3-27
3-38
3-38
3-43
3-41
3-44
3-5
C
ONFIGURING THE SWITCH
MenuDescriptionPage
SNTP3-48
ConfigurationConfigures SNTP client settings, including a
Clock Time ZoneSets the local time zone for the system clock3-49
SNMP3-50
ConfigurationConfigures community strings and related
Agent StatusEnables or disables SNMP 3-53
SNMPv33-58
Engine IDSets the SNMP v3 engine ID3-58
Remote Engine IDSets the SNMP v3 engine ID on a remote
UsersConfigures SNMP v3 users3-60
Remote UsersConfigures SNMP v3 users on a remote
GroupsConfigures SNMP v3 groups3-66
ViewsConfigures SNMP v3 views3-72
Security3-53
User AccountsConfigures user names, passwords, and access
General ConfigurationEnables DNS; configures domain name and
Static Host TableConfigures static entries for domain name to
CacheDisplays cache entries discovered by
Displays the ports that are attached to a
neighboring multicast router for each VLAN
ID
Assigns ports that are attached to a
neighboring multicast router
Displays all multicast groups active on this
switch, including multicast IP addresses and
VLAN ID
Indicates multicast addresses associated with
the selected VLAN
domain list; and specifies IP address of name
servers for dynamic lookup
address mapping
designated name servers
3-216
3-225
3-228
3-230
3-231
3-232
3-233
3-235
3-238
3-240
3-11
C
ONFIGURING THE SWITCH
MenuDescriptionPage
DHCP3-242
Relay ConfigurationSpecifies DHCP relay servers; enables or
ServerConfigures DHCP server parameters3-242
GeneralEnables DHCP server; configures excluded
Pool ConfigurationConfigures address pools for network groups
IP BindingDisplays addresses currently bound to DHCP
IP3-265
General3-269
Global SettingsEnables or disables routing, specifies the
Routing InterfaceConfigures the IP interface for the specified
ARP3-273
GeneralSets the protocol timeout, and enables or
Static AddressesStatically maps a physical address to an IP
Dynamic AddressesShows dynamically learned entries in the IP
Other AddressesShows internal addresses used by the switch3-279
StatisticsShows statistics on ARP requests sent and
Table 3-2 Switch Main Menu (Continued)
3-242
disables relay service
3-245
address range
3-246
or a specific host
3-252
clients
3-269
default gateway
3-271
VLAN
3-274
disables proxy ARP for the specified VLAN
3-276
address
3-277
routing table
3-280
received
3-12
N
AVIGATING THE WEB BROWSER INTERFACE
Table 3-2 Switch Main Menu (Continued)
MenuDescriptionPage
Statistics3-282
IP Shows statistics for IP traffic, including the
amount of traffic, address errors, routing,
fragmentation and reassembly
ICMPShows statistics for ICMP traffic, including
the amount of traffic, protocol errors, and the
number of echoes, timestamps, and address
masks
UDPShows statistics for UDP, including the
amount of traffic and errors
TCP Shows statistics for TCP, including the
amount of traffic and TCP connection activity
Routing3-266
Static RoutesConfigures and display static routing entries3-289
Routing TableShows all routing entries, including local,
static and dynamic routes
VRRP3-256
Group Configuration Configures VRRP groups, including virtual
interface address, advertisement interval,
preemption, priority, and authentication
Global Statistics Displays global statistics for VRRP protocol
packet errors
Group Statistics Displays statistics for VRRP protocol events
and errors on the specified VRRP group and
interface
3-282
3-284
3-287
3-288
3-290
3-256
3-262
3-263
3-13
C
ONFIGURING THE SWITCH
MenuDescriptionPage
Routing Protocol3-268
RIP3-292
General SettingsEnables or disables RIP, sets the global RIP
Network AddressesConfigures the network interfaces that will
Interface SettingsConfigures RIP parameters for each interface,
StatisticsDisplays general information on update time,
OSPF3-303
General Configuration Enables or disables OSPF; also configures the
Area ConfigurationSpecifies rules for importing routes into each
Area Range
Configuration
Interface
Configuration
Virtual Link
Configuration
Network Area Address
Configuration
Summary Address
Configuration
Redistribute
Configuration
Table 3-2 Switch Main Menu (Continued)
version and timer values
use RIP
including send and receive versions, message
loopback prevention, and authentication
route changes and number of queries, as well
as a list of statistics for known interfaces and
neighbors
Router ID and various other global settings
area
Configures route summaries to advertise at an
area boundary
Shows area ID and designated router; also
configures OSPF protocol settings and
authentication for each interface
Configures a virtual link through a transit area
to the backbone
Defines OSPF areas and associated interfaces 3-323
Aggregates routes learned from other
protocols for advertising into other
autonomous systems
Redistributes routes from one routing domain
to another
3-293
3-295
3-296
3-300
3-305
3-309
3-313
3-315
3-321
3-325
3-327
3-14
B
ASIC CONFIGURATION
Table 3-2 Switch Main Menu (Continued)
MenuDescriptionPage
NSSA SettingsConfigures settings for importing routes into
or exporting routes out of not-so-stubby areas
Link State Database
Information
Border Router
Information
Neighbor Information Displays information about neighboring
Shows information about different OSPF
Link State Advertisements (LSAs) stored in
this router’s database
Displays routing table entries for area border
routers and autonomous system boundary
routers
routers on each interface within an OSPF area
Basic Configuration
Displaying System Information
You can easily identify the system by displaying the device name, location
and contact information.
3-329
3-330
3-333
3-334
Field Attributes
• System Name – Name assigned to the switch system.
• Object ID – MIB II object ID for switch’s network management
subsystem.
• Location – Specifies the system location.
• Contact – Administrator responsible for the system.
• System Up Time – Length of time the management agent has been up.
These additional parameters are displayed for the CLI.
• MAC Address – The physical layer address for this switch.
• Web server – Shows if management access via HTTP is enabled.
• Web server port – Shows the TCP port number used by the web
interface.
3-15
C
ONFIGURING THE SWITCH
• Web secure server – Shows if management access via HTTPS is
enabled.
• Web secure server port – Shows the TCP port used by the HTTPS
interface.
• Telnet server – Shows if management access via Telnet is enabled.
• Telnet server port – Shows the TCP port used by the Telnet interface.
• Authentication login – Shows the user login authentication sequence.
• Jumbo Frame – Shows if jumbo frames are enabled.
• POST result – Shows results of the power-on self-test
Web – Click System, System Information. Specify the system name,
location, and contact information for the system administrator, then click
Apply. (This page also includes a Telnet button that allows access to the
Command Line Interface via Telnet.)
3-16
Figure 3-3 System Information
B
ASIC CONFIGURATION
CLI – Specify the hostname, location and contact information.
Console(config)#hostname R&D 54-34
Console(config)#snmp-server location WC 94-143
Console(config)#snmp-server contact Ted4-142
Console(config)#exit
Console#show system4-80
System description: SMC8724ML3 L3 GE Switch
System OID string: 1.3.6.1.4.1.202.20.45
System information
System Up time: 0 days, 1 hours, 28 minutes, and 0.51
seconds
System Name: R&D 5
System Location: WC 9
System Contact: Ted
MAC address (unit1): 00-30-F1-D4-73-A0
Web server: enabled
Web server port: 80
Web secure server: enabled
Web secure server port: 443
Telnet server: enable
Telnet server port: 23
Authentication login: local RADIUS none
Jumbo Frame: Disabled
POST result
UART Loopback Test ........... PASS
DRAM Test .................... PASS
Timer Test ................... PASS
PCI Device 1 Test ............ PASS
I2C Bus Initialization ....... PASS
Switch Int Loopback Test ..... PASS
Crossbar Int Loopback Test ... PASS
Fan Speed Test ............... PASS
Done All Pass.
Console#
Displaying Switch Hardware/Software Versions
Use the Switch Information page to display hardware/firmware version
numbers for the main board and management software, as well as the
power status of the system.
Field Attributes
Main Board
• Serial Number – The serial number of the switch.
• Number of Ports – Number of built-in ports.
• Hardware Version – Hardware version of the main board.
3-17
C
ONFIGURING THE SWITCH
• Internal Power Status – Displays the status of the internal power
supply.
Management Software
• EPLD Version – Version number of EEPROM Programmable Logic
Device.
• Loader Version – Version number of loader code.
• Boot-ROM Version – Version of Power-On Self-Test (POST) and
boot code.
• Operation Code Version – Version number of runtime code.
• Role – Shows that this switch is operating as Master or Slave.
These additional parameters are displayed for the CLI.
• Unit ID – Unit number in stack.
• Redundant Power Status – Displays the status of the redundant power
supply.
Web – Click System, Switch Information.
3-18
Figure 3-4 Switch Information
B
ASIC CONFIGURATION
CLI – Use the following command to display version information.
Console#show version4-81
Unit 1
Serial number: A422000632
Hardware version: R01
EPLD version: 15.15
Number of ports: 24
Main power status: up
Redundant power status: not present
Agent (master)
Unit ID: 1
Loader version: 1.0.1.3
Boot ROM version: 1.0.1.6
Operation code version: 1.0.0.0
Console#
Displaying Bridge Extension Capabilities
The Bridge MIB includes extensions for managed devices that support
Multicast Filtering, Traffic Classes, and Virtual LANs. You can access these
extensions to display default settings for the key variables.
Field Attributes
• Extended Multicast Filtering Services – This switch does not support
the filtering of individual multicast addresses based on GMRP (GARP
Multicast Registration Protocol).
• Traffic Classes – This switch provides mapping of user priorities to
multiple traffic classes. (Refer to “Class of Service Configuration” on
page 3-203.)
• Static Entry Individual Port – This switch allows static filtering for
unicast and multicast addresses. (Refer to “Setting Static Addresses” on
page 3-151.)
• VLAN Learning – This switch uses Independent VLAN Learning
(IVL), where each port maintains its own filtering database.
• Configurable PVID Tagging – This switch allows you to override the
default Port VLAN ID (PVID used in frame tags) and egress status
(VLAN-Tagged or Untagged) on each port. (Refer to “VLAN
Configuration” on page 3-181.)
3-19
C
ONFIGURING THE SWITCH
• Local VLAN Capable – This switch does not support multiple local
bridges outside of the scope of 802.1Q defined VLANs.
• GMRP – GARP Multicast Registration Protocol (GMRP) allows
network devices to register endstations with multicast groups. This
switch does not support GMRP; it uses the Internet Group Management
Protocol (IGMP) to provide automatic multicast filtering.
Console#show bridge-ext4-265
Max support VLAN numbers: 256
Max support VLAN ID: 4093
Extended multicast filtering services: No
Static entry individual port: Yes
VLAN learning: IVL
Configurable PVID tagging: Yes
Local VLAN capable: No
Traffic classes: Enabled
Global GVRP status: Disabled
GMRP: Disabled
Console#
3-20
B
ASIC CONFIGURATION
Configuring Support for Jumbo Frames
The switch provides more efficient throughput for large sequential data
transfers by supporting jumbo frames up to 9000 bytes. Compared to
standard Ethernet frames that run only up to 1.5 KB, using jumbo frames
significantly reduces the per-packet overhead required to process protocol
encapsulation fields.
Command Usage
To use jumbo frames, both the source and destination end nodes (such as a
computer or server) must support this feature. Also, when the connection
is operating at full duplex, all switches in the network between the two end
nodes must be able to accept the extended frame size. And for half-duplex
connections, all devices in the collision domain would need to support
jumbo frames.
Command Attributes
Jumbo Packet Status – Configures support for jumbo frames.
(Default: Disabled)
Web – Click System, Jumbo Frames. Enable or disable support for jumbo
frames, and click Apply.
Figure 3-6 Configuring Support for Jumbo Frames
CLI – This example enables jumbo frames globally for the switch.
Console(config)#jumbo frame4-82
Console(config)#
3-21
C
ONFIGURING THE SWITCH
Setting the Switch’s IP Address
This section describes how to configure an initial IP interface for
management access over the network. The IP address for this stack is
obtained via DHCP by default. To manually configure an address, you
need to change the stack’s default settings to values that are compatible
with your network. You may also need to a establish a default gateway
between the stack and management stations that exist on another network
segment (if routing is not enabled on this stack).
You can manually configure a specific IP address, or direct the device to
obtain an address from a BOOTP or DHCP server. Valid IP addresses
consist of four decimal numbers, 0 to 255, separated by periods. Anything
outside this format will not be accepted by the CLI program.
Command Usage
• This section describes how to configure a single local interface for initial
access to the stack. To configure multiple IP interfaces on this stack, you
must set up an IP interface for each VLAN (page 3-271).
• To enable routing between the different interfaces on this stack, you
must enable IP routing (page 3-269).
• To enable routing between the interfaces defined on this stack and
external network interfaces, you must configure static routes (page
page 3-289) or use dynamic routing; i.e., either RIP (page 3-292) or
OSPF (page 3-303).
• The precedence for configuring IP interfaces is the IP / General /
Routing Interface menu (page 3-271), static routes (page 3-289), and then
dynamic routing.
Command Attributes
• VLAN – ID of the configured VLAN (1-4093). By default, all ports on
the stack are members of VLAN 1. However, the management station
can be attached to a port belonging to any VLAN, as long as that VLAN
has been assigned an IP address.
3-22
B
ASIC CONFIGURATION
• IP Address Mode – Specifies whether IP functionality is enabled via
manual configuration (Static), Dynamic Host Configuration Protocol
(DHCP), or Boot Protocol (BOOTP). If DHCP/BOOTP is enabled, IP
will not function until a reply has been received from the server.
Requests will be broadcast periodically by the switch for an IP address.
(DHCP/BOOTP values can include the IP address, subnet mask, and
default gateway.)
• IP Address – Address of the VLAN to which the management station
is attached. (Note you can manage the stack through any configured IP
interface.) Valid IP addresses consist of four numbers, 0 to 255,
separated by periods. (Default: 0.0.0.0)
• Subnet Mask – This mask identifies the host address bits used for
routing to specific subnets. (Default: 255.0.0.0)
• Default Gateway – IP address of the gateway router between the stack
and management stations that exist on other network segments.
(Default: 0.0.0.0)
Manual Configuration
Web – Click IP, General, Routing Interface. Select the VLAN through
which the management station is attached, set the IP Address Mode to
“Static,” and specify a “Primary” interface. Enter the IP address, subnet
mask and g ateway, then c l i ck Apply.
Figure 3-7 IP Interface Configuration - Manual
3-23
C
ONFIGURING THE SWITCH
Click IP, Global Setting. If this stack and management stations exist on
other network segments, then specify the default gateway, and click Apply.
Figure 3-8 Default Gateway
CLI – Specify the management interface, IP address and default gateway.
If your network provides DHCP/BOOTP services, you can configure the
stack to be dynamically configured by these services.
Web – Click IP, General, Routing Interface. Specify the VLAN to which
the management station is attached, set the IP Address Mode to DHCP or
BOOTP. Click Apply to save your changes. Then click Restart DHCP to
immediately request a new address. Note that the stack will also broadcast
a request for IP configuration settings on each power reset.
Figure 3-9 IP Interface Configuration - DHCP
Note: If you lose your management connection, make a console
connection to the Master unit and enter “show ip interface” to
determine the new stack address.
3-25
C
ONFIGURING THE SWITCH
CLI – Specify the management interface, and set the IP address mode to
DHCP or BOOTP, and then enter the “ip dhcp restart client” command.
Vlan 1 is up, addressing mode is DHCP
Interface address is 192.168.1.253, mask is 255.255.255.0, Primary
MTU is 1500 bytes
Proxy ARP is disabled
Split horizon is enabled
Console#
Renewing DCHP – DHCP may lease addresses to clients indefinitely or
for a specific period of time. If the address expires or the stack is moved to
another network segment, you will lose management access to the stack. In
this case, you can reboot the stack or submit a client request to restart
DHCP service via the CLI.
Web – If the address assigned by DHCP is no longer functioning, you will
not be able to renew the IP settings via the web interface. You can only
restart DHCP service via the web interface if the current address is still
available.
CLI – Enter the following command to restart DHCP service.
Console#ip dhcp restart client4-158
Console#
3-26
B
ASIC CONFIGURATION
Managing Firmware
You can upload/download firmware to or from a TFTP server, or copy
files to and from switch units in a stack. By saving runtime code to a file on
a TFTP server, that file can later be downloaded to the switch to restore
operation. You can also set the switch to use new firmware without
overwriting the previous version. You must specify the method of file
transfer, along with the file type and file names as required.
Command Attributes
• File Transfer Method – The firmware copy operation includes these
options:
- file to file – Copies a file within the switch directory, assigning it a new
name.
- file to tftp – Copies a file from the switch to a TFTP server.
- tftp to file – Copies a file from a TFTP server to the switch.
- file to unit – Copies a file from this switch to another unit in the stack.
- unit to file – Copies a file from another unit in the stack to this switch.
• TFTP Server IP Address – The IP address of a TFTP server.
• File Type – Specify opcode (operational code) to copy firmware.
• File Name –
leading letter of the file name should not be a period (.), and the
maximum length for file names on the TFTP server is 127 characters or
31 characters for files on the switch. (Valid characters: A-Z, a-z, 0-9, “.”,
“-”, “_”)
• Source/Destination Unit – Stack unit. (Range: 1 - 8)
The file name should not contain slashes (\ or /),
the
Note: Up to two copies of the system software (i.e., the runtime
firmware) can be stored in the file directory on the switch. The
currently designated startup version of this file cannot be deleted.
3-27
C
ONFIGURING THE SWITCH
Downloading System Software from a Server
When downloading runtime code, you can specify the destination file
name to replace the current image, or first download the file using a
different name from the current runtime code file, and then set the new
file as the startup file.
Web – Click System, File Management, Copy Operation. Select “tftp to
file” as the file transfer method, enter the IP address of the TFTP server,
set the file type to “opcode,” enter the file name of the software to
download, select a file on the switch to overwrite or specify a new file
name, then click Apply. If you replaced the current firmware used for
startup and want to start using the new operation code, reboot the system
via the System/Reset menu.
3-28
Figure 3-10 Copy Firmware
B
ASIC CONFIGURATION
If you download to a new destination file, go to the File Management, Set
Start-Up menu, mark the operation code file used at startup, and click
Apply. To start the new firmware, reboot the system via the System/Reset
menu.
Figure 3-11 Setting the Startup Code
To delete a file select System, File Management, Delete. Select the file
name from the given list by checking the tick box and click Apply. Note
that the file currently designated as the startup code cannot be deleted.
Figure 3-12 Deleting Files
3-29
C
ONFIGURING THE SWITCH
CLI – To download new firmware form a TFTP server, enter the IP
address of the TFTP server, select “config” as the file type, then enter the
source and destination file names. When the file has finished downloading,
set the new file to start up the system, and then restart the switch.
To start the new firmware, enter the “reload” command or reboot the
system.
Console#copy tftp file4-84
TFTP server ip address: 10.1.0.19
Choose file type:
-Write to FLASH finish.
Success.
Console#config
Console(config)#boot system opcode:V10054-90
Console(config)#exit
Console#reload4-30
Saving or Restoring Configuration Settings
You can upload/download configuration settings to/from a TFTP server,
or copy files to and from switch units in a stack. The configuration file can
be later downloaded to restore the switch’s settings.
Command Attributes
• File Transfer Method – The configuration copy operation includes these
options:
- file to file – Copies a file within the switch directory, assigning it a new
name.
- file to running-config – Copies a file in the switch to the running
configuration.
- file to startup-config – Copies a file in the switch to the startup
configuration.
- file to tftp – Copies a file from the switch to a TFTP server.
- running-config to file – Copies the running configuration to a file.
- running-config to startup-config – Copies the running config to the
startup config.
3-30
B
ASIC CONFIGURATION
- running-config to tftp – Copies the running configuration to a TFTP
server.
- startup-config to file – Copies the startup configuration to a file on the
switch.
- startup-config to running-config – Copies the startup config to the
running config.
- startup-config to tftp – Copies the startup configuration to a TFTP
server.
- tftp to file – Copies a file from a TFTP server to the switch.
- tftp to running-config – Copies a file from a TFTP server to the
running config.
- tftp to startup-config – Copies a file from a TFTP server to the startup
config.
- file to unit – Copies a file from this switch to another unit in the stack.
- unit to file – Copies a file from another unit in the stack to this switch.
• TFTP Server IP Address – The IP address of a TFTP server.
• File Type – Specify config (configuration) to copy configuration
settings.
• File Name — The configuration file name should not contain slashes
(\ or /), the leading letter of the file name should not be a period (.), and
the maximum length for file names on the TFTP server is 127 characters
or 31 characters for files on the switch. (Valid characters: A-Z, a-z, 0-9,
“.”, “-”, “_”)
• Source/Destination Unit – Stack unit. (Range: 1 - 8)
Note: The maximum number of user-defined configuration files is
limited only by available flash memory space.
3-31
C
ONFIGURING THE SWITCH
Downloading Configuration Settings from a Server
You can download the configuration file under a new file name and then
set it as the startup file, or you can specify the current startup
configuration file as the destination file to directly replace it. Note that the
file “Factory_Default_Config.cfg” can be copied to the TFTP server, but
cannot be used as the destination on the switch.
Web – Click System, File Management, Copy Operation. Choose “tftp to
startup-config” or “tftp to file,” and enter the IP address of the TFTP
server. Specify the name of the file to download, select a file on the switch
to overwrite or specify a new file name, and then click Apply.
3-32
Figure 3-13 Downloading Configuration Settings for Start-Up
B
ASIC CONFIGURATION
If you download to a new file name using “tftp to startup-config” or “tftp
to file,” the file is automatically set as the start-up configuration file. To use
the new settings, reboot the system via the System/Reset menu. You can
also select any configuration file as the start-up configuration by using the
System/File Management/Set Start-Up page.
Figure 3-14 Setting the Startup Configuration Settings
CLI – Enter the IP address of the TFTP server, specify the source file on
the server, set the startup file name on the switch, and then restart the
switch.
Console#copy tftp startup-config4-84
TFTP server ip address: 192.168.1.19
Source configuration file name: config-1
Startup configuration file name [] : startup
\Write to FLASH Programming.
-Write to FLASH finish.
Success.
Console#reload
To select another configuration file as the start-up configuration, use the
boot system command and then restart the switch.
Console#config
Console(config)#boot system config: startup4-90
Console(config)#exit
Console#reload4-30
3-33
C
ONFIGURING THE SWITCH
Console Port Settings
You can access the onboard configuration program by attaching a VT100
compatible device to the switch’s serial console port. Management access
through the console port is controlled by various parameters, including a
password, timeouts, and basic communication settings. These parameters
can be configured via the web or CLI interface.
Command Attributes
• Login Timeout – Sets the interval that the system waits for a user to log
into the CLI. If a login attempt is not detected within the timeout
interval, the connection is terminated for the session.
(Range: 0 - 300 seconds; Default: 0)
• Exec Timeout – Sets the interval that the system waits until user input
is detected. If user input is not detected within the timeout interval, the
current session is terminated. (Range: 0 - 65535 seconds; Default: 0
seconds)
• Password Threshold – Sets the password intrusion threshold, which
limits the number of failed logon attempts. When the logon attempt
threshold is reached, the system interface becomes silent for a specified
amount of time (set by the Silent Time parameter) before allowing the
next logon attempt. (Range: 0-120; Default: 3 attempts)
• Silent Time – Sets the amount of time the management console is
inaccessible after the number of unsuccessful logon attempts has been
exceeded. (Range: 0-65535; Default: 0)
• Data Bits – Sets the number of data bits per character that are
interpreted and generated by the console port. If parity is being
generated, specify 7 data bits per character. If no parity is required,
specify 8 data bits per character. (Default: 8 bits)
• Parity – Defines the generation of a parity bit. Communication
protocols provided by some terminals can require a specific parity bit
setting. Specify Even, Odd, or None. (Default: None)
• Speed – Sets the terminal line’s baud rate for transmit (to terminal) and
receive (from terminal). Set the speed to match the baud rate of the
3-34
B
ASIC CONFIGURATION
device connected to the serial port. (Range: 9600, 19200, 38400, 57600,
or 115200 baud, Auto; Default: Auto)
• Stop Bits – Sets the number of the stop bits transmitted per byte.
(Range: 1-2; Default: 1 stop bit)
• Password
2
– Specifies a password for the line connection. When a
connection is started on a line with password protection, the system
prompts for the password. If you enter the correct password, the system
shows a prompt. (Default: No password)
• Login – Enables password checking at login. You can select
authentication by a single global password as configured for the
Password parameter, or by passwords set up for specific user-name
accounts. (Default: Local)
Web – Click System, Line, Console. Specify the console port connection
parameters as required, then click Apply.
2. CLI only.
Figure 3-15 Configuring the Console Port
3-35
C
ONFIGURING THE SWITCH
CLI – Enter Line Configuration mode for the console, then specify the
connection parameters as required. To display the current console port
settings, use the show line command from the Normal Exec level.
You can access the onboard configuration program over the network using
Telnet (i.e., a virtual terminal). Management access via Telnet can be
enabled/disabled and other various parameters set, including the TCP port
number, timeouts, and a password. These parameters can be configured
via the web or CLI interface.
Command Attributes
• Telnet Status – Enables or disables Telnet access to the switch.
(Default: Enabled)
• Telnet Port Number – Sets the TCP port number for Telnet on the
switch. (Default: 23)
• Login Timeout – Sets the interval that the system waits for a user to log
into the CLI. If a login attempt is not detected within the timeout
3-36
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.