Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Trademarks used in this text: Dell, Dell OpenManage, the DELL logo, and PowerConnect are trademarks of Dell Inc. Microsoft and Windows
are registered trademarks of Microsoft Corporation.
Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products.
Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.
Understanding the Stack Topology
Stacking Failover Topology
Stacking Members and Unit ID
Removing and Replacing Stacking Members
Exchanging Stacking Members
Switching from the Stack Master to the Backup Stack Master
Features Overview
Power over Ethernet
Head of Line Blocking
Flow Control Support (IEEE 802.3X)
Back Pressure Support
Virtual Cable Testing (VCT)
MDI/MDIX Support
Auto Negotiation
MAC Address Supported Features
Layer 2 Features
VLAN Supported Features
Spanning Tree Protocol Features
Link Aggregation
Quality of Service Features
Device Management Features
Security Features
Viewing Switch Asset Information
Defining System Time Settings
Viewing System Health Information
Managing Power over Ethernet
Viewing Version Information
Managing Stack Members
Resetting the Device
Viewing RMON Statistics Group
Viewing RMON History Control Statistics
Viewing the RMON History Table
Defining Device RMON Events
Viewing the RMON Events Log
Defining RMON Device Alarms
PowerConnect 3424/3448 and PowerConnect 3424P/3448P are stackable, advanced multi-layer
devices. PowerConnect units can function either as stand-alone, multi-layer, switching devices or
stackable devices with up to six stacking members.
This
User Guide
the device.
System Description
PowerConnect 3424/3448 and PowerConnect 3424P/3448P combine versatility with minimal
management. The PowerConnect 3424 and 3448 series include the following device types:
•PowerConnect 3424
•PowerConnect 3424P
•PowerConnect 3448
•PowerConnect 3448P
PowerConnect 3424
The PowerConnect 3424 provides 24 10/100Mbps ports plus two SFP ports, and two Copper ports
which can be used to forward traffic in a stand-alone device, or as stacking ports when the device is
stacked. The device also provides one RS-232 console port. The PowerConnect 3424 is a stackable
device, but also operates as a stand-alone device.
contains the information needed for installing, configuring, and maintaining
PowerConnect 3424P
The PowerConnect 3424P provides 24 10/100Mbps ports plus two SFP ports, and two Copper ports
which can be used to forward traffic in a stand-alone device, or as stacking ports when the device is
stacked. The device also provides one RS-232 console port. The PowerConnect 3424P is a stackable
device, but also operates as a stand-alone device. The PowerConnect 3424P also provides Power
over Ethernet (PoE).
Figure 1-1. PowerConnect 3424 and PowerConnect 3424P
Introduction21
PowerConnect 3448
The PowerConnect 3448 provides 48 10/100Mbps ports plus two SFP ports, and two Copper ports
which can be used to forward traffic in a stand-alone device, or as stacking ports when the device is
stacked. The device also provides one RS-232 console port. The PowerConnect 3448 is a stackable
device, but also functions as a stand-alone device.
PowerConnect 3448P
The PowerConnect 3448P provides 48 10/100Mbps ports, two SFP ports, and two copper ports that
can be used to forward traffic when the device is in stand-alone mode, or as stacking ports when the
device is part of a stack. The device also provides one RS-232 console port. In addition,
PowerConnect 3448P provides PoE.
www.dell.com | support.dell.com
Figure 1-2. PowerConnect 3448 and PowerConnect 3448P
Stacking Overview
PowerConnect 3424/P and PowerConnect 3448/P stacking provides multiple switch management
through a single point as if all stack members are a single unit. All stack members are accessed
through a single IP address through which the stack is managed. The stack is managed from a:
•Web-based interface
•SNMP Management Station
•Command Line Interface (CLI)
PowerConnect 3424/P and PowerConnect 3448/P devices support stacking up to six units per stack,
or can operate as stand-alone units.
During the Stacking setup, one switch is selected as the Stack Master and another stacking member
can be selected as the Backup Master. All other devices are selected as stack members, and assigned
a unique Unit ID.
Switch software is downloaded separately for each stack members. However, all units in the stack
must be running the same software version.
Switch stacking and configuration is maintained by the Stack Master. The Stack Master detects
and reconfigures the ports with minimal operational impact in the event of:
•Unit Failure
•Inter-unit Stacking Link Failure
•Unit Insertion
•Removal of a Stacking Unit
22Introduction
Understanding the Stack Topology
The PowerConnect 3400 series operates in a Ring topology. A stacked Ring topology is where all
devices in the stack are connected to each other forming a circle. Each device in the stack accepts
data and sends it to the device to which it is attached. The packet continues through the stack until
it reaches its destination. The system discovers the optimal path on which to send traffic.
Figure 1-3. Stacking Ring Topology
Ring Topology
Most difficulties incurred in Ring topologies occur when a device in the ring becomes nonfunctional, or a link is severed. With the PowerConnect 3424/P and PowerConnect 3448/P stack,
the system automatically switches to a Stacking Failover topology without any system downtime.
An SNMP message is automatically generated, but no stack management action is required.
However, the stacking link or stacking member must be repaired to ensure the stacking integrity.
After the stacking issues are resolved, the device can be reconnected to the stack without
interruption, and the Ring topology is restored.
Stacking Failover Topology
If a failure occurs in the stacking topology, the stack reverts to Stacking Failover Topology. In the
Stacking Failover topology, devices operate in a chain formation. The Stack Master determines
where the packets are sent. Each unit is connected to two neighboring devices, except for the top
and bottom units.
Stacking Members and Unit ID
Stacking Unit IDs are essential to the stacking configuration. The stacking operation is determined
during the boot process. The operation mode is determined by the Unit ID selected during the
initialization process. For example, if the user selected the stand-alone mode, the device boots in
the boot-up process as a stand-alone device.
The device units are shipped with a default Unit ID of the stand-alone unit. If the device is
operating as a stand-alone unit, all stacking LEDs are off.
Introduction23
Once the user selects a different Unit ID, it is not erased, and remains valid, even if the unit is reset.
Unit ID 1 and Unit ID 2 are reserved for Master enabled units. Unit IDs 3 to 6 can be defined for
stack members.
When the Master unit boots or when inserting or removing a stack member, the Master unit
initiates a stacking discovering process.
NOTE: If two members are discovered with the same Unit ID the stack continues to function, however
only the unit with the older join time joins the stack. A message is sent to the user, notifying that a unit
failed to join the stack.
Removing and Replacing Stacking Members
www.dell.com | support.dell.com
Unit 1 and Unit 2 are Master enabled units. Unit 1 and Unit 2 are either designated as Master Unit
or Backup Master Unit. The stack Master assignment is performed during the configuration
process. One Master enabled stack member is elected as Master, and the other Master enabled
stack member is elected as Backup Master, according to the following decision process:
•If only one Stack Master enabled unit is present, it is elected as the Master.
•If two Master enabled stacking members are present, and one has been manually configured
as the Stack Master, the manually configured member is elected as Stack Master.
•If two Master enabled units are present and neither has been manually configured as the
Master, the one with the longer up-time is elected as the Stack Master.
•If two Master enabled units are present and both have been manually configured as the
Master, the one with the longer up-time is elected as the Stack Master.
•If the two Master enabled stacking members are the same age, Unit 1 is elected as the Stack
Master.
For example, Unit 2 is inserted in the first minute of a ten-minute cycle, and Unit 1 is inserted in
fifth minute of the same cycle, the units are considered to be the same age. If there are two Master
enabled stack members that are the same age, then Unit 1 is elected master.
The Stack Master and the Backup Master maintain a Warm Standby. The Warm Standby ensures
that the Backup Master takes over for the Stack Master if a failover occurs. This guarantees that the
stack continues to operate normally.
During the Warm Standby, the Master and the Backup Master are synchronized with the static
configuration only. When the Stacking Master is configured, the Stack Master must synchronize
the Stacking Backup Master. The Dynamic configuration is not saved, for example, dynamically
learned MAC addresses are not saved.
Each port in the stack has a specific Unit ID, port type, and port number, which are part of both the
configuration commands and the configuration files. Configuration files are managed only from
the device Stack Master, including:
24Introduction
NOTE: Two stacking member are considered the same age if they were inserted within a
ten minute interval.
•Saving to the FLASH
•Uploading Configuration files to an external TFTP Server
•Downloading Configuration files from an external TFTP Server
NOTE: Stack configuration for all configured ports is saved, even if the stack is reset and/or the
ports are no longer present.
Whenever a reboot occurs, topology discovery is performed, and the Master learns all units in the
stack. Unit IDs are saved in the unit and are learned through topology discovery. If a unit attempts
to boot without a selected Master, and the unit is not operating in stand-alone mode, the unit does
not boot.
Configuration files are changed only through explicit user configuration. Configuration files are
not automatically modified when:
•Units are Added
•Units are Removed
•Units are reassigned Unit IDs
•Units toggle between Stacking Mode and Stand-alone Mode
Each time the system reboots, the Startup Configuration file in the Master unit is used to
configure the stack.
If a stack member is removed from the stack, and then replaced with a unit with the same Unit ID,
the stack member is configured with the original device configuration. Only ports which are
physically present are displayed in the PowerConnect OpenManage Switch Administrator home
page, and can be configured through the web management system. Non-present ports are
configured through the CLI or SNMP interfaces.
Exchanging Stacking Members
If a stack member with the same Unit ID replaces an existing Unit ID with the same Unit ID, the
previous device configuration is applied to the inserted stack member. If the new inserted device
has either more or fewer ports than the previous device, the relevant port configuration is applied
to the new stack member. For example,
•If a PowerConnect 3424/P replaces PowerConnect 3424/P, all port configurations remain
the same.
•If a PowerConnect 3448/P replaces the PowerConnect 3448/P, all port configurations remain
the same.
•If a PowerConnect 3448/P replaces PowerConnect 3424/P, the first 3448/P 24 FE ports receive
the 3424/P 24 FE port configuration. The GE port configurations remain the same. The
remaining ports receive the default port configuration.
Figure 1-5. PowerConect 3424/P port replaces PowerConnect 3448/P port
Same
Configuration
Same
Configuration
Same
Configuration
Same
Configuration
Same
Configuration
•If a PowerConnect 3424/P replaces PowerConnect 3448/P, the PowerConnect 3424/P 24 FE
ports receives the first 24 FE PowerConnect 3448/P port configuration. The GE port
configurations remain the same.
26Introduction
Default
Configuration
Figure 1-6. PowerConnect 3448/P port replaces PowerConect 3424/P Port
Same
Configuration
Same
Configuration
Switching from the Stack Master to the Backup Stack Master
The Backup Master replaces the Stack Master if the following events occur:
•The Stack Master fails or is removed from the stack.
•Links from the Stack Master to the stacking members fails.
•A soft switchover is performed with either via web interface or the CLI.
Switching between the Stack Master and the Backup Master results in a limited service loss. Any
dynamic tables are relearned if a failure occurs. The running configuration file is synchronized
between Stack Master and the Backup Master, and continues running on the Backup Master.
Introduction27
Features Overview
This section describes the device features. For a complete list of all updated device features, see the
latest software version
Power over Ethernet
Power over Ethernet (PoE) provides power to devices over existing LAN cabling, without updating
or modifying the network infrastructure. PoE removes the need for placing network devices next to
power sources. PoE can be used in the following applications:
•IP Phones
•Wireless Access Points
www.dell.com | support.dell.com
•IP Gateways
•PDAs
•Audio and video remote monitoring
For more information about Power over Ethernet, see "Managing Power over Ethernet".
Head of Line Blocking
Head of Line (HOL) blocking results in traffic delays and frame loss caused by traffic competing
for the same egress port resources. HOL blocking queues packets, and the packets at the head of
the queue are forwarded before packets at the end of the queue.
Flow Control Support (IEEE 802.3X)
Flow control enables lower speed devices to communicate with higher speed devices, by requesting
that the higher speed device refrains from sending packets. Transmissions are temporarily halted to
prevent buffer overflows.
For information on configuring Flow Control for ports or LAGs, see "Defining Port Configuration"
or "Defining LAG Parameters."
Release Notes
.
Back Pressure Support
On half-duplex links, the receiving port prevents buffer overflows by occupying the link so that it is
unavailable for additional traffic.
For information on configuring Flow Control for ports or LAGs, see "Defining Port Configuration"
or "Defining LAG Parameters."
Virtual Cable Testing (VCT)
VCT detects and reports copper link cabling occurrences such as open cables and cable shorts. For
more information on testing cables, see "Running Cable Diagnostics".
28Introduction
MDI/MDIX Support
The device automatically detects whether the cable connected to an RJ-45 port is crossed or
straight through, when auto-negotiation is enabled.
Standard wiring for end stations is
hubs and switches is known as
For information on configuring MDI/MDIX for ports or LAGs, see "Defining Port Configuration"
or "Defining LAG Parameters."
Media-Dependent Interface
Media-Dependent Interface with Crossover
(MDI) and the standard wiring for
(MDIX).
Auto Negotiation
Auto negotiation allows the device to advertise modes of operation. The auto negotiation function
provides the means to exchange information between two devices that share a point-to-point link
segment, and to automatically configure both devices to take maximum advantage of their
transmission capabilities.
The PowerConnect 3400 series enhances auto negotiation by providing port advertisement. Port
advertisement allows the system administrator to configure the port speeds that are advertised.
For more information on auto-negotiation, see "Defining Port Configuration" or "Defining LAG
Parameters."
MAC Address Supported Features
MAC Address Capacity Support
The device supports up to 8K MAC addresses. The device reserves specific MAC addresses for
system use.
Static MAC Entries
MAC entries can be manually entered in the Bridging Table, as an alternative to learning them
from incoming frames. These user-defined entries are not subject to aging, and are preserved across
resets and reboots.
For more information, see "Defining Static Addresses."
Self-Learning MAC Addresses
The device enables automatic MAC address learning from incoming packets. The MAC addresses
are stored in the Bridging Table.
Automatic Aging for MAC Addresses
MAC addresses, from which no traffic is received for a given period, are aged out. This prevents the
Bridging Table from overflowing.
For more information on configuring the MAC Address Age Out Time, see "Viewing Dynamic
Addresses."
Introduction29
VLAN-aware MAC-based Switching
The device always performs VLAN-aware bridging. Classic bridging(IEEE802.1D) is not
performed, where frames are forwarded based only on their destination MAC address. However, a
similar functionality can be configured for untagged frames. Frames addressed to a destination
MAC address that is not associated with any port are flooded to all ports of the relevant VLAN.
MAC Multicast Support
Multicast service is a limited broadcast service, which allows one-to-many and many-to-many
connections for information distribution. Layer 2 Multicast service is where a single frame is
addressed to a specific Multicast address, from where copies of the frame are transmitted to the
relevant ports.
www.dell.com | support.dell.com
For more information, see "Assigning Multicast Forward All Parameters."
Layer 2 Features
IGMP Snooping
IGMP Snooping examines IGMP frame contents, when they are forwarded by the device from work
stations to an upstream Multicast router. From the frame, the device identifies work stations
configured for Multicast sessions, and which Multicast routers are sending Multicast frames.
For more information, see "IGMP Snooping."
Port Mirroring
Port mirroring monitors and mirrors network traffic by forwarding copies of incoming and outgoing
packets from a monitored port to a monitoring port. Users specify which target port receives copies
of all traffic passing through a specified source port.
For more information, see "Defining Port Mirroring Sessions."
Broadcast Storm Control
Storm Control enables limiting the amount of Multicast and Broadcast frames accepted and
forwarded by the device.
When Layer 2 frames are forwarded, Broadcast and Multicast frames are flooded to all ports on the
relevant VLAN. This occupies bandwidth, and loads all nodes connected on all ports.
For more information, see "Enabling Storm Control."
30Introduction
Loading...
+ 372 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.