Dell Fcx624 E Users Manual Configuration Guide
2015-02-09
: Dell Dell-Fcx624-E-Users-Manual-543953 dell-fcx624-e-users-manual-543953 dell pdf
Open the PDF directly: View PDF 
.
Page Count: 1494
| Download | |
| Open PDF In Browser | View PDF |
53-1002266-01
18 March 2011
PowerConnect B-Series FCX
Configuration Guide
Information in this document is subject to change without notice.
© 2011 Dell Inc. All rights reserved.
Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Trademarks used in this text: Dell, the DELL logo, Dell OpenManage and PowerConnect are trademarks of Dell Inc.; Microsoft,
Windows,and Windows Server are either trademarks or registered trademarks of Microsoft Corporation in the United States and/
or other countries.
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.
Regulatory Model Code: FCX624-I, FCX624-E, FCX624-S, FCX648-I, FCX648-E, FCX648-S.
Contents
About This Document
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix
Device nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix
Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xl
Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xl
Command syntax conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . xl
Notes, cautions, and danger notices . . . . . . . . . . . . . . . . . . . . . . xl
Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xli
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xli
Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xli
Contacting Dell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xli
Chapter 1
Getting Familiar with Management Applications
Using the management port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
How the management port works. . . . . . . . . . . . . . . . . . . . . . . . . 1
CLI Commands for use with the management port. . . . . . . . . . . 2
Logging on through the CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
On-line help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Command completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Scroll control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Line editing commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Using stack-unit, slot number, and port number
with CLI commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
CLI nomenclature on Stackable devices . . . . . . . . . . . . . . . . . . . 6
Searching and filtering output from CLI commands . . . . . . . . . . 6
Using special characters in regular expressions . . . . . . . . . . . . . 8
Creating an alias for a CLI command . . . . . . . . . . . . . . . . . . . . . 10
Logging on through the Web Management Interface . . . . . . . . . . . . 11
Navigating the Web Management Interface . . . . . . . . . . . . . . . 12
Logging on through Brocade Network Advisor . . . . . . . . . . . . . . . . . 16
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
iii
Chapter 2
Configuring Basic Software Features
Configuring basic system parameters . . . . . . . . . . . . . . . . . . . . . . . . 18
Entering system administration information . . . . . . . . . . . . . . . 18
Configuring Simple Network Management Protocol (SNMP)
parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Disabling Syslog messages and traps for CLI access . . . . . . . . 22
Cancelling an outbound Telnet session . . . . . . . . . . . . . . . . . . . 23
Specifying a Simple Network Time Protocol (SNTP) server. . . . 23
Setting the system clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Limiting broadcast, multicast, and unknown unicast traffic. . . 27
Configuring CLI banners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Configuring a local MAC address for Layer 2 management traffic32
Configuring basic port parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Assigning a port name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Modifying port speed and duplex mode. . . . . . . . . . . . . . . . . . . 33
Enabling auto-negotiation maximum port speed
advertisement and down-shift . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Modifying port duplex mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configuring MDI/MDIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Disabling or re-enabling a port . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Configuring flow control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Configuring symmetric flow control on PowerConnect B-Series FCX
devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Configuring PHY FIFO Rx and Tx depth. . . . . . . . . . . . . . . . . . . . 44
Configuring the IPG on PowerConnect Stackable devices . . . . 44
Enabling and disabling support for 100BaseTX . . . . . . . . . . . . 45
Enabling and disabling support for 100BaseFX . . . . . . . . . . . . 45
Changing the Gbps fiber negotiation mode . . . . . . . . . . . . . . . . 46
Modifying port priority (QoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Dynamic configuration of Voice over IP (VoIP) phones . . . . . . . 47
Configuring port flap dampening . . . . . . . . . . . . . . . . . . . . . . . . 48
Port loop detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Chapter 3
Operations, Administration, and Maintenance
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Determining the software versions installed and running on a device58
Determining the flash image version running on the device . . 58
Determining the boot image version running on the device . . . 59
Determining the image versions installed in flash memory . . . 59
Flash image verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Image file types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Viewing the contents of flash files . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Using SNMP to upgrade software . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Changing the block size for TFTP file transfers . . . . . . . . . . . . . . . . . 63
Rebooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Displaying the boot preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
iv
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Loading and saving configuration files . . . . . . . . . . . . . . . . . . . . . . . 65
Replacing the startup configuration with the running configuration
65
Replacing the running configuration with the startup configuration
66
Logging changes to the startup-config file . . . . . . . . . . . . . . . . . 66
Copying a configuration file to or from a TFTP server . . . . . . . . 66
Dynamic configuration loading . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Maximum file sizes for startup-config file and running-config . 69
Loading and saving configuration files with IPv6 . . . . . . . . . . . . . . . 69
Using the IPv6 copy command . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Copying a file from an IPv6 TFTP server. . . . . . . . . . . . . . . . . . . 70
Using the IPv6 ncopy command . . . . . . . . . . . . . . . . . . . . . . . . . 71
Uploading files from an IPv6 TFTP server . . . . . . . . . . . . . . . . . 72
Using SNMP to save and load configuration information . . . . . 73
Erasing image and configuration files . . . . . . . . . . . . . . . . . . . . 74
Scheduling a system reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Reloading at a specific time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Reloading after a specific amount of time. . . . . . . . . . . . . . . . . 75
Displaying the amount of time remaining before
a scheduled reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Canceling a scheduled reload. . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Diagnostic error codes and remedies for TFTP transfers . . . . . . . . . 75
Testing network connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Pinging an IPv4 address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Tracing an IPv4 route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Chapter 4
Software-based Licensing
Software license terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Software-based licensing overview . . . . . . . . . . . . . . . . . . . . . . . . . . 80
How software-based licensing works . . . . . . . . . . . . . . . . . . . . . 80
License types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Non-licensed features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Licensed features and part numbers . . . . . . . . . . . . . . . . . . . . . . . . 81
Licensing rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Obtaining a license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Installing a license file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Verifying the license file installation . . . . . . . . . . . . . . . . . . . . . . 88
Deleting a license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Other licensing options available from the
Brocade Software Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Viewing software license information. . . . . . . . . . . . . . . . . . . . . 89
Transferring a license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Syslog messages and trap information . . . . . . . . . . . . . . . . . . . . . . . 90
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
v
Viewing information about software licenses . . . . . . . . . . . . . . . . . . 91
Viewing the License ID (LID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Viewing the license database . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Viewing software packages installed in the device . . . . . . . . . . 93
Chapter 5
Stackable Devices
IronStack overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
IronStack technology features . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Stackable models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
IronStack terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Building an IronStack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
IronStack topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
IronStack construction methods. . . . . . . . . . . . . . . . . . . . . . . .100
Scenario 1 - Configuring a three-member IronStack
in a ring topology using secure-setup. . . . . . . . . . . . . . . . . . . .101
Scenario 2 - Configuring a three-member IronStack
in a ring topology using the automatic setup process. . . . . . .105
Scenario 3 - Configuring a three-member IronStack
in a ring topology using the manual configuration process . .108
Configuring an FCX IronStack . . . . . . . . . . . . . . . . . . . . . . . . . .109
Configuring PowerConnect B-Series FCX stacking ports. . . . .109
Configuring a default stacking port to function as
a data port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Verifying an IronStack configuration. . . . . . . . . . . . . . . . . . . . .116
Managing your IronStack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Logging in through the CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Logging in through Brocade Network Advisor . . . . . . . . . . . . .118
Logging in through the console port . . . . . . . . . . . . . . . . . . . . .118
IronStack management MAC address . . . . . . . . . . . . . . . . . . .120
Removing MAC address entries . . . . . . . . . . . . . . . . . . . . . . . .122
CLI command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
IronStack CLI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
Copying the flash image to a stack unit from
the Active Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Reloading a stack unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Controlling stack topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Managing IronStack partitioning. . . . . . . . . . . . . . . . . . . . . . . .127
MIB support for the IronStack. . . . . . . . . . . . . . . . . . . . . . . . . .128
Persistent MAC address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Unconfiguring an IronStack. . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Displaying IronStack information . . . . . . . . . . . . . . . . . . . . . . .131
Adding, removing, or replacing units in an IronStack . . . . . . . 147
Renumbering stack units . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
Syslog, SNMP, and traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151
Troubleshooting an IronStack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151
Troubleshooting an unsuccessful stack build . . . . . . . . . . . . .152
Troubleshooting image copy issues . . . . . . . . . . . . . . . . . . . . .153
Stack mismatches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154
vi
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Image mismatches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154
Advanced feature privileges (PowerConnect B-Series FCX ) . .154
Configuration mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
Memory allocation failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156
Recovering from a mismatch . . . . . . . . . . . . . . . . . . . . . . . . . .156
Troubleshooting secure-setup. . . . . . . . . . . . . . . . . . . . . . . . . .157
Troubleshooting unit replacement issues . . . . . . . . . . . . . . . .158
More about IronStack technology . . . . . . . . . . . . . . . . . . . . . . . . . .158
Configuration, startup configuration files and stacking flash.158
IronStack topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159
Port down and aging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159
Device roles and elections . . . . . . . . . . . . . . . . . . . . . . . . . . . .159
PowerConnect B-Series FCX hitless stacking . . . . . . . . . . . . . . . . .162
Supported events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
Non-supported events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
Supported protocols and services . . . . . . . . . . . . . . . . . . . . . .163
Configuration notes and feature limitations . . . . . . . . . . . . . .165
What happens during a hitless stacking switchover or
failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Standby Controller role in hitless stacking. . . . . . . . . . . . . . . .168
Support during stack formation, stack merge,
and stack split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169
Hitless stacking default behavior . . . . . . . . . . . . . . . . . . . . . . .173
Hitless stacking failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
Hitless stacking switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Displaying information about hitless stacking . . . . . . . . . . . . .183
Syslog messages for hitless stacking failover and switchover183
Displaying hitless stacking diagnostic information . . . . . . . . .184
Chapter 6
Monitoring Hardware Components
Virtual cable testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
Viewing the results of the cable analysis . . . . . . . . . . . . . . . . .190
Supported Fiber Optic Transceivers. . . . . . . . . . . . . . . . . . . . . . . . .191
Digital optical monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192
Configuration limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192
Enabling digital optical monitoring . . . . . . . . . . . . . . . . . . . . . .192
Setting the alarm interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
Displaying information about installed media . . . . . . . . . . . . .193
Viewing optical monitoring information . . . . . . . . . . . . . . . . . .194
Syslog messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196
Chapter 7
Configuring IPv6 Management on
PowerConnect B-Series FCXSwitches
IPv6 management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
IPv6 addressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
Enabling and disabling IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . .199
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
vii
IPv6 management features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199
IPv6 management ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199
IPv6 debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200
IPv6 Web management using HTTP and HTTPS . . . . . . . . . . .200
IPv6 logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201
Name-to-IPv6 address resolution using IPv6 DNS server . . . .201
Defining an IPv6 DNS entry. . . . . . . . . . . . . . . . . . . . . . . . . . . .201
IPv6 ping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202
SNTP over IPv6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203
SNMP3 over IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203
Specifying an IPv6 SNMP trap receiver . . . . . . . . . . . . . . . . . .203
Secure Shell, SCP, and IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . .204
IPv6 Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204
IPv6 traceroute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205
IPv6 management commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205
Chapter 8
Configuring Spanning Tree Protocol (STP) Related Features
STP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207
Configuring standard STP parameters. . . . . . . . . . . . . . . . . . . . . . .208
STP parameters and defaults . . . . . . . . . . . . . . . . . . . . . . . . . .208
Enabling or disabling the Spanning Tree Protocol (STP) . . . . .209
Changing STP bridge and port parameters . . . . . . . . . . . . . . .210
STP protection enhancement . . . . . . . . . . . . . . . . . . . . . . . . . .212
Displaying STP information . . . . . . . . . . . . . . . . . . . . . . . . . . . .214
Configuring STP related features . . . . . . . . . . . . . . . . . . . . . . . . . . .223
Fast port span . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223
Fast Uplink Span . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225
802.1W Rapid Spanning Tree (RSTP) . . . . . . . . . . . . . . . . . . . .227
802.1W Draft 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265
Single Spanning Tree (SSTP) . . . . . . . . . . . . . . . . . . . . . . . . . . .269
STP per VLAN group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
PVST/PVST+ compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
Overview of PVST and PVST+ . . . . . . . . . . . . . . . . . . . . . . . . . . 276
VLAN tags and dual mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277
Configuring PVST+ support . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
Displaying PVST+ support information . . . . . . . . . . . . . . . . . . .278
Configuration examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279
PVRST compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282
BPDU guard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282
Enabling BPDU protection by port. . . . . . . . . . . . . . . . . . . . . . .282
Re-enabling ports disabled by BPDU guard . . . . . . . . . . . . . . .283
Displaying the BPDU guard status . . . . . . . . . . . . . . . . . . . . . .283
Example console messages . . . . . . . . . . . . . . . . . . . . . . . . . . .284
Root guard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284
Enabling STP root guard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285
Displaying the STP root guard . . . . . . . . . . . . . . . . . . . . . . . . . .285
Displaying the root guard by VLAN . . . . . . . . . . . . . . . . . . . . . .285
viii
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Error disable recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286
Enabling error disable recovery . . . . . . . . . . . . . . . . . . . . . . . .286
Setting the recovery interval . . . . . . . . . . . . . . . . . . . . . . . . . . .286
Displaying the error disable recovery state by interface . . . . .287
Displaying the recovery state for all conditions . . . . . . . . . . . .287
Displaying the recovery state by port number and cause. . . .287
Errdisable Syslog messages . . . . . . . . . . . . . . . . . . . . . . . . . . .288
802.1s Multiple Spanning Tree Protocol . . . . . . . . . . . . . . . . . . . . .288
Multiple spanning-tree regions . . . . . . . . . . . . . . . . . . . . . . . . .288
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290
Configuring MSTP mode and scope . . . . . . . . . . . . . . . . . . . . .290
Reduced occurrences of MSTP reconvergence . . . . . . . . . . . .291
Configuring additional MSTP parameters . . . . . . . . . . . . . . . .293
Chapter 9
Configuring Basic Layer 2 Features
About port regions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306
PowerConnect B-Series FCX device port regions. . . . . . . . . . .306
Enabling or disabling the Spanning Tree Protocol (STP). . . . . . . . .306
Modifying STP bridge and port parameters . . . . . . . . . . . . . . .307
MAC learning rate control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307
Changing the MAC age time and disabling MAC address learning 307
Disabling the automatic learning of MAC addresses . . . . . . .308
Displaying the MAC address table . . . . . . . . . . . . . . . . . . . . . .308
Configuring static MAC entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308
Multi-port static MAC address. . . . . . . . . . . . . . . . . . . . . . . . . .309
Configuring VLAN-based static MAC entries . . . . . . . . . . . . . . . . . . 310
Clearing MAC address entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Flow-based MAC address learning. . . . . . . . . . . . . . . . . . . . . . . . . .311
Feature overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311
The benefits of flow-based learning . . . . . . . . . . . . . . . . . . . . .311
How flow-based learning works . . . . . . . . . . . . . . . . . . . . . . . .312
Configuration considerations . . . . . . . . . . . . . . . . . . . . . . . . . .312
Configuring flow-based MAC address learning . . . . . . . . . . . .313
Displaying information about flow-based MACs. . . . . . . . . . . . 314
Clearing flow-based MAC address entries . . . . . . . . . . . . . . . . 314
Enabling port-based VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Assigning IEEE 802.1Q tagging to a port . . . . . . . . . . . . . . . . .315
Defining MAC address filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Configuration notes and limitations . . . . . . . . . . . . . . . . . . . . . 316
Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Enabling logging of management traffic permitted by MAC address
filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318
MAC address filter override for 802.1X-enabled ports . . . . . .319
Locking a port to restrict addresses . . . . . . . . . . . . . . . . . . . . . . . .320
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320
Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
ix
Displaying and modifying system parameter default settings . . . .321
Configuration considerations . . . . . . . . . . . . . . . . . . . . . . . . . .321
Displaying system parameter default values . . . . . . . . . . . . . .321
Modifying system parameter default values . . . . . . . . . . . . . .325
TDynamic Buffer Allocation for an IronStack. . . . . . . . . . . . . . . . . .326
Generic buffer profiles on PowerConnect Stackable devices .329
Remote Fault Notification (RFN) on 1G fiber connections . . . . . . .329
Enabling and disabling remote fault notification. . . . . . . . . . .330
Link Fault Signaling (LFS) for 10G . . . . . . . . . . . . . . . . . . . . . . . . . .330
Jumbo frame support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .331
Chapter 10
Configuring Metro Features
Topology groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333
Master VLAN and member VLANs . . . . . . . . . . . . . . . . . . . . . .334
Control ports and free ports . . . . . . . . . . . . . . . . . . . . . . . . . . .334
Configuration considerations . . . . . . . . . . . . . . . . . . . . . . . . . .334
Configuring a topology group . . . . . . . . . . . . . . . . . . . . . . . . . .335
Displaying topology group information . . . . . . . . . . . . . . . . . . .336
Metro Ring Protocol (MRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .337
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339
MRP rings without shared interfaces (MRP Phase 1) . . . . . . .339
MRP rings with shared interfaces (MRP Phase 2). . . . . . . . . .340
Ring initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .341
How ring breaks are detected and healed . . . . . . . . . . . . . . . .346
Master VLANs and customer VLANs . . . . . . . . . . . . . . . . . . . . .348
Configuring MRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349
Using MRP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352
Displaying MRP information . . . . . . . . . . . . . . . . . . . . . . . . . . .353
MRP CLI example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355
Virtual Switch Redundancy Protocol (VSRP) . . . . . . . . . . . . . . . . . .357
Configuration notes and feature limitations . . . . . . . . . . . . . .358
Layer 2 and Layer 3 redundancy . . . . . . . . . . . . . . . . . . . . . . .359
Master election and failover . . . . . . . . . . . . . . . . . . . . . . . . . . .359
VSRP-Aware security features . . . . . . . . . . . . . . . . . . . . . . . . . .364
VSRP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .364
Configuring basic VSRP parameters. . . . . . . . . . . . . . . . . . . . .367
Configuring optional VSRP parameters . . . . . . . . . . . . . . . . . .368
Displaying VSRP information. . . . . . . . . . . . . . . . . . . . . . . . . . . 376
VSRP fast start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .379
VSRP and MRP signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .380
x
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Chapter 11
Configuring Uni-Directional Link Detection (UDLD) and Protected
Link Groups
UDLD overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .383
UDLD for tagged ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .384
Configuration notes and feature limitations . . . . . . . . . . . . . .384
Enabling UDLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385
Enabling UDLD for tagged ports . . . . . . . . . . . . . . . . . . . . . . . .385
Changing the Keepalive interval . . . . . . . . . . . . . . . . . . . . . . . .385
Changing the Keepalive retries . . . . . . . . . . . . . . . . . . . . . . . . .386
Displaying UDLD information . . . . . . . . . . . . . . . . . . . . . . . . . .386
Clearing UDLD statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .388
Protected link groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .388
About active ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389
Using UDLD with protected link groups . . . . . . . . . . . . . . . . . .389
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389
Creating a protected link group and assigning
an active port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390
Chapter 12
Configuring Trunk Groups and Dynamic Link Aggregation
Trunk group overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393
Trunk group connectivity to a server. . . . . . . . . . . . . . . . . . . . .394
Trunk group rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395
Trunk group configuration examples . . . . . . . . . . . . . . . . . . . .396
Support for flexible trunk group membership . . . . . . . . . . . . .398
Trunk group load sharing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .398
Configuring a trunk group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .400
CLI syntax for configuring consecutive ports in a trunk group400
CLI syntax for configuring non-consecutive ports in a trunk group401
Example 1: Configuring the trunk groups shown
in Figure 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .401
Example 2: Configuring a trunk group that spans
two Gbps Ethernet modules in a chassis device . . . . . . . . . . .402
Example 3: Configuring a multi-slot trunk group
with one port per module . . . . . . . . . . . . . . . . . . . . . . . . . . . . .403
Example 4: Configuring a trunk group of 10 Gbps
Ethernet ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .403
Additional trunking options . . . . . . . . . . . . . . . . . . . . . . . . . . . .404
Displaying trunk group configuration information . . . . . . . . . . . . .408
Viewing the first and last ports in a trunk group . . . . . . . . . . .409
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
xi
Dynamic link aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
IronStack LACP trunk group configuration example . . . . . . . . 411
Examples of valid LACP trunk groups . . . . . . . . . . . . . . . . . . . . 411
Configuration notes and limitations . . . . . . . . . . . . . . . . . . . . .412
Adaptation to trunk disappearance . . . . . . . . . . . . . . . . . . . . .413
Flexible trunk eligibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .413
Enabling dynamic link aggregation. . . . . . . . . . . . . . . . . . . . . . 414
How changing the VLAN membership of a port
affects trunk groups and dynamic keys . . . . . . . . . . . . . . . . . . 416
Additional trunking options for LACP trunk ports. . . . . . . . . . . 416
Link aggregation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Displaying and determining the status of aggregate links . . . . . . .421
Events that affect the status of ports in an aggregate link. . .422
Displaying link aggregation and port status information . . . .422
Displaying LACP status information . . . . . . . . . . . . . . . . . . . . .424
Clearing the negotiated aggregate links table . . . . . . . . . . . . . . . .425
Configuring single link LACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .425
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .425
CLI syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .425
Chapter 13
Configuring Virtual LANs (VLANs)
VLAN overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .427
Types of VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .427
Default VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .433
802.1Q tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .434
Spanning Tree Protocol (STP) . . . . . . . . . . . . . . . . . . . . . . . . . .437
Virtual routing interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .437
VLAN and virtual routing interface groups . . . . . . . . . . . . . . . .439
Dynamic, static, and excluded port membership . . . . . . . . . .439
Super aggregated VLANs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .441
Trunk group ports and VLAN membership . . . . . . . . . . . . . . . .441
Summary of VLAN configuration rules . . . . . . . . . . . . . . . . . . .442
Routing between VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .443
Virtual routing interfaces (Layer 3 Switches only) . . . . . . . . . .443
Routing between VLANs using virtual routing interfaces
(Layer 3 Switches only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .443
Dynamic port assignment (Layer 2 Switches and
Layer 3 Switches). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .444
Assigning a different VLAN ID to the default VLAN . . . . . . . . .444
Assigning different VLAN IDs to reserved VLANs
4091 and 4092 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .445
Assigning trunk group ports . . . . . . . . . . . . . . . . . . . . . . . . . . .446
Configuring port-based VLANs . . . . . . . . . . . . . . . . . . . . . . . . .446
Modifying a port-based VLAN . . . . . . . . . . . . . . . . . . . . . . . . . .450
Enable spanning tree on a VLAN . . . . . . . . . . . . . . . . . . . . . . .451
Configuring IP subnet, IPX network and
protocol-based VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .452
Configuration example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .452
xii
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring IP subnet, IPX network, and protocol-based
VLANs within port-based VLANs. . . . . . . . . . . . . . . . . . . . . . . . . . . .454
Configuring an IPv6 protocol VLAN . . . . . . . . . . . . . . . . . . . . . . . . .458
Routing between VLANs using virtual routing
interfaces (Layer 3 Switches only) . . . . . . . . . . . . . . . . . . . . . . . . . .458
Configuring protocol VLANs with dynamic ports . . . . . . . . . . . . . . .464
Aging of dynamic ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .465
Configuration guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .466
Configuring an IP, IPX, or AppleTalk Protocol
VLAN with Dynamic Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . .466
Configuring an IP subnet VLAN with dynamic ports . . . . . . . .466
Configuring an IPX network VLAN with dynamic ports . . . . . .467
Configuring uplink ports within a port-based VLAN . . . . . . . . . . . .468
Configuration considerations . . . . . . . . . . . . . . . . . . . . . . . . . .468
Configuration syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .468
Configuring the same IP subnet address on
multiple port-based VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .469
Configuring VLAN groups and virtual routing interface groups . . .472
Configuring a VLAN group . . . . . . . . . . . . . . . . . . . . . . . . . . . . .472
Configuring a virtual routing interface group . . . . . . . . . . . . . . 474
Displaying the VLAN group and virtual routing
interface group information . . . . . . . . . . . . . . . . . . . . . . . . . . .475
Allocating memory for more VLANs or virtual
routing interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Configuring super aggregated VLANs . . . . . . . . . . . . . . . . . . . . . . . 477
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .480
Configuring aggregated VLANs . . . . . . . . . . . . . . . . . . . . . . . . .480
Verifying the configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . .481
Complete CLI examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .481
Configuring 802.1Q-in-Q tagging . . . . . . . . . . . . . . . . . . . . . . . . . . .484
Configuration rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .485
Enabling 802.1Q-in-Q tagging . . . . . . . . . . . . . . . . . . . . . . . . . .485
Example configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .487
Configuring 802.1Q-in-Q tag profiles . . . . . . . . . . . . . . . . . . . .488
Configuring private VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .488
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .491
Enabling broadcast or unknown unicast traffic
to the PVLAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .495
CLI example for a general PVLAN network . . . . . . . . . . . . . . . .496
CLI example for a PVLAN network with switch-switch
link ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .496
Dual-mode VLAN ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .497
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
xiii
Displaying VLAN information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .500
Displaying VLANs in alphanumeric order . . . . . . . . . . . . . . . . .500
Displaying system-wide VLAN information . . . . . . . . . . . . . . . .501
Displaying global VLAN information . . . . . . . . . . . . . . . . . . . . .502
Displaying VLAN information for specific ports . . . . . . . . . . . .502
Displaying a port VLAN membership . . . . . . . . . . . . . . . . . . . .503
Displaying a port dual-mode VLAN membership . . . . . . . . . . .503
Displaying port default VLAN IDs (PVIDs) . . . . . . . . . . . . . . . . .503
Displaying PVLAN information. . . . . . . . . . . . . . . . . . . . . . . . . .504
Chapter 14
Configuring GARP VLAN Registration Protocol (GVRP)
GVRP overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .505
Application examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .506
Dynamic core and fixed edge . . . . . . . . . . . . . . . . . . . . . . . . . .506
Dynamic core and dynamic edge . . . . . . . . . . . . . . . . . . . . . . .507
Fixed core and dynamic edge . . . . . . . . . . . . . . . . . . . . . . . . . .508
Fixed core and fixed edge . . . . . . . . . . . . . . . . . . . . . . . . . . . . .508
VLAN names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .508
Configuration notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .508
Configuring GVRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Changing the GVRP base VLAN ID . . . . . . . . . . . . . . . . . . . . . . 510
Increasing the maximum configurable value of the Leaveall timer
510
Enabling GVRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .511
Disabling VLAN advertising . . . . . . . . . . . . . . . . . . . . . . . . . . . .511
Disabling VLAN learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .512
Changing the GVRP timers . . . . . . . . . . . . . . . . . . . . . . . . . . . .512
Converting a VLAN created by GVRP into a statically-configured VLAN514
Displaying GVRP information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Displaying GVRP configuration information . . . . . . . . . . . . . . .515
Displaying GVRP VLAN information. . . . . . . . . . . . . . . . . . . . . . 517
Displaying GVRP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . .519
Displaying CPU utilization statistics . . . . . . . . . . . . . . . . . . . . .520
Displaying GVRP diagnostic information . . . . . . . . . . . . . . . . .522
Clearing GVRP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .522
CLI examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .522
Dynamic core and fixed edge . . . . . . . . . . . . . . . . . . . . . . . . . .523
Dynamic core and dynamic edge . . . . . . . . . . . . . . . . . . . . . . .524
Fixed core and dynamic edge . . . . . . . . . . . . . . . . . . . . . . . . . .524
Fixed core and fixed edge . . . . . . . . . . . . . . . . . . . . . . . . . . . . .525
Chapter 15
Configuring MAC-based VLANs
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .527
Static and dynamic hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . .527
MAC-based VLAN feature structure . . . . . . . . . . . . . . . . . . . . .527
Dynamic MAC-based VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .528
xiv
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuration notes and feature limitations . . . . . . . . . . . . . . . . . .529
Configuration example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .530
Configuring MAC-based VLANs. . . . . . . . . . . . . . . . . . . . . . . . . . . . .531
Using MAC-based VLANs and 802.1X security on the same port531
Configuring generic and Dell vendor-specific attributes on the
RADIUS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .532
Aging for MAC-based VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . .533
Disabling aging for MAC-based VLAN sessions . . . . . . . . . . . .534
Configuring the maximum MAC addresses per port . . . . . . . .535
Configuring a MAC-based VLAN for a static host . . . . . . . . . . .535
Configuring MAC-based VLAN for a dynamic host . . . . . . . . . .536
Configuring dynamic MAC-based VLAN . . . . . . . . . . . . . . . . . .536
Configuring MAC-based VLANs using SNMP . . . . . . . . . . . . . . . . . .537
Displaying Information about MAC-based VLANs . . . . . . . . . . . . . .537
Displaying the MAC-VLAN table. . . . . . . . . . . . . . . . . . . . . . . . .537
Displaying the MAC-VLAN table for a specific MAC address . .537
Displaying allowed MAC addresses . . . . . . . . . . . . . . . . . . . . .538
Displaying denied MAC addresses . . . . . . . . . . . . . . . . . . . . . .538
Displaying detailed MAC-VLAN data . . . . . . . . . . . . . . . . . . . . .539
Displaying MAC-VLAN information for a specific interface . . .541
Displaying MAC addresses in a MAC-based VLAN . . . . . . . . . .542
Displaying MAC-based VLAN logging . . . . . . . . . . . . . . . . . . . .543
Clearing MAC-VLAN information . . . . . . . . . . . . . . . . . . . . . . . . . . . .543
Sample application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .543
Chapter 16
Configuring Rule-Based IP Access Control Lists (ACLs)
ACL overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .548
Types of IP ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .548
ACL IDs and entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .548
Numbered and named ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . .549
Default ACL action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .549
How hardware-based ACLs work . . . . . . . . . . . . . . . . . . . . . . . . . . .550
How fragmented packets are processed . . . . . . . . . . . . . . . . .550
Hardware aging of Layer 4 CAM entries . . . . . . . . . . . . . . . . . .550
Configuration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .550
Configuring standard numbered ACLs. . . . . . . . . . . . . . . . . . . . . . .551
Standard numbered ACL syntax . . . . . . . . . . . . . . . . . . . . . . . .551
Configuration example for standard numbered ACLs . . . . . . .553
Configuring standard named ACLs . . . . . . . . . . . . . . . . . . . . . . . . .553
Standard named ACL syntax . . . . . . . . . . . . . . . . . . . . . . . . . . .554
Configuration example for standard named ACLs . . . . . . . . . .555
Configuring extended numbered ACLs . . . . . . . . . . . . . . . . . . . . . .556
Extended numbered ACL syntax . . . . . . . . . . . . . . . . . . . . . . . .556
Configuration examples for extended numbered ACLs . . . . . .560
Configuring extended named ACLs . . . . . . . . . . . . . . . . . . . . . . . . .562
Extended named ACL syntax . . . . . . . . . . . . . . . . . . . . . . . . . . .562
Configuration example for extended named ACLs. . . . . . . . . .566
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
xv
Preserving user input for ACL TCP/UDP port numbers. . . . . . . . . .566
Managing ACL comment text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .567
Adding a comment to an entry in a numbered ACL . . . . . . . . .567
Adding a comment to an entry in a named ACL. . . . . . . . . . . .568
Deleting a comment from an ACL entry . . . . . . . . . . . . . . . . . .568
Viewing comments in an ACL . . . . . . . . . . . . . . . . . . . . . . . . . .568
Applying an ACL to a virtual interface in a protocolor subnet-based VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .569
Enabling ACL logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .570
Enabling strict control of ACL filtering of fragmented packets. . . .572
Enabling ACL support for switched traffic in the router image . . .573
Enabling ACL filtering based on VLAN membership or VE port
membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .573
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Applying an IPv4 ACL to specific VLAN members on
a port (Layer 2 devices only) . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Applying an IPv4 ACL to a subset of ports on a virtual
interface (Layer 3 devices only) . . . . . . . . . . . . . . . . . . . . . . . .575
Using ACLs to filter ARP packets . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Configuration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Configuring ACLs for ARP filtering . . . . . . . . . . . . . . . . . . . . . . . 576
Displaying ACL filters for ARP . . . . . . . . . . . . . . . . . . . . . . . . . .577
Clearing the filter count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .578
Filtering on IP precedence and ToS values . . . . . . . . . . . . . . . . . . .578
TCP flags - edge port security . . . . . . . . . . . . . . . . . . . . . . . . . .578
QoS options for IP ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .579
Configuration notes for PowerConnect B-Series FCX devices.579
Using an IP ACL to mark DSCP values (DSCP marking). . . . . .580
DSCP matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .581
ACL-based rate limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .582
ACL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .582
Using ACLs to control multicast features. . . . . . . . . . . . . . . . . . . . .582
Enabling and viewing hardware usage statistics for an ACL . . . . .582
Displaying ACL information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .583
Troubleshooting ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .583
Policy-based routing (PBR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .584
Chapter 17
Configuring Quality of Service
Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .591
Processing of classified traffic . . . . . . . . . . . . . . . . . . . . . . . . .591
xvi
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
QoS for stackable devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .595
QoS profile restrictions in an IronStack . . . . . . . . . . . . . . . . . .595
QoS behavior for trusting Layer 2 (802.1p) in an IronStack . .595
QoS behavior for trusting Layer 3 (DSCP) in an IronStack . . .595
QoS behavior on port priority and VLAN priority
in an IronStack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .596
QoS behavior for 802.1p marking in an IronStack . . . . . . . . .596
QoS queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .596
Assigning QoS priorities to traffic. . . . . . . . . . . . . . . . . . . . . . . . . . .596
Changing a port priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .597
Assigning static MAC entries to priority queues. . . . . . . . . . . .597
Buffer allocation/threshold for QoS queues . . . . . . . . . . . . . .598
802.1p priority override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .598
Configuration notes and feature limitations . . . . . . . . . . . . . .598
Enabling 802.1p priority override . . . . . . . . . . . . . . . . . . . . . . .598
Marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .599
Configuring DSCP-based QoS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .599
Application notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .599
Using ACLs to honor DSCP-based QoS . . . . . . . . . . . . . . . . . . .599
Configuring the QoS mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . .600
Default DSCP to internal forwarding priority mappings. . . . . .600
Changing the DSCP to internal forwarding
priority mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .601
Changing the VLAN priority 802.1p to hardware
forwarding queue mappings . . . . . . . . . . . . . . . . . . . . . . . . . . .602
8 to 4 queue mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .602
Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .603
QoS queuing methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .603
Selecting the QoS queuing method . . . . . . . . . . . . . . . . . . . . .605
Configuring the QoS queues . . . . . . . . . . . . . . . . . . . . . . . . . . .605
Viewing QoS settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .608
Viewing DSCP-based QoS settings . . . . . . . . . . . . . . . . . . . . . . . . . .608
Chapter 18
Configuring Traffic Policies
Traffic policies overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .611
Configuration notes and feature limitations . . . . . . . . . . . . . . . . . .612
Maximum number of traffic policies supported on a device . . . . .612
Setting the maximum number of traffic policies
supported on a Layer 3 device . . . . . . . . . . . . . . . . . . . . . . . . .613
ACL-based rate limiting using traffic policies. . . . . . . . . . . . . . . . . .613
Support for fixed rate limiting and adaptive rate limiting . . . .614
Configuring ACL-based fixed rate limiting . . . . . . . . . . . . . . . . .614
Configuring ACL-based adaptive rate limiting . . . . . . . . . . . . .615
Specifying the action to be taken for packets that are
over the limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
xvii
ACL statistics and rate limit counting . . . . . . . . . . . . . . . . . . . . . . .619
Enabling ACL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .619
Enabling ACL statistics with rate limiting traffic policies. . . . .620
Viewing ACL and rate limit counters . . . . . . . . . . . . . . . . . . . . .620
Clearing ACL and rate limit counters . . . . . . . . . . . . . . . . . . . .621
Viewing traffic policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .622
Chapter 19
Configuring Base Layer 3 and Enabling Routing Protocols
Adding a static IP route. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .623
Adding a static ARP entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .624
Modifying and displaying layer 3 system parameter limits . . . . . .625
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .625
PowerConnect IPv6 models . . . . . . . . . . . . . . . . . . . . . . . . . . .625
Displaying Layer 3 system parameter limits . . . . . . . . . . . . . .625
Configuring RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .626
Enabling RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .627
Enabling redistribution of IP static routes into RIP . . . . . . . . .627
Enabling redistribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .628
Enabling learning of default routes . . . . . . . . . . . . . . . . . . . . .629
Changing the route loop prevention method . . . . . . . . . . . . . .629
Other layer 3 protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .629
Enabling or disabling routing protocols . . . . . . . . . . . . . . . . . . . . . .629
Enabling or disabling layer 2 switching . . . . . . . . . . . . . . . . . . . . . .630
Configuration Notes and Feature Limitations . . . . . . . . . . . . .630
Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .630
Chapter 20
Configuring Port Mirroring and Monitoring
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .633
Configuring port mirroring and monitoring . . . . . . . . . . . . . . . . . . .633
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .634
Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .635
Configuring mirroring on an Ironstack . . . . . . . . . . . . . . . . . . . . . . .637
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .637
ACL-based inbound mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .638
Creating an ACL-based inbound mirror clause for PowerConnect BSeries FCX devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .638
MAC address filter-based mirroring . . . . . . . . . . . . . . . . . . . . . . . . .638
Configuring MAC address filter-based mirroring . . . . . . . . . . .638
VLAN-based mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .639
Chapter 21
Configuring Rate Limiting and Rate Shaping on
PowerConnect B-Series FCX Switches
Rate limiting overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .643
xviii
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Rate limiting in hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .644
How Fixed rate limiting works . . . . . . . . . . . . . . . . . . . . . . . . . .644
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .645
Configuring a port-based rate limiting policy . . . . . . . . . . . . . .645
Configuring an ACL-based rate limiting policy . . . . . . . . . . . . .645
Displaying the fixed rate limiting configuration . . . . . . . . . . . .645
Rate shaping overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .646
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .646
Configuring outbound rate shaping for a port . . . . . . . . . . . . .647
Configuring outbound rate shaping for a specific priority . . . .647
Configuring outbound rate shaping for a trunk port . . . . . . . .647
Displaying rate shaping configurations . . . . . . . . . . . . . . . . . .648
Chapter 22
Configuring IP Multicast Traffic Reduction for
PowerConnect B-Series FCX Switches
IGMP snooping overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .649
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .651
Configuring queriers and non-queriers. . . . . . . . . . . . . . . . . . .652
VLAN specific configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .653
Using IGMPv2 with IGMPv3. . . . . . . . . . . . . . . . . . . . . . . . . . . .653
PIM SM traffic snooping overview . . . . . . . . . . . . . . . . . . . . . . . . . .653
Application example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .653
Configuring IGMP snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .655
Displaying IGMP snooping information . . . . . . . . . . . . . . . . . . . . . .663
Displaying querier information . . . . . . . . . . . . . . . . . . . . . . . . .668
Clear IGMP snooping commands . . . . . . . . . . . . . . . . . . . . . . . 671
Chapter 23
Enabling the Foundry Discovery Protocol (FDP) and Reading Cisco
Discovery Protocol (CDP) Packets
Using FDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .673
Configuring FDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .673
Displaying FDP information . . . . . . . . . . . . . . . . . . . . . . . . . . . .675
Clearing FDP and CDP information. . . . . . . . . . . . . . . . . . . . . .677
Reading CDP packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .678
Enabling interception of CDP packets globally . . . . . . . . . . . .678
Enabling interception of CDP packets on an interface . . . . . .679
Displaying CDP information. . . . . . . . . . . . . . . . . . . . . . . . . . . .679
Clearing CDP information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .681
Chapter 24
Configuring LLDP and LLDP-MED
Terms used in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .684
LLDP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .684
Benefits of LLDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .685
LLDP-MED overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .686
Benefits of LLDP-MED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .686
LLDP-MED class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .687
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
xix
General operating principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .687
Operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .687
LLDP packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .688
TLV support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .689
MIB support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .692
Syslog messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .692
Configuring LLDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .692
Configuration notes and considerations . . . . . . . . . . . . . . . . .693
Enabling and disabling LLDP. . . . . . . . . . . . . . . . . . . . . . . . . . .693
Enabling support for tagged LLDP packets . . . . . . . . . . . . . . .694
Changing a port LLDP operating mode . . . . . . . . . . . . . . . . . .694
Specifying the maximum number of LLDP neighbors . . . . . . .696
Enabling LLDP SNMP notifications and syslog messages . . .697
Changing the minimum time between LLDP transmissions . .698
Changing the interval between regular LLDP transmissions .698
Changing the holdtime multiplier for transmit TTL . . . . . . . . .699
Changing the minimum time between port reinitializations . .699
LLDP TLVs advertised by the Dell PowerConnect device. . . . .699
Configuring LLDP-MED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .707
Enabling LLDP-MED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .708
Enabling SNMP notifications and syslog messages
for LLDP-MED topology changes. . . . . . . . . . . . . . . . . . . . . . . .708
Changing the fast start repeat count . . . . . . . . . . . . . . . . . . . .708
Defining a location id. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .709
Defining an LLDP-MED network policy . . . . . . . . . . . . . . . . . . . 715
LLDP-MED attributes advertised by the Dell PowerConnect device717
Displaying LLDP statistics and configuration settings. . . . . . . 718
LLDP configuration summary . . . . . . . . . . . . . . . . . . . . . . . . . . 719
LLDP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
LLDP neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .721
LLDP neighbors detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .722
LLDP configuration details . . . . . . . . . . . . . . . . . . . . . . . . . . . .723
Resetting LLDP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .725
Clearing cached LLDP neighbor information. . . . . . . . . . . . . . . . . .725
Chapter 25
Configuring IP Multicast Protocols
Overview of IP multicasting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .727
IPv4 multicast group addresses . . . . . . . . . . . . . . . . . . . . . . . .728
Mapping of IPv4 Multicast group addresses to
Ethernet MAC addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .728
Supported Layer 3 multicast routing protocols . . . . . . . . . . . .728
Suppression of unregistered multicast packets . . . . . . . . . . .729
Multicast terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .729
Changing global IP multicast parameters . . . . . . . . . . . . . . . . . . . .729
Changing dynamic memory allocation for IP
multicast groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .729
Changing IGMP V1 and V2 parameters . . . . . . . . . . . . . . . . . .731
Adding an interface to a multicast group . . . . . . . . . . . . . . . . . . . .732
xx
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
PIM Dense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .733
Initiating PIM multicasts on a network . . . . . . . . . . . . . . . . . . .734
Pruning a multicast tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .734
Grafts to a multicast Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . .736
PIM DM versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .736
Configuring PIM DM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .737
Failover time in a multi-path topology . . . . . . . . . . . . . . . . . . . 741
Modifying the TTL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
PIM Sparse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
PIM Sparse switch types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
RP paths and SPT paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
Configuring PIM Sparse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
Displaying PIM Sparse configuration information
and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .750
PIM Passive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .762
Passive multicast route insertion. . . . . . . . . . . . . . . . . . . . . . . . . . .763
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring an IP tunnel763
Using ACLs to control multicast features. . . . . . . . . . . . . . . . . . . . .764
Using ACLs to limit static RP groups . . . . . . . . . . . . . . . . . . . . .764
Using ACLs to limit PIM RP candidate advertisement . . . . . . .766
Disabling CPU processing for select multicast groups . . . . . . . . . .767
CLI command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .768
Viewing disabled multicast addresses . . . . . . . . . . . . . . . . . . .768
Displaying the multicast configuration for
another multicast router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .769
IGMP V3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .770
Default IGMP version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
Compatibility with IGMP V1 and V2 . . . . . . . . . . . . . . . . . . . . . 771
Globally enabling the IGMP version . . . . . . . . . . . . . . . . . . . . . 771
Enabling the IGMP version per interface setting . . . . . . . . . . . 771
Enabling the IGMP version on a physical port within
a virtual routing interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . .772
Enabling membership tracking and fast leave . . . . . . . . . . . .772
Setting the query interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . .773
Setting the group membership time. . . . . . . . . . . . . . . . . . . . .773
Setting the maximum response time . . . . . . . . . . . . . . . . . . . .773
IGMP V3 and source specific multicast protocols . . . . . . . . . . 774
Displaying IGMP V3 information on Layer 3 Switches. . . . . . . 774
Clearing IGMP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .778
IGMP Proxy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .778
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .778
Configuring IGMP Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .779
Displaying IGMP Proxy traffic . . . . . . . . . . . . . . . . . . . . . . . . . .779
IP multicast protocols and IGMP snooping on the same device . .779
Configuration example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .780
CLI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .781
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
xxi
Chapter 26
Configuring IP
Basic configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .784
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .784
Full Layer 3 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .784
IP interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .785
IP packet flow through a Layer 3 Switch. . . . . . . . . . . . . . . . . .785
IP route exchange protocols . . . . . . . . . . . . . . . . . . . . . . . . . . .790
IP multicast protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .790
IP interface redundancy protocols . . . . . . . . . . . . . . . . . . . . . .791
Access Control Lists and IP access policies. . . . . . . . . . . . . . .791
Basic IP parameters and defaults – Layer 3 Switches . . . . . . . . . .791
When parameter changes take effect . . . . . . . . . . . . . . . . . . .792
IP global parameters – Layer 3 Switches. . . . . . . . . . . . . . . . .792
IP interface parameters – Layer 3 Switches . . . . . . . . . . . . . .796
Basic IP parameters and defaults – Layer 2 Switches . . . . . . . . . .797
IP global parameters – Layer 2 Switches. . . . . . . . . . . . . . . . .797
Interface IP parameters – Layer 2 Switches . . . . . . . . . . . . . .799
Configuring IP parameters – Layer 3 Switches . . . . . . . . . . . . . . . .799
Configuring IP addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .799
Configuring Domain Name Server (DNS) resolver. . . . . . . . . .803
Configuring packet parameters . . . . . . . . . . . . . . . . . . . . . . . .806
Changing the router ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .809
Configuring ARP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . .810
Configuring forwarding parameters . . . . . . . . . . . . . . . . . . . . .815
Disabling ICMP messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
Disabling ICMP Redirect Messages . . . . . . . . . . . . . . . . . . . . .819
Configuring static routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .819
Configuring a default network route . . . . . . . . . . . . . . . . . . . . .828
Configuring IP load sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . .829
Configuring IRDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .832
Configuring RARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .834
Configuring UDP broadcast and IP helper parameters . . . . . .836
Configuring BootP/DHCP relay parameters . . . . . . . . . . . . . . .839
DHCP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .841
Displaying DHCP server information. . . . . . . . . . . . . . . . . . . . .851
DHCP Client-Based Auto-Configuration and Flash
image update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .854
Configuring IP parameters – Layer 2 Switches . . . . . . . . . . . . . . . .862
Configuring the management IP address and specifying
the default gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .863
Configuring Domain Name Server (DNS) resolver. . . . . . . . . .863
Changing the TTL threshold . . . . . . . . . . . . . . . . . . . . . . . . . . .865
Configuring DHCP Assist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .865
Displaying IP configuration information and statistics . . . . . . . . . .869
Changing the network mask display to prefix format . . . . . . .869
Displaying IP information – Layer 3 Switches . . . . . . . . . . . . .869
Displaying IP information – Layer 2 Switches . . . . . . . . . . . . .883
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .887
xxii
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Chapter 27
Configuring Multicast Listening Discovery (MLD) Snooping on
PowerConnect B-Series FCX Switches
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .889
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .891
Configuring queriers and non-queriers. . . . . . . . . . . . . . . . . . .892
VLAN specific configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .892
Using MLDv1 with MLDv2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .892
Configuring MLD snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .893
Configuring the hardware and software resource limits . . . . .893
Disabling transmission and receipt of MLD packets on a port894
Configuring the global MLD mode . . . . . . . . . . . . . . . . . . . . . .894
Modifying the age interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . .894
Modifying the query interval (Active MLD snooping mode only)895
Configuring the global MLD version . . . . . . . . . . . . . . . . . . . . .895
Configuring report control . . . . . . . . . . . . . . . . . . . . . . . . . . . . .895
Modifying the wait time before stopping traffic when receiving a
leave message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .896
Modifying the multicast cache (mcache) aging time. . . . . . . .896
Disabling error and warning messages . . . . . . . . . . . . . . . . . .896
Configuring the MLD mode for a VLAN . . . . . . . . . . . . . . . . . . .896
Disabling MLD snooping for the VLAN . . . . . . . . . . . . . . . . . . .897
Configuring the MLD version for the VLAN . . . . . . . . . . . . . . . .897
Configuring the MLD version for individual ports . . . . . . . . . .897
Configuring static groups to the entire VLAN or to individual ports
897
Configuring static router ports . . . . . . . . . . . . . . . . . . . . . . . . .898
Turning off static group proxy . . . . . . . . . . . . . . . . . . . . . . . . . .898
Enabling MLDv2 membership tracking and fast leave for the VLAN
898
Configuring fast leave for MLDv1 . . . . . . . . . . . . . . . . . . . . . . .899
Enabling fast convergence . . . . . . . . . . . . . . . . . . . . . . . . . . . .899
Displaying MLD snooping information . . . . . . . . . . . . . . . . . . .900
Clear MLD snooping commands. . . . . . . . . . . . . . . . . . . . . . . .904
Chapter 28
Configuring RIP (IPv4)
RIP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .907
ICMP host unreachable message for undeliverable ARPs . . .908
RIP parameters and defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .908
RIP global parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .908
RIP interface parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .909
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
xxiii
Configuring RIP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .910
Enabling RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .910
Configuring metric parameters . . . . . . . . . . . . . . . . . . . . . . . . .910
Changing the administrative distance. . . . . . . . . . . . . . . . . . .911
Configuring redistribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . .912
Configuring route learning and advertising parameters . . . . .914
Changing the route loop prevention method . . . . . . . . . . . . . .915
Suppressing RIP route advertisement on a VRRP or
VRRPE backup interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .916
Configuring RIP route filters . . . . . . . . . . . . . . . . . . . . . . . . . . .916
Displaying RIP filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
Displaying CPU utilization statistics . . . . . . . . . . . . . . . . . . . . . . . . .918
Chapter 29
Configuring OSPF Version 2 (IPv4)
Overview of OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .922
OSPF point-to-point links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .923
Designated routers in multi-access networks . . . . . . . . . . . . .924
Designated router election in multi-access networks . . . . . . .924
OSPF RFC 1583 and 2178 compliance . . . . . . . . . . . . . . . . . .925
Reduction of equivalent AS External LSAs . . . . . . . . . . . . . . . .926
Support for OSPF RFC 2328 Appendix E . . . . . . . . . . . . . . . . .928
Dynamic OSPF activation and configuration . . . . . . . . . . . . . .929
Dynamic OSPF memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .930
OSPF graceful restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .930
xxiv
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .930
Configuration rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .931
OSPF parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .931
Enabling OSPF on the router . . . . . . . . . . . . . . . . . . . . . . . . . . .932
Assigning OSPF areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .933
Assigning an area range (optional) . . . . . . . . . . . . . . . . . . . . . .937
Assigning interfaces to an area . . . . . . . . . . . . . . . . . . . . . . . .937
Modifying interface defaults . . . . . . . . . . . . . . . . . . . . . . . . . . .937
Changing the timer for OSPF authentication changes . . . . . .940
Block flooding of outbound LSAs on specific OSPF interfaces941
Configuring an OSPF non-broadcast interface. . . . . . . . . . . . .941
Assigning virtual links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .942
Modifying virtual link parameters . . . . . . . . . . . . . . . . . . . . . . .944
Changing the reference bandwidth for the cost on OSPF interfaces
946
Defining redistribution filters . . . . . . . . . . . . . . . . . . . . . . . . . .947
Preventing specific OSPF routes from being installed in the IP route
table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .950
Modifying the default metric for redistribution . . . . . . . . . . . .953
Enabling route redistribution. . . . . . . . . . . . . . . . . . . . . . . . . . .953
Disabling or re-enabling load sharing. . . . . . . . . . . . . . . . . . . .955
Configuring external route summarization . . . . . . . . . . . . . . . .956
Configuring default route origination . . . . . . . . . . . . . . . . . . . .957
Modifying SPF timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .958
Modifying the redistribution metric type . . . . . . . . . . . . . . . . .959
Modifying the administrative distance . . . . . . . . . . . . . . . . . . .959
Configuring OSPF group Link State Advertisement
(LSA) pacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .960
Modifying OSPF traps generated . . . . . . . . . . . . . . . . . . . . . . .961
Specifying the types of OSPF Syslog messages to log . . . . . .962
Modifying the OSPF standard compliance setting. . . . . . . . . .962
Modifying the exit overflow interval . . . . . . . . . . . . . . . . . . . . .962
Configuring an OSPF point-to-point link . . . . . . . . . . . . . . . . . .963
Configuring OSPF graceful restart . . . . . . . . . . . . . . . . . . . . . .963
Clearing OSPF information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .964
Clearing OSPF neighbor information . . . . . . . . . . . . . . . . . . . .965
Clearing OSPF topology information . . . . . . . . . . . . . . . . . . . . .965
Clearing redistributed routes from the OSPF routing table . . .965
Clearing information for OSPF areas . . . . . . . . . . . . . . . . . . . .966
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
xxv
Displaying OSPF information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .966
Displaying general OSPF configuration information . . . . . . . .967
Displaying CPU utilization statistics . . . . . . . . . . . . . . . . . . . . .968
Displaying OSPF area information . . . . . . . . . . . . . . . . . . . . . .969
Displaying OSPF neighbor information . . . . . . . . . . . . . . . . . . .969
Displaying OSPF interface information. . . . . . . . . . . . . . . . . . . 971
Displaying OSPF route information . . . . . . . . . . . . . . . . . . . . . .973
Displaying OSPF external link state information . . . . . . . . . . .975
Displaying OSPF link state information . . . . . . . . . . . . . . . . . . 976
Displaying the data in an LSA . . . . . . . . . . . . . . . . . . . . . . . . . . 976
Displaying OSPF virtual neighbor information . . . . . . . . . . . . . 977
Displaying OSPF virtual link information . . . . . . . . . . . . . . . . . 977
Displaying OSPF ABR and ASBR information . . . . . . . . . . . . . . 977
Displaying OSPF trap status . . . . . . . . . . . . . . . . . . . . . . . . . . .978
Displaying OSPF graceful restart information . . . . . . . . . . . . .978
Chapter 30
Configuring BGP4 (IPv4)
Overview of BGP4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .982
Relationship between the BGP4 route table and
the IP route table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .982
How BGP4 selects a path for a route . . . . . . . . . . . . . . . . . . . .983
BGP4 message types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .985
BGP4 graceful restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .987
Basic configuration and activation for BGP4 . . . . . . . . . . . . . . . . .987
Note regarding disabling BGP4. . . . . . . . . . . . . . . . . . . . . . . . .988
BGP4 parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .988
When parameter changes take effect . . . . . . . . . . . . . . . . . . .989
Memory considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .991
Memory configuration options obsoleted by
dynamic memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .991
Basic configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .992
Enabling BGP4 on the router . . . . . . . . . . . . . . . . . . . . . . . . . .992
Changing the router ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .992
Setting the local AS number . . . . . . . . . . . . . . . . . . . . . . . . . . .993
Adding a loopback interface . . . . . . . . . . . . . . . . . . . . . . . . . . .993
Adding BGP4 neighbors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .993
Adding a BGP4 peer group . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
xxvi
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Optional configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
Changing the Keep Alive Time and Hold Time . . . . . . . . . . . 1004
Changing the BGP4 next-hop update timer . . . . . . . . . . . . . 1005
Enabling fast external fallover. . . . . . . . . . . . . . . . . . . . . . . . 1005
Changing the maximum number of paths for
BGP4 load sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
Customizing BGP4 load sharing . . . . . . . . . . . . . . . . . . . . . . .1007
Specifying a list of networks to advertise. . . . . . . . . . . . . . . 1008
Changing the default local preference . . . . . . . . . . . . . . . . . 1009
Using the IP default route as a valid next hop for
a BGP4 route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1010
Advertising the default route. . . . . . . . . . . . . . . . . . . . . . . . . .1010
Changing the default MED (Metric) used for
route redistribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1010
Enabling next-hop recursion . . . . . . . . . . . . . . . . . . . . . . . . . .1011
Changing administrative distances . . . . . . . . . . . . . . . . . . . .1014
Requiring the first AS to be the neighbor AS . . . . . . . . . . . . .1015
Disabling or re-enabling comparison of the AS-Path length .1015
Enabling or disabling comparison of the router IDs . . . . . . .1016
Configuring the Layer 3 Switch to always compare
Multi-Exit Discriminators (MEDs) . . . . . . . . . . . . . . . . . . . . . .1016
Treating missing MEDs as the worst MEDs . . . . . . . . . . . . . .1017
Configuring route reflection parameters . . . . . . . . . . . . . . . .1017
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1021
Aggregating routes advertised to BGP4 neighbors . . . . . . . .1024
Configuring BGP4 graceful restart . . . . . . . . . . . . . . . . . . . . . . . . 1025
Configuring BGP4 graceful restart . . . . . . . . . . . . . . . . . . . . 1025
Configuring timers for BGP4 graceful restart (optional) . . . 1025
BGP null0 routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026
Configuration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1027
Configuration examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028
Show commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
Modifying redistribution parameters . . . . . . . . . . . . . . . . . . . . . . 1030
Redistributing connected routes. . . . . . . . . . . . . . . . . . . . . . .1031
Redistributing RIP routes. . . . . . . . . . . . . . . . . . . . . . . . . . . . .1031
Redistributing OSPF external routes. . . . . . . . . . . . . . . . . . . .1031
Redistributing static routes . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
Disabling or re-enabling re-advertisement of all learned
BGP4 routes to all BGP4 neighbors . . . . . . . . . . . . . . . . . . . 1032
Redistributing IBGP routes into RIP and OSPF. . . . . . . . . . . 1033
Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
Filtering specific IP addresses . . . . . . . . . . . . . . . . . . . . . . . 1033
Filtering AS-paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035
Filtering communities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038
Defining IP prefix lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1041
Defining neighbor distribute lists . . . . . . . . . . . . . . . . . . . . . 1042
Defining route maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
Using a table map to set the rag value. . . . . . . . . . . . . . . . . 1050
Configuring cooperative BGP4 route filtering. . . . . . . . . . . . .1051
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
xxvii
Configuring route flap dampening . . . . . . . . . . . . . . . . . . . . . . . . 1054
Globally configuring route flap dampening . . . . . . . . . . . . . 1055
Using a route map to configure route flap dampening
for specific routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055
Using a route map to configure route flap dampening for
a specific neighbor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056
Removing route dampening from a route. . . . . . . . . . . . . . . .1057
Removing route dampening from a neighbor routes
suppressed due to aggregation . . . . . . . . . . . . . . . . . . . . . . .1057
Displaying and clearing route flap dampening statistics . . 1059
Generating traps for BGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1060
Displaying BGP4 information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1061
Displaying summary BGP4 information . . . . . . . . . . . . . . . . .1061
Displaying the active BGP4 configuration . . . . . . . . . . . . . . 1064
Displaying CPU utilization statistics . . . . . . . . . . . . . . . . . . . 1064
Displaying summary neighbor information . . . . . . . . . . . . . 1066
Displaying BGP4 neighbor information. . . . . . . . . . . . . . . . . 1067
Displaying peer group information . . . . . . . . . . . . . . . . . . . . .1078
Displaying summary route information . . . . . . . . . . . . . . . . .1079
Displaying the BGP4 route table . . . . . . . . . . . . . . . . . . . . . . 1080
Displaying BGP4 route-attribute entries . . . . . . . . . . . . . . . . 1086
Displaying the routes BGP4 has placed in the
IP route table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1087
Displaying route flap dampening statistics . . . . . . . . . . . . . 1088
Displaying the active route map configuration . . . . . . . . . . 1089
Displaying BGP4 graceful restart neighbor information . . . 1090
Updating route information and resetting a neighbor session . 1090
Using soft reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . .1091
Dynamically requesting a route refresh from
a BGP4 neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093
Closing or resetting a neighbor session . . . . . . . . . . . . . . . . 1096
Clearing and resetting BGP4 routes in the IP route table . . .1097
Clearing traffic counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1097
Clearing route flap dampening statistics. . . . . . . . . . . . . . . . . . . 1098
Removing route flap dampening . . . . . . . . . . . . . . . . . . . . . . . . . 1098
Clearing diagnostic buffers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1098
Chapter 31
Configuring VRRP and VRRPE
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1101
Overview of VRRP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1102
Overview of VRRPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1106
Configuration note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109
Comparison of VRRP and VRRPE . . . . . . . . . . . . . . . . . . . . . . . . .
VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VRRPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Architectural differences . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1109
1109
1109
1109
VRRP and VRRPE parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .1110
xxviii
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic VRRP parameters . . . . . . . . . . . . . . . . . . . . . .
Configuring the Owner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring a Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration rules for VRRP. . . . . . . . . . . . . . . . . . . . . . . . .
1113
1113
1113
1113
Configuring basic VRRPE parameters . . . . . . . . . . . . . . . . . . . . . 1113
Configuration rules for VRRPE . . . . . . . . . . . . . . . . . . . . . . . .1114
Note regarding disabling VRRP or VRRPE . . . . . . . . . . . . . . . . . . .1114
Configuring additional VRRP and VRRPE parameters . . . . . . . . .1114
Forcing a Master router to abdicate to a standby router . . . . . . 1121
Displaying VRRP and VRRPE information . . . . . . . . . . . . . . . . . .
Displaying summary information . . . . . . . . . . . . . . . . . . . . .
Displaying detailed information . . . . . . . . . . . . . . . . . . . . . .
Displaying statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Clearing VRRP or VRRPE statistics . . . . . . . . . . . . . . . . . . . .
Displaying CPU utilization statistics . . . . . . . . . . . . . . . . . . .
1122
1122
1123
1128
1130
1130
Configuration examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1131
VRRP example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1131
VRRPE example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1132
Chapter 32
Securing Access to Management Functions
Securing access methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135
Restricting remote access to management functions . . . . . . . . .1137
Using ACLs to restrict remote access . . . . . . . . . . . . . . . . . . 1138
Defining the console idle time . . . . . . . . . . . . . . . . . . . . . . . 1140
Restricting remote access to the device to
specific IP addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1141
Restricting access to the device based on IP or
MAC address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142
Defining the Telnet idle time . . . . . . . . . . . . . . . . . . . . . . . . . 1143
Changing the login timeout period for Telnet sessions . . . . 1143
Specifying the maximum number of login attempts
for Telnet access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144
Changing the login timeout period for Telnet sessions . . . . 1144
Restricting remote access to the device to
specific VLAN IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144
Designated VLAN for Telnet management sessions
to a Layer 2 Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145
Device management security . . . . . . . . . . . . . . . . . . . . . . . . 1146
Disabling specific access methods. . . . . . . . . . . . . . . . . . . . 1148
Setting passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting a Telnet password . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting passwords for management privilege levels . . . . . .
Recovering from a lost password . . . . . . . . . . . . . . . . . . . . .
Displaying the SNMP community string . . . . . . . . . . . . . . . .
Disabling password encryption . . . . . . . . . . . . . . . . . . . . . . .
Specifying a minimum password length. . . . . . . . . . . . . . . .
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
1149
1149
1150
1152
1153
1153
1153
xxix
Setting up local user accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . 1154
Enhancements to username and password . . . . . . . . . . . . 1154
Configuring a local user account . . . . . . . . . . . . . . . . . . . . . 1158
Create password option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1160
Changing a local user password . . . . . . . . . . . . . . . . . . . . . . .1161
Configuring SSL security for the Web Management Interface . . .1161
Enabling the SSL server on the Dell PowerConnect device .1161
Changing the SSL server certificate key size . . . . . . . . . . . . 1162
Support for SSL digital certificates larger than 2048 bytes 1162
Importing digital certificates and RSA private key files. . . . 1162
Generating an SSL certificate . . . . . . . . . . . . . . . . . . . . . . . . 1163
Configuring TACACS/TACACS+ security . . . . . . . . . . . . . . . . . . . . 1163
How TACACS+ differs from TACACS . . . . . . . . . . . . . . . . . . . . 1164
TACACS/TACACS+ authentication, authorization,
and accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164
TACACS authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1166
TACACS/TACACS+ configuration considerations . . . . . . . . . 1169
Enabling TACACS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1170
Identifying the TACACS/TACACS+ servers. . . . . . . . . . . . . . . .1170
Specifying different servers for individual AAA functions . . .1171
Setting optional TACACS/TACACS+ parameters . . . . . . . . . . .1172
Configuring authentication-method lists for
TACACS/TACACS+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1173
Configuring TACACS+ authorization . . . . . . . . . . . . . . . . . . . .1175
Configuring TACACS+ accounting . . . . . . . . . . . . . . . . . . . . . .1178
Configuring an interface as the source for all
TACACS/TACACS+ packets. . . . . . . . . . . . . . . . . . . . . . . . . . . .1179
Displaying TACACS/TACACS+ statistics and
configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . 1180
Configuring RADIUS security . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1181
RADIUS authentication, authorization, and accounting . . . 1181
RADIUS configuration considerations. . . . . . . . . . . . . . . . . . 1184
RADIUS configuration procedure . . . . . . . . . . . . . . . . . . . . . 1185
Configuring Dell-specific attributes on the
RADIUS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1185
Enabling SNMP to configure RADIUS . . . . . . . . . . . . . . . . . . .1187
Identifying the RADIUS server to the Dell PowerConnect device1188
Specifying different servers for individual AAA functions . . 1188
Configuring a RADIUS server per port . . . . . . . . . . . . . . . . . 1189
Mapping a RADIUS server to individual ports . . . . . . . . . . . 1190
Setting RADIUS parameters . . . . . . . . . . . . . . . . . . . . . . . . . 1190
Configuring authentication-method lists for RADIUS. . . . . . 1192
Configuring RADIUS authorization . . . . . . . . . . . . . . . . . . . . 1194
Configuring RADIUS accounting . . . . . . . . . . . . . . . . . . . . . . 1195
Configuring an interface as the source for all
RADIUS packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196
Displaying RADIUS configuration information . . . . . . . . . . . 1196
Configuring authentication-method lists . . . . . . . . . . . . . . . . . . . 1198
Configuration considerations for authenticationmethod lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1199
Examples of authentication-method lists. . . . . . . . . . . . . . . 1199
xxx
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
TCP Flags - edge port security . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201
Using TCP Flags in combination with other ACL features . . 1202
Chapter 33
Configuring SSH2 and SCP
SSH version 2 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tested SSH2 clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unsupported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1203
1204
1204
1204
AES encryption for SSH2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205
Configuring SSH2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recreating SSH keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generating a host key pair . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring DSA challenge-response authentication . . . . .
1205
1206
1206
1207
Setting optional parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1209
Setting the number of SSH authentication retries . . . . . . . .1210
Deactivating user authentication . . . . . . . . . . . . . . . . . . . . . .1210
Enabling empty password logins. . . . . . . . . . . . . . . . . . . . . . .1210
Setting the SSH port number . . . . . . . . . . . . . . . . . . . . . . . . 1211
Setting the SSH login timeout value . . . . . . . . . . . . . . . . . . . 1211
Designating an interface as the source for all SSH packets 1211
Configuring the maximum idle time for SSH sessions . . . . 1211
Filtering SSH access using ACLs . . . . . . . . . . . . . . . . . . . . . . . . . 1212
Terminating an active SSH connection . . . . . . . . . . . . . . . . . . . . 1212
Displaying SSH connection information . . . . . . . . . . . . . . . . . . . 1212
Using Secure copy with SSH2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213
Enabling and disabling SCP . . . . . . . . . . . . . . . . . . . . . . . . . 1213
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1214
Example file transfers using SCP . . . . . . . . . . . . . . . . . . . . . .1214
Chapter 34
Configuring 802.1X Port Security
IETF RFC support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1217
How 802.1X port security works . . . . . . . . . . . . . . . . . . . . . . . . .
Device roles in an 802.1X configuration . . . . . . . . . . . . . . .
Communication between the devices . . . . . . . . . . . . . . . . .
Controlled and uncontrolled ports . . . . . . . . . . . . . . . . . . . .
Message exchange during authentication . . . . . . . . . . . . . .
Authenticating multiple hosts connected to the same port
802.1X port security and sFlow . . . . . . . . . . . . . . . . . . . . . .
802.1X accounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
1218
1218
1219
1219
1220
1223
1226
1226
xxxi
Configuring 802.1X port security . . . . . . . . . . . . . . . . . . . . . . . . . 1227
Configuring an authentication method list for 802.1X . . . . 1227
Setting RADIUS parameters . . . . . . . . . . . . . . . . . . . . . . . . . 1228
Configuring dynamic VLAN assignment for 802.1X ports . . 1230
Dynamically applying IP ACLs and MAC address filters
to 802.1X ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234
Enabling 802.1X port security. . . . . . . . . . . . . . . . . . . . . . . . 1237
Setting the port control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1238
Configuring periodic re-authentication . . . . . . . . . . . . . . . . . 1239
Re-authenticating a port manually . . . . . . . . . . . . . . . . . . . . 1239
Setting the quiet period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1240
Specifying the wait interval and number of EAP-request/
identity frame retransmissions from the Dell PowerConnect device
1240
Specifying the wait interval and number of EAP-request/
identity frame retransmissions from the RADIUS server . . .1241
Specifying a timeout for retransmission of messages
to the authentication server . . . . . . . . . . . . . . . . . . . . . . . . . 1242
Initializing 802.1X on a port . . . . . . . . . . . . . . . . . . . . . . . . . 1242
Allowing access to multiple hosts . . . . . . . . . . . . . . . . . . . . . 1242
Defining MAC address filters for EAP frames. . . . . . . . . . . . 1245
Configuring VLAN access for non-EAP-capable clients . . . . 1245
Configuring 802.1X accounting . . . . . . . . . . . . . . . . . . . . . . . . . . 1246
802.1X Accounting attributes for RADIUS . . . . . . . . . . . . . . 1246
Enabling 802.1X accounting . . . . . . . . . . . . . . . . . . . . . . . . . .1247
Displaying 802.1X information. . . . . . . . . . . . . . . . . . . . . . . . . . . .1247
Displaying 802.1X configuration information . . . . . . . . . . . .1247
Displaying 802.1X statistics . . . . . . . . . . . . . . . . . . . . . . . . . 1250
Clearing 802.1X statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 1251
Displaying dynamically assigned VLAN information . . . . . . 1251
Displaying information about dynamically applied
MAC address filters and IP ACLs . . . . . . . . . . . . . . . . . . . . . . 1252
Displaying 802.1X multiple-host authentication information1255
Sample 802.1X configurations. . . . . . . . . . . . . . . . . . . . . . . . . . .
Point-to-point configuration. . . . . . . . . . . . . . . . . . . . . . . . . .
Hub configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
802.1X Authentication with dynamic VLAN assignment . . .
1258
1259
1260
1261
Using multi-device port authentication and 802.1X
security on the same port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1262
Chapter 35
Using the MAC Port Security Feature
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1263
Local and global resources . . . . . . . . . . . . . . . . . . . . . . . . . . 1264
Configuration notes and feature limitations . . . . . . . . . . . . 1264
xxxii
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring the MAC port security feature . . . . . . . . . . . . . . . . .
Enabling the MAC port security feature . . . . . . . . . . . . . . . .
Setting the maximum number of secure MAC addresses
for an interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the port security age timer . . . . . . . . . . . . . . . . . . . .
Specifying secure MAC addresses . . . . . . . . . . . . . . . . . . . .
Autosaving secure MAC addresses to the
startup-config file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying the action taken when a security
violation occurs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1264
1265
1265
1265
1266
1266
1267
Clearing port security statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 1268
Clearing restricted MAC addresses. . . . . . . . . . . . . . . . . . . . 1268
Clearing violation statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 1268
Displaying port security information . . . . . . . . . . . . . . . . . . . . . . 1268
Displaying port security settings . . . . . . . . . . . . . . . . . . . . . . 1269
Displaying the secure MAC addresses . . . . . . . . . . . . . . . . . 1269
Displaying port security statistics . . . . . . . . . . . . . . . . . . . . . 1270
Displaying restricted MAC addresses on a port . . . . . . . . . . .1271
Chapter 36
Configuring Multi-Device Port Authentication
How multi-device port authentication works. . . . . . . . . . . . . . . . .1274
RADIUS authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1274
Authentication-failure actions . . . . . . . . . . . . . . . . . . . . . . . . .1274
Supported RADIUS attributes . . . . . . . . . . . . . . . . . . . . . . . . 1275
Support for dynamic VLAN assignment . . . . . . . . . . . . . . . . 1275
Support for dynamic ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . 1275
Support for authenticating multiple MAC addresses
on an interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1275
Support for source guard protection. . . . . . . . . . . . . . . . . . . .1276
Using multi-device port authentication and 802.1X
security on the same port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1276
Configuring Dell-specific attributes on the
RADIUS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1277
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
xxxiii
Configuring multi-device port authentication . . . . . . . . . . . . . . .
Enabling multi-device port authentication . . . . . . . . . . . . . .
Specifying the format of the MAC addresses sent to the
RADIUS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying the authentication-failure action . . . . . . . . . . . .
Generating traps for multi-device port authentication . . . .
Defining MAC address filters. . . . . . . . . . . . . . . . . . . . . . . . .
Configuring dynamic VLAN assignment . . . . . . . . . . . . . . . .
Dynamically applying IP ACLs to authenticated
MAC addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling source guard protection . . . . . . . . . . . . . . . . . . . . .
Clearing authenticated MAC addresses . . . . . . . . . . . . . . . .
Disabling aging for authenticated MAC addresses . . . . . . .
Changing the hardware aging period for blocked
MAC addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying the aging time for blocked MAC addresses . . . .
Specifying the RADIUS timeout action . . . . . . . . . . . . . . . . .
Multi-device port authentication password override . . . . . .
Limiting the number of authenticated MAC addresses. . . .
1278
1278
1279
1279
1280
1280
1280
1283
1286
1287
1288
1288
1289
1289
1291
1291
Displaying multi-device port authentication information . . . . . . 1291
Displaying authenticated MAC address information . . . . . . 1292
Displaying multi-device port authentication
configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . 1292
Displaying multi-device port authentication information
for a specific MAC address or port . . . . . . . . . . . . . . . . . . . . 1293
Displaying the authenticated MAC addresses . . . . . . . . . . . 1294
Displaying the non-authenticated MAC addresses . . . . . . . 1294
Displaying multi-device port authentication information
for a port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1295
Displaying multi-device port authentication settings
and authenticated MAC addresses . . . . . . . . . . . . . . . . . . . 1295
Displaying the MAC authentication table for PowerConnect B-Series
FCX devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1298
Example configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299
Multi-device port authentication with dynamic
VLAN assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1300
Examples of multi-device port authentication and 802.1X
authentication configuration on the same port. . . . . . . . . . 1302
Chapter 37
Configuring Web Authentication
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1307
Configuration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1308
Configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1309
Enabling and disabling web authentication . . . . . . . . . . . . . . . . .1311
Configuring the web authentication mode . . . . . . . . . . . . . . . . . .1311
Using local user databases . . . . . . . . . . . . . . . . . . . . . . . . . . 1312
Using passcodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1315
Using automatic authentication . . . . . . . . . . . . . . . . . . . . . . 1320
xxxiv
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Chapter 38
Configuring web authentication options . . . . . . . . . . . . . . . . . . .
Enabling RADIUS accounting for web authentication . . . . .
Changing the login mode (HTTPS or HTTP) . . . . . . . . . . . . .
Specifying trusted ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying hosts that are permanently authenticated . . . .
Configuring the re-authentication period . . . . . . . . . . . . . . .
Defining the web authentication cycle . . . . . . . . . . . . . . . . .
Limiting the number of web authentication attempts. . . . .
Clearing authenticated hosts from the web
authentication table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting and clearing the block duration for web
authentication attempts . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manually blocking and unblocking a specific host . . . . . . .
Limiting the number of authenticated hosts . . . . . . . . . . . .
Filtering DNS queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Forcing re-authentication when ports are down . . . . . . . . .
Forcing re-authentication after an inactive period . . . . . . .
Defining the web authorization redirect address . . . . . . . .
Deleting a web authentication VLAN . . . . . . . . . . . . . . . . . .
Web authentication pages . . . . . . . . . . . . . . . . . . . . . . . . . .
1320
1320
1321
1321
1321
1322
1322
1322
Displaying web authentication information. . . . . . . . . . . . . . . . .
Displaying the web authentication configuration . . . . . . . .
Displaying a list of authenticated hosts . . . . . . . . . . . . . . . .
Displaying a list of hosts attempting to authenticate . . . . .
Displaying a list of blocked hosts . . . . . . . . . . . . . . . . . . . . .
Displaying a list of local user databases . . . . . . . . . . . . . . .
Displaying a list of users in a local user database . . . . . . .
Displaying passcodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1333
1333
1335
1336
1336
1337
1337
1338
1323
1323
1323
1324
1324
1324
1325
1325
1326
1326
Protecting Against Denial of Service Attacks
Protecting against Smurf attacks. . . . . . . . . . . . . . . . . . . . . . . . . 1339
Avoiding being an intermediary in a Smurf attack. . . . . . . . 1340
Avoiding being a victim in a Smurf attack . . . . . . . . . . . . . . 1340
Protecting against TCP SYN attacks. . . . . . . . . . . . . . . . . . . . . . . .1341
TCP security enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . 1342
Displaying statistics about packets dropped
because of DoS attacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1343
Chapter 39
Inspecting and Tracking DHCP Packets
Dynamic ARP inspection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1345
ARP poisoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1345
How DAI works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346
Configuration notes and feature limitations . . . . . . . . . . . . .1347
Configuring DAI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1347
Displaying ARP inspection status and ports . . . . . . . . . . . . 1349
Displaying the ARP table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1349
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
xxxv
DHCP snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1349
How DHCP snooping works . . . . . . . . . . . . . . . . . . . . . . . . . . 1350
System reboot and the binding database . . . . . . . . . . . . . . .1351
Configuration notes and feature limitations . . . . . . . . . . . . .1351
Configuring DHCP snooping . . . . . . . . . . . . . . . . . . . . . . . . . .1351
Clearing the DHCP binding database . . . . . . . . . . . . . . . . . . 1352
Displaying DHCP snooping status and ports . . . . . . . . . . . . 1353
Displaying the DHCP snooping binding database . . . . . . . . 1353
Displaying DHCP binding entry and status. . . . . . . . . . . . . . 1353
DHCP snooping configuration example . . . . . . . . . . . . . . . . 1353
Chapter 40
DHCP relay agent information (DHCP Option 82) . . . . . . . . . . . .
Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DHCP Option 82 sub-options . . . . . . . . . . . . . . . . . . . . . . . .
Configuring DHCP option 82 . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing information about DHCP option 82 processing . . .
1354
1355
1355
1357
1359
IP source guard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration notes and feature limitations . . . . . . . . . . . .
Enabling IP source guard on a port . . . . . . . . . . . . . . . . . . .
Defining static IP source bindings . . . . . . . . . . . . . . . . . . . .
Enabling IP source guard per-port-per-VLAN . . . . . . . . . . . .
Enabling IP source guard on a VE . . . . . . . . . . . . . . . . . . . . .
Displaying learned IP addresses. . . . . . . . . . . . . . . . . . . . . .
1360
1361
1362
1362
1363
1363
1363
Securing SNMP Access
SNMP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1365
Establishing SNMP community strings . . . . . . . . . . . . . . . . . . . .
Encryption of SNMP community strings . . . . . . . . . . . . . . . .
Adding an SNMP community string . . . . . . . . . . . . . . . . . . .
Displaying the SNMP community strings . . . . . . . . . . . . . . .
1366
1366
1366
1368
Using the user-based security model. . . . . . . . . . . . . . . . . . . . . . 1369
Configuring your NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1369
Configuring SNMP version 3 on Dell PowerConnect devices1369
Defining the engine id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1370
Defining an SNMP group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1370
Defining an SNMP user account. . . . . . . . . . . . . . . . . . . . . . .1371
Defining SNMP views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1373
SNMP version 3 traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1374
Defining an SNMP group and specifying which
view is notified of traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1374
Defining the UDP port for SNMP v3 traps . . . . . . . . . . . . . . 1375
Trap MIB changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1375
Specifying an IPv6 host as an SNMP trap receiver . . . . . . . .1376
SNMP v3 over IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1376
Specifying an IPv6 host as an SNMP trap receiver . . . . . . . .1376
Viewing IPv6 SNMP server addresses . . . . . . . . . . . . . . . . . .1376
xxxvi
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Displaying SNMP Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . .1377
Displaying the Engine ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1377
Displaying SNMP groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1377
Displaying user information. . . . . . . . . . . . . . . . . . . . . . . . . . 1378
Interpreting varbinds in report packets . . . . . . . . . . . . . . . . 1378
SNMP v3 Configuration examples . . . . . . . . . . . . . . . . . . . . . . . . 1379
Simple SNMP v3 configuration . . . . . . . . . . . . . . . . . . . . . . . 1379
More detailed SNMP v3 configuration . . . . . . . . . . . . . . . . . 1379
Chapter 41
Using Syslog
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1381
Displaying Syslog messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling real-time display of Syslog messages . . . . . . . . . .
Enabling real-time display for a Telnet or SSH session . . . .
Show log on all terminals . . . . . . . . . . . . . . . . . . . . . . . . . . .
1382
1383
1383
1383
Configuring the Syslog service . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying the Syslog configuration . . . . . . . . . . . . . . . . . . .
Disabling or re-enabling Syslog. . . . . . . . . . . . . . . . . . . . . . .
Specifying a Syslog server. . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying an additional Syslog server . . . . . . . . . . . . . . . . .
Disabling logging of a message level . . . . . . . . . . . . . . . . . .
Changing the number of entries the local buffer can hold .
Changing the log facility . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Interface names in Syslog messages. . . . . . . . .
Displaying TCP or UDP port numbers in Syslog messages .
Retaining Syslog messages after a soft reboot . . . . . . . . . .
Clearing the Syslog messages from the local buffer . . . . . .
1383
1384
1387
1388
1388
1388
1389
1389
1390
1390
1391
1391
Syslog messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1391
Appendix A
Network Monitoring
Basic management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1417
Viewing system information . . . . . . . . . . . . . . . . . . . . . . . . . . 1417
Viewing configuration information . . . . . . . . . . . . . . . . . . . . .1418
Viewing port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1419
Viewing STP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1421
Clearing statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1421
Viewing egress queue counters on PowerConnect B-Series FCX
devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1422
RMON support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1423
Maximum number of entries allowed in the
RMON control table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1423
Statistics (RMON group 1). . . . . . . . . . . . . . . . . . . . . . . . . . . .1424
History (RMON group 2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1426
Alarm (RMON group 3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1426
Event (RMON group 9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1426
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
xxxvii
sFlow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1427
sFlow version 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1427
sFlow support for IPv6 packets. . . . . . . . . . . . . . . . . . . . . . . 1428
Configuration considerations . . . . . . . . . . . . . . . . . . . . . . . . 1429
Configuring and enabling sFlow . . . . . . . . . . . . . . . . . . . . . . 1430
Configuring sFlow version 5 features . . . . . . . . . . . . . . . . . . 1436
Displaying sFlow information . . . . . . . . . . . . . . . . . . . . . . . . 1439
Configuring a utilization list for an uplink port . . . . . . . . . . . . . . 1442
Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1443
Displaying utilization percentages for an uplink . . . . . . . . . 1443
Appendix B
Software Specifications
IEEE compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1445
RFC support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1445
Internet drafts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1452
xxxviii
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
About This Document
Introduction
This guide describes the following product families from Dell:
• PowerConnect B-Series FCX Stackable Switches.
This guide includes procedures for configuring the software. The software procedures show how to
perform tasks using the CLI. This guide also describes how to monitor Dell products using statistics
and summary screens.
This guide applies to the PowerConnect models listed in Table 1.
Device nomenclature
Table 1 lists the terms (product names) contained in this guide and the specific set of devices to
which each term refers.
TABLE 1
PowerConnect family of switches
This name
Refers to these devices
PowerConnect Stackable Devices
NOTE: The PowerConnect Stackable Devices include the PowerConnect B-Series FCX devices.
PowerConnect B-Series FCX
PowerConnect B-FCX624s,PowerConnect B-FCX648s,PowerConnect B-FCX624-E,
PowerConnect B-FCX624-I, PowerConnect B-FCX648-E, PowerConnect B-FCX648-I
NOTE: All PowerConnect B-Series FCX devices can be ordered from the factory as
-ADV models. ADV models include support for Layer 3 BGP. PowerConnect B-FCXE
and PowerConnect B-FCXI models require an optional SFP+ module to support
stacking.
Audience
This document is designed for system administrators with a working knowledge of Layer 2 and
Layer 3 switching and routing.
If you are using a Layer 3 Switch, you should be familiar with the following protocols if applicable to
your network – IP, RIP, OSPF, BGP, ISIS, IGMP, PIM, DVMRP, and VRRP.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
xxxix
Document conventions
This section describes text formatting conventions and important notice formats used in this
document.
Text formatting
The narrative-text formatting conventions that are used are as follows:
bold text
Identifies command names
Identifies the names of user-manipulated GUI elements
Identifies keywords
Identifies text to enter at the GUI or CLI
italic text
Provides emphasis
Identifies variables
Identifies document titles
code text
Identifies CLI output
For readability, command names in the narrative portions of this guide are presented in bold:
for example, show version.
Command syntax conventions
Command syntax in this manual follows these conventions:
TABLE 2
Command syntax conventions
Convention
Description
bold face font
Commands and keywords.
italic
Variables for which you supply values.
[]
Keywords or arguments that appear within square brackets are
optional.
{x | y | z}
A choice of required keywords appears in braces separated by vertical
bars. You must select one.
screen font
Examples of information displayed on the screen.
<>
Nonprinting characters, for example passwords, appear in angle
brackets
[]
Default responses to system prompts appear in square brackets.
Notes, cautions, and danger notices
The following notices and statements are used in this manual. They are listed below in order of
increasing severity of potential hazards.
xl
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
NOTE
A note provides a tip, guidance or advice, emphasizes important information, or provides a
reference to related information.
CAUTION
A Caution statement alerts you to situations that can be potentially hazardous to you or
cause damage to hardware, firmware, software, or data.
DANGER
A Danger statement indicates conditions or situations that can be potentially lethal or
extremely hazardous to you. Safety labels are also attached directly to products to warn of
these conditions or situations.
Notice to the reader
This document may contain references to the trademarks of the following corporations. These
trademarks are the properties of their respective companies and corporations.
Related publications
The following Dell documents supplement the information in this guide:
• PowerConnect B-FCX Switch Hardware Installation Guide
• PowerConnect B-MLXe MIB Reference
• PowerConnect B-Series FCX Web Management Interface User Guide
NOTE
For the latest edition of these documents, which contain the most up-to-date information, refer
to support.dell.com.
Getting technical help
Dell is committed to ensuring that your investment in our products remains cost-effective. If
you need assistance, or find errors in the manuals, contact Dell Technical Support.
Contacting Dell
For customers in the United States, call 800-WWW.DELL (800.999.3355).
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
xli
NOTE
If you do not have an active Internet connection, you can find contact information on your
purchase invoice, packing slip, bill, or Dell product catalog.
Dell provides several online and telephone-based support and service options. Availability
varies by country and product, and some services may not be available in your area. To contact
Dell for sales, technical support, or customer service issues:
1. Visit http://support.dell.com.
2. Click your country or region at the bottom of the page. For a full listing of countries and
regions, click All.
3. In the Support menu, click All Support.
Choose the method of contacting Dell that is convenient for you.
xlii
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Chapter
Getting Familiar with Management Applications
1
Table 3 lists the individual Dell PowerConnect switches and the management application features
they support.
TABLE 3
16
Supported management application features
Feature
PowerConnect B-Series FCX
Management port
Yes
industry-standard Command Line
Interface (CLI), including support for:
• Serial and Telnet access
• Alias command
• On-line help
• Command completion
• Scroll control
• Line editing
• Searching and filtering output
• Special characters
Yes
Web-based GUI
• Web Management Interface
Yes
Brocade Network Advisor
Yes
Using the management port
NOTE
The management port applies to PowerConnect B-Series FCX devices.
The management port is an out-of-band port that customers can use to manage their devices
without interfering with the in-band ports. The management port is widely used to download
images and configurations, for Telnet sessions, and for Web management.
For PowerConnect B-Series FCX devices, the MAC address for the management port is derived from
the base MAC address of the unit, plus the number of ports in the base module. For example, on a
48-port PowerConnect B-Series FCX standalone device, the base MAC address is
0000.1234.2200. The management port MAC address for this device would be 0000.1234.2200
plus 0x30, or 0000.1234.2230. The 0x30 in this case equals the 48 ports on the base module.
How the management port works
The following rules apply to management ports:
• Only packets that are specifically addressed to the management port MAC address or the
broadcast MAC address are processed by the Layer 2 or Layer 3 switch. All other packets are
filtered out.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
1
1
Using the management port
• No packet received on a management port is sent to any in-band ports, and no packets
received on in-band ports are sent to a management port.
•
•
•
•
A management port is not part of any VLAN
Protocols are not supported on the management port.
Creating a management VLAN disables the management port on the device.
For PowerConnect B-Series FCX devices, all features that can be configured from the global
configuration mode can also be configured from the interface level of the management port.
Features that are configured through the management port take effect globally, not on the
management port itself.
For switches, any in-band port may be used for management purposes. A router sends Layer 3
packets using the MAC address of the port as the source MAC address.
For stacking devices, (for example, an PowerConnect B-Series FCX stack) each stack unit has one
out-of band management port. Only the management port on the Active Controller will actively send
and receive packets. If a new Active Controller is elected, the new Active Controller management
port will become the active management port. In this situation, the MAC address of the old Active
Controller and the MAC address of the new controller will be different.
CLI Commands for use with the management port
The following CLI commands can be used with a management port.
To display the current configuration, use the show running-config interface management
command.
Syntax: show running-config interface management
PowerConnect(config-if-mgmt)#ip addr 10.44.9.64/24
PowerConnect(config)#show running-config interface management 1
interface management 1
ip address 10.44.9/64 255.255.255.0
To display the current configuration, use the show interfaces management command.
Syntax: show interfaces management
PowerConnect(config)#show interfaces management 1
GigEthernetmgmt1 is up, line protocol is up
Hardware is GigEthernet, address is 0000.9876.544a (bia 0000.9876.544a)
Configured speed auto, actual 1Gbit, configured duplex fdx, actual fdx
Configured mdi mode AUTO, actual none
BPRU guard is disabled, ROOT protect is disabled
Link Error Dampening is Disabled
STP configured to OFF, priority is level0, mac-learning is enabled
Flow Control is config disabled, oper enabled
Mirror disabled, Monitor disabled
Not member of any active trunks
Not member of any configured trunks
No port name
IPG MII 0 bits-time, IPG GMII 0 bits-time
IP MTU 1500 bytes
300 second input rate: 83728 bits/sec, 130 packets/sec, 0.01% utilization
300 second output rate: 24 bits/sec, 0 packets/sec, 0.00% utilization
39926 packets input, 3210077 bytes, 0 no buffer
Received 4353 broadcasts, 32503 multicasts, 370 unicasts
0 input errors, 0 CRC, 0 frame, 0 ignored
0 runts, 0 giants
2
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
1
Logging on through the CLI
22 packets output, 1540 bytres, 0 underruns
Transmitted 0 broadcasts, 6 multicasts, 16 unicasts
0 output errors, 0 collisions
To display the management interface information in brief form, enter the show interfaces brief
management command.
Syntax: show interfaces brief management
PowerConnect(config)#show interfaces brief management 1
Port
Link
State
Dupl Speed Trunk
Tag
Pri
mgmt1 Up
None
Full 1G
None
No
0
MAC
0000.9876.544a
Name
To display management port statistics, enter the show statistics management command.
Syntax: show statistics management
PowerConnect(config)#show statistics management 1
Port
Link
State
Dupl Speed Trunk
Tag
mgmt1 Up
None
Full 1G
None
No
Port mgmt1 Counters:
InOctets
InPkts
InBroadcastPkts
InMultiastPkts
InUnicastPkts
InBadPkts
InFragments
InDiscards
CRC
InErrors
InGiantPkts
InShortPkts
InJabber
InFlowCtrlPkts
InBitsPerSec
InPktsPerSec
InUtilization
3210941
39939
4355
35214
370
0
0
0
0
0
0
0
0
0
83728
130
0.01%
Pri
0
MAC
0000.9876.544a
OutOctets
OutPackets
OutbroadcastPkts
OutMulticastPkts
OutUnicastPkts
1540
22
0
6
16
OutErrors
Collisions
LateCollisions
0
0
0
OutFlowCtrlPkts
OutBitsPerSec
OutPktsPerSec
OutUtilization
0
24
0
0.00%
Name
To display the management interface statistics in brief form, enter the show statistics brief
management command.
Syntax: show statistics brief management
PowerConnect(config)#show statistics brief management 1
Port
In Packets Out PacketsTrunk
In Errors
Out Errors
mgmt1
39946
22
0
0
Total
39945
22
0
0
Logging on through the CLI
Once an IP address is assigned to a Dell PowerConnect device running Layer 2 software or to an
interface on the Dell PowerConnect device running Layer 3 software, you can access the CLI either
through the direct serial connection to the device or through a local or remote Telnet session.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
3
1
Logging on through the CLI
You can initiate a local Telnet or SNMP connection by attaching a cable to a port and specifying the
assigned management station IP address.
The commands in the CLI are organized into the following levels:
• User EXEC – Lets you display information and perform basic tasks such as pings and
traceroutes.
• Privileged EXEC – Lets you use the same commands as those at the User EXEC level plus
configuration commands that do not require saving the changes to the system-config file.
• CONFIG – Lets you make configuration changes to the device. To save the changes across
reboots, you need to save them to the system-config file. The CONFIG level contains sub-levels
for individual ports, for VLANs, for routing protocols, and other configuration areas.
NOTE
By default, any user who can open a serial or Telnet connection to the Dell PowerConnect device can
access all these CLI levels. To secure access, you can configure Enable passwords or local user
accounts, or you can configure the device to use a RADIUS or TACACS/TACACS+ server for
authentication. Refer to Chapter 32, “Securing Access to Management Functions”.
On-line help
To display a list of available commands or command options, enter “?” or press Tab. If you have not
entered part of a command at the command prompt, all the commands supported at the current
CLI level are listed. If you enter part of a command, then enter “?” or press Tab, the CLI lists the
options you can enter at this point in the command string.
If you enter an invalid command followed by ?, a message appears indicating the command was
unrecognized. An example is given below.
PowerConnect(config)#rooter ip
Unrecognized command
Command completion
The CLI supports command completion, so you do not need to enter the entire name of a command
or option. As long as you enter enough characters of the command or option name to avoid
ambiguity with other commands or options, the CLI understands what you are typing.
Scroll control
By default, the CLI uses a page mode to paginate displays that are longer than the number of rows
in your terminal emulation window. For example, if you display a list of all the commands at the
global CONFIG level but your terminal emulation window does not have enough rows to display
them all at once, the page mode stops the display and lists your choices for continuing the display.
An example is given below.
aaa
all-client
appletalk
arp
boot
some lines omitted for brevity...
4
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Using stack-unit, slot number, and port number with CLI commands
1
ipx
lock-address
logging
mac
--More--, next page: Space, next line:
Return key, quit: Control-c
The software provides the following scrolling options:
• Press the Space bar to display the next page (one screen at a time).
• Press the Return or Enter key to display the next line (one line at a time).
• Press Ctrl+C or Ctrl+Q to cancel the display.
Line editing commands
The CLI supports the following line editing commands. To enter a line-editing command, use the
CTRL+key combination for the command by pressing and holding the CTRL key, then pressing the
letter associated with the command.
TABLE 4
CLI line editing commands
Ctrl+Key combination
Description
Ctrl+A
Moves to the first character on the command line.
Ctrl+B
Moves the cursor back one character.
Ctrl+C
Escapes and terminates command prompts and ongoing tasks (such as
lengthy displays), and displays a fresh command prompt.
Ctrl+D
Deletes the character at the cursor.
Ctrl+E
Moves to the end of the current command line.
Ctrl+F
Moves the cursor forward one character.
Ctrl+K
Deletes all characters from the cursor to the end of the command line.
Ctrl+L; Ctrl+R
Repeats the current command line on a new line.
Ctrl+N
Enters the next command line in the history buffer.
Ctrl+P
Enters the previous command line in the history buffer.
Ctrl+U; Ctrl+X
Deletes all characters from the cursor to the beginning of the command line.
Ctrl+W
Deletes the last word you typed.
Ctrl+Z
Moves from any CONFIG level of the CLI to the Privileged EXEC level; at the
Privileged EXEC level, moves to the User EXEC level.
Using stack-unit, slot number, and port number
with CLI commands
Many CLI commands require users to enter port numbers as part of the command syntax, and
many show command outputs display port numbers. The port numbers are entered and displayed
in one of the following formats:
• port number only
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
5
1
Using stack-unit, slot number, and port number with CLI commands
• slot number and port number
• stack-unit, slot number, and port number
The following sections show which format is supported on which devices. The ports are labelled on
the front panels of the devices.
CLI nomenclature on Stackable devices
Stackable devices (PowerConnect B-Series FCX) use the stack-unit/slot/port nomenclature. When
you enter CLI commands that include the port number as part of the syntax, you must use the
stack-unit/slot/port number format. For example, the following commands change the CLI from
the global CONFIG level to the configuration level for the first port on the device:
PowerConnect(config)#interface e 1/1/1
PowerConnect(config-if-e1000-1/1/1)#
Syntax: ethernet //
Refer to Chapter 5, “Stackable Devices” for more information about these devices.
Searching and filtering output from CLI commands
You can filter CLI output from show commands and at the --More-- prompt. You can search for
individual characters, strings, or construct complex regular expressions to filter the output.
Searching and filtering output from Show commands
You can filter output from show commands to display lines containing a specified string, lines that
do not contain a specified string, or output starting with a line containing a specified string. The
search string is a regular expression consisting of a single character or string of characters. You
can use special characters to construct complex regular expressions. Refer to “Using special
characters in regular expressions” on page 8 for information on special characters used with
regular expressions.
Displaying lines containing a specified string
The following command filters the output of the show interface command for port 3/11 so it
displays only lines containing the word “Internet”. This command can be used to display the IP
address of the interface.
PowerConnect#show interface e 3/11 | include Internet
Internet address is 192.168.1.11/24, MTU 1518 bytes, encapsulation ethernet
Syntax: | include
NOTE
The vertical bar ( | ) is part of the command.
Note that the regular expression specified as the search string is case sensitive. In the example
above, a search string of “Internet” would match the line containing the IP address, but a search
string of “internet” would not.
6
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Using stack-unit, slot number, and port number with CLI commands
1
Displaying lines that do not contain a specified string
The following command filters the output of the show who command so it displays only lines that
do not contain the word “closed”. This command can be used to display open connections to the
Dell PowerConnect device.
PowerConnect#show who | exclude closed
Console connections:
established
you are connecting to this session
2 seconds in idle
Telnet connections (inbound):
1
established, client ip address 192.168.9.37
27 seconds in idle
Telnet connection (outbound):
SSH connections:
Syntax: | exclude
Displaying lines starting with a specified string
The following command filters the output of the show who command so it displays output starting
with the first line that contains the word “SSH”. This command can be used to display information
about SSH connections to the Dell PowerConnect device.
PowerConnect#show who | begin SSH
SSH connections:
1
established, client ip address 192.168.9.210
7 seconds in idle
2
closed
3
closed
4
closed
5
closed
Syntax: | begin
Searching and filtering output at the --More-- prompt
The --More-- prompt displays when output extends beyond a single page. From this prompt, you can
press the Space bar to display the next page, the Return or Enter key to display the next line, or
Ctrl+C or Q to cancel the display. In addition, you can search and filter output from this prompt.
At the --More-- prompt, you can press the forward slash key ( / ) and then enter a search string. The
Dell PowerConnect device displays output starting from the first line that contains the search
string, similar to the begin option for show commands. An example is given below.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
7
1
Using stack-unit, slot number, and port number with CLI commands
--More--, next page: Space, next line: Return key, quit: Control-c
/telnet
The results of the search are displayed.
searching...
telnet
temperature
terminal
traceroute
undebug
undelete
whois
write
Telnet by name or IP address
temperature sensor commands
display syslog
TraceRoute to IP node
Disable debugging functions (see also 'debug')
Undelete flash card files
WHOIS lookup
Write running configuration to flash or terminal
To display lines containing only a specified search string (similar to the include option for show
commands) press the plus sign key ( + ) at the --More-- prompt and then enter the search string.
--More--, next page: Space, next line: Return key, quit: Control-c
+telnet
The filtered results are displayed.
filtering...
telnet
Telnet by name or IP address
To display lines that do not contain a specified search string (similar to the exclude option for show
commands) press the minus sign key ( - ) at the --More-- prompt and then enter the search string.
--More--, next page: Space, next line: Return key, quit: Control-c
-telnet
The filtered results are displayed.
filtering...
temperature
terminal
traceroute
undebug
undelete
whois
write
temperature sensor commands
display syslog
TraceRoute to IP node
Disable debugging functions (see also 'debug')
Undelete flash card files
WHOIS lookup
Write running configuration to flash or terminal
As with the commands for filtering output from show commands, the search string is a regular
expression consisting of a single character or string of characters. You can use special characters
to construct complex regular expressions. See the next section for information on special
characters used with regular expressions.
Using special characters in regular expressions
You use a regular expression to specify a single character or multiple characters as a search string.
In addition, you can include special characters that influence the way the software matches the
output against the search string. These special characters are listed in the following table.
8
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Using stack-unit, slot number, and port number with CLI commands
TABLE 5
1
Special characters for regular expressions
Character
Operation
.
The period matches on any single character, including a blank space.
For example, the following regular expression matches “aaz”, “abz”, “acz”, and so on, but not just
“az”:
a.z
*
The asterisk matches on zero or more sequential instances of a pattern.
For example, the following regular expression matches output that contains the string “abc”,
followed by zero or more Xs:
abcX*
+
The plus sign matches on one or more sequential instances of a pattern.
For example, the following regular expression matches output that contains "de", followed by a
sequence of “g”s, such as “deg”, “degg”, “deggg”, and so on:
deg+
?
The question mark matches on zero occurrences or one occurrence of a pattern.
For example, the following regular expression matches output that contains "dg" or "deg":
de?g
NOTE: Normally when you type a question mark, the CLI lists the commands or options at that CLI
level that begin with the character or string you entered. However, if you enter Ctrl+V and
then type a question mark, the question mark is inserted into the command line, allowing
you to use it as part of a regular expression.
^
A caret (when not used within brackets) matches on the beginning of an input string.
For example, the following regular expression matches output that begins with “deg”:
^deg
$
A dollar sign matches on the end of an input string.
For example, the following regular expression matches output that ends with “deg”:
deg$
_
An underscore matches on one or more of the following:
, (comma)
{ (left curly brace)
} (right curly brace)
( (left parenthesis)
) (right parenthesis)
The beginning of the input string
The end of the input string
A blank space
For example, the following regular expression matches on “100” but not on “1002”, “2100”, and
so on.
_100_
[]
Square brackets enclose a range of single-character patterns.
For example, the following regular expression matches output that contains “1”, “2”, “3”, “4”, or
“5”:
[1-5]
You can use the following expression symbols within the brackets. These symbols are allowed
only inside the brackets.
• ^ – The caret matches on any characters except the ones in the brackets. For example, the
following regular expression matches output that does not contain “1”, “2”, “3”, “4”, or “5”:
•
•
•
•
•
•
•
•
•
[^1-5]
- The hyphen separates the beginning and ending of a range of characters. A match occurs if
any of the characters within the range is present. See the example above.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
9
1
Using stack-unit, slot number, and port number with CLI commands
TABLE 5
Special characters for regular expressions (Continued)
Character
Operation
|
A vertical bar separates two alternative values or sets of values. The output can match one or the
other value.
For example, the following regular expression matches output that contains either “abc” or “defg”:
abc|defg
()
Parentheses allow you to create complex expressions.
For example, the following complex expression matches on “abc”, “abcabc”, or “defg”, but not on
“abcdefgdefg”:
((abc)+)|((defg)?)
If you want to filter for a special character instead of using the special character as described in the
table above, enter “\” (backslash) in front of the character. For example, to filter on output
containing an asterisk, enter the asterisk portion of the regular expression as “\*”.
PowerConnect#show ip route bgp | include \*
Creating an alias for a CLI command
You can create aliases for CLI commands. An alias serves as a shorthand version of a longer CLI
command. For example, you can create an alias called shoro for the CLI command show ip route.
Then when you enter shoro at the command prompt, the show ip route command is executed.
To create an alias called shoro for the CLI command show ip route, enter the following command.
PowerConnect(config)#alias shoro = show ip route
Syntax: [no] alias =
The must be a single word, without spaces.
After the alias is configured, entering shoro at either the Privileged EXEC or CONFIG levels of the
CLI, executes the show ip route command.
To create an alias called wrsbc for the CLI command copy running-config tftp 10.10.10.10 test.cfg,
enter the following command.
PowerConnect(config)#alias wrsbc = copy running-config tftp 10.10.10.10 test.cfg
To remove the wrsbc alias from the configuration, enter one of the following commands.
PowerConnect(config)#no alias wrsbc
or
PowerConnect(config)#unalias wrsbc
Syntax: unalias
The specified must be the name of an alias already configured on the Dell
PowerConnect device.
To display the aliases currently configured on the Dell PowerConnect device, enter the following
command at either the Privileged EXEC or CONFIG levels of the CLI.
PowerConnect#alias
wrsbc
shoro
copy running-config tftp 10.10.10.10 test.cfg
show ip route
Syntax: alias
10
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Logging on through the Web Management Interface
1
Configuration notes
The following configuration notes apply to this feature:
• You cannot include additional parameters with the alias at the command prompt. For example,
after you create the shoro alias, shoro bgp would not be a valid command.
• If configured on the Dell PowerConnect device, authentication, authorization, and accounting
is performed on the actual command, not on the alias for the command.
• To save an alias definition to the startup-config file, use the write memory command.
Logging on through the Web Management Interface
To use the Web Management Interface, open a Web browser and enter the IP address of the
management port on the Dell PowerConnect device in the Location or Address field. The Web
browser contacts the Dell PowerConnect device and displays a Login panel, such as the one shown
below.
FIGURE 1
Web Management Interface login panel
NOTE
If you are unable to connect with the device through a Web browser due to a proxy problem, it may
be necessary to set your Web browser to direct Internet access instead of using a proxy. For
information on how to change a proxy setting, refer to the on-line help provided with your Web
browser.
To log in, click on the Login link. The following dialog box is displayed.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
11
1
Logging on through the Web Management Interface
FIGURE 2
Web Management Interface login dialog
The login username and password you enter depends on whether your device is configured with
AAA authentication for SNMP. If AAA authentication for SNMP is not configured, you can use the
user name “get” and the default read-only password “public” for read-only access. However, for
read-write access, you must enter “set” for the user name, and enter a read-write community string
you have configured on the device for the password. There is no default read-write community
string. You must add one using the CLI.
As an alternative to using the SNMP community strings to log in, you can configure the Dell
PowerConnect device to secure Web management access using local user accounts or Access
Control Lists (ACLs).
Navigating the Web Management Interface
When you log into a device, the System configuration panel is displayed. This panel allows you to
enable or disable major system features. You can return to this panel from any other panel by
selecting the Home link.
The Site Map link gives you a view of all available options on a single screen.
Figure 3 displays the first Web Management Interface panel for Layer 3 Switch features, while
Figure 4 displays the first panel for Layer 2 Switch features. These panels allow you to configure the
features supported by the Layer 3 Switch and Layer 2 Switch software.
12
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Logging on through the Web Management Interface
FIGURE 3
1
First panel for Layer 3 Switch features
NOTE
If you are using Internet Explorer 6.0 to view the Web Management Interface, make sure the version
you are running includes the latest service packs. Otherwise, the navigation tree (the left-most pane
in Figure 3) will not display properly. For information on how to load the latest service packs, refer
to the on-line help provided with your Web browser.
FIGURE 4
First panel for Layer 2 Switch features
NOTE
If you are using Internet Explorer 6.0 to view the Web Management Interface, make sure the version
you are running includes the latest service packs. Otherwise, the navigation tree (the left-most pane
in Figure 3) will not display properly. For information on how to load the latest service packs, refer
to the on-line help provided with your Web browser.
The left pane of the Web Management Interface window contains a “tree view,” similar to the one
found in Windows Explorer. Configuration options are grouped into folders in the tree view. These
folders, when expanded, reveal additional options. To expand a folder, click on the plus sign to the
left of the folder icon.
You can configure the appearance of the Web Management Interface by using one of the following
methods.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
13
1
Logging on through the Web Management Interface
Using the CLI, you can modify the appearance of the Web Management Interface with the
web-management command.
To cause the Web Management Interface to display the List view by default, enter the following
command.
PowerConnect(config)#web-management list-menu
To disable the front panel frame, enter the following command.
PowerConnect(config)#no web-management front-panel
When you save the configuration with the write memory command, the changes will take place the
next time you start the Web Management Interface, or if you are currently running the Web
Management Interface, the changes will take place when you click the Refresh button on your
browser.
Using the Web Management Interface
1. Click on the plus sign next to Configure in the tree view to expand the list of configuration
options.
2. Click on the plus sign next to System in the tree view to expand the list of system configuration
links.
3. Click on the plus sign next to Management in the tree view to expand the list of system
management links.
4. Click on the Web Preference link to display the Web Management Preferences panel.
5. Enable or disable elements on the Web Management Interface by clicking on the appropriate
radio buttons on the panel. The following figure identifies the elements you can change.
14
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Logging on through the Web Management Interface
1
Front Panel
Device
Front Panel Frame
Menu Type
(Tree View shown)
Page Menu
Bottom Frame
Menu Frame
Device
NOTE
The tree view is available when you use the Web Management Interface with Netscape 4.0 or
higher or Internet Explorer 4.0 or higher browsers. If you use the Web Management Interface
with an older browser, the Web Management Interface displays the List view only, and the Web
Management Preferences panel does not include an option to display the tree view.
6. When you have finished, click the Apply button on the panel, then click the Refresh button on
your browser to activate the changes.
7.
To save the configuration, click the plus sign next to the Command folder, then click the Save to
Flash link.
NOTE
The only changes that become permanent are the settings to the Menu Type and the Front
Panel Frame. Any other elements you enable or disable will go back to their default settings
the next time you start the Web Management Interface.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
15
1
Logging on through Brocade Network Advisor
Logging on through Brocade Network Advisor
Refer to the Brocade® Network Advisor manual for information about using Brocade Network
Advisor.
16
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Chapter
Configuring Basic Software Features
2
Table 6 lists the individual Dell PowerConnect switches and the basic software features they
support.
TABLE 6
Supported basic software features
Feature
PowerConnect B-Series FCX
Basic System Parameters
System name, contact, and location
Yes
SNMP trap receiver and trap source
address
Yes
Disable Syslog messages and traps for
CLI access
Yes
Cancelling an outbound Telnet session
Yes
System time using a Simple Network
Time Protocol (SNTP) server or local
system counter
Yes
System clock
Yes
Packet-based broadcast, multicast, and
unknown-unicast limits
Yes
CLI banners
Yes
Local MAC address for Layer 2
management traffic
Yes
Basic Port Parameters
Port name
Yes
10/100/1000 port speed
Yes
Auto-negotiation
Yes
Auto-negotiation maximum port speed
advertisement and down-shift
Yes
Duplex mode
Yes
Auto MDI/MDIX detection
Yes
Port status (enable or disable)
Yes
Flow control:
• Responds to flow control packets,
but does not generate them
Yes
Symmetric flow control
• Can transmit and receive 802.1x
PAUSE frames
Yes
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
17
2
Configuring basic system parameters
TABLE 6
Supported basic software features
Feature
PowerConnect B-Series FCX
Auto-negotiation and advertisement of
flow control
Yes
PHY FIFO Rx and TX Depth
Yes
Interpacket Gap (IPG) adjustment
Yes
CLI support for 100BaseTX and
100BaseFX
Yes
Gbps fiber negotiate mode
Yes
QoS priority
Yes
VOIP autoconfiguration and CDP
Yes
Port flap dampening
Yes
Port loop detection
Yes
Configuring basic system parameters
Dell PowerConnect devices are configured at the factory with default parameters that allow you to
begin using the basic features of the system immediately. However, many of the advanced features
such as VLANs or routing protocols for the device must first be enabled at the system (global) level
before they can be configured. If you use the Command Line Interface (CLI) to configure system
parameters, you can find these system level parameters at the Global CONFIG level of the CLI.
NOTE
Before assigning or modifying any router parameters, you must assign the IP subnet (interface)
addresses for each port.
NOTE
For information about configuring IP addresses, DNS resolver, DHCP assist, and other IP-related
parameters, refer to Chapter 26, “Configuring IP”.
NOTE
For information about the Syslog buffer and messages, refer to Chapter 41, “Using Syslog”.
The procedures in this section describe how to configure the basic system parameters listed in
Table 6.
Entering system administration information
You can configure a system name, contact, and location for a Dell PowerConnect device and save
the information locally in the configuration file for future reference. This information is not required
for system operation but is suggested. When you configure a system name, the name replaces the
default system name in the CLI command prompt.
The name, contact, and location each can be up to 32 alphanumeric characters.
Here is an example of how to configure a system name, system contact, and location.
18
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic system parameters
2
PowerConnect(config)# hostname zappa
zappa(config)# snmp-server contact Support Services
zappa(config)# snmp-server location Centerville
zappa(config)# end
zappa# write memory
Syntax: hostname
Syntax: snmp-server contact
Syntax: snmp-server location
The text strings can contain blanks. The SNMP text strings do not require quotation marks when
they contain blanks but the host name does.
NOTE
The chassis name command does not change the CLI prompt. Instead, the command assigns an
administrative ID to the device.
Configuring Simple Network Management Protocol (SNMP) parameters
Use the procedures in this section to perform the following configuration tasks:
•
•
•
•
•
Specify an SNMP trap receiver.
Specify a source address and community string for all traps sent by the device.
Change the holddown time for SNMP traps
Disable individual SNMP traps. (All traps are enabled by default.)
Disable traps for CLI access that is authenticated by a local user account, a RADIUS server, or
a TACACS/TACACS+ server.
NOTE
To add and modify “get” (read-only) and “set” (read-write) community strings, refer to Chapter 32,
“Securing Access to Management Functions”.
Specifying an SNMP trap receiver
You can specify a trap receiver to ensure that all SNMP traps sent by the Dell PowerConnect device
go to the same SNMP trap receiver or set of receivers, typically one or more host devices on the
network. When you specify the host, you also specify a community string. The Dell PowerConnect
device sends all the SNMP traps to the specified hosts and includes the specified community
string. Administrators can therefore filter for traps from a Dell PowerConnect device based on IP
address or community string.
When you add a trap receiver, the software automatically encrypts the community string you
associate with the receiver when the string is displayed by the CLI or Web Management Interface.
If you want the software to show the community string in the clear, you must explicitly specify this
when you add a trap receiver. In either case, the software does not encrypt the string in the SNMP
traps sent to the receiver.
To specify the host to which the device sends all SNMP traps, use one of the following methods.
To add a trap receiver and encrypt the display of the community string, enter commands such as
the following.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
19
2
Configuring basic system parameters
To specify an SNMP trap receiver and change the UDP port that will be used to receive traps, enter
a command such as the following.
PowerConnect(config)# snmp-server host 2.2.2.2 0 mypublic port 200
PowerConnect(config)# write memory
Syntax: snmp-server host [0 | 1] [port ]
The parameter specifies the IP address of the trap receiver.
The 0 | 1 parameter specifies whether you want the software to encrypt the string (1) or show the
string in the clear (0). The default is 0.
The parameter specifies an SNMP community string configured on the Dell PowerConnect
device. The string can be a read-only string or a read-write string. The string is not used to
authenticate access to the trap host but is instead a useful method for filtering traps on the host.
For example, if you configure each of your Dell PowerConnect devices that use the trap host to send
a different community string, you can easily distinguish among the traps from different Dell
PowerConnect devices based on the community strings.
The command in the example above adds trap receiver 2.2.2.2 and configures the software to
encrypt display of the community string. When you save the new community string to the
startup-config file (using the write memory command), the software adds the following command
to the file.
snmp-server host 2.2.2.2 1
To add a trap receiver and configure the software to encrypt display of the community string in the
CLI and Web Management Interface, enter commands such as the following.
PowerConnect(config)# snmp-server host 2.2.2.2 0 PowerConnect-12
PowerConnect(config)# write memory
The port parameter allows you to specify which UDP port will be used by the trap receiver.
This parameter allows you to configure several trap receivers in a system. With this parameter,
Brocade Network Advisor Network Manager and another network management application can
coexist in the same system. Dell PowerConnect devices can be configured to send copies of traps
to more than one network management application.
Specifying a single trap source
You can specify a single trap source to ensure that all SNMP traps sent by the Layer 3 switch use
the same source IP address. For configuration details, refer to “Configuring ARP parameters” on
page 810
Setting the SNMP trap holddown time
When a Dell PowerConnect device starts up, the software waits for Layer 2 convergence (STP) and
Layer 3 convergence (OSPF) before beginning to send SNMP traps to external SNMP servers. Until
convergence occurs, the device might not be able to reach the servers, in which case the messages
are lost.
By default, a Dell PowerConnect device uses a one-minute holddown time to wait for the
convergence to occur before starting to send SNMP traps. After the holddown time expires, the
device sends the traps, including traps such as “cold start” or “warm start” that occur before the
holddown time expires.
You can change the holddown time to a value from one second to ten minutes.
20
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic system parameters
2
To change the holddown time for SNMP traps, enter a command such as the following at the global
CONFIG level of the CLI.
PowerConnect(config)# snmp-server enable traps holddown-time 30
The command in this example changes the holddown time for SNMP traps to 30 seconds. The
device waits 30 seconds to allow convergence in STP and OSPF before sending traps to the SNMP
trap receiver.
Syntax: [no] snmp-server enable traps holddown-time
The parameter specifies the number of seconds and can be from 1 – 600 (ten minutes).
The default is 60 seconds.
Disabling SNMP traps
Dell PowerConnect devices come with SNMP trap generation enabled by default for all traps. You
can selectively disable one or more of the following traps.
NOTE
By default, all SNMP traps are enabled at system startup.
Layer 2 traps
The following traps are generated on devices running Layer 2 software:
•
•
•
•
•
•
•
•
•
SNMP authentication keys
Power supply failure
Fan failure
Cold start
Link up
Link down
Bridge new root
Bridge topology change
Locked address violation
Layer 3 traps
The following traps are generated on devices running Layer 3 software:
•
•
•
•
•
•
•
•
•
•
SNMP authentication key
Power supply failure
Fan failure
Cold start
Link up
Link down
Bridge new root
Bridge topology change
Locked address violation
BGP4
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
21
2
Configuring basic system parameters
• OSPF
• VRRP
• VRRPE
To stop link down occurrences from being reported, enter the following.
PowerConnect(config)# no snmp-server enable traps link-down
Syntax: [no] snmp-server enable traps
Disabling Syslog messages and traps for CLI access
Dell PowerConnect devices send Syslog messages and SNMP traps when a user logs into or out of
the User EXEC or Privileged EXEC level of the CLI. The feature applies to users whose access is
authenticated by an authentication-method list based on a local user account, RADIUS server, or
TACACS/TACACS+ server.
NOTE
The Privileged EXEC level is sometimes called the “Enable” level, because the command for
accessing this level is enable.
The feature is enabled by default.
Examples of Syslog messages for CLI access
When a user whose access is authenticated by a local user account, a RADIUS server, or a
TACACS/TACACS+ server logs into or out of the CLI User EXEC or Privileged EXEC mode, the
software generates a Syslog message and trap containing the following information:
•
•
•
•
The time stamp
The user name
Whether the user logged in or out
The CLI level the user logged into or out of (User EXEC or Privileged EXEC level)
NOTE
Messages for accessing the User EXEC level apply only to access through Telnet. The device does
not authenticate initial access through serial connections but does authenticate serial access to the
Privileged EXEC level. Messages for accessing the Privileged EXEC level apply to access through the
serial connection or Telnet.
The following examples show login and logout messages for the User EXEC and Privileged EXEC
levels of the CLI.
22
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic system parameters
2
PowerConnect# show logging
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
Buffer logging: level ACDMEINW, 12 messages logged
level code: A=alert C=critical D=debugging M=emergency E=error
I=informational N=notification W=warning
Static Log Buffer:
Dec 15 19:04:14:A:Fan 1, fan on right connector, failed
Dynamic Log Buffer (50 entries):
Oct 15 18:01:11:info:dg logout from USER EXEC mode
Oct 15 17:59:22:info:dg logout from PRIVILEGE EXEC mode
Oct 15 17:38:07:info:dg login to PRIVILEGE EXEC mode
Oct 15 17:38:03:info:dg login to USER EXEC mode
Syntax: show logging
The first message (the one on the bottom) indicates that user “dg” logged in to the CLI User EXEC
level on October 15 at 5:38 PM and 3 seconds (Oct 15 17:38:03). The same user logged into the
Privileged EXEC level four seconds later.
The user remained in the Privileged EXEC mode until 5:59 PM and 22 seconds. (The user could
have used the CONFIG modes as well. Once you access the Privileged EXEC level, no further
authentication is required to access the CONFIG levels.) At 6:01 PM and 11 seconds, the user
ended the CLI session.
Disabling the Syslog messages and traps
Logging of CLI access is enabled by default. If you want to disable the logging, enter the following
commands.
PowerConnect(config)# no logging enable user-login
PowerConnect(config)# write memory
PowerConnect(config)# end
PowerConnect# reload
Syntax: [no] logging enable user-login
Cancelling an outbound Telnet session
If you want to cancel a Telnet session from the console to a remote Telnet server (for example, if the
connection is frozen), you can terminate the Telnet session by doing the following.
1. At the console, press Ctrl+^ (Ctrl+Shift-6).
2. Press the X key to terminate the Telnet session.
Pressing Ctrl+^ twice in a row causes a single Ctrl+^ character to be sent to the Telnet server. After
you press Ctrl+^, pressing any key other than X or Ctrl+^ returns you to the Telnet session.
Specifying a Simple Network Time Protocol (SNTP) server
You can configure the Dell PowerConnect device to consult SNTP servers for the current system
time and date.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
23
2
Configuring basic system parameters
NOTE
Dell PowerConnect devices do not retain time and date information across power cycles. Unless you
want to reconfigure the system time counter each time the system is reset, Dell PowerConnect
recommends that you use the SNTP feature.
To identify an SNTP server with IP address 208.99.8.95 to act as the clock reference for a Dell
PowerConnect device, enter the following.
PowerConnect(config)# sntp server 208.99.8.95
Syntax: sntp server | []
The parameter specifies the SNTP version the server is running and can be from 1 – 4.
The default is 1. You can configure up to three SNTP servers by entering three separate sntp server
commands.
By default, the Dell PowerConnect device polls its SNTP server every 30 minutes (1800 seconds).
To configure the Dell PowerConnect device to poll for clock updates from a SNTP server every 15
minutes, enter the following.
PowerConnect(config)# sntp poll-interval 900
Syntax: [no] sntp poll-interval <1-65535>
To display information about SNTP associations, enter the following command.
PowerConnect# show sntp associations
address
ref clock
st
~207.95.6.102
0.0.0.0
16
~207.95.6.101
0.0.0.0
16
* synced, ~ configured
when
202
202
poll
4
0
delay
0.0
0.0
disp
5.45
0.0
Syntax: show sntp associations
The following table describes the information displayed by the show sntp associations command.
TABLE 7
Output from the show sntp associations command
This field...
Displays...
(leading character)
One or both of the following:
*
Synchronized to this peer
~
Peer is statically configured
address
IP address of the peer
ref clock
IP address of the peer reference clock
st
NTP stratum level of the peer
when
Amount of time since the last NTP packet was received from the peer
poll
Poll interval in seconds
delay
Round trip delay in milliseconds
disp
Dispersion in seconds
To display information about SNTP status, enter the following command.
24
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic system parameters
2
PowerConnect# show sntp status
Clock is synchronized, stratum = 4, reference clock = 10.70.20.23
precision is 2**-20
reference time is 3489354594.3780510747
clock offset is 0.0000 msec, root delay is 0.41 msec
root dispersion is 0.11 msec, peer dispersion is 0.00 msec
sntp poll-interval is 10 secs
Syntax: show sntp status
The following table describes the information displayed by the show sntp status command.
TABLE 8
Output from the show sntp status command
This field...
Indicates...
unsynchronized
System is not synchronized to an NTP peer.
synchronized
System is synchronized to an NTP peer.
stratum
NTP stratum level of this system
reference clock
IP Address of the peer (if any) to which the unit is synchronized
precision
Precision of this system's clock (in Hz)
reference time
Reference time stamp
clock offset
Offset of clock to synchronized peer
root delay
Total delay along the path to the root clock
root dispersion
Dispersion of the root path
peer dispersion
Dispersion of the synchronized peer
sntp poll-interval
Shows how often the Dell PowerConnect device polls for clock
updates from an SNTP server.
Setting the system clock
In addition to SNTP support, Dell PowerConnect switches and routers also allow you to set the
system time counter. The time counter setting is not retained across power cycles and is not
automatically synchronized with an SNTP server. The counter merely starts the system time and
date clock with the time and date you specify.
NOTE
You can synchronize the time counter with your SNTP server time by entering the sntp sync
command from the Privileged EXEC level of the CLI.
NOTE
Unless you identify an SNTP server for the system time and date, you will need to re-enter the time
and date following each reboot.
For more details about SNTP, refer to “Specifying a Simple Network Time Protocol (SNTP) server” on
page 23.
To set the system time and date to 10:15:05 on October 15, 2003, enter the following command.
PowerConnect# clock set 10:15:05 10-15-2003
Syntax: [no] clock set |
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
25
2
Configuring basic system parameters
By default, Dell PowerConnect switches and routers do not change the system time for daylight
saving time. To enable daylight saving time, enter the following command.
PowerConnect# clock summer-time
Syntax: clock summer-time
Although SNTP servers typically deliver the time and date in Greenwich Mean Time (GMT), you can
configure the Dell PowerConnect device to adjust the time for any one-hour offset from GMT or for
one of the following U.S. time zones:
•
•
•
•
•
•
•
•
•
•
•
•
US Pacific
Alaska
Aleutian
Arizona
Central
East-Indiana
Eastern
Hawaii
Michigan
Mountain
Pacific
Samoa
To change the time zone to Australian East Coast time (which is normally 10 hours ahead of GMT),
enter the following command.
PowerConnect(config)# clock timezone gmt gmt+10
Syntax: clock timezone gmt | us
You can enter one of the following values for :
• US time zones (us): alaska, aleutian, arizona, central, east-indiana, eastern, hawaii, michigan,
mountain, pacific, samoa.
• GMT time zones (gmt): gmt+0:00 to gmt+12:00 in increments of 1, and gmt-0:00 to gmt-12:00
in decrements of 1 are supported.
New start and end dates for US daylight saving time
NOTE
This feature applies to US time zones only.
The system will automatically change the system clock to Daylight Saving Time (DST), in compliance
with the new federally mandated start of daylight saving time, which is extended one month
beginning in 2007. The DST will start at 2:00am on the second Sunday in March and will end at
2:00am on the first Sunday in November.
The DST feature is automatic, but to trigger the device to the correct time, the device must be
configured to the US time zone, not the GMT offset. To configure your device to use the US time
zone, enter the following command.
PowerConnect (config)# clock timezone us pacific
26
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic system parameters
2
Syntax: [no] clock timezone us
Enter pacific, eastern, central, or mountain for .
This command must be configured on every device that follows the US DST.
To verify the change, run a show clock command.
PowerConnect # show clock
Refer to October 19, 2006 - Daylight Saving Time 2007 Advisory, posted on kp.foundrynet.com for
more information
Limiting broadcast, multicast, and unknown unicast traffic
Dell PowerConnect devices can forward all flooded traffic at wire speed within a VLAN. However,
some third-party networking devices cannot handle high rates of broadcast, multicast, or
unknown-unicast traffic. If high rates of traffic are being received by the Dell PowerConnect device
on a given port of that VLAN, you can limit the number of broadcast, multicast, or unknown-unicast
packets or bytes received each second on that port. This can help to control the number of such
packets or bytes that are flooded on the VLAN to other devices.
Configuration notes and feature limitationss:
• PowerConnect B-Series FCX devices
- To enable unknown-unicast limiting or multicast limiting, enable it after enabling
broadcast limiting. Unknown-unicast limiting and multicast limiting use the limit defined in
broadcast limiting. You cannot set a separate limit for unknown-unicast limiting and
multicast limiting.
-
PowerConnect B-Series FCX devices support packet-based limiting only.
Command syntax for packet-based limiting on PowerConnect B-Series FCX
devices
To enable broadcast limiting on a group of ports by counting the number of packets received, enter
commands such as the following.
PowerConnect(config)# interface ethernet 1/1/1 to 1/1/8
PowerConnect(config-mif-e1000-1/1/1-1/1/8)# broadcast limit 65536
To include unknown unicast limiting by counting the number of packets received, enter commands
such as the following.
PowerConnect(config-mif-e1000-1/1/1-1/1/8)# unknown-unicast limit
To include multicasts limiting, enter the following command after enabling broadcast limiting.
PowerConnect(config-mif-e1000-1-8)# multicast limit
Syntax: [no] broadcast limit
Syntax: [no] multicast limit
Syntax: [no] unknown-unicast limit
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
27
2
Configuring basic system parameters
The variable specifies the maximum number of packets per second. It can be any number
that is a multiple of 65536, up to a maximum value of 2147418112. If you enter the multicast limit
command, multicast packets are included in the corresponding limit. If you specify 0, limiting is
disabled. If you specify a number that is not a multiple of 65536, the software rounds the number
to the next multiple of 65536. Limiting is disabled by default.
Viewing broadcast, multicast, and unknown unicast limits
You can use the show run interface command to display the broadcast, multicast, and
unknown-unicast limits configured on the device.
You can use the following commands, in addition to the show run interface command, to display
the broadcast, multicast, and unknown-unicast limits configured on the device:
• show rate-limit unknown-unicast
• show rate-limit broadcast
Use the show run interface command to view the broadcast, multicast, and unknown-unicast limit
configured on each port.
Example
PowerConnect# show run interface
interface ethernet 4
broadcast limit 1245184 bytes
multicast limit
!
interface ethernet 5
broadcast limit 1245184 bytes
multicast limit
!
interface ethernet 12
unknown-unicast limit 524288
!
interface ethernet 13
unknown-unicast limit 65536 bytes
!
interface ethernet 14
broadcast limit 65536
!
interface ethernet 23
broadcast limit 131072
multicast limit
!
Syntax: show run interface
Use the show rate-limit unknown-unicast command to display the unknown unicast limit for each
port region to which it applies.
Example
PowerConnect# show rate-limit unknown-unicast
Unknown Unicast Limit Settings:
Port Region Combined Limit Packets/Bytes
1 - 12
524288
Packets
13 - 24
65536
Bytes
28
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic system parameters
2
Syntax: show rate-limit unknown-unicast
Use the show rate-limit broadcast command to display the broadcast limit or broadcast and
multicast limit for each port to which it applies.
Example
PowerConnect# show rate-limit broadcast
Broadcast/Multicast Limit Settings:
Port
Limit
Packets/Bytes
Packet Type(s)
4
1245184
Bytes
Broadcast + Multicast
5
1245184
Bytes
Broadcast + Multicast
14
65536
Packets
Broadcast only
23
131072
Packets
Broadcast + Multicast
Syntax: show rate-limit broadcast
Configuring CLI banners
Dell PowerConnect devices can be configured to display a greeting message on users’ terminals
when they enter the Privileged EXEC CLI level or access the device through Telnet. In addition, a
Dell PowerConnect device can display a message on the Console when an incoming Telnet CLI
session is detected.
Setting a message of the day banner
You can configure the Dell PowerConnect device to display a message on a user terminal when he
or she establishes a Telnet CLI session. For example, to display the message “Welcome to
PowerConnect!” when a Telnet CLI session is established.
PowerConnect(config)# banner motd $ (Press Return)
Enter TEXT message, End with the character '$'.
Welcome to PowerConnect!! $
A delimiting character is established on the first line of the banner motd command. You begin and
end the message with this delimiting character. The delimiting character can be any character
except “ (double-quotation mark) and cannot appear in the banner text. In this example, the
delimiting character is $ (dollar sign). The text in between the dollar signs is the contents of the
banner. The banner text can be up to 4000 characters long, which can consist of multiple lines.
Syntax: [no] banner motd
To remove the banner, enter the no banner motd command.
NOTE
The banner command is equivalent to the banner motd
command.
When you access the Web Management Interface, the banner is displayed.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
29
2
Configuring basic system parameters
NOTE
If you are using a Web client to view the message of the day, and your banners are very wide, with
large borders, you may need to set your PC display resolution to a number greater than the width of
your banner. For example, if your banner is 100 characters wide and the display is set to 80
characters, the banner may distort, or wrap, and be difficult to read. If you set your display resolution
to 120 characters, the banner will display correctly.
Requiring users to press the Enter key after the message of the day banner
In earlier IronWare software releases, users were required to press the Enter key after the Message
of the Day (MOTD) was displayed, prior to logging in to the Dell PowerConnect device on a console
or from a Telnet session. Now, this requirement is disabled by default. Unless configured, users do
not have to press Enter after the MOTD banner is displayed.
For example, if the MOTD "Authorized Access Only" is configured, by default, the following
messages are displayed when a user tries to access the Dell PowerConnect device from a Telnet
session.
Authorized Access Only ...
Username:
The user can then login to the device.
However, if the requirement to press the Enter key is enabled, the following messages are displayed
when accessing the switch from Telnet.
Authorized Access Only ...
Press to accept and continue the login process....
The user must press the Enter key before the login prompt is displayed.
Also, on the console, the following messages are displayed if the requirement to press the Enter
key is disabled.
Press Enter key to login
Authorized Access Only ...
User Access Verification
Please Enter Login Name:
However, if the requirement to press the Enter key after a MOTD is enabled, the following messages
are displayed when accessing the switch on the console.
Press Enter key to login
Authorized Access Only ...
Press to accept and continue the login process....
The user must press the Enter key to continue to the login prompt.
30
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic system parameters
2
To enable the requirement to press the Enter key after the MOTD is displayed, enter a command
such as the following.
PowerConnect(config)# banner motd require-enter-key
Syntax: [no] banner motd require-enter-key
Use the no form of the command to disable the requirement.
Setting a privileged EXEC CLI level banner
You can configure the Dell PowerConnect device to display a message when a user enters the
Privileged EXEC CLI level.
Example
PowerConnect(config)# banner exec_mode # (Press Return)
Enter TEXT message, End with the character '#'.
You are entering Privileged EXEC level
Do not foul anything up! #
As with the banner motd command, you begin and end the message with a delimiting character; in
this example, the delimiting character is #(pound sign). The delimiting character can be any
character except “ (double-quotation mark) and cannot appear in the banner text. The text in
between the pound signs is the contents of the banner. Banner text can be up to 4000 characters,
which can consist of multiple lines.
Syntax: [no] banner exec_mode
To remove the banner, enter the no banner exec_mode command.
Displaying a console message when an incoming Telnet session is detected
You can configure the Dell PowerConnect device to display a message on the Console when a user
establishes a Telnet session. This message indicates where the user is connecting from and
displays a configurable text message.
Example
PowerConnect(config)# banner incoming $ (Press Return)
Enter TEXT message, End with the character '$'.
Incoming Telnet Session!! $
When a user connects to the CLI using Telnet, the following message appears on the Console.
Telnet from 209.157.22.63
Incoming Telnet Session!!
As with the banner motd command, you begin and end the message with a delimiting character; in
this example, the delimiting character is $(dollar sign). The delimiting character can be any
character except “ (double-quotation mark) and cannot appear in the banner text. The text in
between the dollar signs is the contents of the banner. Banner text can be up to 4000 characters,
which can consist of multiple lines.
Syntax: [no] banner incoming
To remove the banner, enter the no banner incoming command.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
31
2
Configuring basic port parameters
Configuring a local MAC address for Layer 2 management traffic
By default, Layer 2 devices use the MAC address of the first port as the MAC address for Layer 2
management traffic. For example, when the Dell PowerConnect device receives an ARP request for
its management IP address, it responds with the first port MAC address. This may cause problems
in some configurations where the Dell PowerConnect device uses the same MAC address for
management traffic as for switched traffic.
You can configure the Dell PowerConnect device to use a different MAC address for Layer 2
management traffic than for switched traffic. When you issue the use-local-management-mac, the
Dell PowerConnect device changes a local bit in the first port MAC address and uses this MAC
address for management traffic. The second bit of the first port MAC address is changed to 2. For
example, if the MAC address is 00e0.5201.9900 after the feature is enabled, the switch uses
02e0.5201.9900 for management functions. Switched traffic will continue to use the first port
MAC address without the local bit setting.
Example
PowerConnect(config)# use-local-management-mac
PowerConnect(config)# write memory
PowerConnect(config)# end
PowerConnect# reload
Syntax: [no] use-local-management-mac
NOTE
You must save the configuration and reload the software to place the change into effect.
NOTE
This feature is only available for the switch code. It is not available for router code.
Configuring basic port parameters
The procedures in this section describe how to configure the port parameters shown in Table 6.
All Dell PowerConnect ports are pre-configured with default values that allow the device to be fully
operational at initial startup without any additional configuration. However, in some cases,
changes to the port parameters may be necessary to adjust to attached devices or other network
requirements.
Assigning a port name
A port name can be assigned to help identify interfaces on the network. You can assign a port
name to physical ports, virtual interfaces, and loopback interfaces.
To assign a name to a port.
PowerConnect(config)# interface ethernet 2
PowerConnect(config-if-e1000-2)# port-name Marsha
Syntax: port-name
The parameter is an alphanumeric string. The name can be up to 64 characters long. The
name can contain blanks. You do not need to use quotation marks around the string, even when it
contains blanks.
32
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic port parameters
2
Modifying port speed and duplex mode
The Gigabit Ethernet copper ports are designed to auto-sense and auto-negotiate the speed and
duplex mode of the connected device. If the attached device does not support this operation, you
can manually enter the port speed to operate at either 10, 100, or 1000 Mbps. The default and
recommended setting is 10/100/1000 auto-sense.
NOTE
You can modify the port speed of copper ports only; this feature does not apply to fiber ports.
NOTE
For optimal link operation, copper ports on devices that do not support 803.3u must be configured
with like parameters, such as speed (10,100,1000), duplex (half, full), MDI/MDIX, and Flow Control.
Configuration syntax
The following commands change the port speed of copper interface 8 on a PowerConnect from the
default of 10/100/1000 auto-sense, to 100 Mbps operating in full-duplex mode.
PowerConnect(config)# interface ethernet 8
PowerConnect(config-if-e1000-8)# speed-duplex 100-full
Syntax: speed-duplex
where can be one of the following:
•
•
•
•
•
•
•
10-full – 10 Mbps, full duplex
10-half – 10 Mbps, half duplex
100-full – 100 Mbps, full duplex
100-half – 100 Mbps, half duplex
1000-full-master – 1 Gbps, full duplex master
1000-full-slave – 1 Gbps, full duplex slave
auto – auto-negotiation
The default is auto (auto-negotiation).
Use the no form of the command to restore the default.
NOTE
On PowerConnect devices, when setting the speed and duplex-mode of an interface to 1000-full,
configure one side of the link as master (1000-full-master) and the other side as slave
(1000-full-slave).
Enabling auto-negotiation maximum port speed
advertisement and down-shift
NOTE
For optimal link operation, link ports on devices that do not support 803.3u must be configured with
like parameters, such as speed (10,100,1000), duplex (half, full), MDI/MDIX, and Flow Control.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
33
2
Configuring basic port parameters
Maximum Port speed advertisement and Port speed down-shift are enhancements to the
auto-negotiation feature, a mechanism for accommodating multi-speed network devices by
automatically configuring the highest performance mode of inter-operation between two connected
devices.
Port speed down-shift enables Gbps copper ports on the Dell PowerConnect device to establish a
link at 1000 Mbps over a 4-pair wire when possible, or to down-shift to 100 Mbps if the medium is
a 2-pair wire.
Maximum port speed advertisement enables you to configure an auto-negotiation maximum speed
that Gbps copper ports on the Dell PowerConnect device will advertise to the connected device.
You can configure a port to advertise a maximum speed of either 100 Mbps or 10 Mbps. When the
maximum port speed advertisement feature is configured on a port that is operating at 100 Mbps
maximum speed, the port will advertise 10/100 Mbps capability to the connected device.
Similarly, if a port is configured at 10 Mbps maximum speed, the port will advertise 10 Mbps
capability to the connected device.
The port speed down-shift and maximum port speed advertisement features operate dynamically
at the physical link layer between two connected network devices. They examine the cabling
conditions and the physical capabilities of the remote link, then configure the speed of the link
segment according to the highest physical-layer technology that both devices can accommodate.
The port speed down-shift and maximum port speed advertisement features operate dynamically
at the physical link layer, independent of logical trunk group configurations. Although Dell
recommends that you use the same cable types and auto-negotiation configuration on all
members of a trunk group, you could utilize the auto-negotiation features conducive to your cabling
environment. For example, in certain circumstances, you could configure each port in a trunk
group to have its own auto-negotiation maximum port speed advertisement or port speed
down-shift configuration.
Application notes
• Port speed down-shift and maximum port speed advertisement work only when
auto-negotiation is enabled (CLI command speed-duplex auto). If auto-negotiation is OFF, the
device will reject the port speed down-shift and maximum port speed advertisement
configuration.
• When port speed down-shift or maximum port speed advertisement is enabled on a port, the
device will reject any configuration attempts to set the port to a forced speed mode (100 Mbps
or 1000 Mbps).
• When the port speed down-shift feature is enabled on a combo port, the port will not support
true media automatic detection, meaning the device will not be able to detect and select the
fiber or copper connector based on link availability.
Enabling port speed down-shift
To enable port speed down-shift on a port that has auto-negotiation enabled, enter a command
such as the following at the Global CONFIG level of the CLI.
PowerConnect(config)# link-config gig copper autoneg-control down-shift ethernet
1 ethernet 2
The above command configures Gbps copper ports 1 and 2 to establish a link at 1000 Mbps over a
4-pair wire when possible, or to down-shift (reduce the speed) to 100 Mbps when the medium is a
2-pair wire.
34
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic port parameters
2
Syntax: [no] link-config gig copper autoneg-control down-shift ethernet [ethernet ] |
to ...
Specify the variable in the following formats:
• PowerConnect B-Series FCX stackable switches –
You can list all of the ports individually, use the keyword to to specify ranges of ports, or a
combination of both.
You can enable port speed down-shift on one or two ports at a time.
To disable port speed down-shift after it has been enabled, enter the no form of the command.
Configuring port speed down-shift and auto-negotiation for a range of ports
Port speed down-shift and auto-negotiation can be configured for an entire range of ports with a
single command.
For example, to configure down-shift on ports 0/1/1 to 0/1/10 and 0/1/15 to 0/1/20 on the
device, enter the following.
PowerConnect(config)# link-config gig copper autoneg-control down-shift ethernet
0/1/1 to 0/1/10 ethernet 0/1/15 to 0/1/20
To configure down-shift on ports 5 to 13 and 17 to 19 on a compact switch, enter the following.
PowerConnect(config)# link-config gig copper autoneg-control down-shift ethernet
5 to 13 ethernet 17 to 19
Syntax: [no] link-config gig copper autoneg-control [down-shift | 100m-auto | 10m-auto] ethernet
The is the list of ports to which the command will be applied.
For , specify the ports in the following formats:
• PowerConnect B-Series FCX stackable switches –
You can list all of the ports individually, use the keyword to to specify ranges of ports, or a
combination of both. To apply the configuration to all ports on the device, use the keyword all
instead of listing the ports individually.
The output from the show run command for this configuration will resemble the following.
PowerConnect# show run
Current configuration:
!
ver 7.2.00a
!
module 1 FCX-48-port-management-module
module 2 FCX-cx4-2-port-16G-module
!
link-config gig copper autoneg-control down-shift ethernet 0/1/1 to 0/1/10
ethernet 0/1/15 to 0/1/20
!
!
ip address 10.44.9.11 255.255.255.0
ip default-gateway 10.44.9.1
!
end
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
35
2
Configuring basic port parameters
To disable selective auto-negotiation of 100m-auto on ports 0/1/21 to 0/1/25 and 0/1/30, enter
the following.
PowerConnect(config)# no link-config gig copper autoneg-control 100m-auto
ethernet 0/1/21 to 0/1/25 ethernet 0/1/30
Configuring maximum port speed advertisement
To configure a maximum port speed advertisement of 10 Mbps on a port that has auto-negotiation
enabled, enter a command such as the following at the Global CONFIG level of the CLI.
PowerConnect(config)# link-config gig copper autoneg-control 10m ethernet 1
To configure a maximum port speed advertisement of 100 Mbps on a port that has
auto-negotiation enabled, enter the following command at the Global CONFIG level of the CLI.
PowerConnect(config)# link-config gig copper autoneg-control 100m ethernet 2
Syntax: [no] link-config gig copper autoneg-control 10m | 100m ethernet [ethernet
[]
Specify the variable in the following formats:
• PowerConnect B-Series FCX stackable switches –
You can list all of the ports individually, use the keyword to to specify ranges of ports, or a
combination of both.
You can enable maximum port speed advertisement on one or two ports at a time.
To disable maximum port speed advertisement after it has been enabled, enter the no form of the
command.
Modifying port duplex mode
You can manually configure a 10/100 Mbps port to accept either full-duplex (bi-directional) or
half-duplex (uni-directional) traffic.
NOTE
You can modify the port duplex mode of copper ports only. This feature does not apply to fiber ports.
Port duplex mode and port speed are modified by the same command.
Configuration syntax
To change the port speed of interface 8 from the default of 10/100/1000 auto-sense to 10 Mbps
operating at full-duplex, enter the following.
PowerConnect(config)# interface ethernet 8
PowerConnect(config-if-e1000-8)# speed-duplex 10-full
Syntax: speed-duplex
The can be one of the following:
• 10-full
• 10-half
• 100-full
36
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic port parameters
2
• 100-half
• auto (default)
Configuring MDI/MDIX
Dell PowerConnect devices support automatic Media Dependent Interface (MDI) and Media
Dependent Interface Crossover (MDIX) detection on all Gbps Ethernet Copper ports.
MDI/MDIX is a type of Ethernet port connection using twisted pair cabling. The standard wiring for
end stations is MDI, whereas the standard wiring for hubs and switches is MDIX. MDI ports
connect to MDIX ports using straight-through twisted pair cabling. For example, an end station
connected to a hub or a switch uses a straight-through cable. MDI-to-MDI and MDIX-to-MDIX
connections use crossover twisted pair cabling. So, two end stations connected to each other, or
two hubs or switches connected to each other, use crossover cable.
The auto MDI/MDIX detection feature can automatically correct errors in cable selection, making
the distinction between a straight-through cable and a crossover cable insignificant.
Configuration notes
• This feature applies to copper ports only.
• The mdi-mdix mdi and mdi-mdix mdix commands work independently of auto-negotiation.
Thus, these commands work whether auto-negotiation is turned ON or OFF.
• Do not use the mdi-mdix commands on ports that are manually configured with a speed and
duplex of 100-full. In this case, make sure the other port (remote end of the connection) is
also configured to 100-full and a cross-over cable is used if the connected device is another
switch, hub, or router, or a straight-through cable if the connected device is a host NIC.
Configuration syntax
The auto MDI/MDIX detection feature is enabled on all Gbps copper ports by default. For each
port, you can disable auto MDI/MDIX, designate the port as an MDI port, or designate the port as
an MDIX port.
To turn off automatic MDI/MDIX detection and define a port as an MDI only port.
PowerConnect(config-if-e1000-2)# mdi-mdix mdi
To turn off automatic MDI/MDIX detection and define a port as an MDIX only port.
PowerConnect(config-if-e1000-2)# mdi-mdix mdix
To turn on automatic MDI/MDIX detection on a port that was previously set as an MDI or MDIX port.
PowerConnect(config-if-e1000-2)# mdi-mdix auto
Syntax: mdi-mdix
After you enter the mdi-mdix command, the Dell PowerConnect device resets the port and applies
the change.
To display the MDI/MDIX settings, including the configured value and the actual resolved setting
(for mdi-mdix auto), enter the command show interface at any level of the CLI.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
37
2
Configuring basic port parameters
Disabling or re-enabling a port
A port can be made inactive (disable) or active (enable) by selecting the appropriate status option.
The default value for a port is enabled.
To disable port 8 of a Dell PowerConnect device, enter the following.
PowerConnect(config)# interface ethernet 8
PowerConnect(config-if-e1000-8)# disable
You also can disable or re-enable a virtual interface. To do so, enter commands such as the
following.
PowerConnect(config)# interface ve v1
PowerConnect(config-vif-1)# disable
Syntax: disable
To re-enable a virtual interface, enter the enable command at the Interface configuration level. For
example, to re-enable virtual interface v1, enter the following command.
PowerConnect(config-vif-1)# enable
Syntax: enable
Configuring flow control
Flow control (802.3x) is a QoS mechanism created to manage the flow of data between two
full-duplex Ethernet devices. Specifically, a device that is oversubscribed (is receiving more traffic
than it can handle) sends an 802.3x PAUSE frame to its link partner to temporarily reduce the
amount of data the link partner is transmitting. Without flow control, buffers would overflow,
packets would be dropped, and data retransmission would be required.
All PowerConnect devices support asymmetric flow control, meaning they can receive PAUSE
frames but cannot transmit them. In addition, FCX devices also support symmetric flow control,
meaning they can both receive and transmit 802.3x PAUSE frames. For details about symmetric
flow control, refer to “Configuring symmetric flow control on PowerConnect B-Series FCX devices”
on page 40.
Configuration notes
• Auto-negotiation of flow control is not supported on 10 Gbps ports, fiber ports, and copper or
fiber combination ports.
• When any of the flow control commands are applied to a port that is up, the port will be
disabled and re-enabled.
• For 10 Gbps ports, the show interface display shows Flow Control is enabled or Flow
Control is disabled, depending on the configuration.
• When flow-control is enabled, the hardware can only advertise PAUSE frames. It does not
advertise Asym.
38
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic port parameters
2
Disabling or re-enabling flow control
You can configure the Dell PowerConnect device to operate with or without flow control. Flow
control is enabled by default globally and on all full-duplex ports. You can disable and re-enable
flow control at the Global CONFIG level for all ports. When enabled globally, you can disable and
re-enable flow control on individual ports.
To disable flow control, enter the following command.
PowerConnect(config)# no flow-control
To turn the feature back on, enter the following command.
PowerConnect(config)# flow-control
Syntax: [no] flow-control
NOTE
For optimal link operation, link ports on devices that do not support 803.3u must be configured with
like parameters, such as speed (10,100,1000), duplex (half, full), MDI/MDIX, and Flow Control.
Negotiation and advertisement of flow control
By default, when flow control is enabled globally and auto-negotiation is ON, flow control is enabled
and advertised on 10/100/1000M ports. If auto-negotiation is OFF or if the port speed was
configured manually, then flow control is not negotiated with or advertised to the peer. For details
about auto-negotiation, refer to “Modifying port speed and duplex mode” on page 33.
To disable the advertisement of flow control capability on a port, enter the following commands.
PowerConnect(config)# interface ethernet 0/1/21
PowerConnect(config-if-e1000-0/1/21)# no flow-control
To also disable flow control negotiation, enter the following commands.
PowerConnect(config)# interface ethernet 0/1/21
PowerConnect(config-if-e1000-0/1/21)# no flow-control neg-on
Syntax: [no] flow-control [neg-on]
• flow-control [default] - Enable flow control, flow control negotiation, and advertise flow control
• no flow-control neg-on - Disable flow control negotiation
• no flow-control - Disable flow control, flow control negotiation, and advertising of flow control
Commands may be entered in IF (single port) or MIF (multiple ports at once) mode.
Example
PowerConnect(config)# interface ethernet 0/1/21
PowerConnect(config-if-e1000-0/1/21)# no flow-control
This command disables flow control on port 0/1/21.
PowerConnect(config)# interface ethernet 0/1/11 to 0/1/15
PowerConnect(config-mif-0/1/11-0/1/15)# no flow-control
This command disables flow control on ports 0/1/11 to 0/1/15.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
39
2
Configuring basic port parameters
Displaying flow-control status
The show interface command displays configuration, operation, and negotiation status
where applicable.
For example, on a PowerConnect Stackable device, issuing the command for 10/100/1000M port
0/1/21 displays the following output.
PowerConnect# show interfaces ethernet 0/1/21
GigabitEthernet0/1/21 is up, line protocol is up
Hardware is GigabitEthernet, address is 00e0.5204.4014 (bia 00e0.5204.4014)
Configured speed auto, actual 100Mbit, configured duplex fdx, actual fdx
Configured mdi mode AUTO, actual MDIX
Member of L2 VLAN ID 1, port is untagged, port state is LISTENING
BPDU Guard is disabled, Root Protect is disabled
STP configured to ON, priority is level0
Flow Control is config enabled, oper enabled, negotiation disabled
Mirror disabled, Monitor disabled
Not member of any active trunks
Not member of any configured trunks
No port name
Inter-Packet Gap (IPG) is 96 bit times
300 second input rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
300 second output rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 multicasts, 0 unicasts
0 input errors, 0 CRC, 0 frame, 0 ignored
0 runts, 0 giants
5 packets output, 320 bytes, 0 underruns
Transmitted 0 broadcasts, 5 multicasts, 0 unicasts
0 output errors, 0 collisions
The line highlighted in bold will resemble one of the following, depending on the configuration:
• If flow-control negotiation is enabled (and a neighbor does not negotiate flow control), the
display shows:
Flow Control is config enabled, oper disabled, negotiation enabled
• If flow control is enabled, and flow-control negotiation is disabled, the output shows.
Flow Control is config enabled, oper enabled, negotiation disabled
• If flow control is disabled, the display shows.
Flow Control is config disabled, oper disabled
Configuring symmetric flow control on PowerConnect B-Series FCX
devices
In addition to asymmetric flow control, PowerConnect B-Series FCX devices support symmetric flow
control, meaning they can both receive and transmit 802.3x PAUSE frames.
By default on PowerConnect B-Series FCX devices, packets are dropped from the end of the queue
at the egress port (tail drop mode), when the maximum queue limit is reached. Conversely, when
symmetric flow control is enabled, packets are guaranteed delivery since they are managed at the
ingress port and no packets are dropped.
40
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic port parameters
2
Symmetric flow control addresses the requirements of a lossless service class in an Internet Small
Computer System Interface (iSCSI) environment. It is supported on FCX standalone units as well as
on all FCX units in an IronStack.
About XON and XOFF thresholds
An 802.3x PAUSE frame is generated when the buffer limit at the ingress port reaches or exceeds
the port’s upper watermark threshold (XOFF limit). The PAUSE frame requests that the sender stop
transmitting traffic for a period of time. The time allotted enables the egress and ingress queues to
be cleared. When the ingress queue falls below the port’s lower watermark threshold (XON limit),
an 802.3x PAUSE frame with a quanta of 0 (zero) is generated. The PAUSE frame requests that the
sender resume sending traffic normally.
Each 1G and 10G port is configured with a default total number of buffers as well as a default XOFF
and XON threshold. The defaults are different for 1G ports versus 10G ports. Also, the default XOFF
and XON thresholds are different for jumbo mode versus non-jumbo mode. The defaults are shown
in Table 9.
TABLE 9
XON and XOFF default thresholds
Limit when Jumbo disabled /
% of buffer limit
Limit when Jumbo enabled /
% of buffer limit
Total buffers
272
272
XOFF
240 / 91%
216 / 82%
XON
200 / 75%
184 / 70%
Total buffers
416
416
XOFF
376 / 91%
336 / 82%
XON
312 / 75%
288 / 70%
1G ports
10G ports
If necessary, you can change the total buffer limits and the XON and XOFF default thresholds. Refer
to “Changing the total buffer limits” on page 43 and “Changing the XON and XOFF thresholds” on
page 42, respectively.
Configuration notes and feature limitations for symmetric flow control
Note the following configuration notes and feature limitations before enabling symmetric flow
control.
•
•
•
•
Symmetric flow control is supported on PowerConnect B-Series FCX devices only.
Symmetric flow control is supported on all PowerConnect B-Series FCX 1G and 10G data ports.
Symmetric flow control is not supported on stacking ports or across units in a stack.
To use this feature, 802.3x flow control must be enabled globally and per interface on the
PowerConnect B-Series FCX . By default, 802.3x flow control is enabled, but can be disabled
with the no flow-control command.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
41
2
Configuring basic port parameters
• The following QoS features are not supported together with symmetric flow control:
- Dynamic buffer allocation (CLI commands qd-descriptor and qd-buffer)
- Buffer profiles (CLI command buffer-profile port-region)
- DSCP-based QoS (CLI command trust dscp)
NOTE
Although the above QoS features are not supported with symmetric flow control, the CLI will
still accept these commands. The last command issued will be the one placed into effect on
the device. For example, if trust dscp is enabled after symmetric-flow-control is enabled,
symmetric flow control will be disabled and trust dscp will be placed into effect. Make sure you
do not enable incompatible QoS features when symmetric flow control is enabled on the
device.
• Head of Line (HOL) blocking may occur when symmetric flow control is enabled. This means
that a peer can stop transmitting traffic streams unrelated to the congestion stream.
Enabling and disabling symmetric flow control
By default, symmetric flow control is disabled and tail drop mode is enabled. However, because
flow control is enabled by default on all full-duplex ports, these ports will always honor received
802.3x Pause frames, whether or not symmetric flow control is enabled.
To enable symmetric flow control globally on all full-duplex data ports of a standalone unit, enter
the following command.
PowerConnect(config)# symmetric-flow-control enable
To enable symmetric flow control globally on all full-duplex data ports of a particular unit in an
IronStack, enter a command such as the following.
PowerConnect(config)# symmetric-flow-control enable unit 4
Syntax: [no] symmetric-flow-control enable [unit ]
The parameter specifies one of the units in a stacking system.
Master/Standby/Members are examples of a stack-unit
To disable symmetric flow control once it has been enabled, use the no form of the command.
Changing the XON and XOFF thresholds
This section describes how to change the XON and XOFF thresholds described in “About XON and
XOFF thresholds” on page 41.
To change the thresholds for all 1G ports, enter a command such as the following.
PowerConnect(config)# symmetric-flow-control set 1 xoff 91 xon 75
To change the thresholds for all 10G ports, enter a command such as the following.
PowerConnect(config)# symmetric-flow-control set 2 xoff 91 xon 75
In the above configuration examples, when the XOFF limit of 91% is reached or exceeded, the Dell
PowerConnect device will send PAUSE frames to the sender telling it to stop transmitting data
temporarily. When the XON limit of 75% is reached, the Dell PowerConnect device will send PAUSE
frames to the sender telling it to resume sending data.
42
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic port parameters
2
Syntax: symmetric-flow-control set 1 | 2 xoff <%> xon <%>
symmetric-flow-control set 1 sets the XOFF and XON limits for 1G ports.
symmetric-flow-control set 2 sets the XOFF and XON limits for 10G ports.
For xoff <%>, the <%> minimum value is 60% and the maximum value is 95%.
For xon <%>, the <%> minimum value is 50% and the maximum value is 90%.
Use the show symmetric command to view the default or configured XON and XOFF thresholds.
Refer to “Displaying symmetric flow control status” on page 43.
Changing the total buffer limits
This section describes how to change the total buffer limits described in “About XON and XOFF
thresholds” on page 41. You can change the limits for all 1G ports and for all 10G ports.
To change the total buffer limit for all 1G ports, enter a command such as the following.
PowerConnect(config)# symmetric-flow-control set 1 buffers 320
Total buffers modified, 1G: 320, 10G: 128
To change the total buffer limit for all 10G ports, enter a command such as the following.
PowerConnect(config)# symmetric-flow-control set 2 buffers 128
Total buffers modified, 1G: 320, 10G: 128
Syntax: symmetric-flow-control set 1 | 2 buffers
symmetric-flow-control set 1 buffers sets the total buffer limits for 1G ports. The default
is 272. You can specify a number from 64 – 320.
symmetric-flow-control set 2 buffers sets the total buffer limits for 10G ports. The default
is 416. You can specify a number from 64 – 1632.
Use the show symmetric command to view the default or configured total buffer limits. Refer to
“Displaying symmetric flow control status” on page 43.
Displaying symmetric flow control status
The show symmetric-flow-control command displays the status of symmetric flow control as well as
the default or configured total buffer limits and XON and XOFF thresholds.
PowerConnect(config)# show symmetric
Symmetric Flow Control Information:
----------------------------------Symmetric Flow Control is enabled on units: 2 3
Buffer parameters:
1G Ports:
Total Buffers : 272
XOFF Limit
: 240(91%)
XON Limit
: 200(75%)
10G Ports:
Total Buffers : 416
XOFF Limit
: 376(91%)
XON Limit
: 312(75%)
Syntax: show symmetric-flow-control
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
43
2
Configuring basic port parameters
Configuring PHY FIFO Rx and Tx depth
PHY devices on PowerConnect B-Series FCX devices contain transmit and receive synchronizing
FIFOs to adjust for frequency differences between clocks. The phy-fifo-depth command allows you
to configure the depth of the transmit and receive FIFOs. There are 4 settings (0-3) with 0 as the
default. A higher setting indicates a deeper FIFO.
The default setting works for most connections. However, if the clock differences are greater than
the default will handle, CRCs and errors will begin to appear on the ports. Raising the FIFO depth
setting will adjust for clock differences.
Dell recommends that you disable the port before applying this command, and re-enable the port.
Applying the command while traffic is flowing through the port can cause CRC and other errors for
any packets that are actually passing through the PHY while the command is being applied.
Syntax: [no] phy-fifo-depth
•
is a value between 0 and 3. (0 is the default.)
This command can be issued for a single port from the IF config mode or for multiple ports from the
MIF config mode.
NOTE
Higher settings give better tolerance for clock differences with the partner phy, but may marginally
increase latency as well.
Configuring the IPG on PowerConnect Stackable devices
On PowerConnect B-Series FCX devices, you can configure an IPG for each port. An IPG is a
configurable time delay between successive data packets.
You can configure an IPG with a range from 48-120 bit times in multiples of 8, with a default of 96.
The IPG may be set from either the interface configuration level or the multiple interface level.
Configuration notes
• This section describes the configuration procedures for PowerConnect Stackable devices.
• When an IPG is applied to a trunk group, it applies to all ports in the trunk group. When you are
creating a new trunk group, the IPG setting on the primary port is automatically applied to the
secondary ports.
• This feature is supported on 10/100/1000M ports.
Configuring IPG on a 10/100/1000M port
To configure an IPG of 112 on Ethernet interface 0/1/21, for example, enter the following
command.
PowerConnect(config)# interface ethernet 0/1/21
PowerConnect(config-if-e1000-0/1/21)# ipg 112
For multiple interface levels, to configure IPG for ports 0/1/11 and 0/1/14 through 0/1/17, enter
the following commands.
PowerConnect(config)# interface ethernet 0/1/11 ethernet 0/1/14 to 0/1/17
PowerConnect(config-mif-0/1/11,0/1/14-0/1/17)# ipg 104
44
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic port parameters
2
Syntax: [no] ipg
For value, enter a number in the range from 48-120 bit times in multiples of 8. The default is 96.
As a result of the above configuration, the output from the show interface Ethernet 0/1/21
command is as follows.
PowerConnect# show interfaces ethernet 0/1/21
GigabitEthernet 0/1/21 is up, line protocol is up
Hardware is GigabitEthernet, address is 00e0.5204.4014 (bia 00e0.5204.4014)
Configured speed auto, actual 100Mbit, configured duplex fdx, actual fdx
Configured mdi mode AUTO, actual MDIX
Member of L2 VLAN ID 1, port is untagged, port state is FORWARDING
BPDU Guard is disabled, Root Protect is disabled
STP configured to ON, priority is level0
Flow Control is config enabled, oper enabled, negotiation disabled
Mirror disabled, Monitor disabled
Not member of any active trunks
Not member of any configured trunks
No port name
Inter-Packet Gap (IPG) is 112 bit times
IP MTU 10222 bytes
300 second input rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
300 second output rate: 248 bits/sec, 0 packets/sec, 0.00% utilization
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 multicasts, 0 unicasts
0 input errors, 0 CRC, 0 frame, 0 ignored
0 runts, 0 giants
80 packets output, 5120 bytes, 0 underruns
Transmitted 0 broadcasts, 80 multicasts, 0 unicasts
0 output errors, 0 collisions
Enabling and disabling support for 100BaseTX
Configuration notes
• This feature requires that autonegotiation be enabled on the other end of the link.
• Although combo ports (ports 1 – 4) on Hybrid Fiber (HF) models support the 1000Base-TX SFP,
they cannot be configured to operate at 100 Mbps. The 100 Mbps operating speed is
supported only with non-combo ports (ports 5-24).
• 1000Base-TX modules must be configured individually, one interface at a time.
• 1000Base-TX modules do not support Digital Optical Monitoring.
• This module requires a Cat5 cable and uses an RJ45 connector.
Enabling and disabling support for 100BaseFX
Some Dell PowerConnect devices support 100BaseFX fiber transceivers. After you physically
install a 100BaseFX transceiver, you must enter a CLI command to enable it. .
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
45
2
Configuring basic port parameters
Chassis-based and Stackable devices
NOTE
The following procedure applies to Stackable devices and to Chassis-based 100/1000 Fiber
interface modules only. The CLI syntax for enabling and disabling 100BaseFX support on these
devices differs than on a Compact device. Make sure you refer to the appropriate procedures.
PowerConnect devices support the following types of SFPs for 100BaseFX:
•
•
•
•
Multimode SFP – maximum distance is 2 kilometers
Bidirectional single mode SFP – maximum distance is 10 kilometers
Long Reach (LR) – maximum distance is 40 kilometers
Intermediate Reach (IR) – maximum distance is 15 kilometers
NOTE
Connect the 100BaseFX fiber transceiver after configuring both sides of the link. Otherwise, the
link could become unstable, fluctuating between up and down states.
To enable support for 100BaseFX on an fiber port or on a Stackable switch, enter commands such
as the following.
PowerConnect(config)# interface ethernet 1/6
PowerConnect(config-if-1/6)# 100-fx
The above commands enable 100BaseFX on port 6 in slot 1.
Syntax: [no] 100-fx
To disable 100BaseFX support on a fiber port, enter the no form of the command. Note that you
must disable 100BaseFX support before inserting a different type of module In the same port.
Otherwise, the device will not recognize traffic traversing the port.
Changing the Gbps fiber negotiation mode
The globally configured Gbps negotiation mode is the default mode for all Gbps fiber ports. You
can override the globally configured default and set individual ports to the following:
• Negotiate-full-auto – The port first tries to perform a handshake with the other port to
exchange capability information. If the other port does not respond to the handshake attempt,
the port uses the manually configured configuration information (or the defaults if an
administrator has not set the information). This is the default.
• Auto-Gbps – The port tries to perform a handshake with the other port to exchange capability
information.
• Negotiation-off – The port does not try to perform a handshake. Instead, the port uses
configuration information manually configured by an administrator.
To change the mode for individual ports, enter commands such as the following.
PowerConnect(config)# interface ethernet 1 to 4
PowerConnect(config-mif-1-4)# gig-default auto-gig
This command overrides the global setting and sets the negotiation mode to auto-Gbps for ports 1
– 4.
Syntax: gig-default neg-full-auto | auto-gig | neg-off
46
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic port parameters
2
NOTE
When Gbps negotiation mode is turned off (CLI command gig-default neg-off), the Dell device may
inadvertently take down both ends of a link. This is a hardware limitation for which there is currently
no workaround.
Modifying port priority (QoS)
You can give preference to the inbound traffic on specific ports by changing the Quality of Service
(QoS) level on those ports. For information and procedures, refer to Chapter 17, “Configuring
Quality of Service”.
Dynamic configuration of Voice over IP (VoIP) phones
You can configure a PowerConnect device to automatically detect and re-configure a VoIP phone
when it is physically moved from one port to another within the same device. To do so, you must
configure a voice VLAN ID on the port to which the VoIP phone is connected. The software stores
the voice VLAN ID in the port database for retrieval by the VoIP phone.
The dynamic configuration of a VoIP phone works in conjunction with the VoiP phone discovery
process. Upon installation, and sometimes periodically, a VoIP phone will query the Dell
PowerConnect device for VoIP information and will advertise information about itself, such as,
device ID, port ID, and platform. When the Dell PowerConnect device receives the VoIP phone
query, it sends the voice VLAN ID in a reply packet back to the VoIP phone. The VoIP phone then
configures itself within the voice VLAN.
As long as the port to which the VoIP phone is connected has a voice VLAN ID, the phone will
configure itself into that voice VLAN. If you change the voice VLAN ID, the software will immediately
send the new ID to the VoIP phone, and the VoIP phone will re-configure itself with the new voice
VLAN.
Configuration notes
• This feature works with any VoIP phone that:
- Runs CDP
- Sends a VoIP VLAN query message
- Can configure its voice VLAN after receiving the VoIP VLAN reply
• Automatic configuration of a VoIP phone will not work if one of the following applies:
- You do not configure a voice VLAN ID for a port with a VoIP phone
- You remove the configured voice VLAN ID from a port without configuring a new one
- You remove the port from the voice VLAN
• Make sure the port is able to intercept CDP packets (cdp run command).
• Some VoIP phones may require a reboot after configuring or re-configuring a voice VLAN ID.
For example, if your VoIP phone queries for VLAN information only once upon boot up, you must
reboot the VoIP phone before it can accept the VLAN configuration.
• Dell PowerConnect devices do not currently support Cisco 7970 VOIP phones.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
47
2
Configuring basic port parameters
Enabling dynamic configuration of a Voice over IP (VoIP) phone
You can create a voice VLAN ID for a port, or for a group of ports.
To create a voice VLAN ID for a port, enter commands such as the following.
PowerConnect(config)# interface ethernet 2
PowerConnect(config-if-e1000-2)# voice-vlan 1001
To create a voice VLAN ID for a group of ports, enter commands such as the following.
PowerConnect(config)# interface ethernet 1-8
PowerConnect(config-mif-1-8)# voice-vlan 1001
Syntax: [no] voice-vlan
where is a valid VLAN ID between 1 – 4095.
To remove a voice VLAN ID, use the no form of the command.
Viewing voice VLAN configurations
You can view the configuration of a voice VLAN for a particular port or for all ports.
To view the voice VLAN configuration for a port, specify the port number with the show voice-vlan
command. The following example shows the command output results.
PowerConnect# show voice-vlan ethernet 2
Voice vlan ID for port 2: 1001
The following example shows the message that appears when the port does not have a configured
voice VLAN.
PowerConnect# show voice-vlan ethernet 2
Voice vlan is not configured for port 2.
To view the voice VLAN for all ports, use the show voice-vlan command. The following example
shows the command output results.
PowerConnect# show voice-vlan
Port ID
Voice-vlan
2
1001
8
150
15
200
Syntax: show voice-vlan [ethernet ]
Specify the variable in the following formats:
• PowerConnect B-Series FCX stackable switches –
You can list all of the ports individually, use the keyword to to specify ranges of ports, or a
combination of both.
Configuring port flap dampening
Port Flap Dampening increases the resilience and availability of the network by limiting the number
of port state transitions on an interface.
48
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic port parameters
2
If the port link state toggles from up to down for a specified number of times within a specified
period, the interface is physically disabled for the specified wait period. Once the wait period
expires, the port link state is re-enabled. However, if the wait period is set to zero (0) seconds, the
port link state will remain disabled until it is manually re-enabled.
Configuration notes
• When a flap dampening port becomes a member of a trunk group, that port, as well as all
other member ports of that trunk group, will inherit the primary port configuration. This means
that the member ports will inherit the primary port flap dampening configuration, regardless of
any previous configuration.
• The Dell PowerConnect device counts the number of times a port link state toggles from "up to
down", and not from "down to up".
• The sampling time or window (the time during which the specified toggle threshold can occur
before the wait period is activated) is triggered when the first "up to down" transition occurs.
• "Up to down" transitions include UDLD-based toggles, as well as the physical link state.
Configuring port flap dampening on an interface
This feature is configured at the interface level.
PowerConnect(config)# interface ethernet 2/1
PowerConnect(config-if-e10000-2/1)# link-error-disable 10 3 10
Syntax: [no] link-error-disable
The is the number of times a port link state goes from up to down and down to
up before the wait period is activated. Enter a value from 1 - 50.
The is the amount of time during which the specified toggle threshold can
occur before the wait period is activated. The default is 0 seconds. Enter 1 – 65535 seconds.
The is the amount of time the port remains disabled (down) before it becomes
enabled. Enter a value from 0 – 65535 seconds; 0 indicates that the port will stay down until an
administrative override occurs.
Configuring port flap dampening on a trunk
You can configure the port flap dampening feature on the primary port of a trunk using the
link-error-disable command. Once configured on the primary port, the feature is enabled on all
ports that are members of the trunk. You cannot configure port flap dampening on port members
of the trunk.
Enter commands such as the following on the primary port of a trunk.
PowerConnect(config)# interface ethernet 2/1
PowerConnect(config-if-e10000-2/1)# link-error-disable 10 3 10
Re-enabling a port disabled by port flap dampening
A port disabled by port flap dampening is automatically re-enabled once the wait period expires;
however, if the wait period is set to zero (0) seconds, you must re-enable the port by entering the
following command on the disabled port.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
49
2
Configuring basic port parameters
PowerConnect(config)# interface ethernet 2/1
PowerConnect(config-if-e10000-2/1)# no link-error-disable 10 3 10
Displaying ports configured with port flap dampening
Ports that have been disabled due to the port flap dampening feature are identified in the output of
the show link-error-disable command. The following shows an example output.
PowerConnect# show link-error-disable
Port 2/1 is forced down by link-error-disable.
Use the show link-error-disable all command to display the ports with the port flap dampening
feature enabled.
For PowerConnect Stackable devices, the output of the command shows the following.
PowerConnect# show link-error-disable all
Port8/1 is configured for link-error-disable
threshold:1, sampling_period:10, waiting_period:0
Port8/2 is configured for link-error-disable
threshold:1, sampling_period:10, waiting_period:0
Port8/3 is configured for link-error-disable
threshold:1, sampling_period:10, waiting_period:0
Port8/4 is configured for link-error-disable
threshold:1, sampling_period:10, waiting_period:0
Port8/5 is configured for link-error-disable
threshold:4, sampling_period:10, waiting_period:2
Port8/9 is configured for link-error-disable
threshold:2, sampling_period:20, waiting_period:0
Table 10 defines the port flap dampening statistics displayed by the show link-error-disable all
command.
TABLE 10
50
Output of show link-error-disable
This column...
Displays...
Port #
The port number.
Threshold
The number of times the port link state will go from up to down and
down to up before the wait period is activated.
Sampling-Time
The number of seconds during which the specified toggle threshold can
occur before the wait period is activated.
Shutoff-Time
The number of seconds the port will remain disabled (down) before it
becomes enabled. A zero (0) indicates that the port will stay down until
an administrative override occurs.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic port parameters
TABLE 10
2
Output of show link-error-disable (Continued)
This column...
State
Counter
Displays...
The port state can be one of the following:
Idle – The link is normal and no link state toggles have been
detected or sampled.
• Down – The port is disabled because the number of sampled errors
exceeded the configured threshold.
• Err – The port sampled one or more errors.
•
•
•
•
If the port state is Idle, this field displays N/A.
If the port state is Down, this field shows the remaining value of the
shutoff timer.
If the port state is Err, this field shows the number of errors
sampled.
Syntax: show link-error-disable [all]
Example
PowerConnect# show interface ethernet 15
GigabitEthernet15 is up, line protocol is up
Link Error Dampening is Enabled
Hardware is GigabitEthernet, address is 00e0.5200.010e (bia 00e0.5200.010e)
Configured speed auto, actual 1Gbit, configured duplex fdx, actual fdx
Configured mdi mode AUTO, actual MDIX
PowerConnect# show interface ethernet 17
GigabitEthernet17 is ERR-DISABLED, line protocol is down
Link Error Dampening is Enabled
Hardware is GigabitEthernet, address is 00e0.5200.010e (bia 00e0.5200.010e)
Configured speed auto, actual unknown, configured duplex fdx, actual unknown
The line “Link Error Dampening” displays “Enabled” if port flap dampening is enabled on the port
or “Disabled” if the feature is disabled on the port. The feature is enabled on the ports in the two
examples above. Also, the characters “ERR-DISABLED” is displayed for the “GbpsEthernet” line if
the port is disabled because of link errors.
Syntax: show interface ethernet
The ERR-DIS entry under the “Link” column indicates the port is down due to link errors.
Syslog messages for port flap dampening
The following Syslog messages are generated for port flap dampening.
• If the threshold for the number of times that a port link toggles from “up” to “down” then
“down” to “up” has been exceeded, the following Syslog message is displayed.
0d00h02m10s:I:ERR_DISABLE: Link flaps on port ethernet 16 exceeded threshold;
port in err-disable state
• If the wait time (port is down) expires and the port is brought up the following Syslog message
is displayed.
0d00h02m41s:I:ERR_DISABLE: Interface ethernet 16, err-disable recovery timeout
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
51
2
Configuring basic port parameters
Port loop detection
This feature allows the Dell PowerConnect device to disable a port that is on the receiving end of a
loop by sending test packets. You can configure the time period during which test packets are sent.
Strict mode and loose mode
There are two types of loop detection; Strict Mode and Loose Mode. In Strict Mode, a port is
disabled only if a packet is looped back to that same port. Strict Mode overcomes specific
hardware issues where packets are echoed back to the input port. In Strict Mode, loop detection
must be configured on the physical port.
In Loose Mode, loop detection is configured on the VLAN of the receiving port. Loose Mode
disables the receiving port if packets originate from any port or VLAN on the same device. The VLAN
of the receiving port must be configured for loop detection in order to disable the port.
Recovering disabled ports
Once a loop is detected on a port, it is placed in Err-Disable state. The port will remain disabled
until one of the following occurs:
• You manually disable and enable the port at the Interface Level of the CLI.
• You enter the command clear loop-detection. This command clears loop detection statistics
and enables all Err-Disabled ports.
• The device automatically re-enables the port. To set your device to automatically re-enable
Err-Disabled ports, refer to “Configuring the device to automatically re-enable ports” on
page 53.
Configuration notes
• Loopback detection packets are sent and received on both tagged and untagged ports.
Therefore, this feature cannot be used to detect a loop across separate devices.
The following information applies to Loose Mode loop detection:
• With Loose Mode, two ports of a loop are disabled.
• Different VLANs may disable different ports. A disabled port affects every VLAN using it.
• Loose Mode floods test packets to the entire VLAN. This can impact system performance if too
many VLANs are configured for Loose Mode loop detection.
NOTE
Dell recommends that you limit the use of Loose Mode. If you have a large number of VLANS,
configuring loop detection on all of them can significantly affect system performance because of the
flooding of test packets to all configured VLANs. An alternative to configuring loop detection in a
VLAN-group of many VLANs is to configure a separate VLAN with the same tagged port and
configuration, and enable loop detection on this VLAN only.
NOTE
When loop detection is used with L2 loop prevention protocols, such as spanning tree (STP), the L2
protocol takes higher priority. Loop detection cannot send or receive probe packets if ports are
blocked by L2 protocols, so it does not detect L2 loops when STP is running because loops within a
VLAN have been prevented by STP. Loop detection running in Loose Mode can detect and break L3
52
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic port parameters
2
loops because STP cannot prevent loops across different VLANs. In these instances, the ports are
not blocked and loop detection is able to send out probe packets in one VLAN and receive packets
in another VLAN. In this way, loop detection running in Loose Mode disables both ingress and egress
ports.
Enabling loop detection
Use the loop-detection command to enable loop detection on a physical port (Strict Mode) or a
VLAN (Loose Mode). Loop detection is disabled by default. The following example shows a Strict
Mode configuration.
PowerConnect(config)# interface ethernet 1/1
PowerConnect(config-if-e1000-1/1)# loop-detection
The following example shows a Loose Mode configuration.
PowerConnect(config)# vlan20
PowerConnect(config-vlan-20)# loop-detection
By default, the port will send test packets every one second, or the number of seconds specified by
the loop-detection-interval command. Refer to “Configuring a global loop detection interval” on
page 53.
Syntax: [no] loop-detection
Use the [no] form of the command to disable loop detection.
Configuring a global loop detection interval
The loop detection interval specifies how often a test packet is sent on a port. When loop detection
is enabled, the loop detection time unit is 0.1 second, with a default of 10 (one second). The range
is from 1 (one tenth of a second) to 100 (10 seconds). You can use the show loop-detection status
command to view the loop detection interval.
To configure the global loop detection interval, enter a command similar to the following.
PowerConnect(config)# loop-detection-interval 50
This command sets the loop-detection interval to 5 seconds (50 x 0.1).
To revert to the default global loop detection interval of 10, enter one of the following.
PowerConnect(config)# loop-detection-interval 10
OR
PowerConnect(config)# no loop-detection-interval 50
Syntax: [no] loop-detection-interval
where is a value from 1 to 100. The system multiplies your entry by 0.1 to calculate the
interval at which test packets will be sent.
Configuring the device to automatically re-enable ports
To configure the Dell PowerConnect device to automatically re-enable ports that were disabled
because of a loop detection, enter the following command.
PowerConnect(config)# errdisable recovery cause loop-detection
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
53
2
Configuring basic port parameters
The above command will cause the Dell PowerConnect device to automatically re-enable ports that
were disabled because of a loop detection. By default, the device will wait 300 seconds before
re-enabling the ports. You can optionally change this interval to a value from 10 to 65535
seconds. Refer to “Specifying the recovery time interval” on page 54.
Syntax: [no] errdisable recovery cause loop-detection
Use the [no] form of the command to disable this feature.
Specifying the recovery time interval
The recovery time interval specifies the number of seconds the Dell PowerConnect device will wait
before automatically re-enabling ports that were disabled because of a loop detection. (Refer to
“Configuring the device to automatically re-enable ports” on page 53.) By default, the device will
wait 300 seconds. To change the recovery time interval, enter a command such as the following.
PowerConnect(config)# errdisable recovery interval 120
The above command configures the device to wait 120 seconds (2 minutes) before re-enabling the
ports.
To revert back to the default recovery time interval of 300 seconds (5 minutes), enter one of the
following commands.
PowerConnect(config)# errdisable recovery interval 300
OR
PowerConnect(config)# no errdisable recovery interval 120
Syntax: [no] errdisable recovery interval
where is a number from 10 to 65535.
Clearing loop-detection
To clear loop detection statistics and re-enable all ports that are in Err-Disable state because of a
loop detection, enter the following command.
PowerConnect# clear loop-detection
Displaying loop-detection information
Use the show loop-detection status command to display loop detection status, as shown.
PowerConnect# show loop-detection status
loop detection packets interval: 10 (unit 0.1 sec)
Number of err-disabled ports: 3
You can re-enable err-disable ports one by one by "disable" then "enable"
under interface config, re-enable all by "clear loop-detect", or
configure "errdisable recovery cause loop-detection" for automatic recovery
index port/vlan status
#errdis sent-pkts recv-pkts
1
1/13
untag, LEARNING
0
0
0
2
1/15
untag, BLOCKING
0
0
0
3
1/17
untag, DISABLED
0
0
0
4
1/18
ERR-DISABLE by itself
1
6
1
5
1/19
ERR-DISABLE by vlan 12
0
0
0
6
vlan12
2 ERR-DISABLE ports
2
24
2
54
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuring basic port parameters
2
If a port is errdisabled in Strict mode, it shows “ERR-DISABLE by itself”. If it is errdisabled due to its
associated vlan, it shows “ERR-DISABLE by vlan ?”
The following command displays the current disabled ports, including the cause and the time.
PowerConnect# show loop-detection disable
Number of err-disabled ports: 3
You can re-enable err-disable ports one by one by "disable" then "enable"
under interface config, re-enable all by "clear loop-detect", or
configure "errdisable recovery cause loop-detection" for automatic recovery
index port
caused-by
disabled-time
1
1/18
itself
00:13:30
2
1/19
vlan 12
00:13:30
3
1/20
vlan 12
00:13:30
This example shows the disabled ports, the cause, and the time the port was disabled. If
loop-detection is configured on a physical port, the disable cause will show “itself”. For VLANs
configured for loop-detection, the cause will be a VLAN.
The following command shows the hardware and software resources being used by the
loop-detection feature.
Vlans configured loop-detection use 1 HW MAC
Vlans not configured but use HW MAC: 1 10
configuration pool
linklist pool
alloc in-use
16
6
16
10
avail get-fail
10
0
6
0
limit
3712
3712
get-mem
6
10
size init
15
16
16
16
Displaying loop detection resource information
Use the show loop-detection resource command to display the hardware and software resource
information on loop detection.
PowerConnect# show loop-detection resource
Vlans configured loop-detection use 1 HW MAC
Vlans not configured but use HW MAC: 1 10
configuration pool
linklist pool
alloc in-use
16
6
16
10
avail get-fail
10
0
6
0
limit
3712
3712
get-mem
6
10
size init
15
16
16
16
Syntax: show loop-detection resource
Table 11 describes the output fields for this command.
TABLE 11
Field definitions for the show loop-detection resource command
This field...
Describes...
This command displays the following information for the configuration pool and the linklist pool.
alloc
Memory allocated
in-use
Memory in use
avail
Available memory
get-fail
The number of get requests that have failed
limit
The maximum memory allocation
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
55
2
Configuring basic port parameters
TABLE 11
Field definitions for the show loop-detection resource command (Continued)
This field...
Describes...
get-mem
The number of get-memory requests
size
The size
init
The number of requests initiated
Syslog message
The following message is logged when a port is disabled due to loop detection. This message also
appears on the console.
loop-detect: port ?\?\? vlan ?, into errdisable state
The Errdisable function logs a message whenever it re-enables a port.
56
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Chapter
Operations, Administration, and Maintenance
3
Table 12 lists the individual Dell PowerConnect switches and the operations, administration, and
maintenance features they support.
TABLE 12
Supported operations, administration, and maintenance features
Feature
PowerConnect B-Series FCX
Flash and boot code verification
Yes
Flash image verification
Yes
Software upgrade via CLI
Yes
Software upgrade via SNMP
Yes
Hitless management:
• Hitless switchover
• Hitless failover
• Hitless OS upgrade
Yes
Refer to“PowerConnect B-Series FCX hitless
stacking” on page 162
Block size for TFTP file transfers
Yes
Software reboot
Yes
Show boot preference
Yes
Load and save configuration files
Yes
System reload scheduling
Yes
Diagnostic error codes and remedies for
TFTP transfers
Yes
IPv4 ping
Yes
IPv4 traceroute
Yes
Overview
For easy software image management, all Dell PowerConnect devices support the download and
upload of software images between the flash modules on the devices and a Trivial File Transfer
Protocol (TFTP) server on the network.
Dell PowerConnect devices have two flash memory modules:
• Primary flash – The default local storage device for image files and configuration files.
• Secondary flash – A second flash storage device. You can use the secondary flash to store
redundant images for additional booting reliability or to preserve one software image while
testing another one.
Only one flash device is active at a time. By default, the primary image will become active upon
reload.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
57
3
Determining the software versions installed and running on a device
You can update the software contained on a flash module using TFTP to copy the update image
from a TFTP server onto the flash module. In addition, you can copy software images and
configuration files from a flash module to a TFTP server.
NOTE
Dell PowerConnect devices are TFTP clients but not TFTP servers. You must perform the TFTP
transaction from the Dell PowerConnect device. You cannot “put” a file onto the Dell PowerConnect
device using the interface of your TFTP server.
NOTE
If you are attempting to transfer a file using TFTP but have received an error message, refer to
“Diagnostic error codes and remedies for TFTP transfers” on page 75.
Determining the software versions installed and running on a device
Use the following methods to display the software versions running on the device and the versions
installed in flash memory.
Determining the flash image version running on the device
To determine the flash image version running on a device, enter the show version command at any
level of the CLI. Some examples are shown below.
Compact devices
To determine the flash image version running on a Compact device, enter the show version
command at any level of the CLI. The following shows an example output.
PowerConnect#show version
SW: Version 7.2.00aT53 Copyright (c) 2009 Brocade Communications Systems, Inc.
Compiled on Mar 26 2003 at 13:50:31 labeled as FER0 7.2.00a
(3089381 bytes) from Primary fer 7.2.00a.bin
HW: Stackable FES2402-PREM-ILP
==========================================================================
330 MHz Power PC processor 8245 (version 129/1014) 66 MHz bus
512 KB boot flash memory
16384 KB code flash memory
128 MB DRAM
Monitor Option is on
The system uptime is 4 days 4 hours 8 minutes 33 seconds
The system : started=warm start
The version information is shown in bold type in this example:
• “ 7.2.00aT53” indicates the flash code version number. The “T53” is used by Dell for record
keeping.
• “labeled as FER07200a” indicates the flash code image label. The label indicates the image
type and version and is especially useful if you change the image file name.
• “Primary fer07200a.bin” indicates the flash code image file name that was loaded.
58
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Determining the software versions installed and running on a device
3
Determining the boot image version running on the device
To determine the boot image running on a device, enter the show flash command at any level of the
CLI. The following shows an example output.
PowerConnect#show flash
Active Management Module (Slot 9):
Compressed Pri Code size = 3613675, Version 03.1.00aT3e3 (sxr03100a.bin)
Compressed Sec Code size = 2250218, Version 03.1.00aT3e1 (sxs03100a.bin)
Compressed BootROM Code size = 524288, Version 03.0.01T3e5
Code Flash Free Space = 9699328
Standby Management Module (Slot 10):
Compressed Pri Code size = 3613675, Version 03.1.00aT3e3 (sxr03100a.bin)
Compressed Sec Code size = 2250218, Version 03.1.00aT3e1 (sxs03100a.bin)
Compressed BootROM Code size = 524288, Version 03.0.01T3e5
Code Flash Free Space = 524288
The boot code version is shown in bold type.
Determining the image versions installed in flash memory
Enter the show flash command to display the boot and flash images installed on the device. An
example of the command output is shown in “Determining the boot image version running on the
device” on page 59:
• The “Compressed Pri Code size” line lists the flash code version installed in the primary flash
area.
• The “Compressed Sec Code size” line lists the flash code version installed in the secondary
flash area.
• The “Boot Monitor Image size” line lists the boot code version installed in flash memory. The
device does not have separate primary and secondary flash areas for the boot image. The
flash memory module contains only one boot image.
If TFTP was used to install the file on the Dell PowerConnect device, the path may also be displayed
with the filename in the show flash output. For example (path1/SXR05100.bin).
NOTE
To minimize the boot-monitor image size on PowerConnect devices, the ping and tftp
operations performed in the boot-monitor mode are restricted to copper ports on the
PowerConnect Chassis management modules and to copper ports on the PowerConnect
stackable switch combination copper and fiber ports. The fiber ports on these devices do not
have the ability to ping or tftp from the boot-monitor mode.
Flash image verification
The Flash Image Verification feature allows you to verify boot images based on hash codes, and to
generate hash codes where needed. This feature lets you select from three data integrity
verification algorithms:
• MD5 - Message Digest algorithm (RFC 1321)
• SHA1 - US Secure Hash Algorithm (RFC 3174)
• CRC - Cyclic Redundancy Checksum algorithm
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
59
3
Determining the software versions installed and running on a device
CLI commands
Use the following command syntax to verify the flash image:
Syntax: verify md5 | sha1 | crc32 | primary | secondary []
•
•
•
•
•
•
•
md5 – Generates a 16-byte hash code
sha1 – Generates a 20-byte hash code
crc32 – Generates a 4 byte checksum
ascii string – A valid image filename
primary – The primary boot image (primary.img)
secondary – The secondary boot image (secondary.img)
hash code – The hash code to verify
The following examples show how the verify command can be used in a variety of circumstances.
To generate an MD5 hash value for the secondary image, enter the following command.
PowerConnect#verify md5 secondary
PowerConnect#.........................Done
Size = 2044830, MD5 01c410d6d153189a4a5d36c955653862
To generate a SHA-1 hash value for the secondary image, enter the following command.
PowerConnect#verify sha secondary
PowerConnect#.........................Done
Size = 2044830, SHA1 49d12d26552072337f7f5fcaef4cf4b742a9f525
To generate a CRC32 hash value for the secondary image, enter the following command.
PowerConnect#verify crc32 secondary
PowerConnect#.........................Done
Size = 2044830, CRC32 b31fcbc0
To verify the hash value of a secondary image with a known value, enter the following commands.
PowerConnect#verify md5 secondary 01c410d6d153189a4a5d36c955653861
PowerConnect#.........................Done
Size = 2044830, MD5 01c410d6d153189a4a5d36c955653862
Verification FAILED.
In the previous example, the codes did not match, and verification failed. If verification succeeds,
the output will look like this.
PowerConnect#verify md5 secondary 01c410d6d153189a4a5d36c955653861
PowerConnect#.........................Done
Size = 2044830, MD5 01c410d6d153189a4a5d36c955653861
Verification SUCEEDED.
The following examples show this process for SHA-1 and CRC32 algorithms.
PowerConnect#verify sha secondary 49d12d26552072337f7f5fcaef4cf4b742a9f525
PowerConnect#.........................Done
Size = 2044830, sha 49d12d26552072337f7f5fcaef4cf4b742a9f525
Verification SUCCEEDED.
and
PowerConnect#verify crc32 secondary b31fcbc0
PowerConnect#.........................Done
Size = 2044830, CRC32 b31fcbc0
Verification SUCCEEDED.
60
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Image file types
3
Image file types
This section lists the boot and flash image file types supported and how to install them on the
PowerConnect family of switches. For information about a specific version of code, refer to the
release notes.
TABLE 13
Software image files
Product
Boot image1
Flash image
PowerConnect B-Series FCX
GRZxxxxxx.bin
FCXSxxxxx.bin (Layer 2) or
FCXRxxxxx.bin (Layer 3)
1.
Viewing the contents of flash files
The copy flash console command can be used to display the contents of a configuration file,
backup file, or renamed file stored in flash memory. The file contents are displayed on the console
when the command is entered at the CLI.
To display a list of files stored in flash memory, do one of the following:
• For PowerConnect B-Series FCX devices, enter the show dir command at any level of the CLI, or
enter the dir command at the boot-monitor mode.
The following shows an example command output.
PowerConnect#show dir
133 [38f4] boot-parameter
0 [ffff] bootrom
3802772 [0000] primary
4867691 [0000] secondary
163 [dd8e] stacking.boot
1773 [0d2d] startup-config
1808 [acfa] startup-config.backup
8674340 bytes 7 File(s)
56492032 bytes free
Syntax: show dir
To display the contents of a flash configuration file, enter a command such as the following from
the User EXEC or Privileged EXEC mode of the CLI:
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
61
3
Using SNMP to upgrade software
PowerConnect#copy flash console startup-config.backup
ver ver 7.2.00aT7f1!
stack unit 1
module 1 FCX-24-port-management-module
module 2 FCX-cx4-2-port-16g-module
module 3 FCX-xfp-2-port-16g-module
priority 80
stack-port 1/2/1 1/2/2
stack unit 2
module 1 FCX-48-port-management-module
module 2 FCX-cx4-2-port-16g-module
module 3 FCX-xfp-2-port-16g-module
stack-port 2/2/1 2/2/2
stack enable
!
!
!
!
vlan 1 name DEFAULT-VLAN by port
no spanning-tree
metro-rings 1
metro-ring 1
master
ring-interfaces ethernet 1/1/2 ethernet 1/1/3
enable
!
vlan 10 by port
mac-vlan-permit ethe 1/1/5 to 1/1/6 ethe 2/1/5 to 2/1/6
vlan 20 by port
untagged ethe 1/1/7 to 1/1/8
no spanning-tree
pvlan type primary
pvlan mapping 40 ethe 1/1/8
pvlan mapping 30 ethe 1/1/7
!
vlan 30 by port
untagged ethe 1/1/9 to 1/1/10
no spanning-tree
pvlan type community
!
...
some lines omitted for brevity...
no spanning-tree !
Syntax: copy flash console
For , enter the name of a file stored in flash memory.
Using SNMP to upgrade software
You can use a third-party SNMP management application to upgrade software on a PowerConnect
device.
NOTE
Dell recommends that you make a backup copy of the startup-config file before you upgrade the
software. If you need to run an older release, you will need to use the backup copy of the
startup-config file.
62
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Changing the block size for TFTP file transfers
3
1. Configure a read-write community string on the Dell PowerConnect device, if one is not already
configured. To configure a read-write community string, enter the following command from the
global CONFIG level of the CLI.
snmp-server community ro | rw
where is the community string and can be up to 32 characters long.
2. On the Dell PowerConnect device, enter the following command from the global CONFIG level
of the CLI.
no snmp-server pw-check
This command disables password checking for SNMP set requests. If a third-party SNMP
management application does not add a password to the password field when it sends SNMP
set requests to a Dell PowerConnect device, by default the Dell PowerConnect device rejects
the request.
Changing the block size for TFTP file transfers
When you use TFTP to copy a file to or from a Dell PowerConnect device, the device transfers the
data in blocks of 8192 bytes by default. You can change the block size to one of the following if
needed:
•
•
•
•
•
•
•
•
•
4096
2048
1024
512
256
128
64
32
16
To change the block size for TFTP file transfers, enter a command such as the following at the
global CONFIG level of the CLI.
PowerConnect(config)#flash 2047
set flash copy block size to 2048
Syntax: [no] flash
The software rounds up the value you enter to the next valid power of two, and displays the
resulting value. In this example, the software rounds the value up to 2048.
NOTE
If the value you enter is one of the valid powers of two for this parameter, the software still rounds
the value up to the next valid power of two. Thus, if you enter 2048, the software rounds the value
up to 4096.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
63
3
Rebooting
Rebooting
You can use boot commands to immediately initiate software boots from a software image stored
in primary or secondary flash on a Dell PowerConnect device or from a BootP or TFTP server. You
can test new versions of code on a Dell PowerConnect device or choose the preferred boot source
from the console boot prompt without requiring a system reset.
NOTE
It is very important that you verify a successful TFTP transfer of the boot code before you reset the
system. If the boot code is not transferred successfully but you try to reset the system, the system
will not have the boot code with which to successfully boot.
By default, the Dell device first attempts to boot from the image stored in its primary flash, then its
secondary flash, and then from a TFTP server. You can modify this booting sequence at the global
CONFIG level of the CLI using the boot system… command.
To initiate an immediate boot from the CLI, enter one of the boot system… commands.
Configuration notes
• If you are booting the device from a TFTP server through a fiber connection, use the following
command: boot system tftp fiber-port.
• In an IronStack, the boot system tftp command will cause the
system to boot the active unit with the image specified in the command. The rest of the units in
the stack will boot with the primary or secondary image, depending on their boot configuration.
Displaying the boot preference
Use the show boot-preference command to display the boot sequence in the startup config and
running config files. The boot sequence displayed is also identified as either user-configured or the
default.
The following example shows the default boot sequence preference.
PowerConnect #show boot-preference
Boot system preference (Configured):
Use Default
Boot system preference(Default):
Boot system flash primary
Boot system flash secondary
The following example shows a user-configured boot sequence preference.
PowerConnect #show boot-preference
Boot system preference(Configured):
Boot system flash secondary
Boot system tftp 10.1.1.1 FCX04000b1.bin
Boot system flash primary
Boot system preference (Default)
Boot system flash primary
Boot system flash secondary
Syntax: show boot-preference
64
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Loading and saving configuration files
3
The results of the show run command for the configured example above appear as follows.
PowerConnect #show run
Current Configuration:
!
ver 7.2.00aT7f1
!
module 1 FCX-48-port-management-module
module 2 FCX-xfp-2-port-16g-module
module 3 FCX-xfp-2-port-16g-module
!
alias cp=copy tf 10.1.1.1 FCX04000bl.bin pri
!
!
boot sys fl sec
boot sys df 10.1.1.1 FCX04000bl.bin
boot sys fl pri
ip address 10.1.1.4 255.255.255.0
snmp-client 10.1.1.1
!
end
Loading and saving configuration files
For easy configuration management, all Dell PowerConnect devices support both the download and
upload of configuration files between the devices and a TFTP server on the network.
You can upload either the startup configuration file or the running configuration file to the TFTP
server for backup and use in booting the system:
• Startup configuration file – This file contains the configuration information that is currently
saved in flash. To display this file, enter the show configuration command at any CLI prompt.
• Running configuration file – This file contains the configuration active in the system RAM but
not yet saved to flash. These changes could represent a short-term requirement or general
configuration change. To display this file, enter the show running-config or write terminal
command at any CLI prompt.
Each device can have one startup configuration file and one running configuration file. The startup
configuration file is shared by both flash modules. The running configuration file resides in DRAM.
When you load the startup-config file, the CLI parses the file three times.
1. During the first pass, the parser searches for system-max commands. A system-max
command changes the size of statically configured memory.
2. During the second pass, the parser implements the system-max commands if present and also
implements trunk configuration commands (trunk command) if present.
3. During the third pass, the parser implements the remaining commands.
Replacing the startup configuration with the running configuration
After you make configuration changes to the active system, you can save those changes by writing
them to flash memory. When you write configuration changes to flash memory, you replace the
startup configuration with the running configuration.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
65
3
Loading and saving configuration files
To replace the startup configuration with the running configuration, enter the following command
at any Enable or CONFIG command prompt.
PowerConnect#write memory
Replacing the running configuration with the startup configuration
If you want to back out of the changes you have made to the running configuration and return to
the startup configuration, enter the following command at the Privileged EXEC level of the CLI.
PowerConnect#reload
Logging changes to the startup-config file
You can configure a Dell PowerConnect device to generate a Syslog message when the
startup-config file is changed. The trap is enabled by default.
The following Syslog message is generated when the startup-config file is changed.
startup-config was changed
If the startup-config file was modified by a valid user, the following Syslog message is generated.
startup-config was changed by
To disable or re-enable Syslog messages when the startup-config file is changed, use the following
command.
Syntax: [no] logging enable config-changed
Copying a configuration file to or from a TFTP server
To copy the startup-config or running-config file to or from a TFTP server, use one of the following
methods.
NOTE
For details about the copy and ncopy commands used with IPv6, refer to “Using the IPv6 copy
command” on page 69and “Using the IPv6 ncopy command” on page 71.
NOTE
You can name the configuration file when you copy it to a TFTP server. However, when you copy a
configuration file from the server to a Dell PowerConnect device, the file is always copied as
“startup-config” or “running-config”, depending on which type of file you saved to the server.
To initiate transfers of configuration files to or from a TFTP server using the CLI, enter one of the
following commands:
• copy startup-config tftp – Use this command to upload a copy of the
startup configuration file from the Layer 2 Switch or Layer 3 Switch to a TFTP server.
• copy running-config tftp – Use this command to upload a copy of
the running configuration file from the Layer 2 Switch or Layer 3 Switch to a TFTP server.
• copy tftp startup-config – Use this command to download a copy of
the startup configuration file from a TFTP server to a Layer 2 Switch or Layer 3 Switch.
66
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Loading and saving configuration files
3
Dynamic configuration loading
You can load dynamic configuration commands (commands that do not require a reload to take
effect) from a file on a TFTP server into the running-config on the Dell PowerConnect device. You
can make configuration changes off-line, then load the changes directly into the device
running-config, without reloading the software.
Usage considerations
• Use this feature only to load configuration information that does not require a software reload
to take effect. For example, you cannot use this feature to change statically configured
memory (system-max command) or to enter trunk group configuration information into the
running-config.
• Do not use this feature if you have deleted a trunk group but have not yet placed the changes
into effect by saving the configuration and then reloading. When you delete a trunk group, the
command to configure the trunk group is removed from the device running-config, but the
trunk group remains active. To finish deleting a trunk group, save the configuration (to the
startup-config file), then reload the software. After you reload the software, then you can load
the configuration from the file.
• Do not load port configuration information for secondary ports in a trunk group. Since all ports
in a trunk group use the port configuration settings of the primary port in the group, the
software cannot implement the changes to the secondary port.
Preparing the configuration file
A configuration file that you create must follow the same syntax rules as the startup-config file the
device creates.
• The configuration file is a script containing CLI configuration commands. The CLI reacts to
each command entered from the file in the same way the CLI reacts to the command if you
enter it. For example, if the command results in an error message or a change to the CLI
configuration level, the software responds by displaying the message or changing the CLI level.
• The software retains the running-config that is currently on the device, and changes the
running-config only by adding new commands from the configuration file. If the running config
already contains a command that is also in the configuration file you are loading, the CLI
rejects the new command as a duplicate and displays an error message. For example, if the
running-config already contains a a command that configures ACL 1, the software rejects ACL
1 in the configuration file, and displays a message that ACL 1 is already configured.
• The file can contain global CONFIG commands or configuration commands for interfaces,
routing protocols, and so on. You cannot enter User EXEC or Privileged EXEC commands.
• The default CLI configuration level in a configuration file is the global CONFIG level. Thus, the
first command in the file must be a global CONFIG command or “ ! ”. The ! (exclamation point)
character means “return to the global CONFIG level”.
NOTE
You can enter text following “ ! “ as a comment. However, the “ !” is not a comment marker. It
returns the CLI to the global configuration level.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
67
3
Loading and saving configuration files
NOTE
If you copy-and-paste a configuration into a management session, the CLI ignores the “ ! “
instead of changing the CLI to the global CONFIG level. As a result, you might get different
results if you copy-and-paste a configuration instead of loading the configuration using TFTP.
• Make sure you enter each command at the correct CLI level. Since some commands have
identical forms at both the global CONFIG level and individual configuration levels, if the CLI
response to the configuration file results in the CLI entering a configuration level you did not
intend, then you can get unexpected results.
For example, if a trunk group is active on the device, and the configuration file contains a
command to disable STP on one of the secondary ports in the trunk group, the CLI rejects the
commands to enter the interface configuration level for the port and moves on to the next
command in the file you are loading. If the next command is a spanning-tree command whose
syntax is valid at the global CONFIG level as well as the interface configuration level, then the
software applies the command globally. Here is an example.
The configuration file contains these commands.
interface ethernet 2
no spanning-tree
The CLI responds like this.
PowerConnect(config)#interface ethernet 2
Error - cannot configure secondary ports of a trunk
PowerConnect(config)#no spanning-tree
PowerConnect(config)#
• If the file contains commands that must be entered in a specific order, the commands must
appear in the file in the required order. For example, if you want to use the file to replace an IP
address on an interface, you must first remove the old address using “no” in front of the ip
address command, then add the new address. Otherwise, the CLI displays an error message
and does not implement the command. Here is an example.
The configuration file contains these commands.
interface ethernet 11
ip address 10.10.10.69/24
The running-config already has a command to add an address to port 11, so the CLI responds
like this.
PowerConnect(config)#interface ethernet 11
PowerConnect(config-if-e1000-11)#ip add 10.10.10.69/24
Error: can only assign one primary ip address per subnet
PowerConnect(config-if-e1000-11)#
To successfully replace the address, enter commands into the file as follows.
interface ethernet 11
no ip address 20.20.20.69/24
ip address 10.10.10.69/24
This time, the CLI accepts the command, and no error message is displayed.
PowerConnect(config)#interface ethernet 11
PowerConnect(config-if-e1000-11)#no ip add 20.20.20.69/24
PowerConnect(config-if-e1000-111)#ip add 10.10.10.69/24
PowerConnect(config-if-e1000-11)
68
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Loading and saving configuration files with IPv6
3
• Always use the end command at the end of the file. The end command must appear on the
last line of the file, by itself.
Loading the configuration information into the running-config
To load the file from a TFTP server, use either of the following commands:
• copy tftp running-config
• ncopy tftp running-config
NOTE
If you are loading a configuration file that uses a truncated form of the CLI command access-list, the
software will not go into batch mode.
For example, the following command line will initiate batch mode.
access-list 131 permit host pc1 host pc2
The following command line will not initiate batch mode.
acc 131 permit host pc1 host pc2
Maximum file sizes for startup-config file and running-config
Each Dell PowerConnect device has a maximum allowable size for the running-config and the
startup-config file. If you use TFTP to load additional information into a device running-config or
startup-config file, it is possible to exceed the maximum allowable size. If this occurs, you will not
be able to save the configuration changes.
The maximum size for the running-config and the startup-config file is 64K each.
To determine the size of a running-config or startup-config file, copy it to a TFTP server, then use the
directory services on the server to list the size of the copied file. To copy the running-config or
startup-config file to a TFTP server, use one of the following commands:
• Commands to copy the running-config to a TFTP server:
• copy running-config tftp
• ncopy running-config tftp
• Commands to copy the startup-config file to a TFTP server:
• copy startup-config tftp
• ncopy startup-config tftp
Loading and saving configuration files with IPv6
This section describes the IPv6 copy and ncopy commands.
Using the IPv6 copy command
The copy command for IPv6 allows you to do the following:
• Copy a file from a specified source to an IPv6 TFTP server
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
69
3
Loading and saving configuration files with IPv6
• Copy a file from an IPv6 TFTP server to a specified destination
Copying a file to an IPv6 TFTP server
You can copy a file from the following sources to an IPv6 TFTP server:
• Flash memory
• Running configuration
• Startup configuration
Copying a file from flash memory
For example, to copy the primary or secondary boot image from the device flash memory to an IPv6
TFTP server, enter a command such as the following.
PowerConnect#copy flash tftp 2001:7382:e0ff:7837::3 test.img secondary
This command copies the secondary boot image named test.img from flash memory to a TFTP
server with the IPv6 address of 2001:7382:e0ff:7837::3.
Syntax: copy flash tftp primary | secondary
The parameter specifies the address of the TFTP server. You must specify this
address in hexadecimal using 16-bit values between colons as documented in RFC 2373.
The parameter specifies the name of the file you want to copy to the IPv6 TFTP
server.
The primary keyword specifies the primary boot image, while the secondary keyword specifies the
secondary boot image.
Copying a file from the running or startup configuration
For example, to copy the running configuration to an IPv6 TFTP server, enter a command such as
the following.
PowerConnect#copy running-config tftp 2001:7382:e0ff:7837::3 newrun.cfg
This command copies the running configuration to a TFTP server with the IPv6 address of
2001:7382:e0ff:7837::3 and names the file on the TFTP server newrun.cfg.
Syntax: copy running-config | startup-config tftp
Specify the running-config keyword to copy the running configuration file to the specified IPv6 TFTP
server.
Specify the startup-config keyword to copy the startup configuration file to the specified IPv6 TFTP
server.
The tftp parameter specifies the address of the TFTP server. You must specify this
address in hexadecimal using 16-bit values between colons as documented in RFC 2373.
The parameter specifies the name of the file that is copied to the IPv6
TFTP server.
Copying a file from an IPv6 TFTP server
You can copy a file from an IPv6 TFTP server to the following destinations:
70
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Loading and saving configuration files with IPv6
3
• Flash memory
• Running configuration
• Startup configuration
Copying a file to flash memory
For example, to copy a boot image from an IPv6 TFTP server to the primary or secondary storage
location in the device flash memory, enter a command such as the following.
PowerConnect#copy tftp flash 2001:7382:e0ff:7837::3 test.img secondary
This command copies a boot image named test.img from an IPv6 TFTP server with the IPv6
address of 2001:7382:e0ff:7837::3 to the secondary storage location in the device flash memory.
Syntax: copy tftp flash primary | secondary
The parameter specifies the address of the TFTP server. You must specify this
address in hexadecimal using 16-bit values between colons as documented in RFC 2373.
The parameter specifies the name of the file you want to copy from the IPv6
TFTP server.
The primary keyword specifies the primary storage location in the device flash memory, while the
secondary keyword specifies the secondary storage location in the device flash memory.
Copying a file to the running or startup configuration
For example, to copy a configuration file from an IPv6 TFTP server to the running or startup
configuration, enter a command such as the following.
PowerConnect#copy tftp running-config 2001:7382:e0ff:7837::3 newrun.cfg overwrite
This command copies the newrun.cfg file from the IPv6 TFTP server and overwrites the running
configuration file with the contents of newrun.cfg.
NOTE
To activate this configuration, you must reload (reset) the device.
Syntax: copy tftp running-config | startup-config [overwrite]
Specify the running-config keyword to copy the running configuration from the specified IPv6 TFTP
server.
The parameter specifies the address of the TFTP server. You must specify this
address in hexadecimal using 16-bit values between colons as documented in RFC 2373.
The parameter specifies the name of the file that is copied from the IPv6 TFTP
server.
The overwrite keyword specifies that the device should overwrite the current configuration file with
the copied file. If you do not specify this parameter, the device copies the file into the current
running or startup configuration but does not overwrite the current configuration.
Using the IPv6 ncopy command
The ncopy command for IPv6 allows you to do the following:
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
71
3
Loading and saving configuration files with IPv6
•
•
•
•
Copy a primary or secondary boot image from flash memory to an IPv6 TFTP server.
Copy the running configuration to an IPv6 TFTP server.
Copy the startup configuration to an IPv6 TFTP server
Upload various files from an IPv6 TFTP server.
Copying a primary or secondary boot Image from flash memory to an IPv6 TFTP
server
For example, to copy the primary or secondary boot image from the device flash memory to an IPv6
TFTP server, enter a command such as the following.
PowerConnect#ncopy flash primary tftp 2001:7382:e0ff:7837::3 primary.img
This command copies the primary boot image named primary.img from flash memory to a TFTP
server with the IPv6 address of 2001:7382:e0ff:7837::3.
Syntax: ncopy flash primary | secondary tftp
The primary keyword specifies the primary boot image, while the secondary keyword specifies the
secondary boot image.
The tftp parameter specifies the address of the TFTP server. You must specify this
address in hexadecimal using 16-bit values between colons as documented in RFC 2373.
The parameter specifies the name of the file you want to copy from flash
memory.
Copying the running or startup configuration to an IPv6 TFTP server
For example, to copy a device running or startup configuration to an IPv6 TFTP server, enter a
command such as the following.
PowerConnect#ncopy running-config tftp 2001:7382:e0ff:7837::3 bakrun.cfg
This command copies a device running configuration to a TFTP server with the IPv6 address of
2001:7382:e0ff:7837::3 and names the destination file bakrun.cfg.
Syntax: ncopy running-config | startup-config tftp
Specify the running-config keyword to copy the device running configuration or the startup-config
keyword to copy the device startup configuration.
The tftp parameter specifies the address of the TFTP server. You must specify this
address in hexadecimal using 16-bit values between colons as documented in RFC 2373.
The parameter specifies the name of the running configuration that is
copied to the IPv6 TFTP server.
Uploading files from an IPv6 TFTP server
You can upload the following files from an IPv6 TFTP server:
• Primary boot image.
• Secondary boot image.
• Running configuration.
72
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Loading and saving configuration files with IPv6
3
• Startup configuration.
Uploading a primary or secondary boot image from an IPv6 TFTP server
For example, to upload a primary or secondary boot image from an IPv6 TFTP server to a device
flash memory, enter a command such as the following.
PowerConnect#ncopy tftp 2001:7382:e0ff:7837::3 primary.img flash primary
This command uploads the primary boot image named primary.img from a TFTP server with the
IPv6 address of 2001:7382:e0ff:7837::3 to the device primary storage location in flash memory.
Syntax: ncopy tftp flash primary | secondary
The tftp parameter specifies the address of the TFTP server. You must specify this
address in hexadecimal using 16-bit values between colons as documented in RFC 2373.
The parameter specifies the name of the file you want to copy from the TFTP
server.
The primary keyword specifies the primary location in flash memory, while the secondary keyword
specifies the secondary location in flash memory.
Uploading a running or startup configuration from an IPv6 TFTP server
For example to upload a running or startup configuration from an IPv6 TFTP server to a device,
enter a command such as the following.
PowerConnect#ncopy tftp 2001:7382:e0ff:7837::3 newrun.cfg running-config
This command uploads a file named newrun.cfg from a TFTP server with the IPv6 address of
2001:7382:e0ff:7837::3 to the device.
Syntax: ncopy tftp running-config | startup-config
The tftp parameter specifies the address of the TFTP server. You must specify this
address in hexadecimal using 16-bit values between colons as documented in RFC 2373.
The parameter specifies the name of the file you want to copy from the TFTP
server.
Specify the running-config keyword to upload the specified file from the IPv6 TFTP server to the
device. The device copies the specified file into the current running configuration but does not
overwrite the current configuration.
Specify the startup-config keyword to upload the specified file from the IPv6 TFTP server to the
device. The the device copies the specified file into the current startup configuration but does not
overwrite the current configuration.
Using SNMP to save and load configuration information
You can use a third-party SNMP management application to save and load a configuration on a Dell
PowerConnect device.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
73
3
Scheduling a system reload
1. Configure a read-write community string on the Dell PowerConnect device, if one is not already
configured. To configure a read-write community string, enter the following command from the
global CONFIG level of the CLI.
snmp-server community ro | rw
where is the community string and can be up to 32 characters long.
2. On the Dell device, enter the following command from the global CONFIG level of the CLI.
no snmp-server pw-check
This command disables password checking for SNMP set requests. If a third-party SNMP
management application does not add a password to the password field when it sends SNMP
set requests to a device, by default the Dell device rejects the request.
Erasing image and configuration files
To erase software images or configuration files, use the commands described below. These
commands are valid at the Privileged EXEC level of the CLI:
• erase flash primary erases the image stored in primary flash of the system.
• erase flash secondary erases the image stored in secondary flash of the system.
• erase startup-config erases the configuration stored in the startup configuration file; however,
the running configuration remains intact until system reboot.
Scheduling a system reload
In addition to reloading the system manually, you can configure the Dell PowerConnect device to
reload itself at a specific time or after a specific amount of time has passed.
NOTE
The scheduled reload feature requires the system clock. You can use a Simple Network Time
Protocol (SNTP) server to set the clock or you can set the device clock manually. Refer to “Specifying
a Simple Network Time Protocol (SNTP) server” on page 23 or “Setting the system clock” on
page 25.
Reloading at a specific time
To schedule a system reload for a specific time, use the reload at command. For example, to
schedule a system reload from the primary flash module for 6:00:00 AM, April 1, 2003, enter the
following command at the global CONFIG level of the CLI.
PowerConnect#reload at 06:00:00 04-01-03
Syntax: reload at [primary | secondary]
is the hours, minutes, and seconds.
is the month, day, and year.
primary | secondary specifies whether the reload is to occur from the primary code flash module or
the secondary code flash module. The default is primary.
74
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Diagnostic error codes and remedies for TFTP transfers
3
Reloading after a specific amount of time
To schedule a system reload to occur after a specific amount of time has passed on the system
clock, use reload after command. For example, to schedule a system reload from the secondary
flash one day and 12 hours later, enter the following command at the global CONFIG level of the
CLI.
PowerConnect#reload after 01:12:00 secondary
Syntax: reload after [primary | secondary]
is the number of days, hours, and minutes.
primary | secondary specifies whether the reload is to occur from the primary code flash module or
the secondary code flash module.
Displaying the amount of time remaining before
a scheduled reload
To display how much time is remaining before a scheduled system reload, enter the following
command from any level of the CLI.
PowerConnect#show reload
Canceling a scheduled reload
To cancel a scheduled system reload using the CLI, enter the following command at the global
CONFIG level of the CLI.
PowerConnect#reload cancel
Diagnostic error codes and remedies for TFTP transfers
If an error occurs with a TFTP transfer to or from a Layer 2 Switch or Layer 3 switch, one of the
following error codes displays on the console.
Error
code
Message
Explanation and action
1
Flash read preparation failed.
2
Flash read failed.
A flash error occurred during the download.
Retry the download. If it fails again, contact customer support.
3
Flash write preparation failed.
4
Flash write failed.
5
TFTP session timeout.
TFTP failed because of a time out.
Check IP connectivity and make sure the TFTP server is running.
6
TFTP out of buffer space.
The file is larger than the amount of room on the device or TFTP server.
If you are copying an image file to flash, first copy the other image to
your TFTP server, then delete it from flash. (Use the erase flash... CLI
command at the Privileged EXEC level to erase the image in the flash.)
If you are copying a configuration file to flash, edit the file to remove
unneeded information, then try again.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
75
3
Testing network connectivity
Error
code
Message
Explanation and action
7
TFTP busy, only one TFTP
session can be active.
Another TFTP transfer is active on another CLI session, or Web
management session, or Brocade Network Advisor session.
Wait, then retry the transfer.
8
File type check failed.
You accidentally attempted to copy the incorrect image code into the
system. For example, you might have tried to copy a Chassis image into
a Compact device.
Retry the transfer using the correct image.
16
TFTP remote - general error.
17
TFTP remote - no such file.
The TFTP configuration has an error. The specific error message
describes the error.
Correct the error, then retry the transfer.
18
TFTP remote - access violation.
19
TFTP remote - disk full.
20
TFTP remote - illegal operation.
21
TFTP remote - unknown
transfer ID.
22
TFTP remote - file already
exists.
23
TFTP remote - no such user.
Testing network connectivity
After you install the network cables, you can test network connectivity to other devices by pinging
those devices. You also can observe the LEDs related to network connection and perform trace
routes.
Pinging an IPv4 address
NOTE
This section describes the IPv4 ping command. For details about IPv6 ping, refer to “IPv6 ping” on
page 255.
To verify that a Dell PowerConnect device can reach another device through the network, enter a
command such as the following at any level of the CLI on the Dell PowerConnect device:
PowerConnect> ping 192.33.4.7
Syntax: ping | [source ] [count ] [timeout ] [ttl
] [size ] [quiet] [numeric] [no-fragment] [verify] [data <1-to-4 byte hex>]
[brief [max-print-per-sec ] ]
NOTE
If the device is a Layer 2 Switch or Layer 3 Switch, you can use the host name only if you have already
enabled the Domain Name Server (DNS) resolver feature on the device from which you are sending
the ping. Refer to “Configuring IP” on page 783.
The required parameter is the IP address or host name of the device.
76
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Testing network connectivity
3
The source specifies an IP address to be used as the origin of the ping packets.
The count parameter specifies how many ping packets the device sends. You can specify
from 1 – 4294967296. The default is 1.
The timeout parameter specifies how many milliseconds the Dell PowerConnect device
waits for a reply from the pinged device. You can specify a timeout from 1 – 4294967296
milliseconds. The default is 5000 (5 seconds).
The ttl parameter specifies the maximum number of hops. You can specify a TTL from 1 –
255. The default is 64.
The size parameter specifies the size of the ICMP data portion of the packet. This is the
payload and does not include the header. You can specify from 0 – 4000. The default is 16.
The no-fragment parameter turns on the “don’t fragment” bit in the IP header of the ping packet.
This option is disabled by default.
The quiet parameter hides informational messages such as a summary of the ping parameters
sent to the device and instead only displays messages indicating the success or failure of the ping.
This option is disabled by default.
The verify parameter verifies that the data in the echo packet (the reply packet) is the same as the
data in the echo request (the ping). By default the device does not verify the data.
The data <1 – 4 byte hex> parameter lets you specify a specific data pattern for the payload
instead of the default data pattern, “abcd”, in the packet data payload. The pattern repeats itself
throughout the ICMP message (payload) portion of the packet.
NOTE
For numeric parameter values, the CLI does not check that the value you enter is within the allowed
range. Instead, if you do exceed the range for a numeric value, the software rounds the value to the
nearest valid value.
The brief parameter causes ping test characters to be displayed. The following ping test characters
are supported:
!
Indicates that a reply was received.
.
Indicates that the network server timed out while waiting for a reply.
U
Indicates that a destination unreachable error PDU was received.
I
Indicates that the user interrupted ping.
NOTE
The number of ! characters displayed may not correspond to the number of successful replies
by the ping command. Similarly, the number of . characters displayed may not correspond to
the number of server timeouts that occurred while waiting for a reply. The "success" or
"timeout" results are shown in the display as “Success rate is XX percent (X/Y)".
The optional max-print-per-sec parameter specifies the maximum number of target
responses the Dell PowerConnect device can display per second while in brief mode. You can
specify from 0 – 2047. The default is 511.
NOTE
If you address the ping to the IP broadcast address, the device lists the first four responses to the
ping.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
77
3
Testing network connectivity
Tracing an IPv4 route
NOTE
This section describes the IPv4 traceroute command. For details about IPv6 traceroute, refer to
“IPv6 Traceroute” on page 253.
Use the traceroute command to determine the path through which a Dell PowerConnect device can
reach another device. Enter the command at any level of the CLI.
The CLI displays trace route information for each hop as soon as the information is received.
Traceroute requests display all responses to a given TTL. In addition, if there are multiple equal-cost
routes to the destination, the Dell PowerConnect device displays up to three responses by default.
PowerConnect> traceroute 192.33.4.7
Syntax: traceroute [maxttl ] [minttl ] [numeric] [timeout ]
[source-ip ]
Possible and default values are as follows.
minttl – minimum TTL (hops) value: Possible values are 1 – 255. Default value is 1 second.
maxttl – maximum TTL (hops) value: Possible values are 1 – 255. Default value is 30 seconds.
timeout – Possible values are 1 – 120. Default value is 2 seconds.
numeric – Lets you change the display to list the devices by their IP addresses instead of their
names.
source-ip – Specifies an IP address to be used as the origin for the traceroute.
78
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Chapter
4
Software-based Licensing
Table 14 lists the individual Dell PowerConnect switches and the software licensing features they
support.
TABLE 14
Supported software licensing features
Feature
PowerConnect B-Series FCX
Software-based licensing
Yes
License generation
License query
Deleting a license
Software license terminology
This section defines the key terms used in this chapter.
• Entitlement certificate – The proof-of-purchase certificate (paper-pack) issued by Dell when a
license is purchased. The certificate contains a unique transaction key that is used in
conjunction with the License ID of the Dell PowerConnect device to generate and download a
software license from the Brocade software portal.
• License file – The file produced by the Brocade software portal when the license is generated.
The file is uploaded to the Dell PowerConnect device and controls access to a licensed feature
or feature set.
• License ID (LID) – This is a number that uniquely identifies the Dell PowerConnect device. The
LID is used in conjunction with a transaction key to generate and download a software license
from the Brocade software portal. The software license is tied to the LID of the Dell
PowerConnect device for which the license was ordered and generated.
• Licensed feature – Any hardware or software feature or set of features that require a valid
software license in order to operate on the device.
• Transaction key – This unique key, along with the LID, is used to generate a software license
from the Brocade software portal. The transaction key is issued by Dell when a license is
purchased. The transaction key is delivered according to the method specified when the order
is placed:
• Paper-pack – The transaction key is recorded on an entitlement certificate, which is
mailed to the customer.
If a delivery method was not specified at the time of the order, the key will be delivered via
paper-pack.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
79
4
Software-based licensing overview
Software-based licensing overview
With the introduction of software-based licensing, one or more valid software licenses are required
to run such licensed features on the device.
Dell PowerConnect devices support software-based licensing will use software-based licensing
only, eliminating the need for a customer- or factory-installed EEPROM on the management module
or switch backplane.
Software-based licensing provides increased scalability and rapid deployment of hardware and
software features on the supported Dell family of switches. For example, for premium upgrades, it
is no longer necessary to physically open the chassis and install an EEPROM to upgrade the
system. Instead, the Web is used to generate, download, and install a software license that will
enable premium features on the device.
How software-based licensing works
A permanent license can be ordered pre-installed in a Dell PowerConnect device when first shipped
from the factory, or later ordered and installed by the customer. In either case, additional licenses
can be ordered as needed.
When a license is ordered separately (not pre-installed), an entitlement certificate, along with a
transaction key, are issued to the customer by Dell as proof of purchase. The transaction key and
LID of the Dell PowerConnect device are used to generate a license key from the Brocade software
licensing portal. The license key is contained within a license file, which is downloaded to the
customer’s PC, where the file can then be transferred to a TFTP or SCP server, then uploaded to the
Dell PowerConnect device.
Once a license is installed on the Dell PowerConnect device, it has the following effect:
• For PowerConnect B-Series FCX devices, the license unlocks the licensed feature and it
becomes available immediately. There is no need to reload the software.
License types
The following license types are supported on PowerConnect devices:
• Application-related – Enables premium or advanced features on the device, for example,
advanced Layer 3 for the PowerConnect B-Series FCX devices.
• Normal license – Also called a permanent license, this enables a license-controlled feature to
run on the device indefinitely.
Non-licensed features
Table 15 lists the PowerConnect software images that do not require a license to run on the
device.
TABLE 15
=
80
Software image files that do not require a license
Product
Image filename - No license required
PowerConnect B-Series FCX
FCXSxxxxx.bin (Layer 2) or
FCXRxxxxx.bin (Layer 3)
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Licensed features and part numbers
4
For a list of features supported with these images, refer to the release notes.
Licensed features and part numbers
Table 16 lists the supported licensed features, associated image filenames, and related part
numbers.
NOTE
There are no changes to the part numbers for products with pre-installed (factory-installed) licenses.
These part numbers are listed for reference in the last column of Table 16.
TABLE 16
Product
Licensed features and part numbers
Licensed feature or feature set
PowerConne ADV Layer 3:
• BGP4
ct B-Series
FCX
Image filename
Part numbers for
software license only
Part numbers for hardware with
pre-installed software license
N/A1
5D4KF(DL-FCX-ADVLIC-SW)
9P0D4(DL-FCX624-E-ADV)
GWGVP(DL-FCX-624-I-ADV)
9G27R(DL-FCX624S-ADV)
9WYV5(DL-FCX648-E-ADV)
N2F2W(DL-FCX648-I-ADV)
9464V(DL-FCX648S-ADV)
Licensing rules
This section lists the software licensing rules and caveats related to the Dell PowerConnect devices
that support software-based licensing.
General notes
The following licensing rules apply to all PowerConnect devices that support software licensing:
• A license is tied to the unique LID of the management module or fixed configuration switch for
which the license was ordered. Therefore, a license can be used on one particular device only.
It cannot be used on any other device.
PowerConnect B-Series FCX devices
The following licensing rules apply to PowerConnect B-Series FCX devices:
• Each stack unit in an PowerConnect B-Series FCX IronStack must have a separate software
license for the same licensed feature. For example, if there are eight units in an IronStack,
eight separate licenses must be purchased to run BGP in the stack. Any unit in a stack that
does not have a license to run BGP will be non-operational.
• All joining stack members, as well as the Standby Controller, must have an equal or more
advanced license compared to the Active Controller. A unit with a license that is “inferior” to the
Active Controller will not be able to join the IronStack. A unit with a “superior” license will be
able to join the IronStack, however, that member will not be elected as the Standby Controller.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
81
4
Licensed features and part numbers
For example, if stack member unit 4 does not have a license to run BGP whereas the Active
controller does, unit 4 has an inferior license and will not be allowed to join the stack. Likewise,
if unit 4 has a license to run BGP whereas the Active controller does not, unit 4 has a superior
license and will be allowed to join the stack, but will not be elected as the Standby Controller.
• For hitless stacking limitations with software-based licensing, refer to “Configuration notes and
feature limitations” on page 165.
82
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuration tasks
4
Configuration tasks
This section describes the configuration tasks for generating and obtaining a software license,
then installing it on the Dell PowerConnect device. Perform the tasks in the order listed in Table 17.
TABLE 17
Configuration tasks for software licensing
Configuration task
See...
1
Order the desired license.
For a list of available licenses and associated part
numbers, see “Licensed features and part numbers”
on page 81.
2
When you receive the transaction key, retrieve
the LID of the Dell PowerConnect device.
If you received the transaction key via
paper-pack, record the LID on the entitlement
certificate in the space provided.
“Viewing the License ID (LID)” on page 91
3
Log in to the Brocade software portal to
generate and obtain the license file.
“Obtaining a license” on page 83
4
Upload the license file to the Dell PowerConnect
device.
“Installing a license file” on page 88
5
Verify that the license is installed.
“Verifying the license file installation” on page 88
Obtaining a license
The procedures in this section show how to generate and obtain a software license.
1. Order a license for the desired licensed feature. Refer to Table 16 for a list of valid part
numbers and licensed features.
2. When you receive the paper-pack transaction key, retrieve the LID of your Dell PowerConnect
device by entering the show version command on the device. Example command output is
shown in “Viewing the License ID (LID)” on page 91.”
If you received a paper-pack transaction key, write the LID in the space provided on the
entitlement certificate.
NOTE
Do not discard the entitlement certificate with electronic key. Keep it in a safe place in case it
is needed for technical support or product replacement (RMAs).
3. Log in to the brocade software portal at http://swportal.brocade.com and complete the
software license request. If you do not have a login ID and password, request access by
following the instructions on the screen.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
83
4
Configuration tasks
Figure 5 shows the Software Portal Login window.
FIGURE 5
84
Brocade Software Portal Login window
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Configuration tasks
4
Figure 6 shows the License Management Welcome window that appears after logging in to the
software portal. From this window, mouse over the License Management banner, then
IP/Ethernet, then click on License Generation with Transaction key.
FIGURE 6
License Management Welcome window
License Query
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
85
4
Configuration tasks
Figure 7 shows the IP/Ethernet License Generation window for generating a license using a
transaction key and LID.
FIGURE 7
IP Ethernet License Generation window
Enter the required information in each text box shown in Figure 7.
• For a description of the field, move the mouse pointer over the text box.
• An asterisk next to a field indicates that the information is required.
• You can generate more than one license at a time. For each license request, enter the Unit
Information (Unit ID and transaction key) then click on the Add button.
When you have finished entering the required information, read the End User License
Agreement, then click on the check box to indicate that you have read and accept it.
86
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
4
Configuration tasks
Press the Generate button to generate the license. Figure 8 shows the results window, which
displays an order summary and the results of the license request.
• If the license request was successful, the “Status” field will indicate Success and the
“License File” field will contain a hyperlink to the generated license file. The license file will
also be automatically e-mailed to the specified Customer e-mail ID.
• If the license request failed, the “Status” field will indicate the reason it failed and the
action to be taken.
FIGURE 8
IP/Ethernet License Generation Results window
partner501@company.com
partner501@company.com
Success
License Key
4. Download the license file to your PC by either clicking on the hyperlink or saving it from the
e-mail attachment.
5. Upload the license file to the PowerConnect device as instructed in the section “Installing a
license file” on page 88.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
87
4
Deleting a license
Installing a license file
Once you obtain a license file, place it on a TFTP or SCP server to which the Dell PowerConnect
device has access, then use TFTP or SCP to copy the file to the license database of the Dell
PowerConnect device.
Using TFTP to install a license file
To copy a license file from a TFTP server to the license database of the Dell PowerConnect device,
enter a command such as the following at the Privileged EXEC level of the CLI:
PowerConnect# copy tftp license 10.1.1.1 lic.xml
Syntax: copy tftp license
is the address of the IPv4 TFTP server.
is the filename of the license file.
Using Secure Copy (SCP) to install a license
SSH and SCP must be enabled on the Dell PowerConnect device before the procedures in this
section can be performed. For details, see the chapter “Configuring SSH2 and SCP” on page 1423.
To copy a license file from an SCP-enabled client to the license database of the Dell PowerConnect
device, enter a command such as the following on the SCP-enabled client.
c:\scp c:\license\license101 terry@10.1.1.1:license
Syntax: scp @:license
Verifying the license file installation
Use the show license command to verify that the license is installed on the device. Details about
this command are in the section “Viewing the license database” on page 92.
Deleting a license
A license will remain in the license database until it is deleted. If you want to delete a license, Dell
recommends that you first disable the licensed feature before deleting the associated license.
To delete a license, enter a command such as the following at the Privileged EXEC level of the CLI:
PowerConnect# license delete 7
This command immediately removes the license from the license database. The CLI commands
related to the licensed feature will no longer be available from the CLI. The licensed feature will
continue to run as configured until the software is reloaded, at which time the feature will be
disabled and removed from the system. Syslog and trap messages are generated when the license
is deleted.
Syntax: license delete
is a valid license index number. This information can be retrieved from the show
license command output. For more information, refer to “Viewing information about software
licenses” on page 91.
88
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Other licensing options available from the Brocade Software Portal
4
Other licensing options available from the
Brocade Software Portal
This section describes other software licensing tasks supported from the Brocade software portal.
Viewing software license information
You can use the License Query option to view software license information for a particular unit,
transaction key, or both. You can export the report to Excel for sharing or archiving purposes.
Depending on the status of the license, for example whether or not the license was generated, the
report will include the following Information:
•
•
•
•
•
•
•
Hardware part number, serial number, and description
Software part number, serial number, and description
Date the license was installed
Transaction key
LID
Feature name
Product line
To access the License Query option, select it from the License Management Welcome window
shown in Figure 6.
Figure 9 shows the License Query window.
FIGURE 9
License Query window
• To view software license information for a particular unit, enter the LID in the Unit ID field then
click on Search.
• To view software license information for a particular transaction key, enter the unique number
in the Transaction key field then click on Search.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
89
4
Transferring a license
Figure 10 shows an example of the license query results.
FIGURE 10
License Query results window
In this example, the line items for Level 1 display hardware-related information and the line items
for Level 2 display software-related information. If the query was performed before the transaction
key was generated, the first row (Level 1) would not appear as part of the search results. Similarly,
if the query was performed before the license was generated, some of the information in the
second row would not be displayed.
Transferring a license
A license can be transferred between Dell PowerConnect devices if the following conditions are
true:
• The device is under an active support contract, and
• The license is being transferred between two like-models (e.g., from a 24-port model to another
24-port model or from a 48-port model to another 48-port model).
Contact your Dell representative for more information.
Syslog messages and trap information
The following Syslog messages and traps are supported for software-based licensing.
TABLE 18
90
Syslog messages
Message level
Message
Explanation
Informational
License: Package with LID
is added
Indicates that the license package has
been added.
Informational
License: Package with LID
is removed
Indicates that the license package has
been deleted.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Viewing information about software licenses
TABLE 18
4
Syslog messages
Message level
Message
Explanation
Warning
License: Package with LID
expires in days
The trial license is about to expire. This
message will begin to display 3 days before
the expiration date, and every 2 hours on
the last day that the license will expire.
Notification
License: Package with LID
has expired
The trial license has expired.
Viewing information about software licenses
This section describes the show commands associated with software licensing. These commands
are issued on the Dell PowerConnect device, at any level of the CLI.
NOTE
You can also view information about software licenses from the Brocade software portal. Refer to
“Viewing software license information” on page 89.
Viewing the License ID (LID)
Dell PowerConnect devices that ship during and after the release of software licensing will have the
LID imprinted on the label affixed to the device. You also can use the CLI command show version to
view the LID on these devices, and on devices that shipped before the release of software
licensing.
Use the show version command to display the serial number, license, and LID of the device. The
following is example output from an PowerConnect B-Series FCX unit with the license
FCX-ADV-LIC-SW installed.
PowerConnect#show version
Copyright (c) 1996-2010 Brocade Communications Systems, Inc.
UNIT 1: compiled on Mar 30 2010 at 18:39:20 labeled as FCXR07000b1
(5245400 bytes) from Secondary FCXR07000b1.bin
SW: Version 07.0.00b1T7f3
Boot-Monitor Image size = 369286, Version:07.0.01T7f5 (grz07001)
HW: Stackable FCX624SF
==========================================================================
UNIT 1: SL 1: FCX-24GS 24-port Management Module
Serial #: PR320400289
license: FCX_adv_router_soft_package
(lid: rtihfjffhno)
P-ENGINE 0: type DB10, rev 01
==========================================================================
UNIT 1: SL 2: FCX-2XGC 2-port 16G Module (2-CX4)
==========================================================================
800 MHz Power PC processor 8544E (version 33/0022) 400 MHz bus
65536 KB flash memory
256 MB DRAM
Monitor Option is on
STACKID 1 system uptime is 16 hours 35 minutes 25 seconds
The system : started=warm start reloaded=by "reload"
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
91
4
Viewing information about software licenses
Viewing the license database
To display general information about all software licenses in the license database, use the show
license command. The following shows example output.
PowerConnect#show license
-----------------------------------------------------------------------------Index Package
Lid
Status
License
License
Name
Type
Period
-----------------------------------------------------------------------------1
FCX624-ADV-LIC-SW
egut-cd0J
active
normal
unlimited
2
FCX624-ADV-LIC-SW
egut-cd0J
valid
normal
unlimited
To display detailed information about a particular license, use the show license
command. The following shows example output.
PowerConnect#show license 1
Syntax: show license []
The following table describes the information displayed by the show license command.
TABLE 19
Output from the show license command
This field...
Displays...
Index
The license hash number that uniquely identifies the license.
Package Name
The package name for the license.
Lid
The license ID. This number is embedded in the Dell PowerConnect
device.
Status
Indicates the status of the license:
Valid – A license is valid if the LID matches the serial number of the
device for which the license was purchased, and the package name
is recognized by the system.
• Invalid – The LID does not match the serial number of the device
for which the license was purchased.
• Active – The license is valid and in effect on the device.
• Not used – The license is not in effect on the device.
• Expired – For trial licenses only, this indicates that the trial license
has expired.
•
License Type
Indicates whether the license is normal (permanent) or trial (temporary).
License Period
If the license type is trial (temporary), this field will display the number of
days the license is valid. If the license type is normal (permanent), this
field will display “unlimited”.
Trial license information
The following details display in the output of the show license command.
92
+ days used
The number of days the trial license has been in effect.
+ hours used
The number of hours the trial license has been in effect.
+ days left
The number of days left before the trial license expires.
+ hours left
The number of hours left before the trial license expires.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Viewing information about software licenses
4
Viewing software packages installed in the device
Use the show version command to view the software packages that are currently installed in the
device.
NOTE
The software package name is not the same as the license name.
PowerConnect#show version
Copyright (c) 1996-2010 Brocade Communications Systems, Inc.
UNIT 1: compiled on Mar 30 2010 at 18:39:20 labeled as FCXR07000b1
(5245400 bytes) from Secondary FCXR07000b1.bin
SW: Version 07.0.00b1T7f3
Boot-Monitor Image size = 369286, Version:07.0.01T7f5 (grz07001)
HW: Stackable FCX624SF
==========================================================================
UNIT 1: SL 1: FCX-24GS 24-port Management Module
Serial #: PR320400289
license: FCX_adv_router_soft_package
(lid: rtihfjffhno)
P-ENGINE 0: type DB10, rev 01
==========================================================================
UNIT 1: SL 2: FCX-2XGC 2-port 16G Module (2-CX4)
==========================================================================
800 MHz Power PC processor 8544E (version 33/0022) 400 MHz bus
65536 KB flash memory
256 MB DRAM
Monitor Option is on
STACKID 1 system uptime is 16 hours 35 minutes 25 seconds
The system : started=warm start reloaded=by "reload"
Table 20 lists the supported software packages.
TABLE 20
Software packages
Product
Software package name
License needed?
PowerConnect B-Series
BASE_SOFT_PACKAGE
No
FCX_FULL_ROUTER_SOFT_PACKAGE
No
FCX_ADV_ROUTER_SOFT_PACKAGE
Yes
FCX
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
93
4
94
Viewing information about software licenses
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Chapter
5
Stackable Devices
Table 21 lists the individual Dell PowerConnect switches and the Ironstack features they support.
TABLE 21
Supported Ironstack features
Feature
PowerConnect B-Series FCX1
Building an IronStack
• Secure-setup
• Automatic configuration
• Manual configuration
Yes
Ironstack management
Yes
Ironstack management MAC address
Yes
Ironstack partitioning
Yes
Persistent MAC address
Yes
Ironstack software upgrade
Yes
Ironstack and stack mismatch
troubleshooting
Yes
Hitless stacking:
• Hitless failover
• Hitless switchover
Yes
1. All PowerConnect B-Series FCX models can be ordered from the factory as -ADV models.
ADV models include support for Layer 3 BGP. PowerConnect B-Series FCX-E and
PowerConnect B-Series FCX-I models require an optional 10 Gbps SFP+ module to support
stacking.
IronStack overview
This section gives a brief overview of IronStack technology, including IronStack terminology. This
section also lists the PowerConnect B-Series FCX models that support stacking.
IronStack technology features
A stack is a group of devices that are connected so that they operate as a single chassis. Dell
IronStack technology features include:
•
•
•
•
•
Management by a single IP address
Support for up to eight units per stack
Flexible stacking ports
Linear and ring stack topology support
Secure-setup utility to make stack setup easy and secure
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
95
5
IronStack overview
•
•
•
•
•
•
•
Active Controller, Standby Controller, and member units in a stack
Active Controller management of entire stack
Active Controller download of software images to all stack units
Standby Controller for stack redundancy
Active Controller maintenance of information database for all stack units
Packet switching in hardware between ports on stack units
All protocols operate on an IronStack in the same way as on a chassis system.
Stackable models
PowerConnect B-Series FCX devices
All PowerConnect B-Series FCXdevices can be active members of a IronStack. PowerConnect
B-Series FCX-E and PowerConnect B-Series FCX-I models require an optional 10 Gbps SFP+ module
to support stacking. For information about how to install PowerConnect B-Series FCX devices, see
the PowerConnect B-FCX Switch Hardware Installation Guide.
All PowerConnect B-Series FCX devices can be ordered from the factory as -ADV models with
support for Layer 3 BGP.
IronStack terminology
Stack unit roles:
• Active Controller - Handles stack management and configures all system- and interface-level
features.
• Future Active Controller - The unit that will take over as Active Controller after the next
reload, if its priority has been changed to the highest priority. When a priority for a stack
unit is changed to be higher than the existing Active Controller, the takeover does not
happen immediately to prevent disruptions in the stack operation.
• Standby Controller - The stack member with the highest priority after the Active Controller. The
Standby Controller takes over if the current Active Controller fails.
• Stack Member - A unit functioning in the stack in a capacity other than Active or Standby
Controller.
• Stack Unit - Any device functioning within the stack, including the Active Controller and Standby
Controller.
• Upstream Stack Unit - An upstream unit is connected to the first stacking port on the
Active Controller. (The left-hand port as you face the stacking ports.)
• Downstream Stack Unit - A downstream unit is connected to the second stacking port on
the Active Controller. (The right-hand port as you face the stacking ports.) General
terminology
• Bootup Role - the role a unit takes during the boot sequence. This role can be standalone,
Active Controller, Standby Controller, or stack member. The Active Controller or a standalone
unit can access the full range of the CLI. Until a stack is formed, the local consoles on the
Standby Controller and stack members provide access to a limited form of the CLI, such as the
96
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
IronStack overview
5
show, stack, and a few debug commands. When the stack is formed, all local consoles are
directed to the Active Controller, which can access the entire CLI. The last line of output from
the show version command indicates the role of a unit, unless it is a standalone unit, in which
case it is not shown. For example:
My stack unit ID = 1, bootup role = active
• Clean Unit - A unit that contains no startup flash configuration or run time configuration. To
erase old configuration information, enter the erase startup-config command and reset the
unit. For PowerConnect B-Series FCX devices, the run-time configuration on a clean unit may
also contain default-port information,
• Control Path - A path across stacking links dedicated to carrying control traffic such as
commands to program hardware or software image data for upgrades. A stack unit must join
the control path to operate fully in the stack.
• Default Port - PowerConnect B-Series FCX devices use the default-port command to define
stacking port candidates.
• Interprocessor Communications (IPC) - The process by which proprietary packets are
exchanged between stack unit CPUs.
• IronStack - A set of stackable units (maximum of eight) and their connected stacking links so
that: all units can be accessed through their common connections, a single unit can manage
the entire stack, and configurable entities, such as VLANs and trunk groups, can have
members on multiple stack units.
• Non-Functioning Stack Unit - A stack unit that is recognized as a stack member, and is
communicating with the Active Controller over the Control Path, but is in a non-functioning
state. Because of this state, traffic from the non-stack ports will not be forwarded into the
stack - they will be dropped or discarded. This may be caused by an image or configuration
mismatch.
• Sequential Connection - Stack unit IDs, beginning with the Active Controller, are sequential. For
example, 1, 3, 4, 6, 7 is sequential if Active Controller is 1. 1, 7, 6, 4, 3 are non-sequential in a
linear topology, but become sequential in a ring topology when counted from the other
direction as: 1, 3, 4, 6, 7. Gaps in numbering are allowed.
• Standalone Unit - A unit that is not enabled for stacking, or an Active Controller without any
Standby Controller or stack members.
• Stacking Link - A cable that connects a stacking port on one unit to a stacking port on another
unit.
• Stack Path - A data path formed across the stacking links to determine the set of stack
members that are present in the stack topology, and their locations in the stack.
• Stacking Port - A physical interface on a stack unit that connects a stacking link. Stacking ports
are point-to-point links that exchange proprietary packets. Stacking ports must be 10 Gbps
Ethernet ports, and cannot be configured for any other purpose while operating as stacking
ports. Dell stacking units contain two ports that can be stacking ports. However, the flexible
stacking port feature also allows you to use one port as a stacking port and the other port as a
regular data port. Refer to “Controlling stack topology” on page 126.
• Stack Slot - slot in a stack is synonymous with line module in a chassis. Table 22 shows the
port and slot designations for PowerConnect stackable devices.
• Stack Topology - A contiguously-connected set of stack units in an IronStack that are currently
communicating with each other. All units that are present in the stack topology appear in
output from the show stack command.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
97
5
Building an IronStack
• Static Configuration - A configuration that remains in the database of the Active Controller even
if the unit it refers to is removed from the stack. Static configurations are derived from the
startup configuration file during the boot sequence, are manually entered, or are converted
from dynamic configurations after a write memory command is issued.
• Dynamic Configuration - A unit configuration that is dynamically learned by a new stack unit
from the Active Controller. A dynamic configuration disappears when the unit leaves the stack.
Building an IronStack
This section describes how to build an IronStack. Before you begin, you should be familiar with the
supported stack topologies and the software requirements. When you are ready to build your stack,
you can go directly to the instructions.
IronStack topologies
IronStack technology supports linear and ring stack topologies. Although stackable units may be
connected in a simple linear topology, Dell recommends a ring topology because it offers the best
redundancy and the most resilient operation.
Mixed unit topologies
For more information about PowerConnect B-Series FCX stack topologies, see “PowerConnect
B-Series FCX stack topologies” on page 98.
PowerConnect B-Series FCX stack topologies
A IronStack can contain all one model, or any combination of the PowerConnect B-Series FCX
models. You can mix 24-port and 48-port FCX devices in a single stack, to a maximum of eight units
per stack.
The procedure for cabling a stack of PowerConnect B-Series FCX devices differs depending on
whether your stack contains PowerConnect B-Series FCX-E and PowerConnect B-Series FCX-I
devices. Figure 11 shows PowerConnect B-FCX-S devices cabled in linear and ring stack topologies.
Note that these devices are cabled from the rear panel. Figure 12 shows PowerConnect B-FCX-E
devices in a ring topology stack. Figure 13 shows PowerConnect B-FCX-E devices in a linear
topology stack.
Figure 14 shows a mixed linear topology stack of PowerConnect B-FCX-S, and PowerConnect
B-FCX-E or PowerConnect B-FCX-I devices. Because the PowerConnect B- FCX-E and PowerConnect
B-FCX-I devices are cabled from the front panel, and PowerConnect B-FCX-S and devices are cabled
from the rear panel by default, you need to reconfigure the default stacking ports on PowerConnect
B-FCX-S devices to the ports on the front panel. For more information about reconfiguring default
stacking ports, see “Configuring default ports on FCX devices” on page 111.
98
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
5
Building an IronStack
FIGURE 11
PowerConnect B-Series FCX linear and ring stack topologies
FIGURE 12
PowerConnect B-FCX-E ring topology stack using SFP+ module ports
Reset
1
Console
PS
Mgmt
1
2
1
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
5
6
2
7
8
9
11
10
12
13
14
15
16
17
18
19
20
21
23
25
27
29
31
33
35
37
39
41
43
45
47
22
24
26
28
30
32
34
36
38
40
42
44
46
48
1
3
5
7
9
11
13
15
17
19
21
23
2
4
6
8
10
12
14
16
18
20
22
24
1
3
5
7
9
11
13
15
17
19
21
23
2
4
6
8
10
12
14
16
18
20
22
24
Diag
PS
Reset
Console
Mgmt
Diag
4
Reset
Console
Mgmt
2
3
1
2
Diag
PS
99
5
Building an IronStack
FIGURE 13
PowerConnect B-FCX-E linear topology stack using SFP+ module ports
Reset
1
Console
PS
Mgmt
1
2
Diag
5
4
Reset
Console
Mgmt
1
7
6
2
8
9
11
10
12
13
15
14
17
16
19
18
20
21
23
25
27
29
31
33
35
37
39
41
43
45
47
22
24
26
28
30
32
34
36
38
40
42
44
46
48
1
3
5
7
9
11
13
15
17
19
21
23
2
4
6
8
10
12
14
16
18
20
22
24
1
3
5
7
9
11
13
15
17
19
21
23
2
4
6
8
10
12
14
16
18
20
22
24
Diag
PS
Reset
Console
Mgmt
FIGURE 14
2
3
1
2
Diag
PS
Mixed linear stack of PowerConnect B-FCX-E devices and PowerConnect B-FCX-S
devices
Device
Reset
1
Console
PS
Mgmt
1
2
Diag
5
4
Reset
Console
Mgmt
2
3
1
6
2
7
8
9
11
10
12
13
14
15
16
17
18
19
20
21
23
25
27
29
31
33
35
37
39
41
43
45
47
22
24
26
28
30
32
34
36
38
40
42
44
46
48
1
3
5
7
9
11
13
15
17
19
21
23
2
4
6
8
10
12
14
16
18
20
22
24
Diag
PS
Software requirements
All units in an IronStack must be running the same software version. See “Troubleshooting an
IronStack” on page 151 for more information.
IronStack construction methods
There are three ways to build an IronStack.
100
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Building an IronStack
5
1. Use the secure-setup utility to form your stack. Secure-setup gives you control over the design
of your stack topology and provides security through password verification. For the
secure-setup procedure, refer to “Scenario 1 - Configuring a three-member IronStack in a ring
topology using secure-setup” on page 101.
2. Automatic stack configuration. With this method, you enter all configuration information,
including the module type and the priorities of all members into the unit you decide will be the
Active Controller and set its priority to be the highest. When you enable stacking on the Active
Controller the stack then forms automatically. This method requires that you start with clean
units (except for the Active Controller) that do not contain startup or run time configurations.
Refer to “Scenario 2 - Configuring a three-member IronStack in a ring topology using the
automatic setup process” on page 105.
3. Manual stack configuration. With this method, you configure every unit individually, and enable
stacking on each unit. Once the units are connected together, they will automatically operate
as an IronStack. With this method the unit with the highest priority becomes the Active
Controller, and ID assignment is determined by the sequence in which you physically connect
the units. Refer to “Scenario 3 - Configuring a three-member IronStack in a ring topology using
the manual configuration process” on page 108.
Configuration notes
Before you configure your IronStack, consider the following guidelines:
• Consider the number of units, and the mix of units your stack will contain, and how the
stacking ports on the units will be connected. For more information about PowerConnect
B-Series FCX devices, refer to the PowerConnect B-FCX Switch Hardware Installation Guide.
• The stack should be physically cabled in a linear or ring topology. Connect only those units that
will be active in the stack.
• When you have a full stack of 8 units, you may need to increase the trap hold time from the
default, which is 60 seconds, to five minutes (300 seconds). This will prevent the loss of initial
boot traps. To increase the trap hold time, use the following command.
PowerConnect# snmp-server enable traps hold 300
Syntax: snmp-server enable traps hold
NOTE
The router image requires more time to boot than the switch image.
Scenario 1 - Configuring a three-member IronStack
in a ring topology using secure-setup
NOTE
.For more detailed information about configuring an PowerConnect B-FCX IronStack, see
“Configuring an FCX IronStack” on page 109.
This scenario describes how to build an IronStack using the secure-setup utility. Secure-setup lets
you easily configure your entire stack through the Active Controller, which propagates the
configuration to all stack members. Secure-setup is the most secure way to build an IronStack, and
gives you the most control over how your stack is built. For example, secure-setup offers three
security features that prevent unauthorized devices from accessing or joining an IronStack:
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
101
5
Building an IronStack
• Authentication of secure-setup packets provides verification that these packets are from
genuine Dell stack unit. MD5-based port verification confirms stacking ports.
• Superuser password is required to allow password-protected devices to become members of
an IronStack.
• The stack disable command. When this command is issued, a unit does not listen for or send
stacking packets, which means that no other device in the network can force the
stacking-disabled unit to join an IronStack.
Secure-setup can also be used to add units to an existing IronStack (refer to “Adding, removing, or
replacing units in an IronStack” on page 147) and to change the stack IDs of stack members (refer
to “IronStack unit identification” on page 122).
When secure-setup is issued on a unit that is not already the Active Controller, this unit becomes
the Active Controller, and, if it does not have an assigned priority, secure-setup assigns it a priority
of 128. Any unit that then tries to join the stack must have an assigned priority less than 128. If
secure-setup discovers a unit with a priority of 128 or higher, it changes the priority to 118.
When secure-setup is issued on a unit that is not already the Active Controller, this unit becomes
the Active Controller. If this unit does not already have an assigned priority, secure-setup will assign
this unit a priority of 128 by default, if no other units in the stack have a priority higher than 128. If
another unit in the stack has a priority of 128 or higher, secure-setup will give the Active Controller
a priority equal to the highest priority unit in the stack (which is by default the Standby Controller).
When the Active Controller and the Standby Controller have identical priorities, during a reset, the
old Active Controller cannot reassume its role from the Standby Controller (which has become the
Active Controller at the reset).
If the previous Active Controller again becomes active, and you want it to resume the role of Active
Controller, you should set the priority for the Standby Controller to a priority lower than 128. If you
do not want the previous Active Controller to remain Active Controller, you can set the same priority
for both Active and Standby Controllers (higher than, or equal to 128). For details, refer to
“IronStack unit priority” on page 123.
NOTE
Secure-setup works for units within a single stack. It does not work across stacks.
Follow the steps given below to configure a three-member stack in a ring topology using
secure-setup.
1. Connect the devices using the stacking ports and stack cabling. For more information refer to
the appropriate hardware installation guides.
2. Power on the units.
3. Connect your console to the intended Active Controller. The unit through which you run
secure-setup becomes the Active Controller by default.
4. Issue the stack enable command on the intended Active Controller.
PowerConnect# config t
PowerConnect(config)# stack enable
PowerConnect(config)# exit
PowerConnect#
102
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Building an IronStack
5
5. Enter the stack secure-setup command. As shown In the following example, this command
triggers a Dell proprietary discovery protocol that begins the discovery process in both
upstream and downstream directions. The discovery process produces a list of upstream and
downstream devices that are available to join the stack. Secure-setup can detect up to 7 units
in each direction (14 total), but since the maximum number of units in a stack is 8, you must
select a maximum of 7 units from both directions.
NOTE
To exit the secure-setup, enter ^C at any time.
You should see output similar to the following.
PowerConnect# stack secure-setup
PowerConnect# Discovering the stack topology...
Current Discovered Topology - RING
Available UPSTREAM units
Hop(s) Type
Mac Address
1
FCX624 0012.f239.2d40
2
FCX624 0012.f2d5.2100
Available DOWNSTREAM units
Hop(s) Type
Mac Address
1
FCX624 0012.f2d5.2100
2
FCX624 0012.f239.2d40
Do you accept the topology (RING) (y/n)?: y
If you accept the topology, you will see output similar to the following.
Selected Topology:
Active Id
Type
1
FCX648
Mac Address
00e0.52ab.cd00
Selected UPSTREAM units
Hop(s) Id
Type
Mac Address
1
3
FCX624 0012.f239.2d40
2
2
FCX624 0012.f2d5.2100
Selected DOWNSTREAM units
Hop(s) Id
Type
Mac Address
1
2
FCX624 0012.f2d5.2100
2
3
FCX624 0012.f239.2d40
Do you accept the unit ids (y/n)?: y
To accept the unit ID assignments, type y. If you do not want to accept the ID assignments, type
n. You can use secure-setup to renumber the units in your stack. Refer to “Renumbering stack
units” on page 149.
If you accept the unit IDs, the stack is formed, and you can see the stack topology using the
show stack command.
PowerConnect# show stack
alone: standalone, D: dynamic config, S: static config
ID
Type
Role
Mac Address
Pri State
Comment
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
103
5
Building an IronStack
1
2
3
S FCX648 active 00e0.52ab.cd00 128 local
D FCX624 standby 0012.f2d5.2100 60 remote
D FCX624 member 0012.f239.2d40
0 remote
Ready
Ready
Ready
active
standby
+---+
+---+
+---+
-2/1| 1 |3/1--2/1| 2 |3/1--2/2| 3 |2/1+---+
+---+
+---+
Current stack management MAC is 00e0.52ab.cd00
NOTE
For field descriptions for the show stack command, refer to “Displaying stack information” on
page 135.
NOTE
In this output, D indicates a dynamic configuration. After you perform a write memory, this display
will change to S, for static configuration.
6. The Active Controller automatically checks all prospective stack members to see if they are
password protected. If a unit is password protected, you will be asked to enter the password
before you can add the unit. If you do not know the password, take one of the following actions:
• Discontinue secure-setup by entering ^C
• Obtain the device password from the administrator
• Continue secure-setup for your stack. The password-protected device and all devices
connected behind it will not be included in the setup process.
In the following example, the second unit is password protected, so you are asked for the
password.
PowerConnect# stack secure-setup
PowerConnect# Discovering the stack topology...
Verifying password for the password protected units...
Found UPSTREAM units
Hop(s) Type
Mac Address
1
2
FCX648 001b.ed5e.c480
2
3
FCX648 00e0.5205.0000
Enter password for FCX648 located at 2 hop(s): ****
Enter the number of the desired UPSTREAM units (1-2)[1]: 2
Selected Topology:
Active Id
Type
1
FCX624
Mac Address
00e0.5201.4000
Selected UPSTREAM units
Hop(s) Id
Type
Mac Address
1
2
FCX648 001b.ed5e.c480
2
3
FCX648 00e0.5205.0000
Do you accept the unit id's (y/n)?: y
104
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Building an IronStack
7.
5
When the Active Controller has finished the authentication process, you will see output that
shows the suggested assigned stack IDs for each member. You can accept these
recommendations, or you can manually configure stack IDs. Enter the show stack command to
verify that all units are in the ready state.
PowerConnect# show stack
alone: standalone, D: dynamic config, S: static
ID
Type
Role
Mac Address
Pri State
1 S FCX624 active 00e0.5201.4000 128 local
2 S FCX648 standby 001b.ed5e.c480
0 remote
3 S FCX648 member 00e0.5205.0000
0 remote
config
Comment
Ready
Ready
Ready
active
standby
+---+
+---+
+---+
-2/1| 1 |3/1--2/1| 2 |3/1--2/2| 3 |2/1|
+---+
+---+
+---+
|
|
|
|-------------------------------------|
Current stack management MAC is 00e0.5201.4000
PowerConnect#
NOTE
For field descriptions for the show stack command, refer to “Displaying stack information” on
page 135.
8. Enter the write memory command on the Active Controller once all of the stack units are
active. This command initiates configuration synchronization, which copies the configuration
file of the Active Controller to the rest of the stack units.
NOTE
The secure-setup process may modify your configuration with information about new units,
stacking ports, etc. For this reason, it is very important to save this information by issuing the
write memory command. If you do not do this, you may lose your configuration information the
next time the stack reboots.
The secure-setup process for your stack is now complete.
NOTE
During the secure-setup process, after 1 minute of inactivity, authentication for stack members will
expire and you will need to restart the process.
Scenario 2 - Configuring a three-member IronStack
in a ring topology using the automatic setup process
PowerConnect B-Series FCX devices determine stacking port candidates through the default-port
setting. An PowerConnect B-Series FCX stackable device with the default port configuration is still
considered a clean unit. To ensure that the device remains a clean unit, do not do a write memory
on the device.
For more detailed information about configuring an FCX IronStack, see “Configuring an FCX
IronStack” on page 109.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
105
5
Building an IronStack
Follow the steps given below to configure a three-member IronStack in a ring topology using
automatic setup process.
1. Power on the devices.
2. This process requires clean devices (except for the Active Controller) that do not contain any
configuration information. To change a device to a clean device, enter the erase startup-config
command and reset the device. When all of the devices are clean, continue with the next step.
NOTE
The physical connections must be sequential, and must match the stack configuration.
3. Log in to the device that you want to be the Active Controller.
4. Configure the rest of the units by assigning ID numbers and module information on each
unit.The stack ID can be any number from 1 through 8.
PowerConnect# config t
PowerConnect(config)# stack unit 2
PowerConnect(config-unit-2)# module 1 FCX-24-port-management-module
PowerConnect(config-unit-2)# module 2 FCX-xfp-1-port-16g-module
PowerConnect(config-unit-2)# module 3 FCX-xfp-1-port-16g-module
PowerConnect(config-unit-2)# stack unit 3
PowerConnect(config-unit-3)# module 1 FCX-24-port-management-module
PowerConnect(config-unit-3)# module 2 FCX-xfp-1-port-16g-module
PowerConnect(config-unit-3)# module 3 FCX-xfp-1-port-16g-module
NOTE
Each stack unit must have a unique ID number.
5. Assign a priority to the Active Controller using the priority command, as shown.
PowerConnect(config)# stack unit 1
PowerConnect(config-stack-1)# priority 255
Syntax: priority
• is a value from 0-255. 255 is the highest priority
6. Assign a priority to the unit that will act as Standby Controller.
PowerConnect# config t
PowerConnect(config)# stack unit 2
PowerConnect(config-unit-2)# priority 240
7.
Do a write memory command to save your settings.
8. Enter the stack enable command.
9. Physically connect the devices in a stack topology, which triggers an election during which the
stack is automatically configured. For more information about cabling the devices, refer to the
appropriate hardware installation guides.
NOTE
When you are configuring individual stack units, you can skip ID numbers. However, the
sequence in which the units are connected must match the order in which you configure them.
Verify your stack configuration by entering the show running config command.
106
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Building an IronStack
5
PowerConnect# show running config
Current configuration:
!
ver 07.2.00a
!
stack unit 1
module 1 FCX-24-port-management-module
priority 255
stack unit 2
module 1 FCX-24-port-management-module
priority 240
stack unit 3
module 1 FCX-24-port-management-module
stack enable
!
NOTE
For field descriptions for the show running config command, refer to “Displaying running
configuration information” on page 143.
10. To see information about your stack, enter the show stack command.
PowerConnect# show stack
alone: standalone, D: dynamic config, S: static
ID
Type
Role
Mac Address
Pri State
1 S FCX624 active 00e0.5200.0100 255 local
2 S FCX624 standby 0012.f2eb.afc0 240 remote
3 S FCX624 member 001b.ed5d.a1c0
0 remote
config
Comment
Ready
Ready
Ready
active
standby
+---+
+---+
+---+
-2/1| 1 |3/1--2/1| 2 |3/1--2/2| 3 |2/1|
+---+
+---+
+---+
|
|
|
|-------------------------------------|
Current stack management MAC is 00e0.5200.0100
PowerConnect#
NOTE
For field descriptions for the show stack command, refer to “Displaying stack information” on
page 135.
Configuration notes for scenario 2
Consider the following items when building a stack using the automatic setup process:
• If a new unit configuration matches other unit configurations, the Active Controller gives this
unit the lowest sequential ID.
• In a ring topology, the same new unit might assume either ID if either direction produces
sequential IDs. For example, in a four-member stack where IDs 2 and 4 are reserved, a new
unit could assume either I2 or ID 4 because either ID 1,2,3 or 1, 3, 4 is sequential.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
107
5
Building an IronStack
Scenario 3 - Configuring a three-member IronStack
in a ring topology using the manual configuration process
NOTE
For more detailed information about configuring an PowerConnect B-Series FCX IronStack, see
“Configuring an FCX IronStack” on page 109
Follow the steps given below to configure a three-member IronStack in a ring topology using the
manual configuration process.
1. Power on the devices. Do not connect the stacking cables at this point.
2. Assign a priority of 255 to unit 1, and a priority of 240 to unit 3 using the priority command. You
do not have to assign a priority to the third device. Enter the stack enable command on each
device. In this example, device 1 will be the Active Controller and device 2 will be the Standby
Controller.
Unit 1
PowerConnect# config t
PowerConnect(config)# stack unit 1
PowerConnect(config-unit-1)# priority 255
PowerConnect(config-unit-1)# stack enable
Enable stacking. This unit actively participates in stacking
PowerConnect(config-unit-1)# write memory
Write startup-config done.
PowerConnect(config-unit-1)# Flash Memory Write (8192 bytes per dot) .Flash to
Flash Done.
PowerConnect(config-unit-1)# end
Unit 2
PowerConnect# config t
PowerConnectconfig)# stack enable
Enable stacking. This unit actively participates in stacking
PowerConnect(config)# Handle election, was standalone --> member,
assigned-ID=2, T=261285 ms.
Write startup-config done.
FCX624-STK Switch(config-unit-1)# Flash Memory Write (8192 bytes per dot)
.Flash to Flash Done.
PowerConnect(config-unit-1)# end
PowerConnect# config t
Unit 3
PowerConnect# config t
PowerConnect(config)# stack unit 1
PowerConnect(config-unit-1)# priority 240
PowerConnect(config-unit-1)# stack enable
Enable stacking. This unit actively participates in stacking
PowerConnect(config-unit-1)# end
3. Connect the devices in a stack topology. The Active Controller will retain its ID. The rest of the
units are assigned unique ID numbers depending on the sequence in which you connected
them.
108
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Building an IronStack
5
For more information about cabling the devices, refer to the appropriate hardware installation
guides.
NOTE
This method does not guarantee sequential stack IDs. If you want to change stack IDs to make them
sequential, you can use secure-setup. Refer to “Renumbering stack units” on page 149.
Configuring an FCX IronStack
Every PowerConnect B-Series FCX-S device contains two default 16 Gbps stacking ports on the rear
panel and two 10 Gbps ports on the front panel that can also be used as stacking ports.
NOTE
PowerConnect B-Series FCX-I and PowerConnect B-Series FCX-E devices can only be used for
stacking if they have an optional 10 Gbps SFP+ module installed in the front panel. These devices
do not have stacking ports on the rear panels.
An PowerConnect B-Series FCX IronStack may contain up to eight 24-port and 48-port devices,
using any combination of the rear panel stacking ports and the front panel optional stacking ports.
For PowerConnect B-Series FCXs devices, to use ports other than the factory-default 16 Gbps ports,
you must define the ports for each device in the run time configuration. You can also configure the
16 Gbps ports to operate as 10 Gbps ports. See “Configuring PowerConnect B-Series FCX stacking
ports” on page 109.
An PowerConnect B-Series FCX “clean unit” may contain a default port configuration, but it is still
considered a clean unit. To preserve this state, do not do a write memory on the unit before you
build the stack. An PowerConnect B-Series FCX device with the default port configuration is still
considered a clean unit. To ensure that the device remains a clean unit, do not do a write memory
on the device. (Write memory adds a startup-config, and the device is no longer a clean unit.)
NOTE
The automatic setup process will not work for PowerConnect B-Series FCX devices that do not
contain the default port information in their clean unit configurations.
Configuring PowerConnect B-Series FCX stacking ports
PowerConnect B-Series FCX-S devices have two 10 Gbps ports on the front panel and two 16 Gbps
ports on the rear panel. All of these ports may be used as stacking ports, however the non-default
ports must be configured as stacking ports when setting up your PowerConnect B-Series FCX-S
IronStack.
PowerConnect B-Series FCX-I and PowerConnect B-Series FCX-E devices do not have 16 Gpbs ports
on the rear panel. These devices may be used in an IronStack by installing the 10 Gbps 4-port SFP+
module in the module slot on the front panel. Once you have installed one of these modules, ports
1 and 2 act as the default stacking ports. However, you can also use these ports to pass regular
traffic, after disabling the stacking default. See “Changing default stacking port configurations” on
page 112.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
109
5
Building an IronStack
NOTE
If you are adding PowerConnect B-Series FCX-E or PowerConnect B-Series FCX-I devices to a stack
containing PowerConnect B-Series FCX-S devices, you must reconfigure the stacking ports on the
PowerConnect B-Series FCX-S devices to be the 10 Gbps ports on the front panel. You can then
connect all of the devices in a stack using front panel ports.
Changing PowerConnect B-Series FCX-S and CX4 ports from 16 Gbps to 10 Gbps
You can configure the 16 Gbps PowerConnect B-Series FCX4 ports to operate as 10 Gbps ports
using the speed-duplex command, as shown in the following example.
Syntax: speed-duplex [10-full | 10-half | 100-full | 100-half | 1000-full-master | 1000-full-slave
|10g-full | auto]
•
•
•
•
•
•
•
•
10-full - 10M, full duplex
10-half - 10M, half duplex
100-full - 100M, full duplex
100-half - 100M, half duplex
1000-full-master - 1G, full duplex, master
1000-full-slave - 1G, full duplex, slave
10g-full - 10G, full duplex
auto - Autonegotiation
NOTE
Both ends of a link must be configured for 10 Gbps for the link to operate as 10 Gbps. If you want
the link to operate as a 16 Gbps link, both ends of the link must be configured for 16 Gbps.
PowerConnect(config-if-e10000-cx4-1/2/1)# speed-duplex 10g-full
PowerConnect(config-if-e10000-cx4-1/2/1)# end
PowerConnect# show int br | in Up
1/1/4
Up
Forward
Full 1G
None No 1
0
001b.f288.0003
1/2/1
Up
Forward
Full 10G
None No 1
0
001b.f288.0019
1/3/1
Up
Forward
Full 10G
None No N/A 0
001b.f288.001b
3/3/1
Up
Forward
Full 10G
None No N/A 0
0024.3814.9df3
mgmt1
Up
None
Full 1G
None No 1
0
001b.f288.0018
PowerConnect# show interface e 1/2/1
16GigabitEthernet1/2/1 is up, line protocol is up
Hardware is 16GigabitEthernet, address is 001b.f288.0019 (bia 001b.f288.0019)
Interface type is 16Gig CX4
Configured speed 10Gbit, actual 10Gbit, configured duplex fdx, actual fdx
Member of L2 VLAN ID 1, port is untagged, port state is FORWARDING
BPDU guard is Disabled, ROOT protect is Disabled
Link Error Dampening is Disabled
STP configured to ON, priority is level0, mac-learning is enabled
Flow Control is enabled
mirror disabled, monitor disabled
Not member of any active trunks
Not member of any configured trunks
No port name
IP MTU 1500 bytes, encapsulation ethernet
300 second input rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
300 second output rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 multicasts, 0 unicasts
0 input errors, 0 CRC, 0 frame, 0 ignored
110
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Building an IronStack
5
0 runts, 0 giants
0 packets output, 0 bytes, 0 underruns
Transmitted 0 broadcasts, 0 multicasts, 0 unicasts
0 output errors, 0 collisions
Relay Agent Information option: Disabled
Changing PowerConnect B-Series FCX-S and PowerConnect B-Series
FCXS-PowerConnect B-Series FCX4 ports from 10 Gbps to 16 Gbps
To change the PowerConnect B-Series FCX4 ports from 10 Gbps back to 16 Gbps, enter the no
speed-duplex 10g command at the interface level of the CLI, as shown in this example.
PowerConnect(config-if-e10000-cx4-1/2/1)# no speed-duplex 10g
PowerConnect(config-if-e10000-cx4-1/2/1)# show interface br | in Up
1/1/4
Up
Forward
Full 1G
None No 1
0
001b.f288.0003
1/2/1
Up
Forward
Full 16G
None No 1
0
001b.f288.0019
1/3/1
Up
Forward
Full 10G
None No N/A 0
001b.f288.001b
3/3/1
Up
Forward
Full 10G
None No N/A 0
0024.3814.9df3
mgmt1
Up
None
Full 1G
None No 1
0
001b.f288.0018
PowerConnect(config-if-e10000-cx4-1/2/1)# show interface e 1/2/1
16GigabitEthernet1/2/1 is up, line protocol is up
Hardware is 16GigabitEthernet, address is 001b.f288.0019 (bia 001b.f288.0019)
Interface type is 16Gig CX4
Configured speed 16Gbit, actual 16Gbit, configured duplex fdx, actual fdx
Member of L2 VLAN ID 1, port is untagged, port state is FORWARDING
BPDU guard is Disabled, ROOT protect is Disabled
Link Error Dampening is Disabled
STP configured to ON, priority is level0, mac-learning is enabled
Flow Control is enabled
mirror disabled, monitor disabled
Not member of any active trunks
Not member of any configured trunks
No port name
IP MTU 1500 bytes, encapsulation ethernet
300 second input rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
300 second output rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 multicasts, 0 unicasts
0 input errors, 0 CRC, 0 frame, 0 ignored
0 runts, 0 giants
0 packets output, 0 bytes, 0 underruns
Transmitted 0 broadcasts, 0 multicasts, 0 unicasts
0 output errors, 0 collisions
Relay Agent Information option: Disabled
PowerConnect(config-if-e10000-cx4-1/2/1)#
Configuring default ports on FCX devices
On FCX devices, the default-port command is used to define stacking port candidates. A stacking
port is always a default port, but a default port may not necessarily be a stacking port. Default
ports can become stacking ports using the secure-setup utility, or through automatic stack
building.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
111
5
Building an IronStack
Secure-setup probe packets can be received by a default port whether or not it is acting as a
stacking port. Stacking packets can be only received by a stacking port (which is also always a
default port). In order to use stacking ports that are not defined in the default configuration, you
must define the port settings for each unit using the default-port command, so that secure-setup
can discover the topology of the stack.
The 4-byte Ethernet preamble for the Ethernet frame is used when a port is configured as a default
stacking port. For non-default ports, the standard 8-byte Ethernet preamble is used. For a default
port that is used as a regular data port, the standard 8-byte Ethernet preamble must be explicitly
enabled on the port using the longpreamble command. For details, refer to “Configuring a default
stacking port to function as a data port” on page 115.
Stackable devices ship with two default stacking ports configured. Use the stack-port command to
select only one of these factory default ports as the stacking port. If you do not configure
stack-port, both default ports will operate as stacking ports.
Use the default-port command to use ports other than the factory default ports as stacking ports.
You must configure default-port on each unit before building a stack. Once you have configured
default-port on all units, you can then use any of the three stack construction methods to build a
stack. The Active Controller then learns the port configuration for each unit.
NOTE
You cannot change the setting for a default port if the port is in use.
Changing default stacking port configurations
For PowerConnect B-Series FCX-E and PowerConnect B-Series FCX-I devices, ports 1 and 2 of the
optional 10 Gbps SFP+ module (slot 2) act as the default stacking ports. You can change the
default stacking ports to 3 and 4 on this module, or disable stacking, on all of the module ports.
The following example changes the default ports on a 10 Gbps module from 1 and 2 to 3 and 4.
PowerConnect 10g-1(config)# stack unit 1
10g-1(config-unit-1)#
10g-1(config-unit-1)# default-ports 1/2/3 - 1/2/4
Table 22 identifies the slot and port designations for each model.
NOTE
PowerConnect B-Series FCX-I and PowerConnect B-Series FCX-E models cannot be used in an
IronStack without the addition of an optional 10 Gbps SFP+ module.
NOTE
The two left ports on the Four-port 10 Gpbs SFP+ module do not pass regular Ethernet traffic by
default. If stacking is not required the stack disable comand must be entered at the global level and
the stack disable CLI command must be configured on these two ports in order for them to pass
regular traffic.
NOTE
If stacking is needed but not all default stacking ports are needed. Specify the stack ports per unit.
For non-stacking ports to be used as regular data port, the long-preamble command should be used
on the non-stacking port interface.
112
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Building an IronStack
TABLE 22
5
Slot and port designations for PowerConnect stackable devices
Device
Slot 1
Slot 2
Slot 3
Slot 4
PowerConnect
B-Series
FCX624S
24 10/100/1000 ports
on front panel
Two 16 Gbps ports on rear
panel
Two 10 Gbps ports
on front panel
N/A
PowerConnect
B-Series
FCX648S
48 10/100/1000 ports
on front panel
Two 16 Gbps ports on rear
panel
Two 10 Gbps ports
on front panel
N/A
PowerConnect
B-Series FCX-E
devices with
four-port 1 Gbps
SFP module
Four-port 1 Gbps SFP
module plus the first four
copper ports act as a
combo port. Slot 1 also
contains the remaining
20 10/100/1000 ports.
N/A
N/A
N/A
PowerConnect
B-Series FCX-I
devices with
four-port 1 Gbps
SFP module
Four-port 1 Gbps SFP
module plus the first four
copper ports act as a
combo port. Slot 1 also
contains the remaining
20 10/100/1000 ports.
N/A
N/A
N/A
PowerConnect
B-Series FCX-E
devices with
four-port 10
Gbps SFP+
module
48 10/100/1000 ports
on front panel
Four-port 10 Gbps SFP+
module (supports
stacking)
N/A
N/A
PowerConnect
B-Series FCX-I
devices with
four-port 10
Gbps SFP+
module
48 10/100/1000 ports
on front panel
Four-port 10 Gbps SFP+
module (supports
stacking)
N/A
N/A
NOTE
Do not connect stacking ports to non-stacking ports. Stacking ports have a proprietary packet
format that renders them incompatible with regular ports even when they are forwarding regular
packets. In linear topologies, make sure that end units have only one stacking port configured
(secure-setup automatically configures only one stacking port for an end unit).
Configuring a single stack port
NOTE
The two left ports on the Four-port 10 Gpbs SFP+ module do not pass regular Ethernet traffic by
default. The stack disable must be entered at the global level and the long preamble command must
be configured on these two ports in order for them to pass regular traffic. Use show stack stack-port
command to confirm port mode.
To configure a single stack port, enter a command similar to the following.
PowerConnect(config)# stack unit 3
PowerConnect(config-unit-3)# stack-port 3/2/1
Syntax: [no] stack-port
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
113
5
Building an IronStack
If you enter an incorrect stack port number, you will get an error similar to the following.
PowerConnectconfig-unit-3)# stack-port 3/4/1
Error! port 3/4/1 is invalid
PowerConnect(config-unit-3)# stack-port 3/2/1
To return both ports to stacking status, enter the no stack-port command on the single stacking
port. This converts both ports to stacking ports. By default, if both ports are stacking ports, they are
displayed by the system only when stacking is enabled. If only one port is configured as a stacking
port, the system always displays this port.
Using secure-setup to build an FCX IronStack
You can use the secure-setup utility to build an PowerConnect B-Series FCX IronStack by
performing the following steps.
1. When you have designated the desired stacking ports and connected your PowerConnect
B-Series FCX units together, on stack unit 1, enter stack enable and stack secure-setup, as
shown.
PowerConnect# stack enable
PowerConnect# stack secure-setup
PowerConnect# Discovering the stack topology...
Available UPSTREAM units
Hop(s) Id
Type
Mac Address
1
new FCX648 0012.f2d6.0511
2
new FCX624
0200.9999.0000
Enter the number of the desired UPSTREAM units (0-2)[0]: 2
Selected Topology:
Active Id
Type
Mac Address
1
FCX624 001b.f2e5.0100
Selected UPSTREAM units
Hop(s) Id
Type
Mac Address
1
2
FCX648 0012.f2d6.0511
2
3
FCX624
0200.9999.0000
Do you accept the unit ids (y/n)?: y
PowerConnect# Election, was alone --> active, assigned-ID=1, total 3 units, my
priority=128
Election, was active, no role change, assigned-ID=1, total 3 units, my
priority=128
reset unit 2: diff bootup id=1
reset unit 3: diff bootup id=1
Election, was alone --> active, assigned-ID=1, total 3 units, my priority=128
Detect stack member 2 capable
Detect stack unit 2 has different startup config flash, will synchronize it
Detect stack unit 3 has different startup config flash, will synchronize it
Done hot swap: Set stack unit 3 to Ready
Done hot swap: Set stack unit 2 to Ready
Synchronize startup config to stack unit 2
Flash Memory Write (8192 bytes per dot).Synchronize startup config to stack
unit 3
Flash Memory Write (8192 bytes per dot). Stack unit 2 Power supply 1 with 4
10000 mwatts capacity is up
Stack unit 2 Power supply 2 is down
114
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Building an IronStack
5
Stack unit 3 Power supply 1 is up
Stack unit 3 Power supply 2 is down
Config changed due to add/del units. Do write mem if you want to keep it
Election, was active, no role change, assigned-ID=1, total 3 units, my
priority=128
PowerConnect#
Config changed due to add/del units. Do write mem if you want to keep it
PowerConnect# show stack
alone: standalone, D: dynamic config, S: static config
ID
Type
Role
Mac Address
Pri State
Comment
1 S FCX624 active 001b.f2e5.0100 128 local
Ready
2 D FCX648 standby 0012.f2d6.0511
0 remote
Ready
3 D FCX624
member 0200.9999.0000
0 remote
Ready
standby
active
+---+
+---+
+---+
| 3 |3/1--3/1| 2 |2/1--2/1| 1 |
+---+
+---+
+---+
Current stack management MAC is 001b.f2e5.0100
PowerConnect# write mem
Write startup-config done.
PowerConnect# Flash Memory Write (8192 bytes per dot) .Flash to Flash Done.
PowerConnect#show stack
alone: standalone, D: dynamic config, S: static config
ID
Type
Role
Mac Address
Pri State
Comment
1 S FCX624 active 001b.f2e5.0100 128 local
Ready
2 S FCX648 standby 0012.f2d6.0511
0 remote
Ready
3 S FCX624
member 0200.9999.0000
0 remote
Ready
standby
active
+---+
+---+
+---+
| 3 |3/1--3/1| 2 |2/1--2/1| 1 |
+---+
+---+
+---+
Current stack management MAC is 001b.f2e5.0100
PowerConnect#
Configuring a default stacking port to function as
a data port
You can configure one of the two default stacking ports as a stacking port and the other port as a
regular data port. By default, the 4-byte Ethernet preamble for the Ethernet frame is used when a
port is configured as a default stacking port. This is done to compensate for extra overhead caused
by stacking protocol. To use a default stacking port as a regular data port, the Ethernet preamble
must be set to 8 bytes.
To configure a default port to use the long preamble, enter the following command at the Interface
level of the CLI:
PowerConnect(config)#int e 1/2/1
PowerConnect(config-if-e10000-1/2/1)#longpreamble
Syntax: [no] longpreamble
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
115
5
Building an IronStack
Use the no form of the command to revert to the 4-byte Ethernet preamble.
Verifying an IronStack configuration
Verifying an PowerConnect B-Series FCX IronStack configuration
The following output shows an example configuration of an PowerConnect B-Series FCX IronStack.
PowerConnect# show stack
alone: standalone, D: dynamic config, S: static config
ID
Type
Role
Mac Address
Pri State
Comment
2 S FCX648 standby 00e0.5202.0000
0 remote
Ready
3 S FCX624 member 00e0.5203.0000
0 remote
Ready
4 S FCX648
member 00e0.5204.0000
0 remote
Ready
5 S FCX648 member 0000.0000.0000
0 remoteReady
8 S FCX648 active 00e0.5201.0000 128 local
Ready
active
standby
+---+
+---+
+---+
+---+
-2/1| 8 |2/2--2/1| 4 |2/2--2/1| 3 |2/2--2/1| 2 |2/2|
+---+
+---+
+---+
+---+
|
|--------------------------------------------------|
Current stack management MAC is 00e0.5201.0000
The next example shows output from the show version command for the same FCX stack.
PowerConnect# show version
Copyright (c) 1996-2009 Brocade Communications Systems, Inc.
UNIT 8: compiled on Jun 17 2009 at 06:23:29 labeled as FCX06000a359
(3578117 bytes) from Primary FCX06000a359.bin
SW: Version 7.2.0a
UNIT 2: compiled on Jun 17 2009 at 06:23:29 labeled as FCX06000a359
(3578117 bytes) from Primary FCX06000a359.bin
SW: Version 7.2.0a
UNIT 3: compiled on Jun 17 2009 at 06:23:29 labeled as FCX06000a359
(3578117 bytes) from Primary FCX06000a359.bin
SW: Version 7.2.0a
UNIT 4: compiled on Jun 17 2009 at 06:23:29 labeled as FCX06000a359
(3578117 bytes) from Primary FCX06000a359.bin
SW: Version 7.2.0a
Boot-Monitor Image size = 365257, Version:06.0.00T7f5 (grz06000)
HW: Stackable FCX648P
==========================================================================
UNIT 2: SL 1: FCX-48G 48-port Management Module
P-ENGINE 0: type DB90, rev 01
P-ENGINE 1: type DB90, rev 01
==========================================================================
UNIT 2: SL 2: FCX-2XGC 2-port 16G Module (2-CX4)
==========================================================================
UNIT 3: SL 1: FCX-24G 24-port Management Module
P-ENGINE 0: type DB90, rev 01
==========================================================================
UNIT 3: SL 2: FCX-2XGC 2-port 16G Module (2-CX4)
==========================================================================
UNIT 3: SL 3: FCX-2XG 2-port 16G Module (2-XFP)
==========================================================================
UNIT 4: SL 1: FCX-48G 48-port Management Module
P-ENGINE 0: type DB90, rev 01
116
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Building an IronStack
5
P-ENGINE 1: type DB90, rev 01
==========================================================================
UNIT 4: SL 2: FCX-2XGC 2-port 16G Module (2-CX4)
==========================================================================
UNIT 4: SL 3: FCX-2XG 2-port 16G Module (2-XFP)
==========================================================================
UNIT 8: SL 1: FCX-48G 48-port Management Module
P-ENGINE 0: type DB90, rev 01
P-ENGINE 1: type DB90, rev 01
==========================================================================
UNIT 8: SL 2: FCX-2XGC 2-port 16G Module (2-CX4)
==========================================================================
800 MHz Power PC processor (version 33/0022) 144 MHz bus
65536 KB flash memory
256 MB DRAM
Monitor Option is on
STACKID 8 system uptime is 21 hours 2 minutes 23 seconds
STACKID 2 system uptime is 21 hours 2 minutes 22 seconds
STACKID 3 system uptime is 21 hours 2 minutes 23 seconds
STACKID 4 system uptime is 21 hours 2 minutes 22 seconds
The system : started=warm start reloaded=by "reload"
My stack unit ID = 8, bootup role = active
*** NOT FOR PRODUCTION ***
NOTE
For field descriptions for the show running config command, refer to “Displaying running
configuration information” on page 143.
NOTE
For field descriptions for the show stack and show stack detail commands, refer to “Displaying
stack information” on page 135.
The output from the show stack command contains a visual diagram of the stack. The dashed
line between ports 1/2/1 and 3/2/1 indicates that this stack is configured in a ring topology. If
the link between ports 1/2/1 and 3/2/1 is lost, the stack topology changes to linear, and the
diagram changes to resemble the following.
active
standby
+---+
+---+
+---+
-2/1| 1 |3/1--2/1| 2 |3/1--2/2| 3 |2/1+---+
+---+
+---+
The interfaces at either of a stack member are stacking ports. If no interface is displayed, it
indicates that there is no stacking port configured. For example, the following diagram shows
that stack units 1 and 3 each have only one stacking port configured.
active
standby
+---+
+---+
+---+
| 1 |3/1--2/1| 2 |3/1--2/2| 3 |
+---+
+---+
+---+
For more detailed information, you can enter the show stack detail command.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
117
5
Managing your IronStack
Managing your IronStack
Your IronStack can be managed through a single IP address. You can manage the stack using this
IP address even if you remove the Active Controller or any member from the stack. You can also
connect to the Active Controller through Telnet or SSH using this address. All management
functions, such as SNMP, use this IP address to acquire MIB information and other management
data.
A Dell IronStack can be configured and managed using the command line interface (CLI) over a
serial connection to a console port, or using Brocade Network Advisor. To determine what version
of Brocade Network Advisor supports IronStack refer to the Brocade Network Advisor User Guide.
Logging in through the CLI
You can access the IronStack and the CLI in two ways:
• Through a direct serial connection to the console port
• Through a local or remote Telnet session using the stack IP address
You can initiate a local Telnet or SNMP connection by attaching a cable to a port and specifying the
assigned management station IP address.
The stacking commands in the CLI are organized into the following levels:
• Global – Commands issued in the global mode are applied to the entire stack.
• Stack Member Configuration Mode – Commands issued in this mode apply to the specified
stack member. Configuration information resides in the Active Controller.
• Configuration Mode – This is where you make configuration changes to the unit. To save
changes across reloads, you need to save them to the Active Controller startup-config file. The
configuration mode contains sub-levels for individual ports, for VLANs, for routing protocols,
and other configuration areas.
NOTE
By default, any user who can open a serial or Telnet connection to the IronStack can access all of
these CLI levels. To secure access, you can configure Enable passwords or local user accounts, or
you can configure the Active Controller to use a RADIUS or TACACS/TACACS+ server for
authentication. Refer to Chapter 32, “Securing Access to Management Functions”.
Logging in through Brocade Network Advisor
Brocade Network Advisor supports stack technology. To determine what version of Brocade
Network Advisor supports stack technology and to find information on Brocade Network Advisor,
refer to the Brocade Network Advisor manual.
Logging in through the console port
When a device becomes a stack member in the IronStack, it establishes a remote connection to a
virtual console port on the Active Controller. Input and output are relayed between the physical
console port on the stack member and the virtual console port on the Active Controller. Since each
stack member connects to an independent virtual console port on the Active Controller, the
console ports on multiple stack units may be used simultaneously. However, messages displayed
118
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
5
on the Active Controller physical console port during a reload will not be visible on the console ports
of the stack members because the remote connections are not established until the software
loading process is complete. It is preferable to connect a cable to the console port on the stack unit
that will normally be the Active Controller, rather than to the console port of one of the other stack
units.
When a stack unit establishes communication with the Active Controller, it also establishes a
remote console session to the Active Controller. In a normally functioning IronStack, a console
cable may be connected to any of the stack units and provide access to the same commands on
the Active Controller.
You can terminate a session by entering Ctrl+O followed by 'x' or 'X', or by entering the 'exit'
command from the User EXEC level, or by entering the 'logout' command at any level.
NOTE
For the rconsole connections from the stack units to the Active Controller, the escape sequence and
other methods of terminating the session are not available.
NOTE
Error messages that are generated during a reload of the Active Controller will not appear on
rconsole connections from the stack units to the Active Controller. To see these error messages, you
must connect a console cable to the Active Controller itself.
To establish an rconsole session, enter the rconsole command as shown:
PowerConnect# rconsole 1
Syntax: rconsole
The following example shows how to establish rconsole sessions to stack members. Notice that the
show stack command on the stack members displays different information than what is shown
when the show stack command is entered on the Active Controller.
To see the status of your stack units, enter the show stack command on the Active Controller.
PowerConnect# show stack
alone: standalone, D: dynamic config, S: static config
ID Type
Role
Mac Address
Pri State
Comment
1 S FCX648 active
0012.f2de.8100
128 local
Ready
2 S FCX624 standby
0012.f2e2.ba40
0
remote
Ready
3 S FCX624 member
001b.ed7a.22c0
0
remote
Ready
active
standby
+---+
+---+
+---+
-2/1| 1 |3/1--2/1| 2 |3/1--2/2| 3 |2/1|
+---+
+---+
+---+
|
|
|
|-------------------------------------|
Current stack management MAC is 0012.f2de.8100
PowerConnect#
NOTE
For field descriptions for the show stack command, refer to “Displaying stack information” on
page 135.
Establish a remote console session with stack unit 2.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
119
5
Managing your IronStack
PowerConnect# rconsole 2
Connecting to unit 2... (Press Ctrl-O X to exit)
rconsole-2@PowerConnect#show stack
ID
Type
Role
Mac Address
Prio State
2 S FCX624P standby
0012.f2e2.ba40
0
local
Comment
Ready
rconsole-2@PowerConnect# exit
rconsole-2@PowerConnect> exit
Disconnected. Returning to local session...
Establish a remote console session with stack unit 3.
PowerConnect# rconsole 3
Connecting to unit 3... (Press Ctrl-O X to exit)
rconsole-3@PowerConnect# show stack
ID Type
Role
Mac Address
Prio State
3 S FCX624P member
001b.ed7a.22c0
0
local
Comment
Ready
rconsole-3@PowerConnect# logout
Disconnected. Returning to local session...
PowerConnect#
IronStack management MAC address
The IronStack is identified in the network by a single MAC address, usually the MAC address of the
Active Controller (the default). If a new Active Controller is elected, the MAC address of the new
Active Controller (by default) becomes the MAC address for the entire stack. However, you can
manually configure your stack to use a specified MAC address. Refer to “Manual allocation of the
IronStack MAC address” on page 120.
In an IronStack, the management MAC address is generated by the software, and is always the
MAC address of the first port of the Active Controller. This ensures that the management MAC
address remains consistent across stack reboots, and helps prevent frequent topology changes as
a result of protocol enable, disable, and configuration changes.
When you are configuring Layer 2 protocols on stack units, such as STP, RSTP, and MSTP, the
management MAC address of the Active Controller acts as the Bridge ID.
You can also configure the IronStack to retain its original MAC address, or wait for a specified
amount of time before assuming the address of a new Active Controller, using the Persistent MAC
Address feature (refer to “Persistent MAC address” on page 128).
NOTE
All physical IP interfaces on IronStack devices share the same MAC address. It is not recommended
to connect two or more physical IP interfaces between two routers.
Manual allocation of the IronStack MAC address
You can manually configure your IronStack to use a specific MAC address. This overrides the
default condition where the stack uses the MAC address of whatever unit is currently serving as
Active Controller.
NOTE
This command is useful for administration purposes, however it should be used with caution to
prevent duplication of MAC addresses.
120
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
5
NOTE
For hitless stacking failover, Dell recommends that you configure the IronStack MAC address using
the stack mac command. Without this configuration, the MAC address of the stack will change to
the new base MAC address of the Active Controller. This could cause a spanning tree root change.
Even without a spanning tree change, a client (for example, a personal computer) pinging the stack
might encounter a long delay depending on the client MAC aging time. The client won’t work until it
ages out the old MAC address and sends ARP requests to relearn the new stack MAC address.
To configure a stack MAC address manually, enter the following command.
PowerConnect(config)# stack mac 0000.0000.0011
Syntax: [no] stack mac
mac-address - a hexidecimal MAC address in the xxxx.xxxx.xxxx format
Enter the no form of this command to return the MAC address to that of the Active Controller.
Output for this command resembles the following.
PowerConnect(config)# stack mac 0000.0000.0011
PowerConnect(config)# show running-config
Current configuration:
!
ver 7.2.00a 100T7e1
!
stack 1
module 1 FCX-48-port-management-module
module 2 FCX-cx4-2-port-16g-module
priority 80
stack 2
module 1 FCX-24-port-management-module
module 2 FCX-cx4-2-port-16g-module
module 3 FCX-cx4-2-port-16g-module
stack enable
stack mac 0000.0000.0011
To display the stack MAC address, enter the show chassis command.
PowerConnect# show chassis
The stack unit 1 chassis info:
Power supply 1 (NA - AC - Regular) present, status ok
Power supply 2 not present
Fan 1 ok
Fan 2 ok
Exhaust Side Temperature Readings:
Current temperature : 35.5
Warning level.......: 80.0
Shutdown level......: 90.0
Intake Side Temperature Readings:
Current temperature : 33.5
Boot Prom MAC: 0012.f2de.9440
Management MAC: 0000.0000.0011
deg-C
deg-C
deg-C
deg-C
The stack unit 2 chassis info:
Power supply 1 (NA - AC - Regular) present, status ok
Power supply 2 not present
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
121
5
Managing your IronStack
Fan 1 ok
Fan 2 ok
--More--, next page: Space, next line: Return key, quit: Control-c
NOTE
For field descriptions for the show chassis command, refer to “Displaying chassis information” on
page 133.
Removing MAC address entries
You can remove the following types of learned MAC address entries from the Dell system MAC
address table:
•
•
•
•
All MAC address entries
All MAC address entries for a specified Ethernet port
All MAC address entries for a specified VLAN
A specified MAC address entry in all VLANs
For example, to remove entries for the MAC address 000d.cb80.00d in all VLANs, enter the
following command at the Privileged EXEC level of the CLI.
PowerConnect# clear mac-address 000d.cb80.00d0
Syntax: clear mac-address | ethernet | vlan
• If you enter the clear mac-address command without any parameters, the software removes all
MAC entries.
• Use the parameter to remove a specified MAC address from all VLANs. Specify
the MAC address in the following format: HHHH.HHHH.HHHH.
• Use the ethernet parameter to remove all MAC addresses for a specified Ethernet port.
Specify the variable in the format .
• Use the vlan parameter to remove all MAC addresses for a specified VLAN.
IronStack unit identification
Stack units are identified by numbers 1 though 8. You can display stack unit IDs by entering the
show stack command (refer to “Displaying IronStack information” on page 131).
A new device (one that has not been connected in an IronStack or has not been manually assigned
a stack unit number) ships with a default number of 1. Once you enable stacking and the unit
becomes part of an IronStack, its default stack unit number changes to the lowest available
number in the stack.
Stack units must each have a unique identification number. Every stack member, including any
standalone units, retains its stack unit number unless that number is already being used in the
stack, or until you manually renumber the unit using secure-setup. For more information about how
to renumber stack IDs using secure-setup, refer to “Renumbering stack units” on page 149
122
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
5
IronStack unit priority
A unit with a higher priority is more likely to be elected Active Controller. The priority value can be 0
to 255 with a priority of 255 being the highest. The default priority value assigned to the Active
Controller and Standby is 128.
You can assign the highest priority value to the stack unit you want to function as the Active
Controller. When you enter a new priority value for a stack unit, that value takes effect immediately,
but does not affect the current Active Controller until the next reset. For details, refer to “Changing
the priority of a stack unit” on page 123.
You can give your Active and Standby Controllers the same priority, or different priorities (Active
highest, Standby second-highest). When Active and Standby Controllers have the same priority, if
the Active fails and the Standby takes over, then the original Active becomes operational again, it
will not be able to resume its original role if the new Active Controller has more members.
NOTE
For two unit stacks, this behavior does not apply. When the Active and Standby Controllers have the
same priority, the Active Controller will always resume its original role.
In the same situation, when the priorities of the Active and Standby Controllers are different, the
old Active Controller will regain its role and will reset the other units.
For example, suppose both Active and Standby Controllers have the same priority. If there are more
than two units in a stack and the Active Controller leaves and comes back, it cannot win back the
Active role because the new Active Controller has more members than the old Active Controller,
which has no members. If there are only two units in a stack, the old Active Controller may win back
the Active role if it has a lower unit ID. In this case, both the old Active Contoller and new Active
Controller have no members, so the unit with the lower unit ID wins the Active role.
If you want to assign the same priority to the Active and Standby Controllers, you must do so after
the stack is formed. This prevents the intended Standby Controller from becoming the Active
Controller during stack construction.
Changing the priority of a stack member will trigger an election that takes effect immediately
unless the Active Controller role changes. If this is the case, the changes will not take effect until
after the next stack reload.
To display stack member priority values, enter the show stack command.
PowerConnect(config-unit-3)# show stack
alone: standalone, D: dynamic config, S: static config
ID
Type
Role
Mac Address
Pri State
Comment
1 S
FCX624 active
0012.f2eb.a900
128 local
Ready
2 S
FCX624 standby
00f0.424f.4243
0
remote
Ready, member after reload
3 S
FCX624 member
001b.ed5d.a100
200 remote
Ready, active after reload
PowerConnect(config-unit-3)#
Changing the priority of a stack unit
To change the priority value for a stack unit, enter the priority command.
PowerConnect(Config)# stack unit 1
PowerConnect(Config-unit-1)# priority 128
Syntax: priority
• is a value from 0 - 255. 255 is the highest priority.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
123
5
Managing your IronStack
CLI command syntax
CLI syntax that refers to stack units must contain all of the following parameters:
//
• - If the device is operating as a standalone, the stack-unit will be 0 or 1. Stack IDs
can be 0 or any number from 1 through 8.
• - Refers to a specific group of ports on each device.
• - A valid port number. You can list all of the ports individually, use the keyword to to
specify ranges of ports, or a combination of both. To apply the configuration to all ports on the
device, use the keyword all in
IronStack CLI commands
CLI commands specific to stacking are listed in Table 23, with a link to the description for each
command. For more information about CLI commands and syntax conventions, refer to Chapter 1,
“Getting Familiar with Management Applications”.
TABLE 23
124
Stacking CLI commands
Command
Description location...
copy flash flash
“Copying the flash image to a stack unit from the Active Controller” on
page 126
clear stack ipc
“Troubleshooting an unsuccessful stack build” on page 152
cx4-10g
“Changing PowerConnect B-Series FCX-S and CX4 ports from 16 Gbps to 10
Gbps” on page 110
kill console
“Configuring TACACS/TACACS+ for devices in a Dell IronStack” on page 1165
priority
“Changing the priority of a stack unit” on page 123
rconsole
“Logging in through the console port” on page 118
reload stack unit
“Reloading a stack unit” on page 126
show chassis
“Displaying chassis information” on page 133
show flash
“Displaying flash information” on page 131
show memory
“Displaying memory information” on page 132
show module
“Displaying stack module information” on page 134
show running-config
“Displaying running configuration information” on page 143
show stack
“Displaying stack information” on page 135
show stack detail
“Displaying stack information” on page 135
show stack flash
“Displaying stack flash information” on page 137
show stack ipc
“Troubleshooting an unsuccessful stack build” on page 152
show stack neighbors
“Displaying stack neighbors” on page 142
show stack resource
“Displaying stack information” on page 135
show stack rel-ipc stats
“Displaying stack rel-IPC statistics” on page 138
show stack rel-ipc stats unit #
“Displaying stack rel-IPC statistics for a specific stack unit” on page 141
show stack stack-port
“Displaying stack port information” on page 143
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
TABLE 23
5
Stacking CLI commands (Continued)
Command
Description location...
show statistics stack-port
“Displaying stacking port statistics” on page 146
show interfaces stack-ports
“Displaying stacking port interface information” on page 145
show version
“Displaying software version information” on page 144
stack enable
“Stacking mode” on page 125
stack disable
“Stacking mode” on page 125
stack mac [mac-address]
“IronStack management MAC address” on page 120
stack persistent-mac-timer
“Persistent MAC address” on page 128
stack-port
“Changing default stacking port configurations” on page 112
default-ports
“Changing default stacking port configurations” on page 112
stack secure-setup
“Scenario 1 - Configuring a three-member IronStack in a ring topology using
secure-setup” on page 101
stack unconfigure
“Unconfiguring an IronStack” on page 130
hitless-failover enable
“Enabling hitless stacking” on page 174
stack-switchover
“Executing a hitless stacking switchover” on page 177
debug stacking sync_rel_msg
“Displaying hitless stacking diagnostic information” on page 184
Stacking mode
When a unit is stack-enabled or joins a stack either actively or passively, it reserves priority queue 7
for stacking traffic control, assigns buffers for the stacking ports, and configures the first two 10
Gbps ports as stacking ports.
NOTE
Designated stacking ports cannot contain any configuration information, such as VLAN
membership, etc. If configuration information exists, stack enable will fail. You must remove all
configuration information from the port and re-issue the stack enable command.
To enable stacking mode on a new unit before you add it to the stack, enter the following
command.
PowerConnect(config)# stack enable
Enable stacking. This unit actively participates in stacking
Syntax: [no] stack enable
To see the configuration of the stack at any time, enter the show stacking configuration command.
To remove stacking capability, enter the no stack enable command. This prevents the unit from
actively sending out probe messages, however the unit could still be called to join a stack by an
Active Controller. To prevent this, enter the stack disable command.
The stack disable command prevents a unit from sending or listening for any stacking probe
messages. In this mode, the unit cannot be forced to join a stack.
PowerConnect(config)# stack disable
Syntax: [no] stack disable
To remove this restriction, enter the no stack disable command.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
125
5
Managing your IronStack
NOTE
The two left ports on the Four-port 10Gbps SFP+ module do not pass regular Ethernet traffic by
default. The stack disable command must be entered at the global level and the stack disable
command must be configured on these two ports in order for them to pass regular traffic.
Copying the flash image to a stack unit from
the Active Controller
To copy the flash image to a stack unit from the Active Controller primary or secondary flash, enter
the following command.
PowerConnect# copy flash flash unit-id-pri 2
Syntax: copy flash flash [primary | secondary | unit-id-pri | unit-id-sec ]
•
•
•
•
primary - Copy secondary to primary
secondary - Copy primary to secondary
unit-id-pri - Copy active primary image to unit-id
unit-id-sec - Copy active secondary image to unit-id
The unit-id-pri or unit-id-sec keywords are used to copy images to a stack member from the Active
Controller primary and secondary flash, respectively. For , enter a value from 1 through
8. For FCXS devices, the unit range is from 1 through 10.
Reloading a stack unit
To reload a stack unit, enter the following command.
PowerConnect# reload
Syntax: reload [after | at | cancel | unit-id ]
• after - schedule reloading after certain time period
• at - schedule reloading at an exact later time
• cancel - cancel scheduled reload
• unit-id - stack members to reload
• The unit-id can be a combination, such as 2,4-6,8. Tokens must be separated by a
comma and there is no space.
Controlling stack topology
Because Stackable devices allow you to use one of the two ports intended for stacking as a regular
data port, you can control the size of your stack. The following example shows a stack where the
existing ring topology is changed so that only one unit in the upstream direction is connected
through a stacking port, which limits the size of the stack to two units.
PowerConnect# stack secure-setup
PowerConnect# Discovering the stack topology...
Current Discovered Topology - RING
126
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
5
Available UPSTREAM units
Hop(s) Type
Mac Address
1
FCX624 0012.f2d5.2100
2
FCX624 001b.ed5d.9940
Available DOWNSTREAM units
Hop(s) Type
Mac Address
1
FCX624 001b.ed5d.9940
2
FCX624 0012.f2d5.2100
Do you accept the topology (RING) (y/n)?: n
Available UPSTREAM units
Hop(s) Type
Mac Address
1
FCX624 0012.f2d5.2100
2
FCX624 001b.ed5d.9940
Available DOWNSTREAM units
Hop(s) Type
Mac Address
1
FCX624 001b.ed5d.9940
2
FCX624 0012.f2d5.2100
Enter the number of the desired UPSTREAM units (0-2)[0]: 1
Enter the number of the desired DOWNSTREAM units (0-1)[0]:
Selected Topology:
Active Id
Type
1
FCX624
Mac Address
0012.f239.2d40
Selected UPSTREAM units
Hop(s) Id
Type
Mac Address
1
2
FCX624 0012.f2d5.2100
Do you accept the unit ids (y/n)?: y
PowerConnect#Election, was alone --> active, assigned-ID=1
reset unit 2: diff bootup id=1
PowerConnect# show stack
alone: standalone, D: dynamic config, S: static
ID Type
Role
Mac Address
Pri State
1 S FCX624 active 0012.f239.2d40 128 local
2 S FCX624 standby 0012.f2d5.2100
0 remote
config
Comment
Ready
Ready
Managing IronStack partitioning
When a unit in an IronStack with a linear topology fails, the IronStack divides (partitions) into two or
more separate stacks that all have the same configuration. This may cause an IP address conflict
in the network. If you want to keep the stacks separate, you will need to change the IP address of
each new stack.
When a stack breaks into partitions, the partition with the Active Controller remains operational. If
a partition contains the Standby Controller, this partition will become operational because the
Standby Controller will assume the Active role and will reload the partition units. A partition without
an Active or Standby Controller will not function. To reconfigure these units to act in standalone
mode, you must first do a stack unconfigure me command on each unit. Refer to “Unconfiguring an
IronStack” on page 130.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
127
5
Managing your IronStack
To reverse the partitioning, reconnect all of the units into the original stack topology using the
stacking ports. This is the same as merging stacks. If the original Active Controller again has the
highest priority, it will regain its role. If two partition Active Controllers have the same priority, the
Active Controller with the most stack members will win the election. This process helps minimize
traffic interruption.
Ring topology stacks do not partition in the event of a member failure. Operation is interrupted
briefly while the stack recalculates a new path. Ring topologies are more stable than linear
topologies because they provide redundant pathways in case of accidental failure.
Merging IronStacks
IronStacks may be merged, but the total number of stack units must not exceed 8. For example,
you could combine two stacks with 4 units each into a single stack of 8 units.
You can merge stacks by connecting them together using the stacking ports. Before doing this,
make sure that none of the stacking ports have been reconfigured as data ports (for example,
ports on an end unit in a linear stack topology). You cannot use secure-setup to merge stacks
because secure-setup does not work across stack boundaries.
When stacks are merged, an election is held among the Active Controllers. The winner retains its
configuration and the IDs of all of its original stack members. The remaining stack units lose their
configuration and are reset. If the IDs of the losing stack units conflict with the IDs of the winning
units they may change, and the IDs will no longer be sequential. You can use secure-setup to
renumber the members in the newly merged stack. The following examples show how stack
merging works:
• If a stack partitions into multiple stacks because of a connection failure, and you fix the
connection, the stack partitions will merge back into the original stack with no change to stack
IDs, because in this case all stack IDs are distinct.
• In a linear stack topology, the end units of the stack will have only one stacking port
configured. Before you can merge two linear stacks, you must reconfigure the end units so that
both ports are stacking ports.
MIB support for the IronStack
All statistics about packets received and sent, RMON, jumbo frames, runts, giants, and other
instances are gathered through the stack interfaces and are accessible through SNMP. The
functionality for an IronStack is the same as that for a standard 10 Gbps interface. Information
includes types of modules, including optics modules.
NOTE
A type counter has been added to count the number of packets greater than 1518 bytes (jumbo
frames).
For detailed information about stacking MIBs, refer to the MIB Reference Guide.
Persistent MAC address
The MAC address for the entire IronStack is determined by the MAC address of the Active
Controller. When an Active Controller is removed from the stack, and a new Active Controller is
elected, by default the MAC address of the new Active Controller becomes the MAC address for the
IronStack. When you enable the Persistent MAC Address feature, you configure a time delay before
128
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
5
the stack MAC address changes. During this configured interval, if the previous Active Controller is
reinstalled in the stack, the stack continues to use the MAC address of this unit, even though it may
no longer be the Active Controller. If the previous Active Controller does not rejoin the stack during
the specified time interval, the stack assumes the address of the new Active Controller as the stack
MAC address.
The Persistent MAC Address feature allows you to configure a period of time during which the
original base MAC address will not change if the Active Controller fails, or is removed for
maintenance. This timer is triggered when the Standby Controller becomes the Active Controller.
When the timer expires, the new Active Controller will change the previous MAC address to its base
MAC address and advertise this MAC address to management VLANs to update the ARP peer table.
If you want to use the new address, you will have to re-enter the stack-persistent-mac-timer
command again to reactivate the persistent MAC address,
To enable Persistent MAC Address, enter the following command.
PowerConnect(config)# stack persistent-mac-timer 120
Syntax: [no] stack persistent-mac-timer
The variable is the number of minutes during which the IronStack will retain the original
MAC Address if the Active Controller fails or is removed for service. The valid value range is from 5 6000 minutes. If you enter a 0, it means “keep this address forever”. The default is 60 minutes.
To disable Persistent MAC Address, enter the following command.
PowerConnect(config)# no stack persistent-mac-timer
NOTE
If you enter the [no] version of this command while the persistent MAC address timer is active, the
stack will disregard the persistent MAC address and will assume the MAC address of the new Active
Controller.
NOTE
Persistent MAC and stack MAC cannot be used together.
In the following example, the persistent MAC timer has been set to the default of 60 minutes.
PowerConnect(config)# stack persistent-mac 60
PowerConnect(config)# show running-config
Current configuration:
!
ver 7.2.00aT7f1
!
stack 1
module 1 fcx-48-port-managment-module
module 2 fcx-cx4-2-port-16g-module
priority 80
stack 2
module 1 fcx-48-port-managment-module
module 2 fcx-cx4-2-port-16g-module
module 3 fcx-cx4-2-port-16g-module
stack 3
module 1 fcx-48-port-managment-module
module 2 fcx-cx4-2-port-16g-module
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
129
5
Managing your IronStack
priority 40
stack enable
stack persistent-mac 60
To display the stack MAC addresses, enter the show stack command.
PowerConnect(config)# show stack
alone: standalone, D: dynamic config, S: static config
ID
Type
Role
Mac Address
Prio State
Comment
1 S FCX648S active
0012.f2d5.9380
80
local
Ready
2 S FCX648 member
00e0.6666.8880
0
remote
Ready
3 S FCX624 standby
0012.f2dc.0ec0
40
remote
Ready
Current persistent MAC is 0012.f2d5.9380
PowerConnect(config)# stack mac 111.111.111
Error: persistent stacking MAC address timer is configured
PowerConnect(config)#
The following example shows what the Persistent MAC information looks like in the output of the
show stack command when the Standby Controller becomes the Active Controller.
PowerConnect# show stack
alone: standalone, D: dynamic config, S: static
ID
Type
Role
Mac Address
Prio
1 S FCX648P
active
0000.0000.0000
80
2 S FCX648
standby
00e0.6666.8880
0
3 S FCX624
master
0012.f2dc.0ec0
40
PowerConnect#Persistent MAC timer expires in 59
config
State
Comment
reserved
remote
Ready
local
Ready
minutes 52 seconds.
Current persistent MAC is 0012.f2d5.9380
Unconfiguring an IronStack
The stack unconfigure command is a run time command that returns stack units to their
pre-stacking state. When a stack unit is unconfigured, its stacking flash is removed, and its
startup-config.txt flash file is recovered. These actions apply to all units to which this command is
applied, regardless of the role of the unit in the stack.
When the stack unconfigure command is applied to the Active Controller, it removes stack enable
from the run time configuration but not from the startup configuration. If you want to remove stack
enable from the Active Controller permanently, you must enter the write memory command.
When the stack unconfigure command is applied to the Standby Controller or a stack member
(besides the Active Controller) it removes stack enable from the recovered startup-config.txt and
resets the unit.
When a stack unit that did not have an original startup-config file is unconfigured, it becomes a
clean unit. It is possible that this unit could automatically rejoin the stack if its module
configuration matches that of the Active Controller. To prevent this from happening accidentally, it
is best to first disconnect the unit, and then issue the stack unconfigure me command on it.
To remove the configuration from a specific IronStack unit, or from the entire stack, enter a
command similar to the following.
PowerConnect# stack unconfigure 3
Syntax: stack unconfigure | all | me | clean| rollback]
• stack unit - unconfigure the stack member with this ID
• all - unconfigure every unit including this unit
130
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
5
• me - unconfigure this unit only
• clean - removes all startup configuration files including v4 and v5 and makes this a clean unit
NOTE
The stack unconfigure me command is available to all units, while stack unconfigure all and stack
unconfigure are available on the Active Controller only.
The following example shows a session where stack unit 2 is unconfigured.
PowerConnect# show stack
alone: standalone, D: dynamic config, S: static
ID
Type
Role
Mac Address
Pri State
1 S FCX624 active 0012.f2eb.a900 128 local
2 S FCX648 standby 00f0.424f.4243
0 remote
3 S FCX624 member 00e0.5201.0100
0 remote
config
Comment
Ready
Ready
Ready
PowerConnect# stack unconfigure 2
Will recover pre-stacking startup config of this unit, and reset it. Are you sure?
(enter 'y' or 'n'): y
Stack 2 deletes stack bootup flash and recover startup-config.txt from .old
PowerConnect# show stack
alone: standalone, D: dynamic config, S: static
ID
Type
Role
Mac Address
Pri State
1 S FCX624 active 0012.f2eb.a900 128 local
2 S FCX648 member 0000.0000.0000
0 reserved
3 S FCX624 standby 00e0.5201.0100
0 remote
config
Comment
Ready
Ready
When the stack unconfigure 2 command is issued, stack unit 2 recovers the startup-config.txt from
the startup-config.old configuration file that was saved when this unit downloaded its configuration
from the Active Controller. As the output shows, stack member 2 has been removed from the stack,
and ID 2 is now is reserved for a replacement unit. Stack member 3 is now the Standby Controller.
Displaying IronStack information
This section describes the show commands for an IronStack, including output examples and field
descriptions.
Displaying flash information
Use the show flash command to display flash memory information for all members of a stack, or for
a specified stack member.
Syntax: show flash
Output from the show flash command for a stack resembles the following (for a stack with three
members).
From the Active Controller for the entire stack:
PowerConnect# show flash
Stack unit 1:
Compressed Pri Code size = 3034232, Version 05.0.00T7e1 (FCX05000.bin)
Compressed Sec Code size = 2873568, Version 04.2.00T7e1 (FCX04200.bin)
Compressed BootROM Code size = 405217, Version 04.0.00T7e5
Code Flash Free Space = 2146304
Stack unit 2:
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
131
5
Managing your IronStack
Compressed Pri Code size = 3034232, Version 05.0.00T7e1 (FCX05000.bin)
Compressed Sec Code size = 2873523, Version 04.2.00aT7e1 (FCX04200a.bin)
Compressed BootROM Code size = 403073, Version 03.0.00T7e5
Code Flash Free Space = 24117248
Stack unit 3:
Compressed Pri Code size = 3034232, Version 05.0.00T7e1 (FCX05000.bin)
Compressed Sec Code size = 2873568, Version 04.2.00T7e1 (FCX04200.bin)
Compressed BootROM Code size = 405217, Version 04.0.00T7e5
Code Flash Free Space = 2252800
PowerConnect#
For stack member 3 only:
PowerConnect# show flash stack 3
Stack unit 3:
Compressed Pri Code size = 3034232, Version 05.0.00T7e1 (FCX05000.bin)
Compressed Sec Code size = 2873568, Version 04.2.00T7e1 (FCX04200.bin)
Compressed BootROM Code size = 405217, Version 04.0.00T7e5
Code Flash Free Space = 2252800
PowerConnect#
Table 24 describes the fields displayed in this example.
TABLE 24
Field definitions for the show flash command
This field...
Describes...
Compressed Pri Code size
The compressed size, version, and image name for the Primary Code
Compressed Sec Code size
The compressed size, version, and image name for the Secondary
Code
Compressed BootROM Code size
The compressed size and version for the BootROM Code
Code Flash Free Space
The amount of available free space on the Flash memory
Displaying memory information
The show memory command displays information about stack units. The following example shows
output from this command for a stack with eight units.
PowerConnect# show memory
Stack unit 1:
Total DRAM: 268435456 bytes
Dynamic memory: 238026752 bytes
Stack unit 2:
Total DRAM: 268435456 bytes
Dynamic memory: 238026752 bytes
Stack unit 3:
Total DRAM: 268435456 bytes
Dynamic memory: 238026752 bytes
Stack unit 4:
Total DRAM: 268435456 bytes
Dynamic memory: 238026752 bytes
Stack unit 5:
Total DRAM: 268435456 bytes
Dynamic memory: 238026752 bytes
Stack unit 6:
Total DRAM: 268435456 bytes
Dynamic memory: 238026752 bytes
Stack unit 7:
Total DRAM: 268435456 bytes
132
total, 182820476 bytes free, 23% used
total, 172751776 bytes free, 27% used
total, 172751776 bytes free, 27% used
total, 172751776 bytes free, 27% used
total, 107140664 bytes free, 54% used
total, 172751740 bytes free, 27% used
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
5
Dynamic memory: 238026752 bytes total, 182820504 bytes free, 23% used
Stack unit 8:
Total DRAM: 268435456 bytes
Dynamic memory: 238026752 bytes total, 182811440 bytes free, 23% used
PowerConnect#
Syntax: show memory
Table 25 describes the fields displayed in this output example.
TABLE 25
Field definitions for the show memory command
This field...
Describes...
Total DRAM
The size (in bytes) of DRAM
Dynamic memory
The total number of bytes in dynamic memory, including the number of bytes
that are available (free, or unused), and the percentage of memory used.
Displaying chassis information
The show chassis command displays chassis information for each stack unit. Output resembles the
following (in this example, a three member stack).
PowerConnect# show chassis
The stack unit 1 chassis info:
Power supply 1 (NA - AC - Regular) present, status ok
Power supply 2 not present
Fan 1 ok
Fan 2 ok
Exhaust Side Temperature Readings:
Current temperature : 33.0
Warning level.......: 85.0
Shutdown level......: 90.0
Intake Side Temperature Readings:
Current temperature : 31.0
Boot Prom MAC: 0012.f2e4.6e00
Management MAC: 0012.f2e4.6e00
deg-C
deg-C
deg-C
deg-C
The stack unit 2 chassis info:
Power supply 1 (NA - AC - Regular) present, status ok
Power supply 2 not present
Fan 1 ok
Fan 2 ok
Exhaust Side Temperature Readings:
Current temperature : 32.5
Warning level.......: 85.0
Shutdown level......: 90.0
Intake Side Temperature Readings:
Current temperature : 31.0
Boot Prom MAC: 0012.f2e3.11c0
deg-C
deg-C
deg-C
deg-C
The stack unit 3 chassis info:
Power supply 1 (NA - AC - Regular) present, status ok
Power supply 2 not present
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
133
5
Managing your IronStack
Fan 1 ok
Fan 2 ok
Exhaust Side Temperature Readings:
Current temperature : 31.5
Warning level.......: 85.0
Shutdown level......: 90.0
Intake Side Temperature Readings:
Current temperature : 32.0
Boot Prom MAC: 0012.f2db.e500
deg-C
deg-C
deg-C
deg-C
Syntax: show chassis
Table 26 describes the fields displayed in this output example.
TABLE 26
Field definitions for the show chassis command
This field...
Describes...
Power Supply 1
The status of the primary power supply.
Power Supply 2
The status of the secondary power supply, if present.
Fan 1 and Fan 2
The status of the cooling fans
Exhaust Side Temperature
Readings
From the air exhaust side of the chassis, the current temperature reading, the
warning level temperature setting, and the shutdown level temperature
setting.
Intake Side Temperature Reading The current temperature reading from the air intake side of the chassis.
Boot Prom MAC
The MAC address of the boot prom
Management MAC
For the Active Controller only, the management MAC address
Displaying stack module information
The show module command displays information about the stack unit modules. Output resembles
the following.
PowerConnect(config)# show module
Module
S1:M1 FCX-24G 24-port Management Module
S1:M2 FCX-2XGC 2-port 16G Module (2-CX4)
S1:M3 FCX-1XG 1-port 16G Module (1-XFP)
S3:M1 FCX-48G 48-port Management Module
S3:M2 FCX-1XG 1-port 16G Module (1-XFP)
S3:M3 FCX-1XGC 1-port 16G Module (1-CX4)
S4:M1 FCX-48G 48-port Management Module
S4:M2 FCX-1XGC 1-port 16G Module (1-CX4)
S4:M3 FCX-1XG 1-port 16G Module (1-XFP)
S5:M1 FCX-24G 24-port Management Module
S5:M2 FCX-1XG 1-port 16G Module (1-XFP)
S5:M3 FCX-1XG 1-port 16G Module (1-XFP)
S5:M4 FCX-1XG 1-port 16G Module (1-XFP)
S6:M1 FCX-24G 24-port Management Module
S6:M2 FCX-1XGC 1-port 16G Module (1-CX4)
S6:M3 FCX-1XGC 1-port 16G Module (1-CX4)
S7:M1 FCX-48G 48-port Management Module
S7:M2 FCX-1XGC 1-port 16G Module (1-CX4)
S7:M3 FCX-1XGC 1-port 16G Module (1-CX4)
S8:M1 FCX-48G 48-port Management Module
134
Status
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Ports
24
2
1
48
1
1
48
1
1
24
1
1
1
24
1
1
48
1
1
48
Starting MAC
00e0.5201.4000
00e0.5201.4018
00e0.5201.401a
001b.ed5e.c480
001b.ed5e.c4b0
001b.ed5e.c4b1
001b.ed5e.ac00
001b.ed5e.ac30
001b.ed5e.ac31
001b.ed5d.a180
001b.ed5d.a198
001b.ed5d.a199
001b.ed5d.a19a
00e0.5200.3000
00e0.5200.3018
00e0.5200.3019
00e0.4444.0000
00e0.4444.0030
00e0.4444.0031
0012.f2eb.d540
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
S8:M2 FCX-1XG 1-port 16G Module (1-XFP)
S8:M3 FCX-1XG 1-port 16G Module (1-XFP)
PowerConnect(config)#
OK
OK
1
1
5
0012.f2eb.d570
0012.f2eb.d571
Syntax: show module
Table 27 describes the fields displayed in this output example.
TABLE 27
Field definitions for the show module command
This field...
Describes...
Module
Identifies the module, by stack unit ID, module number, module type
Status
The status of this module
Ports
The number of ports in this module
Starting MAC
The starting MAC address for this module
Displaying stack resource information
Use the show stack resource command to display stack resource information, as shown in this
example.
PowerConnect# show stack resource
alloc in-use avail get-fail
register attribute
2400
2347
53
0
general 12B data
32
8
24
0
RB-tree node
4096
2347
1749
0
PowerConnect#
limit get-mem size init
556800
3089
142 2400
7424
8
12
32
237568
2702
18 1024
Syntax: show stack resource
Table 28 describes the output fields for this command.
TABLE 28
Field definitions for the show stack resource command
This field...
Describes...
This command displays the following information for register attributes, general 12B data, and RB-tree node
alloc
Memory allocated
in-use
Memory in use
avail
Available memory
get-fail
The number of get requests that have failed.
limit
The maximum memory allocation
get-mem
The number of get-memory requests
size
The size
init
The number of requests initiated.
Displaying stack information
You can display information about any and all of the members in an IronStack by entering show
commands from the Active Controller console port. If you enter show commands from a unit that is
not the Active Controller, the information may not be displayed correctly.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
135
5
Managing your IronStack
The show stack command displays general information about an IronStack, for all members, for a
specified member, and with additional detail if required.
The following output covers the entire stack.
PowerConnect(config)# show stack
alone: standalone, D: dynamic config, S: static config
ID
Type
Role
Mac Address
Pri State
Comment
1 S FCX648 active 0012.f2eb.a900 130 local
Ready
2 S FCX648 standby 00f0.424f.4243
0 remote
Ready
3 S FCX624 member 00e0.5201.0100
0 remote
Ready
4 S FCX624 member 0000.0000.0000
0 reserved
If you add a stack member ID, output is displayed for that member only.
PowerConnect# show stack 1
ID
Type
Role
Mac Address
1 S FCX648 active
0012.f2eb.a900
Prio State
130 local
Comment
Ready
PowerConnect# show stack 2
ID
Type
Role
Mac Address
2 S FCX648 standby
00f0.424f.4243
Prio State
0
remote
Comment
Ready, member after reload
PowerConnect#show stack 3
ID
Type
Role
Mac Address
3 S FCX624 member
00f0.424f.4243
Prio State
0
remote
Comment
Ready
If you add detail to the show stack command, output resembles the following.
PowerConnect(config)# show stack detail
ID
Type
Role
Mac Address
1 S FCX624 member
00e0.5201.4000
2 S FCX624 member
00e0.5205.0000
3 S FCX624 member
001b.ed5e.c480
4 S FCX624 active
001b.ed5e.ac00
5 S FCX624 standby
001b.ed5d.a180
6 S FCX624 member
00e0.5200.3000
7 S FCX624 member
00e0.4444.0000
8 S FCX624 member
0012.f2eb.d540
ID
1
2
3
4
5
6
7
8
Stack Port Status
Stack-port1
Stack-port2
up (1/2/1)
up (1/2/2)
up (2/2/1)
up (2/2/2)
up (3/2/1)
up (3/3/1)
up (4/2/1)
up (4/3/1)
up (5/2/1)
up (5/3/1)
up (6/2/1)
up (6/3/1)
up (7/2/1)
up (7/3/1)
up (8/2/1)
up (8/3/1)
Prio
0
0
0
128
0
0
0
0
State
remote
remote
remote
local
remote
remote
remote
remote
Comment
Ready
Ready
Ready
Ready
Ready
Ready
Ready
Ready
Neighbors
Stack-port1
3
5
2
7
8
1
6
4
Stack-port2
6
3
1
8
2
7
4
5
Syntax: show stack |
Table 29 describes the fields displayed by the show stack command.
136
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
TABLE 29
5
Field descriptions for the show stack command
This field
Indicates...
alone: Standalone
This device is operating as a standalone device
S: static configuration
The configuration for this unit is static (has been saved with a write
memory command).
D: dynamic configuration
The configuration for this unit is dynamic and may be overwritten by a new
stack unit. To change to a static configuration, enter the write memory
command.
ID
The stack identification number for this unit.
Type
The model of this unit.
Role
The role of this unit within the stack.
MAC address
The MAC address of this unit.
Priority
The priority assigned to this unit.
State
The operational state of this unit.
Comments
Additional information about this unit (optional).
Table 30 describes the output from the show stack detail command (in addition to the show stack
command fields shown in the previous table).
TABLE 30
Field descriptions for the show stack detail command
This field
Indicates...
Stack Port Status
Indicates stacking port status for each stack unit.
Neighbors
Identifies stack neighbors (by unit ID) for each stack unit.
ID
The stack identification number for this unit.
Stack-port 1
Indicates the port state (up or down) and identifies the port by number
(stack-ID/slot/port).
Stack-port 2
Indicates the port state (up or down) and identifies the port by number
(stack-ID/slot/port).
Displaying stack flash information
Use the show stack flash command to display information about flash memory for stack members,
as shown in this example.
PowerConnect# show stack flash
There is no startup-config.old
There was no stack flash read during bootup
Current written stack flash:
FCX624S, ID =1, role= active, priority=128, config=1, jumbo=X PPVLAN=X S2M=
stack p: [0]=1/2/1 [1]=1/2/2 , , hash-chain=X vlan#=X
active-chg=0
Syntax: show stack flash
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
137
5
Managing your IronStack
TABLE 31
Field descriptions for the show stack flash command
This field
Indicates...
ID
Device ID
role
The role of this device in the stack
priority
The priority of this device in the stack
config
Indicates the port state (up or down) and identifies the port by number
(stack-ID/slot/port).
Syntax: show stack flash
Displaying stack rel-IPC statistics
Use the show stack rel-ipc stats command to display session statistics for stack units.
PowerConnect# show stack rel-ipc stats
Reliable IPC statistics:
Global statistics:
Pkts rcvd w/no session: 2
Msgs rcvd w/no handler: 0
Unit statistics:
Unit 2 statistics:
Msgs sent: 1678 Msgs received: 470, Pkt sends failed: 0
Message types sent:
[9]=1571,
[10]=2,
[19]=53,
Message types received:
[9]=467,
[10]=1,
[11]=50,
[13]=2,
[13]=2,
Session statistics, unit 2, channel 0:
Session state: established (last established 31 minutes 7 seconds ago)
Connections established: 1
Remote resets: 0, Reset packets sent: 0
Connection statistics (for current connection, if established):
Msgs sent: 1440, Msgs received: 467
Atomic batches sent: 0, Atomic batches received: 0
Pkts sent: 1242, Pkts received: 1094
Msg bytes sent: 68013, Msg bytes received: 16812
Pkt bytes sent: 291680, Pkt bytes received: 31808
Flushes requested: 108, Suspends: 0, Resumes: 0
Packets sent with data (DAT), ACKs, and window updates (WND):
Other: 1, ACK: 467, WND: 6, ACK+WND: 0
DAT: 768, DAT+ACK: 0, DAT+WND: 0, DAT+ACK+WND: 0
Data retransmits done: 160, Zero-window probes sent: 0
Dup ACK pkts rcvd: 19, Pkts rcvd w/dup data: 0
Pkts rcvd w/data past window: 0
Session statistics, unit 2, channel 2:
Session state: established (last established 31 minutes 5 seconds ago)
Connections established: 1
Remote resets: 0, Reset packets sent: 0
Connection statistics (for current connection, if established):
138
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
5
Msgs sent: 0, Msgs received: 0
Atomic batches sent: 0, Atomic batches received: 0
Pkts sent: 1, Pkts received: 6
Msg bytes sent: 0, Msg bytes received: 0
Pkt bytes sent: 12, Pkt bytes received: 72
Flushes requested: 0, Suspends: 0, Resumes: 0
Packets sent with data (DAT), ACKs, and window updates (WND):
Other: 1, ACK: 0, WND: 0, ACK+WND: 0
DAT: 0, DAT+ACK: 0, DAT+WND: 0, DAT+ACK+WND: 0
Data retransmits done: 0, Zero-window probes sent: 0
Dup ACK pkts rcvd: 6, Pkts rcvd w/dup data: 0
Pkts rcvd w/data past window: 0
Session statistics, unit 2, channel 3:
Session state: established (last established 31 minutes 7 seconds ago)
Connections established: 1
Remote resets: 0, Reset packets sent: 0
Connection statistics (for current connection, if established):
Msgs sent: 234, Msgs received: 0
Atomic batches sent: 0, Atomic batches received: 0
Pkts sent: 255, Pkts received: 241
Msg bytes sent: 8424, Msg bytes received: 0
Pkt bytes sent: 13220, Pkt bytes received: 2892
Flushes requested: 0, Suspends: 0, Resumes: 0
Packets sent with data (DAT), ACKs, and window updates (WND):
Other: 1, ACK: 0, WND: 0, ACK+WND: 0
DAT: 254, DAT+ACK: 0, DAT+WND: 0, DAT+ACK+WND: 0
Data retransmits done: 20, Zero-window probes sent: 0
Dup ACK pkts rcvd: 7, Pkts rcvd w/dup data: 0
Pkts rcvd w/data past window: 0
Session statistics, unit 2, channel 5:
Session state: established (last established 31 minutes 5 seconds ago)
Connections established: 1
Remote resets: 0, Reset packets sent: 0
Connection statistics (for current connection, if established):
Msgs sent: 2, Msgs received: 2
Atomic batches sent: 0, Atomic batches received: 0
Pkts sent: 7, Pkts received: 11
Msg bytes sent: 123, Msg bytes received: 20
Pkt bytes sent: 260, Pkt bytes received: 216
Flushes requested: 2, Suspends: 0, Resumes: 0
Packets sent with data (DAT), ACKs, and window updates (WND):
Other: 3, ACK: 1, WND: 0, ACK+WND: 0
DAT: 3, DAT+ACK: 0, DAT+WND: 0, DAT+ACK+WND: 0
Data retransmits done: 1, Zero-window probes sent: 0
Dup ACK pkts rcvd: 6, Pkts rcvd w/dup data: 0
Pkts rcvd w/data past window: 0
Unit 3 statistics:
Msgs sent: 1193 Msgs received: 492, Pkt sends failed: 0
Message types sent:
[9]=1158,
[10]=2,
[19]=29,
Message types received:
[9]=489,
[10]=1,
[11]=2,
[13]=2,
[13]=2,
Session statistics, unit 3, channel 0:
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
139
5
Managing your IronStack
Session state: established (last established 31 minutes 11 seconds ago)
Connections established: 1
Remote resets: 0, Reset packets sent: 0
Connection statistics (for current connection, if established):
Msgs sent: 955, Msgs received: 489
Atomic batches sent: 0, Atomic batches received: 0
Pkts sent: 1172, Pkts received: 1054
Msg bytes sent: 43705, Msg bytes received: 18696
Pkt bytes sent: 236968, Pkt bytes received: 33564
Flushes requested: 59, Suspends: 0, Resumes: 0
Packets sent with data (DAT), ACKs, and window updates (WND):
Other: 2, ACK: 487, WND: 7, ACK+WND: 0
DAT: 675, DAT+ACK: 1, DAT+WND: 0, DAT+ACK+WND: 0
Data retransmits done: 129, Zero-window probes sent: 0
Dup ACK pkts rcvd: 17, Pkts rcvd w/dup data: 0
Pkts rcvd w/data past window: 0
Session statistics, unit 3, channel 2:
Session state: established (last established 31 minutes 10 seconds ago)
Connections established: 1
Remote resets: 0, Reset packets sent: 0
Connection statistics (for current connection, if established):
Msgs sent: 0, Msgs received: 0
Atomic batches sent: 0, Atomic batches received: 0
Pkts sent: 1, Pkts received: 7
Msg bytes sent: 0, Msg bytes received: 0
Pkt bytes sent: 12, Pkt bytes received: 84
Flushes requested: 0, Suspends: 0, Resumes: 0
Packets sent with data (DAT), ACKs, and window updates (WND):
Other: 1, ACK: 0, WND: 0, ACK+WND: 0
DAT: 0, DAT+ACK: 0, DAT+WND: 0, DAT+ACK+WND: 0
Data retransmits done: 0, Zero-window probes sent: 0
Dup ACK pkts rcvd: 7, Pkts rcvd w/dup data: 0
Pkts rcvd w/data past window: 0
Session statistics, unit 3, channel 3:
Session state: established (last established 31 minutes 11 seconds ago)
Connections established: 1
Remote resets: 0, Reset packets sent: 0
Connection statistics (for current connection, if established):
Msgs sent: 234, Msgs received: 0
Atomic batches sent: 0, Atomic batches received: 0
Pkts sent: 235, Pkts received: 238
Msg bytes sent: 8424, Msg bytes received: 0
Pkt bytes sent: 12180, Pkt bytes received: 2856
Flushes requested: 0, Suspends: 0, Resumes: 0
Packets sent with data (DAT), ACKs, and window updates (WND):
Other: 1, ACK: 0, WND: 0, ACK+WND: 0
DAT: 234, DAT+ACK: 0, DAT+WND: 0, DAT+ACK+WND: 0
Data retransmits done: 0, Zero-window probes sent: 0
Dup ACK pkts rcvd: 4, Pkts rcvd w/dup data: 0
Pkts rcvd w/data past window: 0
Session statistics, unit 3, channel 6:
Session state: established (last established 31 minutes 10 seconds ago)
Connections established: 1
Remote resets: 0, Reset packets sent: 0
Connection statistics (for current connection, if established):
Msgs sent: 2, Msgs received: 2
Atomic batches sent: 0, Atomic batches received: 0
140
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
5
Pkts sent: 8, Pkts received: 13
Msg bytes sent: 123, Msg bytes received: 20V
Pkt bytes sent: 232, Pkt bytes received: 296
Flushes requested: 2, Suspends: 0, Resumes: 0
Packets sent with data (DAT), ACKs, and window updates (WND)
Other: 5, ACK: 1, WND: 0, ACK+WND: 0
DAT: 2, DAT+ACK: 0, DAT+WND: 0, DAT+ACK+WND: 0
Data retransmits done: 0, Zero-window probes sent: 0
Dup ACK pkts rcvd: 6, Pkts rcvd w/dup data: 0
Pkts rcvd w/data past window: 0
Syntax: show stack rel-ipc stats
Displaying stack rel-IPC statistics for a specific stack unit
To display IPC statistics for a specific unit, enter the following command:
PowerConnect# show stack rel-ipc stats unit 3
Unit 3 statistics:
Msgs sent: 1217 Msgs received: 509, Pkt sends failed: 0
Message types sent:
[9]=1182,
[10]=2,
[19]=29,
Message types received:
[9]=506,
[10]=1,
[11]=2,
[13]=2,
[13]=2,
Session statistics, unit 3, channel 0:
Session state: established (last established 32 minutes 19 seconds ago)
Connections established: 1
Remote resets: 0, Reset packets sent: 0
Connection statistics (for current connection, if established):
Msgs sent: 971, Msgs received: 506
Atomic batches sent: 0, Atomic batches received: 0
Pkts sent: 1205, Pkts received: 1088
Msg bytes sent: 44281, Msg bytes received: 19308
Pkt bytes sent: 238004, Pkt bytes received: 34652
Flushes requested: 59, Suspends: 0, Resumes: 0
Packets sent with data (DAT), ACKs, and window updates (WND):
Other: 2, ACK: 504, WND: 7, ACK+WND: 0
DAT: 691, DAT+ACK: 1, DAT+WND: 0, DAT+ACK+WND: 0
Data retransmits done: 129, Zero-window probes sent: 0
Dup ACK pkts rcvd: 18, Pkts rcvd w/dup data: 0
Pkts rcvd w/data past window: 0
Session statistics, unit 3, channel 2:
Session state: established (last established 32 minutes 17 seconds ago)
Connections established: 1
Remote resets: 0, Reset packets sent: 0
Connection statistics (for current connection, if established):
Msgs sent: 0, Msgs received: 0
Atomic batches sent: 0, Atomic batches received: 0
Pkts sent: 1, Pkts received: 7
Msg bytes sent: 0, Msg bytes received: 0
Pkt bytes sent: 12, Pkt bytes received: 84
Flushes requested: 0, Suspends: 0, Resumes: 0
Packets sent with data (DAT), ACKs, and window updates (WND):
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
141
5
Managing your IronStack
Other: 1, ACK: 0, WND: 0, ACK+WND: 0
DAT: 0, DAT+ACK: 0, DAT+WND: 0, DAT+ACK+WND: 0
Data retransmits done: 0, Zero-window probes sent: 0
Dup ACK pkts rcvd: 7, Pkts rcvd w/dup data: 0
Pkts rcvd w/data past window: 0
Session statistics, unit 3, channel 3:
Session state: established (last established 32 minutes 19 seconds ago)
Connections established: 1
Remote resets: 0, Reset packets sent: 0
Connection statistics (for current connection, if established):
Msgs sent: 242, Msgs received: 0
Atomic batches sent: 0, Atomic batches received: 0
Pkts sent: 243, Pkts received: 246
Msg bytes sent: 8712, Msg bytes received: 0
Pkt bytes sent: 12596, Pkt bytes received: 2952
Flushes requested: 0, Suspends: 0, Resumes: 0
Packets sent with data (DAT), ACKs, and window updates (WND):
Other: 1, ACK: 0, WND: 0, ACK+WND: 0
DAT: 242, DAT+ACK: 0, DAT+WND: 0, DAT+ACK+WND: 0
Data retransmits done: 0, Zero-window probes sent: 0
Dup ACK pkts rcvd: 4, Pkts rcvd w/dup data: 0
Pkts rcvd w/data past window: 0
Session statistics, unit 3, channel 6:
Session state: established (last established 32 minutes 17 seconds ago)
Connections established: 1
Remote resets: 0, Reset packets sent: 0
Connection statistics (for current connection, if established):
Msgs sent: 2, Msgs received: 2
Atomic batches sent: 0, Atomic batches received: 0
Pkts sent: 8, Pkts received: 13
Msg bytes sent: 123, Msg bytes received: 20
Pkt bytes sent: 232, Pkt bytes received: 296
Flushes requested: 2, Suspends: 0, Resumes: 0
Packets sent with data (DAT), ACKs, and window updates (WND):
Other: 5, ACK: 1, WND: 0, ACK+WND: 0
DAT: 2, DAT+ACK: 0, DAT+WND: 0, DAT+ACK+WND: 0
Data retransmits done: 0, Zero-window probes sent: 0
Dup ACK pkts rcvd: 6, Pkts rcvd w/dup data: 0
Pkts rcvd w/data past window: 0
PowerConnect#
Syntax: show stack rel-ipc unit num
Displaying stack neighbors
The show stack neighbors command displays information about stack member neighbors.
PowerConnect# show stack neighbors
ID Stack-port1
Stack-port2
1
3
2
2
1
3
3
2
1
The topology of stack system is ring, and has 3 stack unit(s)
From left to right (starting with active unit): 1 2 3
Syntax: show stack neighbors
142
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
5
Table 32 describes the output from the show stack neighbors command.
TABLE 32
Field descriptions for the show stack neighbors command
This field
Indicates...
ID
The stack identification number for this unit.
Stack-port1
Identifies the neighbor stack unit for stack-port1 for this unit id
Stack-port2
Identifies the neighbor stack unit for stack-port2 for this unit id
Displaying stack port information
The show stack stack-ports command displays information about stack port status.
PowerConnect(config)# show stack stack-ports
ID
Stack-port1
Stack-port2
1
up (1/2/1)
up (1/2/2)
2
up (2/2/1)
up (2/2/2)
3
up (3/2/1)
up (3/3/1)
4
up (4/2/1)
up (4/3/1)
5
up (5/2/1)
up (5/3/1)
Syntax: show stack stack-ports
Table 33 describes the output from the show stack stack-ports command.
TABLE 33
Field descriptions for the show stack stack-ports command
This field
Indicates...
ID
The stack identification number for this unit
Stack-port1
Indicates port state (up or down) and identifies the port by number (stack-ID/slot/port)
Stack-port 2
Indicates port state (up or down) and identifies the port by number (stack-ID/slot/port)
Displaying running configuration information
The show running-config command displays information about the current stack configuration.
PowerConnect(config)# show running-config
Current configuration:
!
ver 7.2.0.a
!
stack unit 1
module 1 FCX-24-port-management-module
module 2 FCX-cx4-2-port-16g-module
module 3 FCX-xfp-1-port-16g-module
stack-port 1/2/1 1/3/1
stack unit 2
module 1 FCX-48-port-management-module
module 2 FCX-xfp-2-port-16g-module
stack unit 3
module 1 FCX-48-port-management-module
module 2 FCX-xfp-1-port-16g-module
module 3 FCX-cx4-1-port-16g-module
stack unit 4
module 1 FCX-48-port-management-module
module 2 FCX-cx4-1-port-16g-module
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
143
5
Managing your IronStack
module 3 FCX-xfp-1-port-16g-module
priority 128
stack enable
!
Syntax: show running-config
Table 34 describes the output from the show running-config command.
TABLE 34
Field descriptions for the show running-config command
This field
Indicates...
Stack unit <#>
The stack identification number for this unit.
Module <#>
Identifies the configuration for modules on this unit.
Pri
Indicates that a priority has been assigned to this stack unit
Displaying configured stacking ports
The stacking ports may display in the output from the show running-config command in three
different ways.
1. When stacking is enabled, the output shows both stacking ports.
stack unit 1
module 1 FCX-24-port-management-module
module 2 FCX-cx4-2-port-16g-module
module 3 FCX-xfp-1-port-16g-module
stack-port 1/2/1 1/3/1
2. When stacking is not enabled, neither stacking port is displayed.
stack unit
module 1
module 2
module 3
1
FCX-24-port-management-module
FCX-cx4-2-port-16g-module
FCX-xfp-1-port-16g-module
3. If one stacking port is configured, that port will be displayed regardless of whether or not
stacking is enabled.
stack unit 1
module 1 FCX-24-port-management-module
module 2 FCX-cx4-2-port-16g-module
module 3 FCX-xfp-1-port-16g-module
stack-port 1/3/1
Displaying software version information
The show version command shows the software version that the stack is running. Note that the last
line of this output shows the bootup ID and role for this unit. Output resembles the following.
PowerConnect(config)# show version
SW: Version 07.2.00aT7e1 Copyright (c) 2009 Brocade Communications Systems, Inc.
Compiled on Jul 23 2008 at 02:38:03 labeled as FCX05002
(3054675 bytes) from Primary FCX05002.bin
STACKID 1: compiled on Jul 23 2008 at 02:38:03 labeled as FCX05000
(3054675 bytes) from Primary FCX05000.bin
STACKID 2: compiled on Jul 23 2008 at 02:38:03 labeled as FCX05000
(3054675 bytes) from Primary FCX05000.bin
STACKID 3: compiled on Jul 23 2008 at 02:38:03 labeled as FCX05000
144
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
5
(3054675 bytes) from Primary FCX05000.bin
BootROM: Version 04.0.00T7e5 (FEv2)
HW: Chassis FCX648
==========================================================================
STACKID 1: SL 1: FCX-24G 24-port Management Module
Serial #: PR11060248
P-ASIC 0: type D804, rev 01
==========================================================================
STACKID 1: SL 2: FCX-2XGC 2-port 16G Module (2-CX4)
==========================================================================
STACKID 1: SL 3: FCX-1XG 1-port 16G Module (1-XFP)
==========================================================================
STACKID 2: SL 1: FCX-48G 48-port Management Module
Serial #: AN07510010
P-ASIC 0: type D804, rev 01
P-ASIC 1: type D804, rev 01
==========================================================================
STACKID 2: SL 2: FCX-1XG 1-port 16G Module (1-XFP)
==========================================================================
STACKID 2: SL 3: FCX-1XGC 1-port 16G Module (1-CX4)
==========================================================================
STACKID 3: SL 1: FCX-48G 48-port Management Module
Serial #: AN07510269
P-ASIC 0: type D804, rev 01
P-ASIC 1: type D804, rev 01
==========================================================================
STACKID 3: SL 2: FCX-1XGC 1-port 16G Module (1-CX4)
==========================================================================
STACKID 3: SL 3: FCX-1XG 1-port 16G Module (1-XFP)
==========================================================================
==========================================================================
400 MHz Power PC processor 8248 (version 130/2014) 66 MHz bus
512 KB boot flash memory
30720 KB code flash memory
128 MB DRAM
Monitor Option is on
The system uptime is 18 minutes 4 seconds
STACKID 1 system uptime 18 minutes 4 seconds
STACKID 2 system uptime 18 minutes 3 seconds
STACKID 3 system uptime 18 minutes 3 seconds
The system started at 21:08:51 GMT+00 Fri Jul 25 2008
The system : started=warm start
reloaded=by "reload"
My stack unit ID = 1, bootup role = active
Syntax: show version
Displaying stacking port interface information
The show interfaces stack-ports command displays information about the stacking ports on all
stack units.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
145
5
Managing your IronStack
PowerConnect# show interfaces stack-ports
Port
1/2/1
1/2/2
2/2/1
2/2/2
3/2/1
3/2/2
4/2/1
4/2/2
Link
Up
Up
Up
Up
Up
Up
Up
Up
State
Forward
Forward
Forward
Forward
Forward
Forward
Forward
Forward
Dupl
Full
Full
Full
Full
Full
Full
Full
Full
Speed
10G-CX4
10G-CX4
10G-CX4
10G-CX4
10G-CX4
10G-CX4
10G-CX4
10G-CX4
Trunk
None
None
None
None
None
None
None
None
Tag
No
No
No
No
No
No
No
No
P
l
l
l
l
l
l
l
l
MAC
Name
0012.f2e4.6e30
0012.f2e4.6e31
0012.f2e3.11f0
0012.f2e3.11f1
0012.f2db.e530
0012.f2db.e531
0012.f2e2.c770
0012.f2e2.c771
Syntax: show interfaces stack-ports
Table 35 describes the fields displayed by the show interfaces stack-ports command.
TABLE 35
Field descriptions for the show interfaces stack-ports command
This field
Indicates...
Port
The stack identification number for this unit.
Link
Identifies the configuration for modules on this unit.
State
Indicates that a priority has been assigned to this stack unit
Dupl
Indicates whether the port is configured as half or full duplex
Speed
Indicates the port speed
Trunk
Indicates whether the port is part of a trunk
Tag
Indicates whether the port is tagged or untagged
P
Port priority
MAC
The MAC address of the port
Name
An optional name assigned to the port
Displaying stacking port statistics
The show statistics stack-ports command displays information about all stacking ports in an
IronStack topology.
PowerConnect# show statistics stack-ports
Port
In Packets
Out Packets
1/2/1
22223
4528
1/2/2
35506
3844
2/2/1
3161
34173
2/2/2
24721
3676
3/2/1
3048
23881
3/2/2
13540
2857
4/2/1
2862
13537
4/2/2
3626
3184
5/2/1
3183
3621
5/2/2
3265
13508
6/2/1
14020
3655
6/3/1
3652
17705
7/2/1
17705
3658
7/3/1
4047
21802
TOTAL
146
154559
153629
In Errors
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Out Errors
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
5
Syntax: show statistics stack-ports
Table 36 describes the fields displayed by the show statistics stack-ports command.
TABLE 36
Field definitions for the show statistics stack-ports command
This field
Indicates...
Port
The stack identification number for this unit.
In Packets
The number of incoming packets on this port
Out Packets
The number of outgoing packets on this port
In Errors
The number of incoming errors on this port
Out Errors
The number of outgoing errors on this port
Adding, removing, or replacing units in an IronStack
The following sections describe how to add, remove, or replace units in an IronStack. The
recommended method is to connect units to the stack before you supply power to the units,
however, you can also connect powered units.
Installing a new unit in an IronStack using secure-setup
This method can be applied to clean units, or units that have existing configurations.
1. Connect the new unit to the stack by connecting the 10 Gbps stacking ports.
2. Run secure-setup on the Active Controller and assign an ID to the new unit. The Active
Controller will reset the new unit.
3. Once the new unit boots and joins the stack, do a write memory on the Active Controller.
Installing a new unit using static configuration
If the new unit is a clean unit and the connection is sequential you can add it using the static setup
process.
1. Enter the module configuration of the new unit into the Active Controller configuration.
2. Connect the new unit to the stack using the 10Gbps stacking ports. The sequence in which you
connect the unit must match that of the Active Controller configuration. The Active Controller
automatically resets the unit.
3. Once the new unit boots and joins the stack, do a write memory on the Active Controller. You
should see the following message.
Done hot swap: Set stack unit 3 to Fully-Operational:16
Configuration notes
Configuration on a new unit can be accomplished in three ways:
• If the Active Controller has no configuration information for the new unit, it learns the new
unit's configuration. This is a dynamic configuration and will disappear if the new unit leaves
the stack. In order for the configuration to stay on the Active Controller (to make it a static
configuration), you must do a write memory on the Active Controller.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
147
5
Managing your IronStack
• If the Active Controller has configuration information for a new unit, and it matches the base
module (module 1) of the new unit, no action is necessary. If configuration information for
non-base modules on the new unit does not match the information on the Active Controller, the
Active Controller learns the configuration for the new unit module types and merges it with the
information it has for the base module. This merged configuration remains static and will stay
on the Active Controller even if the new unit leaves the stack.
• If the Active Controller has configuration information for the new unit, but it does not match the
base module of the new unit, a configuration mismatch can occur where the configuration
related to this unit is removed even after the mismatch is resolved. Refer to “Recovering from a
mismatch” on page 156 for more information.
Removing a unit from an IronStack
To remove a unit from the stack, disconnect the cables from the stacking ports. This can be done
whether the units are powered-on or powered-off. When you remove a unit that is powered-on, it is
still in stacking enabled mode. To remove the stacking files, enter the stack unconfigure me or
stack unconfigure clean command. When the unit reboots, it will operate as a standalone unit.
Refer to “Unconfiguring an IronStack” on page 130.
When a unit is removed from a stack, the Active Controller deletes this unit configuration if it is
dynamically learned. Refer to “IronStack terminology” on page 96 for definitions of static and
dynamic configurations.
Replacing an IronStack unit
Replacing with a clean unit
If the stack unit ID numbering is sequential, you can easily swap a failed unit with an identical clean
unit using this procedure.
1. Remove the old unit from the stack.
2. Make sure that the hardware (module) configuration of the replacement unit is identical to that
of the failed unit.
3. Connect the new unit to the stack using the same stacking ports used by the old unit.
4. If the configuration of the replacement unit matches the configuration on the Active Controller,
the Active Controller resets the new unit, which automatically becomes active in the stack, and
the stack retains its original topology.
Replacing with multiple clean units
If you are replacing multiple old units with clean units, the Active Controller replaces the unit with
the lowest ID first. You must use secure-setup If the replacement is not a clean unit, the connection
is not sequential, or you do not want the Active Controller to trigger an automatic replacement. Use
the following steps.
1. Remove the old stack unit from the stack
2. Connect the new unit to the existing stack using the same stacking ports used by the old unit.
3. Run secure-setup to select the ID of the old unit for the new unit. The Active Controller resets
the unit, and it joins the stack.
148
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
5
NOTE
Adding, removing or replacing a stack unit which is not at the end of linear topology may cause the
other units in the stack to reset if these units lose their path to the Active Controller during the
process. Adding or removing a unit in a ring topology should not cause the other units to reset
because each unit can still find a path to the Active Controller.
Moving a unit to another stack
Moving a member from a stack and to another stack can result in non-sequential ID assignment.
The Active Controller will honor the new unit original ID if that ID is not being used in the new stack.
The Active Controller will assign a new ID if the original ID is already being used. To prevent
non-sequential stack ID assignments, configure the unit that is moving as a clean unit before
adding it to the new stack.
Removing an Active Controller from a powered stack
To remove an Active Controller from a powered stack, disconnect the Active Controller. The Standby
Controller waits for 30 seconds and then assumes the role of Active Controller. A single Active
Controller device functions as a standalone unit even it is still stacking-enabled. You do not have to
issue a stack unconfigure me command for an Active Controller.
Renumbering stack units
You can use secure-setup to renumber stack units in a previously constructed stack. In the
following example, three units make up a stack, yet two of the units are numbered 5 and 6 (the
Active Controller is numbered 1). Since this stack is only going to contain 3 units, you can renumber
the other units so that they are unit 2 and unit 3.
The most effective way to number your stack members is sequentially. You can skip numbers, but
they should still be sequential, from 1 to 8. Sequential numbering makes it easy to replace stack
units, and easier to troubleshoot issues.
NOTE
In a ring topology, 1, 2, 4, 5, and 1, 5, 4, 2 are both sequential.
Example
PowerConnect# stack secure-setup
PowerConnect#Discovering the stack topology...
Available UPSTREAM units
Hop(s) Type
Mac Address
1
FCX624 0012.f2d5.2100
2
FCX624 001b.ed5d.9940
Enter the number of the desired UPSTREAM units (1-2)[1]: 2
Selected topology:
Active id Type
Mac Address
1
FCX624 0012.f239.2d40
Selected UPSTREAM units
Hop(s)
id Type
Mac Address
1
5 FCX624 0012.f2d5.2100
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
149
5
Managing your IronStack
2
6
FCX624
001b.ed5d.9940
Do you accept the unit ids? (y/n)?: n
Enter an unused id for the UPSTREAM FCX623 unit a 1 hop(s) (1-8)[5]: 2
Enter an unused id for the UPSTREAM FCX624 unit at 2 hop(s) (1-8) [6]: 3
PowerConnect# Election, was active, no role change, assigned-ID=1
reset unit 2: diff bootup id=5
reset unit 3: diff bootup id=6
Election, was active, no role change, assigned-ID=1
PowerConnect# show
ID Type
Role
1 S FCX624 active
2 S FCX624 standby
3 S FCX624 member
stack
Mac Address
Pri
0012.f239.2d40 128
0012.f2d5.2100
0
001b.ed5d.9940
0
State
local
remote
remote
Comment
Ready
Ready
Ready
Configuration Notes:
• Renumbering may result in the removal of a unit configuration if the stack unit base module
does not match the configuration on the Active Controller. However, secure-setup renumbering
never changes the interface configuration. For example, if you switch the IDs of identical units
2 and 3, the Active Controller does not change 2/1/5 to 3/1/5 and vice versa.
• If the configuration for the ID you select for a specific unit does not match the configuration on
that unit, secure-setup will change the static configuration into a dynamic configuration so it
can be overwritten by the learned configuration.
• When swapping IDs for two or more identical units - for example, if units 2, 3, and 4 are
identical, changing 2 to 3, 3 to 4, and 4 to 2 will not affect the configurations of the units
except that the units will reset and assume the new IDs.
• If you swap IDs for two units that are not identical -The Active Controller removes the
configurations and resets both units. When both units boot with new IDs, the Active Controller
learns their module types and creates new unit configurations for both. However, all interface
configuration information related to units 2 and 3 is gone.
• When you renumber identical units using secure-setup, the configurations are not mapped to
the new units (since the configurations match exactly). However, if you switch the IDs of units
that are not identical, a configuration mismatch occurs. Refer to “Recovering from a mismatch”
on page 156
• When you assign an unused ID to a stack unit, the unit is reset with the new ID. All unit and
interface configuration information related to the old stack ID is deleted. The Active Controller
learns the configuration for the new unit (instead of creating interface configuration for the
new unit.
• Release 5.0 does not support user changes to the Active Controller ID.
• Secure-setup does not swap configuration information for units that have had their IDs
changed. For example, it does not change the 2/1/3 interface configuration or VLAN
membership information into 3/1/3 information if the unit ID changes from 2 to 3.
• If the configuration for a unit being replaced does not match the new unit type, the Active
Controller removes the unit configuration and associated interface configuration.
• All learned configurations due to mismatches or the addition of new units are dynamic
configurations. To convert them into static configurations, do a write memory to preserve the
configurations if a unit is removed from the stack.
150
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Troubleshooting an IronStack
5
Syslog, SNMP, and traps
Syslog messages from stack units are forwarded to, and can be viewed from, the Active Controller.
All stack units support SNMP gets, sets, and traps, which are managed by the Active Controller. An
SNMP trap is sent from a stack unit to the stack Active Controller, and forwarded from the Active
Controller to an SNMP-configured server. An external network management station can execute
SNMP gets and sets for MIBs and collect information about any port on the stack.
SNMP traps can be configured for the insertion or removal of a stack unit or uplink module, and for
optic identification.
For more information about Syslog messages, refer to Chapter 41, “Using Syslog”.
Configuring SNMP for an IronStack
SNMP server and feature configuration is the same for an IronStack as it is for standalone units. In
an IronStack, SNMP gets and sets are processed by the Active Controller for the Standby Controller
and all stack members. SNMP traps generated by the Standby Controller and stack members are
propagated to the configured SNMP server through the Active Controller. For more information
about how to configure an SNMP server for PowerConnect devices, refer to Chapter 40, “Securing
SNMP Access”.
SNMP engine IDs for stackable devices
For Dell stacking devices, if an engine ID is not manually created or a stack MAC address is not
specified and saved, the stack will lose its engine ID if the Active Controller fails and the Standby
Controller takes over, because the Standby Controller creates a new engine ID at bootup. To
prevent this from happening, you will need to either create a new engine ID or create a new stack
MAC address to ensure that the engine ID is saved to the startup configuration. This should be
done before the SNMPv3 user is created.
If a new Active Controller is elected (for example, the Standby Controller becomes the Active
Controller) you will see the following results:
• If you have configured the engineID saved it to the startup configuration file, the new stack
configuration will use the saved engine ID.
• If you have not configured an engineID, but a stack MAC address is configured, the new stack
configuration will retain the original engineID since it is based on the stack MAC address.
• If you have not configured an engineID, and no stack MAC address is configured, the new stack
configuration will use the default engineID, which is based on its own management MAC
address of the new Active Controller. Since the engine ID will have changed, any SNMPv3
Clients will need to be reconfigured with the new engineID.
Troubleshooting an IronStack
The most common reason for an unsuccessful stack build is either a software configuration
mismatch, a hardware configuration mismatch, or a combination of both.
The following sections describe common troubleshooting procedures for an IronStack.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
151
5
Troubleshooting an IronStack
Troubleshooting an unsuccessful stack build
If you are unable to build a stack, (for example, the show stack command does not display any
stack units), perform the following steps.
1. Enter the show run command on each unit to make sure the configuration contains “stack
enable”. If it does not, enter the stack enable command on the unit. Before a stack is formed,
you can still access the console port on each device. Once a stack is successfully formed, you
are redirected to the Active Controller.
NOTE
If you are building a stack using secure-setup, you do not have to enter stack enable on each
unit.
2. Check that all of your stacking port connections are secure and working properly. Enter the
show interface stack on each device to confirm that the stacking port links are up and the
ports are in the forward state.
PowerConnect# show interfaces stack
Port Link State
Dupl Speed Trunk
1/2/1 Up
Forward Full 10G
None
1/2/2 Up
Forward Full 10G
None
Tag
No
No
P MAC
Name
1 0012.f2eb.a902
1 0012.f2eb.a904
3. Confirm that all of the devices are running the same software image
4. Use the show log command to display any IPC version mismatch messages. These messages
appear in one minute when receiving mismatched probe packets, and then once every 10
minutes.
5. Type show stack ipc to see if any traffic has been sent or received. Enter clear stack ipc to clear
the traffic statistics and then enter show stack ipc again so you can easily see differences in
traffic flow.
PowerConnect# show stack ipc
Recv IPC 330 packets
Message types have callbacks:
1 : Reliable IPC message
.... more message types removed.
Send message types:
[5]=190,
[6]=10,
[14]=126,
Recv message types:
[5]=224,
[6]=6,
[20]=1,
[27]=9,
Statistics:
send pkt num
send msg num
send frag pkt num
pkt buf alloc
:
:
:
:
2 : Reliable IPC atomic batch
964,
964,
0,
964,
[9]=636,
[11]=2,
[14]=90,
[18]=2,
recv pkt num
recv msg num
recv frag pkt num
:
:
:
330,
330,
0,
Reliable-mail
send success receive time us
target ID
0
0
0
0
target MAC
0
0
2
0
There is 0 current jumbo IPC session
Possible errors:
*** state not ready
152
:
1,
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Troubleshooting an IronStack
5
If the send message types: field is empty, it means that stack enable has not been configured.
If the number of Recv IPC packets increases, but there are no Recv message types, then the
packets are being dropped for various reasons, including the wrong IPC version, or a checksum
error. The Possible errors field will list reasons for packet loss.
NOTE
A small “***state not ready” count is normal, but if it continues to increase a problem is
indicated.
6. If the results of a show stack command show other stack members, but lists them as
non-operational, this could be due to an image mismatch, or a configuration mismatch. In the
event of an image mismatch, you can download the correct images to the entire stack from the
Active Controller. Refer to “Configuration mismatch” on page 155 for more information about
configuration mismatches.
NOTE
If your intended stacking ports are connected in a ring topology, they will not all appear to be in
the forwarding state because of spanning tree, but secure-setup can still build the stack.
7.
If you run out of flash memory while doing a write memory, your stack devices may contain very
large startup-config.v4 or startup-config.old files, which are preserved for recovery purposes
(refer to “Unconfiguring an IronStack” on page 130 for more information). If you do not need
these files, you can delete them using the flash delete command. Enter the show dir command
to see all flash files.
8. Check to be sure you do not have any stacking to non-stacking connections. If you see the
following message.
Warning! Proc ???? packet in 2m from 0012.f2222.8300, Wrong dev/port: dev=4,
port=18, DSA=4971100 497--E
You might have stacking to non-stacking port connections
This indicates that you may have a connection between a stacking port and a non-stacking
port. This message will appear every 10 minutes after the first display. If you see this message
once only, and your connections are correct, your stack should be operating properly. Only
repeat displays of this message indicate a problem.
Troubleshooting image copy issues
The copy tftp flash command copies the image to all stack units including the Active Controller. The
copy flash flash command copies the image from the primary or secondary flash on the Active
Controller to the primary or secondary flash image of a stack member, respectively. If you are
unable to copy an image to one or more stack units, check the following:
• Make sure the unit is actually part of the stack. Use the show stack command.
• If a unit joins a stack after the image copy command was issued, you will need to copy the
image to this unit separately.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
153
5
Stack mismatches
Stack mismatches
When a stack mismatch occurs, the Active Controller can put any stack member into a
non-operational state, which disables all of the ports except the stacking ports. Stack mismatches
can occur for a variety of reasons, which are discussed in this section.
NOTE
The Active Controller can still download an image to the non-operational unit.
The Active Controller generates a log message whenever it puts a stack unit into a non-operational
state. The following examples describe the types of mismatches and the related log message:
• Advanced feature mismatch - The Active Controller is enabled for advanced features (such as
BGP) and the stack unit is not enabled.
Stack: Unit 2 00e0.1020.0100 doesn’t have the matching advanced feature
privileges
• Image mismatch - A stack unit is running a different software image than that of the Active
Controller.
Stack: Unit 2 00c0.1020.0100 image mismatch
• Configuration mismatch - The module configuration for a stack unit does not match the
reserved configuration on the Active Controller.
Stack: Unit 2 00e0.1020.0100 config mismatch
• Memory allocation mismatch - The Active Controller does not have enough memory to
accommodate the stack unit.
Stack: Malloc failure for unit 2.00e0.1020.0100
These mismatches are described in the following sections.
Image mismatches
Advanced feature privileges (PowerConnect B-Series FCX )
For PowerConnect B-Series FCX stack units, advanced feature privileges must be enabled to run
advanced features such as BGP. Both Active and Standby units must be enabled for advanced
features for these features to operate across the stack. A unit that is not enabled for these features
is put into a non-operational state.
If the Active Controller is not enabled for advanced features, these features will not operate on the
stack.
IronStack technology requires that all stack units run the same version of the software image. In
cases where the software version differs, there are two levels of mismatch, major and minor.
154
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Image mismatches
5
Major mismatch
A major mismatch indicates an Interprocessor Communications (IPC)-related data structure
change, or an election algorithm change, or that a version of the software that does not support
stacking is installed on a unit. This can happen when the software undergoes a major change
(such as a change from 05.0.00 to 05.1.00). When a major mismatch occurs, the system logs and
prints a message similar to the following.
Warning! Recv 424 IPC in 1m from 0012.f21b.a900 e1/1/25: wrong version 5 !=6.
Please make sure all units run the same image.
In a major mismatch, the stack cannot be built and will not operate. You must download the correct
version of the software to the mismatched units individually.
Minor mismatch
With a minor mismatch, an operating stack can still exist, but traffic is dropped from all ports
except for the stacking ports for units with the mismatched software. You can download the correct
image to the mismatched devices from the Active Controller. A minor software mismatch means
that there is no IPC or election algorithm change, but there is a release version disparity. Minor
software mismatches can happen with patch release upgrades. The system logs and prints a
message similar to the following.
Warning! put stack unit 2 to non-operational reason=image mismatch
The show stack command displays output similar to the following.
PowerConnect# show stack
alone: standalone, D: dynamic config, S: static config
ID Type
Role
Mac Address
Pri
State Comment
1 S FCX624 active 0012.f2eb.a900
128
local Ready
2 S FCX648 standby 00f0.424f.4243
0
remote NON-OP: image mismatch
3 S FCX624 member 00e0.5201.0100
0
remote Ready
If the configuration of a stack unit does not match the configuration of the Active Controller, the
stack unit will not function. You must manually correct the configuration error for the unit to
become operational within the stack. In this example, unit 2 is non-operational due to an image
mismatch. To correct this situation, use the copy flash flash command (refer to “Copying the flash
image to a stack unit from the Active Controller” on page 126).
Configuration mismatch
Generally, when a stack unit is added to or removed from the stack, its static configuration is not
overwritten by the Active Controller. However, secure-setup allows you to overwrite a static
configuration on a unit, in which case the Active Controller deletes the configuration for the old unit,
and adds the configuration of the new unit.
A configuration mismatch occurs when the base module configuration for a replacement stack unit
does not match the run time configuration on the Active Controller .If the configuration on the
Active Controller is static, it cannot be overwritten by the new configuration, and a configuration
mismatch occurs.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
155
5
Image mismatches
Configuration mismatches can happen during manual setups, or when moving a unit from one
stack to another stack. Secure-setup will try to overwrite a configuration mismatch even if the
configuration is static. The overwrite attempt may fail if there are multi-slot trunk or LACP
configurations on the ports of the unit to be overwritten. If this is the case, secure-setup will be
unable to resolve the mismatch.
When you renumber identical units using secure-setup, the configurations are not mapped to the
new units (since they match exactly). However, if you switch the IDs of units that are not identical, a
configuration mismatch occurs.
Configuration mismatches can also occur when LACP or multi-slot trunking configurations exist on
the modules of replacement units. In these cases, you will need to manually remove the LACP or
multi-slot trunking configuration on the replacement unit before you try to add it to the stack.
When a configuration mismatch occurs, port-related functions on all ports are disabled on the
mismatched unit (except for the stacking ports). All other functions are unaffected. For example,
the Active Controller can still copy the unit's image or reset the unit. Please refer to “Recovering
from a mismatch” on page 156.
Memory allocation failure
A memory allocation (malloc) failure occurs when the Active Controller does not have enough
memory to run a stack unit. This failure may occur if you configure large numbers (for example, 4 K
of VLANs, or STP instances (for example, 255).in the router image. This message means that the
Active Controller is low on memory after allocating these resources and does not have enough
remaining memory to control a stack member. You can correct this by reducing the number of
VLANs or STP instances.
NOTE
After you make configuration changes such as number of VLANs or STP instances, you must reset
the stack.
Recovering from a mismatch
When a configuration mismatch occurs, the Active Controller logs and displays a configuration
mismatch message, and puts the mismatched unit into a non-operational state. In the following
example, the original stack unit 3 has failed, and a replacement unit has been installed that does
not match the configuration of the original unit. You should see the following message.
Warning! put stack unit 3 to non-operational reason= config mismatch
Follow the steps given below to recover from a configuration or image mismatch.
1. Enter the stack secure-setup command.
2. Enter the show stack command to see the status of the stack, and a show running-config
command to see the configurations of the stack units. If secure-setup does not resolve the
configuration mismatch, proceed to step 3.
PowerConnect# show
alone: standalone,
ID Type
Role
1
FCX624 active
2
FCX648 member
3
FCX624 standby
156
stack
D: dynamic config,
Mac Address
Pri
0012.f2eb.a900 128
00f0.424f.4243
0
00e0.5201.0100
0
S: static config
State
Comment
local
Ready
remote
Ready
remote
NON-OP: config mismatch
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Image mismatches
5
PowerConnectt# show running config
stack unit 1
module 1 FCX-24-port-management-module
module 3 FCX-cx4-2-port-16g-module
module 4 FCX-xfp-2-port-16g-module
priority 128
stack unit 2
module 1 FCX-24-port-management-module
module 3 FCX-xfp-2-port-16g-module
stack unit 3
module 1 FCX-48-port-management-module
module 2 FCX-cx4-2-port-16g-module
module 3 FCX-cx4-2-port-16g-module
stack enable
3. To resolve the mismatch, you must remove the configuration for stack unit 3. Use the following
command.
PowerConnect# no stack unit 3
If you are unable to remove the configuration because of a multi-slot trunk configuration, it
means secure-setup cannot overwrite the Active Controller configuration due to multi-slot
trunking configurations on the ports of the unit to be overwritten. You must first manually
remove the multi-slot trunk configuration.
4. When you have successfully deleted the mismatched stack unit, a re-election is triggered, and
the Active Controller learns the correct module configuration from the Standby Controller or
from other stack members.
Follow the steps given below to recover from an image mismatch.
1. Use the copy flash flash command to replace a mis-matched image with the correct image.
Refer to “Copying the flash image to a stack unit from the Active Controller” on page 126.
2. Reset the unit. After the reset, the unit will contain the new image and the mis-match condition
will not exist. To verify, use the show stack command.
Troubleshooting secure-setup
Secure-setup can be used to form linear and ring stack topologies. For information about the
procedure, refer to “Scenario 1 - Configuring a three-member IronStack in a ring topology using
secure-setup” on page 101. During this procedure, if secure-setup does not detect all the units that
should be detected, perform the following checks:
•
•
•
•
Make sure that all the cables are properly connected
Make sure that all the relevant ports are in UP state
Make sure that all the units are running the same image
Make sure that you issue the stack enable command only on the unit that will serve as the
Active Controller
• Make sure that stack disable is not configured on any prospective members
• Make sure that the connection is sequential (refer to “IronStack terminology” on page 96,
Sequential Connection)
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
157
5
More about IronStack technology
If secure-setup times out (this may happen due to inactivity), you will not be able to make any
changes in your configuration or stack topology until you restart the session by entering the stack
secure-setup command.
The unit discovery process is triggered when secure-setup is initiated. However, if the stack unit is
placed in a topology where another unit in the stack is already running the discovery process, the
current discovery process is terminated. If this is the case, you will see a message similar to the
following.
"Topology discovery is already in progress originated from . Please
try later."
This means a discovery process is already active and was initiated from the unit with the
mentioned in the message. You will need to re-issue secure-setup.
If there is already an active discovery process, secure-setup may not discover all the intended units.
If this is the case, you will need to restart the secure-setup process.
Troubleshooting unit replacement issues
If you are unsuccessful in building a stack using the automatic setup process (refer to “Scenario 2 Configuring a three-member IronStack in a ring topology using the automatic setup process” on
page 105), or adding or replacing a unit in a stack, consider the following issues:
•
•
•
•
•
Make sure that the number of units in your stack does not exceed the maximum of 8
Make sure that the replacement unit is a clean unit (does not contain a startup-config.txt file)
Make sure that the replacement unit running configuration does not contain “stack enable”
Make sure the replacement unit running configuration does not contain “stack disable”
Make sure that the configurations of the stack ports on the Active Controller match the
physical connections to the unit
More about IronStack technology
This section discusses stacking technology in greater detail than the information presented in
Section 1.
Configuration, startup configuration files and stacking flash
Stacking system behavior is defined by the run time configuration, which can be displayed using
the show run command. The write memory command stores the run time configuration in a flash
file called startup-config.txt. During bootup, the system reads and applies the startup-config.txt file
to the run time configuration. The startup-config.txt file can be shown using the show config
command.
The stacking system installs a stacking.boot file on each unit that tells the unit what its role is
during the boot process. The stacking.boot file is generated whenever there is an election that
defines the roles for all units.
When an Active Controller is booted, or a write memory command is issued, the Active Controller
synchronizes its startup-config.txt file to every stack unit. The original startup-config.txt files in the
Standby Controller and other stack members are renamed to startup-config.old. If you issue the
“stack unconfigure me” command on the Standby Controller or stack member directly, these units
158
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
More about IronStack technology
5
will recover their original startup-config.txt files and reboot as standalone devices. If you enter the
stack unconfigure all command from the Active Controller all devices will recover their old
startup-config.txt files and become standalone devices. When this happens, the startup-config.old
file is renamed to startup-config.txt, and the stacking.boot file is removed. For more information,
refer to “Unconfiguring an IronStack” on page 130.
Whenever a change is made to a stack unit's configuration, such as priority, (which could affect
stack elections) an election is held, and the result is written into the stacking.boot file. A prompt
message appears on the console that suggests you do a write memory. For an Active Controller role
change to take effect, you will need to reset the entire stack.
If you do not do a write memory, and reset the stack, the stack units will continue to operate in their
roles as defined by the stacking.boot file. After the reset, each unit readjusts based on the current
run time configuration. However, you may get different results depending on what has not been
saved. If you have renumbered the stack unit IDs, you may see a configuration mismatch, because
your changes no longer match the Active Controller configuration.
If you change priorities to elect an Active Controller, the new Active Controller will assume its role
after a reboot whether you have done a write memory or not. If you do not save your priority change
before the next reboot, the reboot will trigger an election that may result in a different winner based
on the priority in the unsaved configuration. The new winner assumes its role after the next reboot.
If you change the stacking port configuration and do not save your changes, you may encounter
connectivity errors. To recover from a configuration error, run Secure Startup to define the correct
stacking port.
NOTE
You should always do a write memory after making stacking-related configuration changes such as
priority and stacking ports. If you do not want to keep the changes, change the configuration back
to the previous version, and do a write memory. Do not discard configuration changes by using the
reset without a write memory.
IronStack topologies
IronStack technology supports both linear and ring stack topologies. Because the unicast switching
follows the shortest path in a ring topology, this topology offers the strongest redundancy. When the
ring is broken, the stack recalculates the forwarding path the resumes the flow of traffic within a
few seconds. In a ring topology, all stack members must have two stacking ports, however, In a
linear topology, both end units use only one stacking port, leaving the other port available as a data
port. To see an illustrated example of each topology, refer to “IronStack topologies” on page 98.
Port down and aging
If a unit is powered down, or the stacking link is removed, the system immediately detects the port
down and knows that its neighbor is gone. That unit is immediately removed from the Active
Controller. If a unit is gone or no longer stack-enabled, but its stacking link is still on, it will take 20
seconds to age the neighbor out. The following message will be logged and displayed.
Warning! my mac=00f0.424f.4243, age out up-stream
Device roles and elections
There are three distinct roles played by units that are part of an IronStack:
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
159
5
More about IronStack technology
• Active Controller
• Standby Controller
• Stack member
Active Controller
The Active Controller contains the saved and running configuration files for each stack member.
The configuration files include the system-level settings for the stack, and the interface-level
settings for each stack member, as well as MIB counters and port status. The Standby Controller
also has a synchronized copy of the Active Controller startup config file for use in the event the
Active Controller fails.
When a stack is formed, the console function for each stack member is automatically redirected to
the Active Controller console. The Active Controller console port handles all stack management
functions, as well as ping, Telnet sessions, and tftp image downloads for every stack member. If
you connect to the console port on a stack member that is not the Active Controller, you are
automatically directed through the console of the Active Controller.
The Active Controller synchronizes its start-up configuration with the Standby Controller and the
rest of the stack members. You can recover the previous flash configuration of the Standby
Controller and the stack members by issuing the stack unconfigure command. For an example of
this command and the output generated, refer to “Unconfiguring an IronStack” on page 130.
The Active Controller may reset the rest of the stack members, if necessary. However, if the Active
Controller itself must be reset because of a role or ID change, you must issue the reset command.
If the Active Controller fails, the Standby Controller waits 30 seconds, and then takes over as Active
Controller, resetting itself and all other stack members. If the old Active Controller becomes
operational, it may or may not resume its role as Active, depending on the configured priorities.
Standby Controller
In addition to the Active Controller, another stack member is elected as the Standby Controller.
After a default interval of 30 seconds, the Standby Controller takes over if the Active Controller
fails.
NOTE
Because it can take as long as 20 seconds to age out a neighbor, the Standby takeover period may
last up to 50 seconds. Refer to “Port down and aging” on page 159.)
The Standby Controller synchronizes its configuration with the Active Controller at each reset.
Bootup role
When a stack unit boots, it boots in a particular role, such as standalone, Active Controller, Standby
Controller, or stack member. When the bootup role is Standby Controller or stack member, the CLI
available to the unit is limited to show and stack commands. A unit in the role of Standby or stack
member will not act without instructions from the Active Controller. To convert a Standby Controller
or stack member into a standalone device, use the stack unconfigure me command, (refer to
“Unconfiguring an IronStack” on page 130).
The last line of the show version output identifies the unit role unless the unit is in standalone
mode.
160
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
More about IronStack technology
5
Example
My stack unit ID = 1, bootup role = active
My stack unit ID = 3, bootup role = standby
Active Controller and Standby Controller elections
Whenever there is a topology change in the stack (a reset, unit failure, or the addition or removal of
members), elections are held to determine the status of the Active Controller and Standby
Controller. The results of the election take effect after the next stack reset.
The following conditions, in the order shown, determine which units will serve as Active Controller
and Standby Controller after an election:
• Boot as Active Controller - Indicates that a unit was previously Active Controller before the
current boot sequence and will again assume the role of Active Controller when two standalone
units are combined into a stack. When a third standalone unit joins the stack, a current Active
Controller becomes subject to the other factors in this list. The reason for this hierarchy of
factors is to achieve a predictable winner regardless of the boot up sequence for a unit. You
can upgrade your current Active Controller to “boot as active controller” status by performing a
write memory. The system interprets the write memory action as a directive to maintain the
current Active Controller role regardless of resets or a new unit joining the stack.
• Priority - The unit with the highest priority value.
• Greater number of members - The unit that has control over the greater number of stack
members.
• Lowest boot stack ID - The unit that has the lowest boot stack ID (1-8, 1 is the lowest).
• MAC address - The member with the lowest MAC address.
Active Controller and Standby Controller resets
If the Active Controller is reset or removed from the stack, the entire stack reloads and Active
Controller and Standby Controller elections are initiated. If the unit functioning as the previous
Active Controller is no longer part of the stack, the Standby Controller unit becomes the new Active
Controller. After a reset, if no stack member qualifies as Active Controller, the existing Standby
Controller waits 30 seconds and then assumes the role of Active Controller.
If both Active and Standby Controllers are removed the rest of the stack will continue to function
because they are operating on whatever is programmed in the hardware. The stack members will
not be able to learn any new addresses. You will see the following message every few minutes.
Stack member is non-operational because of no Active or Standby Controller
You can recover to standalone mode by “stack unconfigure me”
Use stack unconfigure me to restore the units into standalone devices with a pre-stacking
configuration.
Selecting a standby unit
You can choose a Standby Controller by configuring a stack unit priority to be the second highest, or
the same as the Active Controller. If the priorities are configured the same for both, when the
original Active Controller fails, the Standby Controller takes over. If the original Active Controller
becomes active again, it will not win back its active role, which helps to minimize interruption of the
stack. However, if the original Active Controller has the higher priority, it will win back its role and
reset all of the stack units.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
161
5
PowerConnect B-Series FCX hitless stacking
Standby Controller election criteria
The Standby Controller election is based on the following criteria.
1. The highest priority
2. Bootup as Active Controller
3. Bootup as Standby Controller
4. The lowest boot ID
5. The lowest MAC address
Since Standby election candidates must have startup configurations that have been synchronized
with the Active Controller, if the Active Controller does not have a startup-config.txt file, there will
not be a Standby Controller. Once a write memory is performed on the Active Controller, the
startup-config.txt file is written and synchronized to all stack members, and a Standby Controller
can be elected.
PowerConnect B-Series FCX hitless stacking
Hitless stacking is supported on FCX units in an IronStack. It is a high-availability feature set that
ensures sub-second or no loss of data traffic during the following events:
•
•
•
•
Active Controller failure or role change
Software failure
Addition or removal of units in a stack
Removal or disconnection of the stacking cable between the Active and Standby Controllers
During such events, the Standby Controller takes over the active role and the system continues to
forward traffic seamlessly, as if no failure or topology change has occurred. In software releases
that do not support hitless stacking, events such as these could cause most of the units in a stack
to reset, resulting in an impact to data traffic.
The following hitless stacking features are supported:
Hitless stacking switchover – A manually-controlled (CLI-driven) or automatic switchover of the
Active and Standby Controllers without reloading the stack and without any packet loss to the
services and protocols that are supported by hitless stacking. A switchover is activated by the CLI
command stack switch-over. A switchover might also be activated by the CLI command priority,
depending on the configured priority value.
Hitless stacking failover – An automatic, forced switchover of the Active and Standby Controllers
because of a failure or abnormal termination of the Active Controller. In the event of a failover, the
Active Controller abruptly leaves the stack and the Standby Controller immediately assumes the
active role. Like a switchover, a failover occurs without reloading the stack. Unlike a switchover, a
failover generally happens without warning and will likely have sub-second packet loss (packets
traversing the stacking link may be lost) for a brief period of time.
The services and protocols supported by hitless stacking are listed in Table 37 on page 164.
Hitless stacking is disabled by default. To enable it, refer to “Enabling hitless stacking” on
page 174.
162
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
PowerConnect B-Series FCX hitless stacking
5
Supported events
The following events are supported by hitless stacking:
•
•
•
•
Failover
Switchover
Priority change
Role change
Non-supported events
The following events are not supported by hitless stacking. These events require a software reload,
resulting in an impact to data traffic.
• Unit ID change – When a stack is formed or when a unit is renumbered using secure-setup.
• Stack merge – When the old Active Controller comes back up, it reboots. If it has fewer number
of members than the Active Controller, it loses the election, regardless of its priority. If it has a
higher priority, it becomes the Standby Controller after the reboot and is synchronized with the
Active Controller. Next, a switchover occurs and it becomes the new Active Controller.
Supported protocols and services
Table 37 lists the services and protocols that are supported by hitless stacking. Table 37 also
highlights the impact of a hitless switchover or failover to the system’s major functions.
NOTE
Services and protocols that are not listed in Table 37 will encounter disruptions, but will resume
normal operation once the new Active Controller is back up and running.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
163
5
PowerConnect B-Series FCX hitless stacking
TABLE 37
Hitless-supported services and protocols – PowerConnect B-Series FCX
Traffic type
Supported protocols and services
Impact
Layer 2 switched traffic,
including unicast and
multicast
+
System-level
+
Layer 4
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
802.1p and 802.1Q
802.3ad – LACP
DSCP honoring and Diffserv
Dual-mode VLAN
IGMP v1, v2, and v3 snooping
IPv4 ACLs
Layer 2 ACLs
Layer 2 switching (VLAN and 802.1Q-in-Q)
MAC-based VLANs
MLD v1 and v2 snooping
MRP
Multiple spanning tree (MSTP)
Physical port/link state
PIM SM snooping
Port mirroring and monitoring
Port trunking
Rapid spanning tree (RSTP)
Spanning tree (STP)
ToS-based QoS
Traffic policies
UDLD
VSRP
Layer 2 switched traffic is not impacted during a hitless
stacking event. All existing switched traffic flows
continue uninterrupted.
BGP4
IPv4 unicast forwarding
OSPF v2
OSPF v2 with ECMP
Static routes
VRRP
VRRP-E
Layer 3 routed traffic for supported protocols is not
impacted during a hitless stacking event.
Layer 3 IPv4 routed traffic
(unicast)
New switched flows are not learned by the switch
during the switchover process and are flooded to the
VLAN members in hardware. After the new Active
Controller becomes operational, new switched flows
are learned and forwarded accordingly. The Layer 2
control protocol states are not interrupted during the
switchover process.
All existing Layer 3 IPv4 multicast flows and receivers
may be interrupted. Traffic will converge to normalcy
after the new active module becomes operational.
Other Layer 3 protocols that are not supported will be
interrupted during the switchover or failover.
If BGP4 graceful restart or OSPF graceful restart is
enabled, it will be gracefully restarted and traffic will
converge to normalcy after the new active module
becomes operational. For details about OSPF graceful
restart, refer to “OSPF graceful restart” on page 930.
For details about BGP4 graceful restart, refer to “BGP4
graceful restart” on page 987.
Management traffic
164
N/A
All existing management sessions (SNMP, TELNET,
HTTP, HTTPS, FTP, TFTP, SSH etc.), are interrupted
during the switchover process. All such sessions are
terminated and can be re-established after the new
Active Controller takes over.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
PowerConnect B-Series FCX hitless stacking
TABLE 37
5
Hitless-supported services and protocols – PowerConnect B-Series FCX
Traffic type
Supported protocols and services
Impact
Security
•
Supported security protocols and services are not
impacted during a switchover or failover, with the
following exceptions:
• 802.1X is impacted if re-authentication does not
occur in a specific time window.
• MDPA is impacted if re-authentication does not
occur in a variable-length time window.
• In some cases, a few IP source guard packets may
be permitted or dropped.
• If 802.1X and MDPA are enabled together on the
same port, both will be impacted during a
switchover or failover. Hitless support for these
features applies to ports with 802.1X only or
multi-device port authentication only.
• For MAC port security, secure MACs are
synchronized between the Active and Standby
Controllers, so they are hitless. However, denied
MACs are lost during a switchover or failover but
may be relearned if traffic is present.
•
•
•
•
•
•
•
802.1X, including use with dynamic ACLs
and VLANs
EAP with RADIUS
IPv4 ACLs
DHCP snooping
Dynamic ARP inspection
IP source guard
Multi-device port authentication (MDPA),
including use with dynamic ACLs and
VLANs
MAC port security
Configured ACLs will operate in a hitless manner,
meaning the system will continue to permit and deny
traffic during the switchover or failover process.
After a switchover or failover, the new Active Controller
will re-authenticate 802.1X or MDPA sessions that
were being forwarded in hardware. The hardware
continues to forward them (even with dynamic ACL,
dynamic VLAN, or both) while re-authentication occurs.
After trying to re-authenticate for a certain amount of
time (depending on the number of sessions to
re-authorize), sessions that did not re-authenticate are
removed.
Other services to
Management
•
•
•
•
•
•
•
AAA
DHCP
sFlow
SNMP v1, v2, and v3
SNMP traps
SNTP
Traceroute
Supported protocols and services are not impacted
during a switchover or failover.
DNS lookups will continue after a switchover or failover.
This information is not synchronized.
Ping traffic will be minimally impacted.
NOTE: If the FCX stack is rebooted, sFlow is disabled
on standby and member units until the
configuration is synchronized between the
Active and Standby Controllers.
Configuration notes and feature limitations
• For hitless stacking on the PowerConnect B-Series FCX, Dell recommends that you configure
the IronStack MAC address using the stack mac command. Without this configuration, the
MAC address of the stack will change to the new base MAC address of the Active Controller.
This could cause a spanning tree root change. Even without a spanning tree change, a client
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
165
5
PowerConnect B-Series FCX hitless stacking
(for example, a personal computer) pinging the stack might encounter a long delay depending
on the client MAC aging time. The client won’t work until it ages out the old MAC address and
sends ARP requests to relearn the new stack MAC address. Refer to “Manual allocation of the
IronStack MAC address” on page 120.
• PBR is not supported by hitless stacking. When PBR is configured in an FCX IronStack, the
stack will reload in the event of a failover. Also, manual switchover or internal switchover due to
a higher priority standby is not allowed.
• Layer 3 multicast traffic is not supported by hitless stacking.
• After a switchover or failover, the Syslog may contain invalid (non-existent) port numbers in
messages such as “Interface state up". This is because some messages from the
old Active Controller will remain in the Syslog after a switchover or failover.
• Failover for devices connected to the management port is not supported. For example, if during
a failover, an end station is connected to the stack through the management port of the Active
Controller, the connection will be shut down. After the failover, the management port on the
new Active Controller will work.
• The following describes hitless stacking limitations with software-based licensing:
• If the Active Controller has a superior license (for example, BGP support) compared to all
other units in the stack, all of the units except for the Active Controller will be placed in a
non-operational state.
• The Standby Controller cannot have a “superior” license compared to the Active Controller.
For example, if unit 2 has a license to run BGP whereas the Active Controller does not, unit
2 has a superior license and will be allowed to join the stack, but will not be elected as the
Standby Controller.
• If software-based licensing is installed on the Active Controller after the stack is up and
running, the licensed feature will function on the Active Controller ports, but will not
function on ports on other units of the stack.
What happens during a hitless stacking switchover or
failover
This section describes the internal events that enable a controlled or forced switchover to take
place in a hitless manner, as well as the events that occur during the switchover.
Real-time synchronization among all PowerConnect B-Series FCX units in a stack
Hitless stacking requires that the Active Controller, Standby Controller, and stack members are fully
synchronized at any given point in time. This is accomplished by baseline and dynamic
synchronization of all units in a stack.
When an PowerConnect B-Series FCX stack is first booted and becomes operational, baseline
synchronization occurs across all of the units in the stack. The Active Controller copies the current
state of its CPU to all units of the stack, including the Standby Controller. The information received
from the Active Controller is programmed locally in hardware on all units. The information includes:
• Start-up and run-time configuration (CLI) – These files are copied to the Standby Controller
only.
• Layer 2 protocols – Layer 2 protocols such as STP, RSTP, MRP, and VSRP run concurrently on
both the Active and Standby Controller.
166
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
PowerConnect B-Series FCX hitless stacking
5
• Hardware Abstraction Layer (HAL) – This includes the prefix-based routing table, next hop
information for outgoing interfaces, and tunnel information.
• Layer 3 IP forwarding information – This includes the routing table, IP cache table, and ARP
table, as well as static and connected routes.
• Layer 3 routing protocols are not copied to any of the units in the stack, but remain in init state
on the Standby Controller until a switchover occurs. Peer adjacency will be restored after a
switchover. If BGP4 or OSPF graceful restart are enabled during a switchover, the Standby
Controller (new Active Controller) will initiate a graceful restart and a new set of routes will be
relearned. The new set of routes will be the same as the old routes, except in the case of a
network change.
When control protocols are synchronized and protocol synchronization timers have expired, the
Standby Controller will be in hot-standby mode, meaning the Standby Controller will be ready to
take over as the Active Controller. In the event of a switchover, the Standby Controller will pick up
where the active module left off, without interrupting data traffic.
After baseline synchronization, any new events that occur on the Active Controller will be
dynamically synchronized on the Standby Controller. Examples of such events include:
•
•
•
•
•
•
CLI/HTTP/SNMP configurations
CPU receive packets
Link events
Interrupts
Layer 2 and Layer 3 forwarding table updates
Dynamic user authentication updates such as 802.1X or multi-device port authentication
Dynamic events are synchronized in such a way that if the Active Controller fails before fully
executing an event, the Standby Controller (newly Active Controller) will execute the event after the
failover. Also, if the Active Controller aborts the event, the Standby Controller will abort the event as
well.
After a switchover, the new Active Controller receives updates from the stack members and sends
verification information to the stack members to ensure that they are synchronized.
NOTE
If there is no Active Controller after a reload, the bootup standby assumes the active role in
approximately 60 seconds without a reload. A bootup standby is the device that was the Standby
Controller before the reload. It may not be the current Standby Controller.
NOTE
The events described above occur internally and do not create or affect the external network
topology.
How a Hitless switchover or failover impacts system functions
Fora description of the feature’s impact to major system functions, refer to Table 37 on page 164.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
167
5
PowerConnect B-Series FCX hitless stacking
Standby Controller role in hitless stacking
In software releases that do not support hitless stacking, the Standby Controller functions as a
dummy device, meaning it provides limited access to the CLI, such as show, stack, and a few debug
commands. The Active Controller can access the full range of the CLI. The Standby Controller
synchronizes its configuration with the Active Controller at each reset.
With the introduction of hitless stacking, the Standby Controller shadows the Active Controller. The
role or behavior of the Standby Controller with hitless stacking is as follows:
• The local console on the Standby Controller still accepts only show, stack, and a few debug
commands.
• The runtime configuration on the Standby Controller is synchronized with the Active Controller
whenever there is a configuration change.
• Protocols are configured in the runtime configuration, but no protocol packets are sent out on
the Standby.
• The state of every unit is known, including the state of the Active Controller. The show
commands will display current information, such as STP or port states.
• When a failover occurs, the Standby Controller will use its current runtime configuration. The
configuration could be different from the Active Controller if the last configuration transmission
was lost.
• After a failover, the new Active Controller (old standby) programs all other units in hardware,
based on its runtime configuration.
Standby Controller election
Candidates for Standby Controller must meet the following criteria:
• The unit is operational and the image and module configuration match that of the Active
Controller
• The runtime configuration matches that of the Active Controller
• The unit does not have a “superior” license compared to the Active Controller. For example, if
unit 2 has a license to run BGP whereas the Active Controller does not, unit 2 has a superior
license and will be allowed to join the stack, but will not be elected as the Standby Controller.
If more than one unit in the stack meets this criteria, the Standby Controller is chosen according to
the following criteria, in the order shown:
•
•
•
•
Priority – The unit with the highest priority value.
Current standby – The unit that is currently the Standby Controller.
Bootup master – The unit that was the Active Controller before the stack was reloaded.
Bootup standby – The unit that was the Standby Controller before the stack was reloaded.
Once the Standby Controller is identified, the following internal events take place.
1. The Standby Controller is assigned by the Active Controller 30 to 60 seconds after election (60
seconds if the Active Controller boots up in less than 120 seconds).
2. The Standby Controller receives and processes the runtime configuration sent by the Active
Controller.
3. The Standby Controller learns the protocols within 70 seconds.
168
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
PowerConnect B-Series FCX hitless stacking
5
When the Standby Controller is fully synchronized, the system will be ready for a switchover or
failover.
Runtime configuration mismatch
In some cases, such as a runtime configuration mismatch between the Active Controller and
candidate Standby Controller, the Standby Controller cannot be assigned by the Active Controller
unless the candidate Standby Controller is reloaded.
As illustrated below, the show stack command output will indicate whether there is a runtime
configuration mismatch.
PowerConnect#sh stack
alone: standalone, D: dynamic config, S: static config
ID
Type
Role
Mac Address
Pri State
Comment
1 S FCX624S
active 00e0.5201.0000 30 local
Ready
active
+---+
+---+
-2/1| 2 |2/2--2/1| 1 |2/2+---+
+---+
Note: There is no standby. Reason: u2: diff run-time config
Current stack management MAC is 00e0.5201.0000
Note: no "stack mac" config. My MAC will change after failover.
Support during stack formation, stack merge,
and stack split
This section illustrates hitless stacking support during stack formation, stack merge, and stack
split.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
169
5
PowerConnect B-Series FCX hitless stacking
Figure 15 illustrates hitless stacking support during stack formation. Operational stages 1 and 2
are also shown in this illustration.
FIGURE 15
Hitless stacking support during stack formation
Device
stackformation
formation
FCX stack
New Stack
A stack is created using secure setup or “stack enable”
Active 1
Member 2
Member 3
Member 2 and 3 become “orphans”
1
The stack is formed and fully operational after
all units except the Active controller is rebooted
er
ilov
Fa
Switchover
Wait for 30 sec. (if the Active is up > 2 min.)
Wait for 60 sec. (if the Active is up < 2 min.)
All units (including Standby)
are rebooted
1
Standby assigned by the Active
er
ilov
Fa
Switchover
Configuration synchronized (running
config is copied from the Active)
ver
ilo
Fa
Switchover
Configuration parsed on Standby
er
ilov
Not allowed
Standby becomes Active immediately (no delay),
no reboot occurs, configuration parsing and
hot swap take place. The Standby is assigned
after 30 seconds. Traffic loss is expected.
Not allowed
Standby becomes Active immediately, no reboot
occurs, hot swap take place. The Standby is
assigned after 30 seconds. Traffic loss is expected.
Fa
Switchover
End of Stage 1
Not allowed
Other units are hot swapped
70 sec. for protocol learning
r
ove
Standby becomes Active immediately, no reboot
occurs. The Standby is assigned after 30 seconds.
Traffic loss is expected.
il
Fa
Switchover
Existing stack (after “write mem” and “reload”)
Active 1
Member 2
Member 3
Not allowed
Not allowed
Protocol ready
End of Stage 2
The stack is fully operational and ready
for rapid failover and switchover
ver
Standby becomes Active (no delay), no reboot.
Standby is assigned after 30 seconds.
No traffic loss is expected.
ilo
Fa
Switchover
Active 1
Member 2
Member 3
170
Allowed. No traffic loss is expected.
er
1
After the stack boots up, Member 2
is a “boot up Standby”. There is
no Standby assigned yet.
ilov
The boot up Standby waits
for 40 seconds then reboots
all units including itself.
Fa
Switchover
Not allowed
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
PowerConnect B-Series FCX hitless stacking
5
Figure 16 illustrates hitless stacking support during a stack merge.
FIGURE 16
Hitless stacking support during a stack merge
Device stack merge
Stack 1
Active 1 (pri=30)
Standby 2 (pri=20)
Member 3 (pri=10)
Member 4 (pri=0)
Stack 2
Active 1 (pri=100)
Standby 2 (pri=50)
1
1
Member 1 (pri=30)
Member 2 (pri=20)
Member 3 (pri=10)
Member 4 (pri=0)
Active 5 (pri=100)
Standby 6 (pri=50)
1
When hitless failover is enabled, the stack with
more units will win. Stack 2 will reload and merge
with Stack 1. Stack 2 will retain its IDs.
Stack 1
Active 1 (pri=30)
Standby 2 (pri=20)
Member 3 (pri=10)
Member 4 (pri=0)
Stack 2
Active 1 (pri=100)
Standby 2 (pri=50)
Member 3 (pri=0)
Member 4 (pri=0)
1
1
Active 1 (pri=100)
Standby 2 (pri=50)
Member 3 (pri=0)
Member 4 (pri=0)
Member 5 (pri=30)
Member 6 (pri=20)
Member 7 (pri=10)
Member 8 (pri=0)
1
1
If the number of units in both stacks are the same,
the stack with the highest active priority will win.
Stack 1 will reload and merge with Stack 2.
Stack 1/MAC A
Active 1 (pri=100)
Standby 2 (pri=20)
Member 3 (pri=10)
Member 4 (pri=0)
Stack 2/MAC B
Active 1 (pri=100)
Standby 2 (pri=50)
Member 3 (pri=0)
Member 4 (pri=0)
1
1
Active 1 (pri=100)
Member 2 (pri=20)
Member 3 (pri=10)
Member 4 (pri=0)
Standby 5 (pri=100)
Member 6 (pri=50)
Member 7 (pri=0)
Member 8 (pri=0)
1
1
If the number of units in both stacks is the same
and both Active controllers have the same priority,
the stack with the longer system up time (by 30
seconds or more) will win. Otherwise, the lowest MAC
address will win. Stack 2 will reload and merge with
Stack 1.
Device stack merge when the old Active controller comes back up
Active 1 (pri=100)
Active 2 (pri=50)
Standby 3 (pri=10)
Member 4 (pri=0)
Member 5 (pri=0)
1
Active 1 (pri=100)
Standby 2 (pri=50)
Member 3 (pri=10)
Member 4 (pri=0)
Member 5 (pri=0)
Member 6 (pri=0)
1
When hitless failover is enabled, the stack with
more units will win. Active 1 will reboot and merge
with the stack.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
171
5
PowerConnect B-Series FCX hitless stacking
Figure 17 illustrates hitless stacking support in a stack split.
FIGURE 17
Hitless stacking support in a stack split
stack split
Active 1 (pri=30)
Standby 2 (pri=20)
Member 3 (pri=10)
Member 4 (pri=0)
Active 1 (pri=30)
Standby 2 (pri=20)
1
1
Member 3 (pri=10)
Member 4 (pri=0)
The stack splits into one operational stack
and two “orphan” units.
Active 1 (pri=30)
Member 2 (pri=10)
Standby 3 (pri=20)
Member 4 (pri=0)
Active 1 (pri=30)
Standby 2 (pri=10)
1
Active 3 (pri=20)
Standby 2 (pri=0)
The stack splits into two operational stacks.
172
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
PowerConnect B-Series FCX hitless stacking
5
Hitless stacking default behavior
Hitless stacking is disabled by default. When disabled, the following limitations are in effect:
• If a failover occurs, every unit in the stack will reload
• Manual switchover is not allowed. If the CLI command stack switch-over is entered, the
following message will appear on the console:
Switch-over is not allowed. Reason: hitless-failover not configured.
• Internal switchover resulting from a priority change is blocked until the entire stack is reloaded
or hitless stacking is enabled. A priority change will trigger an election, but the newly-elected
winner will not immediately assume its role. For more information, refer to “Displaying pending
device roles” on page 174.
• If there is no Active Controller after a reload, the bootup standby will assume the active role
after reloading every unit in the stack, including itself.
• During a stack merge, the Active Controller with the highest priority will win the election and
reload every unit of the losing stack.
NOTE
Synchronization between the Active Controller, Standby Controller, and stack members will occur
whether or not hitless stacking is enabled.
When hitless stacking is enabled, the following behavior takes effect immediately:
• If a failover occurs, the stack will not reload.
• Manual switchover (CLI command stack switch-over) is allowed.
• If a priority change occurred while hitless stacking was disabled, and the configured priority
value requires a switchover, the system will start a 60-second timer before performing a
switchover. After the switchover, the highest priority standby will become the Active Controller.
• If there is no Active Controller after a reload, the bootup standby will assume the active role in
approximately 60 seconds without a reload.
• During a stack merge, the Active Controller with the larger number of units will win the election
and reload every unit of the losing stack. If two stacks have the same number of units, then the
priority, system up time, ID, then MAC address is compared. If two stacks have the same
number of units and the same priority, then the stack with the longest system up-time (by 30
seconds or more) will win the election. Otherwise, the smallest ID is compared next, followed
by MAC address. If the losing Active Controller has the highest priority, it will become a standby
after reloading and relearning the protocols. Finally, it will become the Active Controller after an
internal switchover.
NOTE
If the Active Controllers of two merging stacks have different hitless stacking settings (i.e.,
hitless stacking is enabled in one stack and disabled in the other), the default behavior (hitless
stacking disabled) will be used in the stack merge. After the merge, the winner will retain its
hitless stacking setting and runtime configuration for the merged stack.
You can use the show stack command to view whether or not hitless stacking is enabled. Refer to
“Displaying hitless stacking status” on page 174.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
173
5
PowerConnect B-Series FCX hitless stacking
Enabling hitless stacking
Hitless stacking is disabled by default. To enable it, enable hitless failover as described in
“Enabling hitless failover” on page 175.
Displaying hitless stacking status
You can use the show stack command to view whether or not hitless stacking is enabled. The
following example shows that hitless stacking is disabled.
PowerConnect#show stack
alone: standalone, D: dynamic config, S: static config
ID
Type
Role
Mac Address
Pri State
Comment
2 S FCX648S
member 0000.0000.0000
0 reserve
3 S FCX624
member 0024.3876.2640
0 remote Ready
5 S FCX624
standby 00e0.5200.0400 100 remote Ready
8 S FCX648
active 0024.3877.7980 128 local
Ready
active
standby
+---+
+---+
+---+
-2/1| 8 |2/2--2/2| 3 |2/1--2/1| 5 |2/2|
+---+
+---+
+---+
|
|
|
|-------------------------------------|
Standby u5 - No hitless failover. Reason: hitless-failover not configured
Syntax: show stack
Displaying pending device roles
When hitless stacking is disabled, a priority change will trigger an election, but the newly-elected
winner will not assume its role until the entire stack is reloaded or hitless stacking is enabled.
You can use the show stack command to view pending device roles. The “Role” column displays the
current role for each unit. The “Comment” column displays the role that will take effect after a
reload or when hitless stacking is enabled.
PowerConnect#show stack
alone: standalone, D: dynamic config, S: static config
ID
Type
Role
Mac Address
Pri State
Comment
2 S FCX648S
member 0000.0000.0000
0 reserve
3 S FCX624
standby 0024.3876.2640 200 remote Ready, active if reloaded
5 S FCX624
member 00e0.5200.0400 128 remote Ready, standby if reloaded
8 S FCX648
active 0024.3877.7980 128 local
Ready, member if reloaded
active
standby
+---+
+---+
+---+
-2/1| 8 |2/2--2/2| 3 |2/1--2/1| 5 |2/2|
+---+
+---+
+---+
|
|
|
|-------------------------------------|
Standby u3 - No hitless failover. Reason: hitless-failover not configured
174
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
PowerConnect B-Series FCX hitless stacking
5
Syntax: show stack
Hitless stacking failover
Hitless stacking failover provides automatic failover from the Active Controller to the Standby
Controller without resetting any of the units in the stack and with sub-second or no packet loss to
hitless stacking-supported services and protocols.
For a description of the events that occur during a hitless failover, refer to “What happens during a
hitless stacking switchover or failover” on page 166.
For a description this feature’s impact to major system functions, refer to Table 37 on page 164.
For an example of hitless failover operation, refer to “Hitless stacking failover example” on
page 176.
For feature limitations and configuration notes, refer to “Configuration notes and feature
limitations” on page 165.
Enabling hitless failover
To enable hitless failover, enter the following command at the Global CONFIG level of the CLI:
PowerConnect(config)#hitless-failover enable
The command takes effect immediately. Hitless switchover is allowed, and in the event of a failover,
the standby controller will take over the active role without reloading the stack.
Syntax: [no] hitless-failover enable
Use the no form of the command to disable hitless stacking once it has been enabled.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
175
5
PowerConnect B-Series FCX hitless stacking
Hitless stacking failover example
Figure 18 illustrates hitless stacking failover operation when the Active Controller fails.
FIGURE 18
Hitless stacking failover when the Active Controller fails
The stack comes back without the Active controller
.
The Active controller fails
after the stack reloads
Active 1
Member 2 = bootup Standby
Member 3
Member 4
Member 2 = bootup Standby
Member 3
Member 4
1
1
The bootup Standby will become the Active controller
in 50 seconds. The stack will not reload.
50 sec.
Active 2
Member 3
Member 4
1
30-60 sec.
Active 2
Standby 3
Member 4
1
Hitless stacking switchover
Hitless stacking switchover is a manually-controlled (CLI-driven) or automatic switchover of the
Active and Standby Controllers without reloading the stack and without any packet loss to the
services and protocols that are supported by hitless stacking. A switchover is activated by the CLI
command stack switch-over. A switchover might also be activated by the CLI command priority,
depending on the configured priority value.
By default, hitless switchover is not allowed. The default behavior is described in “Hitless stacking
default behavior” on page 173.
Hitless switchover can be used by a system administrator, for example, to perform maintenance on
a controller that has been functioning as the Active Controller.
For a description of the events that occur during a hitless stacking switchover, refer to “What
happens during a hitless stacking switchover or failover” on page 166.
176
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
PowerConnect B-Series FCX hitless stacking
5
For a description this feature’s impact to major system functions, refer to Table 37 on page 164.
For examples of hitless stacking switchover operation, refer to “Hitless stacking switchover
examples” on page 178.
Executing a hitless stacking switchover
The following must be in effect before a hitless switchover (switch over to the Standby Controller) is
allowed:
•
•
•
•
•
Hitless stacking is enabled
The stack has a Standby Controller
The Standby Controller has learned the protocols
The Standby Controller has the same priority as the Active Controller
More than 120 seconds have passed since the previous switchover or failover
You can use the show stack command to view whether or not these properties are in effect. For
more information, see “Displaying information about hitless stacking” on page 183.
To perform a switchover, enter the following command:
PowerConnect# stack switch-over
Standby unit 8 will become Active Controller, and unit 1 will become standby
Are you sure? (enter 'y' or 'n'): y
Unit 1 is no longer the Active Controller
Syntax: stack switch-over
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
177
5
PowerConnect B-Series FCX hitless stacking
Hitless stacking switchover examples
This section illustrates hitless stacking failover and switchover operation during a CLI-driven
switchover or priority change.
Figure 19 illustrates a hitless stacking switchover triggered by the stack switch-over command.
FIGURE 19
Manual switchover
Device stack manual switchover
Active 1
Standby 2
Member 3
1
Execute “stack switch-over”
No waiting period
The Active and Standby priorities must
match or the command is rejected
Standby 1
Active 2
Member 3
1
The Active and Standby controllers switch roles
immediately (no waiting period). No traffic loss
is expected.
Next switchover allowed in
120 seconds
178
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
PowerConnect B-Series FCX hitless stacking
5
Figure 20 illustrates a hitless stacking switchover when the Active Controller goes down then
comes back up. The stack in this example has user-configured priorities.
FIGURE 20
Hitless stacking switchover when the Active Controller comes back up
Active controller comes back (in a
stack with user-assigned priorities).
The Active controller fails
Active 1 (pri=200)
Standby 2 (pri=100)
Member 3 (pri=0)
Member 4 (pri=0)
1
Active (Unit 1 with priority 200)
comes back up
Active 2 (pri=100)
Standby 3 (pri=0)
Member 4 (pri=0)
Member 1 (pri=200)
Active 2 (pri=100)
Standby 3 (pri=0)
Member 4 (pri=0)
1
1
Unit 1 (priority 200) reloads because
it loses the election. After the reload,
It joins the stack as a member.
30 sec.
Standby 1 (pri=200)
Active 2 (pri=100)
Member 3 (pri=0)
Member 4 (pri=0)
1
The Active controller assigns Unit 1
(priority 200) as the Standby controller.
Stages 1 and 2 are complete.
70 sec.
Active 1 (pri=200)
Standby 2 (pri=100)
Member 3 (pri=0)
Member 4 (pri=0)
1
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
A switchover occurs. Unit 1
becomes the Active controller.
179
5
PowerConnect B-Series FCX hitless stacking
Figure 21 illustrates a hitless stacking switchover after the network administrator increases the
priority value of the Standby Controller.
FIGURE 21
Scenario 1 – Hitless stacking switchover after a priority change
Device stack
change - Scenario 1
FCXpriority
stack formation
Active 1 (pri=100)
Standby 2 (pri=0)
Member 3 (pri=0)
Member 4 (pri=0)
1
Priority 200 assigned to Unit 2 (Standby)
Active 1 (pri=100)
Standby 2 (pri=200)
Member 3 (pri=0)
Member 4 (pri=0)
1
Standby 2 becomes the Active controller
without a reload.
ver
ilo
Fa
120 sec.
Active 1 (pri=100)
Standby 2 (pri=200)
Member 3 (pri=0)
Member 4 (pri=0)
Switchover
Not allowed because priorities do
not match.
The priority change triggers re-election
of the Active controller
1
Standby 2 becomes the Active controller
without a reload.
er
ilov
Fa
60 sec.
Standby 1 (pri=100)
Active 2 (pri=200)
Member 3 (pri=0)
Member 4 (pri=0)
180
1
Switchover
Not allowed because priorities do
not match.
The Standby controller is re-assigned
and a switchover occurs.
Stages 1 and 2 are bypassed.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
5
PowerConnect B-Series FCX hitless stacking
Figure 22 illustrates a hitless stacking switchover after the network administrator increases the
priority value of one of the stack members.
FIGURE 22
Scenario 2 – Hitless stacking switchover after a priority change
Device stack
priority
- Scenario 2
FCX
stackchange
formation
Active 1 (pri=100)
Standby 2 (pri=0)
Member 3 (pri=0)
Member 4 (pri=0)
Standby 1 (pri=100)
Member 2 (pri=0)
Active 3 (pri=200)
Member 4 (pri=0)
1
A switchover occurs.
Stages 1 and 2
are complete.
Priority 200 assigned
to Unit 3
Active 1 (pri=100)
Standby 2 (pri=0)
Member 3 (pri=200)
Member 4 (pri=0)
1
120 sec.
Active 1 (pri=100)
Standby 2 (pri=0)
Member 3 (pri=200)
Member 4 (pri=0)
1
The priority change triggers
re-election of the Active controller
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
1
60 sec.
Active 1 (pri=100)
Member 2 (pri=0)
Standby 3 (pri=200)
Member 4 (pri=0)
1
The Standby controller
is re-assigned
181
5
PowerConnect B-Series FCX hitless stacking
Figure 23 illustrates a hitless stacking switchover after the network administrator increases the
priority value for two of the stack members.
FIGURE 23
Scenario 3 – Hitless stacking switchover after a priority change
FCXpriority
stack formation
Device stack
change - Scenario 3
Active 1 (pri=100)
Standby 2 (pri=0)
Member 3 (pri=0)
Member 4 (pri=0)
1
Priority 150 assigned to Unit 3 (Member 3)
Priority 200 assigned to Unit 4 (Member 4)
Active 1 (pri=100)
Standby 2 (pri=0)
Member 3 (pri=150)
Member 4 (pri=200)
1
Standby 2 becomes the Active controller
without a reload
er
ilov
Fa
Switchover
120 sec.
Not allowed because priorities do not match
The priority change triggers re-election
of the Active controller
Active 1 (pri=100)
Standby 2 (pri=0)
Member 3 (pri=150)
Member 4 (pri=200)
1
Standby 2 becomes the Active controller
without a reload
ver
ilo
Fa
30 sec.
Switchover
Not allowed because priorities do not match
Standby re-assigned
Active 1 (pri=100)
Member 2 (pri=0)
Member 3 (pri=150)
Standby 4 (pri=200)
1
Standby 4 becomes the Active controller
without a reload
er
60 sec.
Stage 1&2. Switchover
ilov
Fa
Switchover
Not allowed because priorities do not match
Switchover occurs
Standby 1 (pri=100)
Member 2 (pri=0)
Member 3 (pri=150)
Active 4 (pri=200)
1
Standby 1 becomes the Active controller
without a reload
er
ilov
Fa
30 sec.
Switchover
Member 1 (pri=100)
Member 2 (pri=0)
Standby 3 (pri=150)
Active 4 (pri=200)
Not allowed because priorities do not match
Standby re-assigned
1
Standby 3 becomes the Active controller
without a reload
er
ilov
Fa
Switchover
182
Not allowed because priorities do not match
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
PowerConnect B-Series FCX hitless stacking
5
Displaying information about hitless stacking
Use the show stack command to view information pertinent to a hitless stacking switchover or
failover. The command output illustrates the Active and Standby Controllers, as well as the
readiness of the Standby Controller to take over the role of Active Controller, if needed.
PowerConnect#show stack
alone: standalone, D: dynamic config, S: static config
ID
Type
Role
Mac Address
Pri State
Comment
1 S FCX624S
active 00e0.5200.2900 128 local
Ready
2 S FCX624S
standby 00e0.5200.0100 128 remote Ready
3
S FCX624S
member 0000.0000.0000 128 reserve
active
standby
+---+
+---+
+---+
-1/3| 1 |1/5--1/5| 2 |1/3--1/5| 3 |1/3|
+---+
+---+
+---+
|
|
|
|-------------------------------------|
Standby unit 2: protocols ready, can failover or manually switch over
Current stack management MAC is 0000.5200.1100
NOTE
The text in bold highlights the information added for hitless stacking failover and switchover. For a
description of the fields in this output, see “Field descriptions for the show stack command” on
page 137.
Syslog messages for hitless stacking failover and switchover
Syslog messages are generated for the following events:
• Switchover
• Failover
• Standby Controller assignment
Table 38 lists the supported Syslog messages.
TABLE 38
Syslog messages
Message level
Message
Explanation
Informational
Stack: Stack unit has been
assigned as STANDBY unit of the stack
system
Indicates that the unit has been assigned
as the Standby Controller.
Informational
Stack: Stack is operational due to
SWITCH-OVER
Indicates that a switchover has occurred.
Informational
Stack: Stack is operational due to FAIL-OVER
Indicates that a failover has occurred.
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
183
5
PowerConnect B-Series FCX hitless stacking
To view the System log or the traps logged on an SNMP trap receiver, enter the show log command
at any level of the CLI. The following example output shows what the log might look like after a
switchover or assignment of the Standby Controller.
PowerConnect# show log
Syslog logging: enabled (0 messages dropped, 1 flushes, 0 overruns)
Buffer logging: level ACDMEINW, 8 messages logged
level code: A=alert C=critical D=debugging M=emergency E=error
I=informational N=notification W=warningDynamic Log Buffer (50 lines):
0d00h05m34s:I:System: Interface ethernet mgmt1, state up
0d00h05m33s:I:Stack: Stack unit 8 has been assigned as STANDBY unit of the stack system
0d00h05m33s:I:Stack: Stack is operational due to SWITCH-OVER
0d00h05m32s:I:Stack: Stack unit 1 has been elected as ACTIVE unit of the stack system
0d00h05m29s:W:System:Stack unit 2 Fan speed changed automatically to 2
0d00h05m25s:W:System:Stack unit 5 Fan speed changed automatically to 2
0d00h05m00s:I:System: Interface ethernet mgmt1, state down
0d00h05m00s:I:Security: Telnet server enabled by from session
The following example output shows what the log might look like after a failover of the Active
Controller.
PowerConnect# show log
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
Buffer logging: level ACDMEINW, 12 messages logged
level code: A=alert C=critical D=debugging M=emergency E=error
I=informational N=notification W=warning
Dynamic Log Buffer (50 lines):
0d00h04m41s:I:Stack: Stack unit 3 has been assigned as STANDBY unit of the stack system
0d00h04m12s:I:System: Interface ethernet mgmt1, state up
0d00h04m10s:I:System: Interface ethernet mgmt1, state down
0d00h04m10s:I:System: Interface ethernet mgmt1, state up
0d00h04m09s:I:STP: VLAN 1 Bridge is RootBridge: 800000e052010000 (MgmtPriChg)
0d00h04m09s:I:System: Management MAC address changed to 00e0.5201.0000
0d00h04m09s:I:Stack: Stack is operational due to FAIL-OVER
0d00h04m08s:I:Stack: Stack unit 1 has been elected as ACTIVE unit of the stack system
0d00h04m08s:I:STP: VLAN 1 Port 8/1/1 STP State -> DISABLED (PortDown)
0d00h04m08s:I:STP: VLAN 1 Port 8/1/1 STP State -> FORWARDING (PortDown)
0d00h04m08s:I:System: Interface ethernet 1/2/2, state down
0d00h04m06s:I:System: Interface ethernet 8/2/2, state down
Displaying hitless stacking diagnostic information
Use the debug stacking sync_rel_msg command to display diagnostic information for hitless
stacking switchover or failover. Example display outputs are shown below.
PowerConnect# debug stacking sync_rel_msg 1
stk_sync_rel_msg_create_ipc_session:session created for stack_id=1
stk_sync_rel_msg_send():sent msg_type = 16, len 1203
stk_sync_rel_msg_free:msg freed
start runing config sync
stk_sync_rel_msg_send():sent msg_type = 3, len 1024
stk_sync_rel_msg_free:msg freed
184
PowerConnect B-Series FCX Configuration Guide
53-1002266-01
PowerConnect B-Series FCX hitless stacking
5
PowerConnect# debug stacking sync_rel_msg 4
stk_sync_trunk_mapping:sending trunk mapping...
start running config sync
sync_cdb:send cdb:sess = 0, pBuf = 2132f068
sync_cdb:send cdb:sess = 0, pBuf = 2132f57c
...
stk_sync_cdb:finished cdb sync
PowerConnect# debug stacking sync_rel_msg 8
Hitless sync: TRUNK INFO size (1282)
*************************************
Trunk ID: 10 (1 based), (Hw Trunk ID: 1),
g_sw_sys.trunk_config.trunk_entry[#9]
:number_of_ports = 2; creator = 0
g_sw_sys.trunk_config.trunk_entry[#9] MEMBER PORTS
port_list[0]=#009
port_list[1]=#010
Syntax: debug stacking sync_rel_msg