Foundry Networks EdgeIron switch User Guide

Foundry EdgeIron
User Guide
2100 Gold Street
4980 Great America Parkway
Santa Clara, CA 95054
Tel 408.207.1700
www.foundrynetworks.com
December 2007
Copyright © 2007 Foundry Networks, Inc. All rights reserved.
No part of this work may be reproduced in any form or by any means – graphic, electronic or mechanical, including
photocopying, recording, taping or storage in an information retrieval system – without prior written permission of the
copyright owner.
The trademarks, logos and service marks ("Marks") displayed herein are the property of Foundry or other third parties.
You are not permitted to use these Marks without the prior written consent of Foundry or such appropriate third party.
Foundry Networks, EdgeIron, FastIron, IronView, JetCore, NetIron, ServerIron, TurboIron, IronWare, EdgeIron,
IronPoint, the Iron family of marks and the Foundry Logo are trademarks or registered trademarks of Foundry
Networks, Inc. in the United States and other countries.
All other trademarks mentioned in this document are the property of their respective owners.
Contents
Chapter 1.
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Warranty Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Chapter 1. Updates to Manuals and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Chapter 1. How to Get Help or Report Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2
E-mail Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2
Telephone Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2
Technical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2
List of Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
Chapter 2.
Switch Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1
Connecting to the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1
Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1
Required Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
Remote Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3
Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3
Console Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3
Setting Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Setting an IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Enabling SNMP Management Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
Saving Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8
Managing System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8
December 2007
© 2007 Foundry Networks, Inc.
iii
Foundry EdgeIron User Guide
System Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9
Chapter 3.
Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1
Accessing the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1
Console Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2
Telnet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2
Entering Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
Keywords and Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
Minimum Abbreviation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
Command Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
Getting Help on Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4
Partial Keyword Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5
Negating the Effect of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5
Using Command History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5
Understanding Command Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5
Exec Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6
Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6
Command Line Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7
General Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8
configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9
show history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9
reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10
prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11
end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11
exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11
quit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12
Chapter 4.
Using the Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1
Navigating the Web Browser Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2
Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2
Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2
Panel Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3
Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3
Chapter 5.
Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1
System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2
ip telnet server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3
mac-address-table static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4
iv
© 2007 Foundry Networks, Inc.
December 2007
Contents
show mac-address-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4
pvlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5
show pvlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-6
show interfaces counters brief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-6
jumbo frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-7
show process cpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-7
show tech-support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8
banner motd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-9
hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-10
snmp-server location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-10
snmp-server contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-10
show system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-11
Displaying Switch Hardware/Software Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12
show version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-13
show startup-config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-13
show running-config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-15
show users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-17
Displaying Bridge Extension Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-18
show bridge-ext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-19
Setting the IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-19
ip address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-21
ip default-gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-22
Controlling the Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-22
light unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-22
switch renumber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23
Using DHCP/BOOTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23
ip address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-24
ip dhcp restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-25
Resetting the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-26
reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-26
Web Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-26
ip http port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-27
ip http server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-28
ip http secure-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-28
ip http secure-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-29
Virtual Switch Redundancy Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-30
show vsrp aware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-31
vsrp aware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-31
Chapter 6.
Configuring IP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1
December 2007
© 2007 Foundry Networks, Inc.
v
Foundry EdgeIron User Guide
show arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1
clear arp-cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
ip address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
ip dhcp restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3
ip default-gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4
show ip interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4
show ip redirects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5
ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5
Chapter 7.
Logging Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1
Enabling System Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2
logging on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3
logging history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3
Remote Logs Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5
logging host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6
logging facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6
logging trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-7
clear logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-7
Displaying System Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-8
show log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-8
show logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-9
Sending Simple Mail Transfer Protocol Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-10
logging sendmail host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-12
logging sendmail level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-12
logging sendmail source-email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-13
logging sendmail destination-email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-13
logging sendmail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-14
show logging sendmail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-14
Chapter 8.
System Clock Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1
Configuring SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2
sntp client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2
sntp server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-3
sntp poll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-4
show sntp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-4
Setting the Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-4
clock timezone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5
calendar set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-6
show calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-6
Chapter 9.
vi
© 2007 Foundry Networks, Inc.
December 2007
Contents
Management Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-1
Configuring the Logon Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2
username . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3
enable password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4
Configuring RADIUS/TACACS Logon Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-5
authentication login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-7
authentication enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-8
radius-server host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9
radius-server port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9
radius-server key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9
radius-server retransmit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-10
radius-server timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-10
show radius-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-11
tacacs-server host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-11
tacacs-server port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-12
tacacs-server key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-12
show tacacs-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-12
Configuring TACACS+ Accounting and Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-13
aaa group server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-13
server (TACACS+ Server Group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-14
aaa accounting exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-15
aaa accounting update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-15
accounting exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-16
show accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-16
aaa authorization exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-17
authorization exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-18
show authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-18
Chapter 10.
Configuring SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1
Setting Community Access Strings
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-3
snmp-server community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-4
Specifying Trap Managers and Trap Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-4
snmp-server contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7
snmp-server location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7
snmp-server host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-8
snmp-server enable traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-10
Enabling the SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-10
snmp-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-11
show snmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-11
Configuring SNMPv3 Management Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-12
December 2007
© 2007 Foundry Networks, Inc.
vii
Foundry EdgeIron User Guide
Setting a Local Engine ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-12
Specifying a Remote Engine ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-14
Configuring SNMPv3 Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-15
Setting a Local User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-15
Specifying Remote SNMPv3 Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-19
Configuring SNMPv3 Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-20
snmp-server group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-22
show snmp group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-23
Setting SNMPv3 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-24
snmp-server view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-25
show snmp view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-26
Chapter 11.
Line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-1
line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2
login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2
password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-3
timeout login response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4
exec-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4
password-thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-5
silent-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-6
databits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-6
parity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-7
speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-7
stopbits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-8
disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-8
show line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-9
Chapter 12.
Flash/File Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-1
Downloading System Software from a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-1
Saving or Restoring Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-3
Copying the Running Configuration to a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-3
copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-4
Setting the Startup File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-6
boot system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-6
whichboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-7
Deleting Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-7
delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-7
dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-8
Chapter 13.
Secure Shell Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-1
viii
© 2007 Foundry Networks, Inc.
December 2007
Contents
Generating the Host Key Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-3
delete public-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-4
ip ssh crypto host-key generate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-5
ip ssh crypto zeroize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-5
ip ssh save host-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-6
show ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-6
show public-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-8
Configuring the SSH Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-9
ip ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-10
ip ssh server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-10
ip ssh timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-11
ip ssh authentication-retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-12
ip ssh server-key size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-12
disconnect ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-13
show ip ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-13
Chapter 14.
802.1x Port Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-1
show dot1x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-3
Configuring 802.1x Global Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-6
dot1x default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-6
dot1x max-req . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-7
dot1x re-authenticate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-7
dot1x re-authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-7
dot1x timeout quiet-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-8
dot1x timeout re-authperiod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-8
dot1x timeout tx-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-9
Configuring Port Authorization Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-9
dot1x port-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-10
Displaying 802.1x Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-11
Chapter 15.
Multi-Device Port Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-1
mac-authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-3
mac-authentication auth-passwd-format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-3
mac-authentication auth-fail-vlan-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-4
mac-authentication mac-filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-4
mac-authentication no-override-restrict-vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-5
mac-authentication save-dynamicvlan-to-config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-5
mac-authentication disable-aging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-6
mac-authentication max-age . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-6
mac-authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-7
December 2007
© 2007 Foundry Networks, Inc.
ix
Foundry EdgeIron User Guide
mac-authentication auth-fail-action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-7
mac-authentication apply-mac-auth-filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-8
mac-authentication enable-dynamic-vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-8
mac-authentication move-back-to-old-vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-9
mac-authentication clear-mac-session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-9
mac-authentication clear-auth-mac-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-10
mac-authentication disable-aging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-10
clear auth-mac-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-11
show auth-mac-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-11
show auth-mac-address configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-11
show auth-mac-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-12
show auth-mac-address detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-13
show auth-mac-address authorized-mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-13
show auth-mac-address unauthorized-mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-14
Chapter 16.
IP Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-1
management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-2
show management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-4
Chapter 17.
Interface Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-1
Displaying Interfaces Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-3
Displaying Connection Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-3
mdix auto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-3
port-channel load-balance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-4
show interfaces ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-5
show interfaces brief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-6
show interfaces status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-7
show interfaces counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-7
show interfaces switchport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-10
Configuring Interface Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-11
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-13
channel-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-13
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-14
speed-duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-14
negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-15
capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-16
flowcontrol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-17
combo-forced-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-18
giga-phy-mode (EdgeIron 24G-A, 48G only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-18
shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-19
x
© 2007 Foundry Networks, Inc.
December 2007
Contents
clear counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-19
Configuring Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-20
port security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-20
port security aging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-21
port security autosave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-22
port security (EdgeIron 2402CF and EdgeIron 4802CF) . . . . . . . . . . . . . . . . . . . . . . . . .17-22
show port security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-23
Setting Broadcast Storm Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-24
switchport broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-25
Configuring Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-26
port monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-27
show port monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-28
Configuring Rate Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-29
rate-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-30
Showing Device Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-31
show interfaces counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-34
Statically Configuring a Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-35
Chapter 18.
LACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-1
Dynamically Configuring a Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-1
Enabling LACP on Selected Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-2
lacp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-3
Configuring LACP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-5
Dynamically Creating a Port Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-5
Displaying LACP Port Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-9
show lacp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-9
Displaying LACP Settings and Status for the Local Side . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-13
Internal Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-13
Displaying LACP Settings and Status for the Remote Side . . . . . . . . . . . . . . . . . . . . . . . . . .18-15
Neighbor Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-15
Chapter 19.
Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-1
Setting the ACL Name and Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-4
access-list ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-4
Configuring a Standard IP ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-5
permit, deny (Standard ACL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-6
Configuring an Extended IP ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-7
permit, deny (Extended ACL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-8
show ip access-list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-10
access-list ip mask-precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-10
December 2007
© 2007 Foundry Networks, Inc.
xi
Foundry EdgeIron User Guide
map access-list ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-11
show map access-list ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-12
match access-list ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-12
show marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-13
Configuring a MAC ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-14
access-list mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-16
permit, deny (MAC ACL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-17
show mac access-list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-18
access-list mac mask-precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-19
show access-list mac mask-precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-19
permit offset, deny offset (MAC ACL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-20
map access-list mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-21
show map access-list mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-22
match access-list mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-22
Configuring ACL Masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-23
Specifying the Mask Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-23
Configuring an IP ACL Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-24
Configuring a MAC ACL Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-28
Binding a Port to an Access Control List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-31
ip access-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-32
mac access-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-33
ACL Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-33
show ip access-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-33
show ip access-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-34
show mac access-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-34
Chapter 20.
Address Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-1
Setting Static Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-1
mac-address-table static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-2
show mac-address-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-3
Displaying the Address Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-4
show mac-address-table port-secure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-5
clear mac-address-table dynamic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-6
Changing the Aging Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-6
mac-address-table aging-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-7
show mac-address-table aging-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-7
Chapter 21.
Spanning Tree Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-1
BPDU Prioritization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-2
Enabling a Single Instance of STP per VLAN on an EdgeIron . . . . . . . . . . . . . . . . . . . . . . . . .21-2
xii
© 2007 Foundry Networks, Inc.
December 2007
Contents
STP Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-4
show spanning-tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-5
STP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-7
spanning-tree (Global Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-10
spanning-tree (VLAN Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-11
spanning-tree forward-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-11
spanning-tree hello-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-12
spanning-tree max-age . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-12
spanning-tree priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-13
spanning-tree pathcost method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-13
spanning-tree transmission-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-14
spanning-tree spanning-disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-14
spanning-tree single . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-15
STP Port and Trunk Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-15
STP Port and Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-17
Chapter 22.
802.1Q VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-1
Assigning Ports to VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-2
Forwarding Tagged/Untagged Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-4
Enabling or Disabling GVRP (Global Setting)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-4
bridge-ext gvrp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-4
switchport gvrp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-5
Displaying Basic VLAN Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-5
show bridge-ext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-6
Displaying Current VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-6
show vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-8
Creating VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-9
vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-10
Creating a New Default VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-11
Adding Interfaces Based on Membership Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-11
untagged ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-13
tagged ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-14
dual-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-14
Adding Interfaces Based on Static Membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-15
interface vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-16
switchport mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-16
Configuring VLAN Behavior for Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-17
switchport mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-19
switchport acceptable-frame-types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-19
switchport ingress-filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-20
December 2007
© 2007 Foundry Networks, Inc.
xiii
Foundry EdgeIron User Guide
switchport forbidden vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-21
show vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-21
show interfaces status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-22
show interfaces switchport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-23
Chapter 23.
Private VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-1
Enabling Private VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-2
private-vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-2
private vlan association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-3
Configuring Uplink and Downlink Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-4
switchport mode private-vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-4
switchport private-vlan host-association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-5
switchport private-vlan mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-5
Displaying Private VLAN Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-6
show vlan private-vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-6
Chapter 24.
Protocol VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24-1
Configuring Protocol-Based VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24-1
Configuring Protocol Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24-2
Mapping Protocols to VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24-4
Chapter 25.
Class of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-1
Setting the Default Priority for Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-2
switchport priority default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-3
Mapping CoS Values to Egress Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-4
Setting the Service Weight for Traffic Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-6
queue bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-6
queue cos-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-7
show queue bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-8
show queue cos-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-9
Mapping Layer 3/4 Priorities to CoS Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-9
Selecting IP Precedence/DSCP Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-10
Mapping IP Precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-11
map ip precedence (Global Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-12
map ip precedence (Interface Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-12
Mapping DSCP Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-14
map ip dscp (Global Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-15
map ip dscp (Interface Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-15
Mapping IP Port Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-17
map ip port (Global Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-18
xiv
© 2007 Foundry Networks, Inc.
December 2007
Contents
map ip port (Interface Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-18
show map ip precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-19
show map ip dscp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-20
show map ip port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-20
Mapping CoS Values to ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-21
map access-list ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-23
show map access-list ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-24
Changing Priorities Based on ACL Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-24
match access-list ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-25
show marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-26
Chapter 26.
Multicast Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-1
Configuring IGMP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-2
ip igmp snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-4
ip igmp snooping vlan static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-4
ip igmp snooping version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-5
show ip igmp snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-5
show mac-address-table multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-6
IGMP Querier Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-6
ip igmp snooping querier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-6
ip igmp snooping query-count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-7
ip igmp snooping query-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-7
ip igmp snooping query-max-response-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-8
ip igmp snooping router-port-expire-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-8
Interfaces Attached to a Multicast Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-9
Specifying Interfaces Attached to a Multicast Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-10
switchport multicast packet-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-10
ip igmp snooping vlan mrouter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-11
show ip igmp snooping mrouter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-11
Displaying Port Members of Multicast Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-12
show mac-address-table multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-12
Adding Multicast Addresses to VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-13
Chapter 27.
Stacking Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-1
Operational Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-1
Functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-2
Create and Initiate a Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-4
Special Stacking Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-7
Normal Operation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-8
Single IP Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-12
December 2007
© 2007 Foundry Networks, Inc.
xv
Foundry EdgeIron User Guide
Loop Stacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-12
System Adaptation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-13
Appendix A.
Using Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Displaying Syslog Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Configuring the Syslog Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Displaying the Syslog Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Flash and RAM Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Time Stamps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Example of Syslog Messages on a Device Whose Onboard Clock Is Set . . . . . . . . . . . . . A-5
Displaying and Configuring Syslog Buffer Parameters Using the Web
Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Disabling or Re-Enabling Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Specifying a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Using The Web Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Specifying an Additional Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Changing the Log Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Clearing the Syslog Messages from the Local Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Syslog Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Appendix B.
Trap Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Trap Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Appendix C.
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Troubleshooting Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Appendix D.
Upgrading Firmware via the Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Appendix E.
Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Console Port Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
DB-9 Port Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Console Port to 9-Pin DTE Port on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2
Console Port to 25-Pin DTE Port on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glossary-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
xvi
© 2007 Foundry Networks, Inc.
December 2007
Chapter 1
About This Guide
Audience
This guide is for system administrators with a working knowledge of network management.
You should be familiar with switching and networking concepts.
Nomenclature
This guide uses the following typographical conventions to show information:
Monospace font – Enter text exactly as it appears in this guide.
Note: emphasizes an important fact or calls your attention to a dependency.
Warranty Coverage
Contact Foundry Networks using any of the methods listed above for information about the standard
and extended warranties.
Related Publications
Refer to the Foundry EdgeIron Installation and Basic Configuration Guide for instructions on
installing an EdgeIron switch and for connecting an external redundant power supply to an EdgeIron
switch.
Updates to Manuals and Release Notes
Manuals and release notes for this product may be updated between releases. For the latest edition of manuals
and release notes, check the Foundry Knowledge Portal at kp.foundrynet.com.
How to Get Help or Report Errors
Foundry Networks is committed to ensuring that your investment in our products remains cost-effective. If you
need assistance or find errors in the manuals, contact Foundry Networks using one of the following options.
December 2007
© 2007 Foundry Networks, Inc.
1-1
Foundry EdgeIron User Guide
Web Access
Go to kp.foundrynet.com and log in to the Knowledge Portal (KP) to obtain more information about a product, or to
report documentation errors. To report errors, click on Cases > Create a New Ticket.
E-mail Access
Send an e-mail to: [email protected]
Telephone Access
1.877.TURBOCALL (887.2622) United States
1.408.207.1600 Outside the United States
Technical Specifications
The following table summarizes the technical specifications for the switches:
Properties
EdgeIron
2402CF/4802CF
EdgeIron
24G-A/48G
EdgeIron
24GS/48GS
EdgeIron
8X10G
10/100
Base-T Ports
2402CF: 24
0
0
0
10/100/1000
Base-T ports
2
24G-A: 24
24GS: 24
0
48G: 48
48GS: 48
Mini-GBIC slots
2
4
4
0
10G Xenpak slots
0
0
1
0
10G XFP slots
0
0
0
8
Switching
Performance
(Gbps)
2402CF: 8.8
24G-A: 48
24GS: 48
160
4802CF: 13.6
48G: 80
48GS: 96
Forwarding Rate
for a 64-byte
packet (Mbps)
2402CF: 6.6
24G-A: 35.7
24GS: 50.6
4802C: 10.2
48G: 71.4
48GS: 86.3
24G-A, 48G: 16K
16K
2402CF:
1.7x17.37x9 in.
(4.3x44x22.8 cm)
24G-A:
1.7x17.37x13.9 in.
(4.3x44x35.3 cm)
17.37 x 16.3 x 1.7 in. 1.69x17.32x16.14 in.
44.0 x 41.5 x 4.3 cm (4.3x44x41 cm)
4802CF:
1.7x17.37x12.76 in.
(4.3x44x32.4 cm)
48G:
1.17x17.37x13.9 in.
(4.3x44x35.3 cm)
2402CF: 7 lbs (3.18 kg)
24G-A: 9.5 lbs
(4.36 kg)
24GS: 13.4 lbs
(6.08 kg)
4802CF: 9.5 lbs (4.36 kg)
48G: 12.9lbs
(5.86 kg)
48GS: 14 lbs
(6.36 kg)
2402, 4802:
45W maximum
24G-A, 48G:
100W maximum
24GS:
66 Watts maximum
4802CF: 48
Maximum Number 8K
of MAC Addresses
Physical
Dimensions
(HxWxD)
Weight
Power
Consumption
(Watt)
-2
119
16K
12.9 lbs (5.76 kg)
133 Watts maximum
48GS:
100 Watts maximum
© 2007 Foundry Networks, Inc.
March 2007
How to Get Help or Report Errors
List of Features
The following table summarizes the features available in the switches. Refer to the appropriate
sections in this manual for any feature limitations.
Features
EdgeIron
2402CF/4802CF
EdgeIron
24G-A/48G
EdgeIron
24GS/48GS
EdgeIron 8X10G
Minimum software
release version
Version 2.2.4.29
Version 2.2.4.29
24GS: 2.2.4.21
48GS: 2.2.4.22
Version 2.2.4.21
Size
1U
1U
1U
1U
Uplink
SFP/
1000BASE-T
Combo
SFP/
1000BASE-T
Combo
Xenpak
XFP
Wattage
2402CF:
45 watts per
system
24G-A:
70 watts per
system
24GS:
66 watts per
system
8X10G:
133 watts per
system
4802CF:
48 watts per
system
48G:
105 watts per
system
48GS:
100 watts per
system
Yes
Yes
Yes
Yes
Feature can be
disabled only on
Fast Ethernet
ports
Feature cannot be
disabled
Feature cannot be
disabled
Feature cannot be
disabled
802.1X EAP pass through
PEAP/TLS/TTLS
Yes
Yes
No
No
Message of the Day
Banner
Yes
Yes
Yes
Yes
Port-channel load
balance
Yes on devices
running 2.2.6.x
and later
Yes on devices
running 2.2.6.x
and later
No
No
CPU Type and Speed
2402CF:
MPC8241/166M
Hz (8MB Flash,
32MB SDRAM)
24G-A 48G:
MPC8245/266MH
z (8MB Flash,
32MB SDRAM)
24GS/48GS:
Main Board:
MPC8245/333MH
z (16MB Flash,
64MB SDRAM),
Optional Module:
MPC8241/166MH
z (4MB Flash,
16MB SDRAM)
8X10G: MPC8245
466MHz (32MB
Flash, 128MB
SDRAM)
System
Auto-MDIX
4802CF:
MPC8241/266M
Hz (8MB Flash,
32MB SDRAM)
Redundant Power
External
External
External
External
Jumbo Frames
Yes (up to 2048
bytes)
Yes (up to 9216
bytes)
Yes (up to 9216
bytes)
Yes (up to 9216
bytes)
Flash Memory
8 Mbytes
8 Mbytes
16 Mbytes
32 Mbytes
DRAM
32 Mbytes
32 Mbytes
64 Mbytes
128 Mbytes
December 2007
© 2007 Foundry Networks, Inc.
-3
Foundry EdgeIron User Guide
Features
EdgeIron
2402CF/4802CF
EdgeIron
24G-A/48G
EdgeIron
24GS/48GS
EdgeIron 8X10G
Buffer Architecture
2402CF 32 Mbytes per
system
24G-A 2 Mbyte per
system
24GS 2 Mybtes per
system
8X10G 4 Mybtes per
system
4802CF 64 Mybtes per
system
48G 4 Mybtes per
system
48GS 4 Mybtes per
system
RADIUS and TACACS+
authentication
Yes
Yes
Yes
Yes
Multi-device Port
Authentication
Yes on devices
running 2.2.7.x
and later
Yes on devices
running 2.2.7.x
and later
No
No
TACACS+ AAA
Accounting
Yes, on devices
running 2.2.6.x
and later
Yes, on devices
running 2.2.6.x
and later
Yes, on devices
running 2.2.6.x
and later
Yes, on devices
running 2.2.6.x
and later
BootP
Yes
Yes
Yes
Yes
DHCP Clients
Yes
Yes
Yes
Yes
IP Address Management
Yes
Yes
Yes
Yes
Configuration
Management
Yes
Yes
Yes
Yes
TFTP
Yes
Yes
Yes
Yes
Remote Logging
Yes
Yes
Yes
Yes
HTTPS
Yes
Yes
Yes
Yes
SSH
(version 2.0)
Yes
Yes
Yes
Yes
SSH
(version 1.5)
Yes
Yes
Yes
Yes
SNMP v3
Yes, on devices
running 2.2.6.x
and later
Yes, on devices
running 2.2.6.x
and later
Yes, on devices
running 2.2.6.x
and later
Yes, on devices
running 2.2.6.x
and later
SNTP
Yes
Yes
Yes
Yes
MIB II
Yes
Yes
Yes
Yes
Bridging MIB
Yes
Yes
Yes
Yes
Interface MIB
Yes
Yes
Yes
Yes
RMON MIB
Yes
Yes
Yes
Yes
RADIUS MIB
Yes
Yes
Yes
Yes
Ethernet-like MIB
Yes
Yes
Yes
Yes
Entity MIB
Yes
Yes
Yes
Yes
Extended MIB
Yes
Yes
Yes
Yes
SNMP MIB
Yes
Yes
Yes
Yes
MIB Support
-4
© 2007 Foundry Networks, Inc.
March 2007
How to Get Help or Report Errors
Features
EdgeIron
2402CF/4802CF
EdgeIron
24G-A/48G
EdgeIron
24GS/48GS
EdgeIron 8X10G
Per VLAN Spanning Tree
No
No
Yes
Yes
IEEE 802.1q Port-based
VLANs
Yes
Yes
Yes
Yes
VLANs per switch
255
255
255
255
Private VLANs
No1
Yes
Yes
Yes
IEEE 802.1v Protocol
VLANs
No
No
Yes
Yes
IEEE 802.1D (STP)
Yes
Yes
Yes
Yes
Fast Link Option
Yes
Yes
Yes
Yes
IEEE 802.1w (RSTP)
Yes
Yes
Yes
Yes
Foundry Per VLAN STP
compatible
Yes (up to 32
instances or 60
BPDUs/sec.)
Yes (up to 32
instances or 60
BPDUs/sec.)
Yes (up to 32
instances or 60
BPDUs/sec.)
Yes (up to 32
instances or 60
BPDUs/sec.)
Dual-mode2
Yes
Yes
Yes
Yes
GVRP
Yes
Yes
Yes
Yes
Priority (IEEE 802.1p &
IEEE 802.1q)
Yes
Yes
Yes
Yes
Priority queues per port
4
8
8
8
IP Precedence, IP DSCP,
IP Port
Yes
Yes
Yes
Yes
Strict scheduling for
priority queue
Yes
Yes
Yes
Yes
Cisco EtherChannel
Yes
Yes
Yes
Yes
Port Mirroring
Yes
Yes
Yes
Yes
Trunks
Up to 6 trunks
Up to 6 trunks
Up to 32 trunks
Up to 4 trunks
10/100 Trunks
Up to 6 trunks
None
None
None
Gigabit Trunks
Up to 2 trunks
Up to 6 trunks
Up to 8 trunks
None
10G trunks
None
None
Up to 4 trunks
Up to 4 trunks
Maximum ports per trunk
4
8
8
4
Maximum 10/100 ports
per trunk
4
None
None
None
Maximum gigabit ports
per trunk
2
8
8
None
Maximum 10G ports per
trunk
None
None
4
4
IEEE 802.3ad
Yes - dynamic
Yes - dynamic
Yes - dynamic
Yes - dynamic
Port Security
Yes
Yes
No
No
IEEE 802.1X
Yes
Yes
Yes
Yes
Layer 2
December 2007
© 2007 Foundry Networks, Inc.
-5
Foundry EdgeIron User Guide
Features
EdgeIron
2402CF/4802CF
EdgeIron
24G-A/48G
EdgeIron
24GS/48GS
EdgeIron 8X10G
Rate Limiting - ingress
and egress
Yes
Yes
Yes
Yes
10/100 Rate Limiting
range
1-100 Mbps
None
None
None
10/100 Rate Limiting
resolution
1 Mbps
None
None
None
Gigabit Rate Limiting
range
8-1000 Mbps
1-1000 Mbps
1-1000 Mbps
None
Gigabit Rate Limiting
resolution
8 Mbps
1 Mbps
1 Mbps
None
10G Rate Limiting range
None
None
1-10000 Mbps
1-10000 Mbps
10G Rate Limiting
resolution
None
None
1 Mbps
1 Mbps
Management Interface
Access Filtering
Yes
Yes
Yes
Yes
IEEE 802.3x
Yes
Yes
Yes
Yes
Multicast storm control
Yes, for devices
running 2.2.6.x
and later
Yes, for devices
running 2.2.6.x
and later
Yes, for devices
running 2.2.6.x
and later
Yes, for devices
running 2.2.6.x
and later
Yes
Yes
Yes
Yes
IGMP Snooping
Yes up to 64
IGMP Multicast
groups
Yes up to 64
IGMP Multicast
groups
Yes up to 64
IGMP Multicast
groups
Yes up to 64
IGMP Multicast
groups
Broadcast storm control
Yes
Yes
Yes
Yes
VSRP
Yes
Yes
No
No
L2: 802.1p - Tag-based
Yes
Yes
Yes
Yes
L2: 802.1p - Port-based
Yes
Yes
Yes
Yes
L2: 802.1p - Queuing
4 queues per port 8 queues per port
8 queues per port
8 queues per port
L3 Aware: DiffServ/ IP
TOS
Yes
Yes
Yes
Yes
L4 Aware: TCP portbased
Yes
Yes
No
No
No
Yes
Yes
Yes
Management IP
Filter only
Management
Pass through
128 rules per port 128 rules per port
Layer 3
ToS/DSCP Honoring
Multicast
Priority/QoS
ACLs
Access Control Lists
20 rules per port
1. Contact your Foundry representative if you have questions.
-6
© 2007 Foundry Networks, Inc.
March 2007
How to Get Help or Report Errors
2. Dual Mode refers to a port that can support both tagged and untagged VLANs.
December 2007
© 2007 Foundry Networks, Inc.
-7
Foundry EdgeIron User Guide
-8
© 2007 Foundry Networks, Inc.
March 2007
Chapter 2
Switch Management
Connecting to the Switch
Configuration Options
The Foundry EdgeIron switches include a built-in network management agent. The agent offers a
variety of management options, including SNMP, RMON and a Web-based interface. A PC may also
be connected directly to the switch for configuration and monitoring via a command line interface
(CLI).
Note: The IP address for this switch is assigned via DHCP by default. To change this address, see
“Setting an IP Address” on page 2-4.
The switch’s HTTP Web agent allows you to configure switch parameters, monitor port connections,
and display statistics graphically using a standard Web browser such as Netscape Navigator version
6.2 and higher or Microsoft IE version 5.0 and higher. The switch’s Web management interface can
be accessed from any computer attached to the network.
The switch’s management agent is based on SNMP (Simple Network Management Protocol). This
SNMP agent permits the switch to be managed from any system in the network using management
software.
The CLI program can be accessed by a direct connection to the RS-232 serial console port on the
switch, or remotely by a Telnet connection over the network.
The switch’s CLI configuration program, Web interface, and SNMP agent allow you to perform the
following management functions:
•
Set user names and passwords for up to 16 users
•
Set an IP interface for a management VLAN
•
Configure SNMP parameters
•
Enable/disable any port
•
Set the speed/duplex mode for any port
•
Configure up to 255 IEEE 802.1Q VLANs
(Foundry PVST can service up to 32 VLANs; PVST for all other VLANs will be disabled.)
December 2007
© 2007 Foundry Networks, Inc.
2-1
Foundry EdgeIron User Guide
•
Enable GVRP automatic VLAN registration
•
Configure IGMP multicast filtering
•
Upload and download of system firmware via TFTP
•
Upload and download of switch configuration files via TFTP
•
Configure spanning tree parameters
•
Configure Class of Service (CoS) priority queuing
•
Configure up to six static or LACP trunks
•
Enable port mirroring
•
Set broadcast storm control on any port
•
Display system information and statistics
Required Connections
The switch provides an RS-232 serial port that enables a connection to a PC or terminal for
monitoring and configuring the switch. A null-modem console cable is provided with the switch.
Attach a VT100-compatible terminal, or a PC running a terminal emulation program to the switch.
You can use the console cable provided with this package, or use a null-modem cable.
To connect a terminal to the console port, complete the following steps:
1. Connect the console cable to the serial port on a terminal, or a PC running terminal emulation
software, and tighten the captive retaining screws on the DB-9 connector.
2. Connect the other end of the cable to the RS-232 serial port on the switch.
3. Make sure the terminal emulation software is set as follows:
•
Select the appropriate serial port (COM port 1 or COM port 2).
•
Set the data rate to 9600 baud.
•
Set the data format to 8 data bits, 1 stop bit, and no parity.
•
Set flow control to none.
•
Set the emulation mode to VT100.
•
When using HyperTerminal, select Terminal keys, not Windows keys.
Note: When using HyperTerminal with Microsoft® Windows® 2000, make sure that you have
Windows 2000 Service Pack 2 or later installed. Windows 2000 Service Pack 2 fixes the problem
of arrow keys not functioning in HyperTerminal’s VT100 emulation. See www.microsoft.com for
information on Windows 2000 service packs.
4. Once you have set up the terminal correctly, the console login screen will be displayed.
For a description of how to use the CLI, see “Using the CLI” on page 3-1. For a list of all the CLI
commands and detailed information on using the CLI, refer to “Using the CLI” on page 3-1.
2-2
© 2007 Foundry Networks, Inc.
March 2007
Switch Management
Remote Connections
Prior to accessing the switch’s onboard agent via a network connection, you must first configure it
with a valid IP address, subnet mask, and default gateway using a console connection, DHCP or
BOOTP protocol.
The IP address for this switch is assigned via DHCP by default. To manually configure this address
or enable dynamic address assignment via DHCP or BOOTP, see “Setting an IP Address” on page
2-4.
Note: This switch supports four concurrent Telnet sessions.
After configuring the switch’s IP parameters, you can access the onboard configuration program
from anywhere within the attached network. The onboard configuration program can be accessed
using Telnet from any computer attached to the network. The switch can also be managed by any
computer using a Web browser (Internet Explorer 5.0 or above, or Netscape Navigator 6.2 or above),
or from a network computer using network management software.
Note: The onboard program only provides access to basic configuration functions. To access the
full range of SNMP management functions, you must use SNMP-based network management
software.
Initial Configuration
Console Connection
The CLI program provides two different command levels — normal access level (Normal Exec) and
privileged access level (Privileged Exec). The commands available at the Normal Exec level are a
limited subset of those available at the Privileged Exec level and allow you to only display information
and use basic utilities. To fully configure switch parameters, you must access the CLI at the
Privileged Exec level.
Access to both CLI levels are controlled by user names and passwords. The switch has a default
user name and password for each level. To log into the CLI at the Privileged Exec level using the
default user name and password, perform these steps:
1. To initiate your console connection, press <Enter>. The “User Access Verification” procedure
starts.
2. At the Username prompt, enter “admin.”
3. At the Password prompt, also enter “admin.” (The password characters are not displayed on the
console screen.)
4. The session is opened and the CLI displays the “Console#” prompt indicating you have access at
the Privileged Exec level.
December 2007
© 2007 Foundry Networks, Inc.
2-3
Foundry EdgeIron User Guide
Setting Passwords
Note: If this is your first time to log into the CLI program, you should define new passwords for both
default user names using the “username” command, record them and put them in a safe place.
Passwords can consist of up to thirty two alphanumeric characters and are case sensitive. To
prevent unauthorized access to the switch, set the passwords as follows:
1. Open the console interface with the default user name and password “admin” to access the
Privileged Exec level.
2. Type “configure” and press <Enter>.
3. Type “username guest password 0 password,” for the Normal Exec level, where password is your
new password. Press <Enter>.
4. Type “username admin password 0 password,” for the Privileged Exec level, where password is
your new password. Press <Enter>.
Username: admin
Password:
CLI session with the EdgeIron 4802CF is opened.
To end the CLI session, enter [Exit].
Console#configure
Console(config)#username guest password 0 [password]
Console(config)#username admin password 0 [password]
Console(config)#
Setting an IP Address
You must establish IP address information for the switch to obtain management access through the
network. This can be done in either of the following ways:
Manual – You have to input the information, including IP address and subnet mask. If your
management station is not in the same IP subnet as the switch, you will also need to specify the
default gateway router.
Dynamic – The switch sends IP configuration requests to BOOTP or DHCP address allocation
servers on the network.
Note: Only one VLAN interface can be assigned an IP address (the default is VLAN 1). This defines
the management VLAN, the only VLAN through which you can gain management access to the
switch. If you assign an IP address to any other VLAN, the new IP address overrides the original IP
address and this becomes the new management VLAN.
Manual Configuration
You can manually assign an IP address to the switch. You may also need to specify a default
gateway that resides between this device and management stations that exist on another network
segment. Valid IP addresses consist of four decimal numbers, 0 to 255, separated by periods.
Anything outside this format will not be accepted by the CLI program.
2-4
© 2007 Foundry Networks, Inc.
March 2007
Switch Management
Note: The IP address for this switch is assigned via DHCP by default.
Before you can assign an IP address to the switch, you must obtain the following information from
your network administrator:
•
IP address for the switch
•
Default gateway for the network
•
Network mask for this network
To assign an IP address to the switch, complete the following steps:
1. From the Privileged Exec level global configuration mode prompt, type “interface vlan 1” to
access the interface-configuration mode. Press <Enter>.
2. Type “ip address ip-address netmask,” where “ip-address” is the switch IP address and
“netmask” is the network mask for the network. Press <Enter>.
3. Type “exit” to return to the global configuration mode prompt. Press <Enter>.
4. To set the IP address of the default gateway for the network to which the switch belongs, type “ip
default-gateway gateway,” where “gateway” is the IP address of the default gateway. Press
<Enter>.
Console(config)#interface vlan 1
Console(config-if)#ip address 192.168.1.5
255.255.255.0
Console(config-if)#exit
Console(config)#ip default-gateway 192.168.1.254
Console(config)#
Dynamic Configuration
If you select the “bootp” or “dhcp” option, IP will be enabled but will not function until a BOOTP or
DHCP reply has been received. You therefore need to use the “ip dhcp restart” command to start
broadcasting service requests. Requests will be sent periodically in an effort to obtain IP
configuration information. (BOOTP and DHCP values can include the IP address, subnet mask, and
default gateway.)
If the “bootp” or “dhcp” option is saved to the startup-config file, then the switch will start
broadcasting service requests as soon as it is powered on.
To automatically configure the switch by communicating with BOOTP or DHCP address allocation
servers on the network, complete the following steps:
1. From the Privileged Exec level global configuration mode prompt, type “interface vlan 1” to
access the interface-configuration mode. Press <Enter>.
2. At the interface-configuration mode prompt, use one of the following commands:
•
To obtain IP settings through DHCP, type “ip address dhcp” and press <Enter>.
December 2007
© 2007 Foundry Networks, Inc.
2-5
Foundry EdgeIron User Guide
•
To obtain IP settings through BOOTP, type “ip address bootp” and press <Enter>.
3. Type “exit” to return to the global configuration mode. Press <Enter>.
4. Type “ip dhcp restart” to begin broadcasting service requests. Press <Enter>.
5. Wait a few minutes, and then check the IP configuration settings, by typing the “show ip interface”
command. Press <Enter>.
6. Then save your configuration changes by typing “copy running-config startup-config.” Enter the
startup file name and press <Enter>.
Console(config)#interface vlan 1
Console(config-if)#ip address dhcp
Console(config-if)#end
Console#ip dhcp restart
Console#show ip interface
IP interface vlan
IP address and netmask: 10.1.0.54 255.255.255.0 on
VLAN 1,and address mode: dhcp.
Console#copy running-config startup-config
Startup configuration file name []: startup
Console#
Enabling SNMP Management Access
The switch can be configured to accept management commands from Simple Network Management
Protocol (SNMP) applications such as HP OpenView. You can configure the switch to (1) respond to
SNMP requests or (2) generate SNMP traps.
When SNMP management stations send requests to the switch (either to return information or to set
a parameter), the switch provides the requested data or sets the specified parameter. The switch can
also be configured to send information to SNMP managers (without being requested by the
managers) through trap messages, which inform the manager that certain events have occurred.
The switch includes an SNMP agent that supports SNMP version 1, 2c, and 3 clients. To provide
management access for version 1 or 2c clients, you must specify a community string. The switch
provides a default MIB View (i.e., an SNMPv3 construct) for the default “public” community string that
provides read access to the entire MIB tree, and a default view for the “private” community string that
provides read/write access to the entire MIB tree. However, you may assign new views to version 1
or 2c community strings that suit your specific security requirements.
Community Strings (for SNMP version 1 and 2c clients)
Community strings are used to control management access to SNMP version 1 and 2c stations, as
well as to authorize SNMP stations to receive trap messages from the switch. You therefore need to
assign community strings to specified users, and set the access level.
The default strings are:
• public - with read-only access. Authorized management stations are only able to retrieve MIB
objects.
• private - with read-write access. Authorized management stations are able to both retrieve and
modify MIB objects.
To prevent unauthorized access to the switch from SNMP version 1 or 2c clients, it is recommended
that you change the default community strings.
2-6
© 2007 Foundry Networks, Inc.
March 2007
Switch Management
To configure a community string, complete the following steps:
1. From the Privileged Exec level global configuration mode prompt, type “snmp-server community
string mode,” where “string” is the community access string and “mode” is rw (read/write) or ro
(read only). Press <Enter>. (Note that the default mode is read only.)
2. To remove an existing string, simply type “no snmp-server community string,” where “string” is
the community access string to remove. Press <Enter>.
Console(config)#snmp-server community admin rw
Console(config)#snmp-server community private
Console(config)#
Note: If you do not intend to support access to SNMP version 1 and 2c clients, we recommend that
you delete both of the default community strings. If there are no community strings, then SNMP
management access from SNMP v1 and v2c clients is disabled.
Trap Receivers
You can also specify SNMP stations that are to receive traps from the switch. To configure a trap
receiver, use the “snmp-server host” command. From the Privileged Exec level global configuration
mode prompt, type:
“snmp-server host host-address community-string
[version {1 | 2c | 3 {auth | noauth | priv}}]”
where “host-address” is the IP address for the trap receiver, “community-string” specifies access
rights for a version 1/2c host, or is the user name of a version 3 host, “version” indicates the SNMP
client version, and “auth | noauth | priv” means that authentication, no authentication, or
authentication and privacy is used for v3 clients. Then press <Enter>. For a more detailed
description of these parameters, see “snmp-server host” on page 10-8. The following example
creates a trap host for each type of SNMP client.
Console(config)#snmp-server host 10.1.19.23 batman
Console(config)#snmp-server host 10.1.19.98 robin version 2c
Console(config)#snmp-server host 10.1.19.34 barbie version 3 auth
Console(config)#
Configuring Access for SNMP Version 3 Clients
Note: SNMP Version 3 is available on devices running software release 2.2.6.x and later.
To configure management access for SNMPv3 clients, you need to first create a view that defines
the portions of MIB that the client can read or write, assign the view to a group, and then assign the
user to a group. The following example creates one view called “mib-2” that includes the entire MIB2 tree branch, and then another view that includes the IEEE 802.1d bridge MIB. It assigns these
respective read and read/write views to a group call “r&d” and specifies group authentication via
December 2007
© 2007 Foundry Networks, Inc.
2-7
Foundry EdgeIron User Guide
MD5 or SHA. In the last step, it assigns a v3 user to this group, indicating that MD5 will be used for
authentication, provides the password “greenpeace” for authentication, and the password “einstien”
for encryption.
Console(config)#snmp-server view mib-2 1.3.6.1.2.1 included
Console(config)#snmp-server view 802.1d 1.3.6.1.2.1.17 included
Console(config)#snmp-server group r&d v3 auth mib-2 802.1d
Console(config)#snmp-server user steve r&d v3 auth md5
greenpeace priv des56 einstien
Console(config)#
For a more detailed explanation on how to configure the switch for access from SNMP v3 clients,
refer to “Configuring SNMP” on page 10-1.
Saving Configuration Settings
Configuration commands only modify the running configuration file and are not saved when the
switch is rebooted. To save all your configuration changes in non-volatile storage, you must copy the
running configuration file to the start-up configuration file using the “copy” command.
To save the current configuration settings, enter the following command:
1. From the Privileged Exec mode prompt, type “copy running-config startup-config” and press
<Enter>.
2. Enter the name of the start-up file. Press <Enter>.
Console#copy running-config startup-config
Startup configuration file name [startup]: startup
Write to FLASH Programming.
Write to FLASH finish.
Success.
Console#
Managing System Files
The switch’s flash memory supports three types of system files that can be managed by the CLI
program, Web interface, or SNMP. The switch’s file system allows files to be uploaded and
downloaded, copied, deleted, and set as a start-up file.
The three types of files are:
2-8
•
Configuration – These files store system configuration information and are created when
configuration settings are saved. Saved configuration files can be selected as a system start-up
file or can be uploaded via TFTP to a server for backup. A file named
“Factory_Default_Config.cfg” contains all the system default settings and cannot be deleted from
the system.
•
Operation Code – System software that is executed after boot-up, also known as run-time code.
This code runs the switch operations and provides the CLI, Web and SNMP management
interfaces. See “Copying the Running Configuration to a File” on page 12-3 for more information.
© 2007 Foundry Networks, Inc.
March 2007
Switch Management
•
Diagnostic Code – Software that is run during system boot-up, also known as POST (Power On
Self-Test).
Due to the size limit of the flash memory, the switch supports only two operation code files. However,
you can have as many diagnostic code files and configuration files as available flash memory space
allows.
In the system flash memory, one file of each type must be set as the start-up file. During a system
boot, the diagnostic and operation code files set as the start-up file are run, and then the start-up
configuration file is loaded.
System Defaults
The switch’s system defaults are provided in the configuration file “Factory_Default_Config.cfg.” To
reset the switch defaults, this file should be set as the startup configuration file. See “Saving or
Restoring Configuration Settings” on page 12-3.
The following table lists some of the basic system defaults.
Function
Parameter
Default
Multi-device Port
Authentication
Global Status
Disabled
Port Status
Disabled
Password Format
xxxxxxxxxxxx
No-override Restrict VLAN
Disabled
Global Disable Aging
Disabled
Port Disable Aging
Disabled
Save Dynamic VLAN to Config
Disabled
Max Age
120 seconds
Authentication Fail Action
Block-traffic
Apply Authentication Filter
Disabled
Enable Dynamic VLAN
Disabled
Move Back to Old VLAN
port-configured-vlan
Management VLAN
1
DHCP
Enabled
BOOTP
Disabled
User Specified
Disabled
IP Address
0.0.0.0
Subnet Mask
255.0.0.0
Default Gateway
0.0.0.0
HTTP Server
Enabled
HTTP Port Number
80
HTTP Secure Server
Enabled
HTTP Secure Port Number
443
IP Settings
Web Management
December 2007
© 2007 Foundry Networks, Inc.
2-9
Foundry EdgeIron User Guide
Function
Parameter
Default
SNMP
SNMP Agent
Enabled
Community Strings
“public” (read only)
“private” (read/write)
Traps
Authentication traps: enabled
Link-up-down traps: enabled
SNMP V3
View: defaultview
Group: public (read only); private (read/write)
Privileged Exec Level
Username “admin”
Password “admin”
Normal Exec Level
Username “guest”
Password “guest”
Enable Privileged Exec from
Normal Exec Level
Password “super”
RADIUS Authentication
Disabled
TACACS Authentication
Disabled
Authentication
local
802.1X Port Authentication
Enabled
HTTPS
Enabled
SSH
Disabled
Port Security
Disabled
Security
Console Port Connection
Port Status
Link Aggregation
Spanning Tree Protocol
Address Table
2-10
IP Filtering
Disabled
Baud Rate
9600
Data bits
8
Stop bits
1
Parity
none
Local Console Timeout
0 (disabled)
Admin Status
Enabled
Auto-negotiation
Enabled
Flow Control
Disabled
10/100/1000 Mbps Port Capability
Fast Ethernet ports: 100 Mbps full duplex
Gigabit Ethernet ports: 1000 Mbps full duplex
Full-duplex flow control disabled
Symmetric flow control disabled
Static Trunks
none
LACP (all ports)
Disabled
Status
Enabled, RSTP
(Defaults: All values based on IEEE 802.1w)
Fast Forwarding
Disabled
Aging Time
300 seconds
© 2007 Foundry Networks, Inc.
March 2007
Switch Management
Function
Parameter
Default
Virtual LANs
Default VLAN
1
PVID
1
Acceptable Frame Type
All
Ingress Filtering
Disabled
Switchport Mode (Egress Mode)
Hybrid: tagged/untagged frames
GVRP (global)
Disabled
GVRP (port interface)
Disabled
Ingress Port Priority
0
Weighted Round Robin
EdgeIron 4802CF, 2402CF
Class 0: 1
Class 1: 4
Class 2: 16
Class 3: 64
Class of Service
EdgeIron 24G-A, 48G, 24GS, 48GS, 8X10G
Class 0: 1
Class 1: 2
Class 2: 4
Class 3: 6
Class 4: 8
Class 5: 10
Class 6: 12
Class 7: 14
Multicast Filtering
Broadcast Storm
Protection1
IP Precedence Priority
Disabled
IP DSCP Priority
Disabled
IP Port Priority
Disabled
IGMP Snooping
Disabled
Act as Querier
Enabled
Status
Enabled (all ports)
Broadcast Limit Rate
EdgeIron 4802CF, 2402CF
500 packets per second
EdgeIron 24G-A, 48G
500 packets per second
System Log
Status
Enabled
Messages Logged
Levels 0-7 (all)
Messages Logged to Flash
Levels 0-3
1 Broadcast Storm Protection is available on devices running running software release 2.2.6.x and later.
December 2007
© 2007 Foundry Networks, Inc.
2-11
Foundry EdgeIron User Guide
2-12
© 2007 Foundry Networks, Inc.
March 2007
Chapter 3
Using the CLI
This chapter describes how to use the Command Line Interface (CLI) including how to configure
basic, non-protocol features on EdgeIron devices. There is no Web equivalent.
The CLI commands contained in this chapter are briefly described in the table that follows:
Command
Function
Mode
Page
enable
Activates privileged mode
NE
3-8
disable
Returns to normal mode from privileged mode
PE
3-8
configure
Activates global configuration mode
PE
3-9
show history
Shows the command history buffer
NE, PE
3-9
reload
Restarts the system
PE
3-10
prompt
Customizes the CLI prompt
GC
3-11
end
Returns to Privileged Exec mode
GC, IC,
LC, VC
3-11
exit
Returns to the previous configuration mode, or exits the
CLI
any
3-11
quit
Exits a CLI session
NE, PE
3-12
help
Shows how to use help
any
NA
?
Shows options for command completion (context
sensitive)
any
NA
General
Accessing the CLI
When accessing the management interface for the switch over a direct connection to the server’s
console port, or via a Telnet connection, the switch can be managed by entering command keywords
and parameters at the prompt. Using the switch’s command-line interface (CLI) is very similar to
entering commands on a UNIX system.
December 2007
© 2007 Foundry Networks, Inc.
3-1
Foundry EdgeIron User Guide
Console Connection
To access the switch through the console port, perform these steps:
1. At the console prompt, enter the user name and password. (The default user names are “admin”
and “guest” with corresponding passwords of “admin” and “guest.”) When the administrator user
name and password is entered, the CLI displays the “Console#” prompt and enters privileged
access mode (i.e., Privileged Exec). But when the guest user name and password is entered, the
CLI displays the “Console>” prompt and enters normal access mode (i.e., Normal Exec).
2. Enter the necessary commands to complete your desired tasks.
3. When finished, exit the session with the “quit” or “exit” command.
After connecting to the system through the console port, the login screen displays:
User Access Verification
Username: admin
Password:
CLI session with the EdgeIron 4802CF is opened.
To end the CLI session, enter [Exit].
Console#
Telnet Connection
Telnet operates over the IP transport protocol. In this environment, your management station and
any network device you want to manage over the network must have a valid IP address. Valid IP
addresses consist of four numbers, 0 to 255, separated by periods. Each address consists of a
network portion and host portion. For example, the IP address assigned to this switch, 10.1.0.1,
consists of a network portion (10.1.0) and a host portion (1).
To access the switch through a Telnet session, you must first set the IP address for the switch, and
set the default gateway if you are managing the switch from a different IP subnet. For example:
Console(config)#interface vlan 1
Console(config-if)#ip address 10.1.0.1 255.255.255.0
Console(config-if)#exit
Console(config)#ip default-gateway 10.1.0.254
If your corporate network is connected to another network outside your office or to the Internet, you
need to apply for a registered IP address. However, if you are attached to an isolated network, then
you can use any IP address that matches the network segment to which you are attached.
After you configure the switch with an IP address, you can open a Telnet session by performing
these steps.
1. From the remote host, enter the Telnet command and the IP address of the device you want to
access.
2. At the prompt, enter the user name and system password. The CLI will display the “Vty-0#”
prompt for the administrator to show that you are using privileged access mode (i.e., Privileged
Exec), or “Vty-0>” for the guest to show that you are using normal access mode (i.e., Normal
Exec).
3-2
© 2007 Foundry Networks, Inc.
March 2007
Using the CLI
3. Enter the necessary commands to complete your desired tasks.
4. When finished, exit the session with the “quit” or “exit” command.
After entering the Telnet command, the login screen displays:
Username: admin
Password:
CLI session with the EdgeIron 4802CF is opened.
To end the CLI session, enter [Exit].
Vty-0#
Note: You can open up to four sessions to the device via Telnet.
Entering Commands
This section describes how to enter CLI commands.
Keywords and Arguments
A CLI command is a series of keywords and arguments. Keywords identify a command, and
arguments specify configuration parameters. For example, in the command “show interfaces status
ethernet 1/5,” show interfaces and status are keywords, ethernet is an argument that specifies the
interface type, and 1/5 specifies the unit/port.
You can enter commands as follows:
•
To enter a simple command, enter the command keyword.
•
To enter multiple commands, enter each command in the required order. For example, to enable
Privileged Exec command mode, and display the startup configuration, enter:
Console>enable
Console#show startup-config
•
To enter commands that require parameters, enter the required parameters after the command
keyword. For example, to set a password for the administrator, enter:
Console(config)#username admin password 0 smith
Minimum Abbreviation
The CLI will accept a minimum number of characters that uniquely identify a command. For example,
the command “configure” can be entered as con. If an entry is ambiguous, the system will prompt for
further input.
Command Completion
If you terminate input with a Tab key, the CLI will print the remaining characters of a partial keyword
up to the point of ambiguity. In the “configure” example, typing con followed by a tab will result in
printing the command up to “configure.”
December 2007
© 2007 Foundry Networks, Inc.
3-3
Foundry EdgeIron User Guide
Getting Help on Commands
You can display a brief description of the help system by entering the help command. You can also
display command syntax by using the “?” character to list keywords or parameters.
Showing Commands
If you enter a “?” at the command prompt, the system will display the first level of keywords for the
current command class (Normal Exec or Privileged Exec) or configuration class (Global, Interface,
Line, or VLAN Database). You can also display a list of valid keywords for a specific command. For
example, the command “show ?” displays a list of possible show commands:
Console#show ?
access-group
access-list
bridge-ext
calendar
dns
dot1x
garp
gvrp
history
hosts
interfaces
ip
lacp
line
log
logging
mac
mac-address-table
management
map
marking
port
public-key
pvlan
queue
radius-server
running-config
snmp
sntp
spanning-tree
ssh
startup-config
system
tacacs-server
users
version
vlan
Console#show
Access groups
Access lists
Bridge extend information
Date information
DNS information
Show 802.1X content
Garp property
Show gvrp information of interface history
Information of history
Host information
Information of interfaces
IP information
Show lacp statistic
TTY line information
Login records
Show the contents of logging buffers
MAC access lists
Set configuration of the address table
Show management ip filter
Map priority
Specify marker
Characteristics of the port
Show information of public key
Information of private VLAN
Information of priority queue
Radius server information
The system configuration of running
SNMP statistics
SNTP
Specify spanning-tree
Secure shell
The system configuration of starting up
Information of system
Login by tacacs server
Display information about terminal lines
System hardware and software status
Switch VLAN Virtual Interface
The command “show interfaces ?” will display the following information:
Console>show interfaces ?
counters
Information of interfaces counters
status
Information of interfaces status
switchport Information of interfaces switchport
Console>show interfaces
3-4
© 2007 Foundry Networks, Inc.
March 2007
Using the CLI
Partial Keyword Lookup
If you terminate a partial keyword with a question mark, alternatives that match the initial letters are
provided. (Remember not to leave a space between the command and question mark.) For example
“s?” shows all the keywords starting with “s.”
Console#show s?
snmp
sntp
system
Console#show s
spanning-tree
ssh
startup-config
Negating the Effect of Commands
For many configuration commands you can enter the prefix keyword “no” to cancel the effect of a
command or reset the configuration to the default value. For example, the logging command will log
system messages to a host server. To disable logging, specify the no logging command. This guide
describes the negation effect for all applicable commands.
Using Command History
The CLI maintains a history of commands that have been entered. You can scroll back through the
history of commands by pressing the up arrow key. Any command displayed in the history list can be
executed again, or first modified and then executed.
Using the show history command displays a longer list of recently executed commands.
Understanding Command Modes
The command set is divided into Exec and Configuration classes. Exec commands generally display
information on system status or clear statistical counters. Configuration commands, on the other
hand, modify interface parameters or enable certain switching functions. These classes are further
divided into different modes. Available commands depend on the selected mode. You can always
enter a question mark “?” at the prompt to display a list of the commands available for the current
mode. The command classes and associated modes are displayed in the following table:
Class
Mode
Exec
Normal
Privileged
Configuration*
Global
Interface
Line
VLAN
* You must be in Privileged Exec mode to access any of the configuration modes.
December 2007
© 2007 Foundry Networks, Inc.
3-5
Foundry EdgeIron User Guide
Exec Commands
When you open a new console session on switch with the user name “guest,” the system enters
Normal Exec command mode (or guest mode). Only a limited number of the commands are
available in this mode. You can access all the commands only in Privileged Exec command mode (or
administrator mode). To access Privilege Exec mode, open a new console session with the user
name “admin,” or enter the enable command (followed by the privileged level password if so
configured). The command prompt displays as “Console>” for Normal Exec mode and “Console#” for
Privileged Exec mode.
To enter Privileged Exec mode, enter the following commands and passwords:
Username: admin
Password: [system login password]
CLI session with the EdgeIron 4802CF is opened.
To end the CLI session, enter [Exit].
Console#
Username: guest
Password: [system login password]
CLI session with the EdgeIron 4802CF is opened.
To end the CLI session, enter [Exit].
Console#enable
Password: [privileged level password if so configured]
Console#
Configuration Commands
Configuration commands are privileged level commands used to modify switch settings. These
commands modify the running configuration only and are not saved when the switch is rebooted. To
store the running configuration in nonvolatile storage, use the copy running-config startup-config
command.
The configuration commands are organized into the following modes:
•
Global Configuration - These commands modify the system level configuration, and include
commands such as hostname and snmp-server community.
•
Access Control List Configuration - These commands are used for packet filtering.
•
Interface Configuration - These commands modify the port configuration such as speed-duplex
and negotiation.
•
Line Configuration - These commands modify the console port and Telnet configuration, and
include command such as parity and databits.
•
VLAN Configuration - Includes the command to create VLAN groups.
To enter the Global Configuration mode, enter the command configure in Privileged Exec mode.
The system prompt will change to “Console(config)#” which gives you access privilege to all Global
Configuration commands.
Console#configure
Console(config)#
3-6
© 2007 Foundry Networks, Inc.
March 2007
Using the CLI
To enter Interface, Line Configuration, or VLAN mode, you must enter the “interface ...,” “line...” or
“vlan database” command while in Global Configuration mode. The system prompt will change to
“Console(config-if)#,” “Console(config-line)#” or Console(config-vlan)” indicating that you have
access privileges to the associated commands. You can use the end command to return to the
Privileged Exec mode.
Console(config)#interface ethernet 1/5
Console(config-if)#exit
Console(config)#line console
Console(config-line)#
Command Line Processing
Commands are not case sensitive. You can abbreviate commands and parameters as long as they
contain enough letters to differentiate them from any other available commands or parameters. You
can use the Tab key to complete partial commands, or enter a partial command followed by the “?”
character to display a list of possible matches. You can also use the following editing keystrokes for
command-line processing:
Keystroke
Function
Ctrl-A
Shifts cursor to start of command line.
Ctrl-B
Shifts cursor to the left one character.
Ctrl-C
Terminates the current task and displays the command prompt.
Ctrl-E
Shifts cursor to end of command line.
Ctrl-F
Shifts cursor to the right one character.
Ctrl-K
Deletes all characters from the cursor to the end of the line.
Ctrl-L
Repeats current command line on a new line.
Ctrl-N
Enters the next command line in the history buffer.
Ctrl-P
Shows the last command.
Ctrl-R
Repeats current command line on a new line.
Ctrl-U
Deletes the entire line.
Ctrl-W
Deletes the last word typed.
Esc-B
Moves the cursor back one word.
Esc-D
Deletes from the cursor to the end of the word.
Esc-F
Moves the cursor forward one word.
Delete key or backspace key
Erases a mistake when entering a command.
December 2007
© 2007 Foundry Networks, Inc.
3-7
Foundry EdgeIron User Guide
General Commands
This section presents general CLI commands. These commands are only relevant for the CLI and
have no Web interface equivalent.
enable
Use this command to activate Privileged Exec mode. In privileged mode, additional commands are
available, and certain commands display additional information. See “Understanding Command
Modes” on page 3-5.
Syntax
enable [level]
level - Privilege level to log into the device.
The device has two predefined privilege levels: 0: Normal Exec, 15: Privileged Exec. Enter
level 15 to access Privileged Exec mode.
Default Setting
Level 15
Command Mode
Normal Exec
Command Usage
• “super” is the default password required to change the command mode from Normal Exec to
Privileged Exec. (To set this password, see the enable password command.)
• The “#” character is appended to the end of the prompt to indicate that the system is in privileged
access mode.
• You only need to use Level 15. Setting the password for Level 0 has no effect.
• You cannot set a null password with the enable password command. You will have to enter a
password to access the Privileged Exec mode.
Example
Console#enable
Console#
Related Commands
disable
enable (3-8)
disable
Use this command to return to Normal Exec mode from privileged mode. In normal access mode,
you can only display basic information on the switch's configuration or Ethernet statistics. To gain
access to all commands, you must use the privileged mode. See “Understanding Command Modes”
on page 3-5.
Default Setting
None
3-8
© 2007 Foundry Networks, Inc.
March 2007
Using the CLI
Command Mode
Privileged Exec
Command Usage
The “>” character is appended to the end of the prompt to indicate that the system is in normal
access mode.
Example
Console#disable
Console>
Related Commands
enable (3-8)
configure
Use this command to activate Global Configuration mode. You must enter this mode to modify any
settings on the switch. You must also enter Global Configuration mode prior to enabling some of the
other configuration modes, including Interface Configuration, Line Configuration, and VLAN
Database Configuration. See “Understanding Command Modes” on page 3-5.
Note: This command is available in devices running software version 2.2.4.11 and later.
Syntax
configure [terminal]
• terminal - Specifies where the commands come in. Typing terminal is optional for compatibility
with existing BigIron command line syntax.
Default Setting
None
Command Mode
Privileged Exec
Example
Console#configure
Console(config)#
Related Commands
end (3-11)
show history
Use this command to show the contents of the command history buffer.
Default Setting
None
Command Mode
Normal Exec, Privileged Exec
December 2007
© 2007 Foundry Networks, Inc.
3-9
Foundry EdgeIron User Guide
Command Usage
The history buffer size is fixed at 20 commands.
Example
In this example, the show history command lists the contents of the command history buffer:
Console#show history
Exection command history:
3 sh logging flash
2 sh interfaces
1 sh history
Configuration command history:
4 interface vlan 1
3 exit
2 interface vlan 1
1 end
Console#
The ! command repeats commands from the Execution command history buffer when you are in
Normal Exec or Privileged Exec Mode, and commands from the Configuration command history
buffer when you are in any of the configuration modes. In this example, the !2 command repeats the
second command in the Execution history buffer (config).
Console#!2
Console#config
Console(config)#
reload
Use this command to restart the system.
Note: When the system is restarted, it will always run the Power-On Self-Test. It will also retain all
configuration information stored in non-volatile memory by the copy running-config startup-config
command.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
This command resets the entire system.
Example
This example shows how to reset the switch:
Console#reload
System will be restarted, continue <y/n>? y
3-10
© 2007 Foundry Networks, Inc.
March 2007
Using the CLI
prompt
Use this command to customize the CLI prompt. Use the no form to revert to the default prompt.
Syntax
prompt string
no prompt
string - Any alphanumeric string to use for the command prompt. (Maximum length: 255
characters)
Default Setting
Console
Command Mode
Global Configuration
Example
Console(config)#prompt EIF2402CF
EIF2402CF(config)#
end
Use this command to return to Privileged Exec mode.
Default Setting
None
Command Mode
Global Configuration, Interface Configuration, Line Configuration, VLAN Database Configuration
Example
This example shows how to return to the Privileged Exec mode from the Interface Configuration
mode:
Console(config-if)#end
Console#
exit
Use this command to return to the previous configuration mode or exit the configuration program.
Default Setting
None
Command Mode
Any
December 2007
© 2007 Foundry Networks, Inc.
3-11
Foundry EdgeIron User Guide
Example
This example shows how to return to the Privileged Exec mode from the Global Configuration mode,
and then quit the CLI session:
Console(config)#exit
Console#exit
Press ENTER to start session
User Access Verification
Username:
quit
Use this command to exit the configuration program.
Default Setting
None
Command Mode
Normal Exec, Privileged Exec
Command Usage
The quit and exit commands can both exit the configuration program.
Example
This example shows how to quit a CLI session:
Console#quit
Press ENTER to start session
User Access Verification
Username:
3-12
© 2007 Foundry Networks, Inc.
March 2007
Chapter 4
Using the Web Interface
This chapter describes how to use the Web interface. There is no equivalent CLI section.
The EdgeIron range provides an embedded HTTP Web agent. Using a Web browser you can
configure the switch and view statistics to monitor network activity. The Web agent can be accessed
by any computer on the network using a standard Web browser (Internet Explorer 5.0 or above, or
Netscape Navigator 6.2 or above).
Note: You can also use the Command Line Interface (CLI) to manage the switch over a serial
connection to the console port or via Telnet. For more information on using the CLI, refer to
Chapter 3 “Using the CLI.”
Prior to accessing the switch from a Web browser, be sure you have first performed the following
tasks:
1. Configure the switch with a valid IP address, subnet mask, and default gateway using an out-ofband serial connection, BOOTP or DHCP protocol. (See “Setting the IP Address” on page 5-19.)
2. Set user names and passwords using an out-of-band serial connection. Access to the Web agent
is controlled by the same user names and passwords as the onboard configuration program.
(See “Configuring the Logon Password.” on page 9-2.)
3. After you enter a user name and password, you will have access to the system configuration
program.
Notes: 1. You are allowed three attempts to enter the correct password; on the third failed attempt
the current connection is terminated.
2. If you log into the Web interface as guest (Normal Exec level), you can view page
information but only change the guest password. If you log in as “admin” (Privileged Exec
level), you can apply changes on all pages.
3. If the path between your management station and this switch does not pass through any
device that uses the Spanning Tree Protocol, then you can set the switch port attached to
your management station to fast forwarding to improve the switch’s response time to
management commands issued through the Web interface. (See “STP Port and Trunk
Configuration” on page 21-17.)
December 2007
© 2007 Foundry Networks, Inc.
4-1
Foundry EdgeIron User Guide
Navigating the Web Browser Interface
To access the Web-browser interface you must first enter a user name and password. The
administrator has Read/Write access to all configuration parameters and statistics. The default user
name and password for the administrator is “admin.”
Home Page
When your Web browser connects with the switch’s Web agent, the home page is displayed as
shown below. The home page displays the Main Menu on the left side of the screen and System
Information on the right side. The Main Menu links are used to navigate to other menus, and display
configuration parameters and statistics. (The following screen displays the EdgeIron 4802CF
homepage.)
Configuration Options
Configurable parameters have a dialog box or a drop-down list. Once a configuration change has
been made on a page, be sure to click on the “Apply” or “Apply Changes” button to confirm the new
setting. The following table summarizes the Web page configuration buttons.
Button
Action
Revert
Cancels specified values and restores current values prior to pressing
“Apply.”
Help
Links directly to web help.
Apply
Sets specified values to the system.
Notes: 1. To ensure proper screen refresh, be sure that Internet Explorer 5.x is configured as
follows: Under the menu “Tools / Internet Options / General / Temporary Internet Files /
Settings,” the setting for item “Check for newer versions of stored pages” should be “Every
visit to the page.”
2. When using Internet Explorer 5.0, you may have to manually refresh the screen after
making configuration changes by pressing the browser’s refresh button.
4-2
© 2007 Foundry Networks, Inc.
March 2007
Using the Web Interface
Panel Display
The Web agent displays an image of the switch’s ports, indicating whether each link is up or down.
Clicking on the image of a port opens the Port Configuration page. (See “Configuring Interface
Connections” on page 17-11.)
Main Menu
Using the onboard Web agent, you can define system parameters, manage and control the switch,
and all its ports, or monitor network conditions. The table that follows briefly describes the selections
available from this program.
Menu
Description
Page
System
System Information
Provides basic system description, including contact information
5-2
Switch Information
Shows the number of ports, hardware/firmware version numbers,
and power status
5-12
Bridge Extension
Shows the configuration for bridge extension command
5-18
IP Configuration
Sets the IP address for management access
5-19
Firmware
Manages code image files
12-1
Configuration
Manages switch configuration files
12-3
File
Log
Log
Stores and displays error messages
7-2
System Logs
Sends error messages to a logging process
7-2
Remote Logs
Configures the logging of messages to a remote logging process
7-5
SMTP
Sends an SMTP client message to a participating server
7-10
Restarts the switch
5-26
Reset
SNTP
Configuration
Configures SNTP client settings, including broadcast mode or a
specified list of servers
8-2
Clock Time Zone
Sets the local time zone for the system clock
8-4
SNMP
SNMP Configuration
Configures community strings and related trap functions
10-1
Agent Status
Enables or disables SNMP
10-10
Engine ID
Sets the SNMP v3 engine ID
10-12
Remote Engine ID
Sets the SNMP v3 engine ID on a remote device
10-14
Users
Configures SNMP v3 users
10-15
Remote Users
Configures SNMP v3 users on a remote device
10-19
Groups
Configures SNMP v3 groups
10-20
SNMPv3
December 2007
© 2007 Foundry Networks, Inc.
4-3
Foundry EdgeIron User Guide
Menu
Views
Description
Page
Configures SNMP v3 views
10-24
Security
Passwords
Assigns a new password for the logon user name
9-2
Authentication Settings
Configures RADIUS and TACACS+ authentication parameters
9-5
HTTPS Settings
Configures secure HTTP settings
5-26
SSH Settings
Configures Secure Shell settings.
13-1
Host-Key Settings
Generates the host key pair (public and private)
13-3
Information
Displays general port authentication status information
14-1
Configuration
Enables the changing of general port authentication features
14-6
Port Configuration
Enables the changing of port authentication features
14-9
Statistics
Displays a per-port statistical readout
SSH
802.1X
14-11
ACL
Configuration
Configures packet filtering based on IP or MAC addresses
Mask Configuration
Controls the order in which ACL rules are checked
19-23
Port Binding
Binds a port to the specified ACL
19-31
IP Filter
19-4
Sets IP addresses of clients allowed management access via the
Web, SNMP, and Telnet
16-1
Displays port connection status
17-3
Port
Port Information
Trunk Information
Displays trunk connection status
Port Configuration
Configures port connection settings
17-11
17-3
Trunk Configuration
Configures trunk connection settings
17-35
Trunk Members
Specifies ports to groups in static trunks
18-2
LACP
Configuration
Allows ports to dynamically join trunks
18-1
Aggregation Port
Configures system priority, admin key, and port priority
18-1
Port Counters Information
Displays statistics for LACP protocol messages
18-9
Port Internal Information
Displays settings and operational state for local side
18-13
Port Neighbors Information
Displays settings and operational state for remote side
18-15
Port Broadcast Control
Sets the broadcast control threshold for each port
17-24
Trunk Broadcast Control
Sets the broadcast control threshold for each trunk
17-24
Mirror Port Configuration
Sets the source and target ports for mirroring
17-26
Sets the rate limit for each port
17-29
Lists Ethernet and RMON port statistics
17-31
Rate Limit
Rate Limit Configuration
Port Statistics
Address Table
4-4
Static Addresses
Displays entries for interface, address or VLAN
20-1
Dynamic Addresses
Displays or edits static entries in the Address Table
20-4
Address Aging
Sets timeout for dynamically learned entries
20-6
© 2007 Foundry Networks, Inc.
March 2007
Using the Web Interface
Menu
Description
Page
Spanning Tree
Information
Displays STP values used for the bridge
21-4
Configuration
Configures global bridge settings for STP
21-7
Port Information
Configures individual port settings for STP
21-15
Trunk Information
Configures individual trunk settings for STP
21-15
Port Configuration
Configures individual port settings for STP
21-17
Trunk Configuration
Configures individual trunk settings for STP
21-17
VLAN
802.1Q VLAN
Basic Information
Displays basic information on the VLAN type supported by this
switch
22-5
Current Table
Shows the current port members of each VLAN and whether or
not the port supports VLAN tagging
22-6
Static List
Used to create or remove VLAN groups
22-6
Static Table
Modifies the settings for an existing VLAN
22-9
Static Membership by Port
Configures membership type for interfaces, including tagged or
untagged
22-11
Port Configuration
Specifies default PVID and VLAN attributes
22-15
Trunk Configuration
Specifies default trunk VID and VLAN attributes
22-17
Private VLAN
Status
Enables or disables the private VLAN
23-6
Link Status
Configures the private VLAN
23-4
Default Port Priority
Sets the default priority for each port
25-2
Default Trunk Priority
Sets the default priority for each trunk
25-2
Traffic Class
Maps IEEE 802.1p priority tags to output queues
25-6
Queue Scheduling
Configures Weighted Round Robin queueing
IP Precedence/DSCP Priority
Status
Globally selects IP Precedence or DSCP Priority, or disables both
25-10
IP Precedence Priority
Sets IP Type of Service priority, mapping the precedence tag to a
class-of-service value
25-11
IP DSCP Priority
Sets IP Differentiated Services Code Point priority, mapping a
DSCP tag to a class-of-service value
25-14
IP Port Priority Status
Globally enables or disables IP Port Priority
25-17
IP Port Priority
Sets TCP port priority, defining the socket number and associated
class-of-service value
25-17
ACL CoS Priority
Sets the CoS value and corresponding output queue for packets
matching an ACL rule
25-21
ACL Marker
Change traffic priorities for frames matching an ACL rule
25-24
Priority
25-9
IGMP Snooping
IGMP Configuration
Enables multicast filtering; configures parameters for multicast
query
26-2
Multicast Router
Port Information
Displays the ports that are attached to a neighboring multicast
router/switch for each VLAN ID
26-9
December 2007
© 2007 Foundry Networks, Inc.
4-5
Foundry EdgeIron User Guide
Menu
Static Multicast Router Port
Configuration
4-6
Description
Page
Assigns ports that are attached to a neighboring multicast
router/switch
26-10
IP Multicast Registration Table Displays all multicast groups active on this switch, including
multicast IP addresses and VLAN ID
26-12
IGMP Member Port Table
26-13
Indicates multicast addresses associated with the selected VLAN
© 2007 Foundry Networks, Inc.
March 2007
Chapter 5
Basic Configuration
Using the onboard Web agent or the CLI console, you can define system parameters, manage and
control the switch, and all its ports, or monitor network conditions.
The CLI commands for this section are briefly described in the table that follows:
Command
Function
Mode
ip telnet server
Allows the switch to be monitored or configured from
Telnet; also specifies the port to be used by the Telnet
interface
GC
5-3
mac-address-table static
to map a static address to a port in a VLAN
GC
5-4
show mac-address-table
Displays classes of entries in the bridge-forwarding
database.
PE
5-4
pvlan
Enables or configures private VLAN.
GC
5-5
show pvlan
Displays private VLAN configuration.
PE
5-6
show interfaces counters
brief
Displays interface statistics for all ports.
NE
5-6
jumbo frame
Enables support for jumbo frames.
GC
5-7
show process cpu
Displays the CPU process utilization.
NE, PE
5-7
show tech-support
Displays all the important system information and
configuration.
NE, PE
5-8
banner motd
Defines and enables a message-of-the-day (MOTD)
banner.
GC
5-9
hostname
Specifies or modifies the host name for the device
GC
5-10
snmp-server location
Sets the system location string
GC
5-10
snmp-server contact
Sets the system contact string
GC
5-10
show system
Displays system information
NE, PE
5-11
show bridge-ext
Shows bridge extension configuration
PE
5-19
show version
Displays version information for the system
NE, PE
5-13
show startup-config
Displays the contents of the configuration file (stored in
flash memory) that is used to start up the system
PE
5-13
show running-config
Displays the configuration data currently in use
PE
5-15
December 2007
© 2007 Foundry Networks, Inc.
Page
5-1
Foundry EdgeIron User Guide
Command
Function
Mode
Page
show users
Shows all active console and Telnet sessions, including
user name, idle time, and IP address of Telnet client
NE, PE
5-17
ip address
Sets the IP address for this device
IC
5-21
ip default-gateway
Defines the default gateway through which an in-band
management station can reach this device
GC
5-22
light unit
Displays the switch’s unit ID using its front-panel LEDs
NE, PE
5-22
switch renumber
Renumbers stack units
PE
5-23
ip dhcp restart
Submits a BOOTP or DCHP client request
PE
5-25
reload
Restarts the system
PE
5-26
ip http port
Specifies the port to be used by the Web browser
interface
GC
5-27
ip http server
Allows the switch to be monitored or configured from a
browser
GC
5-28
ip http secure-server
Enables the HTTPS server on the switch
GC
5-28
ip http secure-port
Specifies the TCP port number used for HTTPS
connection to the switch’s Web interface
GC
5-29
show vsrp aware
Use this command to display VSRP information
PE
5-31
vsrp aware
Enables the sending of VSRP packets
GC
5-31
Stacking Commands
IP Commands
Secure Server
VSRP
System Information
Identifies the system by providing a descriptive name, location and contact information.
USING THE WEB INTERFACE
To configure the system name, location, and contact information for the system administrator click
System, System Information. Specify the system name, location, and contact information, then click
5-2
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
Apply. (This page also includes a Telnet button that allows you to access the Command Line Interface
via Telnet.)
•
System Name – Name assigned to the switch system.
•
Object ID – MIB II object ID for switch’s network management subsystem.
•
Location – Specifies the system location.
•
Contact – Administrator responsible for the system.
•
System Up Time – Length of time the management agent has been up.
USING THE CLI
Use the commands in this section to specify the hostname, location and contact information, as well
as to display system information.
ip telnet server
This command allows this device to be monitored or configured from Telnet. It also specifies the TCP
port number used by the Telnet interface. Use the no form without the “port” keyword to disable this
function. Use the no from with the “port” keyword to use the default port.
Syntax
ip telnet server [port port-number]
[no] telnet server [port]
• port - The TCP port used by the Telnet interface.
• port-number - The TCP port number to be used by the browser interface. (Range: 1-65535)
Default Setting
Server: Enabled
Server Port: 23
Command Mode
Global Configuration
December 2007
© 2007 Foundry Networks, Inc.
5-3
Foundry EdgeIron User Guide
Example
Console(config)#ip telnet server
Console(config)#ip telnet port 123
Console(config)#
mac-address-table static
Use this command to map a static address to a port in a VLAN. Use the no form to remove an
address.
Syntax
mac-address-table static mac-address {interface interface} vlan vlan-id [action]
[no] mac-address-table static mac-address vlan vlan-id
• mac-address - MAC address.
• interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
• action • delete-on-reset - Assignment lasts until the switch is reset.
• permanent - Assignment is permanent.
Default Setting
No static addresses are defined. The default mode is permanent.
Command Mode
Global Configuration
Command Usage
The static address for a host device can be assigned to a specific port within a specific VLAN. Use this
command to add static addresses to the MAC Address Table. Static addresses have the following
characteristics:
• Static addresses will not be removed from the address table when a given interface link is down.
• Static addresses are bound to the assigned interface and will not be moved. When a static address is
dynamically learned on an interface, the address will be ignored and will not be written to the address table.
• A static address cannot be learned on another port until the address is removed with the no form of this
command.
Example
Console(config)#mac-address-table static 00-20-1A-20-7D-06 ethernet 1/1 vlan 1
delete-on-reset
Console(config)#
show mac-address-table
Use this command to view classes of entries in the bridge-forwarding database.
Syntax
show mac-address-table [address mac-address [mask]] [interface interface] [vlan vlan-id]
[sort {address | vlan | interface}]
• mac-address - MAC address.
5-4
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
• mask - Bits to ignore in the address.
• interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
• vlan-id - VLAN ID (Range: 1-4094)
• sort - Sort by address, vlan or interface.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
• The MAC Address Table contains the MAC addresses associated with each interface. Note that the Type
field may include the following types:
- Learned - dynamic address entries
- Permanent - static entry
- Delete-on-reset - static entry to be deleted when system is reset
• The maximum number of address entries is 8191.
Example
Console#show mac-address-table
Interface Mac Address
Vlan
--------- ----------------- ---Eth 1/ 1 00-20-1A-20-7D-02
1
Eth 1/26 00-20-1A-20-7D-27
1
Console#
Type
----------------Delete-on-reset
Learned
pvlan
Note: This command is not supported on 2404CF, 4804CF, 24G-A, and 48G.
Use this command in global configuration mode to enable or configure private VLAN. Use the no
form of this command to disable it.
Syntax
pvlan [up-link interface-list down-link interface-list]
[no] pvlan
• up-link – Specifies a list of uplink interfaces.
• down-link – Specifies a list of downlink interfaces.
Default Setting
No pvlan
Command Mode
Global configuration
Command Usage
A Private VLAN allows modification of the default VLAN to provide port-based security and isolation
between ports within the VLAN. Data traffic on the downlink ports can only be forwarded to, and from, the
uplink port. Private VLANs and normal VLANs can exist simultaneously within the same switch.
December 2007
© 2007 Foundry Networks, Inc.
5-5
Foundry EdgeIron User Guide
Example
Console(config)#pvlan up-link ethernet 1/25 down-link ethernet 1/1
Console(config)#
show pvlan
Note: This command is not supported on 2404CF, 4804CF, 24G-A, and 48G.
Use this command in privileged configuration mode to display the configured private VLANs.
Syntax
show pvlan
Default Setting
No pvlan
Command Mode
Priveleged executive
Example
Console#show pvlan
Private VLAN status: Enabled
Up-link port:
Ethernet 1/25
Down-link port:
Ethernet 1/1
Console#
show interfaces counters brief
Use this command to display interface statistics for all ports.
Syntax
show interfaces counters brief
Default Setting
None
Command Mode
Normal Exec
Example
Console#show interfaces counters brief
Ethernet
Packets
Collisions
Port
[Receive
Transmit]
[Receive]
1/ 1
328
10
0
1/ 2
0
0
0
1/ 3
0
0
0
1/ 4
0
0
0
1/ 5
0
0
0
......
Console#
5-6
Errors
[Input
Output]
0
0
0
0
0
0
0
0
0
0
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
jumbo frame
This command enables support for jumbo frames. Use the no form to disable it.
Syntax
jumbo frame
Default Setting
Disabled
Command Mode
Global Configuration
Command Usage
• This switch provides more efficient throughput for large sequential data transfers by supporting
jumbo frames up to 9216 bytes (EdgeIron 24G-A, 48G, 24GS, 48GS, and 8X10G) and mini
jumbo frames up to 2048 bytes (EdgeIron 2402CF and 4802CF). Compared to standard
Ethernet frames that run only up to 1.5 KB, using jumbo frames significantly reduces the perpacket overhead required to process protocol encapsulation fields.
• To use jumbo frames, both the source and destination end nodes (such as a computer or
server) must support this feature. Also, when the connection is operating at full duplex, all
switches in the network between the two end nodes must be able to accept the extended frame
size. And for half-duplex connections, all devices in the collision domain would need to support
jumbo frames.
• Enabling jumbo frames will limit the maximum threshold for broadcast storm control to 64
packets per second. (See the switchport broadcast command on page 17-25.)
Example
Console(config)#jumbo frame
Console(config)#
show process cpu
Use this command to display the CPU process utilization.
Syntax
show process cpu
Default Setting
None
Command Mode
Normal Exec, Privileged Exec
Command Usage
Information on all processes is displayed. The following information is displayed for each process:
• Process Name - Shows the process name.
• 5Sec(%) - Shows what percentage of the cpu the process has utilized in the last 5 seconds.
• 1Min(%) - Shows what percentage of the cpu the process has utilized in the last minute.
• 5Min(%) - Shows what percentage of the cpu the process has utilized in the last 5 minutes.
• 15Min(%) - Shows what percentage of the cpu the process has utilized in the last 15 minutes.
December 2007
© 2007 Foundry Networks, Inc.
5-7
Foundry EdgeIron User Guide
• Runtime(ms) - Shows for how many milliseconds the process has been running for.
Example
Console#show process cpu
Process Name
5Sec(%)
tRootTask
0.93
tExcTask
0.00
.
.
.
SSHD_MAIN_TASK
0.00
SNMP_TASK
0.00
CLITASK0
0.00
tSOC-CLI
0.00
Console#
1Min(%)
0.93
0.00
0.03
0.05
7.09
0.00
5Min(%)
0.93
0.00
15Min(%)
1.26
0.00
0.03
0.05
7.40
0.00
0.03
0.05
7.17
0.00
Runtime(ms)
21244470
0
1183780
1258590
177006520
0
show tech-support
This command displays all the important system information and configuration. It is used to allow for
easier debugging and fault-finding on the switch.
Syntax
show tech-support
Default Setting
None
Command Mode
Normal Exec, Privileged Exec
Command Usage
Information on the following items is displayed.
• System Information - Displays system information.
• Version Information - Displays hardware and software version information.
• VLAN Information - Displays VLAN information.
• Running-config - Displays the configuration information currently in use.
• Spanning-tree - Displays the information for the common spanning tree and multiple spanning
tree.
• Runtime(ms) - Shows for how many milliseconds the process has been running for.
• Interfaces brief - Displays the link and connection status of the switches interfaces.
• Interfaces - Displays the administrative and operational status of the switches interfaces.
• Mac-address-table - Displays classes of entries in the bridge-forwarding database.
• ARP - Displays the contents of the ARP cache.
• Mac-address-table multicast - Displays known multicast addresses.
• IP IGMP Snooping - Displays the IGMP Snooping configuration.
• Logging RAM - Displays the log messages and settings for storing log messages.
• Process CPU - Displays the CPU process utilization.
• Port Security - Displays port security status and settings.
5-8
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
Example
Console#show tech-support
show system
System description: Foundry Networks EdgeIron 48G1X10G
System OID string: 1.3.6.1.4.1.1991.1.5.1.1.4.4.10.1
.
.
.
.
SNTP
0.09
0.11
0.12
SSHD_MAIN
1.10
1.29
1.42
SNMP
0.06
0.06
0.07
CLITASK0
4.54
3.09
2.30
Console#
0.12
1.42
0.07
2.30
14960
168180
9460
348640
banner motd
Use this command to define and enable a message-of-the-day (MOTD) banner. use the no form of
this command to disable this function.
Syntax
banner motd d message d
no banner motd
• d - Any delimiting character, indicating the beginning and end of the message.
• message - Message text.
Default Setting
No banner is defined
Command Mode
Global Configuration
Command Usage
• A delimiting character is established on the first line of the banner motd command. The message
begins and ends at this delimiting character, which cannot be used in the message itself.
• The delimiting character can be any character except “ (double quotation mark).
• Use the no banner motd command to remove the banner.
• The banner text can contain up to 2048 characters and consist of multiple lines.
Example
This example sets the message of the day banner, using $ (dollar sign) as the delimiting character.
Console(config)#banner motd $
Enter TEXT message. End with the character ‘$’.
Hello World! $
Console(config)#exit
Console#exit
Press ENTER to start session
Hello World!
User Access Verification
Username:
December 2007
© 2007 Foundry Networks, Inc.
5-9
Foundry EdgeIron User Guide
hostname
Use this command to specify or modify the system name (as displayed on the system information
page) for this device. Use the no form to restore the default host name.
Syntax
hostname name
no hostname
name - The name of this host. (Maximum length: 255 characters)
Default Setting
None
Command Mode
Global Configuration
Example
Console(config)#hostname EdgeIron 4802CF
Console(config)#
snmp-server location
Use this command to set the system location string. Use the no form to remove the location string.
Syntax
snmp-server location text
no snmp-server location
text - String that describes the system location.
(Maximum length: 255 characters)
Default Setting
None
Command Mode
Global Configuration
Example
Console(config)#snmp-server location WC-19
Console(config)#
Related Commands
snmp-server contact (5-10)
snmp-server contact
Use this command to set the system contact string. Use the no form to remove the system contact
information.
Syntax
snmp-server contact string
no snmp-server contact
5-10
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
string - String that describes the system contact information.
(Maximum length: 255 characters)
Default Setting
None
Command Mode
Global Configuration
Example
Console(config)#snmp-server contact Paul
Console(config)#
Related Commands
snmp-server location (5-10)
show system
Use this command to display system information.
Default Setting
None
Command Mode
Normal Exec, Privileged Exec
Command Usage
•
•
•
•
•
•
•
•
System Name – Name assigned to the switch system.
Object ID – MIB II object ID for switch’s network management subsystem.
Location – Specifies the system location.
Contact – Administrator responsible for the system.
System Up Time – Length of time the management agent has been up.
MAC Address - The physical layer address for the switch.
Web server - Shows if management access via HTTP is enabled or disabled.
Web server port - Shows the TCP port number used by the Web interface.
• Web secure server port - Shows the TCP port number used by the HTTPS server.
• The POST results should all display “PASS.” If any POST test indicates “FAIL,” contact Technical
Support for assistance.
December 2007
© 2007 Foundry Networks, Inc.
5-11
Foundry EdgeIron User Guide
Example
Console#show system
System Description: Foundry Networks EdgeIron 48G1X10G System OID String:
1.
3.6.1.4.1.1991.1.5.1.1.4.10.1 System Information
System Up Time:
0 days, 0 hours, 11 minutes, and 32.52 seconds
System Name:
[NONE]
System Location:
[NONE]
System Contact:
[NONE]
MAC Address (Unit1):
00-0C-DB-88-AF-E0
Web Server:
Enabled
Web Server Port:
80
Web Secure Server:
Enabled
Web Secure Server Port: 443
Telnet Server:
Enable
Telnet Server Port:
23
Jumbo Frame:
Enabled
POST result
UART LOOP BACK Test..........PASS
DRAM Test....................PASS
Timer Test...................PASS
PCI Device 1 Test............PASS
PCI Device 2 Test............PASS
Switch Int Loopback test.....PASS
Done All Pass.
Console#
Displaying Switch Hardware/Software Versions
Both the Web and CLI interfaces can display hardware/firmware version numbers for the main board
and management software, as well as the power status of the system.
USING THE WEB INTERFACE
Click System, Switch Information.
Main Board
5-12
•
Serial Number – The serial number of the switch.
•
Number of Ports – Number of built-in RJ-45 ports
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
•
Hardware Version – Hardware version of the main board.
•
Internal Power Status – Displays the status of the internal power supply.
Management Software
•
Loader Version – Version number of loader code.
•
Boot-ROM Version – Version number of Power-On Self-Test (POST) and boot code.
•
Operation Code Version – Version number of runtime code.
•
Role – Shows that this switch is operating as Master (i.e., operating stand-alone).
USING THE CLI
show version
Use this command to display hardware and software version information for the system.
Default Setting
None
Command Mode
Normal Exec, Privileged Exec
Command Usage
•
•
•
•
•
•
•
•
•
Serial Number – The serial number of the switch.
Number of Ports – Number of built-in RJ-45 ports
Hardware Version – Hardware version of the main board.
Internal Power Status – Displays the status of the internal power supply.
Redundant Power Status - Displays the status of the internal power supply.
Loader Version – Version number of loader code.
Boot-ROM Version – Version number of Power-On Self-Test (POST) and boot code.
Operation Code Version – Version number of runtime code.
Role – Shows that this switch is operating as Master (i.e., operating stand-alone).
Example
Console#show version
Unit1
Serial number
Hardware version
Number of ports
Main power status
Redundant power status
Agent(master)
Unit id
Loader version
Boot rom version
Operation code version
Console#
:A329025054
:R01
:24
:up
:not present
:1
:2.0.2.2
:2.0.2.4
:2.2.6.x
show startup-config
Use this command to display the configuration file stored in non-volatile memory that is used to start
up the system.
Note: The TACACS+ and RADIUS keys on the 2404CF, 4804CF, 24G-A, and 48G are not
encrypted in the configuration file and appear as readable text. They are appear as encrypted text in
December 2007
© 2007 Foundry Networks, Inc.
5-13
Foundry EdgeIron User Guide
the 24G-A, 48G and 8X10G configuration files.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
• Use this command in conjunction with the show running-config command to compare the
information in running memory to the information stored in non-volatile memory.
• This command displays settings for key command modes. Each mode group is separated by “!”
symbols, and includes the configuration mode command, and corresponding commands. This
command displays the following information:
- SNMP community strings
- Users (names and access levels)
- VLAN database (VLAN ID, name and state)
- VLAN configuration settings for each interface
- IP address configured for VLANs
- Spanning tree settings
- Any configured settings for the console port and Telnet
Example
Console#show startup-config
building startup-config, please wait.....
!
!
username admin access-level 15
username admin password 0 admin
!
username guest access-level 0
username guest password 0 guest
!
enable password level 15 0 super
!
snmp-server community public ro
snmp-server community private rw
!
vlan 1 name DefaultVlan
!
interface vlan 1
ip address dhcp
!
line console
!
line vty
!
!
end
Console#
Related Commands
show running-config (5-15)
5-14
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
show running-config
Use this command to display the configuration information currently in use.
Note: The TACACS+ and RADIUS keys on the 2404CF, 4804CF, 24G-A, and 48G are not
encrypted in the configuration file and appear as readable text. They are appear as encrypted text in
the 24G-A, 48G and 8X10G configuration files.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
• Use this command in conjunction with the show startup-config command to compare the
information in running memory to the information stored in non-volatile memory.
• This command displays settings for key command modes. Each mode group is separated by “!”
symbols, and includes the configuration mode command, and corresponding commands. This
command displays the following information:
- SNMP community strings
- Users (names, access levels, and encrypted passwords)
- VLAN database (VLAN ID, name and state)
- VLAN configuration settings for each interface
- IP address configured for VLANs
- Spanning tree settings
- Any configured settings for the console port and Telnet
December 2007
© 2007 Foundry Networks, Inc.
5-15
Foundry EdgeIron User Guide
Example
Console#show running-config
building running-config, please wait.....
!
phymap 00-01-f4-88-f5-20
!
SNTP server 0.0.0.0 0.0.0.0 0.0.0.0
!
!
!
SNMP-server community private rw
SNMP-server community public ro
!
!
username admin access-level 15
username admin password 7 21232f297a57a5a743894a0e4a801fc3
username guest access-level 0
username guest password 7 084e0343a0486ff05530df6c705c8bb4
enable password level 15 7 1b3231655cebb7a1f783eddf27d254ca
!
!
!
!
vlan 1 name DefaultVlan
untagged ethernet 1/1 to 1/24
!
!
!
!
!
spanning-tree mst configuration
!
!
!
!
!
interface ethernet 1/1
!
interface ethernet 1/2
.
.
.
.
!
interface ethernet 1/24
!
!
!
interface VLAN 1
IP address DHCP
!
!
!
!
no map IP precedence
no map IP DSCP
!
!
!
!
line console
!
!
line VTY
!
!
!
end
!
Console#
Related Commands
show startup-config (5-13)
5-16
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
Note: There is no Web equivalent for the following command.
show users
Shows all active console and Telnet sessions, including user name, idle time, and IP address of
Telnet client.
Default Setting
None
Command Mode
Normal Exec, Privileged Exec
Command Usage
The session used to execute this command is indicated by a “*” symbol next to the Line (i.e.,
session) index number.
Example
Console#sh users
Username accounts:
Username Privilege Public-Key
-------- --------- ---------admin
15
None
guest
0
None
Online users
Line
Username Idle time (h:m:s) Remote IP addr.
----------- -------- ----------------- --------------* 0
console
admin
0:00:00
1
vty 0
admin
0:04:37
10.1.0.19
Console#
December 2007
© 2007 Foundry Networks, Inc.
5-17
Foundry EdgeIron User Guide
Displaying Bridge Extension Capabilities
The Bridge MIB includes extensions for managed devices that support Multicast Filtering, Traffic
Classes, and Virtual LANs. You can access these extensions to display default settings for the key
variables, or to configure the global setting for GARP VLAN Registration Protocol (GVRP).
USING THE WEB INTERFACE
Click System, Bridge Extension.
5-18
•
Extended Multicast Filtering Services – This switch does not support the filtering of individual
multicast addresses based on GMRP (GARP Multicast Registration Protocol).
•
Traffic Classes – This switch provides mapping of user priorities to multiple traffic classes. (Refer
to Chapter 25 “Class of Service.)
•
Static Entry Individual Port – This switch allows static filtering for unicast and multicast
addresses. (Refer to “Address Table” on page 20-1.)
•
VLAN Learning – This switch uses Independent VLAN Learning (IVL), where each port
maintains its own filtering database.
•
Configurable PVID Tagging – This switch allows you to override the default Port VLAN ID (PVID
used in frame tags) and egress status (VLAN-Tagged or Untagged) on each port. (Refer to
“802.1Q VLANs” on page 22-1.)
•
Local VLAN Capable – This switch does not support multiple local bridges (i.e., multiple
Spanning Trees).
•
GMRP – GARP Multicast Registration Protocol (GMRP) allows network devices to register
endstations with multicast groups. This switch does not support GMRP; it uses the Internet Group
Management Protocol (IGMP) to provide automatic multicast filtering.
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
USING THE CLI
show bridge-ext
Use this command to show the configuration for bridge extension commands.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
See “Displaying Basic VLAN Information” on page 22-5 and “Configuring Interface Connections”
on page 17-11 for a description of the displayed items.
Example
Console#show bridge-ext
Max support vlan numbers: 255
Max support vlan ID: 4094
Extended multicast filtering services: No
Static entry individual port: Yes
VLAN learning: IVL
Configurable PVID tagging: Yes
Local VLAN capable: No
Traffic classes: Enabled
Global GVRP status: Disabled
GMRP: Disabled
Console#
Setting the IP Address
An IP address may be used for management access to the switch over your network. By default, the
switch uses DHCP to assign IP settings to VLAN 1 on the switch. If you wish to manually configure
IP settings, you need to change the switch’s user-specified defaults (IP address 0.0.0.0 and netmask
255.0.0.0) to values that are compatible with your network. You may also need to a establish a
default gateway between the switch and management stations that exist on another network
segment.
You can manually configure a specific IP address, or direct the device to obtain an address from a
BOOTP or DHCP server when it is powered on. Valid IP addresses consist of four decimal numbers,
0 to 255, separated by periods. Anything outside this format will not be accepted by the CLI program.
December 2007
© 2007 Foundry Networks, Inc.
5-19
Foundry EdgeIron User Guide
USING THE WEB INTERFACE
Click System, IP. Specify the management interface, IP address and default gateway, then click
Apply.
5-20
•
Management VLAN – This is the only VLAN through which you can gain management access to
the switch. By default, all ports on the switch are members of VLAN 1, so a management station
can be connected to any port on the switch. However, if other VLANs are configured and you
change the Management VLAN, you may lose management access to the switch. In this case,
you should reconnect the management station to a port that is a member of the Management
VLAN.
•
IP Address Mode – Specifies whether IP functionality is enabled via manual configuration
(Static), Dynamic Host Configuration Protocol (DHCP), or Boot Protocol (BOOTP). If
DHCP/BOOTP is enabled, IP will not function until a reply has been received from the server.
Requests will be broadcast periodically by the switch for an IP address. (DHCP/BOOTP values
can include the IP address, subnet mask, and default gateway.)
•
IP Address – Address of the VLAN interface that is allowed management access. Valid IP
addresses consist of four numbers, 0 to 255, separated by periods.
•
Subnet Mask – This mask identifies the host address bits used for routing to specific subnets.
•
Gateway IP Address – IP address of the gateway router between this device and management
stations that exist on other network segments.
•
MAC Address – The MAC address of this switch.
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
USING THE CLI
ip address
Use this command to set the IP address for this device. Use the no form to restore the default IP
address.
Syntax
ip address {ip-address netmask | bootp | dhcp}
no ip address
• ip-address - IP address
• netmask - Network mask for the associated IP subnet. This mask identifies the host address
bits used for routing to specific subnets.
• bootp - Obtains IP address from BOOTP.
• dhcp - Obtains IP address from DHCP.
Default Setting
IP address: 0.0.0.0
Netmask: 255.0.0.0
Command Mode
Interface Configuration (VLAN)
Command Usage
• You must assign an IP address to this device to gain management access over the network. You
can manually configure a specific IP address, or direct the device to obtain an address from a
BOOTP or DHCP server. Valid IP addresses consist of four decimal numbers,
0 to 255, separated by periods. Anything outside this format will not be accepted by the
configuration program.
• If you select the bootp or dhcp option, IP is enabled but will not function until a BOOTP or DHCP
reply has been received. Requests will be broadcast periodically by this device in an effort to learn
its IP address. (BOOTP and DHCP values can include the IP address, default gateway, and
subnet mask).
• You can start broadcasting BOOTP or DHCP requests by entering an ip dhcp restart command,
or by rebooting the switch.
Note: Only one VLAN interface can be assigned an IP address (the default is VLAN 1). This
defines the management VLAN, the only VLAN through which you can gain management
access to the switch. If you assign an IP address to any other VLAN, the new IP address
overrides the original IP address and this becomes the new management VLAN.
Example
In the following example, the device is assigned an address in VLAN 1.
Console(config)#interface vlan 1
Console(config-if)#ip address 192.168.1.5 255.255.255.0
Console(config-if)#
Related Commands
ip dhcp restart (5-25)
December 2007
© 2007 Foundry Networks, Inc.
5-21
Foundry EdgeIron User Guide
ip default-gateway
Use this command to a establish a static route between this device and management stations that
exist on another network segment. Use the no form to remove the static route.
Syntax
ip default-gateway gateway
no ip default-gateway
gateway - IP address of the default gateway
Default Setting
No static route is established.
Command Mode
Global Configuration
Command Usage
A gateway must be defined if the management station is located in a different IP segment.
Example
The following example defines a default gateway for this device:
Console(config)#ip default-gateway 10.1.0.254
Console(config)#
Related Commands
show ip redirects (6-5)
Controlling the Stack
Use the following CLI commands to display the stack unit ID and to renumber the switches in a stack.
There is no Web equivalent.
Note: The following commands are only supported on the 24GS and 48GS.
USING THE CLI
light unit
This command displays the stack unit ID using the switch’s front-panel LEDs.
Syntax
light unit [unit]
unit - Specifies a stack unit for which to light its front-panel LEDs.
Default Setting
None
Command Mode
Normal Exec, Privileged Exec
5-22
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
Command Usage
The unit ID is displayed using the port status LED indicators for ports 1 to 8. When the light unit
command is entered, the LED corresponding to the switch’s ID will flash for about 15 seconds.
Example
Console#light unit 1
Console#
switch renumber
This command resets the switch unit identification numbers in the stack. All stack members are
numbered sequentially starting from the top unit for a non-loop stack, or starting from the Master unit
for a looped stack.
Syntax
switch all renumber
Default Setting
• For non-loop stacking, the top unit is unit 1.
• For loop stacking, the master unit is unit 1.
Command Mode
Global Configuration
Example
This example shows how to renumber all units.
Console#switch all renumber
Console#
Using DHCP/BOOTP
If your network provides DHCP/BOOTP services, you can configure the switch to be dynamically
configured by these services.
USING THE WEB INTERFACE
Click System, IP. Specify the Management VLAN, set the IP Address Mode to DHCP or BOOTP.
Then click Apply to save your changes. The switch will broadcast a request for IP configuration
settings on the next power reset. Otherwise, you can click Restart DHCP to immediately request a
new address.
If you lose your management connection, use a console connection and enter show ip interface to
determine the new switch address.
December 2007
© 2007 Foundry Networks, Inc.
5-23
Foundry EdgeIron User Guide
If the address assigned by DHCP is no longer functioning, you will not be able to renew the IP
settings via the Web interface. You can only restart DHCP service via the Web interface if the current
address is still available.
USING THE CLI
ip address
Use this command to set the IP address for this device. Use the no form to restore the default IP
address.
Syntax
ip address {ip-address netmask | bootp | dhcp}
no ip address
• ip-address - IP address
• netmask - Network mask for the associated IP subnet. This mask identifies the host address
bits used for routing to specific subnets.
• bootp - Obtains IP address from BOOTP.
• dhcp - Obtains IP address from DHCP.
Default Setting
IP address: 0.0.0.0
Netmask: 255.0.0.0
Command Mode
Interface Configuration (VLAN)
Command Usage
• You must assign an IP address to this device to gain management access over the network. You
can manually configure a specific IP address, or direct the device to obtain an address from a
BOOTP or DHCP server. Valid IP addresses consist of four decimal numbers,
0 to 255, separated by periods. Anything outside this format will not be accepted by the
configuration program.
• If you select the bootp or dhcp option, IP is enabled but will not function until a BOOTP or DHCP
reply has been received. Requests will be broadcast periodically by this device in an effort to learn
its IP address. (BOOTP and DHCP values can include the IP address, default gateway, and
subnet mask).
5-24
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
• You can start broadcasting BOOTP or DHCP requests by entering an ip dhcp restart command,
or by rebooting the switch.
• DHCP may lease addresses to clients indefinitely or for a specific period of time. If the address
expires or the switch is moved to another network segment, you will lose management access to
the switch. In this case, you can reboot the switch or submit a client request to restart DHCP
service.
Note: Only one VLAN interface can be assigned an IP address (the default is VLAN 1). This
defines the management VLAN, the only VLAN through which you can gain management
access to the switch. If you assign an IP address to any other VLAN, the new IP address
overrides the original IP address and this becomes the new management VLAN.
Example
In the following example, the device is assigned an address in VLAN 1.
Console(config)#interface vlan 1
Console(config-if)#ip address 192.168.1.5 255.255.255.0
Console(config-if)#
Related Commands
ip dhcp restart (5-25)
ip dhcp restart
Use this command to submit a BOOTP or DCHP client request.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
• DHCP requires the server to reassign the client’s last address if available.
• If the BOOTP or DHCP server has been moved to a different domain, the network portion of the
address provided to the client will be based on this new domain.
Example
In the following example, the device is reassigned the same address.
Console(config)#interface vlan 1
Console(config-if)#ip address dhcp
Console(config-if)#end
Console#ip dhcp restart
Console#show ip interface
IP interface vlan
IP address and netmask: 10.1.0.54 255.255.255.0 on VLAN 1,
and address mode: Dhcp.
Console#
Related Commands
ip address (5-21)
show ip interface (6-4)
December 2007
© 2007 Foundry Networks, Inc.
5-25
Foundry EdgeIron User Guide
Resetting the System
USING THE WEB INTERFACE
Select System, Reset to reboot the switch. When prompted, confirm that you want reset the switch.
USING THE CLI
reload
Use this command to restart the system.
Caution: When the system is restarted, it will always run the Power-On Self-Test. It will also retain
all configuration information stored in non-volatile memory by the copy running-config
startup-config command.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
This command resets the entire system.
Example
This example shows how to reset the switch:
Console#reload
System will be restarted, continue <y/n>? y
Note: When restarting the system, it always runs the Power-On Self-Test.
Web Server Settings
The switch supports both HTTP and HTTPS web servers. The commands in this section allow you to
enable or disable the servers and set TCP port numbers. You can configure the switch to enable the
Secure Hypertext Transfer Protocol (HTTPS) over the Secure Socket Layer (SSL), providing secure
access (i.e., an encrypted connection) to the switch’s Web interface.
Both the HTTP and HTTPS service can be enabled independently on the switch. However, you
cannot configure the HTTP and HTTPS servers to use the same TCP port. If you change the HTTPS
port number, clients attempting to connect to the HTTPS server must specify the port number in the
URL, in this format: https://device:port_number.
5-26
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
Note: If you enable HTTPS, you must indicate this in the URL.
For example: https://device [:port_number]
The following Web browsers and operating systems currently support HTTPS:
Web Browser
Operating System
Internet Explorer 5.0 or later
Windows 98, Windows NT (with service pack 6a),
Windows 2000
Netscape Navigator 6.2 or later
Windows 98, Windows NT (with service pack 6a),
Windows 2000, Windows XP, Solaris 2.6
USING THE WEB INTERFACE
When you start HTTPS, the client and server establish a secure encrypted connection. A padlock
icon should appear in the status bar for Internet Explorer 5.x and Netscape Navigator 6.2 or later.
Click System, HTTPS Settings. Select Enabled for the HTTPS Status and specify the port number,
then click Apply.
•
HTTPS Status – Allows you to enable/disable the HTTPS server on the switch.
(Default: Enabled)
•
HTTPS Port – Specifies the TCP port number used for HTTPS/SSL connection to the switch’s
Web interface. The default is port 443.
USING THE CLI
Use the following commands to configure HTTPS through the CLI.
ip http port
Use this command to specify the TCP port number used by the Web browser interface. Use the no
form to use the default port.
Syntax
ip http port port-number
no ip http port
port-number - The TCP port to be used by the browser interface. (Range: 1-65535)
Default Setting
80
December 2007
© 2007 Foundry Networks, Inc.
5-27
Foundry EdgeIron User Guide
Command Mode
Global Configuration
Example
Console(config)#ip http port 769
Console(config)#
Related Commands
ip http server (5-28)
ip http server
Use this command to allow this device to be monitored or configured from a browser. Use the no
form to disable this function.
Syntax
ip http server
no ip http server
Default Setting
Enabled
Command Mode
Global Configuration
Example
Console(config)#ip http server
Console(config)#
Related Commands
ip http port (5-27)
ip http secure-server
Use this command to enable the secure hypertext transfer protocol (HTTPS) over the Secure Socket
Layer (SSL), providing secure access (i.e., an encrypted connection) to the switch’s Web interface.
Use the no form to disable this function.
Syntax
ip http secure-server
no ip http secure-server
Default Setting
Enabled
Command Mode
Global Configuration
5-28
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
Command Usage
• Both HTTP and HTTPS service can be enabled independently.
• If you enable HTTPS, you must indicate this in the URL:
https://device[port_number]
• When you start HTTPS, the connection is established in this way:
- The client authenticates the server using the server’s digital certificate.
- The client and server negotiate a set of security protocols to use for the connection.
- The client and server generate session keys for encrypting and decrypting data.
• The client and server establish a secure encrypted connection.
A padlock icon should appear in the status bar for Internet Explorer 5.x and Netscape
Navigator 6.2 or later.
• The following Web browsers and operating systems currently support HTTPS:
Web Browser
Operating System
Internet Explorer 5.0 or later
Windows 98,Windows NT (with service pack 6a),
Windows 2000
Netscape Navigator 6.2 or later
Windows 98,Windows NT (with service pack 6a),
Windows 2000, Solaris 2.6
Example
Console(config)#ip http secure-server
Console(config)#
Related Commands
ip http secure-port (5-29)
copy (12-4)
ip http secure-port
Use this command to specify the TCP port number used for HTTPS/SSL connection to the switch’s
Web interface. Use the no form to restore the default port.
Syntax
ip http secure-port port_number
no ip http secure-port
• port_number – The TCP port used for HTTPS/SSL.
(Range: 1-65535)
Default Setting
443
Command Mode
Global Configuration
December 2007
© 2007 Foundry Networks, Inc.
5-29
Foundry EdgeIron User Guide
Command Usage
• You cannot configure the HTTP and HTTPS servers to use the same port.
• If you change the HTTPS port number, clients attempting to connect to the HTTPS server must
specify the port number in the URL, in this format:
https://device:port_number
Example
Console(config)#ip http secure-port 1000
Console(config)#
Related Commands
ip http secure-server (5-28)
Virtual Switch Redundancy Protocol
Note: VSRP is available on devices running release 2.2.4.25 and later.
Virtual Switch Redundancy Protocol (VSRP) is a Foundry proprietary protocol that provides
redundancy and sub-second failover in Layer 2 and Layer 3 mesh topologies. Based on the Foundry
Virtual Router Redundancy Protocol Extended (VRRPE), VSRP provides one or more backups for a
Layer 2 Switch or Layer 3 Switch. If the active Layer 2 Switch or Layer 3 Switch becomes
unavailable, one of the backups takes over as the active device and continues forwarding traffic for
the network.
You can use VSRP for Layer 2, Layer 3, or for both layers. On Layer 3 Switches, Layer 2 and Layer 3
share the same VSRP configuration information. On Layer 2 Switches, VSRP applies only to Layer
2.
VSRP
Master
F
F
VSRP
Aware
Optional link
VSRP
Backup
B B B
F
VSRP
Aware
VSRP
Aware
Hello packets
5-30
© 2007 Foundry Networks, Inc.
March 2007
Basic Configuration
In this example, two Foundry devices are configured as redundant paths for VRID 1. On each of the
devices, a Virtual Router ID (VRID) is configured on a port-based VLAN. Since VSRP is primarily a
Layer 2 redundancy protocol, the VRID applies to the entire VLAN. However, you can selectively
remove individual ports from the VRID if needed.
Following Master election (described below), one of the Foundry devices becomes the Master for the
VRID and sets the state of all the VLAN's ports to Forwarding. The other device is a Backup and sets
all the ports in its VRID VLAN to Blocking.
If a failover occurs, the Backup becomes the new Master and changes all its VRID ports to the
Forwarding state.
Other Foundry devices can use the redundant paths provided by the VSRP devices. In this example,
three Foundry devices use the redundant paths. A Foundry device that is not itself configured for
VSRP but is connected to a Foundry device that is configured for VSRP, is VSRP aware. In this
example, the three Foundry devices connected to the VSRP devices are VSRP aware. A Foundry
device that is VSRP aware can failover its link to the new Master in sub-second time, by changing the
MAC address associated with the redundant path.
When you configure VSRP, make sure each of the non-VSRP Foundry devices connected to the
VSRP devices has a separate link to each of the VSRP devices.
The implementation of VSRP on the EdgeIron range only enables the sending of source address
multicast packets for VSRP aware compatibility purposes. These commands cannot be configured
through the web interface.
USING THE CLI
show vsrp aware
Use this command to display VSRP information.
Syntax
show vsrp aware
Command Mode
Privileged Exec
Example
The following example displays the VSRP status.
Console#show vsrp aware
VSRP aware status: Disabled
Console#
vsrp aware
Enables VSRP packets to be sent. The no form disables the sending of VSRP packets.
Syntax
[no] vsrp aware
December 2007
© 2007 Foundry Networks, Inc.
5-31
Foundry EdgeIron User Guide
Default Setting
Disabled
Command Mode
Global Configuration
Example
The following example enables VSRP and displays the current status.
Console(config)#vsrp aware
Console(config)#end
Console#show vsrp aware
VSRP aware status: Enabled
Console#
5-32
© 2007 Foundry Networks, Inc.
March 2007
Chapter 6
Configuring IP Settings
An IP address may be used for management access to the switch over your network. By default, the
switch uses DHCP to assign IP settings to VLAN 1 on the switch. If you wish to manually configure
IP settings, you need to change the switch’s user-specified defaults (IP address 0.0.0.0 and netmask
255.0.0.0) to values that are compatible with your network. You may also need to a establish a
default gateway between the switch and management stations that exist on another network
segment.
The following table describes the basic IP commands. There is no Web equivalent.
Command
Function
Mode
Page
show arp
Displays the contents of the ARP cache.
PE
6-1
clear arp-cache
Clears the contents of the ARP cache.
PE
6-2
ip address
Sets the IP address for this device
IC
6-2
ip dhcp restart
Submits a BOOTP or DCHP client request
PE
6-3
ip default-gateway
Defines the default gateway through which an in-band
management station can reach this device
GC
6-4
show ip interface
Displays the IP settings for this device
PE
6-4
show ip redirects
Displays the default gateway configured for this device
PE
6-5
ping
Sends ICMP echo request packets to another node on the
network
NE, PE
6-5
show arp
This command displays the contents of the arp cache.
Syntax
show arp
Default Setting
None
Command Mode
Privileged Exec
December 2007
© 2007 Foundry Networks, Inc.
6-1
Foundry EdgeIron User Guide
Example
Console#show arp
IP Address
MAC Address
Type
Interface
--------------- ----------------- --------- ----------192.168.1.23 00-04-80-bd-47-4d
other
1
192.168.1.30 00-00-e8-49-5e-dc
dynamic
1
Total entry : 2
Console#
clear arp-cache
This command clears the contents of the ARP cache.
Syntax
clear arp-cache
Default Setting
None
Command Mode
Privileged Exec
Example
Console#clear arp-cache
This operation will delete all the dynamic entries in ARP Cache.
Are you sure to continue this operation (y/n)?y
Console#
ip address
Use this command to set the IP address for this device. Use the no form to restore the default IP
address.
Syntax
ip address {ip-address netmask | bootp | dhcp}
no ip address
• ip-address - IP address
• netmask - Network mask for the associated IP subnet. This mask identifies the host address
bits used for routing to specific subnets.
• bootp - Obtains IP address from BOOTP.
• dhcp - Obtains IP address from DHCP.
Default Setting
IP address: 0.0.0.0
Netmask: 255.0.0.0
Command Mode
Interface Configuration (VLAN)
6-2
© 2007 Foundry Networks, Inc.
March 2007
Configuring IP Settings
Command Usage
• You must assign an IP address to this device to gain management access over the network. You
can manually configure a specific IP address, or direct the device to obtain an address from a
BOOTP or DHCP server. Valid IP addresses consist of four decimal numbers,
0 to 255, separated by periods. Anything outside this format will not be accepted by the
configuration program.
• If you select the bootp or dhcp option, IP is enabled but will not function until a BOOTP or DHCP
reply has been received. Requests will be broadcast periodically by this device in an effort to learn
its IP address. (BOOTP and DHCP values can include the IP address, default gateway, and
subnet mask).
• You can start broadcasting BOOTP or DHCP requests by entering an ip dhcp restart command,
or by rebooting the switch.
Note:Only one VLAN interface can be assigned an IP address (the default is VLAN 1). This
defines the management VLAN, the only VLAN through which you can gain management
access to the switch. If you assign an IP address to any other VLAN, the new IP address
overrides the original IP address and this becomes the new management VLAN.
Example
In the following example, the device is assigned an address in VLAN 1.
Console(config)#interface vlan 1
Console(config-if)#ip address 192.168.1.5 255.255.255.0
Console(config-if)#
Related Commands
ip dhcp restart (6-3)
ip dhcp restart
Use this command to submit a BOOTP or DCHP client request.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
• DHCP requires the server to reassign the client’s last address if available.
• If the BOOTP or DHCP server has been moved to a different domain, the network portion of the
address provided to the client will be based on this new domain.
December 2007
© 2007 Foundry Networks, Inc.
6-3
Foundry EdgeIron User Guide
Example
In the following example, the device is reassigned the same address.
Console(config)#interface vlan 1
Console(config-if)#ip address dhcp
Console(config-if)#end
Console#ip dhcp restart
Console#show ip interface
IP interface vlan
IP address and netmask: 10.1.0.54 255.255.255.0 on VLAN 1,
and address mode: Dhcp.
Console#
Related Commands
(6-2)
ip default-gateway
Use this command to a establish a static route between this device and management stations that
exist on another network segment. Use the no form to remove the static route.
Syntax
ip default-gateway gateway
no ip default-gateway
gateway - IP address of the default gateway
Default Setting
No static route is established.
Command Mode
Global Configuration
Command Usage
A gateway must be defined if the management station is located in a different IP segment.
Example
The following example defines a default gateway for this device:
Console(config)#ip default-gateway 10.1.0.254
Console(config)#
Related Commands
show ip redirects (6-5)
show ip interface
Use this command to display the settings of an IP interface.
Default Setting
All interfaces
Command Mode
Privileged Exec
6-4
© 2007 Foundry Networks, Inc.
March 2007
Configuring IP Settings
Command Usage
This switch can only be assigned one IP address. This address is used for managing the switch.
Example
Console#show ip interface
IP address and netmask: 10.1.0.54 255.255.255.0 on VLAN 1,
and address mode: User specified.
Console#
Related Commands
show ip redirects (6-5)
show ip redirects
Use this command to show the default gateway configured for this device.
Default Setting
None
Command Mode
Privileged Exec
Example
Console#show ip redirects
ip default gateway 10.1.0.254
Console#
Related Commands
ip default-gateway (6-4)
ping
Use this command to send ICMP echo request packets to another node on the network.
Syntax
ping host [count count] [size size]
• host - IP address or IP alias of the host.
• count - Number of packets to send. (Range: 1-16, default: 5)
• size - Number of bytes in a packet. (Range: 32-512, default: 32)
The actual packet size will be eight bytes larger than the size specified because the switch adds
header information.
Default Setting
This command has no default for the host.
Command Mode
Normal Exec, Privileged Exec
December 2007
© 2007 Foundry Networks, Inc.
6-5
Foundry EdgeIron User Guide
Command Usage
• Use the ping command to see if another site on the network can be reached.
• Following are some results of the ping command:
• Normal response -The normal response occurs in one to ten seconds, depending on network
traffic.
• Destination does not respond - If the host does not respond, a “timeout” appears in ten seconds.
• Destination unreachable - The gateway for this destination indicates that the destination is
unreachable.
• Network or host unreachable - The gateway found no corresponding entry in the route table.
• Press <Esc> to stop pinging.
Example
Console#ping 10.1.0.9
Type ESC to abort.
PING to 10.1.0.9, by 5 32-byte payload ICMP packets, timeout is 5 seconds
response time: 10 ms
response time: 10 ms
response time: 10 ms
response time: 10 ms
response time: 0 ms
Ping statistics for 10.1.0.9:
5 packets transmitted, 5 packets received (100%), 0 packets lost (0%)
Approximate round trip times:
Minimum = 0 ms, Maximum = 10 ms, Average = 8 ms
Console#
Related Commands
interface (17-13)
6-6
© 2007 Foundry Networks, Inc.
March 2007
Chapter 7
Logging Commands
The system can be configured to send debug and error messages to a logging process. This logging
process controls the type of error messages that are stored in switch memory or sent to a remote
syslog server.
The system allows you to specify which levels are logged to RAM or flash memory.
Severe error messages that are logged to flash memory are permanently stored in the switch to
assist in troubleshooting network problems. Up to 4096 log entries can be stored in the flash
memory, with the oldest entries being overwritten first when the available log memory (256 kilobytes)
has been exceeded.
To alert system administrators of problems, the switch can use SMTP (Simple Mail Transfer Protocol)
to send email messages when triggered by logging events of a specified level. The messages are
sent to specified SMTP servers on the network and can be retrieved using POP or IMAP clients.
The CLI commands for this section are briefly described in the table that follows:
Command
Function
Mode
Page
logging on
Controls logging of error messages
GC
7-3
logging history
Limits syslog messages saved to memory based on
severity
GC
7-3
logging host
Adds a syslog server host IP address that will receive
logging messages
GC
7-6
logging facility
Sets the facility type for remote logging of syslog
messages
GC
7-6
logging trap
Limits syslog messages saved to a remote server based
on severity
GC
7-7
clear logging
Clears messages from the logging buffer
PE
7-7
show log
Displays the contents of the log buffer
PE
7-8
show logging
Displays the state of logging
PE
7-9
logging sendmail host
SMTP servers to receive alert messages
GC
7-12
logging sendmail level
Severity threshold used to trigger alert messages
GC
7-12
Event Logging Commands
SMTP
December 2007
© 2007 Foundry Networks, Inc.
7-1
Foundry EdgeIron User Guide
Command
Function
Mode
Page
logging sendmail sourceemail
Email address used for “From” field of alert messages
GC
7-13
logging sendmail
destination-email
Email recipients of alert messages
GC
7-13
logging sendmail
Enables SMTP event handling
GC
7-14
show logging sendmail
Displays SMTP event handler settings
NE, PE
7-14
Enabling System Logs
Using System Logs allows you to configure and limit system messages that are logged to flash or
RAM memory. The default is for levels 0 to 3 to be logged to flash and levels 0 to 7 to be logged to
RAM.
USING THE WEB INTERFACE
Click System, System Logs. Specify System Log Status, then change the level of messages, and
click Apply.
•
System Log Status – Enables/disables the logging of debug or error messages to the logging
process.
•
Flash Level – Limits log messages saved to the switch’s permanent flash memory for all levels
up to the specified level. For example, if level 3 is specified, all messages from level 0 to level 3
will be logged to flash.
•
RAM Level – Limits log messages saved to the switch’s temporary RAM memory for all levels up
to the specified level. For example, if level 7 is specified, all messages from level 0 to level 7 will
be logged to RAM.
Note: The Flash Level must be equal to or less than the RAM Level.
7-2
© 2007 Foundry Networks, Inc.
March 2007
Logging Commands
USING THE CLI
logging on
Use this command to control logging of error messages. This command sends debug or error
messages to a logging process. The no form disables the logging process.
Syntax
[no] logging on
Default Setting
None
Command Mode
Global Configuration
Command Usage
The logging process controls error messages saved to switch memory or sent to remote syslog
servers. You can use the logging history command to control the type of error messages that
are stored in memory. The logging trap command controls the type of error messages that are
sent to specified syslog servers.
Example
Console(config)#logging on
Console(config)#
Related Commands
logging history (7-3)
logging trap (7-7)
clear logging (7-7)
logging history
Use this command to limit syslog messages saved to switch memory based on severity. The no form
returns the logging of syslog messages to the default level.
Syntax
logging history {flash | ram} level
no logging history {flash | ram}
• flash - Event history stored in flash memory (i.e., permanent memory).
• ram - Event history stored in temporary RAM (i.e., memory flushed on power reset).
• level - One of the levels listed below. Messages sent include the selected level up through
level 0.
Level Name
Level*
Description
Syslog Definition
emergencies
0
System unusable
LOG_EMERG
alerts
1
Immediate action needed
LOG_ALERT
critical
2
Critical conditions (e.g., memory
allocation, or free memory error resource exhausted)
LOG_CRIT
December 2007
© 2007 Foundry Networks, Inc.
7-3
Foundry EdgeIron User Guide
Level Name
Level*
Description
Syslog Definition
errors
3
Error conditions (e.g., invalid input,
default used)
LOG_ERR
warnings
4
Warning conditions (e.g., return false,
unexpected return)
LOG_WARNING
notifications
5
Normal but significant condition, such
as cold start
LOG_NOTICE
informational
6
Informational messages only
LOG_INFO
debugging
7
Debugging messages
LOG_DEBUG
* There are only Level 2, 5 and 6 error messages for the current firmware release.
Default Setting
Flash: errors (level 3 - 0)
RAM: warnings (level 7 - 0)
Command Mode
Global Configuration
Command Usage
The message level specified for flash memory must be a higher priority (i.e., numerically lower)
than that specified for RAM.
Example
Console(config)#logging history ram 0
Console(config)#
7-4
© 2007 Foundry Networks, Inc.
March 2007
Logging Commands
Remote Logs Configuration
Remote Logs allows you to configure the logging of messages that are sent to syslog servers. You
can also limit the error messages sent to only those messages of a specified level.
USING THE WEB INTERFACE
Click System, Remote Logs. To add an IP address to the Host IP List, type the new IP address in the
Host IP Address box, and then click Add IP. To delete an IP address, click the entry in the Host IP
List, and then click Remove.
•
Remote Log Status – Enables/disables the logging of debug or error messages to the remote
logging process. (Default: enabled)
•
Logging Facility – Sets the facility type for remote logging of syslog messages. There are eight
facility types specified by values of 16 to 23. The facility type is used by the syslog server to
dispatch log messages to an appropriate service. (Default: 23)
•
Logging Trap – Limits log messages that are sent to the remote syslog server for all levels up to
the specified level. For example, if level 3 is specified, all messages from level 0 to level 3 will be
sent to the remote server. (Default: 7)
•
Host IP List – Displays the list of remote server IP addresses that receive the syslog messages.
The maximum number of host IP addresses allowed is five.
•
Host IP Address – Specifies a new server IP address to add to the Host IP List.
December 2007
© 2007 Foundry Networks, Inc.
7-5
Foundry EdgeIron User Guide
USING THE CLI
logging host
Use this command to add a syslog server host IP address that will receive logging messages. Use
the no form to remove a syslog server host.
Syntax
[no] logging host host_ip_address
host_ip_address - The IP address of a syslog server.
Default Setting
None
Command Mode
Global Configuration
Command Usage
• By using this command more than once you can build up a list of host IP addresses.
• The maximum number of host IP addresses allowed is five.
Example
Console(config)#logging host 10.1.0.3
Console(config)#
logging facility
Use this command to set the facility type for remote logging of syslog messages. Use the no form to
return the type to the default.
Syntax
[no] logging facility type
type - A number that indicates the facility used by the syslog server to dispatch log messages
to an appropriate service. (Range: 16-23)
Default Setting
23
Command Mode
Global Configuration
Example
Console(config)#logging facility 19
Console(config)#
7-6
© 2007 Foundry Networks, Inc.
March 2007
Logging Commands
logging trap
Use this command to limit syslog messages saved to a remote server based on severity. Use the no
form to return the remote logging of syslog messages to the default level.
Syntax
logging trap level
no logging trap
level - One of the levels listed below. Messages sent include the selected level up through
level 0.
Level Name
Level*
Description
Syslog Definition
emergencies
0
System unusable
LOG_EMERG
alerts
1
Immediate action needed
LOG_ALERT
critical
2
Critical conditions (e.g., memory
allocation, or free memory error resource exhausted)
LOG_CRIT
errors
3
Error conditions (e.g., invalid input,
default used)
LOG_ERR
warnings
4
Warning conditions (e.g., return false,
unexpected return)
LOG_WARNING
notifications
5
Normal but significant condition, such
as cold start
LOG_NOTICE
informational
6
Informational messages only
LOG_INFO
debugging
7
Debugging messages
LOG_DEBUG
* There are only Level 2, 5 and 6 error messages for the current firmware release.
Default Setting
Level 3 - 0
Command Mode
Global Configuration
Example
Console(config)#logging trap 4
Console(config)#
clear logging
Use this command to clear messages from the log buffer.
Syntax
clear logging [flash | ram]
• flash - Event history stored in flash memory (i.e., permanent memory).
• ram - Event history stored in temporary RAM (i.e., memory flushed on power reset).
Default Setting
None
December 2007
© 2007 Foundry Networks, Inc.
7-7
Foundry EdgeIron User Guide
Command Mode
Privileged Exec
Example
Console#clear logging
Console#
Related Commands
show logging (7-9)
Displaying System Logs
USING THE WEB INTERFACE
The Logs page allows you to scroll through the logged system and event messages. The switch can
store up to 2048 log entries in temporary random access memory (RAM; i.e., memory flushed on
power reset) and up to 4096 entries in permanent flash memory.
To display system logs click System, Logs.
USING THE CLI
show log
This command displays the system and event messages stored in memory.
Syntax
show log {flash | ram} [login]
• flash - Event history stored in flash memory (i.e., permanent memory).
• ram - Event history stored in temporary RAM (i.e., memory flushed on power reset).
• login - Shows the login record only.
Default Setting
None
Command Mode
Privileged Exec
7-8
© 2007 Foundry Networks, Inc.
March 2007
Logging Commands
Command Usage
This command shows the system and event messages stored in memory, including the time
stamp, message level, program module, function, and event number.
Example
The following example shows sample messages stored in RAM.
Console#show log ram
[5] 00:01:06 2001-01-01
"STA root change notification."
level: 6, module: 6, function: 1, and event no.: 1
[4] 00:01:00 2001-01-01
"STA root change notification."
level: 6, module: 6, function: 1, and event no.: 1
[3] 00:00:54 2001-01-01
"STA root change notification."
level: 6, module: 6, function: 1, and event no.: 1
[2] 00:00:50 2001-01-01
"STA topology change notification."
level: 6, module: 6, function: 1, and event no.: 1
[1] 00:00:48 2001-01-01
"VLAN 1 link-up notification."
level: 6, module: 6, function: 1, and event no.: 1
Console#show log ram login
"User(guest/Console) (0.0.0.0) (Dec 15 09:36:24 2003)"
"User(admin/Console) (0.0.0.0) (Dec 15 09:36:01 2003)"#
Console#
show logging
Use this command to display the logging configuration for system and event messages. Type "show
logging" followed by the type of logging information required.
Syntax
show logging {sendmail | flash | ram | trap}
• sendmail - Displays settings for the SMTP event handler.
• flash - Event history stored in flash memory (i.e., permanent memory).
• ram - Event history stored in temporary RAM (i.e., memory flushed on power reset).
• trap - Messages sent to remote syslog servers.
Default Setting
None
Command Mode
Privileged Exec
Console#show logging sendmail
SMTP servers
----------------------------------------------Active SMTP server: 0.0.0.0
SMTP minimum severity level: 7
SMTP destination email addresses
----------------------------------------------SMTP source email address:
SMTP status: Enable
Console#
December 2007
© 2007 Foundry Networks, Inc.
7-9
Foundry EdgeIron User Guide
Console#show logging flash
Syslog logging: Disable
History logging in FLASH: level errors
Console#show logging trap
Syslog logging: Enable
REMOTELOG status: enable
REMOTELOG facility type: local use 3
REMOTELOG level type: Warning conditions
REMOTELOG server ip address: 10.1.0.3
REMOTELOG server ip address: 10.1.0.4
REMOTELOG server ip address: 0.0.0.0
REMOTELOG server ip address: 0.0.0.0
REMOTELOG server ip address: 0.0.0.0
Console#show logging ram
Syslog logging: Enable
History logging in RAM: level debugging
[3] 0:0:41 1/1/1
"VLAN 1 link-up notification."
level: 6, module: 6, function: 1, and event
[2] 0:0:41 1/1/1
"STP topology change notification."
level: 6, module: 6, function: 1, and event
[1] 0:0:12 1/1/1
"Unit 1, Port 5 link-up notification."
level: 6, module: 6, function: 1, and event
[0] 0:0:11 1/1/1
"System coldStart notification."
level: 6, module: 6, function: 1, and event
Console#
no.: 1
no.: 1
no.: 1
no.: 1
Sending Simple Mail Transfer Protocol Alerts
Note: SMTP is not supported for the EIF2402CF and EIF4802CF. SMTP is supported in all other
EdgeIron switches for software version 2.2.6.4 and later versions.
To alert system administrators of problems, the switch can use SMTP (Simple Mail Transfer Protocol)
to send email messages when triggered by logging events of a specified level. The messages are
sent to specified SMTP servers on the network and can be retrieved using POP or IMAP clients.
7-10
© 2007 Foundry Networks, Inc.
March 2007
Logging Commands
USING THE WEB INTERFACE
Click System, Log, SMTP. Enable SMTP, specify a source email address, and select the minimum
severity level. To add an IP address to the SMTP Server List, type the new IP address in the SMTP
Server text box and then click Add. To delete an IP address, click the entry in the SMTP Server List
and then click Remove. Specify up to five email addresses to receive the alert messages, and then
click Apply.
•
Admin Status – Enables/disables the SMTP function. (Default: Disabled)
•
Email Source Address – Sets the email address used for the “From” field in alert messages. You
may use a symbolic email address that identifies the switch, or the address of an administrator
responsible for the switch.
•
Severity – Sets the syslog severity threshold level (see table “Syslog Definition” on page 7-3)
used to trigger alert messages. All events at this level or higher will be sent to the configured email
recipients. For example, using Level 7 will report all events from level 7 to level 0.
(Default: Level 7)
•
SMTP Server List – Specifies a list of up to three recipient SMTP servers. The switch attempts
to connect to the other listed servers if the first fails. Use the New SMTP Server text field and the
Add/Remove buttons to configure the list.
•
Email Destination Address List – Specifies the email recipients of alert messages. You can
specify up to five recipients. Use the New Email Destination Address text field and the
Add/Remove buttons to configure the list.
December 2007
© 2007 Foundry Networks, Inc.
7-11
Foundry EdgeIron User Guide
logging sendmail host
This command specifies SMTP servers that will be sent alert messages. Use the no form to remove
an SMTP server.
Syntax
[no] logging sendmail host ip_address
ip_address - IP address of an SMTP server that will be sent alert messages for event
handling.
Default Setting
None
Command Mode
Global Configuration
Command Usage
• You can specify up to three SMTP servers for event handing. However, you must enter a separate
command to specify each server.
• To send email alerts, the switch first opens a connection, sends all the email alerts waiting in the
queue one by one, and finally closes the connection.
• To open a connection, the switch first selects the server that successfully sent mail during the last
connection, or the first server configured by this command. If it fails to send mail, the switch
selects the next server in the list and tries to send mail again. If it still fails, the system will repeat
the process at a periodic interval. (A trap will be triggered if the switch cannot successfully open
a connection.)
Example
Console(config)#logging sendmail host 192.168.1.19
Console(config)#
logging sendmail level
This command sets the severity threshold used to trigger alert messages.
Syntax
logging sendmail level level
level - One of the system message levels (see “logging history” on page 7-3). Messages sent
include the selected level down to level 0. (Range: 0-7; Default: 7)
Default Setting
Level 7
Command Mode
Global Configuration
Command Usage
The specified level indicates an event threshold. All events at this level or higher will be sent to
the configured email recipients. (For example, using Level 7 will report all events from level 7 to
level 0.)
7-12
© 2007 Foundry Networks, Inc.
March 2007
Logging Commands
Example
This example will send email alerts for system errors from level 3 through 0.
Console(config)#logging sendmail level 3
Console(config)#
logging sendmail source-email
This command sets the email address used for the “From” field in alert messages.
Syntax
logging sendmail source-email email-address
email-address - The source email address used in alert messages. (Range: 1-41 characters)
Default Setting
None
Command Mode
Global Configuration
Command Usage
You may use an symbolic email address that identifies the switch, or the address of an
administrator responsible for the switch.
Example
This example will send email alerts for system errors from level 3 through 0.
Console(config)#logging sendmail source-email [email protected]
Console(config)#
logging sendmail destination-email
This command specifies the email recipients of alert messages. Use the no form to remove a
recipient.
Syntax
[no] logging sendmail destination-email email-address
email-address - The source email address used in alert messages. (Range: 1-41 characters)
Default Setting
None
Command Mode
Global Configuration
Command Usage
You can specify up to five recipients for alert messages. However, you must enter a separate
command to specify each recipient.
December 2007
© 2007 Foundry Networks, Inc.
7-13
Foundry EdgeIron User Guide
Example
Console(config)#logging sendmail destination-email [email protected]
Console(config)#
logging sendmail
This command enables SMTP event handling. Use the no form to disable this function.
Syntax
[no] logging sendmail
Default Setting
Disabled
Command Mode
Global Configuration
Example
Console(config)#logging sendmail
Console(config)#
show logging sendmail
This command displays the settings for the SMTP event handler.
Command Mode
Normal Exec, Privileged Exec
Example
Console#show logging sendmail
SMTP servers
----------------------------------------------Active SMTP server: 0.0.0.0
SMTP minimum severity level: 7
SMTP destination email addresses
----------------------------------------------ted@this-company.com
SMTP source email address: [email protected]
SMTP status: Enable
Console#
7-14
© 2007 Foundry Networks, Inc.
March 2007
Chapter 8
System Clock Commands
Simple Network Time Protocol (SNTP) allows the switch to set its internal clock based on periodic
updates from a time server (SNTP or NTP). Maintaining an accurate time on the switch enables the
system log to record meaningful dates and times for event entries. You can also manually set the
clock using the CLI. (See “calendar set” on page 8-6.) If the clock is not set, the switch will only
record the time from the factory default set at the last bootup.
This switch acts as an SNTP client in two modes:
Unicast – The switch periodically sends a request for a time update to a configured time server. You
can configure up to three time server IP addresses. The switch will attempt to poll each server in the
configured sequence.
Broadcast – The switch sets its clock from a time server in the same subnet that broadcasts time
updates. If there is more than one SNTP server, the switch accepts the first broadcast it detects and
ignores broadcasts from other servers.
The CLI commands for this section are briefly described in the table that follows:
Command
Function
Mode
Page
sntp client
Accepts time from specified time servers
GC
8-2
sntp server
Specifies one or more time servers
GC
8-3
sntp poll
Sets the interval at which the client polls for time
GC
8-4
show sntp
Shows current SNTP configuration settings
NE, PE
8-4
clock timezone
Sets the time zone for the switch’s internal clock
GC
8-5
calendar set
Set the system date and time
PE
8-6
show calendar
Display the current date and time setting
NE, PE
8-6
SNTP
December 2007
© 2007 Foundry Networks, Inc.
8-1
Foundry EdgeIron User Guide
Configuring SNTP
You can configure the switch to send time synchronization requests to specific time servers (i.e.,
client mode), update its clock based on broadcasts from time servers, or use both methods. When
both methods are enabled, the switch will update its clock using information broadcast from time
servers, but will query the specified server(s) if a broadcast is not received within the polling interval.
USING THE WEB INTERFACE
Select SNTP, Configuration. Modify any of the required parameters, and click Apply.
•
SNTP Client – Configures the switch to operate as an SNTP unicast client. This mode requires
at least one time server to be specified in the SNTP Server field.
•
SNTP Polling Interval – Sets the interval between sending requests for a time update from a time
server when set to SNTP Client mode. (Range: 16-16284 seconds; Default: 16 seconds)
•
SNTP Server – In unicast mode, sets the IP address for up to three time servers. The switch
attempts to update the time from the first server, if this fails it attempts an update from the next
server in the sequence.
USING THE CLI
Use the commands in this section to configure SNTP parameters from the CLI.
sntp client
This command enables SNTP client requests for time synchronization from NTP or SNTP time
servers specified with the sntp servers command. Use the no form to disable SNTP client requests.
Syntax
[no] sntp client
Default Setting
Disabled
Command Mode
Global Configuration
Command Usage
•
8-2
The time acquired from time servers is used to record accurate dates and times for log events.
Without SNTP, the switch only records the time starting from the factory default set at the last
bootup (i.e., 00:00:00, Jan. 1, 2001).
© 2007 Foundry Networks, Inc.
March 2007
System Clock Commands
•
This command enables client time requests to time servers specified via the sntp servers
command. It issues time synchronization requests based on the interval set via the sntp poll
command.
•
The SNTP time query method is set to client mode when the first sntp client command is issued.
Example
Console(config)#sntp server 10.1.0.19
Console(config)#sntp poll 60
Console(config)#sntp client
Console(config)#end
Console#show sntp
Current time: Dec 23 02:52:44 2002
Poll interval: 60
Current mode: unicast
Console#
Related Commands
sntp server (8-3)
sntp poll (8-4)
show sntp (8-4)
sntp server
This command sets the IP address of the servers to which SNTP time requests are issued. Use the
this command with no arguments to clear all time servers from the current list.
Syntax
sntp server [ip1 [ip2 [ip3]]]
ip - IP address of an time server (NTP or SNTP).
(Range: 1 - 3 addresses)
Default Setting
None
Command Mode
Global Configuration
Command Usage
This command specifies time servers from which the switch will poll for time updates when set to
SNTP client mode. The client will poll the time servers in the order specified until a response is
received. It issues time synchronization requests based on the interval set via the sntp poll
command.
Example
Console(config)#sntp server 10.1.0.19
Console(config)#
Related Commands
sntp client (8-2)
sntp poll (8-4)
show sntp (8-4)
December 2007
© 2007 Foundry Networks, Inc.
8-3
Foundry EdgeIron User Guide
sntp poll
This command sets the interval between sending time requests when the switch is set to SNTP
client mode. Use the no form to restore to the default.
Syntax
sntp poll seconds
no sntp poll
seconds - Interval between time requests. (Range: 16-16384 seconds)
Default Setting
16 seconds
Command Mode
Global Configuration
Command Usage
This command is only applicable when the switch is set to SNTP client mode.
Example
Console(config)#sntp poll 60
Console(config)#
Related Commands
sntp client (8-2)
show sntp
This command displays the current time and configuration settings for the SNTP client, and indicates
whether or not the local time has been properly updated.
Command Mode
Normal Exec, Privileged Exec
Command Usage
This command displays the current time, the poll interval used for sending time synchronization
requests (when the switch is set to SNTP client mode), and the current SNTP mode (i.e., client
or broadcast).
Example
Console#show sntp
Current time: Dec 23 05:13:28 2002
Poll interval: 16
Current mode: unicast
Console#
Setting the Time Zone
SNTP uses Coordinated Universal Time (or UTC, formerly Greenwich Mean Time, or GMT) based
on the time at the Earth’s prime meridian, zero degrees longitude. To display a time corresponding to
your local time, you must indicate the number of hours and minutes your time zone is east (before) or
west (after) of UTC.
8-4
© 2007 Foundry Networks, Inc.
March 2007
System Clock Commands
USING THE WEB INTERFACE
Select SNTP, Clock Time Zone. Set the offset for your time zone relative to the UTC, and click Apply.
• Current Time – Displays the current time.
• Name – Assigns a name to the time zone.
• Hours (0-23) – The number of hours before/after UTC.
• Minutes (0-59) – The number of minutes before/after UTC.
• Direction – Configures the time zone to be before (east) or after (west) UTC.
USING THE CLI
Use the commands in this section to configure time and date parameters from the CLI.
clock timezone
This command sets the time zone for the switch’s internal clock.
Syntax
clock timezone name hour hours minute minutes {before-utc | after-utc}
• name - Name of timezone, usually an acronym. (Range: 1-29 characters)
• hours - Number of hours before/after UTC. (Range: 1-12 hours)
• minutes - Number of minutes before/after UTC. (Range: 0-59 minutes)
• before-utc - Sets the local time zone before (east) of UTC.
• after-utc - Sets the local time zone after (west) of UTC.
Default Setting
None
Command Mode
Global Configuration
Command Usage
This command sets the local time zone relative to the Coordinated Universal Time (UTC, formerly
Greenwich Mean Time or GMT), based on the earth’s prime meridian, zero degrees longitude. To
display a time corresponding to your local time, you must indicate the number of hours and
minutes your time zone is east (before) or west (after) of UTC.
December 2007
© 2007 Foundry Networks, Inc.
8-5
Foundry EdgeIron User Guide
Example
Console(config)#clock timezone Japan hours 8 minute 0 after-UTC
Console(config)#
Related Commands
show sntp (8-4)
calendar set
This command sets the system clock. It may be used if there is no time server on your network, or if
you have not configured the switch to receive signals from a time server.
Syntax
calendar set hour min sec {day month year | month day year}
• hour - Hour in 24-hour format. (Range: 0 - 23)
• min - Minute. (Range: 0 - 59)
• sec - Second. (Range: 0 - 59)
• month - january | february | march | april | may | june | july | august | september | october
| november | december
• day - Day of month. (Range: 1 - 31)
• year - Year (4-digit). (Range: 2001 - 2101)
Default Setting
None
Command Mode
Privileged Exec
Example
This example shows how to set the system clock to 15:12:34, February 1st, 2004.
Console#calendar set 15 12 34 February 1 2004
Console#
show calendar
This command displays the system clock.
Default Setting
None
Command Mode
Normal Exec, Privileged Exec
Example
Console#show calendar
15 12 44 February 1 2004
Console#
8-6
© 2007 Foundry Networks, Inc.
March 2007
Chapter 9
Management Authentication
You can configure the switch to authenticate users logging into the system for management access
using local or authentication-server methods.
Remote Authentication Dial-in User Service (RADIUS) and Terminal Access Controller Access
Control System Plus (TACACS+) are logon authentication protocols that use software running on a
central server to control access to RADIUS-aware or TACACS+-aware devices on the network. An
authentication server contains a database of multiple user name/password pairs with associated
privilege levels for each user that requires management access to a switch.
You can configure the switch to enable the Secure Hypertext Transfer Protocol (HTTPS) over the
Secure Socket Layer (SSL), providing secure access (i.e., an encrypted connection) to the switch’s
Web interface.
Both the HTTP and HTTPS service can be enabled independently on the switch. However, you
cannot configure the HTTP and HTTPS servers to use the same TCP port. If you change the HTTPS
port number, clients attempting to connect to the HTTPS server must specify the port number in the
URL, in this format: https://device:port_number.
The CLI commands for this section are briefly described in the table that follows:
Command
Function
Mode
Page
username
Sets user name authentication at login
GC
9-3
enable password
Sets a password to control access to various privilege
levels
GC
9-4
authentication login
Defines logon authentication method and precedence
GC
9-7
authentication enable
Defines the authentication method and precedence
for command mode change
GC
9-8
radius-server host
Specifies the RADIUS server
GC
9-9
radius-server port
Sets the RADIUS server network port
GC
9-9
radius-server key
Sets the RADIUS encryption key
GC
9-9
radius-server retransmit
Sets the number of retries
GC
9-10
Authentication Method
RADIUS Client
December 2007
© 2007 Foundry Networks, Inc.
9-1
Foundry EdgeIron User Guide
Command
Function
Mode
Page
radius-server timeout
Sets the interval between sending authentication
requests
GC
9-10
show radius-server
Shows the current RADIUS settings
PE
9-11
tacacs-server host
Specifies the TACACS+ server
GC
9-11
tacacs-server port
Specifies the TACACS+ server network port
GC
9-12
tacacs-server key
Sets the TACACS+ encryption key
GC
9-12
show tacacs-server
Shows the current TACACS+ settings
GC
9-12
aaa group server
Groups different TACACS+ servers into distinct lists
and methods
GC
9-13
server
Assigns a TACACS+ server to the server group
TSGC1
9-14
aaa accounting exec
Enables TACACS+ accounting of requested services
GC
9-15
aaa accounting update
Allows periodic interim accounting records to be sent
to the accounting server
GC
9-15
accounting exec
Applies the accounting method to a Telnet or console
interface
LC
9-16
show accounting
Displays the current accounting settings and statistics PE
9-16
aaa authorization exec
Restricts user access to the network
GC
9-17
authorization exec
Applies the authorization method to a Telnet or
console interface
LC
9-18
show authorization
Displays the current authorization settings
PE
9-18
TACACS+ Client
TACACS+ AAA
1 TACACS+ server group configuration mode.
Configuring the Logon Password.
The guest only has read access for most configuration parameters. However, the administrator has
write access for parameters governing the onboard agent. You should therefore assign a new
administrator password as soon as possible, and store it in a safe place. (If for some reason your
password is lost, you can reload the factory defaults file to restore the default passwords as
described in “Troubleshooting Chart” on page C-1.)
The default guest name is “guest” with the password “guest.” The default administrator name is
“admin” with the password “admin.” Note that user names can only be assigned via the CLI.
9-2
© 2007 Foundry Networks, Inc.
March 2007
Management Authentication
USING THE WEB INTERFACE
Click System, Passwords. To change the password for the current user, enter the old password, then
enter the new password, confirm it by entering it again, then click Apply.
• Password – Specifies the user password.
(Range: 0-8 characters plain text, case sensitive)
Note: User Names and Access Levels may only be set through the CLI.
USING THE CLI
Use the following commands to configure a username, password and access levels:
username
Use this command to require user name authentication at login. Use the no form to remove a user
name.
Syntax
username name {access-level level | nopassword | password {0 | 7} password}
no username name
• name - The name of the user.
Up to 8 characters, case sensitive.
Maximum number of users: 16
• access-level level - Specifies the user level.
• The device has two predefined privilege levels: 0: Normal Exec, 15: Privileged Exec.
• nopassword - No password is required for this user to log in.
• {0 | 7} - 0 means plain password, 7 means encrypted password.
• password password - The authentication password for the user. (Maximum length: 8
characters plain text, 32 encrypted, case sensitive)
Default Setting
• The default access level is Normal Exec.
• The factory defaults for the user names and passwords are:
username
access-level
password
guest
admin
0
15
guest
admin
December 2007
© 2007 Foundry Networks, Inc.
9-3
Foundry EdgeIron User Guide
Command Mode
Global Configuration
Command Usage
The encrypted password is required for compatibility with legacy password settings (i.e., plain text
or encrypted) when reading the configuration file during system bootup or when downloading the
configuration file from a TFTP server. There is no need for you to manually configure encrypted
passwords.
Example
This example shows how the set the access level and password for a user.
Console(config)#username bob access-level 15
Console(config)#username bob password 0 smith
Console(config)#
enable password
After initially logging onto the system, you should set the administrator (Privileged Exec) and guest
(Normal Exec) passwords. Remember to record them in a safe place. Use the enable password
command to set the password for access to the Privileged Exec level from the Normal Exec level.
Use the no form to reset the default password.
Syntax
enable password [level level] {0 | 7} password
no enable password [level level]
• level level - Level for which the password applies.
• The device has two predefined privilege levels: 0: Normal Exec, 15: Privileged Exec. Only level
15 is valid for this command.
• {0 | 7} - 0 means plain password, 7 means encrypted password.
• password - password for this privilege level.
Default Setting
This default password is “super”
Command Mode
Global Configuration
Command Usage
The encrypted password is required for compatibility with legacy password settings (i.e., plain text
or encrypted) when reading the configuration file during system bootup or when downloading the
configuration file from a TFTP server. There is no need for you to manually configure encrypted
passwords.
Example
Console(config)#enable password level 15 0 admin
Console(config)#
9-4
© 2007 Foundry Networks, Inc.
March 2007
Management Authentication
Configuring RADIUS/TACACS Logon Authentication
Note: TACACS+ AAA is only supported in version 2.2.6.x.
You can configure this switch to authenticate users logging into the system for management access
using local, RADIUS, or TACACS+ authentication methods.
RADIUS and TACACS+ are logon authentication protocols that use software running on a central
server to control access to RADIUS-aware or TACACS+-aware devices on the network. An
authentication server contains a database of multiple user name/password pairs with associated
privilege levels for each user that requires management access to a switch.
Like RADIUS, Terminal Access Controller Access Control System Plus (TACACS+) is a system that
uses a central server to control authentication for access to switches on the network.
RADIUS uses UDP while TACACS+ uses TCP. UDP only offers best effort delivery, while TCP offers
a connection-oriented transport. Also, note that RADIUS encrypts only the password in the accessrequest packet from the client to the server, while TACACS+ encrypts the entire body of the packet.
Command Usage
• By default, management access is always checked against the authentication database stored
on the local switch. If a remote authentication server is used, you must specify the authentication
sequence and the corresponding parameters for the remote authentication protocol.
•
RADIUS and TACACS+ logon authentication control management access via the console port,
Web browser, or Telnet. These access options must be configured on the authentication server.
•
RADIUS and TACACS+ logon authentication assign a specific privilege level for each user
name/password pair. The user name, password, and privilege level must be configured on the
authentication server.
•
You can specify up to three authentication methods for any user to indicate the authentication
sequence. For example, if you select (1) RADIUS, (2) TACACS and (3) Local, the user name and
password on the RADIUS server is verified first. If the RADIUS server is not available, then
authentication is attempted using the TACACS+ server, and finally the local user name and
password is checked.
December 2007
© 2007 Foundry Networks, Inc.
9-5
Foundry EdgeIron User Guide
USING THE WEB INTERFACE
To configure local or remote authentication preferences click System, Authentication Settings,
specify the authentication sequence (i.e., one to three methods), fill in the parameters for RADIUS or
TACACS+ authentication if selected, and click Apply.
• Authentication – Select the authentication, or authentication sequence required:
- RADIUS – User authentication is performed using a RADIUS server only.
- TACACS – User authentication is performed using a TACACS+ server only.
- Local – User authentication is performed only locally by the switch.
- [authentication sequence] – User authentication is performed by up to three authentication
methods in the indicated sequence.
• RADIUS Settings
- Server IP Address – Address of the RADIUS server.
(Default: 10.1.0.1)
- Server Port Number – Network (UDP) port of the RADIUS server used for authentication
messages.
(Range: 1-65535; Default: 1812)
- Secret Text String – Encryption key used to authenticate logon access for client. Do not use
blank spaces in the string.
(Maximum length: 20 characters)
- Number of Server Transmits – Number of times the switch will try to authenticate logon
access via the RADIUS server.
(Range: 1-30; Default: 2)
- Timeout for a reply (secs) – The number of seconds the switch waits for a reply from the
RADIUS server before it resends the request. (Range: 1-65535; Default: 5)
• TACACS+ Settings
- Server IP Address – Address of the TACACS+ server.
(Default: 10.1.0.1)
- Server Port Number – Network (TCP) port of TACACS+ server used for authentication
messages.
(Range: 1-65535; Default: 1812)
9-6
© 2007 Foundry Networks, Inc.
March 2007
Management Authentication
- Secret Text String – Encryption key used to authenticate logon access for client. Do not use
blank spaces in the string.
(Maximum length: 20 characters)
Note: The local switch user database has to be set up by manually entering user names and
passwords using the CLI.
USING THE CLI
Use the following commands to configure RADISU/TACACS+ authentication through the CLI.
authentication login
Use this command to define the login authentication method and precedence. Use the no form to
restore the default.
Syntax
authentication login {[local] [radius] [tacacs]}
no authentication login
• local - Use local authentication.
• radius - Use RADIUS server authentication.
• tacacs - Use TACACS+ server authentication.
Default Setting
Local only
Command Mode
Global Configuration
Command Usage
• RADIUS uses UDP while TACACS+ uses TCP. UDP only offers best effort delivery, while TCP
offers a connection-oriented transport. Also, note that RADIUS encrypts only the password in the
access-request packet from the client to the server.
• RADIUS and TACACS+ logon authentication can control management access via the console
port, a Web browser, or Telnet. These access options must be configured on the authentication
server.
• RADIUS and TACACS+ logon authentication assigns a specific privilege level for each user name
and password pair. The user name, password, and privilege level must be configured on the
authentication server.
• You can specify three authentication methods in a single command to indicate the authentication
sequence. For example, if you enter “authentication login radius tacacs local,” the user name
and password on the RADIUS server is verified first. If the RADIUS server is not available, then
authentication is attempted on the TACACS+ server. If the TACACS+ server is not available, the
local user name and password is checked.
Example
Console(config)#authentication login radius local
Console(config)#
December 2007
© 2007 Foundry Networks, Inc.
9-7
Foundry EdgeIron User Guide
Related Commands
username (9-3) - for setting local user names and passwords
authentication enable
This command defines the authentication method and precedence to use when changing from Exec
command mode to Privileged Exec command mode with the enable command (see “enable” on
page 3-8). Use the no form to restore the default.
Syntax
authentication enable {[local] [radius] [tacacs]}
no authentication enable
• local - Use local password only.
• radius - Use RADIUS server password only.
• tacacs - Use TACACS+ server password.
Default Setting
Local
Command Mode
Global Configuration
Command Usage
• RADIUS uses UDP while TACACS+ uses TCP. UDP only offers best effort delivery, while TCP
offers a connection-oriented transport. Also, note that RADIUS encrypts only the password in the
access-request packet from the client to the server, while TACACS+ encrypts the entire body of
the packet.
• RADIUS and TACACS+ logon authentication assigns a specific privilege level for each user name
and password pair. The user name, password, and privilege level must be configured on the
authentication server.
• You can specify three authentication methods in a single command to indicate the authentication
sequence. For example, if you enter “authentication enable radius tacacs local,” the user name
and password on the RADIUS server is verified first. If the RADIUS server is not available, then
authentication is attempted on the TACACS+ server. If the TACACS+ server is not available, the
local user name and password is checked.
Example
Console(config)#authentication enable radius
Console(config)#
Related Commands
enable password (9-4)
9-8
© 2007 Foundry Networks, Inc.
March 2007
Management Authentication
radius-server host
Use this command to specify the RADIUS server. Use the no form to restore the default.
Syntax
radius-server host host_ip_address
no radius-server host
host_ip_address - IP address of a RADIUS server.
Default Setting
10.1.0.1
Command Mode
Global Configuration
Example
Console(config)#radius-server host 192.168.1.25
Console(config)#
radius-server port
Use this command to set the RADIUS server network port. Use the no form to restore the default.
Syntax
radius-server port port_number
no radius-server port
port_number - RADIUS server UDP port used for authentication messages.
(Range: 1-65535)
Default Setting
1812
Command Mode
Global Configuration
Example
Console(config)#radius-server port 181
Console(config)#
radius-server key
Use this command to set the RADIUS encryption key. Use the no form to restore the default.
Syntax
radius-server key key_string
no radius-server key
key_string - Encryption key used to authenticate logon access for client. Do not use blank
spaces in the string.
(Maximum length: 20 characters)
December 2007
© 2007 Foundry Networks, Inc.
9-9
Foundry EdgeIron User Guide
Default Setting
None
Command Mode
Global Configuration
Example
Console(config)#radius-server key green
Console(config)#
radius-server retransmit
Use this command to set the number of retries. Use the no form to restore the default.
Syntax
radius-server retransmit number_of_retries
no radius-server retransmit
number_of_retries - Number of times the switch will try to authenticate logon access via the
RADIUS server. (Range: 1 - 30)
Default Setting
2
Command Mode
Global Configuration
Example
Console(config)#radius-server retransmit 5
Console(config)#
radius-server timeout
Use this command to set the interval between transmitting authentication requests to the RADIUS
server. Use the no form to restore the default.
Syntax
radius-server timeout number_of_seconds
no radius-server timeout
number_of_seconds - Number of seconds the switch waits for a reply before resending a
request. (Range: 1-65535)
Default Setting
5
Command Mode
Global Configuration
Example
Console(config)#radius-server timeout 10
Console(config)#
9-10
© 2007 Foundry Networks, Inc.
March 2007
Management Authentication
show radius-server
Use this command to display the current settings for the RADIUS server.
Default Setting
None
Command Mode
Privileged Exec
Example
Console#show radius-server
Server IP address: 10.1.0.99
Communication key with radius server:
Server port number: 1812
Retransmit times: 2
Request timeout: 5
Console#
tacacs-server host
This command specifies primary TACACS+ server and authentication parameters. Use the no form
to restore the default values.
Note: This command is available in devices running software release 2.2.6.x and later.
Syntax
[no] tacacs-server index host {host_ip_address} [port port] [key key]
• index - Allows you to specify one server. (Default: 1; Range: 1-1)
• host_ip_address - IP address of a TACACS+ server.
• port - TCP port used for authentication messages. Specifying this port overrides the port set
by the global command tacacs-server port (9-12) for this server only. (Default: 49; Range: 165535)
• key - Encryption key used to authenticate logon access for client. Do not use blank spaces in
the string. Specifying this key overrides the key set by the global command tacacs-server
key (9-12) for this server only. (Maximum length: 20 characters)
Default Setting
10.11.12.13
Command Mode
Global Configuration
Example
Console(config)#tacacs-server host 192.168.1.25
Console(config)#
December 2007
© 2007 Foundry Networks, Inc.
9-11
Foundry EdgeIron User Guide
tacacs-server port
Use this command to specify the TACACS+ server network port. Use the no form to restore the
default.
Syntax
tacacs-server port port_number
no tacacs-server port
port_number - TACACS+ server TCP port used for authentication messages. (Range: 165535)
Default Setting
49
Command Mode
Global Configuration
Example
Console(config)#tacacs-server port 181
Console(config)#
tacacs-server key
Use this command to set the TACACS+ encryption key. Use the no form to restore the default.
Syntax
tacacs-server key key_string
no tacacs-server key
key_string - Encryption key used to authenticate logon access for the client. Do not use blank
spaces in the string.
(Maximum length: 20 characters)
Default Setting
None
Command Mode
Global Configuration
Example
Console(config)#tacacs-server key green
Console(config)#
show tacacs-server
Use this command to display the current settings for the TACACS+ server.
Default Setting
None
Command Mode
Privileged Exec
9-12
© 2007 Foundry Networks, Inc.
March 2007
Management Authentication
Example
Console#show tacacs-server
Remote TACACS+ server configuration:
Global settings:
Communication key with TACACS+ server: *****
Server port number:
49
Server 1:
Server IP address: 192.168.1.19
Communication key with TACACS+ server: *****
Server port number: 65
Console#
Configuring TACACS+ Accounting and Authentication
Note: TACACS+ Accounting and Authentication is available in devices running software release
2.2.6.x and later.
To use TACACS+ accounting or authentication; follow these steps:
1. Set up a TACACS+ server. (Refer to the documentation for your specific server.)
2. Specify the TACACS+ server the switch will use. (See “tacacs-server host” on page 9-11.)
3. Create server groups. (See “aaa group server” on page 9-13.).
4. Add servers to the groups. Note that current software only supports one server per group.
(See “server (TACACS+ Server Group)” on page 9-14.)
5. Enable accounting and set the method list for each group.
(See “aaa accounting exec” on page 9-15 or “aaa authorization exec” on page 9-17.)
6. Associate a server group to management interfaces which require accounting or authorization
(i.e., Telnet connection or console port). (See “accounting exec” on page 9-16 or “authorization
exec” on page 9-18).
aaa group server
Use this command to group different TACACS+ server hosts into distinct lists and distinct methods.
To remove a server group, enter the no form of this command.
Syntax
[no] aaa group server tacacs group-name
• group-name - String used to name a group of TACACS+ servers.
(Range: 1-7 characters)
Default Setting
None
Command Mode
Global Configuration
December 2007
© 2007 Foundry Networks, Inc.
9-13
Foundry EdgeIron User Guide
Command Usage
A group-name list server hosts of a particular type. TACACS+ is the only server host type
supported. A server group list is used in conjunction with a global server host list. The server
group lists the IP addresses of the selected server hosts.
Example
Console(config)#aaa group server tacacs tps-servers
Console(config-sg-tacacs)#
server (TACACS+ Server Group)
Use this command to add a TACACS+ server to the current server group. To remove a server from
the current group, use the no form of this command.
Syntax
[no] server {server-index | ip-address}
• server-index - The index for a server to add to the current TACACS+ server group. (Range: 1-1)
Note that only one TACACS+ server may be configured in the current software release.
• ip-address - The IP address for a server to add to the current TACACS+ server group.
Default Setting
None
Command Mode
Server Group Configuration
Command Usage
• You must configure a TACACS+ server with the tacacs-server host command before you can
add a server to a server group with this command.
• You can use the server command followed by a server IP address or the server index to specify
a TACACS+ server. Use show tacacs-server (9-12) command to display the mapping between
the index and the server host entry.
Example
Console(config)#aaa group server tacacs tps-servers
Console(config-sg-tacacs)#server 192.168.1.19
Console(config-sg-tacacs)#
9-14
© 2007 Foundry Networks, Inc.
March 2007
Management Authentication
aaa accounting exec
This command enables TACACS+ accounting of requested services for billing or security purposes.
Use the no form to disable the accounting service.
Syntax
aaa accounting exec {default | list-name} {start-stop} group {tacacs+ | group-name}
no aaa accounting
• exec - Runs accounting for exec service request.
- default - Uses the listed accounting methods that follow this argument as the default list of
methods for accounting services.
- list-name - Character string used to name the list that follows; i.e., in the next command
parameter. (Range: 1-7 characters)
• start-stop - Automatically sends a process start and stop notice to the accounting server. (Note
that the requested user process begins regardless of whether the “start” accounting notice was
received by the accounting server.)
• group - Specifies the server group type.
- tacacs+ - Uses the list of all TACACS+ servers for authentication as defined by the tacacsserver host (9-11) command.
- group-name - Uses a subset of TACACS+ servers for accounting as defined by the server
command (see “server (TACACS+ Server Group)” on page 9-14). (1-7 characters)
Default Setting
None
Command Mode
Global Configuration
Command Usage
Use the aaa accounting exec command to enable accounting and to create named method lists
defining specific accounting methods on a per-interface basis.
Example
Console(config)#aaa accounting exec tps-servers start-stop group tacacs+
Console(config)#
aaa accounting update
This command allows periodic interim accounting records to be sent to the accounting server. Use
the no form to disable this feature.
Syntax
aaa accounting update [periodic interval]
no aaa accounting update
• interval - Interval at which to send periodic updates. (Default: 1; Range:1-2147483647 minutes)
Default Setting
Disabled
Command Mode
Global Configuration
December 2007
© 2007 Foundry Networks, Inc.
9-15
Foundry EdgeIron User Guide
Command Usage
When accounting update is activated, the switch issues interim accounting records for all users
on the system periodically as defined by the specified interval.
Example
Console(config)#aaa accounting update periodic 30
Console(config)#
accounting exec
This command applies the accounting method list to a Telnet or console interface. Use the no form
to disable this feature for the selected management interface.
Syntax
accounting exec {default | list-name}
no accounting
• exec - Runs accounting for exec service request for the current management interface.
- default - Uses the default list of methods for accounting services. The default method list must
first be created with the aaa accounting exec (9-15) command.
- list-name - Specifies the name of a list of accounting methods to use. (Range: 1-7 characters)
Default Setting
Disabled
Command Mode
Line Configuration
Command Usage
After you enable the AAA accounting service and define a named accounting method list (or use
the default method list) for a particular type of accounting, you must apply the defined lists to the
appropriate interfaces including the virtual interface such as telnet and console line for
accounting services to take place.
Example
Console(config)#line console
Console(config-line)#accounting exec default
show accounting
This command displays the current accounting settings and statistics.
Syntax
show accounting [exec [statistics] | statistics]]
• exec - Displays exec accounting records.
• statistics - Displays accounting records.
Default Setting
None
Command Mode
Privileged Exec
9-16
© 2007 Foundry Networks, Inc.
March 2007
Management Authentication
Command Usage
• If you enter show accounting without any keywords, the switch displays exec accounting setting.
• If you enter statistics following show accounting exec statistics or show accounting
statistics, the switch displays information on the current active session, including accounting
type, user name, the authenticated incoming port, and elapsed time since the accounting process
started recording information for this user.
Example
Console#show accounting
Accounting type: Exec
Method list: default
Group list: tacacs+
Interface:
Method list: tps-servers
Group list: tacacs+
Interface:
Console#
aaa authorization exec
This command restricts user access to a network by querying the TACACS+ server for authorization
for any new connection made to the Telnet or console management interface. Use the no form to
disable the authorization service.
Syntax
aaa authorization exec {default | list-name} group {tacacs+ | group-name}
no aaa authorization
• exec - Runs authorization for exec service request.
- default - Uses the default methods for authorization services as defined by the arguments
following the group keyword.
- list-name - Character string used to name the list that follows the group keyword. (Range: 1-7
characters)
• group - Specifies the server group type.
- tacacs+ - Uses the list of all TACACS+ servers for authentication as defined by the tacacsserver host (9-11) command.
- group-name - Uses a subset of TACACS+ servers for accounting as defined by the server
(TACACS+ Server Group) (9-14). (1-7 characters)
Default Setting
None
Command Mode
Global Configuration
Command Usage
• Use the aaa authorization exec command to enable authorization and to create named methods
lists, defining authorization methods that can be used when a user accesses the specified
interface. Method lists for authorization define the ways authorization will be performed and the
sequence in which these methods will be performed. A method list is simply a named list
describing the authorization methods to be used (such as RADIUS or TACACS+), in sequence.
Method lists enable you to designate one or more security protocols to be used for authorization,
thus ensuring a backup system in case the initial method fails.
December 2007
© 2007 Foundry Networks, Inc.
9-17
Foundry EdgeIron User Guide
• The switch uses the first method listed to authorize users for specific network services; if that
method fails to respond, the switch selects the next method listed in the method list. This process
continues until there is successful communication with a listed authorization method, or all
methods defined are exhausted.
Example
Console(config)#aaa authorization exec tps-server group tacacs+
Console(config)#
authorization exec
This command applies the authorization method to a Telnet or console interface. Use the no form to
disable this feature for the selected management interface.
Syntax
authorization exec {default | list-name}
no authorization
• exec - Runs authorization for exec service request for the current management interface.
- default - Uses the default list of methods for accounting services. The default method list must
first be created with the aaa accounting exec (9-15) command.
- list-name - Specifies the name of a list of accounting methods to use. (Range: 1-7 characters)
Default Setting
Disabled
Command Mode
Line Configuration
Command Usage
After you enable the AAA accounting service and define a named accounting method list (or use
the default method list) for a particular type of accounting, you must apply the defined lists to the
appropriate interfaces including the virtual interface such as telnet and console line for
accounting services to take place.
Example
Console(config)#line console
Console(config-line)#authorization exec default
show authorization
This command displays the current authorization settings.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
This command displays the current accounting type and user configured information, including
the method list, group list, and applied interfaces.
9-18
© 2007 Foundry Networks, Inc.
March 2007
Management Authentication
Example
Console#show authorization
Accounting type: Exec
Method list: default
Group list: tacacs+
Interface:
Console#
December 2007
© 2007 Foundry Networks, Inc.
9-19
Foundry EdgeIron User Guide
9-20
© 2007 Foundry Networks, Inc.
March 2007
Chapter 10
Configuring SNMP
Note: SNMP Version 3 is available in devices running software release 2.2.6.x and later.
Simple Network Management Protocol (SNMP) is a communication protocol designed specifically for
managing devices on a network. Equipment commonly managed with SNMP includes switches,
routers and host computers. SNMP is typically used to configure these devices for proper operation
in a network environment, as well as to monitor them to evaluate performance or detect potential
problems.
Managed devices supporting SNMP contain software, which runs locally on the device and is
referred to as an agent. A defined set of variables, known as managed objects, is maintained by the
SNMP agent and used to manage the device. These objects are defined in a Management
Information Base (MIB) that provides a standard presentation of the information controlled by the
agent. SNMP defines both the format of the MIB specifications and the protocol used to access this
information over the network.
The switch includes an onboard agent that supports SNMP versions 1, 2c, and 3 clients. This agent
continuously monitors the status of the switch hardware, as well as the traffic passing through its
ports. A network management station can access this information using software such as IronView
Network Manager. Access to the onboard agent from clients using SNMP v1 and v2c is controlled by
community strings. To communicate with the switch, the management station must first submit a
valid community string for authentication.
Access to the switch from clients using SNMPv3 provides additional security features that cover
message integrity, authentication, and encryption; as well as controlling user access to specific
areas of the MIB tree.
The SNMPv3 security structure consists of security models, with each model having it’s own security
levels. There are three security models defined, SNMPv1, SNMPv2c, and SNMPv3. Users are
assigned to “groups” that are defined by a security model and specified security levels. Each group
also has a defined security access to set of MIB objects for reading and writing, which are known as
“views.” The switch has a default view (all MIB objects) and default groups defined for security
December 2007
© 2007 Foundry Networks, Inc.
10-1
Foundry EdgeIron User Guide
models v1 and v2c. The following table shows the security models and levels available and the
system default settings.
Table 10-1: Security Models and Levels and Their Default Settings
Model Level
Group
Read View Write View
Notify View Security
v1
noAuthNoPriv public,
defaultview none
DefaultROGroup
none
Community string only
v1
noAuthNoPriv private,
defaultview defaultview
DefaultRWGroup
none
Community string only
v1
noAuthNoPriv user defined
v2c
noAuthNoPriv public,
defaultview none
DefaultROGroup
none
Community string only
v2c
noAuthNoPriv private,
none
Community string only
user
defined
user defined user defined Community string only
defaultview defaultview
DefaultRWGroup
v2c
noAuthNoPriv user defined
user
defined
user defined user defined Community string only
v3
noAuthNoPriv user defined
user
defined
user defined user defined A user name match only
v3
AuthNoPriv
user defined
user
defined
user defined user defined Provides user
authentication via MD5 or
SHA algorithms
v3
AuthPriv
user defined
user
defined
user defined user defined Provides user
authentication via MD5 or
SHA algorithms and data
privacy using DES 56-bit
encryption
Note: The predefined default groups and view can be deleted from the system. You can then define
customized groups and views for the SNMP clients that require access.
The CLI commands for configuring SNMP are briefly described in the table that follows:
10-2
Command
Function
Mode
Page
snmp-server
Enables the SNMP agent
GC
10-11
show snmp
Displays the status of SNMP communications
NE, PE
10-11
snmp-server community
Sets up the community access string to permit access to
SNMP commands
GC
10-4
snmp-server contact
Sets the system contact string
GC
10-7
snmp-server location
Sets the system location string
GC
10-7
snmp-server host
Specifies the recipient of an SNMP notification operation
GC
10-8
snmp-server enable traps
Enables the device to send SNMP traps (i.e., SNMP
notifications)
GC
10-10
snmp-server engine-id
Sets the SNMP engine ID
GC
10-13
© 2007 Foundry Networks, Inc.
March 2007
Configuring SNMP
Command
Function
Mode
Page
show snmp engine-id
Shows the SNMP engine ID
PE
10-14
snmp-server view
Adds an SNMP view
GC
10-25
show snmp view
Shows the SNMP views
PE
10-26
snmp-server group
Adds an SNMP group, mapping users to views
GC
10-22
show snmp group
Shows the SNMP groups
PE
10-23
snmp-server user
Adds a user to an SNMP group.
GC
10-17
show snmp user
Shows the SNMP users
PE
10-18
Setting Community Access Strings
You may configure up to five community strings authorized for management access by clients using
SNMP v1 and v2c. All community strings used for IP Trap Managers should be listed in this table. For
security reasons, you should consider removing the default strings.
USING THE WEB INTERFACE
Click SNMP, Configuration. Add new community strings as required, select the access rights from
the Access Mode drop-down list, then click Add.
•
SNMP Community Capability – The switch supports up to five community strings.
•
Current – Displays a list of the community strings currently configured.
•
Community String – A community string that acts like a password and permits access to the
SNMP protocol. Default strings: “public” (read-only access), “private” (read/write access) Range:
1-32 characters, case sensitive.
•
Access Mode – Specifies the access rights for the community string:
- Read-Only – Authorized management stations are only able to retrieve MIB objects.
- Read/Write – Authorized management stations are able to both retrieve and modify MIB
objects.
December 2007
© 2007 Foundry Networks, Inc.
10-3
Foundry EdgeIron User Guide
USING THE CLI
Use the command in this section to configure community strings from the CLI.
snmp-server community
This command defines the SNMP v1 and v2c community access string. Use the no form to remove
the specified community string.
Syntax
snmp-server community string [ro|rw]
no snmp-server community string
• string - Community string that acts like a password and permits access to the SNMP protocol.
(Maximum length: 32 characters, case sensitive; Maximum number of strings: 5)
• ro - Specifies read-only access. Authorized management stations are only able to retrieve MIB
objects.
• rw - Specifies read/write access. Authorized management stations are able to both retrieve and
modify MIB objects.
Default Setting
• public - Read-only access. Authorized management stations are only able to retrieve MIB
objects.
• private - Read/write access. Authorized management stations are able to both retrieve and
modify MIB objects.
Command Mode
Global Configuration
Example
Console(config)#snmp-server community alpha rw
Console(config)#
Specifying Trap Managers and Trap Types
Traps indicating status changes are issued by the switch to specified trap managers. You must
specify trap managers so that key events are reported by this switch to your management station
(using network management platforms such as IronView Network Manager). You can specify up to
five management stations that will receive authentication failure messages and other trap messages
from the switch.
Command Usage
• If you specify an SNMP Version 3 host, then the “Trap Manager Community String” is interpreted
as an SNMP user name. If you use V3 authentication or encryption options (authNoPriv or
authPriv), the user name must first be defined in the SNMPv3 Users page (see “Configuring
SNMPv3 Users” on page 10-15). Otherwise, the authentication password and/or privacy
password will not exist, and the switch will not authorize SNMP access for the host. However, if
you specify a V3 host with the no authentication (noAuth) option, an SNMP user account will be
automatically generated, and the switch will authorize SNMP access for the host.
• Notifications are issued by the switch as trap messages by default. The recipient of a trap
message does not send a response to the switch. Traps are therefore not as reliable as inform
messages, which include a request for acknowledgement of receipt. Informs can be used to
10-4
© 2007 Foundry Networks, Inc.
March 2007
Configuring SNMP
ensure that critical information is received by the host. However, note that informs consume more
system resources because they must be kept in memory until a response is received. Informs also
add to network traffic. You should consider these effects when deciding whether to issue
notifications as traps or informs.
To send an inform to a SNMPv2c host, complete these steps:
1. Enable the SNMP agent (see “Enabling the SNMP Agent” on page 10-10).
2. Enable trap informs as described in the following pages.
3. Create a view with the required notification messages (see “Setting SNMPv3 Views” on page 1024).
4. Create a group that includes the required notify view (see “Configuring SNMPv3 Groups” on
page 10-20).
To send an inform to a SNMPv3 host, complete these steps:
1. Enable the SNMP agent (“Enabling the SNMP Agent” on page 10-10).
2. Enable trap informs as described in the following pages.
3. Create a view with the required notification messages (see “Setting SNMPv3 Views” on page 1024).
4. Create a group that includes the required notify view (see “Configuring SNMPv3 Groups” on
page 10-20).
5. Specify a remote engine ID where the user resides (see “Specifying a Remote Engine ID” on
page 10-14).
6. Then configure a remote user (see “Specifying Remote SNMPv3 Users” on page 10-19).
December 2007
© 2007 Foundry Networks, Inc.
10-5
Foundry EdgeIron User Guide
USING THE WEB INTERFACE
Click SNMP, Configuration. Enter the IP address and community string for each management station
that will receive trap messages, specify the UDP port, SNMP version, trap security level (for v3
clients), trap inform settings (for v2c/v3 clients), and then click Add. Select the trap types required
using the check boxes for Authentication and Link-up/down traps, and then click Apply.
•
Trap Manager Capability – This switch supports up to five trap managers.
•
Current – Displays a list of the trap managers currently configured.
•
Trap Manager IP Address – IP address of a new management station to receive notification
messages.
•
Trap Manager Community String – Specifies a valid community string for the new trap manager
entry. Though you can set this string in the Trap Managers table, we recommend that you define
this string in the SNMP Configuration page (for Version 1 or 2c clients), or define a corresponding
“User Name” in the SNMPv3 Users page (for Version 3 clients). (Range: 1-32 characters, case
sensitive)
•
Trap UDP Port – Specifies the UDP port number used by the trap manager.
•
Trap Version – Indicates if the user is running SNMP v1, v2c, or v3. (Default: v1)
•
Trap Security Level – When trap version 3 is selected, you must specify one of the following
security levels. (Default: noAuthNoPriv)
- noAuthNoPriv – There is no authentication or encryption used in SNMP communications.
- AuthNoPriv – SNMP communications use authentication, but the data is not encrypted (only
available for the SNMPv3 security model).
- AuthPriv – SNMP communications use both authentication and encryption (only available for
the SNMPv3 security model).
•
Trap Inform – Notifications are sent as inform messages. Note that this option is only available
for version 2c and 3 hosts. (Default: traps are used)
- Timeout – The number of seconds to wait for an acknowledgment before resending an inform
message. (Range: 0-2147483647 centiseconds; Default: 1500 centiseconds)
10-6
© 2007 Foundry Networks, Inc.
March 2007
Configuring SNMP
- Retry times – The maximum number of times to resend an inform message if the recipient does
not acknowledge receipt. (Range: 0-255; Default: 3)
•
Enable Authentication Traps1 – Issues a trap message to specified IP trap managers whenever
authentication of an SNMP request fails. (Default: Enabled)
•
Enable Link-up and Link-down Traps1 – Issues a trap message whenever a port link is
established or broken. (Default: Enabled)
USING THE CLI
snmp-server contact
This command sets the system contact string. Use the no form to remove the system contact
information.
Syntax
snmp-server contact string
no snmp-server contact
• string - String that describes the system contact information. (Maximum length: 255 characters)
Default Setting
None
Command Mode
Global Configuration
Example
Console(config)#snmp-server contact Paul
Console(config)#
snmp-server location
This command sets the system location string. Use the no form to remove the location string.
Syntax
snmp-server location text
no snmp-server location
• text - String that describes the system location. (Maximum length: 255 characters)
Default Setting
None
Command Mode
Global Configuration
1. These are legacy notifications and therefore when used for SNMP Version 3 hosts, they must
be enabled in conjunction with the corresponding entries in the Notification View (“Configuring
SNMPv3 Groups” on page 10-20).
December 2007
© 2007 Foundry Networks, Inc.
10-7
Foundry EdgeIron User Guide
Example
Console(config)#snmp-server location WC-19
Console(config)#
snmp-server host
This command specifies the recipient of a Simple Network Management Protocol notification
operation. Use the no form to remove the specified host.
Note: This command is available on devices running software Release 2.2.6.x and later.
Syntax
snmp-server host host-addr [inform [retry retries | timeout seconds]] community-string
[version {1 | 2c | 3 {auth | noauth | priv}} [udp-port port]]
no snmp-server host host-addr
• host-addr - Internet address of the host (the targeted recipient). (Maximum host addresses: 5
trap destination IP address entries)
• inform - Notifications are sent as inform messages. Note that this option is only available for
version 2c and 3 hosts. (Default: traps are used)
-retries - The maximum number of times to resend an inform message if the recipient does not
acknowledge receipt. (Range: 0-255; Default: 3)
-seconds - The number of seconds to wait for an acknowledgment before resending an inform
message. (Range: 0-2147483647 centiseconds; Default: 1500 centiseconds)
• community-string - Password-like community string sent with the notification operation to
SNMP V1 and V2c hosts. Although you can set this string using the snmp-server host
command by itself, we recommend that you define this string using the snmp-server
community command prior to using the snmp-server host command. (Maximum length: 32
characters)
• version - Specifies whether to send notifications as SNMP Version 1, 2c or 3 traps.
(Range: 1, 2c, 3; Default: 1)
-auth | noauth | priv - This group uses SNMPv3 with authentication, no authentication, or with
authentication and privacy. See the table on Table 10-10-1 on page 2 for further information
about these authentication and encryption options.
• port - Host UDP port to use. (Range: 1-65535; Default: 162)
Default Setting
Host Address: None
Notification Type: Traps
SNMP Version: 1
UDP Port: 162
Command Mode
Global Configuration
Command Usage
• If you do not enter an snmp-server host command, no notifications are sent. In order to configure
the switch to send SNMP notifications, you must enter at least one snmp-server host command.
In order to enable multiple hosts, you must issue a separate snmp-server host command for
each host.
10-8
© 2007 Foundry Networks, Inc.
March 2007
Configuring SNMP
• The snmp-server host command is used in conjunction with the snmp-server enable traps
command. Use the snmp-server enable traps command to enable the sending of traps or
informs and to specify which SNMP notifications are sent globally. For a host to receive
notifications, at least one snmp-server enable traps command and the snmp-server host
command for that host must be enabled.
• Some notification types cannot be controlled with the snmp-server enable traps command. For
example, some notification types are always enabled.
• Notifications are issued by the switch as trap messages by default. The recipient of a trap
message does not send a response to the switch. Traps are therefore not as reliable as inform
messages, which include a request for acknowledgement of receipt. Informs can be used to
ensure that critical information is received by the host. However, note that informs consume more
system resources because they must be kept in memory until a response is received. Informs also
add to network traffic. You should consider these effects when deciding whether to issue
notifications as traps or informs.
To send an inform to a SNMPv2c host, complete these steps:
1.Enable the SNMP agent (“snmp-server” on page 10-11).
2.Allow the switch to send SNMP traps; i.e., notifications (“snmp-server enable traps” on page
10-10).
3.Specify the target host that will receive inform messages with the snmp-server host
command as described in this section.
4.Create a view with the required notification messages (“snmp-server view” on page 10-25).
5.Create a group that includes the required notify view (“snmp-server group” on page 10-22).
To send an inform to a SNMPv3 host, complete these steps:
1.Enable the SNMP agent (“snmp-server” on page 10-11).
2.Allow the switch to send SNMP traps; i.e., notifications (“snmp-server enable traps” on page
10-10).
3.Specify the target host that will receive inform messages with the snmp-server host
command as described in this section.
4.Create a view with the required notification messages (“snmp-server view” on page 10-25).
5.Create a group that includes the required notify view (“snmp-server group”).
6.Specify a remote engine ID where the user resides (“snmp-server engine-id” on page 10-13).
7.Then configure a remote user (“snmp-server user” on page 10-17).
• The switch can send SNMP Version 1, 2c or 3 notifications to a host IP address, depending on
the SNMP version that the management station supports. If the snmp-server host command
does not specify the SNMP version, the default is to send SNMP version 1 notifications.
• If you specify an SNMP Version 3 host, then the community string is interpreted as an SNMP user
name. If you use the V3 “auth” or “priv” options, the user name must first be defined with the
snmp-server user command. Otherwise, the authentication password and/or privacy password
will not exist, and the switch will not authorize SNMP access for the host. However, if you specify
a V3 host with the “noauth” option, an SNMP user account will be generated, and the switch will
authorize SNMP access for the host.
Example
Console(config)#snmp-server host 10.1.19.23 batman
Console(config)#
December 2007
© 2007 Foundry Networks, Inc.
10-9
Foundry EdgeIron User Guide
snmp-server enable traps
This command enables this device to send Simple Network Management Protocol traps or informs
(SNMP notifications). Use the no form to disable SNMP notifications.
Syntax
[no] snmp-server enable traps [authentication | link-up-down]
• authentication - Keyword to issue authentication failure notifications.
• link-up-down - Keyword to issue link-up or link-down notifications.
Default Setting
Issue authentication and link-up-down traps.
Command Mode
Global Configuration
Command Usage
• If you do not enter an snmp-server enable traps command, no notifications controlled by this
command are sent. In order to configure this device to send SNMP notifications, you must enter
at least one snmp-server enable traps command. If you enter the command with no keywords,
both authentication and link-up-down notifications are enabled. If you enter the command with a
keyword, only the notification type related to that keyword is enabled.
• The snmp-server enable traps command is used in conjunction with the snmp-server host
command. Use the snmp-server host command to specify which host or hosts receive SNMP
notifications. In order to send notifications, you must configure at least one snmp-server host
command.
• The authentication, link-up, and link-down traps are legacy notifications, and therefore when used
for SNMP Version 3 hosts, they must be enabled in conjunction with the corresponding entries in
the Notify View assigned by the snmp-server group command (page 4-116).
Example
Console(config)#snmp-server enable traps link-up-down
Console(config)#
Enabling the SNMP Agent
Enables SNMPv3 service for all management clients (i.e., versions 1, 2c, 3).
USING THE WEB INTERFACE
Click SNMP, Agent Status. Enable the SNMP Agent by marking the Enabled checkbox, and click
Apply.
• SNMP Agent Status – Enables SNMP on the switch.
10-10
© 2007 Foundry Networks, Inc.
March 2007
Configuring SNMP
USING THE CLI
snmp-server
This command enables the SNMPv3 engine and services for all management clients (i.e., versions
1, 2c, 3). Use the no form to disable the server.
Syntax
[no] snmp-server
Default Setting
Enabled
Command Mode
Global Configuration
Example
Console(config)#snmp-server
Console(config)#
show snmp
This command can be used to check the status of SNMP communications.
Default Setting
None
Command Mode
Normal Exec, Privileged Exec
Command Usage
This command provides information on the community access strings, counter information for
SNMP input and output protocol data units, and whether or not SNMP logging has been enabled
with the snmp-server enable traps command.
December 2007
© 2007 Foundry Networks, Inc.
10-11
Foundry EdgeIron User Guide
Example
Console#show snmp
SNMP Agent: enabled
SNMP traps:
Authentication: enable
Link-up-down: enable
SNMP communities:
1. private, and the privilege is read-write
2. public, and the privilege is read-only
0 SNMP packets input
0 Bad SNMP version errors
0 Unknown community name
0 Illegal operation for community name supplied
0 Encoding errors
0 Number of requested variables
0 Number of altered variables
0 Get-request PDUs
0 Get-next PDUs
0 Set-request PDUs
0 SNMP packets output
0 Too big errors
0 No such name errors
0 Bad values errors
0 General errors
0 Response PDUs
0 Trap PDUs
SNMP logging: disabled
Console#
Configuring SNMPv3 Management Access
To configure SNMPv3 management access to the switch, follow these steps:
1. If you want to change the default engine ID, do so before configuring other SNMP parameters.
2. Specify read and write access views for the switch MIB tree.
3. Configure SNMP user groups with the required security model (i.e., SNMP v1, v2c or v3) and
security level (i.e., authentication and privacy).
4. Assign SNMP users to groups, along with their specific authentication and privacy passwords.
Setting a Local Engine ID
An SNMPv3 engine is an independent SNMP agent that resides on the switch. This engine protects
against message replay, delay, and redirection. The engine ID is also used in combination with user
passwords to generate the security keys for authenticating and encrypting SNMPv3 packets.
A local engine ID is automatically generated that is unique to the switch. This is referred to as the
default engine ID. If the local engineID is deleted or changed, all SNMP users will be cleared. You will
need to reconfigure all existing users.
A new engine ID can be specified by entering 1 to 26 hexadecimal characters. If less than 26
characters are specified, trailing zeroes are added to the value. For example, the value “1234” is
equivalent to “1234” followed by 22 zeroes.
10-12
© 2007 Foundry Networks, Inc.
March 2007
Configuring SNMP
USING THE WEB INTERFACE
Click SNMP, SNMPv3, Engine ID. Enter an ID of up to 26 hexadecimal characters and then click
Save.
USING THE CLI
snmp-server engine-id
This command configures an identification string for the SNMPv3 engine. Use the no form to restore
the default.
Note: This command is available on devices running software Release 2.2.6.x and later.
Syntax
snmp-server engine-id {local | remote {ip-address}} engineid-string
no snmp-server engine-id {local | remote {ip-address}}
• local - Specifies the SNMP engine on this switch.
• remote - Specifies an SNMP engine on a remote device.
• ip-address - The Internet address of the remote device.
• engineid-string - String identifying the engine ID. (Range: 1-26 hexadecimal characters)
Default Setting
A unique engine ID is automatically generated by the switch based on its MAC address.
Command Mode
Global Configuration
Command Usage
• An SNMP engine is an independent SNMP agent that resides either on this switch or on a remote
device. This engine protects against message replay, delay, and redirection. The engine ID is also
used in combination with user passwords to generate the security keys for authenticating and
encrypting SNMPv3 packets.
• A remote engine ID is required when using SNMPv3 informs. (See snmp-server host on page
4-110.) The remote engine ID is used to compute the security digest for authenticating and
encrypting packets sent to a user on the remote host. SNMP passwords are localized using the
engine ID of the authoritative agent. For informs, the authoritative SNMP agent is the remote
agent. You therefore need to configure the remote agent’s SNMP engine ID before you can send
proxy requests or informs to it.
• Trailing zeroes need not be entered to uniquely specify a engine ID. In other words, the value
“1234” is equivalent to “1234” followed by 22 zeroes.
December 2007
© 2007 Foundry Networks, Inc.
10-13
Foundry EdgeIron User Guide
• A local engine ID is automatically generated that is unique to the switch. This is referred to as the
default engine ID. If the local engine ID is deleted or changed, all SNMP users will be cleared. You
will need to reconfigure all existing users (“snmp-server user” on page 10-17).
Example
Console(config)#snmp-server engine-id local 12345
Console(config)#snmp-server engineID remote 54321 192.168.1.19
Console(config)#
show snmp engine-id
This command shows the SNMP engine ID.
Note: This command is available on devices running software Release 2.2.6.x and later.
Command Mode
Privileged Exec
Example
This example shows the default engine ID.
Console#show snmp engine-id
Local SNMP engineID: 8000002a8000000000e8666672
Local SNMP engineBoots: 1
Remote SNMP engineID
80000000030004e2b316c54321
Console#
IP address
192.168.1.19
Field
Description
Local SNMP engineID
String identifying the engine ID.
Local SNMP engineBoots The number of times that the engine has (re-)initialized since the snmp EngineID
was last configured.
Remote SNMP engineID String identifying an engine ID on a remote device.
IP address
IP address of the device containing the corresponding remote SNMP engine.
Specifying a Remote Engine ID
To send inform messages to an SNMPv3 user on a remote device, you must first specify the engine
identifier for the SNMP agent on the remote device where the user resides. The remote engine ID is
used to compute the security digest for authenticating and encrypting packets sent to a user on the
remote host.
SNMP passwords are localized using the engine ID of the authoritative agent. For informs, the
authoritative SNMP agent is the remote agent. You therefore need to configure the remote agent’s
SNMP engine ID before you can send proxy requests or informs to it. (See “Specifying Trap
Managers and Trap Types” on page 10-4 and “Specifying Remote SNMPv3 Users” on page 10-19.)
The engine ID can be specified by entering 1 to 26 hexadecimal characters. If less than 26
characters are specified, trailing zeroes are added to the value. For example, the value “1234” is
equivalent to “1234” followed by 22 zeroes.
10-14
© 2007 Foundry Networks, Inc.
March 2007
Configuring SNMP
USING THE WEB INTERFACE
Click SNMP, SNMPv3, Remote Engine ID. Enter an ID of up to 26 hexadecimal characters and then
click Save.
USING THE CLI
See “snmp-server engine-id” on page 10-13 and “show snmp engine-id” on page 10-14.
Configuring SNMPv3 Users
Each SNMPv3 user is defined by a unique name. Users must be configured with a specific security
level and assigned to a group. The SNMPv3 group restricts users to a specific read, write, or notify
view.
Setting a Local User
USING THE WEB INTERFACE
Click SNMP, SNMPv3, Users. Click New to configure a user name. In the New User page, define a
name and assign it to a group, then click Add to save the configuration and return to the User Name
list. To delete a user, check the box next to the user name, then click Delete. To change the assigned
group of a user, click Change Group in the Actions column of the users table and select the new
group.
December 2007
© 2007 Foundry Networks, Inc.
10-15
Foundry EdgeIron User Guide
10-16
•
User Name – The name of user connecting to the SNMP agent. (Range: 1-32 characters)
•
Group Name – The name of the SNMP group to which the user is assigned. (Range: 1-32
characters)
•
Security Model – The user security model; SNMP v1, v2c or v3.
•
Security Level – The security level used for the user:
•
noAuthNoPriv – There is no authentication or encryption used in SNMP communications.
(This is the default for SNMPv3.)
•
AuthNoPriv – SNMP communications use authentication, but the data is not encrypted (only
available for the SNMPv3 security model).
•
AuthPriv – SNMP communications use both authentication and encryption (only available for
the SNMPv3 security model).
•
Authentication Protocol – The method used for user authentication.
(Options: MD5, SHA; Default: MD5)
•
Authentication Password – A minimum of eight plain text characters is required.
•
Privacy Protocol – The encryption algorithm use for data privacy; only 56-bit DES is available.
•
Privacy Password – A minimum of eight plain text characters is required.
•
Actions – Enables the user to be assigned to another SNMPv3 group.
© 2007 Foundry Networks, Inc.
March 2007
Configuring SNMP
USING THE CLI
snmp-server user
This command adds a user to an SNMP group, restricting the user to a specific SNMP Read, Write,
or Notify View. Use the no form to remove a user from an SNMP group.
Note: This command is available on devices running software Release 2.2.6.x and later.
Syntax
snmp-server user username groupname [remote ip-address] {v1 | v2c | v3 [encrypted]
[auth {md5 | sha} auth-password [priv des56 priv-password]]
no snmp-server user username {v1 | v2c | v3 | remote}
•
•
•
•
•
•
•
•
•
username - Name of user connecting to the SNMP agent. (Range: 1-32 characters)
groupname - Name of an SNMP group to which the user is assigned. (Range: 1-32 characters)
remote - Specifies an SNMP engine on a remote device.
ip-address - The Internet address of the remote device.
v1 | v2c | v3 - Use SNMP version 1, 2c or 3.
encrypted - Accepts the password as encrypted input.
auth - Uses SNMPv3 with authentication.
md5 | sha - Uses MD5 or SHA authentication.
auth-password - Authentication password. Enter as plain text if the encrypted option is not
used. Otherwise, enter an encrypted password. (A minimum of eight characters is required.)
• priv des56 - Uses SNMPv3 with privacy with DES56 encryption.
• priv-password - Privacy password. Enter as plain text if the encrypted option is not used.
Otherwise, enter an encrypted password.
Default Setting
None
Command Mode
Global Configuration
Command Usage
• The SNMP engine ID is used to compute the authentication/privacy digests from the password.
You should therefore configure the engine ID with the snmp-server engine-id (10-13) command
before using this configuration command.
• Before you configure a remote user, use the snmp-server engine-id (10-13) command to specify
the engine ID for the remote device where the user resides. Then use the snmp-server user
command to specify the user and the IP address for the remote device where the user resides.
The remote agent’s SNMP engine ID is used to compute authentication/privacy digests from the
user’s password. If the remote engine ID is not first configured, the snmp-server user command
specifying a remote user will fail.
• SNMP passwords are localized using the engine ID of the authoritative agent. For informs, the
authoritative SNMP agent is the remote agent. You therefore need to configure the remote agent’s
SNMP engine ID before you can send proxy requests or informs to it.
December 2007
© 2007 Foundry Networks, Inc.
10-17
Foundry EdgeIron User Guide
Example
Console(config)#snmp-server user steve group r&d v3 auth md5
greenpeace priv des56 einstien
Console(config)#snmp-server user mark group r&d remote
192.168.1.19 v3 auth md5 greenpeace priv des56 einstien
Console(config)#
show snmp user
This command shows information on SNMP users.
Note: This command is available on devices running software Release 2.2.6.x and later.
Command Mode
Privileged Exec
Example
Console#show snmp user
EngineId: 800000ca030030f1df9ca00000
User Name: steve
Authentication Protocol: md5
Privacy Protocol: des56
Storage Type: nonvolatile
Row Status: active
SNMP remote user
EngineId: 80000000030004e2b316c54321
User Name: mark
Authentication Protocol: mdt
Privacy Protocol: des56
Storage Type: nonvolatile
Row Status: active
Console#
10-18
Field
Description
EngineId
String identifying the engine ID.
User Name
Name of user connecting to the SNMP agent.
Authentication Protocol
The authentication protocol used with SNMPv3.
Privacy Protocol
The privacy protocol used with SNMPv3.
Storage Type
The storage type for this entry.
Row Status
The row status of this entry.
SNMP remote user
A user associated with an SNMP engine on a remote device.
© 2007 Foundry Networks, Inc.
March 2007
Configuring SNMP
Specifying Remote SNMPv3 Users
Each SNMPv3 user is defined by a unique name. Users must be configured with a specific security
level and assigned to a group. The SNMPv3 group restricts users to a specific read and a write view.
To send inform messages to an SNMPv3 user on a remote device, you must first specify the engine
identifier for the SNMP agent on the remote device where the user resides. The remote engine ID is
used to compute the security digest for authenticating and encrypting packets sent to a user on the
remote host. (See “Specifying Trap Managers and Trap Types” on page 10-4 and “Specifying a
Remote Engine ID” on page 10-14.)
USING THE WEB INTERFACE
Click SNMP, SNMPv3, Remote Users. Click New to configure a user name. In the New User page,
define a name and assign it to a group, then click Add to save the configuration and return to the
User Name list. To delete a user, check the box next to the user name, then click Delete.
•
User Name – The name of user connecting to the SNMP agent. (Range: 1-32 characters)
•
Group Name – The name of the SNMP group to which the user is assigned. (Range: 1-32
characters)
•
Engine ID – The engine identifier for the SNMP agent on the remote device where the remote
user resides. Note that the remote engine identifier must be specified before you configure a
remote user. (See “Specifying a Remote Engine ID” on page 3-42.)
•
Remote IP – The Internet address of the remote device where the user resides.
•
Security Model – The user security model; SNMP v1, v2c or v3.
December 2007
© 2007 Foundry Networks, Inc.
10-19
Foundry EdgeIron User Guide
•
Security Level – The security level used for the user:
•
noAuthNoPriv – There is no authentication or encryption used in SNMP communications.
(This is the default for SNMPv3.)
•
AuthNoPriv – SNMP communications use authentication, but the data is not encrypted (only
available for the SNMPv3 security model).
•
AuthPriv – SNMP communications use both authentication and encryption (only available for
the SNMPv3 security model).
•
Authentication Protocol – The method used for user authentication. (Options: MD5, SHA;
Default: MD5)
•
Authentication Password – A minimum of eight plain text characters is required.
•
Privacy Protocol – The encryption algorithm use for data privacy; only 56-bit DES is available.
•
Privacy Password – A minimum of eight plain text characters is required.
USING THE CLI
See “snmp-server user” on page 10-17 and “show snmp user” on page 10-18.
Configuring SNMPv3 Groups
An SNMPv3 group sets the access policy for its assigned users, restricting them to specific read,
write, and notify views. You can use the pre-defined default groups or create new groups to map a
set of SNMP users to SNMP views.
USING THE WEB INTERFACE
Click SNMP, SNMPv3, Groups. Click New to configure a new group. In the New Group page, define
a name, assign a security model and level, and then select read, write, and notify views. Click Add to
save the new group and return to the Groups list. To delete a group, check the box next to the group
name, then click Delete.
10-20
© 2007 Foundry Networks, Inc.
March 2007
Configuring SNMP
•
Group Name – The name of the SNMP group. (Range: 1-32 characters)
•
Model – The group security model; SNMP v1, v2c or v3.
•
Level – The security level used for the group:
-
noAuthNoPriv – There is no authentication or encryption used in SNMP communications.
-
AuthNoPriv – SNMP communications use authentication, but the data is not encrypted (only
available for the SNMPv3 security model).
-
AuthPriv – SNMP communications use both authentication and encryption (only available for
the SNMPv3 security model).
•
Read View – The configured view for read access. (Range: 1-64 characters)
•
Write View – The configured view for write access. (Range: 1-64 characters)
•
Notify View – The configured view for notifications. (Range: 1-64 characters)
Refer to the list of notification messages in “Trap Messages” on page B-1.
December 2007
© 2007 Foundry Networks, Inc.
10-21
Foundry EdgeIron User Guide
USING THE CLI
snmp-server group
This command adds an SNMP group, mapping SNMP users to SNMP views. Use the no form to
remove an SNMP group.
Note: This command is available on devices running software Release 2.2.6.x and later.
Syntax
snmp-server group groupname {v1 | v2c | v3 {auth | noauth | priv}} [read readview]
[write writeview] [notify notifyview]
no snmp-server group groupname
• groupname - Name of an SNMP group. (Range: 1-32 characters)
• v1 | v2c | v3 - Use SNMP version 1, 2c or 3.
• auth | noauth | priv - This group uses SNMPv3 with authentication, no authentication, or with
authentication and privacy. See “Configuring SNMPv3 Management Access” on page 10-12 for
further information about these authentication and encryption options.
• readview - Defines the view for read access. (1-64 characters)
• writeview - Defines the view for write access. (1-64 characters)
• notifyview - Defines the view for notifications. (1-64 characters)
Default Setting
Default groups: public2 (read only), private3 (read/write)
readview - Every object belonging to the Internet OID space (1.3.6.1).
writeview - Nothing is defined.
Command Mode
Global Configuration
Command Usage
• A group sets the access policy for the assigned users.
• When authentication is selected, the MD5 or SHA algorithm is used as specified in the snmpserver (10-11) command.
• When privacy is selected, the DES 56-bit algorithm is used for data encryption.
• For additional information on the notification messages supported by this switch, see “Trap
Messages” on page B-1. Also, note that the authentication, link-up and link-down messages are
legacy traps and must therefore be enabled in conjunction with the snmp-server enable traps
(10-10) command.
Example
Console(config)#snmp-server group r&d v3 auth write daily
Console(config)#
2. No view is defined.
3. Maps to the defaultview.
10-22
© 2007 Foundry Networks, Inc.
March 2007
Configuring SNMP
show snmp group
Four default groups are provided – SNMPv1 read-only access and read/write access, and SNMPv2c
read-only access and read/write access.
Command Mode
Privileged Exec
Example
Console#show snmp group
Group Name: r&d
Security Model: v3
Read View: defaultview
Write View: daily
Notify View: none
Storage Type: permanent
Row Status: active
Group Name: public
Security Model: v1
Read View: defaultview
Write View: none
Notify View: none
Storage Type: volatile
Row Status: active
Group Name: public
Security Model: v2c
Read View: defaultview
Write View: none
Notify View: none
Storage Type: volatile
Row Status: active
Group Name: private
Security Model: v1
Read View: defaultview
Write View: defaultview
Notify View: none
Storage Type: volatile
Row Status: active
Group Name: private
Security Model: v2c
Read View: defaultview
Write View: defaultview
Notify View: none
Storage Type: volatile
Row Status: active
Console#
Field
Description
groupname
Name of an SNMP group.
security model
The SNMP version.
readview
The associated read view.
writeview
The associated write view.
notifyview
The associated notify view.
storage-type
The storage type for this entry.
Row Status
The row status of this entry.
December 2007
© 2007 Foundry Networks, Inc.
10-23
Foundry EdgeIron User Guide
Setting SNMPv3 Views
SNMPv3 views are used to restrict user access to specified portions of the MIB tree. The predefined
view “defaultview” includes access to the entire MIB tree.
USING THE WEB INTERFACE
Click SNMP, SNMPv3, Views. Click New to configure a new view. In the New View page, define a
name and specify OID subtrees in the switch MIB to be included or excluded in the view. Click Back
to save the new view and return to the SNMPv3 Views list. For a specific view, click on View OID
Subtrees to display the current configuration, or click on Edit OID Subtrees to make changes to the
view settings. To delete a view, check the box next to the view name, then click Delete.
10-24
•
View Name – The name of the SNMP view. (Range: 1-64 characters)
•
View OID Subtrees – Shows the currently configured object identifiers of branches within the MIB
tree that define the SNMP view.
•
Edit OID Subtrees – Allows you to configure the object identifiers of branches within the MIB tree.
Wild cards can be used to mask a specific portion of the OID string.
•
Type – Indicates if the object identifier of a branch within the MIB tree is included or excluded
from the SNMP view.
© 2007 Foundry Networks, Inc.
March 2007
Configuring SNMP
USING THE CLI
snmp-server view
This command adds an SNMP view which controls user access to the MIB. Use the no form to
remove an SNMP view.
Syntax
snmp-server view view-name oid-tree {included | excluded}
no snmp-server view view-name
• view-name - Name of an SNMP view. (Range: 1-64 characters)
• oid-tree - Object identifier of a branch within the MIB tree. Wild cards can be used to mask a
specific portion of the OID string. (Refer to the examples.)
• included - Defines an included view.
• excluded - Defines an excluded view.
Default Setting
defaultview (includes access to the entire MIB tree)
Command Mode
Global Configuration
Command Usage
• Views are used in the snmp-server group (10-22) command to restrict user access to specified
portions of the MIB tree.
• The predefined view “defaultview” includes access to the entire MIB tree.
Examples
This view includes MIB-2.
Console(config)#snmp-server view mib-2 1.3.6.1.2.1 included
Console(config)#
This view includes the MIB-2 interfaces table, ifDescr. The wildcard is used to select all the index
values in this table.
Console(config)#snmp-server view ifEntry.2 1.3.6.1.2.1.2.2.1.*.2 included
Console(config)#
This view includes the MIB-2 interfaces table, and the mask selects all index entries.
Console(config)#snmp-server view ifEntry.a 1.3.6.1.2.1.2.2.1.1.* included
Console(config)#
December 2007
© 2007 Foundry Networks, Inc.
10-25
Foundry EdgeIron User Guide
show snmp view
This command shows information on the SNMP views.
Command Mode
Privileged Exec
Example
Console#show snmp view
View Name: mib-2
Subtree OID: 1.2.2.3.6.2.1
View Type: included
Storage Type: permanent
Row Status: active
View Name: defaultview
Subtree OID: 1
View Type: included
Storage Type: permanent
Row Status: active
Console#
10-26
Field
Description
View Name
Name of an SNMP view.
Subtree OID
A branch in the MIB tree.
View Type
Indicates if the view is included or excluded.
Storage Type
The storage type for this entry.
Row Status
The row status of this entry.
© 2007 Foundry Networks, Inc.
March 2007
Chapter 11
Line Commands
You can access the onboard configuration program by attaching a VT100 compatible device to the
server’s serial port. These commands are used to set communication parameters for the serial port
or a virtual terminal. Note that Telnet is considered a virtual terminal connection, and the only
commands that apply to Telnet include exec-timeout and password-thresh.
The following table describes the switch’s line commands. There is no Web equivalent.
Command
Function
Mode
line
Identifies a specific line for configuration and starts the line
configuration mode
GC
11-2
login
Enables password checking at login
LC
11-2
password
Specifies a password on a line
LC
11-3
timeout login response Sets the interval that the system waits for a login attempt
LC
11-4
exec-timeout
Sets the interval that the command interpreter waits until user
input is detected
LC
11-4
password-thresh
Sets the password intrusion threshold, which limits the number
of failed logon attempts
LC
11-5
silent-time
Sets the amount of time the management console is
LC
inaccessible after the number of unsuccessful logon attempts
exceeds the threshold set by the password-thresh command
11-6
databits
Sets the number of data bits per character that are interpreted
and generated by hardware
LC
11-6
parity
Defines the generation of a parity bit
LC
11-7
speed
Sets the terminal baud rate
LC
11-7
stopbits
Sets the number of the stop bits transmitted per byte
LC
11-8
disconnect
Terminates a line connection
PE
11-8
show line
Displays a terminal line's parameters
NE, PE
11-9
December 2007
© 2007 Foundry Networks, Inc.
Page
11-1
Foundry EdgeIron User Guide
line
Use this command to identify a specific line for configuration, and to process subsequent line
configuration commands.
Syntax
line {console | vty}
• console - Console terminal line.
• vty - Virtual terminal for remote console access.
Default Setting
There is no default line.
Command Mode
Global Configuration
Command Usage
Telnet is considered a virtual terminal connection and will be shown as “Vty” in screen displays
such as show users. However, the serial communication parameters (e.g., databits) do not affect
Telnet connections.
Example
To enter console line mode, enter the following command:
Console(config)#line console
Console(config-line)#
Related Commands
show line (11-9)
show users (5-17)
login
Use this command to enable password checking at login. Use the no form to disable password
checking and allow connections without a password.
Syntax
login [local]
no login
local - Selects local password checking. Authentication is based on the user name specified
with the username command.
Default Setting
local - Selects local password checking. Authentication is based on the user name specified
with the username command.
Command Mode
Line Configuration
11-2
© 2007 Foundry Networks, Inc.
March 2007
Line Commands
Command Usage
• There are three authentication modes provided by the switch itself at login:
- login selects authentication by a single global password as specified by the password line
configuration command. When using this method, the management interface starts in Normal
Exec (NE) mode.
- login local selects authentication via the user name and password specified by the username
command (i.e., default setting). When using this method, the management interface starts in
Normal Exec (NE) or Privileged Exec (PE) mode, depending on the user’s privilege level (0 or
15 respectively).
- no login selects no authentication. When using this method, the management interface starts
in Normal Exec (NE) mode.
• This command controls login authentication via the switch itself. To configure user names and
passwords for remote authentication servers, you must use the RADIUS software installed on
those servers.
Example
Console(config-line)#login local
Console(config-line)#
Related Commands
username (9-3)
password (11-3)
password
Use this command to specify the password for a line. Use the no form to remove the password.
Syntax
password {0 | 7} password
no password
- {0 | 7} - 0 means plain password, 7 means encrypted password
- password - Character string that specifies the line password. (Maximum length: 32 characters
plain text, 32 encrypted, case sensitive)
Default Setting
No password is specified.
Command Mode
Line Configuration
Command Usage
• When a connection is started on a line with password protection, the system prompts for the
password. If you enter the correct password, the system shows a prompt. You can use the
password-thresh command to set the number of times a user can enter an incorrect password
before the system terminates the line connection and returns the terminal to the idle state.
• The encrypted password is required for compatibility with legacy password settings (i.e., plain text
or encrypted) when reading the configuration file during system bootup or when downloading the
configuration file from a TFTP server. There is no need for you to manually configure encrypted
passwords.
December 2007
© 2007 Foundry Networks, Inc.
11-3
Foundry EdgeIron User Guide
Example
Console(config-line)#password 0 secret
Console(config-line)#
Related Commands
login (11-2)
password-thresh (11-5)
timeout login response
This command sets the interval that the system waits for a user to log into the CLI. Use the no form
to restore the default setting.
Syntax
timeout login response [seconds]
no timeout login response
seconds - Integer that specifies the timeout interval.
(Range: 0 - 300 seconds; 0: disabled)
Default Setting
CLI: Disabled (0 seconds)
Telnet: 600 seconds
Command Mode
Line Configuration
Command Usage
• If a login attempt is not detected within the timeout interval, the connection is terminated for the
session.
• This command applies to both the local console and Telnet connections.
• The timeout for Telnet cannot be disabled.
• Using the command without specifying a timeout restores the default setting.
Example
To set the timeout to two minutes, enter this command:
Console(config-line)#timeout login response 120
Console(config-line)#
exec-timeout
Use this command to set the interval that the system waits until user input is detected. Use the no
form to remove the timeout definition.
Syntax
exec-timeout seconds
no exec-timeout
seconds - Integer that specifies the number of seconds.
(Range: 0 - 65535 seconds; 0: no timeout)
11-4
© 2007 Foundry Networks, Inc.
March 2007
Line Commands
Default Setting
CLI: No timeout
Telnet: 10 minutes
Command Mode
Line Configuration
Command Usage
• If input is detected, the system resumes the current connection; or if no connections exist, it
returns the terminal to the idle state and disconnects the incoming session.
• This command applies to both the local console and Telnet connections.
• The timeout for Telnet cannot be disabled.
Example
To set the timeout to two minutes, enter this command:
Console(config-line)#exec-timeout 120
Console(config-line)#
password-thresh
Use this command to set the password intrusion threshold which limits the number of failed logon
attempts. Use the no form to remove the threshold value.
Syntax
password-thresh threshold
no password-thresh
threshold - The number of allowed password attempts. (Range: 1-120; 0: no threshold)
Default Setting
The default value is three attempts.
Command Mode
Line Configuration
Command Usage
• When the logon attempt threshold is reached, the system interface becomes silent for a specified
amount of time before allowing the next logon attempt. (Use the silent-time command to set this
interval.) When this threshold is reached for Telnet, the Telnet logon interface shuts down.
• This command applies to both the local console and Telnet connections.
Example
To set the password threshold to five attempts, enter this command:
Console(config-line)#password-thresh 5
Console(config-line)#
Related Commands
silent-time (11-6)
December 2007
© 2007 Foundry Networks, Inc.
11-5
Foundry EdgeIron User Guide
silent-time
Use this command to set the amount of time the management console is inaccessible after the
number of unsuccessful logon attempts exceeds the threshold set by the password-thresh
command. Use the no form to remove the silent time value.
Syntax
silent-time seconds
no silent-time
seconds - The number of seconds to disable console response. (Range: 0-65535; 0: no
silent-time)
Default Setting
The default value is no silent-time.
Command Mode
Line Configuration
Command Usage
If the password threshold was not set with the password-thresh command, silent-time begins
after the default value of three failed logon attempts.
Example
To set the silent time to 60 seconds, enter this command:
Console(config-line)#silent-time 60
Console(config-line)#
Related Commands
password-thresh (11-5)
databits
Use this command to set the number of data bits per character that are interpreted and generated by
the console port. Use the no form to restore the default value.
Syntax
databits {7 | 8}
no databits
• 7 - Seven data bits per character.
• 8 - Eight data bits per character.
Default Setting
8 data bits per character
Command Mode
Line Configuration
Command Usage
The databits command can be used to mask the high bit on input from devices that generate 7
data bits with parity. If parity is being generated, specify 7 data bits per character. If no parity is
required, specify 8 data bits per character.
11-6
© 2007 Foundry Networks, Inc.
March 2007
Line Commands
Example
To specify 7 data bits, enter this command:
Console(config-line)#databits 7
Console(config-line)#
Related Commands
parity (11-7)
parity
Use this command to define generation of a parity bit. Use the no form to restore the default setting.
Syntax
parity {none | even | odd}
no parity
• none - No parity
• even - Even parity
• odd - Odd parity
Default Setting
No parity
Command Mode
Line Configuration
Command Usage
Communication protocols provided by devices such as terminals and modems often require a
specific parity bit setting.
Example
To specify no parity, enter this command:
Console(config-line)#parity none
Console(config-line)#
speed
Use this command to set the terminal line's baud rate. This command sets both the transmit (to
terminal) and receive (from terminal) speeds. Use the no form to restore the default setting.
Syntax
speed bps
no speed
bps - Baud rate in bits per second.
(Options: 9600, 57600, 38400, 19200, 115200 bps)
Default Setting
9600 bps
Command Mode
Line Configuration
December 2007
© 2007 Foundry Networks, Inc.
11-7
Foundry EdgeIron User Guide
Command Usage
Set the speed to match the baud rate of the device connected to the serial port. Some baud rates
available on devices connected to the port might not be supported. The system indicates if the
speed you selected is not supported.
Example
To specify 57600 bps, enter this command:
Console(config-line)#speed 57600
Console(config-line)#
stopbits
Use this command to set the number of the stop bits transmitted per byte. Use the no form to restore
the default setting.
Syntax
stopbits {1 | 2}
• 1 - One stop bit
• 2 - Two stop bits
Default Setting
1 stop bit
Command Mode
Line Configuration
Example
To specify 2 stop bits, enter this command:
Console(config-line)#stopbits 2
Console(config-line)#
disconnect
This command terminates an SSH, Telnet, or console connection.
Syntax
disconnect session-id
session-id – The session identifier for an SSH, Telnet or console connection. (Range: 0-4)
Command Mode
Privileged Exec
Command Usage
Specifying session identifier “0” will disconnect the console connection. Specifying any other
identifiers for an active session will disconnect an SSH or Telnet connection.
Example
Console#disconnect 1
Console#
11-8
© 2007 Foundry Networks, Inc.
March 2007
Line Commands
show line
Use this command to display the terminal line's parameters.
Syntax
show line [console | vty]
• console - Console terminal line.
• vty - Virtual terminal for remote console access.
Default Setting
Shows all lines
Command Mode
Normal Exec, Privileged Exec
Example
To show all lines, enter this command:
Console#show line
Console configuration:
Password threshold: 3 times
Interactive timeout: Disabled
Silent time: Disabled
Baudrate: 9600
Databits: 8
Parity: none
Stopbits: 1
Vty configuration:
Password threshold: 3 times
Interactive timeout: 65535
Console#
December 2007
© 2007 Foundry Networks, Inc.
11-9
Foundry EdgeIron User Guide
11-10
© 2007 Foundry Networks, Inc.
March 2007
Chapter 12
Flash/File Commands
This chapter describes how to copy and transfer system management files using basic, non-protocol
features on EdgeIron devices through the CLI and Web management interfaces.
These commands are used to manage system code and configuration files. You can
upload/download firmware to or from a TFTP server. By saving runtime code to a file on a TFTP
server, that file can later be downloaded to the switch to restore operation. You can also set the
switch to use new firmware without overwriting the previous version.
The CLI commands for this section are briefly described in the table that follows:
Command
Function
Mode
Page
copy
Copies a code image or a switch configuration to or from
flash memory or a TFTP server
PE
12-4
boot system
Specifies the file or image used to start up the system
GC
12-6
delete
Deletes a file or code image
PE
12-7
dir
Displays a list of files in flash memory
PE
12-8
whichboot
Displays the files booted
PE
12-7
Flash/File Commands
Downloading System Software from a Server
When downloading runtime code, you can specify the Destination File Name to replace the current
image, or first download the file using a different name from the current runtime code file, and then
set the new file as the startup file.
December 2007
© 2007 Foundry Networks, Inc.
12-1
Foundry EdgeIron User Guide
USING THE WEB INTERFACE
To transfer an operation code image file from a server click System, Firmware. Enter the IP address
of the TFTP server, enter the file name of the software to download, select a file on the switch to
overwrite or specify a new file name, then click Transfer from Server.
•
TFTP Server IP Address – The IP address of a TFTP server.
•
Destination File Name – File names are case-sensitive, should not contain slashes (\ or /), the
leading letter of the file name should not be a period (.), and the maximum length for file names
on the TFTP server is 127 characters or 31 characters for files on the switch.
(Valid characters: A-Z, a-z, 0-9, “.”, “-”, “_”)
Note: The maximum number of runtime code files is two.
When you download a file using a different name from the current runtime code file, you need to
select the new file name from the drop-down box for the operation code used at startup, and then
click Apply Changes.
To start the new firmware, reboot the system.
Console#reload
System will be restarted, continue <y/n>? y
12-2
© 2007 Foundry Networks, Inc.
March 2007
Flash/File Commands
Saving or Restoring Configuration Settings
You can upload/download configuration settings to/from a TFTP server. The configuration file can be
later downloaded to restore the switch’s settings.
Note: The maximum number of user-defined configuration files is limited only by available flash
memory space.
You can save the configuration file under a new file name and then set it as the startup file, or you
can specify the current startup configuration file as the destination file to directly replace it. Note that
the file “Factory_Default_Config.cfg” can be copied to the TFTP server, but cannot be used as a
destination file name on the switch.
To transfer configuration files from a server click System, Configuration. Enter the IP address of the
TFTP server, enter the name of the file to download, select a file on the switch to overwrite or specify
a new file name, and then click Transfer from Server.
USING THE CLI
See copy (12-4).
Copying the Running Configuration to a File
You can save the current running configuration to a new file name and then set it as the startup file.
Enter a name for the new configuration file, and then click Copy to File.
USING THE WEB INTERFACE
December 2007
© 2007 Foundry Networks, Inc.
12-3
Foundry EdgeIron User Guide
USING THE CLI
Use the copy command in this section to manage system files from the CLI.
copy
Use this command to move (upload/download) a code image or configuration file between the switch’s flash
memory and a TFTP server. When you save the system code or configuration settings to a file on a TFTP server,
that file can later be downloaded to the switch to restore system operation. The success of the file transfer
depends on the accessibility of the TFTP server and the quality of the network connection.
Note: The TACACS+ and RADIUS keys on the 2404CF, 4804CF, 24G-A, and 48G are not
encrypted in the configuration file and appear as readable text. They are appear as encrypted text in
the 24G-A, 48G and 8X10G configuration files.
Syntax
copy file {file | running-config | startup-config | tftp | unit}
copy running-config {file | startup-config | tftp}
copy startup-config {file | running-config | tftp}
copy tftp {https secure-certificate | file | public-key | running-config |
startup-config }
copy unit file
• file - Keyword that allows you to copy to/from a file.
• running-config - Keyword that allows you to copy to/from the current running configuration.
• startup-config - The configuration used for system initialization.
• tftp - Keyword that allows you to copy to/from a TFTP server.
• unit - Keyword that allows you to copy to/from a specific unit in the stack.
• https secure-certificate - Keyword that allows you to copy the https secure site certificate.
• public-key - Keyword that allows you to copy a SSH key from a TFTP server.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
• The system prompts for data required to complete the copy command.
• File names are case-sensitive, should not contain slashes (\ or /), the leading letter of the file name should
not be a period (.), and the maximum length for file names on the TFTP server is 127 characters or 31
characters for files on the switch. (Valid characters: A-Z, a-z, 0-9, “.”, “-”, “_”)
• The number of user-defined configuration files is limited only by available flash memory space.
• You can use “Factory_Default_Config.cfg” as the source to copy from the factory default configuration file,
but you cannot use “Factory_Default_Config.cfg” as the destination.
• To replace the startup configuration, you must use startup-config as the destination.
Example
12-4
© 2007 Foundry Networks, Inc.
March 2007
Flash/File Commands
The following example shows how to upload the configuration settings to a file on the TFTP server:
Console#copy file tftp
Choose file type:
1. config: 2. opcode: 4. diag:
Source file name: startup
TFTP server ip address: 10.1.0.99
Destination file name: startup.01
/
Console#
5. loader: <1,2,4,5>: 1
The following example shows how to download the configuration settings from a file on the TFTP server:
Console#copy tftp file
TFTP server IP address: 10.1.0.99
Choose file type:
1. config: 2. opcode: 4. diag:
Source file name: startup.01
TFTP server ip address: 10.1.0.99
Destination file name: startup.01
/
Console#
5. loader: <1,2,4,5>: 1
The following example shows how to copy the running configuration to a startup file.
Console#copy running-config file
destination file name : startup
/
Console#
The following example shows how to download a configuration file to a startup file:
Console#copy tftp startup-config
TFTP server ip address: 10.1.0.99
Source configuration file name: startup.01
Startup configuration file name [startup]:
/
Console#
The following example shows how to copy a secure-site certificate from an TFTP server. It then reboots the
switch to activate the certificate:
Console#copy tftp https-certificate
TFTP server ip address: 10.1.0.19
Source certificate file name: SS-certificate
Source private file name: SS-private
Private password: ********
Success.
Console#reload
System will be restarted, continue <y/n>? y
December 2007
© 2007 Foundry Networks, Inc.
12-5
Foundry EdgeIron User Guide
Setting the Startup File
Once you have transferred a configuration file to the system’s Flash memory, you will then have to
set it as a startup file.
USING THE WEB INTERFACE
To set the startup file click System, Configuration. Select the new file from the drop-down box for
Startup Configuration File, and click Apply Changes. To use the new settings, reboot the system via
the System/Reset menu.
USING THE CLI
Use the boot system command to set the startup file.
boot system
Use this command to specify the file or image used to start up the system.
Syntax
boot system {boot-rom| config | opcode}: filename
The type of file or image to set as a default includes:
• boot-rom - Boot ROM
• config - Configuration file
• opcode - Run-time operation code
The colon (:) is required.
filename - Name of the configuration file or image name.
Default Setting
None
Command Mode
Global Configuration
Command Usage
• A colon (:) is required after the specified file type.
• If the file contains an error, it cannot be set as the default file.
Example
Console(config)#boot system config: startup
Console(config)#
12-6
© 2007 Foundry Networks, Inc.
March 2007
Flash/File Commands
Related Commands
dir (12-8)
whichboot (12-7)
whichboot
Use this command to display which files booted.
Default Setting
None
Command Mode
Privileged Exec
Example
This example shows the information displayed by the whichboot command. See the table on the
previous page for a description of the file information displayed by this command.
Console#whichboot
file name
file type startup size (byte)
-------------------------------- -------------- ------- ----------Unit1:
FoundryDiag2.2.0.0 Boot-Rom image
Y
816112
FoundryRuntime2.2.7.0 Operation Code
Y
2213756
set-ip
Config File
Y
2867
Console#
Deleting Files
You can delete files from the system’s Flash memory using either the Web or CLI interface.
USING THE WEB INTERFACE
To remove a file click System, Configuration. Select the file from the drop-down box for Remove
Operation Code Image File, and click Remove File.
USING THE CLI
Use the delete command to remove a file from the system’s Flash memory.
delete
Use this command to delete a file or image.
Syntax
delete filename
filename - Name of the configuration file or image name.
December 2007
© 2007 Foundry Networks, Inc.
12-7
Foundry EdgeIron User Guide
Default Setting
None
Command Mode
Privileged Exec
Command Usage
• If the file type is used for system startup, then this file cannot be deleted.
• “Factory_Default_Config.cfg” cannot be deleted.
Example
This example shows how to delete the test2.cfg configuration file from flash memory.
Console#delete test2.cfg
Console#
Related Commands
dir (12-8)
Note: The following CLI commands have no Web equivalent.
dir
Use this command to display a list of files in flash memory.
Syntax
dir [boot-rom | config | opcode [:filename]]
The type of file or image to display includes:
• boot-rom - Boot ROM (or diagnostic) image file
• config - Switch configuration file
• opcode - Run-time operation code image file.
• filename - Name of the file or image. If this file exists but contains errors, information on this file
cannot be shown.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
• If you enter the command dir without any parameters, the system displays all files.
• File information is shown below:
12-8
Column Heading
Description
file name
The name of the file.
file type
File types: Boot-Rom, Operation Code, and Config file.
startup
Shows if this file is used when the system is started.
© 2007 Foundry Networks, Inc.
March 2007
Flash/File Commands
Column Heading
Description
size
The length of the file in bytes.
Example
The following example shows how to display all file information:
Console#dir
file name
file type startup size (byte)
-------------------------------- -------------- ------- ----------FoundryDiag2.2.0.0 Boot-Rom image
Y
816112
FoundryRuntime2.2.7.0 Operation Code
Y
2213756
Factory_Default_Config.cfg
Config File
N
374
set-ip
Config File
Y
2867
startup
Config File
Y
3847
------------------------------------------------------------------Total free space:
4063232
Console#
December 2007
© 2007 Foundry Networks, Inc.
12-9
Foundry EdgeIron User Guide
12-10
© 2007 Foundry Networks, Inc.
March 2007
Chapter 13
Secure Shell Commands
The Berkeley-standard includes remote access tools originally designed for Unix systems. Some of
these tools have also been implemented for Microsoft Windows and other environments. These
tools, including commands such as rlogin (remote login), rsh (remote shell), and rcp (remote copy),
are not secure from hostile attacks. The Secure Shell (SSH) includes server/client applications
intended as a secure replacement for the older Berkley remote access tools. SSH can also provide
remote management access to this switch as a secure replacement for Telnet. When the client
contacts the switch via the SSH protocol, the switch generates a public-key that the client uses along
with a local user name and password for access authentication. SSH also encrypts all data transfers
passing between the switch and SSH-enabled management station clients, and ensures that data
traveling over the network arrives unaltered. Note that you need to install an SSH client on the
management station to access the switch for management via the SSH protocol.
Note: The EdgeIron range supports SSH Version 1.5 and 2.0.
To use the SSH server, complete these steps:
1. Generate a Host Key Pair – On the SSH Host Key Settings page, create a host public/private key
pair.
2. Provide Host Public Key to Clients – Many SSH client programs automatically import the host
public key during the initial connection setup with the switch. Otherwise, you need to manually
create a known hosts file on the management station and place the host public key in it. An entry
for a public key in the known hosts file would appear similar to the following example:
10.1.0.54 1024 35 1568499540186766925933394
677505461732531367489083654725415020245593
199868544358361651999923329781766065830956
1082591321289023376546801726272571413428762
941301196195566782 59566410486957427888146206
519417467729848654686157177393901647793559423
0357741309802273708779454524083971752646358058
176716709574804776117
3. Import Client’s Public Key to the Switch – Use the copy tftp public-key command to copy a file
containing the public key for all the SSH client’s granted management access to the switch. (Note
that these clients must be configured locally on the switch via the User Accounts. (See
“username” on page 9-3.)) The clients are subsequently authenticated using these keys. The
December 2007
© 2007 Foundry Networks, Inc.
13-1
Foundry EdgeIron User Guide
current firmware only accepts public key files based on standard UNIX format as shown in the
following example:
1024 35 1341081685609893921040944920
155425347631641921872958921143173880
055536161631051775940838686311092912
32226828519254374603100937187721199
6963178136627741416898513204911720483
0339254324101637997592371449011938
0060902539484084827178194372288402533
1159521348610229029789827213532671
31629432532818915045306393916643
[email protected]
4. Set the Optional Parameters – On the SSH Settings page, configure the optional parameters,
including the authentication timeout, the number of retries, and the server key size.
5. Enable SSH Service – On the SSH Settings page, enable the SSH server on the switch.
6. Challenge-Response Authentication – When an SSH client attempts to contact the switch, the
SSH server uses the host key pair to negotiate a session key and encryption method. Only
clients that have a private key corresponding to the public keys stored on the switch can access.
The following exchanges take place during this process:
a.The client sends its public key to the switch.
b.The switch compares the client's public key to those stored in memory.
c.If a match is found, the switch uses the public key to encrypt a random sequence of bytes, and
sends this string to the client.
d.The client uses its private key to decrypt the bytes, and sends the decrypted bytes back to the
switch.
e.The switch compares the decrypted bytes to the original bytes it sent. If the two sets match,
this means that the client's private key corresponds to an authorized public key, and the client
is authenticated.
Notes: 1. To use SSH with only password authentication, the host public key must still be given to
the client, either during initial connection or manually entered into the known host file.
However, you do not need to configure the client’s keys.
2. The SSH server supports up to four client sessions. The maximum number of client
sessions includes both current Telnet sessions and SSH sessions.
13-2
© 2007 Foundry Networks, Inc.
March 2007
Secure Shell Commands
The CLI commands for this section are briefly described in the table that follows:
Command
Function
Mode
Page
ip ssh server
Enables the SSH 2.0 server on the switch
GC
13-10
ip ssh
Specifies the authentication timeout for the SSH server and
the number of retries allowed by a client
GC
13-10
disconnect ssh
Terminates an SSH connection
PE
13-13
show ip ssh
Displays the status of the SSH server and the configured
values for authentication timeout and retries
PE
13-13
ip ssh timeout
Specifies the authentication timeout for the SSH server
GC
13-11
ip ssh authenticationretries
Specifies the number of retries allowed by a client
GC
13-12
ip ssh server-key size
Sets the SSH server key size
GC
13-12
copy tftp public-key
Copies the user’s public key from a TFTP server to the switch
PE
12-4
delete public-key
Deletes the public key for the specified user
PE
13-4
ip ssh crypto host-key
generate
Generates the host key
PE
13-5
ip ssh crypto zeroize
Clear the host key from RAM
PE
13-5
ip ssh save host-key
Saves the host key from RAM to flash memory
PE
13-6
disconnect ssh
Terminates a line connection
PE
13-13
show ip ssh
Displays the status of the SSH server and the configured
values for authentication timeout and retries
PE
13-13
show ssh
Displays the status of current SSH sessions
PE
13-6
show public-key
Shows the public key for the specified user or for the host
PE
13-8
show users
Shows SSH users, including privilege level and public key
type
PE
5-17
Secure Shell Commands
Generating the Host Key Pair
A host public/private key pair is used to provide secure communications between an SSH client and
the switch. After generating this key pair, you must provide the host public key to SSH clients and
import the client’s public key to the switch as described in the proceeding section (Command
Usage).
December 2007
© 2007 Foundry Networks, Inc.
13-3
Foundry EdgeIron User Guide
USING THE WEB INTERFACE
The following screen displays the public host-key.
•
Public-Key of Host-Key – The public key for the host.
- RSA: The first field indicates the size of the host key (e.g., 1024), the second field is the encoded
public exponent (e.g., 65537), and the last string is the encoded modulus.
- DSA: The first field indicates that the encryption method used by SSH is based on the Digital
Signature Standard (DSS). The last string is the encoded modulus.
•
Host-Key Type – The key type used to generate the host key pair (i.e., public and private keys).
(Range: RSA, DSA, Both: Default: RSA) The SSH server uses RSA or DSA for key exchange
when the client first establishes a connection with the switch, and then negotiates with the client
to select either DES (56-bit) or 3DES (168-bit) for data encryption.
•
Save Host-Key from Memory to Flash – Saves the host key from RAM (i.e., volatile memory to
flash memory. Otherwise, the host key pair is stored to RAM by default. Note that you must select
this item prior to generating the host-key pair.
•
Generate – This button is used to generate the host key pair. Note that you must first generate
the host key pair before you can enable the SSH server on the SSH Server Settings page.
USING THE CLI
Use the commands in this section to configure Secure Shell from the CLI.
delete public-key
Use this command to delete the specified user’s public key.
Syntax
delete public-key username [dsa | rsa]
• username – Name of an SSH user. (Range: 1-8 characters)
• dsa – DSA public key type.
• rsa – RSA public key type.
13-4
© 2007 Foundry Networks, Inc.
March 2007
Secure Shell Commands
Default Setting
Deletes both the DSA and RSA key.
Command Mode
Privileged Exec
Example
Console#delete public-key admin dsa
Console#
ip ssh crypto host-key generate
Use this command to generate the host key pair (i.e., public and private).
Syntax
ip ssh crypto host-key generate [dsa | rsa]
• dsa – DSA key type.
• rsa – RSA key type.
Default Setting
Generates both the DSA and RSA key pairs.
Command Mode
Privileged Exec
Command Usage
• This command stores the host key pair in memory (i.e., RAM). Use the ip ssh save host-key (136) command to save the host key pair to flash memory.
• Some SSH 2.0 client programs automatically add the public key to the known hosts file as part of
the configuration process. Otherwise, you must manually create a known hosts file and place the
host public key in it.
• The SSH 2.0 server uses this host key to negotiate a session key and encryption method with the
client trying to connect to it.
Example
Console#ip ssh crypto host-key generate dsa
Console#
Related Commands
ip ssh crypto zeroize (13-5)
ip ssh save host-key (13-6)
ip ssh crypto zeroize
Use this command to clear the host key from memory (i.e. RAM).
Syntax
ip ssh crypto zeroize [dsa | rsa]
• dsa – DSA key type.
• rsa – RSA key type.
December 2007
© 2007 Foundry Networks, Inc.
13-5
Foundry EdgeIron User Guide
Default Setting
Clears both the DSA and RSA key.
Command Mode
Privileged Exec
Command Usage
• This command clears the host key from volatile memory (RAM). Use the no ip ssh save hostkey (13-6) command to clear the host key from flash memory.
• The SSH 2.0 server must be disabled before you can execute this command.
Example
Console#ip ssh crypto zeroize dsa
Console#
Related Commands
ip ssh crypto host-key generate (13-5)
ip ssh save host-key (13-6)
ip ssh server (13-10)
ip ssh save host-key
Use this command to save host key from RAM to flash memory.
Syntax
ip ssh save host-key [dsa | rsa]
• dsa – DSA key type.
• rsa – RSA key type.
Default Setting
Saves both the DSA and RSA key.
Command Mode
Privileged Exec
Example
Console#ip ssh save host-key dsa
Console#
Related Commands
ip ssh crypto host-key generate (13-5)
show ssh
Use this command to display the current SSH 2.0 server connections.
Command Mode
Privileged Exec
13-6
© 2007 Foundry Networks, Inc.
March 2007
Secure Shell Commands
Example
Console#show ssh
Connection Version State
0
2.0
Session-Started
Username Encryption
admin
ctos aes128-cbc-hmac-md5
stoc aes128-cbc-hmac-md5
Console#
Field
Description
Session
The session number. (Range: 0-3)
Version
The Secure Shell version number.
State
The authentication negotiation state.
(Values: Negotiation-Started, Authentication-Started, Session-Started)
Username
The user name of the client.
Encryption
The encryption method is automatically negotiated between the client and
server.
Options for SSHv2.0 can include different algorithms for the client-to-server
(ctos) and server-to-client (stoc):
aes128-cbc-hmac-sha1
aes192-cbc-hmac-sha1
aes256-cbc-hmac-sha1
3des-cbc-hmac-sha1
blowfish-cbc-hmac-sha1
aes128-cbc-hmac-md5
aes192-cbc-hmac-md5
aes256-cbc-hmac-md5
3des-cbc-hmac-md5
blowfish-cbc-hmac-md5
Terminology:
DES – Data Encryption Standard (56-bit key)
3DES – Triple-DES (Uses three iterations of DES, 112-bit key)
aes – Advanced Encryption Standard (160 or 224-bit key)
blowfish – Blowfish (32-448 bit key)
cbc – cypher-block chaining
sha1 – Secure Hash Algorithm 1 (160-bit hashes)
md5 – Message Digest algorithm number 5 (128-bit hashes)
December 2007
© 2007 Foundry Networks, Inc.
13-7
Foundry EdgeIron User Guide
show public-key
Use this command to show the public key for the specified user or for the host.
Syntax
show public-key [user [username]| host]
username – Name of an SSH user. (Range: 1-8 characters)
Default Setting
Shows all public keys.
Command Mode
Privileged Exec
Command Usage
• If no parameters are entered, all keys are displayed. If the user keyword is entered, but no user
name is specified, then the public keys for all users are displayed.
• When an RSA key is displayed, the first field indicates the size of the host key (e.g., 1024), the
second field is the encoded public exponent (e.g., 35), and the last string is the encoded modulus.
When a DSA key is displayed, the first field indicates that the encryption method used by SSH is
based on the Digital Signature Standard (DSS), and the last string is the encoded modulus.
Example
Console#show public-key host
Host:
RSA:
1024 35 15684995401867669259333946775054617325313674890
8365472541502024559319986854435836165199923329781766065
8309586108259132128902337654680172627257141342876294130
1196195566782595664104869574278881462065194174677298486
5468615717739390164779355942303577413098022793708779454
524083971752646358058176716709574804776117
DSA:
ssh-dss AAAB3NzaC1kc3MAAACBAPWKZTPbsRIB8ydEXcxM3dyV/yrD
bKStIlnzD/Dg0h2HxcYV44sXZ2JXhamLK6P8bvuiyacWbUW/a4PAtp1
KMSdqsKeh3hKoA3vRRSy1N2XFfAKxl5fwFfvJlPdOkFgzLGMinvSNYQ
wiQXbKTBH0Z4mUZpE85PWxDZMaCNBPjBrRAAAAFQChb4vsdfQGNIjwb
vwrNLaQ77isiwAAAIEAsy5YWDC99ebYHNRj5kh47wY4i8cZvH+/p9cn
rfwFTMU01VFDly3IR2G395NLy5Qd7ZDxfA9mCOfT/yyEfbobMJZi8oG
CstSNOxrZZVnMqWrTYfdrKX7YKBw/Kjw6BmiFq7O+jAhf1Dg45loAc2
7s6TLdtny1wRq/ow2eTCD5nekAAACBAJ8rMccXTxHLFAczWS7EjOyDb
sloBfPuSAb4oAsyjKXKVYNLQkTLZfcFRu41bS2KV5LAwecsigF/+DjK
GWtPNIQqabKgYCw2o/dVzX4Gg+yqdTlYmGA7fHGm8ARGeiG4ssFKy4Z
6DmYPXFum1Yg0fhLwuHpOSKdxT3kk475S7 w0W
Console#
13-8
© 2007 Foundry Networks, Inc.
March 2007
Secure Shell Commands
Configuring the SSH Server
The SSH server includes basic settings for authentication.
USING THE WEB INTERFACE
Click System, SSH Settings. Select Enabled for the SSH Server Status, specify the authentication
timeout and number of retries, then click Apply.
•
SSH Server Status – Allows you to enable/disable the SSH server on the switch.
(Default: Enabled)
•
Version – The Secure Shell version number. Version 2.0 is displayed, but the switch supports
management access via either SSH Version 1.5 or 2.0 clients.
•
SSH Authentication Timeout – Specifies the time interval in seconds that the SSH server waits
for a response from a client during an authentication attempt.
(Range: 1 to 120 seconds; Default: 120 seconds)
•
SSH Authentication Retries – Specifies the number of authentication attempts that a client is
allowed before authentication fails and the client has to restart the authentication process.
(Range: 1-5 times; Default: 3)
•
SSH Server-Key Size – Specifies the SSH server key size. (Range: 512-896 bits)
- The server key is a private key that is never shared outside the switch.
- The host key is shared with the SSH client, and is fixed at 1024 bits.
USING THE CLI
Use the commands in this section to specify the SSH timeout, re-tries and key size, and to
disconnect from an SSH server.
December 2007
© 2007 Foundry Networks, Inc.
13-9
Foundry EdgeIron User Guide
ip ssh
Use this command to configure authentication control parameters for the Secure Shell (SSH 2.0)
server on this switch. Use the no form to restore the default settings.
Syntax
ip ssh {[timeout seconds] | [authentication-retries count]}
no ip ssh {[timeout] | [authentication-retries]}
• seconds – The timeout for client response during SSH negotiation. (Range: 1-120)
• count – The number of authentication attempts permitted after which the interface is reset.
(Range: 1-5)
Default Setting
timeout: 120 seconds
count: 3
Command Mode
Global Configuration
Command Usage
The timeout specifies the interval the switch will wait for a response from the client during the
SSH negotiation phase. Once an SSH 2.0 session has been established, the timeout for user
input is controlled by the exec-timeout command for vty sessions.
Example
Console(config)#ip ssh timeout 60
Console(config)#ip ssh authentication-retires 2
Console(config)#
Related Commands
show ssh (13-6)
ip ssh server
Use this command to enable the Secure Shell (SSH 2.0) server on this switch. Use the no form to
disable this service.
Syntax
ip ssh server
no ip ssh server
Default Setting
Disabled
Command Mode
Global Configuration
Command Usage
• The SSH server supports up to four client sessions. The maximum number of client sessions
includes both current Telnet sessions and SSH sessions.
13-10
© 2007 Foundry Networks, Inc.
March 2007
Secure Shell Commands
• The SSH server uses DSA or RSA for key exchange when the client first establishes a connection
with the switch, and then negotiates with the client to select either DES (56-bit) or 3DES (168-bit)
for data encryption.
• You must generate the host key before enabling the SSH 2.0 server.
Example
Console#ip ssh crypto host-key generate dsa
Console#configure
Console(config)#ip ssh server
Console(config)#
Related Commands
ip ssh crypto host-key generate (13-5)
show ssh (13-6)
ip ssh timeout
Use this command to configure the timeout for the SSH 2.0 server. Use the no form to restore the
default setting.
Syntax
ip ssh timeout seconds
no ip ssh timeout
seconds – The timeout for client response during SSH negotiation. (Range: 1-120)
Default Setting
10 seconds
Command Mode
Global Configuration
Command Usage
The timeout specifies the interval the switch will wait for a response from the client during the
SSH negotiation phase. Once an SSH session has been established, the timeout for user input is
controlled by the exec-timeout command for vty sessions.
Example
Console(config)#ip ssh timeout 60
Console(config)#
Related Commands
exec-timeout (11-4)
show ip ssh (13-13)
December 2007
© 2007 Foundry Networks, Inc.
13-11
Foundry EdgeIron User Guide
ip ssh authentication-retries
Use this command to configure the number of times the SSH 2.0 server attempts to reauthenticate a
user. Use the no form to restore the default setting.
Syntax
ip ssh authentication-retries count
no ip ssh authentication-retries
count – The number of authentication attempts permitted after which the interface is reset.
(Range: 1-5)
Default Setting
3
Command Mode
Global Configuration
Example
Console(config)#ip ssh authentication-retires 2
Console(config)#
Related Commands
show ip ssh (13-13)
ip ssh server-key size
Use this command to set the SSH 2.0 server key size. Use the no form to restore the default setting.
Syntax
ip ssh server-key size key-size
no ip ssh server-key size
key-size – The size of server key. (Range: 512-896 bits)
Default Setting
768 bits
Command Mode
Global Configuration
Command Usage
• The server key is a private key that is never shared outside the switch.
• The host key is shared with the SSH 2.0 client, and is fixed at 1024 bits.
Example
Console(config)#ip ssh server-key size 512
Console(config)#
13-12
© 2007 Foundry Networks, Inc.
March 2007
Secure Shell Commands
disconnect ssh
Use this command to terminate a Secure Shell (SSH 2.0) client connection.
Syntax
disconnect ssh connection-id
connection-id – The session identifier as displayed in the show ip ssh command.
Command Mode
Privileged Exec
Example
Console#disconnect ssh 0
Console#
Related Commands
show ip ssh (13-13)
show ip ssh
Use this command to display the connection settings used when authenticating client access to the
SSH 2.0 server.
Command Mode
Privileged Exec
Example
Console#show ip ssh
SSH Enabled - version 1.99
Negotiation timeout: 120 secs; Authentication retries: 3
Server key size: 768 bits
Console#
December 2007
© 2007 Foundry Networks, Inc.
13-13
Foundry EdgeIron User Guide
13-14
© 2007 Foundry Networks, Inc.
March 2007
Chapter 14
802.1x Port Access Control
Network switches can provide open and easy access to network resources by simply attaching a
client PC. Although this automatic configuration and access is a desirable feature, it also allows
unauthorized personnel to easily intrude and possibly gain access to sensitive network data.
The IEEE 802.1x (dot1x) standard defines a port-based access control procedure that prevents
unauthorized access to a network by requiring users to first submit credentials for authentication.
Access to all switch ports in a network can be centrally controlled from a server, which means that
authorized users can use the same credentials for authentication from any point within the network.
This switch uses the Extensible Authentication Protocol over LANs (EAPOL) to exchange
authentication protocol messages with the client, and a remote RADIUS authentication server to
verify user identity and access rights. When a client (i.e., Supplicant) connects to a switch port, the
switch (i.e., Authenticator) responds with an EAPOL identity request. The client provides its identity
(such as a user name) in an EAPOL response to the switch, which it forwards to the RADIUS server.
The RADIUS server verifies the client identity and sends an access challenge back to the client. The
EAP packet from the RADIUS server contains not only the challenge, but the authentication method
to be used. The client can reject the authentication method and request another, depending on the
configuration of the client software and the RADIUS server. The authentication method is MD5 only.
(TLS, TTLS or other will be supported in future releases.) The client responds to the appropriate
method with its credentials, such as a password or certificate. The RADIUS server verifies the client
credentials and responds with an accept or reject packet. If authentication is successful, the switch
allows the client to access the network. Otherwise, network access is denied and the port remains
blocked.
December 2007
© 2007 Foundry Networks, Inc.
14-1
Foundry EdgeIron User Guide
The operation of 802.1x on the switch requires the following:
•
The switch must have an IP address assigned.
•
RADIUS authentication must be enabled on the switch and the IP address of the RADIUS server
specified.
•
Each switch port that will be used must be set to dot1x “Auto” mode.
•
Each client that needs to be authenticated must have dot1x client software installed and properly
configured.
•
The RADIUS server must support EAPOL and MD5 authentication.
The CLI commands for 802.1x are briefly described in the table that follows:
14-2
Command
Function
Mode
dot1x default
Resets all dot1x parameters to their default values
GC
14-6
dot1x max-req
Sets the maximum number of times the switch will
attempt to send a request to the client before
authentication fails
GC
14-7
dot1x port-control
Sets dot1x mode for a port interface
IC
14-7
dot1x re-authenticate
Forces re-authentication on specific ports
PE
14-7
dot1x re-authentication
Enables re-authentication for all ports
GC
14-7
dot1x timeout quiet-period
Sets the time that a switch port waits after the Max
Request Count has been exceeded before attempting
to acquire a new client
GC
14-8
dot1x timeout re-authperiod
Sets the time period after which a connected client
must be re-authenticated
GC
14-8
dot1x timeout tx-period
Sets the time period during an authentication session
that the switch waits before re-transmitting an EAP
packet
GC
14-9
show dot1x
Shows all dot1x related information
PE
14-3
© 2007 Foundry Networks, Inc.
Page
March 2007
802.1x Port Access Control
USING THE WEB INTERFACE
To display 802.1x information click 802.1x, 802.1x Information.
•
802.1x Re-authentication – Sets the client to be re-authenticated after the interval specified by
the Timeout for Re-authentication Period. Re-authentication can be used to detect if a new device
is plugged into a switch port. (Default: Disabled)
•
802.1x Max Request Count – Sets the maximum number of times the switch port will retransmit
an EAP request packet to the client before it times out the authentication session.
(Range: 1-10; Default 2)
•
Timeout for Quiet Period – Sets the time that a switch port waits after the 802.1x Max Request
Count has been exceeded before attempting to acquire a new client.
(Range: 1-65535 seconds; Default: 60 seconds)
•
Timeout for Re-authentication Period – Sets the time period after which a connected client
must be re-authenticated. (Range: 1-65535 seconds; Default: 3600 seconds)
•
Timeout for TX Period – Sets the time period during an authentication session that the switch
waits before re-transmitting an EAP packet. (Range: 1-65535; Default: 30 seconds)
USING THE CLI
Use the command in this section to display 802.1x settings from the CLI.
show dot1x
Use this command to show general port authentication related settings on the switch or a specific
interface.
Syntax
show dot1x [statistics] [interface interface]
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
Command Mode
Privileged Exec
December 2007
© 2007 Foundry Networks, Inc.
14-3
Foundry EdgeIron User Guide
Command Usage
This command displays the following information:
• Global 802.1x Parameters – Displays the global port access control parameters that can be
configured for this switch as described in the preceding pages, including reauth-enabled (dot1x
re-authentication), reauth-period (dot1x timeout re-authperiod), quiet-period (dot1x timeout
quiet-period), tx-period (dot1x timeout tx-period), and max-req (dot1x max-req). It also
displays the following global parameters which are set to a fixed value, including the following
items:
- supp-timeout– Supplicant timeout.
- server-timeout– Server timeout.
- reauth-max– Maximum number of reauthentication attempts.
• 802.1x Port Summary – Displays the port access control parameters for each interface, including
the following items:
- Status– Administrative state for port access control.
- Operation Mode–Allows single or multiple hosts.
- Mode– Dot1x port control mode (dot1x port-control).
- Authorized– Authorization status (yes or n/a - not authorized).
• 802.1x Port Details – Displays detailed port access control settings for each interface as
described in the preceding pages, including administrative status for port access control,
Operation mode (dot1x port-control), Max count (dot1x max-req), and Port Control (dot1x
port-control). It also displays the following information:
- Status– Authorization status (authorized or unauthorized).
- Supplicant– MAC address of authorized client.
- Current Identifier– Current unit among multiple hosts
• Authenticator State Machine
- State– Current state (including initialize, disconnected, connecting, authenticating,
authenticated, aborting, held, force_authorized, force_unauthorized).
- Reauth Count– Number of times connecting state is re-entered.
• Backend State Machine
- State– Current state (including request, response, success, fail, timeout, idle, initialize).
- Request Count– Number of EAP Request packets sent to the Supplicant without receiving a
response.
- Identifier(Server)– Identifier carried in the most recent EAP Success, Failure or Request packet
received from the Authentication Server.
• Reauthentication State Machine
- State– Current state (including initialize, reauthenticate).
14-4
© 2007 Foundry Networks, Inc.
March 2007
802.1x Port Access Control
Example
Console#show dot1x
Global 802.1X Parameters
reauth-enabled: yes
reauth-period: 300
quiet-period:
350
tx-period:
300
supp-timeout:
30
server-timeout: 30
reauth-max:
2
max-req:
2
802.1X Port Summary
Port Name
1/1
1/2
Status
disabled
disabled
Operation Mode
Single-Host
Single-Host
Mode
ForceAuthorized
ForceAuthorized
Authorized
yes
n/a
1/11
1/24
disabled
enabled
Single-Host
Single-Host
ForceAuthorized
Auto
yes
yes
.
.
802.1X Port Details
802.1X is disabled on port 1/1
.
.
.
802.1X is enabled on port 1/24
Status
Authorized
Operation mode
Single-Host
Max count
5
Port-control
Auto
Supplicant
00-e0-29-94-34-65
Current Identifier 4
Authenticator State Machine
State
Connecting
Reauth Count
1
Backend State Machine
State
Idle
Request Count
0
Identifier(Server) 5
Reauthentication State Machine
State
Initialize
December 2007
© 2007 Foundry Networks, Inc.
14-5
Foundry EdgeIron User Guide
Configuring 802.1x Global Settings
The 802.1x protocol includes global parameters that control the client authentication process that
runs between the client and the switch (i.e., authenticator), as well as the client identity lookup
process that runs between the switch and authentication server. The configuration options for
parameters are described in this section.
USING THE WEB INTERFACE
Select 802.1x, 802.1x Configuration. Enable dot1x globally for the switch, modify any of the
parameters required, and then click Apply.
•
802.1x Re-authentication – Sets the client to be re-authenticated after the interval specified by
the Timeout for Re-authentication Period. Re-authentication can be used to detect if a new device
is plugged into a switch port. (Default: Disabled)
•
802.1x Max Request Count – Sets the maximum number of times the switch port will retransmit
an EAP request packet to the client before it times out the authentication session.
(Range: 1-10; Default 2)
•
Timeout for Quiet Period – Sets the time that a switch port waits after the 802.1X Max Request
Count has been exceeded before attempting to acquire a new client.
(Range: 1-65535 seconds; Default: 60 seconds)
•
Timeout for Re-authentication Period – Sets the time period after which a connected client
must be re-authenticated. (Range: 1-65535 seconds; Default: 3600 seconds)
•
Timeout for Tx Period – Sets the time period during an authentication session that the switch
waits before re-transmitting an EAP packet. (Range: 1-65535; Default: 30 seconds)
USING THE CLI
Use the commands in this section to configure 802.1x settings from the CLI.
dot1x default
Sets all configurable dot1x global and port settings to their default values.
Command Mode
Global Configuration
14-6
© 2007 Foundry Networks, Inc.
March 2007
802.1x Port Access Control
Example
Console(config)#dot1x default
Console(config)#
dot1x max-req
Sets the maximum number of times the switch port will retransmit an EAP request packet to the
client before it times out the authentication session. Use the no form to restore the default.
Syntax
dot1x max-req count
no dot1x max-req
count – The maximum number of requests (Range: 1-10)
Default
2 seconds
Command Mode
Global Configuration
Example
Console(config)#dot1x max-req 2
Console(config)#
dot1x re-authenticate
Forces re-authentication on all ports or a specific interface.
Syntax
dot1x re-authenticate [interface]
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
Command Mode
Privileged Exec
Example
Console#dot1x re-authenticate
Console#
dot1x re-authentication
Enables periodic re-authentication globally for all ports. Use the no form to disable re-authentication.
Syntax
dot1x re-authentication
[no] dot1x re-authentication
December 2007
© 2007 Foundry Networks, Inc.
14-7
Foundry EdgeIron User Guide
Command Mode
Global Configuration
Example
Console(config)#dot1x re-authentication
Console(config)#
dot1x timeout quiet-period
Sets the time that a switch port waits after the Max Request Count has been exceeded before
attempting to acquire a new client. Use the no form of this command to reset the default.
Syntax
dot1x timeout quiet-period seconds
no dot1x timeout quiet-period seconds
seconds - The number of seconds. (Range: 1-65535)
Default
60 seconds
Command Mode
Global Configuration
Example
Console(config)#dot1x timeout quiet-period 350
Console(config)#
dot1x timeout re-authperiod
Sets the time period after which a connected client must be re-authenticated.
Syntax
dot1x timeout re-authperiod seconds
no dot1x timeout re-authperiod
seconds - The number of seconds. (Range: 1-65535)
Default
3600 seconds
Command Mode
Global Configuration
Example
Console(config)#dot1x timeout re-authperiod 300
Console(config)#
14-8
© 2007 Foundry Networks, Inc.
March 2007
802.1x Port Access Control
dot1x timeout tx-period
Sets the time that the switch waits during an authentication session before re-transmitting an EAP
packet. Use the no form to reset to the default value.
Syntax
dot1x timeout tx-period seconds
no dot1x timeout tx-period
seconds - The number of seconds. (Range: 1-65535)
Default
30 seconds
Command Mode
Global Configuration
Example
Console(config)#dot1x timeout tx-period 300
Console(config)#
Configuring Port Authorization Mode
When dot1x is enabled, you need to specify the dot1x authentication mode configured for each port.
USING THE WEB INTERFACE
Click 802.1x, 802.1x Port configuration. Select the authentication mode from the drop-down box and
click Apply.
•
Status – Indicates if authentication is enabled or disabled on the port.
•
Mode – Sets the authentication mode to one of the following options:
- Auto – Requires a dot1x-aware client to be authorized by the authentication server. Clients that
are not dot1x-aware will be denied access.
December 2007
© 2007 Foundry Networks, Inc.
14-9
Foundry EdgeIron User Guide
- Force-Authorized – Forces the port to grant access to all clients, either dot1x-aware or
otherwise.
- Force-Unauthorized – Forces the port to deny access to all clients, either dot1x-aware or
otherwise.
•
Authorized –
- Yes – Connected client is authorized.
- No – Connected client is not authorized.
- [Blank] – Displays nothing when 802.1X is disabled on a port.
•
Supplicant – Indicates the MAC address of a connected client.
•
Trunk – Indicates if the port is configured as a trunk port.
USING THE CLI
Use the commands in this section to configure 802.1x port authorization mode from the CLI.
dot1x port-control
Sets the dot1x mode on a port interface. Use the no form to restore the default.
Syntax
dot1x port-control {auto | force-authorized | force-unauthorized}
no dot1x port-control
• auto – Requires a dot1x-aware connected client to be authorized by the RADIUS server.
Clients that are not dot1x-aware will be denied access.
• force-authorized – Configures the port to grant access to all clients, either dot1x-aware or
otherwise.
• force-unauthorized – Configures the port to deny access to all clients, either dot1x-aware or
otherwise.
Default
force-authorized
Command Mode
Interface Configuration
Example
Console(config)#interface ethernet 1/2
Console(config-if)#dot1x port-control auto
Console(config-if)#
14-10
© 2007 Foundry Networks, Inc.
March 2007
802.1x Port Access Control
Displaying 802.1x Statistics
The EdgeIron switches can display statistics for dot1x protocol exchanges for any port.
Statistical Values
Parameter
Description
Rx EXPOL Start
The number of EAPOL Start frames that have been received by this
Authenticator.
Rx EAPOL Logoff
The number of EAPOL Logoff frames that have been received by this
Authenticator.
Rx EAPOL Invalid
The number of EAPOL frames that have been received by this Authenticator
in which the frame type is not recognized.
Rx EAPOL Total
The number of valid EAPOL frames of any type that have been received by
this Authenticator.
Rx EAP Resp/Id
The number of EAP Resp/Id frames that have been received by this
Authenticator.
Rx EAP Resp/Oth
The number of valid EAP Response frames (other than Resp/Id frames) that
have been received by this Authenticator.
Rx EAP LenError
The number of EAPOL frames that have been received by this Authenticator
in which the Packet Body Length field is invalid.
Rx Last EAPOLVer
The protocol version number carried in the most recently received EAPOL
frame.
Rx Last EAPOLSrc
The source MAC address carried in the most recently received EAPOL
frame.
Tx EAPOL Total
The number of EAPOL frames of any type that have been transmitted by this
Authenticator.
Tx EAP Req/Id
The number of EAP Req/Id frames that have been transmitted by this
Authenticator.
Tx EAP Req/Oth
The number of EAP Request frames (other than Rq/Id frames) that have
been transmitted by this Authenticator.
December 2007
© 2007 Foundry Networks, Inc.
14-11
Foundry EdgeIron User Guide
USING THE WEB INTERFACE
To display 802.1x statistics for a port select dot1x, dot1x Statistics. Select the required port and then
click Query. Click Refresh to update the statistics.
USING THE CLI
Refer to show dot1x (14-3).
14-12
© 2007 Foundry Networks, Inc.
March 2007
Chapter 15
Multi-Device Port Authentication
Note: This feature is available on EdgeIron 2402CF,4802CF, 24G-A and 48G, running software
release 2.2.7.11 and later.
The Multi-Device Port Authentication feature controls the network access of a host based on
authenticating its MAC address. It is a mechanism by which incoming traffic originating from a
specific MAC address is forwarded by the device only if the source MAC address is successfully
authenticated by a RADIUS server. While authentication for a MAC address is in progress, all traffic
from the new MAC address will be blocked until authentication succeeds or fails, before taking
appropriate action.
Authentication uses the RADIUS server by sending a PAP request with username and password
both equal to the MAC address being authenticated. The format of the MAC address sent to the
RADIUS server is configurable through the CLI. On successful authentication, the RADIUS server
may optionally return the VLAN identifier. The VLAN identifier is carried in "Tunnel-Type", "TunnelMedium-Type" and "Tunnel-Private-Group-ID" attributes of RADIUS packets. This VLAN must exist
for authentication to be successful.
When a ports state is changed to "Down", all authorized and unauthorized MAC addresses will be
removed from the secure address table, any pending authentication requests will be cancelled and
the VLAN assignment will be set to the ports default VLAN. The maximum number of concurrent
MAC addresses permitted on a port is configurable on a per-port basis. The total number of MAC
addresses across all ports in a unit is limited by a fixed maximum.
When multiple MAC addresses are forwarding traffic, then the ports VLAN assignments will include
only the subset of VLAN identifiers applicable to all MAC addresses being forwarded (authorized and
unauthorized). This ensures that no host can access a VLAN unless configured for use. On detecting
a new MAC address when the address limit is reached, the unit will remove the oldest unauthorized
MAC address on the port and replace it with the new address. If there are no authorized addresses,
then the oldest authorized address will be replaced. If the RADIUS server cannot validate the users
MAC address, then it is considered an authentication failure, and a specified action is taken.
MAC addresses can be specified that do not have to go through multi-device port authentication.
These MAC addresses are considered pre-authenticated, and are not subject to RADIUS
authentication.
When a port is dynamically assigned to a VLAN through the authentication of a MAC address, and
the MAC session for that address is deleted, then by default the port is removed from its RADIUS-
December 2007
© 2007 Foundry Networks, Inc.
15-1
Foundry EdgeIron User Guide
assigned VLAN and placed back in the VLAN where it was originally assigned. A port will be
removed from its RADIUS-assigned VLAN when any of the following occurs:
•
The link goes down
•
The MAC session is manually deleted.
•
The MAC address that caused the port to be dynamically assigned to a VLAN ages out.
The CLI commands for this section are briefly described in the table that follows:
15-2
Command
Function
Mode
mac-authentication
Globally enables Multi-Device Port Authentication.
IC
15-3
mac-authentication
auth-passwd-format
Configures the password format to send to the RADIUS
server.
GC
15-3
mac-authentication
auth-fail-vlan-id
Specifies the VLAN ID of the restricted VLAN.
GC
15-4
mac-authentication
mac-filter
Defines MAC address filters to specify MAC addresses to
be excluded from the Multi-Device Port Authentication.
GC
15-4
mac-authentication
no-override-restrict-vlan
Configures the switch to ignore RADIUS-specified VLAN
assignments.
GC
15-5
mac-authentication savedynamicvlan-to-config
Configures the switch to save the RADIUS-specified VLAN
assignments.
GC
15-5
mac-authentication
disable-aging
Disables aging for authenticated MAC addresses globally or
on a per port basis.
GC, IC
15-6
mac-authentication
max-age
Specifies the aging time for blocked MAC addresses.
GC
15-6
mac-authentication
Enables Multi-Device Port Authentication on a per port
basis.
IC
15-7
mac-authentication
auth-fail-action
Specifies what action to take when port authentication fails. IC
15-7
mac-authentication
apply-mac-auth-filter
Applies the MAC address filter on an interface.
IC
15-8
mac-authentication
enable-dynamic-vlan
Enables dynamic VLAN assignment for authenticated MAC
addresses.
IC
15-8
mac-authentication
move-back-to-old-vlan
Specifies an alternate VLAN to which to move the port when
the MAC session for the address is deleted.
IC
15-9
mac-authentication
clear-mac-session
Clears an authenticated MAC session on an interface.
IC
15-9
mac-authentication
clear-auth-mac-table
Clears all authenticated MAC sessions on an interface.
IC
15-10
mac-authentication
disable-aging
Disables aging for authenticated MAC addresses.
IC
15-10
clear auth-mac-table
Clears the entire contents of the authenticated MAC
address table.
PE
15-11
show auth-mac-address
Displays the information about the authenticated MAC
addresses on the ports where port authentication is
enabled.
PE
15-11
© 2007 Foundry Networks, Inc.
Page
March 2007
Multi-Device Port Authentication
Command
Function
Mode
Page
show auth-mac-address
configuration
Displays the information about the multi-device port
authentication configuration.
PE
15-11
show auth-mac-address
detail
Displays detailed port authentication settings and
authenticated MAC addresses for a port where the feature
is enabled.
PE
15-13
show auth-mac-address
authorized-mac
Displays MAC addresses that have been successfully
authenticated.
PE
15-13
show auth-mac-address
unauthorized-mac
Displays MAC addresses for which authentication was not
successful.
PE
15-14
mac-authentication
Use this command to globally enable Multi-Device Port Authentication. Use the no form of this
command to disable it.
Syntax
[no] mac-authentication
Default Setting
Disabled
Command Mode
Global Configuration
Example
To globally enable Multi-Device Port Authentication, enter the following command:
Console(config)#mac-authentication
Console(config)#
Related Commands
mac-authentication auth-passwd-format (15-3)
mac-authentication auth-fail-vlan-id (15-4)
mac-authentication auth-passwd-format
Use this command to configure the password format to send to the RADIUS sever. Use the no form
of this command to restore the default password format.
Syntax
[no] mac-authentication auth-passwd-format {xxxx.xxxx.xxxx | xx-xx-xx-xx-xx-xx |
xxxxxxxxxxxx}
Default Setting
Default password format is xxxxxxxxxxxx
Command Mode
Global Configuration
December 2007
© 2007 Foundry Networks, Inc.
15-3
Foundry EdgeIron User Guide
Example
To globally enable Multi-Device Port Authentication, enter the following command:
Console(config)#mac-authentication auth-passwd-format xxxx.xxxx.xxxx
Console(config)#
Related Commands
mac-authentication (15-3)
mac-authentication auth-fail-vlan-id (15-4)
mac-authentication auth-fail-vlan-id
Use this command to globally specify the VLAN ID of the restricted VLAN. Use the no form of this
command to remove the restricted VLAN.
Syntax
[no] mac-authentication auth-fail-vlan-id vlan-id
vlan-id - VLAN ID that the port will move to when RADIUS authentication fails.
Default Setting
None
Command Mode
Global Configuration
Example
The following command assigns VLAN 2 to be the globally restricted VLAN.
Console(config)#mac-authentication auth-fail-vlan-id 2
Console(config)#
Related Commands
mac-authentication (15-3)
mac-authentication no-override-restrict-vlan (15-5)
mac-authentication mac-filter
Use this command to define MAC address filters. The MAC address filters are used to specify MAC
addresses to be excluded from Multi-Device Port Authentication. Use the no form of this command
to remove the MAC address filters.
Syntax
[no] mac-authentication mac-filter filter-id mac-address
• filter-id - Filter number corresponding to MAC address. (Range: 1-64)
• mac-address - MAC address to be excluded from authentication.
15-4
© 2007 Foundry Networks, Inc.
March 2007
Multi-Device Port Authentication
Default Setting
None
Command Mode
Global Configuration
Example
The following example defines MAC filter 1 to MAC address 00-00-E8-12-11-01.
Console(config)#mac-authentication mac-filter 1 0000.E812.1101
Console(config)#
Related Commands
mac-authentication (15-3)
mac-authentication no-override-restrict-vlan
Use this command to configure the device to ignore the RADIUS-specified VLAN assignments. Use
the no form of this command to restore the default.
Syntax
[no] mac-authentication no-override-restrict vlan
Default Setting
Disable restrict-vlan overriding.
Command Mode
Global Configuration
Example
Console(config)#mac-authentication no-override-restrict-vlan
Console(config)#
Related Commands
mac-authentication (15-3)
mac-authentication auth-fail-vlan-id (15-4)
mac-authentication save-dynamicvlan-to-config
Use this command to save the RADIUS-specified VLAN assignments to the switch’s startup-config
file. Use the no form of this command to restore the default.
Syntax
[no] mac-authentication save-dynamicvlan-to-config
Default Setting
Disabled
Command Mode
Global Configuration
December 2007
© 2007 Foundry Networks, Inc.
15-5
Foundry EdgeIron User Guide
Example
Console(config)#mac-authentication save-dynamicvlan-to-config
Console(config)#
Related Commands
mac-authentication (15-3)
mac-authentication disable-aging
Use this command to disable aging for authenticated MAC addresses. Use the no form of this
command to restore the default.
Syntax
[no] mac-authentication disable-aging
Default Setting
Disabled
Command Mode
Global Configuration
Example
Console(config)#mac-authentication disable-aging
Console(config)#
Related Commands
mac-authentication (15-3)
mac-authentication max-age
Use this command to specify the software aging time for blocked MAC addresses. Use the no form
of this command to restore the default.
Syntax
[no] mac-authentication max-age seconds
seconds - The software aging time in seconds. (Range: 1-65535)
Default Setting
120 seconds
Command Mode
Global Configuration
Example
Console(config)#mac-authentication max-age 180
Console(config)#
15-6
© 2007 Foundry Networks, Inc.
March 2007
Multi-Device Port Authentication
Related Commands
mac-authentication (15-3)
mac-authentication
Use this command to enable Multi-Device Port Authentication on a per port basis. Use the no form of
this command to restore the default.
Syntax
[no] mac-authentication
Default Setting
Disabled
Command Mode
Interface Configuration
Example
Console(config)#interface ethernet 1/5
Console(config-if)#mac-authentication
Console(config-if)#
Related Commands
mac-authentication (15-3)
mac-authentication auth-fail-action
Use this command to specify what action to take when Multi-Device Port Authentication fails. Use the
no form of this command to restore the default.
Syntax
[no] mac-authentication auth-fail-action {restrict-vlan [vlan-id] | block-traffic}
• restrict-vlan - Moves the port to a restricted VLAN.
• vlan-id - The VLAN ID.
• block-traffic - Drops traffic from the MAC address.
Default Setting
Block-traffic
Command Mode
Interface Configuration
Example
Console(config)#interface ethernet 1/5
Console(config-if)#mac-authentication auth-fail-action restrict-vlan 2
Console(config-if)#
December 2007
© 2007 Foundry Networks, Inc.
15-7
Foundry EdgeIron User Guide
Related Commands
mac-authentication (15-3)
mac-authentication apply-mac-auth-filter
Use this command to apply the MAC address filter on an interface. Use the no form of this command
to restore the default.
Syntax
[no] mac-authentication apply-mac-auth-filter filter-id
filter-id - The filter ID. (Range: 1-64)
Default Setting
None
Command Mode
Interface Configuration
Example
The following example applies filter 1 to port 5.
Console(config)#interface ethernet 1/5
Console(config-if)#mac-authentication apply-mac-auth-filter 1
Console(config-if)#
Related Commands
mac-authentication (15-3)
mac-authentication enable-dynamic-vlan
Use this command to enable dynamic VLAN assignment for authenticated MAC addresses. Use the
no form of this command to restore the default.
Syntax
[no] mac-authentication enable-dynamic-vlan
Default Setting
Disabled
Command Mode
Interface Configuration
Example
The following example enables dynamic VLAN assignment on port 9.
Console(config)#interface ethernet 1/9
Console(config-if)#mac-authentication enable-dynamic-vlan
Console(config-if)#
15-8
© 2007 Foundry Networks, Inc.
March 2007
Multi-Device Port Authentication
Related Commands
mac-authentication (15-3)
mac-authentication move-back-to-old-vlan
Use this command to specify an alternate VLAN to which to move the port when the MAC session for
the address is deleted. Use the no form of this command to restore the default.
Syntax
[no] mac-authentication move-back-to-old-vlan {disable | port-configured-vlan |
port-restrict-vlan | system-default-vlan}
• disable - Moves the port back to its original VLAN. The port would stay in its RADIUS-assigned
VLAN.
• port-configured-vlan - Removes the port from its RADIUS-assigned VLAN and places the port
back in the VLAN where it was originally assigned.
• port-restrict-vlan - Removes the port from its RADIUS-assigned VLAN and places the port in
the restricted VLAN.
• system-default-vlan - Removes the port from its RADIUS-assigned VLAN and places the port
in the default VLAN.
Default Setting
Port-configured-vlan
Command Mode
Interface Configuration
Example
The following example moves port 9 to the system default VLAN when the RADIUS-authenticated
MAC address is deleted.
Console(config)#interface ethernet 1/9
Console(config-if)#mac-authentication move-back-to-old-vlan system-default-vlan
Console(config-if)#
Related Commands
mac-authentication (15-3)
mac-authentication clear-mac-session
Use this command to clear an authenticated MAC session on an interface.
Syntax
mac-authentication clear-mac-session mac-address
mac-address - MAC address
Command Mode
Global Configuration
December 2007
© 2007 Foundry Networks, Inc.
15-9
Foundry EdgeIron User Guide
Example
The following example clears the authenticated MAC address 00-00-3D-12-23-C4 on port 9.
Console(config)#interface ethernet 1/9
Console(config-if)#mac-authentication clear-mac-session 00-00-3D-12-23-C4
Console(config-if)#
Related Commands
mac-authentication (15-3)
mac-authentication clear-auth-mac-table
Use this command to clear all authenticated MAC sessions on an interface.
Syntax
mac-authentication clear-mac-session
Command Mode
Interface Configuration
Example
The following example clears all authenticated MAC addresses on port 5.
Console(config)#interface ethernet 1/5
Console(config-if)#mac-authentication clear-auth-mac-table
Console(config-if)#
Related Commands
mac-authentication (15-3)
mac-authentication disable-aging
Use this command to disable aging for authenticated MAC addresses on an interface. Use the no
form of this command to restore the default aging time.
Syntax
[no] mac-authentication clear-mac-session
Default Setting
Enabled
Command Mode
Interface Configuration
Example
The following example disables aging for authenticated MAC addresses on port 5.
Console(config)#interface ethernet 1/5
Console(config-if)#mac-authentication disable-aging
Console(config-if)#
15-10
© 2007 Foundry Networks, Inc.
March 2007
Multi-Device Port Authentication
Related Commands
mac-authentication (15-3)
clear auth-mac-table
Use this command to clear the entire contents of the authenticated MAC address table.
Syntax
clear auth-mac-table
Command Mode
Privileged Exec
Example
Console#clear auth-mac-table
Console#
Related Commands
mac-authentication (15-3)
show auth-mac-address
Use this command to display information on authenticated MAC addresses on the ports where MultiDevice Port Authentication in enabled.
Syntax
show auth-mac-address
Command Mode
Privileged Exec
Example
Console#show auth-mac-address
-------------------------------------------------------------Port
Vlan
Accepted MACs
Rejected MACs
Attempted-MACs
-------------------------------------------------------------1/18
100
1
100
0
1/20
40
0
0
0
1/22
100
0
0
0
2/3
30
0
0
0
Console#
Related Commands
mac-authentication (15-3)
show auth-mac-address configuration
Use this command to display information on the Multi-Device Port Authentication configuration.
Syntax
show auth-mac-address configuration
December 2007
© 2007 Foundry Networks, Inc.
15-11
Foundry EdgeIron User Guide
Command Mode
Privileged Exec
Example
Console#show auth-mac-address configuration
Feature enabled: Yes
Number of Ports enabled: 4
-------------------------------------------------------------Port
Fail-Action
Fail-vlan
Dyn-vlan
MAC-filter
-------------------------------------------------------------1/18
Block Traffic 1
No
No
1/20
Block Traffic 1
No
No
1/22
Block Traffic 1
No
Yes
2/3
Block Traffic 1
No
No
Console#
Related Commands
mac-authentication (15-3)
show auth-mac-address
Use this command to display information on the Multi-Device Port Authentication information for a
specific MAC address or port.
Syntax
show auth-mac-address {mac-address | interface}
• mac-address - MAC address.
• interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
Command Mode
Privileged Exec
Example
Console#show auth-mac-address 00-00-01-02-03-04
----------------------------------------------------------------MAC
Port
Vlan Authenticated
Time
Age
----------------------------------------------------------------00-01-02-03-04 1/18
Yes
00d01h10m06s 0
Console#
Related Commands
mac-authentication (15-3)
15-12
© 2007 Foundry Networks, Inc.
March 2007
Multi-Device Port Authentication
show auth-mac-address detail
Use this command to display detailed information on Multi-Device Port Authentication settings and
authenticated MAC addresses for a port where this feature is enabled.
Syntax
show auth-mac-address detail interface
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
Command Mode
Privileged Exec
Example
Console#show auth-mac-address detail ethernet 1/18
Port: 1/18
Dynamic-Vlan Assignment
:Disabled
RADIUS failure action
:Block Traffic
Override-restrict-vlan
:No
Vlan
:100 (RADIUS assigned: No)
Accepted Mac Addresses
:1
Rejected Mac Addresses
:100
Authentication in progress :0
Authentication attempts
:0
RADIUS timeouts
:61250
Aging of MAC-sessions
:Enabled
Max-Age of MAC-sessions
:120 seconds
MAC Filter applied
:No
-------------------------------------------------------------------MAC
RADIUS Server
Authenticated Time
Age
-------------------------------------------------------------------00-00-01-02-03-04 172.155.120.17 No
00d06h32m50s
224
00-00-01-02-03-04 172.155.120.17 No
00d06h32m50s
225
00-00-01-02-03-04 172.155.120.17 No
00d06h34m10s
216
00-00-01-02-03-04 172.155.120.17 No
00d06h34m50s
212
Console#
Related Commands
mac-authentication (15-3)
show auth-mac-address authorized-mac
Use this command to display MAC addresses that have been successfully authenticated.
Syntax
show auth-mac-address authorized-mac
Command Mode
Privileged Exec
Example
Console#show auth-mac-address authorized-mac
-------------------------------------------------------------------Port
MAC
-------------------------------------------------------------------1/1
00-00-01-02-03-04
Console#
December 2007
© 2007 Foundry Networks, Inc.
15-13
Foundry EdgeIron User Guide
Related Commands
mac-authentication (15-3)
show auth-mac-address unauthorized-mac
Use this command to display MAC addresses for which authentication was not successful.
Syntax
show auth-mac-address unauthorized-mac
Command Mode
Privileged Exec
Example
Console#show auth-mac-address unauthorized-mac
-------------------------------------------------------------------Port
MAC
-------------------------------------------------------------------1/1
00-00-051-06-07-07
Console#
Related Commands
mac-authentication (15-3)
15-14
© 2007 Foundry Networks, Inc.
March 2007
Chapter 16
IP Filtering
You can specify the client IP addresses that are allowed management access to the switch through
the web interface, SNMP, or Telnet.
•
The management interfaces are open to all IP addresses by default. Once you add an entry to a
filter list, access to that interface is restricted to the specified addresses.
•
If anyone tries to access a management interface on the switch from an invalid address, the
switch will reject the connection, enter an event message in the system log, and send a trap
message to the trap manager.
•
IP addresses can be configured for SNMP, web and Telnet access respectively. Each of these
groups can include up to five different sets of addresses, either individual addresses or address
ranges.
•
When entering addresses for the same group (i.e., SNMP, web or Telnet), the switch will not
accept overlapping address ranges. When entering addresses for different groups, the switch will
accept overlapping address ranges.
•
You cannot delete an individual address from a specified range. You must delete the entire range,
and reenter the addresses.
•
You can delete an address range just by specifying the start address, or by specifying both the
start address and end address.
Command Attributes
• Web IP Filter – Configures IP address(es) for the web group.
•
SNMP IP Filter – Configures IP address(es) for the SNMP group.
•
Telnet IP Filter – Configures IP address(es) for the Telnet group.
•
IP Filter List – IP addresses that are allowed management access to this interface.
•
Start IP Address – A single IP address, or the starting address of a range.
•
End IP Address – The end address of a range.
Note: This feature is available on devices running software Release 2.2.5.18 and later.
December 2007
© 2007 Foundry Networks, Inc.
16-1
Foundry EdgeIron User Guide
The CLI commands for this section are briefly described in the table that follows:
Command
Function
Mode
Page
management
Configures IP addresses that are allowed management
access
GC
16-2
show management
Displays the client IP addresses that are allowed
management access to the switch through various
protocols.
PE
16-4
USING THE WEB INTERFACE
Click Security, IP Filter. Enter the addresses that are allowed management access to an interface,
and click Add IP Filtering Entry.
USING THE CLI
Use the following command to enable IP filtering using the CLI.
management
This command specifies the client IP addresses that are allowed management access to the switch
through various protocols. Use the no form to restore the default setting.
Syntax
[no] management {all-client | http-client | snmp-client | telnet-client} start-address [endaddress]
• all-client - Adds IP address(es) to the SNMP, web and Telnet groups.
• http-client - Adds IP address(es) to the web group.
• snmp-client - Adds IP address(es) to the SNMP group.
• telnet-client - Adds IP address(es) to the Telnet group.
• start-address - A single IP address, or the starting address of a range.
• end-address - The end address of a range.
16-2
© 2007 Foundry Networks, Inc.
March 2007
IP Filtering
Default Setting
All addresses
Command Mode
Global Configuration
Command Usage
• If anyone tries to access a management interface on the switch from an invalid address, the
switch will reject the connection, enter an event message in the system log, and send a trap
message to the trap manager.
• IP address can be configured for SNMP, web and Telnet access respectively. Each of these
groups can include up to five different sets of addresses, either individual addresses or address
ranges.
• When entering addresses for the same group (i.e., SNMP, web or Telnet), the switch will not
accept overlapping address ranges. When entering addresses for different groups, the switch will
accept overlapping address ranges.
• You cannot delete an individual address from a specified range. You must delete the entire range,
and reenter the addresses.
• You can delete an address range just by specifying the start address, or by specifying both the
start address and end address.
Example
This example restricts management access to the indicated addresses.
Console(config)#management all-client 192.168.1.19
Console(config)#management all-client 192.168.1.25 192.168.1.30
Console(config)#
This example restricts management access for Telnet and SNMP clients.
Console(config)#management telnet-client 192.168.1.19
Console(config)#management telnet-client 192.168.1.25 192.168.1.30
Console(config)#management snmp-client 10.1.2.3 255.255.255.255
Console(config)#end
Console#show management telnet-client
Management IP Filter
TELNET-Client:
Start IP address
End IP address
----------------------------------------------1. 192.168.1.19
192.168.1.19
2. 192.168.1.25
192.168.1.30
Console#show management snmp-client
Management IP Filter
SNMP-Client:
Start IP address
End IP address
----------------------------------------------1. 10.1.2.3
255.255.255.255
Console#
December 2007
© 2007 Foundry Networks, Inc.
16-3
Foundry EdgeIron User Guide
show management
This command displays the client IP addresses that are allowed management access to the switch
through various protocols.
Syntax
show management {all-client | http-client | snmp-client | telnet-client}
• all-client - Adds IP address(es) to the SNMP, web and Telnet groups.
• http-client - Adds IP address(es) to the web group.
• snmp-client - Adds IP address(es) to the SNMP group.
• telnet-client - Adds IP address(es) to the Telnet group.
Command Mode
Privileged Exec
Example
Console#show management all-client
Management Ip Filter
Http-Client:
Start ip address
End ip address
----------------------------------------------1. 192.168.1.19
192.168.1.19
2. 192.168.1.25
192.168.1.30
Snmp-Client:
Start ip address
End ip address
----------------------------------------------1. 192.168.1.19
192.168.1.19
2. 192.168.1.25
192.168.1.30
Telnet-Client:
Start ip address
End ip address
----------------------------------------------1. 192.168.1.19
192.168.1.19
2. 192.168.1.25
192.168.1.30
Console#
16-4
© 2007 Foundry Networks, Inc.
March 2007
Chapter 17
Interface Commands
These commands are used to display or set communication parameters for an Ethernet port,
aggregated link, or VLAN.
The CLI commands for this section are briefly described in the table that follows:
Command
Function
Mode
mdix auto
Enables the automatic medium-dependent interface
crossover (Auto-MDIX) feature on the interface.
IC
17-3
port-channel loadbalance
Configures which active link in a trunk should forward
the packets.
GC
17-4
show interfaces
ethernet
to display the administrative and operational status of
specified interfaces.
NE, PE
17-5
show interfaces brief
Use this command to display the link and connection
status of the switches interfaces.
NE, PE
17-6
interface
Configures an interface type and enters interface
configuration mode
GC
17-13
channel-group
Adds a port to a trunk
IC
17-13
description
Adds a description to an interface configuration
IC
17-14
speed-duplex
Configures the speed and duplex operation of a given
interface when auto-negotiation is disabled
IC
17-14
negotiation
Enables auto-negotiation of a given interface
IC
17-15
capabilities
Advertises the capabilities of a given interface for use in
auto-negotiation
IC
17-16
flowcontrol
Enables flow control on a given interface
IC
17-17
combo-forced-mode
Forces the port type for a combination port
IC
17-18
giga-phy-mode
Forces two connected ports into a master/slave
configuration, to enable gigabit speed
IC
17-18
shutdown
Disables an interface
IC
17-19
switchport broadcast
Configures broadcast storm control
IC
17-25
port security
Enables port security on an interface.
IC
17-20
port security aging
Learns secure address entries for all ports.
GC
17-21
December 2007
© 2007 Foundry Networks, Inc.
Page
17-1
Foundry EdgeIron User Guide
Command
Function
port security autosave Automatically saves learned secure MAC addresses to
the startup configuration file.
Mode
Page
GC
17-22
port security
(EdgeIron
2402CF/4802CF)
Enables port security on an interface.
IC
17-20
show port security
Displays port security settings.
GC
17-23
clear counters
Clears statistics on an interface
PE
17-19
show interfaces status
Displays status for the specified interface
NE, PE
17-7
show interfaces
counters
Displays statistics for the specified interface
NE, PE
17-7
show interfaces
switchport
Displays the administrative and operational status of an
interface
NE, PE
17-10
port monitor
Configures a mirror session
IC
17-27
show port monitor
Shows the configuration for a mirror port
PE
17-28
rate-limit
Configures the maximum input or output rate for an
interface
IC
17-30
show interfaces
counters
Displays statistics for the specified interface
NE, PE
Port Mirroring
Rate Limiting
17-2
© 2007 Foundry Networks, Inc.
17-7
March 2007
Interface Commands
Displaying Interfaces Status
Displaying Connection Status
You can use the Port Information or Trunk Information pages to display the current connection status,
including link state, speed/duplex mode, flow control, and auto-negotiation.
USING THE WEB INTERFACE
Click Port, Port Information or Trunk Information. Modify the required interface settings, and click
Apply.
•
Name – Interface label.
•
Type – Indicates the of port type (100Base-TX, 1000Base-TX or 1000Base-SFP).
•
Admin Status – Shows if the interface is enabled or disabled.
•
Oper Status – Indicates if the link is Up or Down.
•
Speed/Duplex Status – Shows the current speed and duplex mode.
•
Flow Control Status – Indicates the type of flow control currently in use.
•
Autonegotiation – Shows if auto-negotiation is enabled or disabled.
•
Trunk Member – Shows if port is a trunk member. (Port Information only.)
•
Creation – Shows if a trunk is manually configured or dynamically set via LACP. (Trunk
Information only.)
USING THE CLI
Use the commands in this section to display interface settings from the CLI.
mdix auto
This command enables the automatic medium-dependent interface crossover (Auto-MDIX) feature
on the interface. When Auto-MDIX is enabled, the interface automatically detects the required cable
December 2007
© 2007 Foundry Networks, Inc.
17-3
Foundry EdgeIron User Guide
connection type (straight-through or crossover) and configures the connection appropriately. Use the
no form of this command to disable Auto-MDIX.
Syntax
mdix auto
no mdix auto
Default Setting
Enabled
Command Mode
Interface Configuration (Ethernet)
Command Usage
•
The no form of this command is only applicable for the fast Ethernet ports on the EdgeIron
2402CF and 4802CF. This feature cannot be disabled on Gigabit Ethernet ports of the
2402CF and 4802CF. Also, the feature cannot be disabled on the 24G-A, 48G, 24GS, 48GS
or 8X10G.
•
If this feature is disabled on the 2402CF and 4802CF Fast Ethernet ports, the user must use
cross-over cable for interface connections. If this feature is enabled the user can use crossover or straight-through cable for interface connections.
Example
Console(config)#interface ethernet 1/5
Console(config-if)#mdix autoConsole(config-if)#
port-channel load-balance
Use this command to configure which active link in a trunk should forward the packets.
Note: This command is available on EdgeIron 2402CF, 4802CF, 24G-A and 48G running release
2.2.6.19 and later.
Syntax
port-channel load-balance {dst-ip | dst-mac | src-dst-ip | src-dst-mac | src-ip | src-mac}
•
•
•
•
•
•
dst-ip - Selection based on destination IP address.
dst-mac - Selection based on destination MAC address.
src-dst-ip - Selection based on source and destination IP address.
src-dst-mac - Selection based on source and destination MAC address.
src-ip - Selection based on source IP address.
src-mac - Selection based on source MAC address.
Default Setting
None
Command Mode
Global Configuration
17-4
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
Example
Console(config)#port-channel load-balance dst-ip
Console(config)#
show interfaces ethernet
Use this command to display the administrative and operational status of specified interfaces.
Syntax
show interfaces [ethernet [interface]}
interface
• unit - This is device 1.
• port - Port number.
Default Setting
Shows all interfaces.
Command Mode
Normal Exec, Privileged Exec
Command Usage
If no interface is specified, information on all interfaces is displayed. The items displayed by this
command include:
• Link status - Shows if the link is up or down.
• MAC address - Shows the switches MAC address.
• Connection status - Shows link status, speed and duplex mode.
• Native VLAN – Indicates the default Port VLAN ID, whether port is tagged or untagged and port
state.
• STP - Shows if STP is enabled.
• Mirror - Shows if port mirroring is enabled.
• Trunk membership - Indicates if the port is a member of any active or configured trunks.
• Flow control - Shows if flow control is enabled or disabled.
• Port name - Shows if port has been named.
• Utilization - Shows percentage port utilization.
• Statistics - Displays received and transmitted packet statistics; including broadcasts,
multicasts, unicast, input errors, CRC, ignore, giants, packets output, bytes, output errors and
collisions.
December 2007
© 2007 Foundry Networks, Inc.
17-5
Foundry EdgeIron User Guide
Example
This example shows the configuration setting for Ethernet port 1.
Console#show interfaces ethernet 1/1
GigabitEthernet1 is down, line protocol is up
Hardware is GigabitEthernet, address is 0004.80bd.474e (bia 0004.80bd.474e)
Configured speed auto, actual unknown, configured duplex fdx, actual unknown
Member of L2 VLAN ID 1, port is untagged, port state is BLOCKING
STP configured to ON, priority is level0, flow control disabled
mirror disabled, monitor disabled
Not member of any active trunks
Not member of any configured trunks
No port name
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
Received 0 broadcasts, 0 multicasts, 0 unicasts
0 input errors, 0 CRC, 0 ignore
0 giants
0 packets output, 0 bytes
Transmitted 0 broadcast, 0 multicasts, 0 unicasts
0 output errors, 0 collisions
Console#
show interfaces brief
Use this command to display the link and connection status of the switches interfaces.
Syntax
show interfaces brief
Default Setting
Shows all interfaces.
Command Mode
Normal Exec, Privileged Exec
Command Usage
Information on all interfaces is displayed. The items displayed by this command include:
• Link - Shows if the link is up or down.
• State - Shows what state the port is in.
• Dupl - Shows if switch is operating in half-duplex or full-duplex mode.
• Speed - Shows the connection speed.
• Trunk - Indicates if the port is a member of any active or configured trunks.
• Tag - Shows if this is a tagged port or not.
• Priori - Shows the priority level of the port.
• MAC - Shows the switches MAC address.
• Name - Shows if port has been named.
Example
Console#show interfaces
Port Link State
Dupl
---- ---- -------- ---1/1 Down None
None
1/2 Up
Forward Full
.
.
.
1/24 Down None
None
Console#
17-6
ethernet 1/1
Speed Trunk Tag
----- ----- --None None No
100M None No
Priori
-----level0
level0
None
level0 00-04-80-BD-47-65
None
No
MAC
Name(15)
----------------- -------------00-04-80-BD-47-4E
00-04-80-BD-47-4F
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
show interfaces status
Use this command to display the status for an interface.
Syntax
show interfaces status interface
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
• vlan vlan-id (Range: 1-4094)
Default Setting
Shows the status for all interfaces.
Command Mode
Normal Exec, Privileged Exec
Command Usage
• If no interface is specified, information on all interfaces is displayed.
• For a description of the items displayed by this command, see “Displaying Connection Status” on
page 17-3.
Example
Console#show interface status ethernet 1/1
Information of Eth 1/1
Basic information:
Port type: 100TX
Mac address: 00-01-F4-88-F5-21
Configuration:
Name:
Port admin: Up
Speed-duplex: Auto
Capabilities: 10half, 10full, 100half, 100full
Broadcast storm: Enabled
Broadcast storm limit: 500 packets/second
Flow control: Disabled
LACP: Disabled
Port security: Disabled
Max MAC count: 0
Port security action: None
Current status:
Link status: Down
Operation speed-duplex: 100full
Flow control type: None
Console#
show interfaces counters
Use this command to display statistics for an interface.
Note: This command is available on devices running release 2.2.4.11 and later.
December 2007
© 2007 Foundry Networks, Inc.
17-7
Foundry EdgeIron User Guide
Syntax
show interfaces counters [interface | brief]
• interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
• brief - Displays brief information for all ports.
Default Setting
Shows the counters for all interfaces.
Command Mode
Normal Exec, Privileged Exec
Command Usage
• If no interface is specified, information on all interfaces is displayed.
• For a description of the items displayed by this command, see “Showing Device Statistics” on
page 17-31.
Example
Console#show interfaces counters ethernet 1/7
Ethernet 1/ 7
Iftable stats:
Octets input: 30658, Octets output: 196550
Unicast input: 6, Unicast output: 5
Discard input: 0, Discard output: 0
Error input: 0, Error output: 0
Unknown protos input: 0, QLen output: 0
Extended iftable stats:
Multi-cast input: 0, Multi-cast output: 3064
Broadcast input: 262, Broadcast output: 1
Ether-like stats:
Alignment errors: 0, FCS errors: 0
Single Collision frames: 0, Multiple collision frames: 0
SQE Test errors: 0, Deferred transmissions: 0
Late collisions: 0, Excessive collisions: 0
Internal mac transmit errors: 0, Internal mac receive errors: 0
Frame too longs: 0, Carrier sense errors: 0
Symbol errors: 0
RMON stats:
Drop events: 0, Octets: 227208, Packets: 3338
Broadcast pkts: 263, Multi-cast pkts: 3064
Undersize pkts: 0, Oversize pkts: 0
Fragments: 0, Jabbers: 0
CRC align errors: 0, Collisions: 0
Packet size <= 64 octets: 3150, Packet size 65 to 127 octets: 139
Packet size 128 to 255 octets: 49, Packet size 256 to 511 octets: 0
Packet size 512 to 1023 octets: 0, Packet size 1024 to 1518 octets: 0
Console#
17-8
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
This example displays brief information for all ports.
Console#show interfaces counters brief
Ethernet
Packets
Collision
Port
[Receive Transmit]
[Receive]
1/ 1
0
0
0
1/ 2
0
0
0
1/ 3
0
0
0
1/ 4
0
0
0
1/ 5
0
0
0
1/ 6
0
0
0
1/ 7
0
0
0
1/ 8
0
0
0
1/ 9
0
0
0
1/10
0
0
0
1/11
0
0
0
1/12
0
0
0
1/13
0
0
0
1/14
0
0
0
1/15
0
0
0
1/16
0
0
0
1/17
0
0
0
1/18
0
0
0
1/19
0
0
0
1/20
0
0
0
1/21
0
0
0
1/22
0
0
0
1/23
27
819
0
1/24
0
0
0
Console#
December 2007
Errors
[Input Output]
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
0
0
0
© 2007 Foundry Networks, Inc.
17-9
Foundry EdgeIron User Guide
show interfaces switchport
Use this command to display the administrative and operational status of specified interfaces.
Syntax
show interfaces switchport [interface]
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
Default Setting
Shows all interfaces.
Command Mode
Normal Exec, Privileged Exec
Command Usage
If no interface is specified, information on all interfaces is displayed. The items displayed by this
command include:
• Broadcast threshold – Shows if broadcast storm suppression is enabled or disabled; if
enabled it also shows the threshold level. (See “switchport broadcast” on page 17-25).
• Lacp status – Shows if Link Aggregation Control Protocol has been enabled or disabled.
(See “show lacp” on page 18-9.)
• Dual-mode – Indicates if Dual Mode has been enabled.
• VLAN membership mode – Indicates membership mode as Trunk or Hybrid. (See “802.1Q
VLANs” on page 22-1).
• Ingress rule – Shows if ingress filtering is enabled or disabled.
• Acceptable frame type – Shows if acceptable VLAN frames include all types or tagged frames
only. (See “Forwarding Tagged/Untagged Frames” on page 22-4.)
• Native VLAN – Indicates the default Port VLAN ID. (See “802.1Q VLANs” on page 22-1.)
• Priority for untagged traffic – Indicates the default priority for untagged frames. (See
“Mapping Layer 3/4 Priorities to CoS Values” on page 25-9.)
• Gvrp status – Shows if GARP VLAN Registration Protocol is enabled or disabled. (See
“Enabling or Disabling GVRP (Global Setting)” on page 22-4.)
• Allowed Vlan – Shows the VLANs this interface has joined, where “(u)” indicates untagged and
“(t)” indicates tagged (See “show interfaces status” on page 22-22.)
• Forbidden Vlan – Shows the VLANs this interface can not dynamically join via GVRP.
(See “Displaying Basic VLAN Information” on page 22-5.)
17-10
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
Example
This example shows the configuration setting for Ethernet port 15.
Console#show interfaces switchport ethernet 1/15
Information of Eth 1/15
Broadcast threshold: Enabled, 500 packets/second
LACP status: Disabled
Dual-mode: Disabled
Ingress rate limit: disable,100M bits per second
Egress rate limit: disable,100M bits per second
VLAN membership mode: Hybrid
Ingress rule: Disabled
Acceptable frame type: All frames
Priority for untagged traffic: 0
GVRP status: Disabled
Allowed VLAN:
1(u),
Forbidden VLAN:
Console#
Configuring Interface Connections
You can use the Trunk Configuration or Port Configuration page to enable/disable an interface,
manually fix the speed and duplex mode, set flow control, set auto-negotiation, and set the interface
capabilities to advertise.
USING THE WEB INTERFACE
Click Port, Port Configuration or Trunk Configuration. Modify the required interface settings, and click
Apply.
•
Name – Allows you to label an interface. (Range: 1-64 characters)
•
Admin – Allows you to manually disable an interface. You can disable an interface due to
abnormal behavior (e.g., excessive collisions), and then reenable it after the problem has been
resolved. You may also disable an interface for security reasons.
•
Speed/Duplex – Allows manual selection of port speed and duplex mode (i.e., with autonegotiation disabled).
•
Flow Control – Allows automatic or manual selection of flow control.
December 2007
© 2007 Foundry Networks, Inc.
17-11
Foundry EdgeIron User Guide
•
Autonegotiation/Port Capabilities – Allows auto-negotiation to be enabled/disabled. Specifies
the capabilities to be advertised for a port during auto-negotiation. The following capabilities are
supported.
-
10half - Supports 10 Mbps half-duplex operation
10full - Supports 10 Mbps full-duplex operation
100half - Supports 100 Mbps half-duplex operation
100full - Supports 100 Mbps full-duplex operation
1000full - Supports 1000 Mbps full-duplex operation
Sym (Gigabit only) - Check this item to transmit and receive pause frames, or clear it to autonegotiate the sender and receiver for asymmetric pause frames. (Only symmetric pause frames
are supported.)
- FC - Supports flow control
Flow control can eliminate frame loss by “blocking” traffic from end stations or segments
connected directly to the switch when its buffers fill. When enabled, back pressure is used for
half-duplex operation and IEEE 802.3x for full-duplex operation. (Avoid using flow control on a
port connected to a hub unless it is actually required to solve a problem. Otherwise back
pressure jamming signals may degrade overall performance for the segment attached to the
hub.)
Default: Auto-negotiation enabled; Advertised capabilities for 100BASE-TX – 10half, 10full,
100half, 100full; 1000BASE-T – 10half, 10full, 100half, 100full, 1000full;
1000BASE-SX/LX/LH – 1000full)
Note: Due to a hardware limitation, flow control only works on those ports located in the same chip
(ports 1-24, 49 and ports 25-48, 50). Cross-chip flow control does not work.
•
Forced Mode – Indicates if a port or trunk has been set to forced mode.
•
Trunk – Indicates if a port is a member of a trunk. To create trunks and select port members, see
Chapter 26 “Multicast Configuration.”
Note: Auto-negotiation must be disabled before you can configure or force the interface to use the
Speed/Duplex Mode or Flow Control options.
17-12
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
USING THE CLI
Use the commands in this section to configure interface settings from the CLI.
interface
Use this command to configure an interface type and enter interface configuration mode. Use the no
form to remove a trunk.
Syntax
interface interface
no interface port-channel channel-id
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
• vlan vlan-id (Range: 1-4094)
Default Setting
None
Command Mode
Global Configuration
Example
To specify the Ethernet port, enter the following command:
Console(config)#interface ethernet 1/25
Console(config-if)#
channel-group
Use this command to add a port to a trunk. Use the no form to remove a port from a trunk.
Syntax
channel-group channel-id
no channel-group
channel-id - Trunk index (Range: 1-6)
Default Setting
A new trunk contains no ports.
Command Mode
Interface Configuration (Ethernet)
Command Usage
• Static trunks have to be manually configured at both ends of the link.
• Use no channel-group to remove a port group from a trunk.
December 2007
© 2007 Foundry Networks, Inc.
17-13
Foundry EdgeIron User Guide
• Use no interfaces port-channel to remove a trunk from the switch.
• All links in a trunk must operate at the same data rate and duplex mode.
Example
The following example creates trunk 1 and then adds port 11:
Console(config)#interface port-channel 1
Console(config-if)#exit
Console(config)#interface ethernet 1/11
Console(config-if)#channel-group 1
Console(config-if)#
description
Use this command to add a description to an interface. Use the no form to remove the description.
Syntax
description string
no description
string - Comment or a description to help you remember what is attached to this interface.
(Range: 1-64 characters)
Default Setting
None
Command Mode
Interface Configuration (Ethernet, Port Channel)
Example
The following example adds a description to Ethernet port 15.
Console(config)#interface ethernet 1/15
Console(config-if)#description RD-SW#3
Console(config-if)#
speed-duplex
Use this command to configure the speed and duplex mode of a given interface when autonegotiation is disabled. Use the no form to restore the default.
Syntax
speed-duplex {1000full | 100full | 100half | 10full | 10half}
no speed-duplex
• 1000full - Forces 1000 Mbps full-duplex operation
(Not supported on the EdgeIron 2402CF and the EdgeIron 4802CF)
• 100full - Forces 100 Mbps full-duplex operation
• 100half - Forces 100 Mbps half-duplex operation
• 10full - Forces 10 Mbps full-duplex operation
• 10half - Forces 10 Mbps half-duplex operation
17-14
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
Default Setting
• Auto-negotiation is enabled by default.
• When auto-negotiation is disabled, the default speed-duplex setting is 1000full for Gigabit
Ethernet ports.
• For the EdgeIron 2402CF and EdgeIron 4802CF the default is 100full.
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
• To force operation to the speed and duplex mode specified in a speed-duplex command, use the
no negotiation command to disable auto-negotiation on the selected interface.
• When using the negotiation command to enable auto-negotiation, the optimal settings will be
determined by the capabilities command. To set the speed/duplex mode under auto-negotiation,
the required mode must be specified in the capabilities list for an interface.
• After you configure 1000full on both sides of the link, on the EdgeIron side you need to re-enable
negotiation, disable it again, and configure 1000full again in order for the link to work.
Example
The following example configures port 5 (on the EdgeIron 24G-A or 48G) to 1000 Mbps, full-duplex
operation, master mode.
Console(config)#interface ethernet 1/5
Console(config-if)#speed-duplex 1000full
Console(config-if)#giga-phy-mode master
Console(config-if)#no negotiation
The following example configures port 5 (on the EdgeIron 24G-A or 48G) to 1000 Mbps, full-duplex
operation, slave mode.
Console(config)#interface ethernet 1/5
Console(config-if)#no negotiation
Console(config-if)#speed 1000full
Console(config-if)#giga-phy-mode slave
Related Commands
negotiation (17-15)
capabilities (17-16)
negotiation
Use this command to enable auto-negotiation for a given interface. Use the no form to disable autonegotiation.
Syntax
negotiation
no negotiation
Default Setting
Enabled
Command Mode
Interface Configuration (Ethernet, Port Channel)
December 2007
© 2007 Foundry Networks, Inc.
17-15
Foundry EdgeIron User Guide
Command Usage
• When auto-negotiation is enabled the switch will negotiate the best settings for a link based on
the capabilities command. When auto-negotiation is disabled, you must manually specify the link
attributes with the speed-duplex and flowcontrol commands.
• If auto-negotiation is disabled, auto-MDI/MDI-X pin signal configuration will also be disabled for
the RJ-45 ports.
Note: Auto MDI/MDIX cannot work at forced mode.
Example
The following example configures port 11 to use auto-negotiation.
Console(config)#interface ethernet 1/11
Console(config-if)#negotiation
Related Commands
capabilities (17-16)
speed-duplex (17-14)
flowcontrol (17-17)
capabilities
Use this command to advertise the port capabilities of a given interface during auto-negotiation. Use
the no form with parameters to remove an advertised capability, or the no form without parameters
to restore the default values.
Syntax
capabilities {1000full | 100full | 100half | 10full | 10half | flowcontrol | symmetric}
no port-capabilities [1000full | 100full | 100half | 10full | 10half | flowcontrol | symmetric]
• 1000full - Supports 1000 Mbps full-duplex operation
• 100full - Supports 100 Mbps full-duplex operation
• 100half - Supports 100 Mbps half-duplex operation
• 10full - Supports 10 Mbps full-duplex operation
• 10half - Supports 10 Mbps half-duplex operation
• flowcontrol - Supports flow control
• symmetric (Gigabit only) - When specified, the port transmits and receives pause frames;
when not specified, the port will auto-negotiate to determine the sender and receiver for
asymmetric pause frames. (The current switch ASIC only supports symmetric pause frames.)
Note: Flow control setting applies only to forced-mode configuration. The auto-negotiation behavior
is dependent on a port’s capability setting.
Default Setting
• 100BASE-TX: 10half, 10full, 100half, 100full
• 1000BASE-T: 10half, 10full, 100half, 100full, 1000full
• 1000BASE-SX/LX/LH: 1000full
17-16
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
When auto-negotiation is enabled with the negotiation command, the switch will negotiate the
best settings for a link based on the capabilities command. When auto-negotiation is disabled,
you must manually specify the link attributes with the speed-duplex and flowcontrol commands.
Example
The following example configures Ethernet port 5 capabilities to 100half, 100full and flow control.
Console(config)#interface ethernet 1/5
Console(config-if)#capabilities 100half
Console(config-if)#capabilities 100full
Console(config-if)#capabilities flowcontrol
Console(config-if)#
Related Commands
speed-duplex (17-14)
negotiation (17-15)
flowcontrol (17-17)
flowcontrol
Use this command to enable flow control. Use the no form to disable flow control.
Syntax
flowcontrol
no flowcontrol
Default Setting
Flow control enabled
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
• Flow control can eliminate frame loss by “blocking” traffic from end stations or segments
connected directly to the switch when its buffers fill. When enabled, back pressure is used for halfduplex operation and IEEE 802.3x for full-duplex operation.
• When using the negotiation command to enable auto-negotiation, the optimal settings will be
determined by the capabilities command. To enable flow control under auto-negotiation,
“flowcontrol” must be included in the capabilities list for any port.
• To force flow control on or off (with the flowcontrol or no flowcontrol command), use the no
negotiation command to disable auto-negotiation on the selected interface.
• Avoid using flow control on a port connected to a hub unless it is actually required to solve a
problem. Otherwise back pressure jamming signals may degrade overall performance for the
segment attached to the hub.
• Due to a hardware limitation, flow control only works on those ports located in the same chip (ports
1-24, 49 and ports 25-48, 50). Cross-chip flow control does not work.
December 2007
© 2007 Foundry Networks, Inc.
17-17
Foundry EdgeIron User Guide
Example
The following example enables flow control on port 5.
Console(config)#interface ethernet 1/5
Console(config-if)#flowcontrol
Console(config-if)#no negotiation
Console(config-if)#
Related Commands
capabilities (17-16)
negotiation (17-15)
combo-forced-mode
This command forces the port type selected for combination ports 21~24, or 45~48. Use the no form
to restore the default mode.
Syntax
combo-forced-mode mode
no combo-forced-mode
• mode
• copper-forced - Always uses the built-in RJ-45 port.
• sfp-forced - Always uses the SFP port (even if module not installed).
• sfp-preferred-auto - Uses SFP port if both combination types are functioning and the SFP
port has a valid link.
Default Setting
sfp-preferred-auto
Command Mode
Interface Configuration (Ethernet)
Example
This forces the switch to use the built-in RJ-45 port for the combination port 24.
Console(config)#interface ethernet 1/24
Console(config-if)#combo-forced-mode copper-forced
Console(config-if)#
giga-phy-mode (EdgeIron 24G-A, 48G only)
This command forces two connected ports in to a master/slave configuration to enable 1000BASE-T
full duplex. Use the no form to restore the default mode.
Syntax
giga-phy-mode mode
no giga-phy-mode
• mode
• master - Sets the selected port as master.
• slave - Sets the selected port as slave.
Default Setting
Master
17-18
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
Command Mode
Interface Configuration (Ethernet)
Example
This forces the switch port to master in a master/slave configuration.
Console(config)#interface ethernet 1/24
Console(config-if)#giga-phy-mode master
Console(config-if)#
shutdown
Use this command to disable an interface. To restart a disabled interface, use the no form.
Syntax
shutdown
no shutdown
Default Setting
All interfaces are enabled.
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
This command allows you to disable a port due to abnormal behavior (e.g., excessive collisions),
and then reenable it after the problem has been resolved. You may also want to disable a port for
security reasons.
Example
The following example disables port 5.
clear counters
Note: This command is available on devices running software release 2.2.6.23 and later
Use this command to clear statistics on an interface.
Syntax
clear counters interface
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
Default Setting
None
December 2007
© 2007 Foundry Networks, Inc.
17-19
Foundry EdgeIron User Guide
Command Mode
Privileged Exec
Command Usage
Statistics are only initialized for a power reset. This command sets the base value for displayed
statistics to zero for the current management session. However, if you log out and back into the
management interface, the statistics displayed will show the absolute value accumulated since
the last power reset.
Example
The following example clears statistics on port 5.
Console#clear counters ethernet 1/5
Console#
Configuring Port Security
Note: This feature is available on 24G-A, 48G, 2303CF, and 4802CF running release 2.2.5.16 and
later.
port security
Use this command to enable and configure port security on a port. Use the no form to disable port
security, delete secure MAC addresses, or set other parameters to their default values.
Syntax
port security [mac-address mac-address | vlan vlan-id | max-mac-count value {action
{shutdown | trap | trap-and-shutdown | shutdown-interval minutes | restrict}}]
no port security [mac-address mac-address]
• mac-address - Specifies a secure 48-bit MAC address for the interface.
• vlan - Adds a secure MAC address to a specific vlan.
• max-mac-count - Sets the maximum number of secure MAC addresses for the interface.
(Range: 1-20; Default: 1)
• action - Indicates the security action to be taken when a port security violation is detected. After
the interval the port is automatically enabled.
- shutdown - Disable the port only.
- trap - Issue an SNMP trap message only.
- trap-and-shutdown - Issue an SNMP trap message and disable the port.
• shutdown-interval - Sets the shutdown interval if there is a port security violation.
- minutes - Specifies the amount of time. (Range: 1-1440 minutes; Default: Permanently disable
the port)
- restrict - Restricts illegal MAC addresses from gaining access to the network. Only learned
MAC addresses are permitted.
Default Setting
Status: Disabled
Action: None
Maximum Address: 0
17-20
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
Command Mode
Interface Configuration (Ethernet)
Command Usage
• If you enable port security, the switch stops learning new MAC addresses on the specified port
when it has reached a configured maximum number. Only incoming traffic with source addresses
already stored in the dynamic or static address table will be accepted.
• First use the port security max-mac-count command to set the number of addresses, and then
use the port security command to enable security on the port.
• Use the no port security max-mac-count command to disable port security and reset the
maximum number of addresses to the default.
• You can also manually add secure addresses with the mac-address-table static command.
• A secure port has the following restrictions:
- Cannot be connected to a network interconnection device.
- Cannot be a member of a static trunk.
- It can be configured as an LACP trunk port, but the switch does not allow the LACP trunk to be
enabled.
• A port that is already configured as an LACP or static trunk port cannot be enabled as a secure
port.
• If a port is disabled due to a security violation, it must be manually re-enabled by using the no
shutdown command.
Example
This example sets the port security action for port 5.
Console(config)#interface ethernet 1/5
Console(config-if)#port security action trap-and-shutdown
Console(config-if)#port security
Console(config-if)#
Related Commands
shutdown (17-19)
mac-address-table static (20-2)
port security aging
Use this command to age learned secure address entries for all ports. Use the no form to disable
port security aging.
Syntax
[no] port security aging
Default Setting
Status: Disabled
Command Mode
Global Configuration
December 2007
© 2007 Foundry Networks, Inc.
17-21
Foundry EdgeIron User Guide
Command Usage
• Use this command to enable the aging feature.
• To change the aging time for other addresses use the mac-address-table aging-time command.
• Port security aging lasts for 300 seconds.
Example
The following example enables port security aging.
Console#configure
Console(config)#port security aging 15
Console(config)#
port security autosave
Use this command to automatically save learned secure MAC addresses to the startup configuration
file. Use the no form to disable the feature.
Syntax
[no] port security autosave [update-interval]
• update-interval - Allows the user to set a time for the switch to periodically save the port security
configuration to the startup configuration. (Range: 15-1440 minutes; Default: 15 minutes)
Default Setting
Status: Disabled
Command Mode
Global Configuration
Command Usage
By default, learned secure MAC addresses are not saved to the startup configuration file. Use
this command to enable the periodic saving of secure MAC addresses to the startup file.
Example
The following example enables the port security autosave feature, and sets the update interval to
100 minutes.
Console#configure
Console(config)#port security autosave 100
Console(config)#
port security (EdgeIron 2402CF and EdgeIron 4802CF)
Use this command to enable and configure port security on a port. Use the no form to disable port
security and reset the maximum addresses to the default.
Syntax
port security [max-mac-count address-number]
no port security [max-mac-count]
address-number - Sets the maximum number of MAC addresses that can be learned on a
port. (Range: 0 - 20)
17-22
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
Default Setting
Status: Disabled
Maximum Addresses: 0
Command Mode
Interface Configuration (Ethernet)
Command Usage
• If you enable port security on a specified port, the switch will dynamically learn MAC addresses
until the specified number has been reached and then stop. Only incoming traffic with source
addresses already stored in the dynamic or static address table will be accepted.
• To use port security, specify a maximum number of addresses to allow on the port and then let
the switch dynamically learn the <source MAC address, VLAN> pair for frames received on the
port. You can also manually add secure addresses to the port with the mac-address-table static
(20-2) command.
• First use the port security max-mac-count command to set the number of addresses, and then
use the port security command to enable security on the port.
• Use the no port security max-mac-count command to disable port security and reset the
maximum number of addresses to the default.
• A secure port has the following restrictions:
- Cannot be connected to a network interconnection device.
- Cannot be a member of a static trunk.
- It can be configured as an LACP trunk port, but the switch does not allow the LACP trunk to be
enabled.
• A port that is already configured as an LACP or static trunk port cannot be enabled as a secure
port.
• Note that the EdgeIron 2402CF does not provide an intrusion action to shutdown a port or send
an SNMP trap message.
Example
This example sets the maximum MAC addresses and enables port security for port 5.
Console(config)#interface ethernet 1/5
Console(config-if)#port security max-mac-count 10
Console(config-if)#port security
Console(config-if)#
Related Commands
mac-address-table static (20-2)
show port security
Use this command to display port security settings.
Syntax
show port security [[statistic] | [interface interface-id]]
• statistic - Displays port security statistics about secure MAC address count and current secure
MAC address count.
• interface - Specifies a port interface.
December 2007
© 2007 Foundry Networks, Inc.
17-23
Foundry EdgeIron User Guide
Default Setting
Displays all port security settings.
Command Mode
Privileged Exec
Example
The following example displays port security for those ports on which it is enabled.
Console#show port security
Aging admin status: enabled
Interface
admin
max
status
mac count
----------------- ----------Eth 1/1
enable
10
Eth 1/5
enable
5
Eth 1/6
enable
1
Console#
shutdown
time
--------5
3
action
------shutdown
trap
shutdown
Setting Broadcast Storm Thresholds
Broadcast storms may occur when a device on your network is malfunctioning, or if application
programs are not well designed or properly configured. If there is too much broadcast traffic on your
network, performance can be severely degraded or everything can come to complete halt.
You can protect your network from broadcast storms by setting a threshold for broadcast traffic for
each port. Any broadcast packets exceeding the specified threshold will then be dropped.
Note: Broadcast storm control is available on devices running software release 2.2.6.x and later.
Command Usage
• Broadcast Control is enabled by default.
17-24
•
The default threshold is 500 packets per second.
Broadcast Control does not affect IP multicast traffic.
•
EdgeIron 4802CF and 2402CF: The specified threshold applies to all ports on the switch.
•
EdgeIron 24G-A and 48G: The specified threshold is set on a per port basis.
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
USING THE WEB INTERFACE
Click Port, Port Broadcast Control. Set the threshold for all ports, and then click Apply.
•
Port – Specifies a port.
•
Type – Indicates the port type.
•
Protect Status – Shows whether or not broadcast storm control has been enabled.
(Default: Enabled)
•
Threshold – Threshold as percentage of port bandwidth.
(Range: 500-262143 packets per second; Default: 500)
•
Trunk – Indicates if the port is a member of a trunk.
USING THE CLI
switchport broadcast
Note: This command is available on devices running sotware release 2.2.6.23 and later.
Use this command to configure broadcast storm control. Use the no form to disable broadcast storm
control.
Syntax
switchport broadcast packet-rate rate
no switchport broadcast
rate - Threshold level as a rate; i.e., packets per second.
(Range: 500 - 262143)
Default Setting
Enabled for all ports
Packet-rate limit: 500 packets per second
Command Mode
Interface Configuration (Ethernet)
Command Usage
• When broadcast traffic exceeds the specified threshold, packets above that threshold are
dropped.
• This command can enable or disable broadcast storm control for the selected interface. However,
the specified threshold value applies to all ports on the switch.
December 2007
© 2007 Foundry Networks, Inc.
17-25
Foundry EdgeIron User Guide
Example
The following shows how to configure broadcast storm control at 600 packets per second on port 5.
Console(config)#interface ethernet 1/5
Console(config-if)#switchport broadcast packet-rate 600
Console(config-if)#
Configuring Port Mirroring
You can mirror traffic from any source port to a target port for real-time analysis. You can then attach
a logic analyzer or RMON probe to the target port and study the traffic crossing the source port in a
completely unobtrusive manner.
Command Usage
• The source port and target port speeds must match, otherwise traffic may be dropped from the
source port.
•
The EdgeIron 2402CF and 4802CF have this restriction:
- All mirror sessions have to share the same target port.
•
The EdgeIron 24G-A, 24G and 48G have these restrictions:
- The switch supports only one port mirror session.
- The source and target port have to be either both in the port group of 1 to 12 or both in the port
group of 13 to 24; or in the case of the 48G - group 25 to 36 and group 37 to 48 as well.
•
The EdgeIron 24GS or 48GS, if stacked, can have only one mirror port in the stack.
USING THE WEB INTERFACE
Click Port, Mirror. Specify the source port, the traffic type to be mirrored, and the target port, then
click Add.
17-26
•
Mirror Sessions – Displays a list of current mirror sessions.
•
Source Port – The port whose traffic will be monitored.
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
•
Type – Allows you to select the type of traffic to mirror to the target port, Rx (receive), Tx
(transmit), or Both.
•
Target Port – The port that will “duplicate” or “mirror” the traffic on the source port.
USING THE CLI
port monitor
Use this command to configure a mirror session. Use the no form to clear a mirror session.
Syntax
port monitor interface [rx | tx | both]
no port monitor interface
• interface
- ethernet unit/port (source port)
- unit - Switch (unit 1).
- port - Port number.
• rx - Mirror received packets.
• tx - Mirror transmitted packets.
• both - Mirror both received and transmitted packets.
Default Setting
No mirror session is defined. When enabled, the default mirroring is for both received and
transmitted packets.
Command Mode
Interface Configuration (Ethernet, destination port)
Command Usage
• You can mirror traffic from any source port to a destination port for real-time analysis. You can
then attach a logic analyzer or RMON probe to the destination port and study the traffic crossing
the source port in a completely unobtrusive manner.
• The destination port is set by specifying an Ethernet interface.
• The source and destination port speeds should match, otherwise traffic may be dropped from the
source port.
• EdgeIron 4802CF, 2402CF:
- You can create more than one mirror session, but all must share the same destination port.
However, you should avoid sending too much traffic to the destination port from multiple source
ports.
Note: The 4802CF may only set one mirror-to port, but you can set as many as 49 mirror-from
ports.
• EdgeIron 24G-A, 24G, 48G:
- You can create only one mirror port session.
- The source and destination ports have to be either both in the port range 1-12 or both in the
port range 13-24; or in the case of the 48G port range 25-36 or port range 37-48 as well.
December 2007
© 2007 Foundry Networks, Inc.
17-27
Foundry EdgeIron User Guide
Example
The following example configures the switch to mirror all packets from port 6 to port 11:
Console(config)#interface ethernet 1/11
Console(config-if)#port monitor ethernet 1/6 both
Console(config-if)#
Related Commands
show port monitor (17-28)
show port monitor
Use this command to display mirror information.
Syntax
show port monitor [interface]
interface
• ethernet unit/port (source port)
- unit - Switch (unit 1).
- port - Port number.
Default Setting
Shows all sessions.
Command Mode
Privileged Exec
Command Usage
This command displays the currently configured source port, destination port, and mirror mode
(i.e., RX, TX, RX/TX).
Example
The following shows mirroring configured from port 6 to port 11:
Console(config)#interface ethernet 1/11
Console(config-if)#port monitor ethernet 1/6
Console(config-if)#end
Console#show port monitor
Port Mirroring
------------------------------------Destination port(listen port):Eth1/1
Source port(monitored port) :Eth1/6
Mode
:RX/TX
Console#
Related Commands
port monitor (17-27)
17-28
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
Configuring Rate Limits
Note: This command is available on devices running software release 2.2.6.23 and later.
This function allows the network manager to control the maximum rate for traffic transmitted or
received on an interface. Rate limiting is configured on interfaces at the edge of a network to limit
traffic into or out of the network. Traffic that falls within the rate limit is transmitted, while packets that
exceed the acceptable amount of traffic are dropped.
Rate limiting can be applied to individual ports or trunks. When an interface is configured with this
feature, the traffic rate will be monitored by the hardware to verify conformity. Non-conforming traffic
is dropped, conforming traffic is forwarded without any changes.
Command Usage
• The rate-limit range is:
- Fast Ethernet interface – 1 to 100 Mbps
- Gigabit Ethernet interface – 8 to 1000 Mbps
•
The rate-limit resolution – The increment of change:
- Fast Ethernet interface – 1 Mbps
- Gigabit Ethernet interface – 8 Mbps
Note: The egress rate limit for the Gigabit uplink ports cannot be changed from the enable state to
the disable state.
December 2007
© 2007 Foundry Networks, Inc.
17-29
Foundry EdgeIron User Guide
USING THE WEB INTERFACE
Click Rate Limit, Input/Output Rate Limit Port/Trunk Configuration. Set the Input/Output Rate Limit
Status for selected interfaces, then set the rate limit and click Apply.
•
Rate Limit – Sets the input or output rate limit for an interface.
- Default Status – Disabled
- Default Rate – Fast Ethernet: 100 Mbps,
Gigabit Ethernet: 1000 Mbps
USING THE CLI
rate-limit
Use this command to define and enable a rate limit for a specific interface. Use this command
without specifying a rate to restore the default rate. Use the no form to disable rate limiting.
Syntax
rate-limit {input | output} [rate]
no rate-limit {input | output}
• input – Input rate
• output – Output rate
• rate – Maximum value in Mbps.
Default Setting
Fast Ethernet interface – 100 Mbps
Gigabit Ethernet interface – 1000 Mbps
17-30
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
• The range is:
- Fast Ethernet interface – 1 to 100 Mbps
- Gigabit Ethernet interface – 8 to 1000 Mbps
• Resolution – The increment of change:
- Fast Ethernet interface – 1 Mbps
- Gigabit Ethernet interface – 8 Mbps
Example
Console(config)#interface ethernet 1/1
Console(config-if)#rate-limit input 8
Console(config-if)#
This example sets the rate limit for input and output traffic passing through port 1 to 60 Mbps.
Console(config)#interface ethernet 1/1
Console(config-if)#rate-limit input 60
Console(config-if)#rate-limit output 60
Console(config-if)#
Showing Device Statistics
You can display standard statistics on network traffic from the Interfaces Group and Ethernet-like
MIBs, as well as a detailed breakdown of traffic based on the RMOM MIB. Interfaces and Ethernetlike statistics display errors on the traffic passing through each port. This information can be used to
identify potential problems with the switch (such as a faulty port or unusually heavy loading). RMON
statistics provide access to a broad range of statistics, including a total count of different frame types
and sizes passing through each port. All values displayed have been accumulated since the last
system reboot, and are shown as counts per second. Statistics are refreshed every 60 seconds by
default.
Note: RMON groups 2, 3 and 9 can only be accessed using SNMP management software.
December 2007
© 2007 Foundry Networks, Inc.
17-31
Foundry EdgeIron User Guide
Statistical Values
Parameter
Description
Interface Statistics
Received Octets
The total number of octets received on the interface, including framing
characters.
Received Unicast Packets
The number of subnetwork-unicast packets delivered to a higher-layer
protocol.
Received Multicast Packets
The number of packets, delivered by this sub-layer to a higher (sub-)layer,
which were addressed to a multicast address at this sub-layer.
Received Broadcast Packets
The number of packets, delivered by this sub-layer to a higher (sub-)layer,
which were addressed to a broadcast address at this sub-layer.
Received Discarded Packets
The number of inbound packets which were chosen to be discarded even
though no errors had been detected to prevent their being deliverable to
a higher-layer protocol. One possible reason for discarding such a packet
could be to free up buffer space.
Received Unknown Packets
The number of packets received via the interface which were discarded
because of an unknown or unsupported protocol.
Received Errors
The number of inbound packets that contained errors preventing them
from being deliverable to a higher-layer protocol.
Transmit Octets
The total number of octets transmitted out of the interface, including
framing characters.
Transmit Unicast Packets
The total number of packets that higher-level protocols requested be
transmitted to a subnetwork-unicast address, including those that were
discarded or not sent.
Transmit Multicast Packets
The total number of packets that higher-level protocols requested be
transmitted, and which were addressed to a multicast address at this sublayer, including those that were discarded or not sent.
Transmit Broadcast Packets
The total number of packets that higher-level protocols requested be
transmitted, and which were addressed to a broadcast address at this
sub-layer, including those that were discarded or not sent.
Transmit Discarded Packets
The number of outbound packets which were chosen to be discarded
even though no errors had been detected to prevent their being
transmitted. One possible reason for discarding such a packet could be to
free up buffer space.
Transmit Errors
The number of outbound packets that could not be transmitted because
of errors.
Etherlike Statistics
17-32
Alignment Errors
The number of alignment errors (missynchronized data packets).
Late Collisions
The number of times that a collision is detected later than 512 bit-times
into the transmission of a packet.
FCS Errors
A count of frames received on a particular interface that are an integral
number of octets in length but do not pass the FCS check. This count does
not include frames received with frame-too-long or frame-too-short error.
Excessive Collisions
A count of frames for which transmission on a particular interface fails due
to excessive collisions. This counter does not increment when the
interface is operating in full-duplex mode.
Single Collision Frames
The number of successfully transmitted frames for which transmission is
inhibited by exactly one collision.
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
Parameter
Description
Internal MAC Transmit Errors
A count of frames for which transmission on a particular interface fails due
to an internal MAC sublayer transmit error.
Multiple Collision Frames
A count of successfully transmitted frames for which transmission is
inhibited by more than one collision.
Carrier Sense Errors
The number of times that the carrier sense condition was lost or never
asserted when attempting to transmit a frame.
SQE Test Errors
A count of times that the SQE TEST ERROR message is generated by
the PLS sublayer for a particular interface.
Frames Too Long
A count of frames received on a particular interface that exceed the
maximum permitted frame size.
Deferred Transmissions
A count of frames for which the first transmission attempt on a particular
interface is delayed because the medium was busy.
Internal MAC Receive Errors
A count of frames for which reception on a particular interface fails due to
an internal MAC sublayer receive error.
RMON Statistics
Drop Events
The total number of events in which packets were dropped due to lack of
resources.
Jabbers
The total number of frames received that were longer than 1518 octets
(excluding framing bits, but including FCS octets), and had either an FCS
or alignment error.
Received Bytes
Total number of bytes of data received on the network. This statistic can
be used as a reasonable indication of Ethernet utilization.
Collisions
The best estimate of the total number of collisions on this Ethernet
segment.
Received Frames
The total number of frames (bad, broadcast and multicast) received.
Broadcast Frames
The total number of good frames received that were directed to the
broadcast address. Note that this does not include multicast packets.
Multicast Frames
The total number of good frames received that were directed to this
multicast address.
CRC/Alignment Errors
The number of CRC/alignment errors (FCS or alignment errors).
Undersize Frames
The total number of frames received that were less than 64 octets long
(excluding framing bits, but including FCS octets) and were otherwise well
formed.
Oversize Frames
The total number of frames received that were longer than 1518 octets
(excluding framing bits, but including FCS octets) and were otherwise well
formed.
Fragments
The total number of frames received that were less than 64 octets in
length (excluding framing bits, but including FCS octets) and had either an
FCS or alignment error.
64 Bytes Frames
The total number of frames (including bad packets) received and
transmitted that were 64 octets in length (excluding framing bits but
including FCS octets).
65-127 Byte Frames
128-255 Byte Frames
256-511 Byte Frames
512-1023 Byte Frames
1024-1518 Byte Frames
1519-1536 Byte Frames
The total number of frames (including bad packets) received and
transmitted where the number of octets fall within the specified range
(excluding framing bits but including FCS octets).
December 2007
© 2007 Foundry Networks, Inc.
17-33
Foundry EdgeIron User Guide
USING THE WEB INTERFACE
Click Statistics, Port Statistics. Select the required interface, and then click Query. You can also use
the Refresh button at the bottom of the page to update the screen.
USING THE CLI
show interfaces counters
Use this command to display statistics for an interface.
Syntax
show interfaces counters [interface | brief]
• interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
• brief - Displays brief information for all ports.
17-34
© 2007 Foundry Networks, Inc.
March 2007
Interface Commands
Default Setting
Shows the counters for all interfaces.
Command Mode
Normal Exec, Privileged Exec
Command Usage
• If no interface is specified, information on all interfaces is displayed.
• For a description of the items displayed by this command, see “Showing Device Statistics” on
page 17-31.
Example
This example shows statistics for port 13.
Console#show interfaces counters ethernet 1/13
Ethernet 1/13
Iftable stats:
Octets input: 868453, Octets output: 3492122
Unicast input: 7315, Unitcast output: 6658
Discard input: 0, Discard output: 0
Error input: 0, Error output: 0
Unknown protos input: 0, QLen output: 0
Extended iftable stats:
Multi-cast input: 0, Multi-cast output: 17027
Broadcast input: 231, Broadcast output: 7
Ether-like stats:
Alignment errors: 0, FCS errors: 0
Single Collision frames: 0, Multiple collision frames: 0
SQE Test errors: 0, Deferred transmissions: 0
Late collisions: 0, Excessive collisions: 0
Internal mac transmit errors: 0, Internal mac receive errors: 0
Frame too longs: 0, Carrier sense errors: 0
Symbol errors: 0
RMON stats:
Drop events: 0, Octets: 4422579, Packets: 31552
Broadcast pkts: 238, Multi-cast pkts: 17033
Undersize pkts: 0, Oversize pkts: 0
Fragments: 0, Jabbers: 0
CRC align errors: 0, Collisions: 0
Packet size <= 64 octets: 25568, Packet size 65 to 127 octets: 1616
Packet size 128 to 255 octets: 1249, Packet size 256 to 511 octets: 1449
Packet size 512 to 1023 octets: 802, Packet size 1024 to 1518 octets: 871
Console#
Statically Configuring a Trunk
When configuring static trunks, you may not be able to link switches of different types, depending on
the manufacturer’s implementation. Static trunks have to be manually configured at both ends of the
link.
To avoid creating a loop in the network, be sure you add a static trunk via the configuration interface
before connecting the ports, and also disconnect the ports before removing a static trunk via the
configuration interface.
December 2007
© 2007 Foundry Networks, Inc.
17-35
Foundry EdgeIron User Guide
USING THE WEB INTERFACE
Click Port, Trunk Membership. Enter a trunk ID of 1-6 in the Trunk field, select any of the switch ports
from the scroll-down port list, and click Add. After you have completed adding ports to the member
list, click Apply
USING THE CLI
The CLI commands for configuring a trunk are included in the “Enabling LACP on Selected Ports”
section in Chapter 18.
17-36
© 2007 Foundry Networks, Inc.
March 2007
Chapter 18
LACP
These commands are used to display and configure dynamic port trunks.
The CLI commands for this section are briefly described in the table that follows:
Command
Function
Mode
Page
Dynamic Configuration Command
lacp
Configures LACP for the current interface
IC
18-3
lacp system-priority
Configures a port's LACP system priority
IC (Ethernet)
18-6
lacp admin-key
Configures a port's administration key
IC (Ethernet)
18-7
lacp admin-key
Configures an port channel’s administration key
IC (Port Channel)
18-7
lacp port-priority
Configures a port's LACP port priority
IC (Ethernet)
18-8
Trunk Status Display Command
show interfaces status
port-channel
Shows trunk information
NE, PE
17-7
show lacp
Shows LACP information
PE
18-9
Dynamically Configuring a Trunk
Ports can be combined into an aggregate link to increase the bandwidth of a network connection
where bottlenecks exist or to ensure fault recovery. You can create up to six trunks at a time, with any
single trunk containing up to four ports.
Table 18-1: Trunk Load Balance Selection Based on Hashing Calculations
Model Name
Trunk Load Balance Selection Criterion
EIF2402CF, EIF4802CF
L2 Src and Dst MAC address
EIF24G
L2 Src MAC, L2 Dst MAC, L2 ether type, L2 vlan ID, IP multicast Src MAC,
IP multicast Dst MAC
EIF24G-A, EIF48G
L2 Src and Dst MAC address
EIF24GS, EIF48GS
L2 Src and Dst MAC address
EIF8X10G
L2 Src and Dst MAC address
December 2007
© 2007 Foundry Networks, Inc.
18-1
Foundry EdgeIron User Guide
Besides balancing the load across each port in the trunk, the other ports provide redundancy by
taking over the load if a port in the trunk fails. However, before making any physical connections
between devices, use the Web interface or CLI to specify the trunk on the devices at both ends.
When using a port trunk, take note of the following points:
•
Finish configuring port trunks before you connect the corresponding network cables between
switches to avoid creating a loop.
•
The maximum number of ports that can be combined as a static trunk:
-
EdgeIron 4802CF, 2402CF: Four 10/100 Mbps ports, and two 1000 Mbps ports. (Total: 6 ports)
EdgeIron 24G-A, 24G, 48G: Six 1000 Mbps ports.
EdgeIron 24GS, 48GS: Eight 1000 Mbps ports.
EdgeIron 8X10G: Four 10 Gbps ports.
•
The ports at both ends of a connection must be configured as trunk ports.
•
Static trunkshave to be manually configured at both ends of the link
•
The ports at both ends of a trunk must be configured in an identical manner, including
communication mode (i.e., speed, duplex mode and flow control), VLAN assignments, and CoS
settings.
•
All ports on both ends of an LACP trunk must be configured for full duplex, either by forced mode
or auto-negotiation.
•
All the ports in a trunk have to be treated as a whole when moved from/to, added or deleted from
a VLAN.
•
STP, VLAN, and IGMP settings can only be made for the entire trunk.
Enabling LACP on Selected Ports
Ports can be statically grouped into an aggregate link to increase the bandwidth of a network
connection or to ensure fault recovery. Or you can use the Link Aggregation Control Protocol
(LACP), also known as 802.1ad, to automatically negotiate a trunk link between this switch and
another network device. For dynamic trunks, the switches have to comply with LACP. This switch
supports up to six trunks. For example, a trunk consisting of two 1000 Mbps ports can support an
aggregate bandwidth of 4 Gbps when operating at full duplex.
The load spread over the ports is calculated as shown on Table 17-1.
To avoid creating a loop in the network, be sure you enable LACP before connecting the ports, and
also disconnect the ports before disabling LACP. If the target switch has also enabled LACP on the
connected ports, the trunk will be activate automatically. A trunk formed with another switch using
LACP will automatically be assigned the next available trunk ID. If more than four ports attached to
the same target switch have LACP enabled, the additional ports will be placed in standby mode, and
will only be enabled if one of the active links fails. All ports on both ends of an LACP trunk must be
configured for full duplex, either by forced mode or auto-negotiation.
18-2
© 2007 Foundry Networks, Inc.
March 2007
LACP
USING THE WEB INTERFACE
Click Port, LACP, Configuration. Select any of the switch ports from the scroll-down port list and click
Add. After you have completed adding ports to the member list, click Apply.
USING THE CLI
Use the commands in this section to configure both a trunk and LACP parameters from the CLI. For
the interface port channel command.
lacp
Use this command to enable 802.3ad Link Aggregation Control Protocol (LACP) for the current
interface. Use the no form to disable it.
Syntax
[no] lacp
Default Setting
Disabled
Command Mode
Interface Configuration (Ethernet)
Command Usage
• The ports on both ends of an LACP trunk must be configured for full duplex, either by forced mode
or auto-negotiation.
• A trunk formed with another switch using LACP will automatically be assigned the next available
port-channel ID.
• If the target switch has also enabled LACP on the connected ports, the trunk will be activated
automatically.
• If more than four ports attached to the same target switch have LACP enabled, the additional ports
will be placed in standby mode, and will only be enabled if one of the active links fails.
December 2007
© 2007 Foundry Networks, Inc.
18-3
Foundry EdgeIron User Guide
Example
The following shows LACP enabled on ports 11-13. Because LACP has also been enabled on the
ports at the other end of the links, the show interfaces status port-channel 1 command shows that
Trunk 1 has been established.
Console(config)#interface ethernet 1/11
Console(config-if)#lacp
Console(config-if)#exit
Console(config)#interface ethernet 1/12
Console(config-if)#lacp
Console(config-if)#exit
Console(config)#interface ethernet 1/13
Console(config-if)#lacp
Console(config-if)#end
Console#show interfaces status port-channel 1
Information of Trunk 1
Basic information:
Port type: 100TX
Mac address: 00-30-F1-47-58-4E
Configuration:
Name:
Port admin: Up
Speed-duplex: Auto
Capabilities: 10half, 10full, 100half, 100full,
Flow control: Disabled
Port security: Disabled
Port security action: None
Current status:
Created by: Lacp
Link status: Up
Port operation status: Up
Operation speed-duplex: 100full
Flow control type: None
Member Ports: Eth1/11, Eth1/12, Eth1/13,
Console#
The following example enables LACP for ports 1 to 6. Just connect these ports to LACP-enabled
trunk ports on another switch to form a trunk.
Console(config)#interface ethernet 1/1
Console(config-if)#lacp
Console(config-if)#exit
Console(config)#interface ethernet 1/6
Console(config-if)#lacp
Console(config-if)#end
Console#show interfaces status port-channel 1
Information of Trunk
Basic information:
Port type: 1000T
Mac address: 22-22-22-22-22-2d
Configuration:
Name:
Port admin status: Up
Speed-duplex: Auto
Capabilities: 10half, 10full, 100half, 100full, 1000full,
Flow control status: Disabled
Port security: Disabled
Max MAC count: 0
Port security action: None
Combo forced mode: None
Current status:
Created by: Lacp
Link status: Up
Port operation status: Up
Operation speed-duplex: 1000full
Flow control type: None
Member Ports: Eth1/1, Eth1/2, Eth1/3, Eth1/4, Eth1/5, Eth1/6,
Console#
18-4
© 2007 Foundry Networks, Inc.
March 2007
LACP
Configuring LACP Parameters
Dynamically Creating a Port Channel
Ports assigned to a common port channel must meet the following criteria:
•
Ports must have the same LACP System Priority.
•
Ports must have the same LACP port Admin Key.
•
However, if the “port channel” Admin Key is set, then the port Admin Key must be set to the same
value for a port to be allowed to join a channel group.
Note: If the port channel admin key is not set (through the CLI) when a channel group is formed
(i.e., it has a null value of 0), this key is set to the same value as the port admin key used by the
interfaces that joined the group.
Note: The maximum number of ports in a trunk is 8, and the maximum number of trunk groups is
12. There is no limitation on the number of LACP members.
USING THE WEB INTERFACE
Click Port, LACP, Aggregation Port. Set the System Priority, Admin Key, and Port Priority for the Port
Actor. You can optionally configure these settings for the Port Partner. (Be aware that these settings
only affect the administrative state of the partner, and will not take effect until the next time an
aggregate link is formed with this device.) After you have completed setting the port LACP
parameters, click Apply.
•
Set Port Actor – This menu sets the local side of an aggregate link; i.e., the ports on this switch.
•
Port – Port number. (Range: 1-24)
•
System Priority – LACP system priority is used to determine link aggregation group (LAG)
membership, and to identify this device to other switches during LAG negotiations.
December 2007
© 2007 Foundry Networks, Inc.
18-5
Foundry EdgeIron User Guide
(Range: 0-65535; Default: 32768)
- Ports must be configured with the same system priority to join the same LAG.
- System priority is combined with the switch’s MAC address to form the LAG identifier. This
identifier is used to indicate a specific LAG during LACP negotiations with other systems.
•
Admin Key – The LACP administration key must be set to the same value for ports that belong
to the same LAG. (Range: 0-65535; Default: 0)
•
Port Priority – If a link goes down, LACP port priority is used to select a backup link.
(Range: 0-65535; Default: 32768)
•
Set Port Partner – This menu sets the remote side of an aggregate link; i.e., the ports on the
attached device. The command attributes have the same meaning as those used for the port
actor. However, configuring LACP settings for the partner only applies to its administrative state,
not its operational state, and will only take effect the next time an aggregate link is established
with the partner.
USING THE CLI
Note: The LACP commands in this section are not supported on the 2402CF and 4802CF.
lacp system-priority
This command configures a port's LACP system priority. Use the no form to restore the default
setting.
Syntax
lacp {actor | partner} system-priority priority
no lacp {actor | partner} system-priority
• actor - The local side an aggregate link.
• partner - The remote side of an aggregate link.
• priority - This priority is used to determine link aggregation group (LAG) membership, and to
identify this device to other switches during LAG negotiations. (Range: 0-65535)
Default Setting
32768
Command Mode
Interface Configuration (Ethernet)
Command Usage
• Port must be configured with the same system priority to join the same LAG.
• System priority is combined with the switch’s MAC address to form the LAG identifier. This
identifier is used to indicate a specific LAG during LACP negotiations with other systems.
• Once the remote side of a link has been established, LACP operational settings are already in use
on that side. Configuring LACP settings for the partner only applies to its administrative state, not
its operational state, and will only take effect the next time an aggregate link is established with
the partner.
18-6
© 2007 Foundry Networks, Inc.
March 2007
LACP
Example
Console(config)#interface ethernet 1/5
Console(config-if)#lacp actor system-priority 3
Console(config-if)#
lacp admin-key (Ethernet Interface)
This command configures a port's LACP administration key. Use the no form to restore the default
setting.
Syntax
lacp {actor | partner} admin-key key
[no] lacp {actor | partner} admin-key
• actor - The local side an aggregate link.
• partner - The remote side of an aggregate link.
• key - The port admin key must be set to the same value for ports that belong to the same link
aggregation group (LAG). (Range: 0-65535)
Default Setting
0
Command Mode
Interface Configuration (Ethernet)
Command Usage
• Ports are only allowed to join the same LAG if (1) the LACP system priority matches, (2) the LACP
port admin key matches, and (3) the LACP port channel admin key matches (if configured).
• If the port channel admin key (lacp admin key - Port Channel) is not set when a channel group
is formed (i.e., it has the null value of 0), this key is set to the same value as the port admin key
(lacp admin key - Ethernet Interface) used by the interfaces that joined the group.
• Once the remote side of a link has been established, LACP operational settings are already in use
on that side. Configuring LACP settings for the partner only applies to its administrative state, not
its operational state, and will only take effect the next time an aggregate link is established with
the partner.
Example
Console(config)#interface ethernet 1/5
Console(config-if)#lacp actor admin-key 120
Console(config-if)#
lacp admin-key (Port Channel)
This command configures a port channel's LACP administration key string. Use the no form to
restore the default setting.
Syntax
lacp admin-key key
[no] lacp admin-key
• key - The port channel admin key is used to identify a specific link aggregation group (LAG) during
local LACP setup on this switch. (Range: 0-65535)
December 2007
© 2007 Foundry Networks, Inc.
18-7
Foundry EdgeIron User Guide
Default Setting
0
Command Mode
Interface Configuration (Port Channel)
Command Usage
• Ports are only allowed to join the same LAG if (1) the LACP system priority matches, (2) the LACP
port admin key matches, and (3) the LACP port channel key matches (if configured).
• If the port channel admin key (lacp admin key - Port Channel) is not set when a channel group
is formed (i.e., it has the null value of 0), this key is set to the same value as the port admin key
(lacp admin key - Ethernet Interface) used by the interfaces that joined the group. Note that when
the LAG is no longer used, the port channel admin key is reset to 0.
Example
Console(config)#interface port channel 1
Console(config-if)#lacp admin-key 3
Console(config-if)#
lacp port-priority
This command configures LACP port priority. Use the no form to restore the default setting.
Syntax
lacp {actor | partner} port-priority priority
no lacp {actor | partner} port-priority
• actor - The local side an aggregate link.
• partner - The remote side of an aggregate link.
• priority - LACP port priority is used to select a backup link. (Range: 0-65535)
Default Setting
32768
Command Mode
Interface Configuration (Ethernet)
Command Usage
• Setting a lower value indicates a higher effective priority.
• If an active port link goes down, the backup port with the highest priority is selected to replace the
downed link. However, if two or more ports have the same LACP port priority, the port with the
lowest physical port number will be selected as the backup port.
• Once the remote side of a link has been established, LACP operational settings are already in use
on that side. Configuring LACP settings for the partner only applies to its administrative state, not
its operational state, and will only take effect the next time an aggregate link is established with
the partner.
Example
Console(config)#interface ethernet 1/5
Console(config-if)#lacp actor port-priority 128
18-8
© 2007 Foundry Networks, Inc.
March 2007
LACP
Displaying LACP Port Counters
You can display statistics for LACP protocol messages.
Counter Information
Parameter
Description
LACPDUs Sent
Number of valid LACPDUs transmitted from this channel group.
LACPDUs Received
Number of valid LACPDUs received on this channel group.
Marker Sent
Number of valid Marker PDUs transmitted from this channel group.
Marker Received
Number of valid Marker PDUs received by this channel group.
LACPDUs Unknown Pkts
Number of frames received that either (1) Carry the Slow Protocols Ethernet
Type value, but contain an unknown PDU, or (2) are addressed to the Slow
Protocols group MAC Address, but do not carry the Slow Protocols Ethernet
Type.
LACPDUs Illegal Pkts
Number of frames that carry the Slow Protocols Ethernet Type value, but
contain a badly formed PDU or an illegal value of Protocol Subtype.
USING THE WEB INTERFACE
Click Port, LACP, Port Counters Information. Select a member port to display the corresponding
information.
USING THE CLI
Use the following commands to display LACP settings.
show lacp
This command displays LACP information.
Note: This command is not supported on the 2402CF and 4802CF. You can use the "show
interface status ethernet" command to determine if LACP is enabled on an interface and the "show
interface status port-channel" command to see the trunks that have been formed.
December 2007
© 2007 Foundry Networks, Inc.
18-9
Foundry EdgeIron User Guide
Syntax
show lacp [port-channel] {counters | internal | neighbors | sys-id}
• port-channel - Local identifier for a link aggregation group. (Range: 1-6)
• counters - Statistics for LACP protocol messages.
• internal - Configuration settings and operational state for local side.
• neighbors - Configuration settings and operational state for remote side.
• sys-id - Summary of system priority and MAC address for all channel groups.
Default Setting
Port Channel: all
Command Mode
Privileged Exec
Example
Console#show lacp 1 counters
Channel group : 1 ----------------------------------------------------------Eth 1/ 1 -------------------------------------------------------------------LACPDUs Sent : 21
LACPDUs Received : 21
Marker Sent : 0
Marker Received : 0
LACPDUs Unknown Pkts : 0
LACPDUs Illegal Pkts : 0
.
.
.
18-10
© 2007 Foundry Networks, Inc.
March 2007
LACP
Parameter
Description
LACPDUs Sent
Number of valid LACPDUs transmitted from this channel group.
LACPDUs Received
Number of valid LACPDUs received on this channel group.
Marker Sent
Number of valid Marker PDUs transmitted from this channel group.
Marker Received
Number of valid Marker PDUs received by this channel group.
LACPDUs Unknown Pkts
Number of frames received that either (1) Carry the Slow Protocols Ethernet
Type value, but contain an unknown PDU, or (2) are addressed to the Slow
Protocols group MAC Address, but do not carry the Slow Protocols Ethernet
Type.
LACPDUs Illegal Pkts
Number of frames that carry the Slow Protocols Ethernet Type value, but contain
a badly formed PDU or an illegal value of Protocol Subtype.
Console#show lacp 1 internal
Channel group : 1
------------------------------------------------------------------------Oper Key : 4
Admin Key : 0
Eth 1/1
------------------------------------------------------------------------LACPDUs Internal : 30 sec
LACP System Priority : 32768
LACP Port Priority : 32768
Admin Key : 4
Oper Key : 4
Admin State : defaulted, aggregation, long timeout, LACP-activity
Oper State : distributing, collecting, synchronization,
aggregation, long timeout, LACP-activity
December 2007
© 2007 Foundry Networks, Inc.
18-11
Foundry EdgeIron User Guide
Parameter
Description
Oper Key
Current operational value of the key for the aggregation port.
Admin Key
Current administrative value of the key for the aggregation port.
LACPDUs Internal
Number of seconds before invalidating received LACPDU information.
LACP System Priority
LACP system priority assigned to this port channel.
LACP Port Priority
LACP port priority assigned to this interface within the channel group.
Admin State,
Oper State
Administrative or operational values of the actor’s state parameters:
Expired – The actor’s receive machine is in the expired state;
Defaulted – The actor’s receive machine is using defaulted operational partner
information, administratively configured for the partner.
Distributing – If false, distribution of outgoing frames on this link is disabled; i.e.,
distribution is currently disabled and is not expected to be enabled in the
absence of administrative changes or changes in received protocol information.
Collecting – Collection of incoming frames on this link is enabled; i.e., collection
is currently enabled and is not expected to be disabled in the absence of
administrative changes or changes in received protocol information.
Synchronization – The System considers this link to be IN_SYNC; i.e., it has
been allocated to the correct Link Aggregation Group, the group has been
associated with a compatible Aggregator, and the identity of the Link
Aggregation Group is consistent with the System ID and operational Key
information transmitted.
Aggregation – The system considers this link to be aggregatable; i.e., a potential
candidate for aggregation.
Long timeout – Periodic transmission of LACPDUs uses a slow transmission
rate.
LACP-Activity – Activity control value with regard to this link.
(0: Passive; 1: Active)
Console#show lacp 1 neighbors
Channel group 1 neighbors
------------------------------------------------------------------------Eth 1/1
------------------------------------------------------------------------Partner Admin System ID : 32768, 00-00-00-00-00-00
Partner Oper System ID : 32768, 00-00-00-00-00-01
Partner Admin Port Number : 1
Partner Oper Port Number : 1
Port Admin Priority : 32768
Port Oper Priority : 32768
Admin Key : 0
Oper Key : 4
Admin State : defaulted, distributing, collecting, synchronization,
long timeout,
Oper State : distributing, collecting, synchronization, aggregation,
long timeout, LACP-activity
.
.
.
18-12
© 2007 Foundry Networks, Inc.
March 2007
LACP
Parameter
Description
Partner Admin System ID
LAG partner’s system ID assigned by the user.
Partner Oper System ID
LAG partner’s system ID assigned by the LACP protocol.
Partner Admin Port Number Current administrative value of the port number for the protocol Partner.
Partner Oper Port Number
Operational port number assigned to this aggregation port by the port’s protocol
partner.
Port Admin Priority
Current administrative value of the port priority for the protocol partner.
Port Oper Priority
Priority value assigned to this aggregation port by the partner.
Admin Key
Current administrative value of the Key for the protocol partner.
Oper Key
Current operational value of the Key for the protocol partner.
Admin State
Administrative values of the partner’s state parameters. (See preceding table.)
Oper State
Operational values of the partner’s state parameters. (See preceding table.)
Console#show lacp sysid
Channel group
System Priority
System MAC Address
-----------------------------------------------------------------1
32768
00-30-F1-8F-2C-A7
2
32768
00-30-F1-8F-2C-A7
3
32768
00-30-F1-8F-2C-A7
4
32768
00-30-F1-8F-2C-A7
5
32768
00-30-F1-8F-2C-A7
6
32768
00-30-F1-8F-2C-A7
Console#
Parameter
Description
Channel group
A link aggregation group configured on this switch.
System Priority*
LACP system priority for this channel group.
System MAC Address*
System MAC address.
* The LACP system priority and system MAC address are concatenated to form the LAG system ID.
Displaying LACP Settings and Status for the Local Side
You can display configuration settings and the operational state for the local side of an link
aggregation.
Internal Configuration Information
Parameter
Description
Oper Key
Current operational value of the key for the aggregation port.
Admin Key
Current administrative value of the key for the aggregation port.
LACPDUs Internal
Number of seconds before invalidating received LACPDU information.
LACP System Priority
LACP system priority assigned to this port channel.
December 2007
© 2007 Foundry Networks, Inc.
18-13
Foundry EdgeIron User Guide
Parameter
Description
LACP Port Priority
LACP port priority assigned to this interface within the channel group.
Admin State,
Oper State
Administrative or operational values of the actor’s state parameters:
Expired – The actor’s receive machine is in the expired state;
Defaulted – The actor’s receive machine is using defaulted operational
partner information, administratively configured for the partner.
Distributing – If false, distribution of outgoing frames on this link is disabled;
i.e., distribution is currently disabled and is not expected to be enabled in the
absence of administrative changes or changes in received protocol
information.
Collecting – Collection of incoming frames on this link is enabled; i.e.,
collection is currently enabled and is not expected to be disabled in the
absence of administrative changes or changes in received protocol
information.
Synchronization – The System considers this link to be IN_SYNC; i.e., it has
been allocated to the correct Link Aggregation Group, the group has been
associated with a compatible Aggregator, and the identity of the Link
Aggregation Group is consistent with the System ID and operational Key
information transmitted.
Aggregation – The system considers this link to be aggregatable; i.e., a
potential candidate for aggregation.
Long timeout – Periodic transmission of LACPDUs uses a slow transmission
rate.
LACP-Activity – Activity control value with regard to this link.
(0: Passive; 1: Active)
USING THE WEB INTERFACE
Click Port, LACP, Port Internal Information. Select a port channel to display the corresponding
information.
USING THE CLI
See “show lacp” on page 18-9.
18-14
© 2007 Foundry Networks, Inc.
March 2007
LACP
Displaying LACP Settings and Status for the Remote Side
You can display configuration settings and the operational state for the remote side of an link
aggregation.
Neighbor Configuration Information
Parameter
Description
Partner Admin System ID
LAG partner’s system ID assigned by the user.
Partner Oper System ID
LAG partner’s system ID assigned by the LACP protocol.
Partner Admin Port Number
Current administrative value of the port number for the protocol Partner.
Partner Oper Port Number
Operational port number assigned to this aggregation port by the port’s
protocol partner.
Port Admin Priority
Current administrative value of the port priority for the protocol partner.
Port Oper Priority
Priority value assigned to this aggregation port by the partner.
Admin Key
Current administrative value of the Key for the protocol partner.
Oper Key
Current operational value of the Key for the protocol partner.
Admin State
Administrative values of the partner’s state parameters. (See preceding
table.)
Oper State
Operational values of the partner’s state parameters. (See preceding table.)
USING THE WEB INTERFACE
Click Port, LACP, Port Neighbors Information. Select a port channel to display the corresponding
information.
USING THE CLI
See “show lacp” on page 18-9.
December 2007
© 2007 Foundry Networks, Inc.
18-15
Foundry EdgeIron User Guide
18-16
© 2007 Foundry Networks, Inc.
March 2007
Chapter 19
Access Control Lists
Access Control Lists (ACL) provide packet filtering for IP frames (based on address, protocol, Layer
4 protocol port number or TCP control code) or any frames (based on MAC address or Ethernet
type). To filter incoming packets, first create an access list, add the required rules, specify a mask to
modify the precedence in which the rules are checked, and then bind the list to a specific port.
An ACL is a sequential list of permit or deny conditions that apply to IP addresses, MAC addresses,
or other more specific criteria. This switch tests ingress or egress packets against the conditions in
an ACL one by one. A packet will be accepted as soon as it matches a permit rule, or dropped as
soon as it matches a deny rule. If no rules match for a list of all permit rules, the packet is dropped;
and if no rules match for a list of all deny rules, the packet is accepted.
Note: The EdgeIron 2402CF and 4802CF do not support ACLs, but do support IP Management
filtering.
There are three filtering modes:
•
Standard IP ACL mode (STD-ACL) filters packets based on the source IP address.
•
Extended IP ACL mode (EXT-ACL) filters packets based on source or destination IP address, as
well as protocol type and protocol port number. If the TCP protocol is specified, then you can also
filter packets based on the TCP control code.
•
MAC ACL mode (MAC-ACL) filters packets based on the source or destination MAC address and
the Ethernet frame type (RFC 1060).
The following restrictions apply to ACLs:
•
The EdgeIron range supports ACLs for both ingress and egress filtering. However, you can only
bind one IP ACL and one MAC ACL to any port for ingress filtering, and one IP ACL and one MAC
ACL to any port for egress filtering. In other words, only four ACLs can be bound to an interface
– Ingress IP ACL, Egress IP ACL, Ingress MAC ACL and Egress MAC ACL.
•
When an ACL is bound to an interface as an egress filter, all entries in the ACL must be deny
rules. Otherwise, the bind operation will fail.
•
Each ACL can have up to 20 rules.
•
The maximum number of ACLs per device is also 20.
December 2007
© 2007 Foundry Networks, Inc.
19-1
Foundry EdgeIron User Guide
•
However, due to resource restrictions, the average number of rules bound the ports should not
exceed 20.
•
You must configure a mask for an ACL rule before you can bind it to a port or set the queue or
frame priorities associated with the rule.
•
The switch does not support the explicit “deny any any” rule for the egress IP ACL or the egress
MAC ACLs. If these rules are included in ACL, and you attempt to bind the ACL to an interface
for egress checking, the bind operation will fail.
•
Egress MAC ACLs only work for destination-mac-known packets, not for multicast, broadcast, or
destination-mac-unknown packets.
The order in which active ACLs are checked is as follows:
1. User-defined rules in the Egress MAC ACL for egress ports.
2. User-defined rules in the Egress IP ACL for egress ports.
3. User-defined rules in the Ingress MAC ACL for ingress ports.
4. User-defined rules in the Ingress IP ACL for ingress ports.
5. Explicit default rule (permit any any) in the ingress IP ACL for ingress ports.
6. Explicit default rule (permit any any) in the ingress MAC ACL for ingress ports.
7. If no explicit rule is matched, the implicit default is permit all.
Masks for Access Control Lists
You can specify optional masks that control the order in which ACL rules are checked. The switch
includes two system default masks that pass/filter packets matching the permit/deny the rules
specified in an ingress ACL. You can also configure up to seven user-defined masks for an ACL. A
mask must be bound exclusively to one of the basic ACL types (i.e., Ingress IP ACL, Egress IP ACL,
Ingress MAC ACL or Egress MAC ACL), but a mask can be bound to up to four ACLs of the same
type.
The CLI commands for each respective ACL command group are briefly described in the tables that
precede each section.
19-2
Command Groups
Function
IP ACLs
Configures ACLs based on IP addresses, TCP/UDP
port number, protocol type, and TCP control code
MAC ACLs
Configures ACLs based on hardware addresses,
packet format, and Ethernet type
19-14
ACL Information
Displays ACLs and associated rules; shows ACLs
assigned to each port
19-33
© 2007 Foundry Networks, Inc.
Page
19-5
March 2007
Access Control Lists
The following table briefly describes the commands necessary to create, name and configure IP
ACLs:
Command
Function
Mode
access-list ip
Creates an IP ACL and enters configuration mode
GC
19-4
permit, deny
Filters packets matching a specified source IP
address
STDACL
19-6
permit, deny
Filters packets meeting the specified criteria, including
source and destination IP address, TCP/UDP port
number, protocol type, and TCP control code
EXTACL
19-8
show ip access-list
Displays the rules for configured IP ACLs
PE
19-10
access-list ip mask-precedence
Changes to the mode for configuring access control
masks
GC
19-10
mask
Sets a precedence mask for the ACL rules
IP-Mask
19-25
show access-list ip maskprecedence
Shows the ingress or egress rule masks for IP ACLs
PE
19-30
ip access-group
Adds a port to an IP ACL
IC
19-32
show ip access-group
Shows port assignments for IP ACLs
PE
19-34
map access-list ip
Sets the CoS value and corresponding output queue
for packets matching an ACL rule
IC
19-11
show map access-list ip
Shows CoS value mapped to an access list for an
interface
PE
19-12
match access-list ip
Changes the 802.1p priority, IP Precedence, or DSCP
Priority of a frame matching the defined rule (i.e., also
called packet marking)
IC
19-12
show marking
Displays the current configuration for packet marking
PE
19-13
December 2007
© 2007 Foundry Networks, Inc.
Page
19-3
Foundry EdgeIron User Guide
Setting the ACL Name and Type
To configure an ACL you must first give it a name and specify a type.
USING THE WEB INTERFACE
Use the ACL Configuration page to designate the name and type of an ACL.
Click Security, ACL, ACL Configuration. Enter an ACL name in the Name field, select the list type (IP
Standard, IP Extended, or MAC), and click Add to open the configuration page for the new list.
•
Name – Name of the ACL. (Maximum length: 16 characters)
•
Type – There are three filtering modes:
- Standard: IP ACL mode that filters packets based on the source IP address.
- Extended: IP ACL mode that filters packets based on source or destination IP address, as well
as protocol type and protocol port number. If the “TCP” protocol is specified, then you can also
filter packets based on the TCP control code.
- MAC: MAC ACL mode that filters packets based on the source or destination MAC address and
the Ethernet frame type (RFC 1060).
USING THE CLI
Use the command in this section to create either a standard or extended IP ACL from the CLI.
access-list ip
This command adds an IP access list and enters configuration mode for standard or extended IP
ACLs. Use the no form to remove the specified ACL.
Syntax
[no] access-list ip {standard | extended} acl_name
• standard – Specifies an ACL that filters packets based on the source IP address.
• extended – Specifies an ACL that filters packets based on the source or destination IP address,
and other more specific criteria.
• acl_name – Name of the ACL. (Maximum length: 16 characters)
Default Setting
None
Command Mode
Global Configuration
19-4
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
Command Usage
• An egress ACL must contain all deny rules.
• When you create a new ACL or enter configuration mode for an existing ACL, use the permit or
deny command to add new rules to the bottom of the list. To create an ACL, you must add at least
one rule to the list.
• To remove a rule, use the no permit or no deny command followed by the exact text of a
previously configured rule.
• An ACL can contain up to 20 rules.
Example
Console(config)#access-list ip standard david
Console(config-std-acl)#
Related Commands
permit, deny (Standard ACL) (19-6)
ip access-group (19-32)
show ip access-list (19-10)
Configuring a Standard IP ACL
USING THE WEB INTERFACE
Specify the action (i.e., Permit or Deny). Select the address type (Any, Host, or IP). If you select
“Host,” enter a specific address. If you select “IP,” enter a subnet address and the mask for an
address range. Then click Add.
•
Action – An ACL can contain permit rules, deny rules, or a combination of both.
(Default: Permit rules)
•
Address Type - Specifies the filter type - Any, Host, or IP. (Default: Any)
•
IP Address – Specifies the source IP address. Use “Any” to include all possible addresses, “Host”
to specify a specific host address in the Address field, or “IP” to specify a range of addresses with
the Address and SubMask fields. (Options: Any, Host, IP; Default: Any)
•
Subnet Mask – A subnet mask containing four integers from 0 to 255, each separated by a
period. The mask uses 1 bits to indicate “match” and 0 bits to indicate “ignore.” The mask is
bitwise ANDed with the specified source IP address, and compared with the address for each IP
packet entering the port(s) to which this ACL has been assigned.
December 2007
© 2007 Foundry Networks, Inc.
19-5
Foundry EdgeIron User Guide
USING THE CLI
Use the commands in this section to configure a standard IP ACL from the CLI.
permit, deny (Standard ACL)
This command adds a rule to a Standard IP ACL. The rule sets a filter condition for packets
emanating from the specified source. Use the no form to remove a rule.
Syntax
[no] {permit | deny} {any | source bitmask | host source}
• any – Any source IP address.
• source – Source IP address.
• bitmask – Decimal number representing the address bits to match.
• host – Keyword followed by a specific IP address.
Default Setting
None
Command Mode
Standard ACL
Command Usage
• New rules are appended to the end of the list.
• Address bitmasks are similar to a subnet mask, containing four integers from 0 to 255, each
separated by a period. The binary mask uses 1 bits to indicate “match” and 0 bits to indicate
“ignore.” The bitmask is bitwise ANDed with the specified source IP address, and then compared
with the address for each IP packet entering the port(s) to which this ACL has been assigned.
Example
This example configures one permit rule for the specific address 10.1.1.21 and another rule for the
address range 168.92.16.x – 168.92.31.x using a bitmask.
Console(config-std-acl)#permit host 10.1.1.21
Console(config-std-acl)#permit 168.92.16.0 255.255.240.0
Console(config-std-acl)#
Related Commands
access-list ip (19-4)
19-6
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
Configuring an Extended IP ACL
USING THE WEB INTERFACE
Specify the action (i.e., Permit or Deny). Specify the source and/or destination addresses. Select the
address type (Any, Host, or IP). If you select “Host,” enter a specific address. If you select “IP,” enter
a subnet address and the mask for an address range. Set any other required criteria, such as
service type, protocol type, or TCP control code. Then click Add.
•
Action – An ACL can contain permit rules, deny rules or a combination of both.
(Default: Permit rules)
•
Source Address Type – Specifies the filter type - Any, Host, or IP. (Default: Any)
•
Source/Destination IP – Specifies the source or destination IP address. Use “Any” to include all
possible addresses, “Host” to specify a specific host address in the Address field, or “IP” to specify
a range of addresses with the Address and SubMask fields. (Options: Any, Host, IP; Default: Any)
•
Source/Destination Subnet Mask – Subnet mask for source or destination address. (See
“Configuring a Standard IP ACL” on page 19-5.)
•
Service Type – Packet priority settings based on the following criteria:
•
Precedence – IP precedence level. (Range: 0-7)
•
TOS – Type of Service level. (Range: 0-15)
•
DSCP – DSCP priority level. (Range: 0-64)
•
Protocol – Specifies the protocol type to match as TCP, UDP or Others, where others indicates
a specific protocol number (0-255). (Options: TCP, UDP, Others; Default: TCP)
•
Source/Destination Port – Source/destination port number for the specified protocol type.
(Range: 0-65535)
December 2007
© 2007 Foundry Networks, Inc.
19-7
Foundry EdgeIron User Guide
•
Source/Destination Port Bitmask – Decimal number representing the port bits to match.
(Range: 0-65535)
•
Control Code – Decimal number (representing a bit string) that specifies flag bits in byte 14 of
the TCP header. (Range: 0-63)
•
Control Code Bitmask – Decimal number representing the code bits to match.
The control bitmask is a decimal number (for an equivalent binary bit mask) that is applied to the
control code. Enter a decimal number, where the equivalent binary bit “1” means to match a bit
and “0” means to ignore a bit. The following bits may be specified:
-
1 (fin) – Finish
2 (syn) – Synchronize
4 (rst) – Reset
8 (psh) – Push
16 (ack) – Acknowledgement
32 (urg) – Urgent pointer
For example, use the code value and mask below to catch packets with the following flags set:
- SYN flag valid, use control-code 2, control bitmask 2
- Both SYN and ACK valid, use control-code 18, control bitmask 18
- SYN valid and ACK invalid, use control-code 2, control bitmask 18
USING THE CLI
Use the command in this section to configure IP ACL parameters from the CLI.
permit, deny (Extended ACL)
This command adds a rule to an Extended IP ACL. The rule sets a filter condition for packets with
specific source or destination IP addresses, protocol types, source or destination protocol ports, or
TCP control codes. Use the no form to remove a rule.
Syntax
[no] {permit | deny} [protocol-number | udp]
{any | source address-bitmask | host source}
{any | destination address-bitmask | host destination}
[precedence precedence] [tos tos] [dscp dscp]
[source-port sport [bitmask]] [destination-port dport [port-bitmask]]
[no] {permit | deny} tcp
{any | source address-bitmask | host source}
{any | destination address-bitmask | host destination}
[precedence precedence] [tos tos] [dscp dscp]
[source-port sport [bitmask]] [destination-port dport [port-bitmask]]
[control-flag control-flags flag-bitmask]
• protocol-number – A specific protocol number. (Range: 0-255)
• source – Source IP address.
• destination – Destination IP address.
• address-bitmask – Decimal number representing the address bits to match.
19-8
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
• host – Keyword followed by a specific IP address.
• precedence – IP precedence level. (Range: 0-7)
• tos – Type of Service level. (Range: 0-15)
• dscp – DSCP priority level. (Range: 0-64)
• sport – Protocol* source port number. (Range: 0-65535)
• dport – Protocol* destination port number. (Range: 0-65535)
• port-bitmask – Decimal number representing the port bits to match. (Range: 0-65535)
• control-flags – Decimal number (representing a bit string) that specifies flag bits in byte 14 of
the TCP header. (Range: 0-63)
• flag-bitmask – Decimal number representing the code bits to match.
* Includes TCP, UDP or other protocol types.
Default Setting
None
Command Mode
Extended ACL
Command Usage
• All new rules are appended to the end of the list.
• Address bitmasks are similar to a subnet mask, containing four integers from 0 to 255, each
separated by a period. The binary mask uses 1 bits to indicate “match” and 0 bits to indicate
“ignore.” The bitmask is bitwise ANDed with the specified source IP address, and then compared
with the address for each IP packet entering the port(s) to which this ACL has been assigned.
• You can specify both Precedence and ToS in the same rule. However, if DSCP is used, then
neither Precedence nor ToS can be specified.
• The control-code bitmask is a decimal number (representing an equivalent bit mask) that is
applied to the control code. Enter a decimal number, where the equivalent binary bit “1” means to
match a bit and “0” means to ignore a bit. The following bits may be specified:
- 1 (fin) – Finish
- 2 (syn) – Synchronize
- 4 (rst) – Reset
- 8 (psh) – Push
- 16 (ack) – Acknowledgement
- 32 (urg) – Urgent pointer
• For example, use the code value and mask below to catch packets with the following flags set:
- SYN flag valid, use “control-code 2 2”
- Both SYN and ACK valid, use “control-code 18 18”
- SYN valid and ACK invalid, use “control-code 2 18”
Example
This example accepts any incoming packets if the source address is within subnet 10.7.1.x. For
example, if the rule is matched; i.e., the rule (10.7.1.0 & 255.255.255.0) equals the masked address
(10.7.1.2 & 255.255.255.0), the packet passes through.
Console(config-ext-acl)#permit 10.7.1.1 255.255.255.0 any
Console(config-ext-acl)#
December 2007
© 2007 Foundry Networks, Inc.
19-9
Foundry EdgeIron User Guide
This allows TCP packets from class C addresses 192.168.1.0 to any destination address when set
for destination TCP port 80 (i.e., HTTP).
Console(config-ext-acl)#permit 192.168.1.0 255.255.255.0 any dport 80
Console(config-ext-acl)#
This permits all TCP packets from class C addresses 192.168.1.0 with the TCP control code set to
“SYN.”
Console(config-ext-acl)#permit 192.168.1.0 255.255.255.0 any tcp control-code 2 2
Console(config-ext-acl)#
Related Commands
access-list ip (19-4)
show ip access-list
This command displays the rules for configured IP ACLs.
Syntax
show ip access-list {standard | extended} [acl_name]
• standard – Specifies a standard IP ACL.
• extended – Specifies an extended IP ACL.
• acl_name – Name of the ACL. (Maximum length: 16 characters)
Command Mode
Privileged Exec
Example
Console#show ip access-list standard
IP standard access-list david:
permit 10.7.1.1 255.255.255.0 any
permit 192.168.1.0 255.255.255.0 any dport 80
permit 192.168.1.0 255.255.255.0 any tcp control-code 2 2
Console#
Related Commands
permit, deny (Standard ACL) (19-6)
ip access-group (19-32)
access-list ip mask-precedence
This command changes to the IP Mask mode used to configure access control masks. Use the no
form to delete the mask table.
Syntax
[no] access-list ip mask-precedence {in | out}
• in – Ingress mask for ingress ACLs.
• out – Egress mask for egress ACLs.
Default Setting
Default system mask: Filter inbound packets according to specified IP ACLs.
19-10
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
Command Mode
Global Configuration
Command Usage
• A mask can only be used by all ingress ACLs or all egress ACLs.
• The precedence of the ACL rules applied to a packet is not determined by order of the rules, but
instead by the order of the masks; i.e., the first mask that matches a rule will determine the rule
that is applied to a packet.
• You must configure a mask for an ACL rule before you can bind it to a port or set the queue or
frame priorities associated with the rule.
Example
Console(config)#access-list ip mask-precedence in
Console(config-ip-mask-acl)#
Related Commands
mask (IP ACL) (19-25)
ip access-group (19-32)
map access-list ip
This command sets the output queue for packets matching an ACL rule. The specified CoS value is
only used to map the matching packet to an output queue; it is not written to the packet itself. Use the
no form to remove the CoS mapping.
Syntax
[no] map access-list ip acl_name cos cos-value
• acl_name – Name of the ACL. (Maximum length: 16 characters)
• cos-value – CoS value. (Range: 0-7)
Default Setting
None
Command Mode
Interface Configuration (Ethernet)
Command Usage
• You must configure an ACL mask before you can map CoS values to the rule.
• A packet matching a rule within the specified ACL is mapped to one of the output queues as
shown in the following table. For information on mapping the CoS values to output queues, see
queue cos-map (25-7).
EdgeIron 24G-A, 48G, 24GS, 48GS, 8X10G
Priority
1
2
4
6
8
10
12
14
Queue
0
1
2
3
4
5
6
7
EdgeIron 4802CF, 2402CF
Priority
1
4
16
64
Queue
0
1
2
3
December 2007
© 2007 Foundry Networks, Inc.
19-11
Foundry EdgeIron User Guide
Example
Console(config)#interface ethernet 1/25
Console(config-if)#map access-list ip bill cos 0
Console(config-if)#
Related Commands
ip access-group (19-32)
show map access-list ip (19-12)
show map access-list ip
This command shows the CoS value mapped to an IP ACL for the current interface. (The CoS value
determines the output queue for packets matching an ACL rule.)
Syntax
show map access-list ip [interface]
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
Command Mode
Privileged Exec
Example
Console#show map access-list ip
Access-list to COS of Eth 1/24
Access-list ALS1 cos 0
Console#
Related Commands
map access-list ip (19-11)
match access-list ip
This command changes the IEEE 802.1p priority, IP Precedence, or DSCP Priority of a frame
matching the defined ACL rule. (This feature is commonly referred to as ACL packet marking.) Use
the no form to remove the ACL marker.
Syntax
match access-list ip acl_name [set priority priority] {set tos tos_value | set dscp dscp_value}
no match access-list ip acl_name
• acl_name – Name of the ACL. (Maximum length: 16 characters)
• priority – Class of Service value in the IEEE 802.1p priority tag. (Range: 0-7; 7 is the highest
priority)
• tos_value – IP Precedence value. (Range: 0-7)
• dscp_value – Differentiated Services Code Point value. (Range: 0-63)
Default Setting
None
19-12
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
Command Mode
Interface Configuration (Ethernet)
Command Usage
• You must configure an ACL mask before you can change frame priorities based on an ACL rule.
• Traffic priorities may be included in the IEEE 802.1p priority tag. This tag is also incorporated as
part of the overall IEEE 802.1Q VLAN tag. To specify this priority, use the set priority keywords.
• The IP frame header also includes priority bits in the Type of Service (ToS) octet. The Type of
Service octet may contain three bits for IP Precedence or six bits for Differentiated Services Code
Point (DSCP) service. To specify the IP precedence priority, use the set tos keywords. To specify
the DSCP priority, use the set dscp keywords. Note that the IP frame header can include either
the IP Precedence or DSCP priority type.
• The precedence for priority mapping by this switch is IP Precedence or DSCP Priority, and then
802.1p priority.
Example
Console(config)#interface ethernet 1/12
Console(config-if)#match access-list ip bill set dscp 0
Console(config-if)#
Related Commands
show marking (19-13)
show marking
This command displays the current configuration for packet marking.
Command Mode
Privileged Exec
Example
Console#show marking
Interface ethernet 1/12
match access-list IP bill set DSCP 0
match access-list MAC a set priority 0
Console#
Related Commands
match access-list ip (19-12)
December 2007
© 2007 Foundry Networks, Inc.
19-13
Foundry EdgeIron User Guide
Configuring a MAC ACL
Note: Egress MAC ACLs only work for destination-mac-known packets, not for multicast,
broadcast, or destination-mac-unknown packets.
The following table briefly describes the commands required to configure a MAC ACL:
19-14
Command
Function
Mode
Page
access-list mac
Creates a MAC ACL and enters configuration mode
GC
19-16
permit, deny
Filters packets matching a specified source and
MACdestination address, packet format, and Ethernet type ACL
19-17
show mac access-list
Displays the rules for configured MAC ACLs
PE
19-18
access-list mac maskprecedence
Changes to the mode for configuring access control
masks
GC
19-19
mask
Sets a precedence mask for the ACL rules
MACMask
19-29
show access-list mac maskprecedence
Shows the ingress or egress rule masks for MAC
ACLs
PE
19-30
permit/deny offset
Filters packets matching a pattern starting at the offset MACACL
19-20
mac access-group
Adds a port to a MAC ACL
IC
19-33
show mac access-group
Shows port assignments for MAC ACLs
PE
19-34
map access-list mac
Sets the CoS value and corresponding output queue
for packets matching an ACL rule
IC
19-21
show map access-list mac
Shows CoS value mapped to an access list for an
interface
PE
19-22
match access-list mac
Changes the 802.1p priority the priority of a frame
matching the defined rule (i.e., also called packet
marking)
IC
19-22
show marking
Displays the current configuration for packet marking
PE
19-13
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
USING THE WEB INTERFACE
Specify the action (i.e., Permit or Deny). Specify the source and/or destination addresses. Select the
address type (Any, Host, or MAC). If you select “Host,” enter a specific address (e.g., 11-22-33-4455-66). If you select “MAC,” enter a base address and a hexidecimal bitmask for an address range.
Set any other required criteria, such as VID, Ethernet type, or packet format. Then click Add.
•
Action – An ACL can contain permit rules, deny rules, or a combination of both.
(Default: Permit rules)
•
Source/Destination Address Type – Use “Any” to include all possible addresses, “Host” to
indicate a specific MAC address, or “MAC” to specify an address range with the Address and
Bitmask fields. (Options: Any, Host, MAC; Default: Any)
•
Source/Destination MAC Address – Source or destination MAC address.
•
Source/Destination Bitmask – Hexidecimal mask for source or destination MAC address.
•
VID – VLAN ID. (Range: 1-4095)
•
VID Mask – VLAN bitmask. (Range: 1-4095)
•
Ethernet Type – This option can only be used to filter Ethernet II formatted packets.
(Range: 600-fff hex.)
A detailed listing of Ethernet protocol types can be found in RFC 1060. A few of the more common
types include 0800 (IP), 0806 (ARP), 8137 (IPX).
Note: IPv6 (08DD) is not supported.
•
Ethernet Type Bitmask – Protocol bitmask. (Range: 600-fff hex.)
December 2007
© 2007 Foundry Networks, Inc.
19-15
Foundry EdgeIron User Guide
•
Packet Format – This attribute includes the following packet types:
-
Any – Any Ethernet packet type.
Untagged-eth2 – Untagged Ethernet II packets.
Untagged-802.3 – Untagged Ethernet 802.3 packets.
Tagged-eth2 – Tagged Ethernet II packets.
Tagged-802.3 – Tagged Ethernet 802.3 packets.
USING THE CLI
Use the command in this section to configure MAC ACL parameters from the CLI.
access-list mac
This command adds a MAC access list and enters MAC ACL configuration mode. Use the no form to
remove the specified ACL.
Syntax
[no] access-list mac acl_name
• acl_name – Name of the ACL. (Maximum length: 16 characters)
Default Setting
None
Command Mode
Global Configuration
Command Usage
• An egress ACL must contain all deny rules.
• When you create a new ACL or enter configuration mode for an existing ACL, use the permit or
deny command to add new rules to the bottom of the list. To create an ACL, you must add at least
one rule to the list.
• To remove a rule, use the no permit or no deny command followed by the exact text of a
previously configured rule.
• An ACL can contain up to 32 rules.
Example
Console(config)#access-list mac jerry
Console(config-mac-acl)#
Related Commands
permit, deny (MAC ACL) (19-17)
mac access-group (19-33)
show mac access-list (19-18)
19-16
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
permit, deny (MAC ACL)
This command adds a rule to a MAC ACL. The rule filters packets matching a specified MAC source
or destination address (i.e., physical layer address), or Ethernet protocol type. Use the no form to
remove a rule.
Syntax
[no] {permit | deny}
{any | host source | source address-bitmask}
{any | host destination | destination address-bitmask}
[vid vid vid-bitmask] [ethertype protocol [protocol-bitmask]]
Note: - The default is for Ethernet II packets.
[no] {permit | deny} tagged-eth2
{any | host source | source address-bitmask}
{any | host destination | destination address-bitmask}
[no vid vid-bitmask] [ethertype protocol [protocol-bitmask]]
[no] {permit | deny} untagged-eth2
{any | host source | source address-bitmask}
{any | host destination | destination address-bitmask}
[ethertype protocol [protocol-bitmask]]
[no] {permit | deny} tagged-802.3
{any | host source | source address-bitmask}
{any | host destination | destination address-bitmask}
[vid vid vid-bitmask]
[no] {permit | deny} untagged-802.3
{any | host source | source address-bitmask}
{any | host destination | destination address-bitmask}
• tagged-eth2 – Tagged Ethernet II packets.
• untagged-eth2 – Untagged Ethernet II packets.
• tagged-802.3 – Tagged Ethernet 802.3 packets.
• untagged-802.3 – Untagged Ethernet 802.3 packets.
• any – Any MAC source or destination address.
• host – A specific MAC address.
• source – Source MAC address.
• destination – Destination MAC address range with bitmask.
• address-bitmask* – Bitmask for MAC address (in hexidecimal format).
• vid – VLAN ID. (Range: 1-4095)
• vid-bitmask* – VLAN bitmask. (Range: 1-4095)
• protocol – A specific Ethernet protocol number. (Range: 600-fff hex.)
• protocol-bitmask* – Protocol bitmask. (Range: 600-fff hex.)
* For all bitmasks, “1” means care and “0” means ignore.
Default Setting
None
December 2007
© 2007 Foundry Networks, Inc.
19-17
Foundry EdgeIron User Guide
Command Mode
MAC ACL
Command Usage
• New rules are added to the end of the list.
• The ethertype option can only be used to filter Ethernet II formatted packets.
• A detailed listing of Ethernet protocol types can be found in RFC 1060. A few of the more common
types include the following:
- 0800 - IP
- 0806 - ARP
- 8137 - IPX
Example
This rule permits packets from any source MAC address to the destination address 00-e0-29-94-34de where the Ethernet type is 0800.
Console(config-mac-acl)#permit any host 00-e0-29-94-34-de
ethertype 0800
Console(config-mac-acl)#
Related Commands
access-list mac (19-16)
show mac access-list
This command displays the rules for configured MAC ACLs.
Syntax
show mac access-list [acl_name]
• acl_name – Name of the ACL. (Maximum length: 16 characters)
Command Mode
Privileged Exec
Example
Console#show mac access-list
MAC access-list jerry:
permit any 00-e0-29-94-34-de ethertype 0800
Console#
Related Commands
permit, deny (MAC ACL) (19-17)
mac access-group (19-33)
19-18
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
access-list mac mask-precedence
This command changes to MAC Mask mode used to configure access control masks. Use the no
form to delete the mask table.
Syntax
[no] access-list ip mask-precedence {in | out}
• in – Ingress mask for ingress ACLs.
• out – Egress mask for egress ACLs.
Default Setting
Default system mask: Filter inbound packets according to specified MAC ACLs.
Command Mode
Global Configuration
Command Usage
• You must configure a mask for an ACL rule before you can bind it to a port or set the queue or
frame priorities associated with the rule.
• A mask can only be used by all ingress ACLs or all egress ACLs.
• The precedence of the ACL rules applied to a packet is not determined by order of the rules, but
instead by the order of the masks; i.e., the first mask that matches a rule will determine the rule
that is applied to a packet.
Example
Console(config)#access-list mac mask-precedence in
Console(config-mac-mask-acl)#
Related Commands
mask (MAC ACL) (19-29)
mac access-group (19-33)
show access-list mac mask-precedence
This command shows the ingress or egress rule masks for MAC ACLs.
Syntax
show access-list mac mask-precedence [in | out]
• in – Ingress mask precedence for ingress ACLs.
• out – Egress mask precedence for egress ACLs.
Command Mode
Privileged Exec
Example
Console#show access-list mac mask-precedence
MAC egress mask ACL:
mask pktformat host any vid ethertype
Console#
December 2007
© 2007 Foundry Networks, Inc.
19-19
Foundry EdgeIron User Guide
Related Commands
mask (MAC ACL) (19-29)
permit offset, deny offset (MAC ACL)
Use this command to add a rule to a MAC ACL. The rule filters packets matching the specified data
pattern starting at the offset. Use the no form to remove a rule.
Syntax
{permit | deny} offset offset_value length bitmask data
no {permit | deny} offset offset_value length bitmask data
• offset_value – Byte offset from the beginning of the frame.
• length – Length of the data pattern to match.
• bitmask – Decimal number representing the data bits to match.
• data – Data to match, entered as a sequence of hexadecimal letters with no separators.
Default Setting
None
Command Mode
MAC ACL
Command Usage
• This command is used to filter frames that match a specified pattern, and can be used to filter
traffic associated with precisely defined events.
• The bitmask is a decimal number (representing an equivalent bit mask) that is applied to the data.
Enter a decimal number, where the equivalent binary bit “1” means to match a bit and “0” means
to ignore a bit.
• Packet filtering based on arbitrary offsets and data patterns can adversely affect switch
throughput. Try to avoid using packet filtering based on pattern matching unless this is absolutely
necessary to solve a specific problem.
Example
This example shows how to filter any Ethernet II packets directed to the IP address 10.1.0.23 that
have the Don’t Fragment flag set.
Console(config)#access-list mac jerry
Console(config-mac-acl)#permit offset ???
Related Commands
mac access-group (19-33)
show mac access-list (19-18)
19-20
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
map access-list mac
This command sets the output queue for packets matching an ACL rule. The specified CoS value is
only used to map the matching packet to an output queue; it is not written to the packet itself. Use the
no form to remove the CoS mapping.
Syntax
[no] map access-list mac acl_name cos cos-value
• acl_name – Name of the ACL. (Maximum length: 16 characters)
• cos-value – CoS value. (Range: 0-7)
Default Setting
None
Command Mode
Interface Configuration (Ethernet)
Command Usage
• You must configure an ACL mask before you can map CoS values to the rule.
• A packet matching a rule within the specified ACL is mapped to one of the output queues as
shown below.
EdgeIron 24G-A, 48G, 24GS, 48GS, 8X10G
Priority
1
2
4
6
8
10
12
14
Queue
0
1
2
3
4
5
6
7
EdgeIron 4802CF, 2402CF
Priority
1
4
16
64
Queue
0
1
2
3
Example
Console(config)#int eth 1/5
Console(config-if)#map access-list mac M5 cos 0
Console(config-if)#
Related Commands
show mac access-list (19-18)
show map access-list mac (19-22)
December 2007
© 2007 Foundry Networks, Inc.
19-21
Foundry EdgeIron User Guide
show map access-list mac
This command shows the CoS value mapped to a MAC ACL for the current interface. (The CoS
value determines the output queue for packets matching an ACL rule.)
Syntax
show map access-list mac [interface]
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
Command Mode
Privileged Exec
Example
Console#show map access-list mac
Access-list to COS of Eth 1/5
Access-list M5 cos 0
Console#
Related Commands
map access-list mac (19-21)
match access-list mac
This command changes the IEEE 802.1p priority of a Layer 2 frame matching the defined ACL rule.
(This feature is commonly referred to as ACL packet marking.) Use the no form to remove the ACL
marker.
Syntax
match access-list mac acl_name set priority priority
no match access-list mac acl_name
• acl_name – Name of the ACL. (Maximum length: 16 characters)
• priority – Class of Service value in the IEEE 802.1p priority tag. (Range: 0-7; 7 is the highest
priority)
Default Setting
None
Command Mode
Interface Configuration (Ethernet)
Command Usage
You must configure an ACL mask before you can change frame priorities based on an ACL rule.
Example
Console(config)#interface ethernet 1/12
Console(config-if)#match access-list mac a set priority 0
Console(config-if)#
19-22
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
Related Commands
show marking (19-13)
Configuring ACL Masks
You can specify optional masks that control the order in which ACL rules are checked. The switch
includes two system default masks that pass/filter packets matching the permit/deny rules specified
in an ingress ACL. You can also configure up to seven user-defined masks for an ingress or egress
ACL. A mask must be bound exclusively to one of the basic ACL types (i.e., Ingress IP ACL, Egress
IP ACL, Ingress MAC ACL or Egress MAC ACL), but a mask can be bound to up to four ACLs of the
same type.
•
Up to seven entries can be assigned to an ACL mask.
•
Packets crossing a port are checked against all the rules in the ACL until a match is found. The
order in which these packets are checked is determined by the mask, and not the order in which
the ACL rules are entered.
•
First create the required ACLs and the ingress or egress masks before mapping an ACL to an
interface.
•
You must configure a mask for an ACL rule before you can bind it to a port or set the queue or
frame priorities associated with the rule.
Specifying the Mask Type
To configure an ACL mask you must first specify the mask type.
USING THE WEB INTERFACE
Use the ACL Mask Configuration page to edit the mask for the Ingress IP ACL, Egress IP ACL,
Ingress MAC ACL or Egress MAC ACL.
Click Security, ACL, ACL Mask Configuration. Click Edit for one of the basic mask types to open the
configuration page.
USING THE CLI
Use the command in this section to configure IP ACL mask parameters from the CLI.
December 2007
© 2007 Foundry Networks, Inc.
19-23
Foundry EdgeIron User Guide
Example
This example creates an IP ingress mask with two rules. Each rule is checked in order of
precedence to look for a match in the ACL entries. The first entry matching a mask is applied to the
inbound packet.
Console(config)#access-list ip mask-precedence in
Console(config-ip-mask-acl)#mask host any
Console(config-ip-mask-acl)#mask 255.255.255.0 any
Console(config-ip-mask-acl)#
Configuring an IP ACL Mask
This mask defines the fields to check in the IP header.
•
Masks that include an entry for a Layer 4 protocol source port or destination port can only be
applied to packets with a header length of exactly five bytes.
Configure the mask to match the required rules in the IP ingress or egress ACLs. Set the mask to
check for any source or destination address, a specific host address, or an address range. Include
other criteria to search for in the rules, such as a protocol type or one of the service types. Or use a
bitmask to search for specific protocol port(s) or TCP control code(s). Then click Add.
USING THE WEB INTERFACE
19-24
•
Source/Destination Address Type – Use “Any” to include all possible addresses, “Host” to
indicate a specific MAC address, or “MAC” to specify an address range with the Address and
Bitmask fields. (Options: Any, Host, MAC; Default: Any)
•
Source/Destination Subnet Mask – Subnet mask for source or destination address. (See
“Configuring a Standard IP ACL” on page 19-5.)
•
Protocol Mask – Check the protocol field.
•
Service Type Mask – Check the rule for the specified priority type. (Options: Precedence, TOS,
DSCP; Default: TOS)
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
•
Source/Destination Port Bitmask – Protocol port of rule must match this bitmask.
(Range: 0-65535)
•
Control Bitmask – Control flags of rule must match this bitmask. (Range: 0-63)
USING THE CLI
Use the command in this section to configure IP ACL mask parameters from the CLI.
mask (IP ACL)
This command defines a mask for IP ACLs. This mask defines the fields to check in the IP header.
Use the no form to remove a mask.
Syntax
[no] mask [protocol]
{any | host | source-bitmask}
{any | host | destination-bitmask}
[precedence] [tos] [dscp]
[source-port [port-bitmask]] [destination-port [port-bitmask]]
[control-flag [flag-bitmask]]
• protocol – Check the protocol field.
• any – Any address will be matched.
• host – The address must be for a host device, not a subnetwork.
• source-bitmask – Source address of rule must match this bitmask.
• destination-bitmask – Destination address of rule must match this bitmask.
• precedence – Check the IP precedence field.
• tos – Check the TOS field.
• dscp – Check the DSCP field.
• source-port – Check the protocol source port field.
• destination-port – Check the protocol destination port field.
• port-bitmask – Protocol port of rule must match this bitmask. (Range: 0-65535)
• control-flag – Check the field for control flags.
• flag-bitmask – Control flags of rule must match this bitmask. (Range: 0-63)
Default Setting
None
Command Mode
IP Mask
Command Usage
• Packets crossing a port are checked against all the rules in the ACL until a match is found. The
order in which these packets are checked is determined by the mask, and not the order in which
the ACL rules were entered.
• First create the required ACLs and ingress or egress masks before mapping an ACL to an
interface.
• If you enter dscp, you cannot enter tos or precedence. You can enter both tos and precedence
without dscp.
December 2007
© 2007 Foundry Networks, Inc.
19-25
Foundry EdgeIron User Guide
• Masks that include an entry for a Layer 4 protocol source port or destination port can only be
applied to packets with a header length of exactly five bytes.
Example
This example creates an IP ingress mask with two rules. Each rule is checked in order of
precedence to look for a match in the ACL entries. The first entry matching a mask is applied to the
inbound packet.
Console(config)#access-list ip mask-precedence in
Console(config-ip-mask-acl)#mask host any
Console(config-ip-mask-acl)#mask 255.255.255.0 any
Console(config-ip-mask-acl)#
This shows that the entries in the mask override the precedence in which the rules are entered into
the ACL. In the following example, packets with the source address 10.1.1.1 are dropped because
the “deny 10.1.1.1 255.255.255.255” rule has the higher precedence according the “mask host any”
entry.
Console(config)#access-list ip standard A2
Console(config-std-acl)#permit 10.1.1.0 255.255.255.0
Console(config-std-acl)#deny 10.1.1.1 255.255.255.255
Console(config-std-acl)#exit
Console(config)#access-list ip mask-precedence in
Console(config-ip-mask-acl)#mask host any
Console(config-ip-mask-acl)#mask 255.255.255.0 any
Console(config-ip-mask-acl)#
This shows how to create a standard ACL with an ingress mask to deny access to the IP host
171.69.198.102, and permit access to any others.
Console(config)#access-list ip standard A2
Console(config-std-acl)#permit any
Console(config-std-acl)#deny host 171.69.198.102
Console(config-std-acl)#end
Console#show access-list
IP standard access-list A2:
deny host 171.69.198.102
permit any
Console#configure
Console(config)#access-list ip mask-precedence in
Console(config-ip-mask-acl)#mask host any
Console(config-ip-mask-acl)#exit
Console(config)#interface ethernet 1/1
Console(config-if)#ip access-group A2 in
Console(config-if)#end
Console#show access-list
IP standard access-list A2:
deny host 171.69.198.102
permit any
Console#
19-26
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
This shows how to create an extended ACL with an egress mask to drop packets leaving network
171.69.198.0 when the Layer 4 source port is 23.
Console(config)#access-list ip extended A3
Console(config-ext-acl)#deny host 171.69.198.5 any
Console(config-ext-acl)#deny 171.69.198.0 255.255.255.0 any sourceport 23
Console(config-ext-acl)#end
Console#show access-list
IP extended access-list A3:
deny host 171.69.198.5 any
deny 171.69.198.0 255.255.255.0 any source-port 23
Console#config
Console(config)#access-list ip mask-precedence out
Console(config-ip-mask-acl)#mask 255.255.255.0 any source-port
Console(config-ip-mask-acl)#exit
Console(config)#interface ethernet 1/15
Console(config-if)#ip access-group A3 out
Console(config-if)#end
Console#show access-list
IP extended access-list A3:
deny 171.69.198.0 255.255.255.0 any source-port 23
deny host 171.69.198.5 any
IP egress mask ACL:
mask 255.255.255.0 any source-port
Console#
This is a more comprehensive example. It denies any TCP packets in which the SYN bit is ON, and
permits all other packets. It then sets the ingress mask to check the deny rule first, and finally binds
port 1 to this ACL. Note that once the ACL is bound to an interface (i.e., the ACL is active), the order
in which the rules are displayed is determined by the associated mask.
Switch(config)#access-list ip extended 6
Switch(config-ext-acl)#permit any any
Switch(config-ext-acl)#deny tcp any any control-flag 2 2
Switch(config-ext-acl)#end
Console#show access-list
IP extended access-list A6:
permit any any
deny tcp any any control-flag 2 2
Console#configure
Switch(config)#access-list ip mask-precedence in
Switch(config-ip-mask-acl)#mask protocol any any control-flag 2
Switch(config-ip-mask-acl)#end
Console#show access-list
IP extended access-list A6:
permit any any
deny tcp any any control-flag 2 2
IP ingress mask ACL:
mask protocol any any control-flag 2
Console#configure
Console(config)#interface ethernet 1/1
Console(config-if)#ip access-group A6 in
Console(config-if)#end
Console#show access-list
IP extended access-list A6:
deny tcp any any control-flag 2 2
permit any any
IP ingress mask ACL:
mask protocol any any control-flag 2
Console#
December 2007
© 2007 Foundry Networks, Inc.
19-27
Foundry EdgeIron User Guide
Configuring a MAC ACL Mask
This mask defines the fields to check in the packet header.
Note: You must configure a mask for an ACL rule before you can bind it to a port.
USING THE WEB INTERFACE
Configure the mask to match the required rules in the MAC ingress or egress ACLs. Set the mask to
check for any source or destination address, a host address, or an address range. Use a bitmask to
search for specific VLAN ID(s) or Ethernet type(s). Or check for rules where a packet format was
specified. Then click Add.
19-28
•
Source/Destination Address Type – Use “Any” to match any address, “Host” to specify the host
address for a single node, or “MAC” to specify a range of addresses. (Options: Any, Host, MAC;
Default: Any)
•
Source/Destination Bitmask – Address of rule must match this bitmask.
•
VID Bitmask – VLAN ID of rule must match this bitmask.
•
Ethernet Type Bitmask – Ethernet type of rule must match this bitmask.
•
Packet Format Bitmask – A packet format must be specified in the rule.
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
USING THE CLI
Use the command in this section to configure MAC ACL mask parameters from the CLI.
mask (MAC ACL)
This command defines a mask for MAC ACLs. This mask defines the fields to check in the packet
header. Use the no form to remove a mask.
Syntax
[no] mask [pktformat]
{any | host | source-bitmask} {any | host | destination-bitmask}
[vid [vid-bitmask]] [ethertype [ethertype-bitmask]]
• pktformat – Check the packet format field. (If this keyword must be used in the mask, the
packet format must be specified in ACL rule to match.)
• any – Any address will be matched.
• host – The address must be for a single node.
• source-bitmask – Source address of rule must match this bitmask.
• destination-bitmask – Destination address of rule must match this bitmask.
• vid – Check the VLAN ID field.
• vid-bitmask – VLAN ID of rule must match this bitmask.
• ethertype – Check the Ethernet type field.
• ethertype-bitmask – Ethernet type of rule must match this bitmask.
Default Setting
None
Command Mode
MAC Mask
Command Usage
• Up to seven masks can be assigned to an ingress or egress ACL.
• Packets crossing a port are checked against all the rules in the ACL until a match is found. The
order in which these packets are checked is determined by the mask, and not the order in which
the ACL rules were entered.
• First create the required ACLs and inbound or outbound masks before mapping an ACL to an
interface.
December 2007
© 2007 Foundry Networks, Inc.
19-29
Foundry EdgeIron User Guide
Example
This example shows how to create an Ingress MAC ACL and bind it to a port. You can then see that
the order of the rules have been changed by the mask.
Console(config)#access-list mac M4
Console(config-mac-acl)#permit any any
Console(config-mac-acl)#deny tagged-eth2 00-11-11-11-11-11
ff-ff-ff-ff-ff-ff any vid 3
Console(config-mac-acl)#end
Console#show access-list
MAC access-list M4:
permit any any
deny tagged-eth2 host 00-11-11-11-11-11 any vid 3
Console(config)#access-list mac mask-precedence in
Console(config-mac-mask-acl)#mask pktformat
ff-ff-ff-ff-ff-ff any vid
Console(config-mac-mask-acl)#exit
Console(config)#interface ethernet 1/12
Console(config-if)#mac access-group M4 in
Console(config-if)#end
Console#show access-list
MAC access-list M4:
deny tagged-eth2 host 00-11-11-11-11-11 any vid 3
permit any any
MAC ingress mask ACL:
mask pktformat host any vid
Console#
This example creates an Egress MAC ACL.
Console(config)#access-list mac M5
Console(config-mac-acl)#deny tagged-802.3 host
00-11-11-11-11-11 any
Console(config-mac-acl)#deny tagged-eth2 00-11-11-11-11-11
ff-ff-ff-ff-ff-ff any vid 3 ethertype 0806
Console(config-mac-acl)#end
Console#show access-list
MAC access-list M5:
deny tagged-802.3 host 00-11-11-11-11-11 any
deny tagged-eth2 host 00-11-11-11-11-11 any vid 3
ethertype 0806
Console(config)#access-list mac mask-precedence out
Console(config-mac-mask-acl)#mask pktformat
ff-ff-ff-ff-ff-ff any vid
Console(config-mac-mask-acl)#exit
Console(config)#interface ethernet 1/5
Console(config-if)#mac access-group M5 out
Console(config-if)#end
Console#show access-list
MAC access-list M5:
deny tagged-eth2 host 00-11-11-11-11-11 any vid
3 ethertype 0806
deny tagged-802.3 host 00-11-11-11-11-11 any
MAC ingress mask ACL:
mask pktformat host any vid ethertype
Console#
show access-list ip mask-precedence
This command shows the ingress or egress rule masks for IP ACLs.
Syntax
show access-list ip mask-precedence [in | out]
• in – Ingress mask precedence for ingress ACLs.
• out – Egress mask precedence for egress ACLs.
19-30
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
Command Mode
Privileged Exec
Example
Console#show access-list ip mask-precedence
IP ingress mask ACL:
mask host any
mask 255.255.255.0 any
Console#
Related Commands
mask (IP ACL) (19-25)
Binding a Port to an Access Control List
After configuring the Access Control Lists (ACL), you can bind the ports that need to filter traffic to
the appropriate ACLs. You can only bind a port to one ACL for each basic type – IP ingress, IP
egress, MAC ingress and MAC egress.
Command Usage
• This switch supports ACLs for both ingress and egress filtering. However, you can only bind one
IP ACL and one MAC ACL to any port for ingress filtering, and one IP ACL and one MAC ACL to
any port for egress filtering. In other words, only four ACLs can be bound to an interface – Ingress
IP ACL, Egress IP ACL, Ingress MAC ACL and Egress MAC ACL.
•
When an ACL is bound to an interface as an egress filter, all entries in the ACL must be deny
rules. Otherwise, the bind operation will fail.
•
The switch does not support the explicit “deny any any” rule for the egress IP ACL or the egress
MAC ACLs. If these rules are included in the ACL, and you attempt to bind the ACL to an interface
for egress checking, the bind operation will fail.
USING THE WEB INTERFACE
Click ACL, ACL Port Binding. Mark the Enable field for the port you want to bind to an ACL for
ingress or egress traffic, select the required ACL from the drop-down list, then click Apply.
•
Port – Fixed port or SFP module.
December 2007
© 2007 Foundry Networks, Inc.
19-31
Foundry EdgeIron User Guide
•
IP – Specifies the IP ACL to bind to a port.
•
MAC – Specifies the MAC ACL to bind to a port.
•
IN – ACL for ingress packets.
•
OUT – ACL for egress packets.
•
ACL Name – Name of the ACL.
USING THE CLI
Use the command in this section to configure MAC ACL mask parameters from the CLI.
ip access-group
This command binds a port to an IP ACL. Use the no form to remove the port.
Syntax
[no] ip access-group acl_name {in | out}
• acl_name – Name of the ACL. (Maximum length: 16 characters)
• in – Indicates that this list applies to ingress packets.
• out – Indicates that this list applies to egress packets.
Default Setting
None
Command Mode
Interface Configuration (Ethernet)
Command Usage
• A port can only be bound to one ACL.
• If a port is already bound to an ACL and you bind it to a different ACL, the switch will replace the
old binding with the new one.
• You must configure a mask for an ACL rule before you can bind it to a port.
Example
Console(config)#int eth 1/25
Console(config-if)#ip access-group standard david in
Console(config-if)#
Related Commands
show ip access-list (19-10)
19-32
© 2007 Foundry Networks, Inc.
March 2007
Access Control Lists
mac access-group
This command binds a port to a MAC ACL. Use the no form to remove the port.
Syntax
mac access-group acl_name {in | out}
• acl_name – Name of the ACL. (Maximum length: 16 characters)
• in – Indicates that this list applies to ingress packets.
• out – Indicates that this list applies to egress packets.
Default Setting
None
Command Mode
Interface Configuration (Ethernet)
Command Usage
• A port can only be bound to one ACL.
• If a port is already bound to an ACL and you bind it to a different ACL, the switch will replace the
old binding with the new one.
Example
Console(config)#interface ethernet 1/25
Console(config-if)#mac access-group jerry in
Console(config-if)#
Related Commands
show mac access-list (19-18)
ACL Information
The table that follows briefly describes the CLI show commands:
Command
Function
Mode
Page
show ip access-list
Show all ACLs and associated rules
PE
19-30
show ip access-group
Shows the ACLs assigned to each port
PE
19-34
show mac access-group
Shows port assignments for MAC ACLs
PE
19-34
show ip access-group
This command shows the ports assigned to IP ACLs.
Command Mode
Privileged Exec
December 2007
© 2007 Foundry Networks, Inc.
19-33
Foundry EdgeIron User Guide
Example
Console#show ip access-group
Interface ethernet 1/25
IP standard access-list david
Console#
Related Commands
ip access-group (19-32)
show ip access-group
This command shows the ports assigned to IP ACLs.
Command Mode
Privileged Exec
Example
Console#show ip access-group
Interface ethernet 1/25
IP standard access-list david
Console#
Related Commands
ip access-group (19-32)
show mac access-group
This command shows the ports assigned to MAC ACLs.
Command Mode
Privileged Exec
Example
Console#show mac access-group
Interface ethernet 1/5
MAC access-list M5 out
Console#
Related Commands
mac access-group (19-33)
19-34
© 2007 Foundry Networks, Inc.
March 2007
Chapter 20
Address Table
Switches store the addresses for all known devices. This information is used to route traffic directly
between the inbound and outbound ports. All the addresses learned by monitoring traffic are stored
in the dynamic address table. You can also manually configure static addresses that are bound to a
specific port.
The CLI commands for this section are briefly described in the table that follows:
Command
Function
Mode
Page
mac-address-table static
Maps a static address to a port in a VLAN
GC
20-2
show mac-address-table
Displays entries in the forwarding database
PE
20-3
show mac-address-table
port-secure
Displays port security MAC addresses
PE
20-5
clear mac-address-table
dynamic
Removes any learned entries from the forwarding
database
PE
20-6
mac-address-table agingtime
Sets the aging time of the address table
GC
20-7
show mac-address-table
aging-time
Shows the aging time for the address table
PE
20-7
Setting Static Addresses
A static address can be assigned to a specific interface on this switch. Static addresses are bound to
the assigned interface and will not be moved. When a static address is seen on another interface,
the address will be ignored and will not be written to the address table.
Command Usage
Entries specified via both the Web interface and the CLI can be made permanent or can be set to be
deleted on reset.
December 2007
© 2007 Foundry Networks, Inc.
20-1
Foundry EdgeIron User Guide
USING THE WEB INTERFACE
Click Address Table, Static Addresses. Specify the interface, the MAC address and VLAN, then click
Add Static Address.
•
Static Address Counts* – The number of manually configured addresses.
•
Current Static Address Table – Lists all the static addresses.
•
Interface – Port or trunk associated with the device assigned a static address.
•
MAC Address – Physical address of a device mapped to this interface.
•
VLAN – ID of configured VLAN (1-4094).
*Web Only
USING THE CLI
Use the commands in this section to configure and display a static address table.
mac-address-table static
Use this command to map a static address to a port in a VLAN. Use the no form to remove an
address.
Syntax
mac-address-table static mac-address interface vlan vlan-id [action]
no mac-address-table static mac-address vlan vlan-id
• mac-address - MAC address.
• interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-4)
20-2
© 2007 Foundry Networks, Inc.
March 2007
Address Table
• vlan-id - VLAN ID (Range: 1-4094)
• action • delete-on-reset - Assignment lasts until switch is reset.
• permanent - Assignment is permanent.
Default Setting
No static addresses are defined. The default mode is permanent.
Command Mode
Global Configuration
Command Usage
The static address for a host device can be assigned to a specific port within a specific VLAN.
Use this command to add static addresses to the MAC Address Table. Static addresses have the
following characteristics:
• Static addresses will not be removed from the address table when a given interface link is down.
• Static addresses are bound to the assigned interface and will not be moved. When a static
address is seen on another interface, the address will be ignored and will not be written to the
address table.
• A static address cannot be learned on another port until the address is removed with the no form
of this command.
Example
Console(config)#mac-address-table static 00-e0-29-94-34-de ethernet
1/1 vlan 1 delete-on-reset
Console(config)#
show mac-address-table
Use this command to view classes of entries in the bridge-forwarding database.
Syntax
show mac-address-table [address mac-address [mask]] [interface interface] [vlan vlan-id]
[sort {address | vlan | interface}]
• mac-address - MAC address.
• mask - Bits to match in the address.
• interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-4)
• vlan-id - VLAN ID (Range: 1-4094)
• sort - Sort by address, vlan or interface.
Default Setting
None
Command Mode
Privileged Exec
December 2007
© 2007 Foundry Networks, Inc.
20-3
Foundry EdgeIron User Guide
Command Usage
• The MAC Address Table contains the MAC addresses associated with each interface. Note that
the Type field may include the following types:
- Learned - dynamic address entries
- Permanent - static entry
- Delete-on-reset - static entry to be deleted when system is reset
• The mask should be hexadecimal numbers (representing an equivalent bit mask) in the form xxxx-xx-xx-xx-xx that is applied to the specified MAC address. Enter hexadecimal numbers, where
an equivalent binary bit “0” means to match a bit and “1” means to ignore a bit. For example, a
mask of 00-00-00-00-00-00 means an exact match, and a mask of FF-FF-FF-FF-FF-FF means
“any.”
• The maximum number of address entries is 8191.
Example
Console#show mac-address-table
Interface Mac Address
Vlan Type
--------- ----------------- ---- ----------------Eth 1/ 1 00-e0-29-94-34-de
1
Delete-on-reset
Console#
Displaying the Address Table
The Dynamic Address Table contains the MAC addresses learned by monitoring the source address
for traffic entering the switch. When the destination address for inbound traffic is found in the
database, the packets intended for that address is forwarded directly to the associated port.
Otherwise, the traffic is flooded to all ports.
Command Usage
• You can display entries in the dynamic address table by selecting an interface (either port or
trunk), MAC address, or VLAN.
•
20-4
You can sort the information displayed based on interface (port or trunk), MAC address, or VLAN.
© 2007 Foundry Networks, Inc.
March 2007
Address Table
USING THE WEB INTERFACE
Click Address Table, Dynamic Addresses. Specify the search type (i.e., Interface, MAC Address, or
VLAN), the method of sorting the displayed addresses, then click Query.
For example, the following screen shows the dynamic addresses for port 5.
•
Interface – Indicates a port or trunk.
•
MAC Address – Physical address associated with this interface.
•
VLAN – ID of configured VLAN (1-4094).
•
Address Table Sort Key – You can sort the information displayed based on interface (port or
trunk) or MAC address.
•
Dynamic Address Counts – The number of addresses dynamically learned.
•
Current Dynamic Address Table – Lists all the dynamic addresses.
USING THE CLI
To display dynamically learned MAC addresses use the show mac-address-table command. To
remove learned entries from a dynamic address table use the following command.
show mac-address-table port-secure
Use this command to display port security MAC addresses.
Syntax
show mac-address-table [[port-secure [interface interface-id]]]
• interface-id - Specifies a port interface.
Default Setting
Displays all learned secure MAC addresses for the specified interface.
December 2007
© 2007 Foundry Networks, Inc.
20-5
Foundry EdgeIron User Guide
Command Mode
Privileged Exec
Example
The following example clears statistics on port 5.
Console#show mac-address-table port secure
Total entries: X
Interface
MAC Address
VLAN
Type
--------------------------------Eth 1/1
0-0-0-0-1-1
2
Port-secure
Eth 1/1
0-0-0-0-1-2
2
Port-secure
Eth 1/2
0-0-0-0-2-1
3
Port-secure
Console#
clear mac-address-table dynamic
Use this command to remove any learned entries from the forwarding database and to clear the
transmit and receive counts for any static or system configured entries.
Default Setting
None
Command Mode
Privileged Exec
Example
Console#clear mac-address-table dynamic
Console#
Changing the Aging Time
You can set the aging time for entries in the dynamic address table.
Command Usage
• The range for the aging time is 10 - 1000000 seconds. (The default is 300 seconds.)
USING THE WEB INTERFACE
Click Address Table, Address Aging. Check "Aging Status", specify the new aging time, then click
Apply.
20-6
•
Aging Status – Enables or disables the aging time.
•
Aging Time – The time after which a learned entry is discarded.
(Range: 10-1000000 seconds; Default: 300 seconds)
© 2007 Foundry Networks, Inc.
March 2007
Address Table
USING THE CLI
mac-address-table aging-time
Use this command to set the aging time for entries in the address table. Use the no form to restore
the default aging time.
Syntax
mac-address-table aging-time seconds
no mac-address-table aging-time
seconds - Time is number of seconds
(EdgeIron 24GS, 48GS, 8X10G, 4802CF, 2402CF, 24G-A and 48G: 0, or 10-1000000)
Default Setting
300 seconds
Command Mode
Global Configuration
Command Usage
The aging time is used to age out dynamically learned forwarding information.
Example
Console(config)#mac-address-table aging-time 100
Console(config)#
show mac-address-table aging-time
Use this command to show the aging time for entries in the address table.
Default Setting
None
Command Mode
Privileged Exec
Example
Console#show mac-address-table aging-time
Aging time: 300 sec.
Console#
December 2007
© 2007 Foundry Networks, Inc.
20-7
Foundry EdgeIron User Guide
20-8
© 2007 Foundry Networks, Inc.
March 2007
Chapter 21
Spanning Tree Protocol
The Spanning Tree Protocol (STP) can be used to detect and disable network loops, and to provide
backup links between switches, bridges or routers. This allows the switch to interact with other
bridging devices (i.e., an STP-compliant switch, bridge or router) in your network to ensure that only
one route exists between any two stations on the network, and provide backup links that
automatically take over when a primary link goes down.
The Spanning Tree Protocols supported by the switch include the following standards:
•
STP – Spanning Tree Protocol (IEEE 802.1D).
•
RSTP – Rapid Spanning Tree Protocol (IEEE 802.1w).
•
Foundry Per VLAN STP – Foundry Per VLAN spanning tree backward compatible.
•
Foundry Per VLAN RSTP – Foundry Per VLAN rapid spanning tree.
STP uses a distributed algorithm to select a bridging device (STP-compliant switch, bridge or router)
that serves as the root of the spanning tree network. It selects a root port on each bridging device
(except for the root device) that incurs the lowest path cost when forwarding a packet from that
device to the root device. Then it selects a designated bridging device from each LAN that incurs the
lowest path cost when forwarding a packet from that LAN to the root device. All ports connected to
designated bridging devices are assigned as designated ports. After determining the lowest cost
spanning tree, it enables all root ports and designated ports, and disables all other ports. Network
packets are therefore only forwarded between root ports and designated ports, eliminating any
possible network loops.
Once a stable network topology has been established, all bridges listen for Hello BPDUs (Bridge
Protocol Data Units) transmitted from the Root Bridge. If a bridge does not get a Hello BPDU after a
predefined interval (Maximum Age), the bridge assumes that the link to the Root Bridge is down.
This bridge will then initiate negotiations with other bridges to reconfigure the network to reestablish
a valid network topology.
RSTP is designed as a general replacement for the slower, legacy STP. RSTP achieves much faster
reconfiguration (around one tenth of that required by STP) by reducing the number of state changes
before active ports start learning, predefining an alternate route that can be used when a node or
port fails, and retaining the forwarding database for ports insensitive to changes in the tree structure
when reconfiguration occurs.
December 2007
© 2007 Foundry Networks, Inc.
21-1
Foundry EdgeIron User Guide
BPDU Prioritization
Spanning tree relies on Bridge Priority Data Units (BPDUs) to be exchanged in order to maintain a
stable network. If a port stops receiving BPDUs, the EdgeIron assumes that a link is down. The
EdgeIron then sends a Topology Change Notification, causing a spanning-tree recalculation.
Beginning with software release 2.2.6.15, BPDUs are processed by the CPU ahead of other traffic;
otherwise, the EdgeIron might assume that are no BPDUs in the traffic and send a Topology Change
Notification. This BPDU prioritization is critical if there is a high volume of traffic destined for the
CPU. This feature helps to maintain a stable spanning-tree topology, particularly in networks with a
high level of broadcast traffic.
The CLI commands for this section are briefly described in the table that follows:
Command
Function
Mode
Page
spanning-tree single
Enables a single spanning tree mode and disables PVST
GC
21-15
spanning-tree
Enables the spanning tree protocol
GC
21-10
spanning-tree
forward-time
Configures the spanning tree bridge forward time
GC
21-11
spanning-tree hello-time
Configures the spanning tree bridge hello time
GC
21-12
spanning-tree max-age
Configures the spanning tree bridge maximum age
GC
21-12
spanning-tree priority
Configures the spanning tree bridge priority
GC
21-13
spanning-tree
path-cost method
Configures the path cost method for RSTP
GC
21-13
spanning-tree
transmission-limit
Configures the transmission limit for RSTP
GC
21-14
spanning-tree
spanning-disabled
Disables spanning tree for an interface
IC
21-14
show spanning-tree
Shows the spanning tree configuration for the common
spanning tree or for an instance within the multiple spanning
tree
PE
21-5
Enabling a Single Instance of STP per VLAN on an EdgeIron
When you create a port-based VLAN on a Foundry Layer 2 Switch, a Spanning Tree Protocol (STP)
instance is automatically created for the VLAN. In addition, the default VLAN has its own instance of
STP. (Refer to the "Configuring Spanning Tree Protocol" chapter in the Foundry Switch and Router
Installation and Basic Configuration Guide.)
Note: This feature is available on devices running release 2.2.4.11 and later.
21-2
© 2007 Foundry Networks, Inc.
March 2007
Spanning Tree Protocol
A VLAN with its own STP instance ensures that it is isolated from STP problems that may occur in
other VLANs. The following figure shows VLANs 10 and 20 configured on an EdgeIron and a
BigIron. Any STP activity caused by network problems that occur in VLAN 10 will never be
propagated in VLAN 20.
BigIron
EdgeIron
VLAN 10 (tagged)
VLAN 20 (tagged)
VLAN 10
(untagged)
VLAN 20
(untagged)
VLAN 20
(untagged)
VLAN 10
(untagged)
To display VLAN settings and configure a VLAN with an STP instance on the EdgeIron 24G-A, enter
the following commands:
Console#show vlan
VLAN Type
Name
Status
Ports/Channel groups
---- ------- -------- ---------- --------------------------------------1 Static
Active
Eth1/ 1 Eth1/ 4 Eth1/ 5 Eth1/ 6 Eth1/ 7
Eth1/ 8 Eth1/ 9 Eth1/10 Eth1/11 Eth1/12
Eth1/13 Eth1/14 Eth1/15 Eth1/16 Eth1/17
Eth1/18 Eth1/19 Eth1/20 Eth1/21 Eth1/22
Eth1/23 Eth1/24 Eth1/25 Eth1/26
2 Static
Active
Console#configure terminal
Console(config)#vlan 10
Console(config-vlan-10)#tagged ethernet 1/2
Console(config-vlan-10)#tagged ethernet 1/3
Console(config-vlan-10)#untag ethernet 1/4
Console(config-vlan-10)#exit
Console(config)#vlan 20
Console(config-vlan-20)#tagged ethernet 1/2
Console(config-vlan-20)#tagged ethernet 1/3
Console(config-vlan-20)#untag ethernet 1/5
The example above allows EdgeIron to have a distinct STP for VLAN 10 and one for VLAN 20.
Note: Make sure that only one VLAN is assigned to an STP instance on the EdgeIron, otherwise, it
will not work.
December 2007
© 2007 Foundry Networks, Inc.
21-3
Foundry EdgeIron User Guide
On the BigIron Layer 2 Switch, create VLANs with the same VLAN IDs as those on the EdgeIron
device as follows.
BigIron(config)#vlan 10
BigIron(config-vlan-10)#tagged ethernet 2/10
BigIron(config-vlan-10)#tagged ethernet 3/5
BigIron(config-vlan-10)#exit
BigIron(config)#vlan 20
BigIron(config-vlan-20)#tagged ethernet 2/10
BigIron(config-vlan-20)#untagged ethernet 3/8
BigIron(config-vlan-20)#exit
BigIron(config)#
STP Information
To display information on the current status of the spanning tree use the procedures that follow.
USING THE WEB INTERFACE
Note: The term STP has been substituted by the term STA in the web screen interface.
Click Spanning Tree, STP Information to display current spanning tree information.
21-4
•
Spanning Tree State – Indicates if the Spanning Tree Protocol is currently enabled on the switch.
•
Bridge ID – Identifies a unique identifier for the switch in the spanning tree. The ID is calculated
using the defined spanning tree priority of the switch and its MAC address. The lower the Bridge
ID, the more likely the switch will act as the root.
•
Max Age – The maximum time (in seconds) the switch can wait without receiving a configuration
message before attempting to reconfigure. All device ports (except for designated ports) should
receive configuration messages at regular intervals. If the root port ages out STP information
(provided in the last configuration message), a new root port is selected from among the device
ports attached to the network. (References to “ports” in this section means “interfaces,” which
includes both ports and trunks.)
•
Hello Time – Specifies the time interval (in seconds) at which the root device transmits a
configuration message.
© 2007 Foundry Networks, Inc.
March 2007
Spanning Tree Protocol
•
Forward Delay – The maximum time (in seconds) the switch will wait before changing states (i.e.,
discarding to learning to forwarding). This delay is required because every device must receive
information about topology changes before it starts to forward frames. In addition, each port
needs time to listen for conflicting information that would make it return to a discarding state;
otherwise, temporary data loops might result.
•
Designated Root – Identifies the priority and MAC address of the device in the spanning tree that
the switch has accepted as the root device.
•
Root Port – Specifies the port number on the switch that is closest to the root. The switch
communicates with the root device through this port. If there is no root port, the switch has been
accepted as the root device of the spanning tree network.
•
Root Path Cost – Identifies the path cost from the root port on the switch to the root device.
•
Configuration Changes – Specifies the number of times the spanning tree has been
reconfigured.
•
Last Topology Change – Identifies the time since the spanning tree was last reconfigured.
USING THE CLI
Use the command in this section to display the state of the spanning tree.
show spanning-tree
Use this command to show the configuration for the spanning tree or for an instance within the
multiple spanning tree (MSTI).
Syntax
show spanning-tree mst {configuration | instance_id interface}
• interface
• ethernet unit/port-number
- unit - This is device 1.
- port-number
• port-channel channel-id (Range: 1-6)
• instance_id - Instance identifier of the multiple spanning tree.
(Range: 1-4094, no leading zeroes)
Default Setting
None
Command Mode
Privileged Exec
Command Usage
• Use the show spanning-tree command with no parameters to display the spanning tree
configuration for the spanning tree and for every interface in the tree.
• Use the show spanning-tree interface command to display the spanning tree configuration for
an interface within the spanning tree.
•
Spanning Tree State – Indicates if the Spanning Tree Protocol is currently enabled on the switch.
December 2007
© 2007 Foundry Networks, Inc.
21-5
Foundry EdgeIron User Guide
•
Bridge ID – Identifies a unique identifier for the switch in the spanning tree. The ID is calculated
using the defined spanning tree priority of the switch and its MAC address. The lower the Bridge
ID, the more likely the switch will act as the root.
•
Max Age – The maximum time (in seconds) the switch can wait without receiving a configuration
message before attempting to reconfigure. All device ports (except for designated ports) should
receive configuration messages at regular intervals. If the root port ages out STP information
(provided in the last configuration message), a new root port is selected from among the device
ports attached to the network. (References to “ports” in this section means “interfaces,” which
includes both ports and trunks.)
•
Hello Time – Specifies the time interval (in seconds) at which the root device transmits a
configuration message.
•
Forward Delay – The maximum time (in seconds) the switch will wait before changing states (i.e.,
discarding to learning to forwarding). This delay is required because every device must receive
information about topology changes before it starts to forward frames. In addition, each port
needs time to listen for conflicting information that would make it return to a discarding state;
otherwise, temporary data loops might result.
•
Designated Root – Identifies the priority and MAC address of the device in the spanning tree that
the switch has accepted as the root device.
•
Root Port – Specifies the port number on the switch that is closest to the root. The switch
communicates with the root device through this port. If there is no root port, the switch has been
accepted as the root device of the spanning tree network.
•
Root Path Cost – Identifies the path cost from the root port on the switch to the root device.
•
Configuration Changes – Specifies the number of times the spanning tree has been
reconfigured.
•
Last Topology Change – Identifies the time since the spanning tree was last reconfigured.
• Use the show spanning-tree mst instance_id command to display the spanning tree
configuration for an instance within the Multiple Spanning Tree (MST).
21-6
© 2007 Foundry Networks, Inc.
March 2007
Spanning Tree Protocol
Example
Console#show spanning-tree mst 1
Spanning-tree information
--------------------------------------------------------------Spanning tree mode
:RSTP
Spanning tree enable/disable
:enable
Instance
:1
Vlans configuration
:1
Priority
:32768
Bridge Hello Time (sec.)
:2
Bridge Max Age (sec.)
:20
Bridge Forward Delay (sec.)
:15
Root Hello Time (sec.)
:2
Root Max Age (sec.)
:20
Root Forward Delay (sec.)
:15
Max hops
:20
Remaining hops
:20
Designated Root:
32768.1.000480BD474D
Current root port
:0
Current root cost
:0
Number of topology changes
:1
Last topology changes time (sec.):1127
Transmission limit
:3
Path Cost Method
:long
--------------------------------------------------------------Eth 1/ 1 information
--------------------------------------------------------------Admin status
: enable
Role
: designate
State
: forwarding
External path cost
: 100000
Internal path cost
: 100000
Priority
: 128
Designated cost
: 0
Designated port
: 128.1
Designated root:
32768.1.000480BD474D
Designated bridge:
32768.1.000480BD474D
Fast forwarding
: disable
Forward transitions : 1
Admin edge port
: disable
Oper edge port
: disable
Admin Link type
: auto
Oper Link type
: point-to-point
Spanning Tree Status : enable
.
.
.
Console#
STP Configuration
Global settings apply to the entire switch.
Command Usage
The Rapid Spanning Tree Protocol (RSTP) supports connections to either STP or RSTP nodes by
monitoring the incoming protocol messages and dynamically adjusting the type of protocol
messages the RSTP node transmits, as described below:
•
STP Mode – If the switch receives an 802.1D BPDU (i.e., STP BPDU) after a port’s migration
delay timer expires, the switch assumes it is connected to an 802.1D bridge and starts using only
802.1D BPDUs.
•
RSTP Mode – If RSTP is using 802.1D BPDUs on a port and receives an RSTP BPDU after the
migration delay expires, RSTP restarts the migration delay timer and begins using RSTP BPDUs
on that port.
December 2007
© 2007 Foundry Networks, Inc.
21-7
Foundry EdgeIron User Guide
USING THE WEB INTERFACE
Click Spanning Tree, STP Configuration. Modify the required attributes, then click Apply.
21-8
•
Bridge ID – A unique identifier for this bridge, consisting of the bridge priority and MAC address
(where the address is taken from the switch system).
•
Spanning Tree State – Enables or disables the spanning tree. If you enable the spanning tree,
you must complete the other fields.
(Default: enabled)
•
Spanning Tree Type – Specifies the type of Spanning Tree Protocol used on the switch:
(Default: RSTP)
-
STP: (IEEE 802.1D; i.e., when this option is selected, the switch will use RSTP set to STP
forced-compatibility mode).
-
RSTP: Rapid Spanning Tree Protocol (IEEE 802.1w)
© 2007 Foundry Networks, Inc.
March 2007
Spanning Tree Protocol
Note: A Spanning Tree instance can exist only on bridges that have compatible VLAN instance
assignments.
Note: Be careful when switching between Spanning Tree modes. Changing modes stops all
Spanning Tree instances for the previous mode and restarts the system in the new mode,
temporarily disrupting user traffic.
•
Priority – Bridge priority is used in selecting the root device, root port, and designated port. The
device with the highest priority becomes the STP root device. However, if all devices have the
same priority, the device with the lowest MAC address will then become the root device.
- Default: 32768
- Range: 0-61440, in steps of 4096
- Options: 0, 4096, 8192, 12288, 16384, 20480, 24576, 28672, 32768, 36864, 40960, 45056,
49152, 53248, 57344, 61440
•
Hello Time – Interval (in seconds) at which the switch transmits a configuration message.
- Default: 2
- Minimum: 1
- Maximum: The lower of 10 or [(Max. Message Age / 2) -1]
•
Maximum Age – The maximum time (in seconds) the switch can wait without receiving a
configuration message before attempting to reconfigure. All device ports (except for designated
ports) should receive configuration messages at regular intervals. Any port that ages out STP
information (provided in the last configuration message) becomes the designated port for the
attached LAN. If it is a root port, a new root port is selected from among the device ports attached
to the network. (References to “ports” in this section means “interfaces,” which includes both ports
and trunks.)
- Default: 20
- Minimum: The higher of 6 or [2 x (Hello Time + 1)].
- Maximum: The lower of 40 or [2 x (Forward Delay - 1)]
•
Forward Delay – The maximum time (in seconds) the switch will wait before changing states (i.e.,
discarding to learning to forwarding). This delay is required because every device must receive
information about topology changes before it starts to forward frames. In addition, each port
needs time to listen for conflicting information that would make it return to a discarding state;
otherwise, temporary data loops might result.
- Default: 15
- Minimum: The higher of 4 or [(Max. Message Age / 2) + 1]
- Maximum: 30
•
Path Cost Method – The path cost is used to determine the best path between devices. The path
cost method is used to determine the range of values that can be assigned to each interface.
- Long: Specifies 32-bit based values that range from 1-200,000,000.
- Short: Specifies 16-bit based values that range from 1-65535. (This is the default.)
December 2007
© 2007 Foundry Networks, Inc.
21-9
Foundry EdgeIron User Guide
•
Transmission Limit – The maximum transmission rate for BPDUs is specified by setting the
minimum interval between the transmission of consecutive protocol messages. (Range: 1-10;
Default: 3)
•
Max Hop Counts — The maximum number of hops allowed in this MSTI region before a BPDU
is discarded. (Range: 1-40; Default: 20)
USING THE CLI
Use the commands in this section to configure spanning tree.
spanning-tree (Global Configuration)
Use this command to enable the Spanning Tree Protocol globally for this switch. Use the no form to
disable it.
Note: Spanning tree can be disabled on a per VLAN basis or per port basis beginning with release
2.2.4.27 as described in “spanning-tree (VLAN Configuration)” on page 21-11 and “spanning-tree
spanning-disabled” on page 21-14.
Syntax
spanning-tree
no spanning-tree
Default Setting
Spanning tree is enabled.
Command Mode
Global Configuration
Command Usage
The Spanning Tree Protocol can be used to detect and disable network loops, and to provide
backup links between switches, bridges or routers. This allows the switch to interact with other
bridging devices (that is, an STP-compliant switch, bridge or router) in your network to ensure
that only one route exists between any two stations on the network, and provide backup links
which automatically take over when a primary link goes down.
Example
The following example enables the Spanning Tree Protocol for this switch:
Console(config)#spanning-tree
Console(config)#
21-10
© 2007 Foundry Networks, Inc.
March 2007
Spanning Tree Protocol
spanning-tree (VLAN Configuration)
Use this command to enable spanning-tree per VLAN. Use the no form to disable it.
Note: Spanning tree can be disabled on a per VLAN or per port basis starting with release 2.2.4.27.
Syntax
spanning-tree
[no] spanning-tree
Default Setting
Spanning tree is enabled.
Command Mode
VLAN Configuration
Example
The following example disables spanning-tree for VLAN 123.:
Console(config)#vlan 123
Console(Config-vlan-123)#no spanning-tree
Console(Config-vlan-123)#
spanning-tree forward-time
Use this command to configure the Spanning Tree bridge forward time globally for this switch. Use
the no form to restore the default.
Syntax
spanning-tree forward-time seconds
no spanning-tree forward-time
seconds - Time in seconds. (Range: 4-30 seconds)
The minimum value is the higher of 4 or [(max-age / 2) + 1].
Default Setting
15 seconds
Command Mode
Global Configuration
Command Usage
This command sets the maximum time (in seconds) the root device will wait before changing
states (i.e., discarding to learning to forwarding). This delay is required because every device
must receive information about topology changes before it starts to forward frames. In addition,
each port needs time to listen for conflicting information that would make it return to a discarding
state; otherwise, temporary data loops might result.
Example
Console(config)#spanning-tree forward-time 20
Console(config)#
December 2007
© 2007 Foundry Networks, Inc.
21-11
Foundry EdgeIron User Guide
spanning-tree hello-time
Use this command to configure the spanning tree bridge hello time globally for this switch. Use the
no form to restore the default.
Syntax
spanning-tree hello-time time
no spanning-tree hello-time
time - Time in seconds. (Range: 1-10 seconds)
The maximum value is the lower of 10 or [(max-age / 2) -1].
Default Setting
2 seconds
Command Mode
Global Configuration
Command Usage
This command sets the time interval (in seconds) at which the root device transmits a
configuration message.
Example
Console(config)#spanning-tree hello-time 5
Console(config)#
spanning-tree max-age
Use this command to configure the spanning tree bridge maximum age globally for this switch. Use
the no form to restore the default.
Syntax
spanning-tree max-age seconds
no spanning-tree max-age
seconds - Time in seconds. (Range: 6-40 seconds)
The minimum value is the higher of 6 or [2 x (hello-time + 1)].
The maximum value is the lower of 40 or [2 x (forward-time - 1)].
Default Setting
20 seconds
Command Mode
Global Configuration
Command Usage
This command sets the maximum time (in seconds) a device can wait without receiving a
configuration message before attempting to reconfigure. All device ports (except for designated
ports) should receive configuration messages at regular intervals. Any port that ages out STP
information (provided in the last configuration message) becomes the designated port for the
attached LAN. If it is a root port, a new root port is selected from among the device ports
attached to the network.
21-12
© 2007 Foundry Networks, Inc.
March 2007
Spanning Tree Protocol
Example
Console(config)#spanning-tree max-age 40
Console(config)#
spanning-tree priority
Use this command to configure the spanning tree priority globally for this switch. Use the no form to
restore the default.
Syntax
spanning-tree priority priority
no spanning-tree priority
priority - Priority of the bridge.
(Range – 0-61440, in steps of 4096; Options: 0, 4096, 8192, 12288, 16384, 20480, 24576,
28672, 32768, 36864, 40960, 45056, 49152, 53248, 57344, 61440)
Default Setting
32768
Command Mode
Global Configuration
Command Usage
Bridge priority is used in selecting the root device, root port, and designated port. The device with
the highest priority becomes the STP root device. However, if all devices have the same priority,
the device with the lowest MAC address will then become the root device.
Example
Console(config)#spanning-tree priority 40000
Console(config)#
spanning-tree pathcost method
Use this command to configure the path cost method used for the Rapid Spanning Tree and Multiple
Spanning Tree. Use the no form to restore the default.
Syntax
spanning-tree pathcost method {long | short}
no spanning-tree pathcost method
• long - Specifies 32-bit based values that range from 1-200,000,000.
• short - Specifies 16-bit based values that range from 1-65535.
Default Setting
short method
Command Mode
Global Configuration
December 2007
© 2007 Foundry Networks, Inc.
21-13
Foundry EdgeIron User Guide
Command Usage
The path cost method is used to determine the best path between devices. Therefore, lower
values should be assigned to ports attached to faster media, and higher values assigned to ports
with slower media. Note that path cost (see “spanning-tree pathcost method” on page 21-13)
takes precedence over port priority (see “Mapping IP Port Priority” on page 25-17).
Example
Console(config)#spanning-tree pathcost method long
Console(config)#
spanning-tree transmission-limit
Use this command to configure the minimum interval between the transmission of consecutive RSTP
BPDUs. Use the no form to restore the default.
Syntax
spanning-tree transmission-limit count
no spanning-tree transmission-limit
count - The transmission limit in seconds. (Range: 1-10)
Default Setting
3
Command Mode
Global Configuration
Command Usage
This command limit the maximum transmission rate for BPDUs.
Example
Console(config)#spanning-tree transmission-limit 4
Console(config)#
spanning-tree spanning-disabled
This command disables the spanning tree algorithm for the specified interface. Use the no form
to reenable the spanning tree algorithm for the specified interface.
Syntax
[no] spanning-tree spanning-disabled
Default Setting
Enabled
Command Mode
Interface Configuration (Ethernet, Port Channel)
21-14
© 2007 Foundry Networks, Inc.
March 2007
Spanning Tree Protocol
Example
This example disables the spanning tree algorithm for port 5.
Console(config)#interface ethernet 1/5
Console(config-if)#spanning-tree spanning-disabled
Console(config-if)#
spanning-tree single
This command enables a single spanning tree mode and disables PVST. Use the no form to disable the single
spannig tree mode.
Syntax
spanning-tree single {802-1D | 802-1w}
no spanning-tree single
• 802-1D - Specifies a spanning tree that is IEEE 802.1D compliant.
• 802-1w - Specifies a spanning tree that is IEEE 802.1w compliant.
Default Setting
Disabled
Command Mode
Global Configuration
Command Usage
Spanning tree is enabled in PVST mode by factory default. When single spanning tree is enabled, it
automatically turns off PVST. The single spanning tree runs on MST instance 1, with which all VLANs are
associated. The "show spanning-tree mst 1" command can be used to display details.
Example
Console(config)#spanning-tree single 802-1w
Console(config)#
STP Port and Trunk Information
The Spanning Tree/STP Port Information and STP Trunk Information display the current status of
ports and trunks in the spanning tree.
USING THE WEB INTERFACE
Click Spanning Tree, STP Port Information or STP Trunk Information.
December 2007
© 2007 Foundry Networks, Inc.
21-15
Foundry EdgeIron User Guide
•
STP Status – Displays current state of this port within the spanning tree:
- Discarding – Port receives STP configuration messages, but does not forward packets.
- Learning – Port has transmitted configuration messages for an interval set by the Forward
Delay parameter without receiving contradictory information. Port address table is cleared, and
the port begins learning addresses.
- Forwarding – Port forwards packets, and continues learning addresses.
The rules defining port status are:
- A port on a network segment with no other STP-compliant bridging device is always forwarding.
- If two ports on a switch are connected to the same segment and there is no other STP device
attached to this segment, the port with the smaller ID forwards packets and the other is
discarding.
- All ports are discarding when the switch is booted, then some of them change state to learning,
and then to forwarding.
•
Forward Transitions – The number of times this port has transitioned from the Learning state to
the Forwarding state.
•
Designated Cost – The cost for a packet to travel from this port to the root in the current spanning
tree configuration. The slower the media, the higher the cost.
•
Designated Bridge – The priority and MAC address of the device through which this port must
communicate to reach the root of the spanning tree.
•
Designated Port – The priority and number of the port on the designated bridging device through
which this switch must communicate with the root of the spanning tree.
•
Oper Link Type – The operational point-to-point status of the LAN segment attached to this
interface. This parameter is determined by manual configuration or by auto-detection, as
described for “Admin Link Type” in the STP Port/Trunk Configuration page.
•
Oper Edge Port – This parameter is initialized to the setting for “Admin Edge Port” in the STP
Port/Trunk Configuration page (i.e., true or false), but will be set to false if a BPDU is received,
indicating that another bridge is attached to this port.
•
Port Role – Roles are assigned according to whether the port is part of the active spanning tree
topology:
- Root: The port is connecting the bridge to the root bridge.
- Designated: The port is connecting a LAN through the bridge to the root bridge.
- Alternate or Backup: A port that may provide connectivity if other bridges, bridge ports, or
LANs fail or are removed.
- Disabled: The role is set to disabled if a port has no role within the spanning tree.
•
Trunk Member – Indicates whether the port is configured as a trunk member. (STP Port
Information page only.)
USING THE CLI
Use the show spanning-tree command to display spanning tree settings by port.
These additional parameters are only displayed in the CLI:
21-16
© 2007 Foundry Networks, Inc.
March 2007
Spanning Tree Protocol
•
Admin status – Shows if STP has been enabled on this interface.
•
Path Cost – This parameter is used by the STP to determine the best path between devices.
Therefore, lower values should be assigned to ports attached to faster media, and higher values
assigned to ports with slower media. (Path cost takes precedence over port priority.)
•
Priority – Defines the priority used for this port in the spanning tree. If the path cost for all ports
on a switch is the same, the port with the highest priority (i.e., lowest value) will be configured as
an active link in the spanning tree. This makes a port with higher priority less likely to be blocked
if the Spanning Tree Protocol is detecting network loops. Where more than one port is assigned
the highest priority, the port with the lowest numeric identifier will be enabled.
•
Designated root – The priority and MAC address of the device in the spanning tree that this
switch has accepted as the root device.
•
Fast forwarding – This field provides the same information as Admin Edge port, and is only
included for backward compatibility with earlier products.
•
Admin Link Type – The link type attached to this interface.
- Point-to-Point – A connection to exactly one other bridge.
- Shared – A connection to two or more bridges.
- Auto – The switch automatically determines if the interface is attached to a point-to-point link
or to shared media.
•
Admin Edge Port – You can enable this option if an interface is attached to a LAN segment that
is at the end of a bridged LAN or to an end node. Since end nodes cannot cause forwarding loops,
they can pass directly through to the spanning tree forwarding state. Specifying Edge Ports
provides quicker convergence for devices such as workstations or servers, retains the current
forwarding database to reduce the amount of frame flooding required to rebuild address tables
during reconfiguration events, does not cause the spanning tree to reconfigure when the interface
changes state, and also overcomes other STP-related timeout problems. However, remember
that Edge Port should only be enabled for ports connected to an end-node device.
STP Port and Trunk Configuration
You can configure RSTP attributes for specific interfaces, including port priority, path cost, link type,
and edge port. You may use a different priority or path cost for ports of same media type to indicate
the preferred path, link type to indicate a point-to-point connection or shared-media connection, and
edge port to indicate if the attached device can support fast forwarding. (References to “ports” in this
section means “interfaces,” which includes both ports and trunks.)
December 2007
© 2007 Foundry Networks, Inc.
21-17
Foundry EdgeIron User Guide
USING THE WEB INTERFACE
Click Spanning Tree, STP Port Configuration or STP Trunk Configuration. Modify the required
attributes, then click Apply.
•
Port — Specifies a port.
•
Spanning Tree — Check to enable spanning tree on a port.
•
STA State – Displays current state of this port within the spanning tree:
- Discarding – Port receives STP configuration messages, but does not forward packets.
- Learning – Port has transmitted configuration messages for an interval set by the Forward
Delay parameter without receiving contradictory information. Port address table is cleared, and
the port begins learning addresses.
- Forwarding – Port forwards packets, and continues learning addresses.
•
Priority – Defines the priority used for this port in the Spanning Tree Protocol. If the path cost for
all ports on a switch is the same, the port with the highest priority (i.e., lowest value) will be
configured as an active link in the spanning tree. This makes a port with higher priority less likely
to be blocked if the Spanning Tree Protocol is detecting network loops. Where more than one port
is assigned the highest priority, the port with lowest numeric identifier will be enabled.
(Default: 128; Range: 0-240, in steps of 16)
•
Path Cost – This parameter is used by the STP to determine the best path between devices.
Therefore, lower values should be assigned to ports attached to faster media, and higher values
assigned to ports with slower media. (Path cost takes precedence over port priority.)
- Range –
Ethernet: 200,000-20,000,000
Fast Ethernet: 20,000-2,000,000
Gigabit Ethernet: 2,000-200,000
- Defaults –
Ethernet – half duplex: 2,000,000; full duplex: 1,000,000; trunk: 500,000
Fast Ethernet – half duplex: 200,000; full duplex: 100,000; trunk: 50,000
Gigabit Ethernet – full duplex: 10,000; trunk: 5,000
Note: When the Path Cost Method is set to short, the maximum path cost is 65,535.
•
Admin Link Type – The link type attached to this interface. (Default: Auto)
- Point-to-Point – A connection to exactly one other bridge.
21-18
© 2007 Foundry Networks, Inc.
March 2007
Spanning Tree Protocol
- Shared – A connection to two or more bridges.
- Auto – The switch automatically determines if the interface is attached to a point-to-point link
or to shared media.
•
Admin Edge Port – You can enable this option if an interface is attached to a LAN segment that
is at the end of a bridged LAN or to an end node. Since end nodes cannot cause forwarding loops,
they can pass directly through to the spanning tree forwarding state. Specifying Edge Ports
provides quicker convergence for devices such as workstations or servers, retains the current
forwarding database to reduce the amount of frame flooding required to rebuild address tables
during reconfiguration events, does not cause the spanning tree to initiate reconfiguration when
the interface changes state, and also overcomes other STP-related timeout problems. However,
remember that Edge Port should only be enabled for ports connected to an end-node device.
•
Migration – Re-checks the appropriate BPDU format to send on the selected interface. If at any
time the switch detects STP BPDUs, including Configuration or Topology Change Notification
BPDUs, it will automatically set the selected interface to forced STP-compatible mode. However,
you can also check this Migration check box to manually re-check the appropriate BPDU format
(RSTP or STP-compatible) to send on the selected interfaces.
•
Trunk – Specifies if a port is member of a trunk.
USING THE CLI
Use the commands described in the “STP Configuration” on page 21-7 to configure spanning tree on
a per port basis.
December 2007
© 2007 Foundry Networks, Inc.
21-19
Foundry EdgeIron User Guide
21-20
© 2007 Foundry Networks, Inc.
March 2007
Chapter 22
802.1Q VLANs
Note: Foundry PVST is supported in all EdgeIron switches starting from version 2.2.4.x.
Note: Foundry PVRST is supported in all EdgeIron switches starting from version 2.2.6.23.
In conventional networks with routers, broadcast traffic is split up into separate domains. Switches
do not inherently support broadcast domains. This can lead to broadcast storms in large networks
that handle traffic such as IPX or NetBEUI. By using IEEE 802.1Q-compliant VLANs, you can
organize any group of network nodes into separate broadcast domains, thus confining broadcast
traffic to the originating group. This also provides a more secure and cleaner network environment.
An IEEE 802.1Q VLAN is a group of ports that can be located anywhere in the network, but
communicate as though they belong to the same physical segment.
VLANs help to simplify network management by allowing you to move devices to a new VLAN
without having to change any physical connections. VLANs can be easily organized to reflect
departmental groups (such as Marketing or R&D), usage groups (such as e-mail), or multicast
groups (used for multimedia applications such as videoconferencing).
VLANs provide greater network efficiency by reducing broadcast traffic, and allow you to make
network changes without having to update IP addresses or IP subnets. VLANs inherently provide a
high level of network security since traffic must pass through a configured Layer 3 link to reach a
different VLAN.
•
Up to 255 VLANs based on the IEEE 802.1Q standard
(PVST can service up to 32 VLANs; PVST for all other VLANs will be disabled.)
•
Distributed VLAN learning across multiple switches using explicit or implicit tagging and GVRP
protocol
•
Port overlapping, allowing a port to participate in multiple VLANs
•
End stations can belong to multiple VLANs
•
Passing traffic between VLAN-aware and VLAN-unaware devices
•
Priority tagging
December 2007
© 2007 Foundry Networks, Inc.
22-1
Foundry EdgeIron User Guide
The CLI commands for this section are briefly described in the table that follows:
Command
Function
Mode
Page
bridge-ext gvrp
Enables GVRP globally for the switch
GC
22-4
show bridge-ext
Shows bridge extension configuration
PE
22-6
vlan
Configures a VLAN, including VID, name and state
GC
22-10
untagged ethernet
Assign a port as an untagged member of a port-based
VLAN
VC
22-14
tagged ethernet
Assigns a port as a tagged member of a port-based
VLAN
VC
22-13
dual-mode
Configures a tagged port to transmit and receive both
tagged and untagged frames
IC
22-14
interface vlan
Enters interface configuration mode for specified VLAN
IC
22-16
switchport mode
Configures VLAN membership mode for an interface
IC
22-16
switchport acceptable-frametypes
Configures frame types to be accepted by an interface IC
22-19
swicthport ingress-filtering
Enables ingress filtering on an interface
IC
22-20
switchport gvrp
Enables GVRP for an interface
IC
22-5
switchport forbidden vlan
Configures forbidden VLANs for an interface
IC
22-21
show vlan
Shows VLAN information
NE, PE
22-8
show interfaces status vlan
Displays status for the specified VLAN interface
NE, PE
22-22
show interfaces switchport
Displays the administrative and operational status of an
interface
NE, PE
22-23
Edit VLAN Groups
Configure VLAN Interfaces
Display VLAN Information
Assigning Ports to VLANs
Before enabling VLANs for the switch, you must first assign each port to the VLAN group(s) in which
it will participate. By default all ports are assigned to VLAN 1 as untagged ports. Add a port as a
tagged port if you want it to carry traffic for one or more VLANs, and any intermediate network
devices or the host at the other end of the connection supports VLANs. Then assign ports on the
other VLAN-aware network devices along the path that will carry this traffic to the same VLAN(s),
either manually or dynamically using GVRP. However, if you want a port on this switch to participate
in one or more VLANs, but none of the intermediate network devices nor the host at the other end of
the connection supports VLANs, then you should add this port to the VLAN as an untagged port.
22-2
© 2007 Foundry Networks, Inc.
March 2007
802.1Q VLANs
Note: VLAN-tagged frames can pass through VLAN-aware or VLAN-unaware network
interconnection devices, but the VLAN tags should be stripped off before passing it on to any endnode host that does not support VLAN tagging.
VLAN Classification – When the switch receives a frame, it classifies the frame in one of two ways.
If the frame is untagged, the switch assigns the frame to an associated VLAN (based on the PVID of
the receiving port. But if the frame is tagged, the switch uses the tagged VLAN ID to identify the port
broadcast domain of the frame.
Port Overlapping – Port overlapping can be used to allow access to commonly shared network
resources among different VLAN groups, such as file servers or printers. Note that if you implement
VLANs which do not overlap, but still need to communicate, you can connect them by using a Layer3 router or switch.
Untagged VLANs – Untagged (or static) VLANs are typically used to reduce broadcast traffic and to
increase security. A group of network users assigned to a VLAN form a broadcast domain that is
separate from other VLANs configured on the switch. Packets are forwarded only between ports that
are designated for the same VLAN. Untagged VLANs can be used to manually isolate user groups
or subnets. However, you should use IEEE 802.3 tagged VLANs with GVRP whenever possible to
fully automate VLAN registration.
Automatic VLAN Registration – GVRP (GARP VLAN Registration Protocol) defines a system
whereby the switch can automatically learn the VLANs to which each endstation should be assigned.
If an endstation (or its network adapter) supports the IEEE 802.1Q VLAN protocol, it can be
configured to broadcast a message to your network indicating the VLAN groups it wants to join.
When this switch receives these messages, it will automatically place the receiving port in the
specified VLANs, and then forward the message to all other ports. When the message arrives at
another switch that supports GVRP, it will also place the receiving port in the specified VLANs, and
pass the message on to all other ports. VLAN requirements are propagated in this way throughout
the network. This allows GVRP-compliant devices to be automatically configured for VLAN groups
based solely on endstation requests.
To implement GVRP in a network, first add the host devices to the required VLANs (using the
operating system or other application software), so that these VLANs can be propagated onto the
network. For both the edge switches attached directly to these hosts, and core switches in the
network, enable GVRP on the links between these devices. You should also determine security
boundaries in the network and disable GVRP on ports to prevent advertisements being propagated,
or forbid ports from joining restricted VLANs.
If you have host devices that do not support GVRP, you must configure static VLANs for the switch
ports connected to these devices. You also still need to enable GVRP on these edge switches, as
well as on the core switches in the network.
December 2007
© 2007 Foundry Networks, Inc.
22-3
Foundry EdgeIron User Guide
Forwarding Tagged/Untagged Frames
If you want to create a small port-based VLAN for devices attached directly to a single switch, you
can assign ports to the same untagged VLAN. However, to participate in a VLAN group that crosses
several switches, you need to create a VLAN for that group and enable tagging on all ports.
Ports can be assigned to multiple tagged or untagged VLANs. Each port on the switch is therefore
capable of passing tagged or untagged frames. When forwarding a frame from the switch along a
path that contains any VLAN-aware devices, the switch should include VLAN tags. When forwarding
a frame from the switch along a path that does not contain any VLAN-aware devices (including the
destination host), the switch must first strip off the VLAN tag before forwarding the frame. When the
switch receives a tagged frame, it will pass this frame onto the VLAN(s) indicated by the frame tag.
However, when the switch receives an untagged frame from a VLAN-unaware device, it first decides
where to forward the frame, and then inserts a VLAN tag reflecting the ingress port’s default VID.
Enabling or Disabling GVRP (Global Setting)
GARP VLAN Registration Protocol (GVRP) defines a way for switches to exchange VLAN
information in order to register VLAN members on ports across the network. VLANs are dynamically
configured based on join messages issued by host devices and propagated throughout the network.
GVRP must be enabled to permit automatic VLAN registration, and to support VLANs which extend
beyond the local switch. (Default: Disabled)
USING THE WEB INTERFACE
Click VLAN, 802.1Q VLAN, GVRP Status. Enable or disable GVRP, and click Apply.
USING THE CLI
bridge-ext gvrp
Use this command to enable GVRP. Use the no form to disable it.
Syntax
bridge-ext gvrp
no bridge-ext gvrp
Default Setting
Disabled
Command Mode
Global Configuration
22-4
© 2007 Foundry Networks, Inc.
March 2007
802.1Q VLANs
Command Usage
GVRP defines a way for switches to exchange VLAN information in order to register VLAN
members on ports across the network. This function should be enabled to permit automatic
VLAN registration, and to support VLANs which extend beyond the local switch.
Example
Console(config)#bridge-ext gvrp
Console(config)#
switchport gvrp
Use this command to enable GVRP for a port. Use the no form to disable it.
Syntax
switchport gvrp
no switchport gvrp
Default Setting
Disabled
Command Mode
Interface Configuration (Ethernet, Port Channel)
Example
Console(config)#interface ethernet 1/1
Console(config-if)#switchport gvrp
Console(config-if)#
Displaying Basic VLAN Information
USING THE WEB INTERFACE
Click VLAN, 802.1Q VLAN, Basic Information.
•
VLAN Version Number – The VLAN version used by this switch as specified in the IEEE 802.1Q
standard. (Web interface only.)
•
Maximum VLAN ID – Maximum VLAN ID recognized by this switch.
•
Maximum Number of Supported VLANs – Maximum number of VLANs that can be configured
on this switch.
December 2007
© 2007 Foundry Networks, Inc.
22-5
Foundry EdgeIron User Guide
USING THE CLI
Enter the following command.
show bridge-ext
Use this command to show the configuration for bridge extension commands.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
See “Displaying Basic VLAN Information” on page 22-5 and “Assigning Ports to VLANs” on page
22-2 for a description of the displayed items.
Example
Console#show bridge-ext
Max support vlan numbers: 255
Max support vlan ID: 4094
Extended multicast filtering services: No
Static entry individual port: Yes
VLAN learning: IVL
Configurable PVID tagging: Yes
Local VLAN capable: No
Traffic classes: Enabled
Global GVRP status: Disabled
GMRP: Disabled
Console#
Displaying Current VLANs
The VLAN Current Table shows the current port members of each VLAN and whether or not the port
supports VLAN tagging. Ports assigned to a large VLAN group that crosses several switches should
use VLAN tagging. However, if you just want to create a small port-based VLAN for one or two
switches, you can disable tagging.
Note: The maximum length of a VLAN name is 32 characters (the same as RFC2674 MIB
definition). When a VLAN name is set through the ifAlias object (RFC2863 MIB), up to 64 characters
can be used, but the name is always truncated to 32 characters, because both refer to the same
database. The maximum lengths for all other names (such as ports and trunks) are 64 characters.
22-6
© 2007 Foundry Networks, Inc.
March 2007
802.1Q VLANs
USING THE WEB INTERFACE
Click VLAN, 802.1Q VLAN, Current Table. Select any ID from the scroll-down list.
•
VLAN ID – ID of configured VLAN (1-4094, no leading zeroes).
•
Up Time at Creation – Time this VLAN was created; i.e., System Up Time.
•
Status – Shows how this VLAN was added to the switch.
- Dynamic GVRP: Automatically learned via GVRP.
- Permanent: Added as a static entry.
•
Tagged Ports – Shows the tagged VLAN port members.
•
Untagged Ports – Shows the untagged VLAN port members
December 2007
© 2007 Foundry Networks, Inc.
22-7
Foundry EdgeIron User Guide
USING THE CLI
Enter the following command.
show vlan
Use this command to show VLAN information.
Syntax
show vlan [id vlan-id | name vlan-name]
• id - Keyword to be followed by the VLAN ID.
- vlan-id - ID of the configured VLAN. (Range: 1-4094, no leading zeroes)
• name - Keyword to be followed by the VLAN name.
- vlan-name - ASCII string from 1 to 32 characters.
Default Setting
Shows all VLANs.
Command Mode
Normal Exec, Privileged Exec
Command Attributes
•
VLAN – ID of configured VLAN (1-4094, no leading zeroes).
•
Type – Shows how this VLAN was added to the switch.
- Dynamic: Automatically learned via GVRP.
- Static: Added as a static entry.
•
Name – Name of the VLAN (1 to 32 characters).
•
Status – Shows if this VLAN is enabled or disabled.
- Active: VLAN is operational.
- Suspend: VLAN is suspended; i.e., does not pass packets.
•
Ports / Channel groups – Shows the VLAN interface members.
Example
The following example shows how to display information for VLAN 33:
Console#show vlan id 1
VLAN Type
Name
Status
Ports/Channel groups
---- ------- ---------------- --------- ------------------------------------33 Static Blue
Active Eth1/ 2 Eth1/ 3 Eth1/ 6 Eth1/ 7
Eth1/ 9 Eth1/ 10 Eth1/ 11 Eth1/ 12
Console#
22-8
© 2007 Foundry Networks, Inc.
March 2007
802.1Q VLANs
Creating VLANs
Use the VLAN Static List to create or remove VLAN groups. To propagate information about VLAN
groups used on this switch to external network devices, you must specify a VLAN ID for each of
these groups.
USING THE WEB INTERFACE
Click VLAN, 802.1Q VLAN, Static List. Enter the VLAN ID and VLAN name, mark the Enable
checkbox to activate the VLAN, and then click Add.
•
Current – Lists all the current VLAN groups created for this system. Up to 255 VLAN groups can
be defined. VLAN 1 is the default untagged VLAN.
•
New – Allows you to specify the name and numeric identifier for a new VLAN group. (The VLAN
name is only used for management on this system; it is not added to the VLAN tag.)
•
VLAN ID – ID of configured VLAN (1-4094, no leading zeroes).
•
Name – Name of the VLAN (1 to 32 characters).
•
Status – Shows if this VLAN is enabled or disabled (Web).
- Enable: VLAN is operational.
- Disable: VLAN is suspended; i.e., does not pass packets.
•
State – Shows if this VLAN is enabled or disabled (CLI).
- Active: VLAN is operational.
- Suspend: VLAN is suspended; i.e., does not pass packets.
•
Add – Adds a new VLAN group to the current list.
•
Remove – Removes a VLAN group from the current list. If any port is assigned to this group as
untagged, it will be reassigned to VLAN group 1 as untagged.
Note: The maximum length of a VLAN name is 32 characters (the same as RFC2674 MIB
definition). When a VLAN name is set through the ifAlias object (RFC2863 MIB), up to 64 characters
can be used, but the name is always truncated to 32 characters, because both refer to the same
database. The maximum lengths for all other names (such as ports and trunks) are 64 characters.
December 2007
© 2007 Foundry Networks, Inc.
22-9
Foundry EdgeIron User Guide
USING THE CLI
Enter the following commands.
vlan
Use this command to create VLANs and enter VLAN configuration mode. Use the no form to delete
a VLAN.
Note: This command is available on devices running release 2.2.4.11 and later.
Syntax
vlan vlan-id [by port | name vlan-name]
no vlan vlan-id
• vlan-id - ID of configured VLAN. (Range: 1-4094, no leading zeroes)
• by port - Forces the VLAN to be port based.
• name - Keyword to be followed by the VLAN name.
• vlan-name - ASCII string from 1 to 16 characters.
Note: The maximum length of a VLAN name is 16 characters (the same as RFC2674 MIB
definition). When a VLAN name is set through the ifAlias object (RFC2863 MIB), up to 64 characters
can be used, but the name is always truncated to 16 characters, because both refer to the same
database. The maximum lengths for all other names (such as ports and trunks) are 64 characters.
Default Setting
By default only VLAN 1 exists and is active.
Command Mode
Global Configuration
Command Usage
• Use the VLAN command mode to add, change and delete VLANs. After finishing configuration
changes, you can display the VLAN settings by entering the show vlan command.
• When no vlan vlan-id is used, the VLAN is deleted.
• You can configure up to 255 VLANs on the switch.
Example
The following example adds a VLAN, using vlan-id 105 and name RD5. The VLAN is activated by
default.
Console(config)#vlan 105 name RD5
Console(config-vlan-105)#
Related Commands
show vlan (22-8)
Note: The default VLAN can be changed beginning with release 2.2.4.26. For information on
changing the default VLAN, see “Creating a New Default VLAN” on page 22-11.
22-10
© 2007 Foundry Networks, Inc.
March 2007
802.1Q VLANs
Creating a New Default VLAN
In release 2.2.4.26 and later, you can create a new default VLAN using the following procedure:
1. Create a new VLAN and assign ports to it.
For the time being, leave one port in the default VLAN.
2. Assign an IP address to the new VLAN.
3. Now move the remaining port of the original default VLAN into the new default VLAN.
Example
The following example shows the code for moving all of the ports from the default VLAN to VLAN
100.
Console(config)#vlan100
Console(config-vlan-100)#untagged ethernet 1/1 to 1/25
Console(config-vlan-100)#exit
Console(config)#interface vlan 100
Console(config-if)#ip address 192.168.2.1 255.255.255.0
Console(config-if)#exit
Console(config)#vlan 100
Console(config-vlan-100)#untagged ethernet 1/26
Adding Interfaces Based on Membership Type
Use the VLAN Static Table to modify the settings for an existing VLAN. You can add or delete port
members for a VLAN, disable or enable VLAN tagging for any port, or prevent a port from being
automatically added to a VLAN via the GVRP protocol. (Note that VLAN 1 is the default untagged
VLAN containing all ports on the switch, and cannot be modified via this page.)
You can use the VLAN Static Table to assign ports to the specified VLAN group as an IEEE 802.1Q
tagged port. Assign ports as tagged if they are connected to 802.1Q VLAN-compliant devices. If the
port is connected to VLAN-unaware devices, frames will be passed to the untagged VLAN group this
port has been assigned to under the VLAN Port Configuration page.
December 2007
© 2007 Foundry Networks, Inc.
22-11
Foundry EdgeIron User Guide
USING THE WEB INTERFACE
Click VLAN, 802.1Q VLAN, Static Table. Select a VLAN ID from the scroll-down list. Modify the
VLAN name and status if required. Select the membership type by marking the appropriate radio
button in the list of ports or trunks. Click Apply.
•
Port – Port identifier.
•
Trunk – Trunk identifier.
•
VLAN – ID of configured VLAN (1-4094, no leading zeroes).
•
Name – Name of the VLAN (1 to 32 characters).
•
Status – Shows if this VLAN is enabled or disabled.
- Enable: VLAN is operational.
- Disable: VLAN is suspended; i.e., does not pass packets.
•
Membership Type – Select VLAN membership for each interface by marking the appropriate
radio button for a port or trunk:
- Tagged: Interface is a member of the VLAN. All packets transmitted by the port will be tagged,
that is, carry a tag and therefore carry VLAN or CoS information.
- Untagged: Interface is a member of the VLAN. All packets transmitted by the port will be
untagged, that is, not carry a tag and therefore not carry VLAN or CoS information. Note that
an interface must be assigned to at least one group as an untagged port.
- Forbidden: Interface is forbidden from automatically joining the VLAN via GVRP. For more
information, see “Automatic VLAN Registration”.
- None: Interface is not a member of the VLAN. Packets associated with this VLAN will not be
transmitted by the interface.
•
22-12
Trunk Member – Indicates if a port is a member of a trunk. To add a trunk to the selected VLAN,
use the last table on the VLAN Static Table page.
© 2007 Foundry Networks, Inc.
March 2007
802.1Q VLANs
USING THE CLI
Enter the following commands.
untagged ethernet
Use this command to assign ports as untagged members of a port-based VLAN. Use the no form to
remove ports from a port-based VLAN.
Note: This command is available beginning with release 2.2.4.11.
Syntax
[no] untagged ethernet interface [to interface]
• interface - Specifies a port number, or the start or end of a port range, to assign to the VLAN.
• unit/port
- unit - This is device 1.
- port - Port number.
• to - Specifies the end of a port number range.
Default Setting
None
Command Mode
VLAN Configuration
Example
The following example shows how to assign switch ports 1 to 8 as untagged members of VLAN 222.
Console(config)#vlan 222 by port
Console(config-vlan-222)#untagged ethernet 1/1 to 1/8
Console(config-if)#
Related Commands
vlan (22-10)
tagged ethernet (22-14)
dual-mode (22-14)
December 2007
© 2007 Foundry Networks, Inc.
22-13
Foundry EdgeIron User Guide
tagged ethernet
Use this command to assign ports as tagged members of a port-based VLAN. Use the no form to
remove ports from the port-based VLAN.
Note: This command is available beginning with release 2.2.4.11.
Syntax
[no] tagged ethernet interface [to interface]
• interface - Specifies a port number, or the start or end of a port range, to assign to the VLAN.
• unit/port
- unit - This is device 1.
- port - Port number.
• to - Specifies the end of a port number range.
Default Setting
None
Command Mode
VLAN Configuration
Example
The following example shows how to assign port 5 as a tagged member of VLAN 222.
Console(config)#vlan 222 by port
Console(config-vlan-222)#tagged ethernet 1/5
Console(config-vlan-222)#
dual-mode
Use this command to enable a tagged VLAN port to accept and transmit both tagged and untagged
traffic. Use the no form to restore the default setting.
Syntax
dual-mode [vlan_id]
no dual-mode
• vlan_id - Specifies the default VLAN ID for the port. (Range: 1-4094, no leading zeroes).
Default Setting
Disabled
Command Usage
Configuring a tagged port as a dual-mode port allows it to accept and transmit both tagged traffic
and untagged traffic at the same time. A dual-mode port transmits only untagged traffic on its default
VLAN (that is either VLAN 1, or a user specified VLAN ID), and only tagged traffic on all other
VLANs.
Command Mode
Interface Configuration
22-14
© 2007 Foundry Networks, Inc.
March 2007
802.1Q VLANs
Example
The following example shows how to enable dual-mode on port 5 and set its default VLAN ID to 10.
Console(config)#vlan 10 by port
Console(config-vlan-10)#tagged ethernet 1/5
Console(config-vlan-10)#exit
Console(config)#interface ethernet 1/5
Console(config-if)#dual-mode 10
Console(config-if)#
Related Commands
vlan (22-10)
tagged ethernet (22-14)
untagged ethernet (22-13)
Adding Interfaces Based on Static Membership
Use the VLAN Static Membership by Port menu to assign VLAN groups to the selected interface add
an interface to the selected VLAN as a tagged member.
USING THE WEB INTERFACE
Click VLAN, 802.1Q VLAN, Static Membership. Select an interface from the scroll-down box (Port or
Trunk). Click Query to display VLAN membership information for the interface. Select a VLAN ID, and
then click Add to add the interface as a tagged member, or click Remove to remove the interface.
After configuring VLAN membership for each interface, click Apply.
•
Interface – Port or trunk identifier.
•
Member – VLANs for which the selected interface is a tagged member.
•
Non-Member – VLANs for which the selected interface is not a tagged member.
December 2007
© 2007 Foundry Networks, Inc.
22-15
Foundry EdgeIron User Guide
USING THE CLI
Enter the following commands.
interface vlan
Use this command to enter interface configuration mode for VLANs, and configure a physical
interface.
Syntax
interface vlan vlan-id
vlan-id - ID of the configured VLAN. (Range: 1-4094, no leading zeroes)
Default Setting
None
Command Mode
Global Configuration
Example
The following example shows how to set the interface configuration mode to VLAN 1, and then
assign an IP address to the VLAN:
Console(config)#interface vlan 1
Console(config-if)#ip address 192.168.1.254 255.255.255.0
Console(config-if)#
switchport mode
Use this command to configure the VLAN membership mode for a port. Use the no form to restore
the default.
Syntax
switchport mode {trunk | hybrid}
no switchport mode
• trunk - Specifies a port as an end-point for a VLAN trunk. A trunk is a direct link between two
switches, so the port transmits tagged frames that identify the source VLAN. Note that frames
belonging to the port’s default VLAN (i.e.,associated with the PVID) are also transmitted as
tagged frames.
• hybrid - Specifies a hybrid VLAN interface. The port may transmit tagged or untagged frames.
Default Setting
All ports are in hybrid mode with the PVID set to VLAN 1.
Command Mode
Interface Configuration (Ethernet, Port Channel)
22-16
© 2007 Foundry Networks, Inc.
March 2007
802.1Q VLANs
Example
The following shows how to set the configuration mode to port 1, and then set the switchport mode to
hybrid:
Console(config)#interface ethernet 1/1
Console(config-if)#switchport mode hybrid
Console(config-if)#
Related Commands
switchport acceptable-frame-types (22-19)
Configuring VLAN Behavior for Interfaces
You can configure VLAN behavior for specific interfaces, including the default VLAN identifier (PVID),
accepted frame types, and ingress filtering, GVRP status, and GARP timers.
Command Usage
• GVRP – GARP VLAN Registration Protocol defines a way for switches to exchange VLAN
information in order to automatically register VLAN members on interfaces across the network.
•
GARP – Group Address Registration Protocol is used by GVRP to register or deregister client
attributes for client services within a bridged LAN. The default values for the GARP timers are
independent of the media access method or data rate. These values should not be changed
unless you are experiencing difficulties with GVRP registration/deregistration.
USING THE WEB INTERFACE
Click VLAN, 802.1Q VLAN, Port Configuration or VLAN Trunk Configuration. Fill in the required
settings for each interface, click Apply.
•
PVID – VLAN ID assigned to untagged frames received on the interface. (Default: 1)
- If an interface is not a member of VLAN 1 and you assign its PVID to this VLAN, the interface
will automatically be added to VLAN 1 as an untagged member. For all other VLANs, an
interface must first be configured as an untagged member before you can assign its PVID to
that group.
December 2007
© 2007 Foundry Networks, Inc.
22-17
Foundry EdgeIron User Guide
•
Acceptable Frame Type – Sets the interface to accept all frame types, including tagged or
untagged frames, or only tagged frames. When set to receive all frame types, any received
frames that are untagged are assigned to the default VLAN. (Option: All, Tagged; Default: All)
•
Ingress Filtering – If ingress filtering is enabled, incoming frames for VLANs which do not include
this ingress port in their member set will be discarded at the ingress port. (Default: Disabled)
- Ingress filtering only affects tagged frames.
- If ingress filtering is disabled, the interface will flood incoming frames for VLANs which do not
include this ingress port in their member set (except for those VLANs explicitly forbidden on this
port).
- If ingress filtering is enabled, the interface will discard incoming frames tagged for VLANs which
do not include this ingress port in their member set.
- Ingress filtering does not affect VLAN independent BPDU frames, such as STP. However, it
does affect VLAN dependent BPDU frames, such as GMRP.
•
GVRP Status – Enables/disables GVRP for the interface. GVRP must be globally enabled for the
switch before this setting can take effect. (See “Enabling or Disabling GVRP (Global Setting)” on
page 22-4.) When disabled, any GVRP packets received on this port will be discarded and no
GVRP registrations will be propagated from other ports. (Default: Enabled)
•
GARP Join Timer* – The interval between transmitting requests/queries to participate in a VLAN
group. (Range: 20-1000 centiseconds; Default: 20)
•
GARP Leave Timer* – The interval a port waits before leaving a VLAN group. This time should
be set to more than twice the join time. This ensures that after a Leave or LeaveAll message has
been issued, the applicants can rejoin before the port actually leaves the group. (Range: 60-3000
centiseconds; Default: 60)
•
GARP LeaveAll Timer* – The interval between sending out a LeaveAll query message for VLAN
group participants and the port leaving the group. This interval should be considerably larger than
the Leave Time to minimize the amount of traffic generated by nodes rejoining the group.
(Range: 500-18000 centiseconds; Default: 1000)
* GARP timer settings must follow this rule:
2 x (join timer) < leave timer < leaveAll timer
•
Mode – Indicates VLAN membership mode for a port.
(Default: Hybrid.)
- 1Q Trunk – Specifies a port as an end-point for a VLAN trunk. A trunk is a direct link between
two switches, so the port transmits tagged frames that identify the source VLAN. Note that
frames belonging to the port’s default VLAN (i.e.,associated with the PVID) are also transmitted
as tagged frames.
- Hybrid – Specifies a hybrid VLAN interface. The port may receive or transmit tagged or
untagged frames.
•
22-18
Dual Mode/VLAN ID – Enables dual mode, the ability of a port to accept both tagged and
untagged traffic at the same time. A dual mode port transmits only untagged traffic on its default
VLAN (that is either VLAN 1, or a user specified VLAN ID), and only tagged traffic on all other
VLANs. Allows you to specify a VLAN ID also. (Range: 1-4094; Default: 0)
© 2007 Foundry Networks, Inc.
March 2007
802.1Q VLANs
•
Trunk Member – Indicates if a port is a member of a trunk. To add a trunk to the selected VLAN,
use the last table on the VLAN Static Table page.
USING THE CLI
Enter the following commands.
switchport mode
Use this command to configure the VLAN membership mode for a port. Use the no form to restore
the default.
Syntax
switchport mode {trunk | hybrid}
no switchport mode
• trunk - Specifies a port as an end-point for a VLAN trunk. A trunk is a direct link between two
switches, so the port transmits tagged frames that identify the source VLAN. Note that frames
belonging to the port’s default VLAN (i.e.,associated with the PVID) are also transmitted as
tagged frames.
• hybrid - Specifies a hybrid VLAN interface. The port may transmit tagged or untagged frames.
Default Setting
All ports are in hybrid mode with the PVID set to VLAN 1.
Command Mode
Interface Configuration (Ethernet, Port Channel)
Example
The following shows how to set the configuration mode to port 1, and then set the switchport mode to
hybrid:
Console(config)#interface ethernet 1/1
Console(config-if)#switchport mode hybrid
Console(config-if)#
Related Commands
switchport acceptable-frame-types (22-19)
switchport acceptable-frame-types
Use this command to configure the acceptable frame types for a port. Use the no form to restore the
default.
Syntax
switchport acceptable-frame-types {all | tagged}
no switchport acceptable-frame-types
• all - The port passes all frames, tagged or untagged.
• tagged - The port only passes tagged frames.
Default Setting
All frame types
December 2007
© 2007 Foundry Networks, Inc.
22-19
Foundry EdgeIron User Guide
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
When set to receive all frame types, any received frames that are untagged are assigned to the
default VLAN.
Example
The following example shows how to restrict the traffic passed on port 1 to tagged frames:
Console(config)#interface ethernet 1/1
Console(config-if)#switchport acceptable-frame-types tagged
Console(config-if)#
Related Commands
switchport mode (22-16)
switchport ingress-filtering
Use this command to enable ingress filtering for an interface. Use the no form to restore the default.
Syntax
[no] switchport ingress-filtering
Default Setting
Disabled
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
• Ingress filtering only affects tagged frames.
• If ingress filtering is disabled and a port receives frames tagged for VLANs for which it is not a
member, these frames will be flooded to all other ports (except for those VLANs explicitly
forbidden on this port).
• If ingress filtering is enabled and a port receives frames tagged for VLANs for which it is not a
member, these frames will be discarded.
• Ingress filtering does not affect VLAN independent BPDU frames, such as GVRP or STP.
However, they do affect VLAN dependent BPDU frames, such as GMRP.
Example
The following example shows how to set the interface to port 1 and then enable ingress filtering:
Console(config)#interface ethernet 1/1
Console(config-if)#switchport ingress-filtering
Console(config-if)#
22-20
© 2007 Foundry Networks, Inc.
March 2007
802.1Q VLANs
switchport forbidden vlan
Use this command to configure forbidden VLANs. Use the no form to remove the list of forbidden
VLANs.
Syntax
switchport forbidden vlan {add vlan-list | remove vlan-list}
no switchport forbidden vlan
• add vlan-list - List of VLAN identifiers to add.
• remove vlan-list - List of VLAN identifiers to remove.
• vlan-list - Separate nonconsecutive VLAN identifiers with a comma and no spaces; use a
hyphen to designate a range of IDs. Do not enter leading zeros. (Range: 1-4094)
Default Setting
No VLANs are included in the forbidden list.
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
• This command prevents a VLAN from being automatically added to the specified interface via
GVRP.
• If a VLAN has been added to the set of allowed VLANs for an interface, then you cannot add it to
the set of forbidden VLANs for that same interface.
Example
The following example shows how to prevent port 1 from being added to VLAN 3:
Console(config)#interface ethernet 1/1
Console(config-if)#switchport forbidden vlan add 3
Console(config-if)#
show vlan
Use this command to show VLAN information.
Syntax
show vlan [id vlan-id | name vlan-name]
• id - Keyword to be followed by the VLAN ID.
-vlan-id - ID of the configured VLAN. (Range: 1-4094, no leading zeroes)
• name - Keyword to be followed by the VLAN name.
-vlan-name - ASCII string from 1 to 32 characters.
Default Setting
Shows all VLANs.
Command Mode
Normal Exec, Privileged Exec
December 2007
© 2007 Foundry Networks, Inc.
22-21
Foundry EdgeIron User Guide
Example
The following example shows how to display information for VLAN 33:
Console#show vlan id 1
VLAN Type
Name
Status
Ports/Channel groups
---- ------- ---------------- --------- ------------------------------------33 Static Blue
Active Eth1/ 2 Eth1/ 3 Eth1/ 6 Eth1/ 7
Eth1/ 9 Eth1/ 10 Eth1/ 11 Eth1/ 12
Console#
show interfaces status
Use this command to display the status for an interface.
Syntax
show interfaces status interface
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
• vlan vlan-id (Range: 1-4094)
Default Setting
Shows the status for all interfaces.
Command Mode
Normal Exec, Privileged Exec
Command Usage
• If no interface is specified, information on all interfaces is displayed.
• For a description of the items displayed by this command, see “Displaying Connection Status” on
page 17-3.
Example
Console#show interface status ethernet 1/5
Information of Eth 1/5
Basic information:
Port type: 100TX
Mac address: 00-30-F1-47-58-3F
Configuration:
Name:
Port admin: Up
Speed-duplex: Auto
Capabilities: 10half, 10full, 100half, 100full,
Broadcast storm: Enabled
Broadcast storm limit: 500 packets/second
Flow control: Disabled
Lacp: Disabled
Port security: Disabled
Port security action: None
Current status:
Link status: Up
Port operation status: Up
Operation speed-duplex: 100full
Flow control type: None
Console#
22-22
© 2007 Foundry Networks, Inc.
March 2007
802.1Q VLANs
show interfaces switchport
Use this command to display the administrative and operational status of specified interfaces.
Syntax
show interfaces switchport [interface]
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
Default Setting
Shows all interfaces.
Command Mode
Normal Exec, Privileged Exec
Command Usage
If no interface is specified, information on all interfaces is displayed. The items displayed by this
command include:
• Broadcast threshold – Shows if broadcast storm suppression is enabled or disabled; if
enabled it also shows the threshold level (see “switchport broadcast” on page 17-25).
• Lacp status – Shows if Link Aggregation Control Protocol has been enabled or disabled
(see “show lacp” on page 18-9).
• Dual-mode – Indicates if Dual Mode has been enabled.
• VLAN membership mode – Indicates membership mode as Trunk or Hybrid (see “switchport
mode” on page 22-16).
• Ingress rule – Shows if ingress filtering is enabled or disabled (see “switchport ingress-filtering”
on page 22-20).
• Acceptable frame type – Shows if acceptable VLAN frames include all types or tagged frames
only (see “switchport acceptable-frame-types” on page 22-19).
• Native VLAN – Indicates the default Port VLAN ID (see “802.1Q VLANs” on page 22-1).
• Priority for untagged traffic – Indicates the default priority for untagged frames (see
“Changing Priorities Based on ACL Rules” on page 25-24).
• Gvrp status – Shows if GARP VLAN Registration Protocol is enabled or disabled (see
“switchport gvrp” on page 22-5).
• Allowed Vlan – Shows the VLANs this interface has joined, where "(u)” indicates untagged and
“(t)” indicates tagged (see “802.1Q VLANs” on page 22-1).
• Forbidden Vlan – Shows the VLANs this interface can not dynamically join via GVRP
(see “switchport forbidden vlan” on page 22-21).
December 2007
© 2007 Foundry Networks, Inc.
22-23
Foundry EdgeIron User Guide
Example
This example shows the configuration setting for Ethernet port 15.
Console#show interfaces switchport ethernet 1/15
Information of Eth 1/23
Broadcast threshold: Enabled, 500 packets/second
Lacp status: Disabled
Dual-mode: 0
Ingress rate limit: disable,1000M bits per second
Egress rate limit: disable,1000M bits per second
VLAN membership mode: Hybrid
Ingress rule: Disabled
Acceptable frame type: All frames
Native VLAN: 1
Priority for untagged traffic: 0
Gvrp status: Disabled
Allowed Vlan:
1(u),
Forbidden Vlan:
Console#
22-24
© 2007 Foundry Networks, Inc.
March 2007
Chapter 23
Private VLANs
Note: Private VLANs are not supported on 2402CF and 4802CF starting from version 2.2.4.0.
Private VLANs provide port-based security and isolation between ports within the assigned VLAN.
Data traffic on downlink ports can only be forwarded to, and from, uplink ports. (Note that private
VLANs and normal VLANs can exist simultaneously within the same switch.)
The EdgeIron switches support two types of private VLAN ports: promiscuous, and community ports.
A promiscuous port can communicate with all interfaces within a private VLAN. Community ports
can only communicate with other ports in their own community VLAN, and with their designated
promiscuous ports.
Primary Ports
Primary VLAN
(promiscuous ports)
x
Downlink Ports
Community VLAN
(private ports)
The following table briefly describes the private VLAN commands:
Command
Function
Mode
Page
private-vlan
Adds or deletes primary and community VLANs
VC
23-2
private-vlan association
Associates a community VLAN with a primary VLAN
VC
23-3
Edit Private VLAN Groups
Configure Private VLAN Interfaces
switchport mode private-vlan
Sets an interface to host mode or promiscuous mode
IC
23-4
switchport private-vlan hostassociation
Associates an interface with a community VLAN
IC
23-5
switchport private-vlan mapping
Maps an interface to a primary VLAN
IC
23-5
NE, PE
23-6
Display Private VLAN Information
show vlan private-vlan
December 2007
Shows private VLAN information
© 2007 Foundry Networks, Inc.
23-1
Foundry EdgeIron User Guide
Enabling Private VLANs
Use the Private VLAN Status page to enable/disable the Private VLAN function.
USING THE WEB INTERFACE
Click VLAN, Private VLAN, Status. Select Enable or Disable from the scroll-down box, and click
Apply.
USING THE CLI
To configure private VLANs, follow these steps:
1. Use the private-vlan command to designate one or more community VLANs and the primary
VLAN that will channel traffic outside the community groups.
2. Use the private-vlan association command to map the community VLAN(s) to the primary
VLAN.
3. Use the switchport mode private-vlan command to configure ports as promiscuous (i.e.,
having access to all ports in the primary VLAN) or host (i.e., having access restricted to
community VLAN members, and channeling all other traffic through a promiscuous port).
4. Use the switchport private-vlan host-association command to assign a port to a community
VLAN.
5. Use the switchport private-vlan mapping command to assign a port to a primary VLAN.
6. Use the show vlan private-vlan command to verify your configuration settings.
private-vlan
Use this command to create a primary or community private VLAN. Use the no form to remove the
specified private VLAN.
Syntax
private-vlan vlan-id {community | primary}
no private-vlan vlan-id
• vlan-id - ID of private VLAN. (Range: 1-4093, no leading zeroes).
• community – Specifies a community VLAN.
• primary – Specifies a primary VLAN.
Default Setting
None
23-2
© 2007 Foundry Networks, Inc.
March 2007
Private VLANs
Command Mode
VLAN Configuration
Command Usage
• Private VLANs are used to restrict traffic to ports within the same VLAN “community,” and channel
traffic passing outside the community through promiscuous ports that have been mapped to the
associated “primary” VLAN.
• Port membership for private VLANs is static. Once a port has been assigned to a private VLAN,
it cannot be dynamically moved to another VLAN via GVRP.
• Private VLAN ports cannot be set to trunked mode. (See “switchport mode” on page 22-16.)
Example
Console(config)#vlan database
Console(config-vlan)#private-vlan 2 primary
Console(config-vlan)#private-vlan 3 community
Console(config)#
private vlan association
Use this command to associate a primary VLAN with a community VLAN. Use the no form to
remove all associations for the specified primary VLAN.
Syntax
private-vlan primary-vlan-id association {secondary-vlan-id | add secondary-vlan-id | remove
secondary-vlan-id}
no private-vlan primary-vlan-id association
• primary-vlan-id - ID of primary VLAN.
(Range: 2-4094, no leading zeroes).
• secondary-vlan-id - ID of community VLAN. (Range: 2-4094, no leading zeroes).
Default Setting
None
Command Mode
VLAN Configuration
Command Usage
Community VLANs provide security for group members. The associated primary VLAN provides
a common interface for access to other network resources within the primary VLAN (e.g., servers
configured with promiscuous ports) and to resources outside of the primary VLAN (via
promiscuous ports).
Example
Console(config-vlan)#private-vlan 2 association 3
Console(config)#
December 2007
© 2007 Foundry Networks, Inc.
23-3
Foundry EdgeIron User Guide
Configuring Uplink and Downlink Ports
USING THE WEB INTERFACE
Use the Private VLAN Link Status page to set ports as downlink or uplink ports. Ports designated as
downlink ports can not communicate with any other ports on the switch except for the uplink ports.
Uplink ports can communicate with any other ports on the switch and with any designated downlink
ports.
Click VLAN, Private VLAN, Link Status. Mark the ports that will serve as uplinks and downlinks for
the private VLAN, then click Apply.
USING THE CLI
switchport mode private-vlan
Use this command to set the private VLAN mode for an interface. Use the no form to restore the
default setting.
Syntax
switchport mode private-vlan {host | promiscuous}
no switchport mode private-vlan
• host – This port type can communicate with all other host ports assigned to the same
community VLAN. All communications outside of this VLAN must pass through a promiscuous
port in the associated primary VLAN.
• promiscuous – This port type can communicate with all other promiscuous ports in the same
primary VLAN, as well as with all the ports in the associated community VLANs.
Default Setting
Normal VLAN
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
Promiscuous ports assigned to a primary VLAN can communicate with all other promiscuous
ports in the same VLAN, as well as with all the ports in the associated community VLANs.
23-4
© 2007 Foundry Networks, Inc.
March 2007
Private VLANs
Example
Console(config)#interface ethernet
Console(config-if)#switchport mode
Console(config)#exit
Console(config)#interface ethernet
Console(config-if)#switchport mode
Console(config)#
1/2
private-vlan promiscuous
1/3
private-vlan host
switchport private-vlan host-association
Use this command to associate an interface with a community VLAN. Use the no form to remove this
association.
Syntax
switchport private-vlan host-association secondary-vlan-id
no switchport private-vlan host-association
• secondary-vlan-id – ID of community VLAN.
(Range: 1-4093, no leading zeroes).
Default Setting
None
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
All ports assigned to a community VLAN can pass traffic between group members, but must
communicate with resources outside of the group via a promiscuous port.
Example
Console(config)#interface ethernet 1/3
Console(config-if)#switchport private-vlan host-association 3
Console(config)#
switchport private-vlan mapping
Use this command to map an interface to a primary VLAN. Use the no form to remove this mapping.
Syntax
switchport private-vlan mapping primary-vlan-id
no switchport private-vlan mapping
primary-vlan-id – ID of primary VLAN. (Range: 1-4093, no leading zeroes).
Default Setting
None
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
Promiscuous ports assigned to a primary VLAN can communicate with any other promiscuous
ports in the same VLAN, and with the group members within any associated community VLANs.
December 2007
© 2007 Foundry Networks, Inc.
23-5
Foundry EdgeIron User Guide
Example
Console(config)#interface ethernet 1/2
Console(config-if)#switchport private-vlan mapping 2
Console(config)#
Displaying Private VLAN Information
There is no comparable Web page to display Private VLAN information.
USING THE CLI
show vlan private-vlan
Use this command to show the private VLAN configuration settings on this switch.
Syntax
show vlan private-vlan [community | primary]
• community – Displays all community VLANs, along with their associate primary VLAN and
assigned host interfaces.
• primary – Displays all primary VLANs, along with any assigned promiscuous interfaces.
Default Setting
None
Command Mode
Privileged Executive
Example
Console#show vlan private-vlan
Primary
Secondary
Type
-------- ----------- ---------5
primary
5
6
community
Console#
23-6
Interfaces
---------------Eth1/ 3
Eth1/ 4 Eth1/ 5
© 2007 Foundry Networks, Inc.
March 2007
Chapter 24
Protocol VLANs
Note: IPv6 (0X08DD) is not supported.
The network devices required to support multiple protocols cannot be easily grouped into a common
VLAN. This may require non-standard devices to pass traffic between different VLANs in order to
encompass all the devices participating in a specific protocol. This kind of configuration deprives
users of the basic benefits of VLANs, including security and easy accessibility.
To avoid these problems, you can configure this switch with protocol-based VLANs that divide the
physical network into logical VLAN groups for each required protocol. When a frame is received at a
port, its VLAN membership can then be determined based on the protocol type being used by the
inbound packets.
Configuring Protocol-Based VLANs
To configure protocol-based VLANs, follow these steps:
1. First configure VLAN groups for the protocols you want to use (see “Creating VLANs” on page
22-9). Although not mandatory, we suggest configuring a separate VLAN for each major protocol
running on your network. Do not add port members at this time.
2. Create a protocol group for each of the protocols you want to assign to a VLAN using the
Protocol VLAN Configuration page.
3. Then map the protocol for each interface to the appropriate VLAN using the Protocol VLAN Port
Configuration page.
The following table briefly describes the protocol VLAN commands:
Command
Function
Mode
Page
protocol-vlan protocol-group
Create a protocol group, specifying the supported
protocols
GC
24-3
protocol-vlan protocol-group
Maps a protocol group to a VLAN
IC
24-5
show protocol-vlan protocolgroup
Shows the configuration of protocol groups
PE
24-3
Protocol VLAN Groups
December 2007
© 2007 Foundry Networks, Inc.
24-1
Foundry EdgeIron User Guide
Command
Function
Mode
show interfaces protocol-vlan
protocol-group
Shows the interfaces mapped to a protocol group and
the corresponding VLAN
PE
Page
24-5
Configuring Protocol Groups
Create a protocol group for one or more protocols.
USING THE WEB INTERFACE
Click VLAN, Protocol VLAN, Configuration. Enter a protocol group ID, frame type and protocol type,
then click Apply.
•
Protocol Group ID – Group identifier of this protocol group. (Range: 1-2147483647)
•
Frame Type – Frame type used by this protocol. (Options: Ethernet, RFC_1042, LLC_other)
•
Protocol Type – The only option for the LLC_other frame type is IPX_raw. The options for all
other frames types include: IP, ARP, RARP.
USING THE CLI
To configure protocol-based VLANs, follow these steps:
1. First configure VLAN groups for the protocols you want to use. Although not mandatory, we
suggest configuring a separate VLAN for each major protocol running on your network. Do not
add port members at this time.
2. Create a protocol group for each of the protocols you want to assign to a VLAN using the
protocol-vlan protocol-group command (General Configuration mode).
3. Then map the protocol for each interface to the appropriate VLAN using the protocol-vlan
protocol-group command (Interface Configuration mode).
24-2
© 2007 Foundry Networks, Inc.
March 2007
Protocol VLANs
protocol-vlan protocol-group (Configuring Groups)
This command creates a protocol group, or to add specific protocols to a group. Use the no form to
remove a protocol group.
Syntax
protocol-vlan protocol-group group-id [{add | remove} frame-type frame protocol-type
protocol]
no protocol-vlan protocol-group group-id
• group-id - Group identifier of this protocol group. (Range: 1-2147483647)
• frame - Frame type used by this protocol. (Options: ethernet, rfc_1042, llc_other)
• protocol - Protocol type. The only option for the llc_other frame type is ipx_raw. The options for
all other frames types include: ip, arp, rarp.
Default Setting
No protocol groups are configured.
Command Mode
Global Configuration
Example
The following creates protocol group 1, and specifies Ethernet frames with IP and ARP protocol
types
:
Console(config)#protocol-vlan protocol-group 1 add frame-type
ethernet protocol-type ip
Console(config)#protocol-vlan protocol-group 1 add frame-type
ethernet protocol-type arp
Console(config)#
show protocol-vlan protocol-group
This command shows the frame and protocol type associated with protocol groups.
Syntax
show protocol-vlan protocol-group [group-id]
• group-id - Group identifier for a protocol group. (Range: 1-2147483647)
Default Setting
All protocol groups are displayed.
Command Mode
Privileged Exec
Example
This shows protocol group 1 configured for IP over Ethernet:
Console#show protocol-vlan protocol-group
ProtocolGroup ID
Frame Type
Protocol Type
------------------ ------------- --------------1
ethernet
08 00
Console#
December 2007
© 2007 Foundry Networks, Inc.
24-3
Foundry EdgeIron User Guide
Mapping Protocols to VLANs
Map a protocol group to a VLAN for each interface that will participate in the group.
USING THE WEB INTERFACE
• When creating a protocol-based VLAN, only assign interfaces using this configuration screen. If
you assign interfaces using any of the other VLAN commands such as VLAN Static Table (see
“Adding Interfaces Based on Static Membership” on page 22-15) or VLAN Static Membership
(see “Adding Interfaces Based on Static Membership” on page 22-15), these interfaces will admit
traffic of any protocol type into the associated VLAN.
• When a frame enters a port that has been assigned to a protocol VLAN, it is processed in the
following manner:
- If the frame is tagged, it will be processed according to the standard rules applied to tagged
frames.
- If the frame is untagged and the protocol type matches, the frame is forwarded to the
appropriate VLAN.
- If the frame is untagged but the protocol type does not match, the frame is forwarded to the
default VLAN for this interface.
Click VLAN, Protocol VLAN, Port Configuration. Select a a port or trunk, enter a protocol group ID,
the corresponding VLAN ID, and click Apply.
24-4
•
Interface – Port or trunk identifier.
•
Protocol Group ID – Group identifier of this protocol group. (Range: 1-2147483647)
•
VLAN ID – VLAN to which matching protocol traffic is forwarded. (Range: 1-4094)
© 2007 Foundry Networks, Inc.
March 2007
Protocol VLANs
USING THE CLI
protocol-vlan protocol-group (Configuring Interfaces)
This command maps a protocol group to a VLAN for the current interface. Use the no form to remove
the protocol mapping for this interface.
Syntax
protocol-vlan protocol-group group-id vlan vlan-id
no protocol-vlan protocol-group group-id vlan
• group-id - Group identifier of this protocol group. (Range: 1-2147483647)
• vlan-id - VLAN to which matching protocol traffic is forwarded. (Range: 1-4094)
Default Setting
No protocol groups are mapped for any interface.
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
• When creating a protocol-based VLAN, only assign interfaces via this command. If you assign
interfaces using any of the other VLAN commands (such as vlan (22-10)), these interfaces will
admit traffic of any protocol type into the associated VLAN.
• When a frame enters a port that has been assigned to a protocol VLAN, it is processed in the
following manner:
• If the frame is tagged, it will be processed according to the standard rules applied to tagged
frames.
• If the frame is untagged and the protocol type matches, the frame is forwarded to the appropriate
VLAN.
• If the frame is untagged but the protocol type does not match, the frame is forwarded to the default
VLAN for this interface.
Example
The following example maps the traffic entering Port 1 which matches the protocol type specified
in protocol group 1 to VLAN 2.
Console(config)#interface ethernet 1/1
Console(config-if)#protocol-vlan protocol-group 1 vlan 2
Console(config-if)#
show interfaces protocol-vlan protocol-group
This command shows the mapping from protocol groups to VLANs for the selected interfaces.
Syntax
show interfaces protocol-vlan protocol-group [interface]
• interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
December 2007
© 2007 Foundry Networks, Inc.
24-5
Foundry EdgeIron User Guide
Default Setting
The mapping for all interfaces is displayed.
Command Mode
Privileged Exec
Example
This shows that traffic entering Port 1 that matches the specifications for protocol group 1 will be
mapped to VLAN 2:
Console#show interfaces protocol-vlan protocol-group
Port
ProtocolGroup ID
Vlan ID
---------- ------------------ ----------Eth 1/1
1
vlan2
Console#
24-6
© 2007 Foundry Networks, Inc.
March 2007
Chapter 25
Class of Service
Class of Service (CoS) allows you to specify which data packets have greater precedence when
traffic is buffered in the switch due to congestion. This switch supports CoS with four priority queues
for each port. Data packets in a port’s high-priority queue will be transmitted before those in the
lower-priority queues. You can set the default priority for each interface, and configure the mapping
of frame priority tags to the switch’s priority queues.
The the CLI commands for this section are briefly described in the table that follows:
Command
Function
Mode
Page
switchport priority default
Sets a port priority for incoming untagged frames
IC
25-3
queue bandwidth
Assigns round-robin weights to the priority queues
GC
25-6
queue cos map
Assigns class of service values to the priority queues
IC
25-7
show queue bandwidth
Shows round-robin weights assigned to the priority
queues
PE
25-8
show queue cos-map
Shows the class of service map
PE
25-9
show interfaces switchport
Displays the administrative and operational status of an
interface
PE
17-10
Layer 2 Priority Commands
Layer 3 and 4 Priority Commands
map ip precedence
Enables IP precedence class of service mapping
GC
25-12
map ip precedence
Maps IP precedence value to a class of service
IC
25-12
map ip dscp
Enables IP DSCP class of service mapping
GC
25-15
map ip dscp
Maps IP DSCP value to a class of service
IC
25-15
map ip port
Enables TCP/UDP class of service mapping
GC
25-18
map ip port
Maps TCP/UDP socket to a class of service
IC
25-18
show map ip precedence
Shows the IP precedence map
PE
25-19
show map ip dscp
Shows the IP DSCP map
PE
25-20
show map ip port
Shows the IP port map
PE
25-20
December 2007
© 2007 Foundry Networks, Inc.
25-1
Foundry EdgeIron User Guide
Setting the Default Priority for Interfaces
You can specify the default port priority for each interface on the switch. All untagged packets
entering the switch are tagged with the specified default port priority, and then sorted into the
appropriate priority queue at the output port.
Command Usage
• The EdgeIron range provides four priority queues for each port. It uses Weighted Round Robin
to prevent head-of-queue blockage.
•
The default priority applies if the incoming frame is an untagged frame received from a VLAN
trunk or a static-access port. This priority does not apply to IEEE 802.1Q VLAN tagged frames. If
the incoming frame is an IEEE 802.1Q VLAN tagged frame, the IEEE 802.1p User Priority bits
will be used.
•
If the output port is an untagged member of the associated VLAN, these frames are stripped of
all VLAN tags prior to transmission.
USING THE WEB INTERFACE
Click Priority, Default Port Priority or Default Trunk Priority. Modify the default priority for any
interface, then click Apply.
25-2
•
Default Priority – The priority that is assigned to untagged frames received on the specified port.
(Range: 0 - 7, Default: 0)
•
Number of Egress Traffic Classes – The number of queue buffers provided for each port.
© 2007 Foundry Networks, Inc.
March 2007
Class of Service
USING THE CLI
switchport priority default
Use this command to set a priority for incoming untagged frames, or the priority of frames received
by the device connected to the specified interface. Use the no form to restore the default value.
Syntax
switchport priority default default-priority-id
no switchport priority default
default-priority-id - The priority number for untagged ingress traffic.
The priority is a number from 0 to 7. Seven is the highest priority.
Default Setting
The priority is not set, and the default value for untagged frames received on the interface is zero.
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
• The precedence for priority mapping is IP Precedence or IP DSCP, and default switchport priority.
• The default priority applies for an untagged frame received on a port set to accept all frame types
(i.e, receives both untagged and tagged frames). This priority does not apply to IEEE 802.1Q
VLAN tagged frames. If the incoming frame is an IEEE 802.1Q VLAN tagged frame, the IEEE
802.1p User Priority bits will be used.
• This switch provides four priority queues for each port. It is configured to use Weighted Round
Robin, which can be viewed with the queue bandwidth command. Inbound frames that do not
have VLAN tags are tagged with the input port’s default ingress user priority, and then placed in
the appropriate priority queue at the output port. The default priority for all ingress ports is zero.
Therefore, any inbound frames that do not have priority tags will be placed in queue 0 of the output
port. (Note that if the output port is an untagged member of the associated VLAN, these frames
are stripped of all VLAN tags prior to transmission.)
Example
The following example shows how to set a default priority on port 3 to 5:
Console(config)#interface ethernet 1/3
Console(config-if)#switchport priority default 5
December 2007
© 2007 Foundry Networks, Inc.
25-3
Foundry EdgeIron User Guide
Mapping CoS Values to Egress Queues
The EdgeIron range processes Class of Service (CoS) priority tagged traffic by using priority queues
for each port, with service schedules based on Weighted Round Robin (WRR). The EIF4802 and
EIF2402 use four priority queues, while the 24G-A and 48G use eight priority queues. Up to eight
separate traffic priorities are defined in IEEE 802.1p. The default priority levels are assigned
according to recommendations in the IEEE 802.1p standard as shown in the following table.
2402CF, 4802CF Priority Queue Mapping
Queue
0
1
2
3
0
1
Priority
2
3
4
5
6
7
24G-A, 48G, 24GS, 48GS and 8X10G Priority Queue Mapping
Queue
0
1
2
3
4
5
6
7
0
1
Priority
2
3
4
5
6
7
25-4
© 2007 Foundry Networks, Inc.
March 2007
Class of Service
The priority levels recommended in the IEEE 802.1p standard for various network applications are
shown in the following table. However, you can map the priority levels to the switch’s output queues
in any way that benefits application traffic for your own network.
Priority Level
Traffic Type
1
Background
2
(Spare)
0 (default)
Best Effort
3
Excellent Effort
4
Controlled Load
5
Video, less than 100 milliseconds latency and jitter
6
Voice, less than 10 milliseconds latency and jitter
7
Network Control
USING THE WEB INTERFACE
Click Priority, Traffic Classes. Assign priorities to the output queues, then click Apply.
•
Priority – CoS value. (Range: 0 to 7, where 7 is the highest priority)
•
Traffic Class – Output queue buffer.
USING THE CLI
Refer to “Setting the Service Weight for Traffic Classes” on page 25-6.
December 2007
© 2007 Foundry Networks, Inc.
25-5
Foundry EdgeIron User Guide
Setting the Service Weight for Traffic Classes
This switch uses the Weighted Round Robin (WRR) algorithm to determine the frequency at which it
services each priority queue. As described in “Mapping CoS Values to Egress Queues” on page 254, the traffic classes are mapped to one of the four egress queues provided for each port. You can
assign a weight to each of these queues (and thereby to the corresponding traffic priorities). This
weight sets the frequency at which each queue will be polled for service, and subsequently affects
the response time for software applications assigned a specific priority value.
USING THE WEB INTERFACE
Click Priority, Queue Scheduling. Select a traffic class by clicking on it with your cursor, enter a
weight value, and then click Apply.
•
•
Interface – Specifies a port or trunk.
WRR Setting Table – Displays a list of weights for each traffic class (i.e., queue).
- EdgeIron 2402CF, 4802CF – Defaults: Weights 1, 4, 16 and 64 are assigned to queue 0, 1, 2
and 3 respectively.
- EdgeIron 24G-A, 48G, 24GS, 48GS, 8X10G – Defaults: Weights 1, 2, 4, 6, 8, 10, 12, 14 are
assigned to queue 0, 1, 2, 3, 4, 5, 6 and 7 respectively.
•
Weight Value – Set a new weight for the selected traffic class. (range: 1-15)
USING THE CLI
queue bandwidth
Use this command to assign Weighted Round-Robin (WRR) weights to the four class of service
(CoS) priority queues. Use the no form to restore the default weights.
Syntax
queue bandwidth weightX...weightY
no queue bandwidth
weightX...weightY - The ratio of weights for queues used by the WRR scheduler.
(See below).
25-6
© 2007 Foundry Networks, Inc.
March 2007
Class of Service
Default Setting
EdgeIron 24G-A, 48G, 24GS, 48GS, 8X10G
Priority
1
2
4
6
8
10
12
14
Queue
0
1
2
3
4
5
6
7
EdgeIron 4802CF, 2402CF
Priority
1
4
16
64
Queue
0
1
2
3
Command Mode
Global Configuration
Command Usage
WRR allows bandwidth sharing at the egress port by defining scheduling weights.
Example
The following example shows how to assign WRR weights of 1, 3, 5 and 7 to the CoS priority queues
0, 1, 2 and 3:
Console(config)#queue bandwidth 1 3 5 7
Console(config)#
Related Commands
show queue bandwidth (25-8)
queue cos-map
Use this command to assign class of service (CoS) values to the priority queues (i.e., hardware
output queues EdgeIron 2402CF, 4802CF: 0-3, and EdgeIron 24G-A, 48G, 24GS, 48GS and 8X10G:
0-7). Use the no form set the CoS map to the default values.
Syntax
queue cos-map queue_id [cos1 ... cosn]
no queue cos-map
• queue_id - The queue ID of the CoS priority queue.
- Ranges are 0 to 3, where 3 is the highest CoS priority queue.
• cos1 .. cosn - The CoS values that are mapped to the queue ID. It is a space-separated list of
numbers. The CoS value is a number from 0 to 7, where 7 is the highest priority.
December 2007
© 2007 Foundry Networks, Inc.
25-7
Foundry EdgeIron User Guide
Default Setting
This switch supports Class of Service by using four priority queues, with Weighted Round Robin
for each port. Eight separate traffic classes are defined in IEEE 802.1p. The default priority levels
are assigned according to recommendations in the IEEE 802.1p standard as shown in the
following table.
Queue
1
2
3
4
0
1
Priority
2
3
4
5
6
7
Note: CoS priority mappings are configured per-port. However, due to a hardware limitations all
mappings are applied system-wide. In other words, no matter which port is set for CoS mapping, it’s
applies globally to all ports.
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
CoS assigned at the ingress port is used to select a CoS priority at the egress port.
Example
The following example shows how to map CoS values 0, 1 and 2 to CoS priority queue 0, value 3 to
CoS priority queue 1, values 4 and 5 to CoS priority queue 2, and values 6 and 7 to CoS priority
queue 3:
Console(config)#interface ethernet
Console(config-if)#queue cos-map 0
Console(config-if)#queue cos-map 1
Console(config-if)#queue cos-map 2
Console(config-if)#queue cos-map 3
Console(config-if)#
1/1
0 1 2
3
4 5
6 7
Related Commands
show queue cos-map (25-9)
show queue bandwidth
Use this command to display the Weighted Round-Robin (WRR) bandwidth allocation for the four
class of service (CoS) priority queues.
Default Setting
None
25-8
© 2007 Foundry Networks, Inc.
March 2007
Class of Service
Command Mode
Privileged Exec
Example
Console#show queue bandwidth
Queue ID Weight
-------- -----0
1
1
4
2
16
3
64
Console#
show queue cos-map
Use this command to show the class of service priority map.
Syntax
show queue cos-map [interface]
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
Default Setting
None
Command Mode
Privileged Exec
Example
Console#show queue
Information of Eth
CoS Value
: 0
Priority Queue: 2
Console#
cos-map ethernet 1/11
1/11
1 2 3 4 5 6 7
0 1 3 4 5 6 7
Mapping Layer 3/4 Priorities to CoS Values
This switch supports a common method of prioritizing layer 3/4 traffic to meet application
requirements. Traffic priorities can be specified in the IP header of a frame, using the priority bits in
the Type of Service (ToS) octet or the number of the TCP port. If priority bits are used, the ToS octet
may contain three bits for IP Precedence or six bits for Differentiated Services Code Point (DSCP)
service. When these services are enabled, the priorities are mapped to a Class of Service value by
the switch, and the traffic then sent to the corresponding output queue.
Because different priority information may be contained in the traffic, this switch maps priority values
to the output queues in the following manner:
•
The precedence for priority mapping is IP Port priority, IP Precedence or DSCP Priority, and then
Default Port Priority.
December 2007
© 2007 Foundry Networks, Inc.
25-9
Foundry EdgeIron User Guide
•
IP Precedence and DSCP Priority cannot both be enabled. Enabling one of these priority types
will automatically disable the other.
•
IP Port, IP Precedence, and DSCP Priority settings are global and apply to all ports on the switch.
Note: IP Precedence/DSCP and TCP port priority to COS mappings are global settings.
Selecting IP Precedence/DSCP Priority
The EdgeIron range allows you to choose between using IP Precedence or DSCP priority. Select
one of the methods or disable this feature.
USING THE WEB INTERFACE
Click Priority, IP Precedence Priority. Select IP Precedence or IP DSCP from the IP
Precedence/DSCP Priority Status menu.
•
IP Precedence/DSCP Priority Status – Selects IP Precedence, DSCP, or disables both priority
services.
USING THE CLI
Refer to the CLI commands in following section.
25-10
© 2007 Foundry Networks, Inc.
March 2007
Class of Service
Mapping IP Precedence
The Type of Service (ToS) octet in the IPv4 header includes three precedence bits defining eight
different priority levels ranging from highest priority for network control packets to lowest priority for
routine traffic. The default IP Precedence values are mapped one-to-one to Class of Service values
(i.e., Precedence value 0 maps to CoS value 0, and so forth). Bits 6 and 7 are used for network
control, and the other bits for various application types. ToS bits are defined in the following table.
Priority Level
Traffic Type
7
Network Control
6
Internetwork Control
5
Critical
4
Flash Override
3
Flash
2
Immediate
1
Priority
0
Routine
USING THE WEB INTERFACE
Click Priority, IP Precedence Priority. Select an IP Precedence value from the IP Precedence Priority
Table by clicking on it with your cursor, enter a value in the Class of Service Value field, and then
click Apply. Be sure to also select IP Precedence from the IP Precedence/DSCP Priority Status
menu.
•
IP Precedence Priority Table – Shows the IP Precedence to CoS map.
•
Class of Service Value – Maps a CoS value to the selected IP Precedence value. Note that “0”
represents low priority and “7” represent high priority.
December 2007
© 2007 Foundry Networks, Inc.
25-11
Foundry EdgeIron User Guide
USING THE CLI
map ip precedence (Global Configuration)
Use this command to enable IP precedence mapping (i.e., IP Type of Service). Use the no form to
disable IP precedence mapping.
Syntax
[no] map ip precedence
Default Setting
Disabled
Command Mode
Global Configuration
Command Usage
• The precedence for priority mapping is IP Precedence or IP DSCP, and default switchport priority.
• IP Precedence and IP DSCP cannot both be enabled. Enabling one of these priority types will
automatically disable the other type.
Example
The following example shows how to enable IP precedence mapping globally:
Console(config)#map ip precedence
Console(config)#
map ip precedence (Interface Configuration)
Use this command to set IP precedence priority (i.e., IP Type of Service priority). Use the no form to
restore the default table.
Syntax
map ip precedence ip-precedence-value cos cos-value
no map ip precedence
• precedence-value - 3-bit precedence value. (Range: 0-7)
• cos-value - Class-of-Service value (Range: 0-7)
25-12
© 2007 Foundry Networks, Inc.
March 2007
Class of Service
Default Setting
The list below shows the default priority mapping.
IP Precedence Value
CoS Value
0
0
1
1
2
2
3
3
4
4
5
5
6
6
7
7
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
• The precedence for priority mapping is IP Precedence or IP DSCP, and default switchport priority.
• IP Precedence values are mapped to default Class of Service values on a one-to-one basis
according to recommendations in the IEEE 802.1p standard, and then mapped to the queue
defaults.
• This command sets the IP Precedence for all interfaces.
Example
The following example shows how to map IP precedence value 1 to CoS value 0:
Console(config)#interface ethernet 1/5
Console(config-if)#map ip precedence 1 cos 0
Console(config-if)#
December 2007
© 2007 Foundry Networks, Inc.
25-13
Foundry EdgeIron User Guide
Mapping DSCP Priority
The DSCP is six bits wide, allowing coding for up to 64 different forwarding behaviors. The DSCP
replaces the ToS bits, and it retains backward compatibility with the three precedence bits so that
non-DSCP compliant, ToS-enabled devices, will not conflict with the DSCP mapping. Based on
network policies, different kinds of traffic can be marked for different kinds of forwarding. The DSCP
default values are defined in the following table. Note that all the DSCP values that are not specified
are mapped to CoS value 0.
IP DSCP Value
CoS Value
0
0
8
1
10, 12, 14, 16
2
18, 20, 22, 24
3
26, 28, 30, 32, 34, 36
4
38, 40, 42
5
48
6
46, 56
7
USING THE WEB INTERFACE
Click Priority, IP DSCP Priority. Select a DSCP priority value from the DSCP Priority Table by clicking
on it with your cursor, enter a value in the Class of Service Value field, and then click Apply. Be sure
to also select IP DSCP from the IP Precedence/DSCP Priority Status menu.
25-14
•
DSCP Priority Table – Shows the DSCP Priority to CoS map.
•
Class of Service Value – Maps a CoS value to the selected DSCP Priority value. Note that “0”
represents low priority and “7” represent high priority.
© 2007 Foundry Networks, Inc.
March 2007
Class of Service
USING THE CLI
map ip dscp (Global Configuration)
Use this command to enable IP DSCP mapping (i.e., Differentiated Services Code Point mapping).
Use the no form to disable IP DSCP mapping.
Syntax
[no] map ip dscp
Default Setting
Disabled
Command Mode
Global Configuration
Command Usage
• The precedence for priority mapping is IP Precedence or IP DSCP, and default switchport priority.
• IP Precedence and IP DSCP cannot both be enabled. Enabling one of these priority types will
automatically disable the other type.
Example
The following example shows how to enable IP DSCP mapping globally:
Console(config)#map ip dscp
Console(config)#
map ip dscp (Interface Configuration)
Use this command to set IP DSCP priority (i.e., Differentiated Services Code Point priority). Use the
no form to restore the default table.
Syntax
map ip dscp dscp-value cos cos-value
no map ip dscp
• dscp-value - 8-bit DSCP value. (Range: 0-255)
• cos-value - Class-of-Service value (Range: 0-7)
December 2007
© 2007 Foundry Networks, Inc.
25-15
Foundry EdgeIron User Guide
Default Setting
The list below shows the default priority mapping. Note that all the DSCP values that are not
specified are mapped to CoS value 0.
IP DSCP Value
CoS Value
0
0
8
1
10, 12, 14, 16
2
18, 20, 22, 24
3
26, 28, 30, 32, 34, 36
4
38, 40, 42
5
48
6
46, 56
7
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
• The precedence for priority mapping is IP Port, IP Precedence or IP DSCP, and default switchport
priority.
• DSCP priority values are mapped to default Class of Service values according to
recommendations in the IEEE 802.1p standard, and then mapped to the queue defaults.
• This command sets the DSCP Priority for all interfaces.
Example
The following example shows how to map IP DSCP value 1 to CoS value 0:
Console(config)#interface ethernet 1/5
Console(config-if)#map ip dscp 1 cos 0
Console(config-if)#
25-16
© 2007 Foundry Networks, Inc.
March 2007
Class of Service
Mapping IP Port Priority
You can also map network applications to Class of Service values based on the IP port number (i.e.,
TCP/UDP port number) in the frame header. Some of the more common TCP service ports include:
HTTP: 80, FTP: 21, Telnet: 23 and POP3: 110.
USING THE WEB INTERFACE
Click Priority, IP Port Priority Status. Set IP Port Priority Status to Enabled.
Click Priority, IP Port Priority. Enter the port number for a network application in the IP Port Number
box and the new CoS value in the Class of Service box, and then click Add IP Port.
•
IP Port Priority Global Status – Enables or disables the IP port priority.
•
IP Port Priority Table – Shows the IP port to CoS map.
•
IP Port Number (TCP/UDP) – Set a new IP port number.
•
Class of Service Value – Sets a CoS value for a new IP port. Note that “0” represents low priority
and “7” represent high priority.
Note: CoS priority mappings are configured per-port. However, due to a hardware limitations all
mappings are applied system-wide. In other words, no matter which port is set for CoS mapping, it’s
applies globally to all ports.
December 2007
© 2007 Foundry Networks, Inc.
25-17
Foundry EdgeIron User Guide
USING THE CLI
map ip port (Global Configuration)
Use this command to enable IP port mapping (i.e., class of service mapping for TCP/UDP sockets).
Use the no form to disable IP port mapping.
Syntax
map ip port
no map ip port
Default Setting
Disabled
Command Mode
Global Configuration
Command Usage
• The precedence for priority mapping is IP Port, IP Precedence or IP DSCP, and default switchport
priority.
Note: Mapping specific values for IP Port Priority is implemented as an interface configuration
command, but any changes will apply to the all interfaces on the switch.
Example
The following example shows how to enable TCP/UDP port mapping globally:
Console(config)#map ip port
Console(config)#
map ip port (Interface Configuration)
Use this command to set IP port priority (i.e., TCP/UDP port priority). Use the no form to remove a
specific setting.
Syntax
map ip port port-number cos cos-value
no map ip port port-number
• port-number - 16-bit TCP port number. (Range: 0-65535)
• cos-value - Class-of-Service value (Range: 0-7)
Default Setting
None
Command Mode
Interface Configuration (Ethernet, Port Channel)
Command Usage
• The precedence for priority mapping is IP Port, IP Precedence or IP DSCP, and default switchport
priority.
• This command sets the IP port priority for all interfaces.
25-18
© 2007 Foundry Networks, Inc.
March 2007
Class of Service
Example
The following example shows how to map HTTP traffic to CoS value 0:
Console(config)#interface ethernet 1/5
Console(config-if)#map ip port 80 cos 0
Console(config-if)#
show map ip precedence
Use this command to show the IP precedence priority map.
Syntax
show map ip precedence [interface]
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
Default Setting
None
Command Mode
Privileged Exec
Example
Console#show map ip precedence ethernet 1/5
Precedence mapping status: disabled
Port
Precedence COS
--------- ---------- --Eth 1/ 5
0
0
Eth 1/ 5
1
1
Eth 1/ 5
2
2
Eth 1/ 5
3
3
Eth 1/ 5
4
4
Eth 1/ 5
5
5
Eth 1/ 5
6
6
Eth 1/ 5
7
7
Console#
Related Commands
map ip precedence (Global Configuration) (25-12)
map ip precedence (Interface Configuration) (25-12)
December 2007
© 2007 Foundry Networks, Inc.
25-19
Foundry EdgeIron User Guide
show map ip dscp
Use this command to show the IP DSCP priority map.
Syntax
show map ip dscp [interface]
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
Default Setting
None
Command Mode
Privileged Exec
Example
Console#show map ip dscp ethernet 1/1
DSCP mapping status: disabled
Port
DSCP COS
--------- ---- --Eth 1/ 1
0
0
Eth 1/ 1
1
0
Eth 1/ 1
2
0
Eth 1/ 1
3
0
.
.
.
Eth 1/ 1
Eth 1/ 1
Console#
62
63
0
0
Related Commands
map ip dscp (Global Configuration) (25-15)
map ip dscp (Interface Configuration) (25-15)
show map ip port
Use this command to show the IP port priority map.
Syntax
show map ip port [interface]
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
Default Setting
None
25-20
© 2007 Foundry Networks, Inc.
March 2007
Class of Service
Command Mode
Privileged Exec
Example
The following shows that HTTP traffic has been mapped to CoS value 0:
Console#show map ip port
TCP port mapping status: disabled
Port
Port no. COS
--------- -------- --Eth 1/ 5
80
0
Console#
Related Commands
map ip port (Global Configuration) (25-18)
map ip port (Interface Configuration) (25-18)
Mapping CoS Values to ACLs
Use the ACL CoS Mapping page to set the output queue for packets matching an ACL rule as shown
in the following table. Note that the specified CoS value is only used to map the matching packet to
an output queue; it is not written to the packet itself. For information on mapping the CoS values to
output queues, see “Mapping CoS Values to Egress Queues” on page 25-4.
Priority
CoS Value
0
0
8
1
10, 12, 14, 16
2
18, 20, 22, 24
3
26, 28, 30, 32, 34, 36
4
38, 40, 42
5
48
6
46, 56
7
Command Usage
You must configure an ACL mask before you can map CoS values to the rule.
December 2007
© 2007 Foundry Networks, Inc.
25-21
Foundry EdgeIron User Guide
USING THE WEB INTERFACE
Click Priority, ACL CoS Priority. Select a port, select an ACL rule, specify a CoS priority, then click
Add.
•
Port – Selects the port to which the ACL CoS is configured on.
•
Name, Type – Not presently implemented.
•
CoS Priority – Enables the CoS priority value level.
•
Add – Adds the specified information to the port.
•
ACL CoS Priority Mapping – Displays the configured information.
* For information on configuring ACLs, see “Access Control Lists” on page 19-1.
25-22
© 2007 Foundry Networks, Inc.
March 2007
Class of Service
USING THE CLI
map access-list ip
This command sets the output queue for packets matching an ACL rule. The specified CoS value is
only used to map the matching packet to an output queue; it is not written to the packet itself. Use the
no form to remove the CoS mapping.
Syntax
[no] map access-list ip acl_name cos cos-value
• acl_name – Name of the ACL. (Maximum length: 16 characters)
• cos-value – CoS value. (Range: 0-7)
Default Setting
None
Command Mode
Interface Configuration (Ethernet)
Command Usage
• You must configure an ACL mask before you can map CoS values to the rule.
• A packet matching a rule within the specified ACL is mapped to one of the output queues as
shown in the following table. For information on mapping the CoS values to output queues, see
queue cos-map (25-7).
EdgeIron 24G-A, 48G, 24GS, 48GS, 8X10G
Priority
1
2
4
6
8
10
12
14
Queue
0
1
2
3
4
5
6
7
EdgeIron 4802CF, 2402CF
Priority
1
4
16
64
Queue
0
1
2
3
Example
Console(config)#interface ethernet 1/25
Console(config-if)#map access-list ip bill cos 0
Console(config-if)#
Related Commands
queue cos-map (25-7)
show map access-list ip (25-24)
December 2007
© 2007 Foundry Networks, Inc.
25-23
Foundry EdgeIron User Guide
show map access-list ip
This command shows the CoS value mapped to an IP ACL for the current interface. (The CoS value
determines the output queue for packets matching an ACL rule.)
Syntax
show map access-list ip [interface]
interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
Command Mode
Privileged Exec
Example
Console#show map access-list ip
Access-list to COS of Eth 1/24
Access-list ALS1 cos 0
Console#
Related Commands
map access-list ip (25-23)
Changing Priorities Based on ACL Rules
You can change traffic priorities for frames matching the defined ACL rule. (This feature is commonly
referred to as ACL packet marking.) This switch can change the IEEE 802.1p priority, IP
Precedence, or DSCP Priority of IP frames; or change the IEEE 802.1p priority of Layer 2 frames.
(This feature is commonly referred to as ACL packet marking.) Use the no form to remove the ACL
marker.
Command Usage
• You must configure an ACL mask before you can change priorities based on a rule.
25-24
•
Traffic priorities may be included in the IEEE 802.1p priority tag. This tag is also incorporated as
part of the overall IEEE 802.1Q VLAN tag. The 802.1p priority may be set for either Layer 2 or IP
frames.
•
The IP frame header also includes priority bits in the Type of Service (ToS) octet. The Type of
Service octet may contain three bits for IP Precedence or six bits for Differentiated Services Code
Point (DSCP) service. Note that the IP frame header can include either the IP Precedence or
DSCP priority type.
•
The precedence for priority mapping by this switch is IP Precedence or DSCP Priority, and then
802.1p priority.
© 2007 Foundry Networks, Inc.
March 2007
Class of Service
USING THE WEB INTERFACE
Click Priority, ACL Marker. Select a port and an ACL rule. To specify a ToS priority, mark the
Precedence/DSCP check box, select Precedence or DSCP from the scroll-down box, and enter a
priority. To specify an 802.1p priority, mark the 802.1p Priority check box, and enter a priority. Then
click Add.
•
Port – Port identifier.
•
Name* – Name of ACL.
•
Type – Type of ACL (IP or MAC).
•
Precedence – IP Precedence value. (Range: 0-7)
•
DSCP – Differentiated Services Code Point value. (Range: 0-63)
•
802.1p Priority – Class of Service value in the IEEE 802.1p priority tag.
(Range: 0-7; 7 is the highest priority)
USING THE CLI
match access-list ip
This command changes the IEEE 802.1p priority, IP Precedence, or DSCP Priority of a frame
matching the defined ACL rule. (This feature is commonly referred to as ACL packet marking.) Use
the no form to remove the ACL marker.
Syntax
match access-list ip acl_name [set priority priority] {set tos tos_value | set dscp dscp_value}
no match access-list ip acl_name
• acl_name – Name of the ACL. (Maximum length: 16 characters)
• priority – Class of Service value in the IEEE 802.1p priority tag. (Range: 0-7; 7 is the highest
priority)
• tos_value – IP Precedence value. (Range: 0-7)
• dscp_value – Differentiated Services Code Point value. (Range: 0-63)
December 2007
© 2007 Foundry Networks, Inc.
25-25
Foundry EdgeIron User Guide
Default Setting
None
Command Mode
Interface Configuration (Ethernet)
Command Usage
• You must configure an ACL mask before you can change frame priorities based on an ACL rule.
• Traffic priorities may be included in the IEEE 802.1p priority tag. This tag is also incorporated as
part of the overall IEEE 802.1Q VLAN tag. To specify this priority, use the set priority keywords.
• The IP frame header also includes priority bits in the Type of Service (ToS) octet. The Type of
Service octet may contain three bits for IP Precedence or six bits for Differentiated Services Code
Point (DSCP) service. To specify the IP precedence priority, use the set tos keywords. To specify
the DSCP priority, use the set dscp keywords. Note that the IP frame header can include either
the IP Precedence or DSCP priority type.
• The precedence for priority mapping by this switch is IP Precedence or DSCP Priority, and then
802.1p priority.
Example
Console(config)#interface ethernet 1/12
Console(config-if)#match access-list ip bill set dscp 0
Console(config-if)#
Related Commands
show marking (25-26)
show marking
This command displays the current configuration for packet marking.
Command Mode
Privileged Exec
Example
Console#show marking
Interface ethernet 1/12
match access-list IP bill set DSCP 0
match access-list MAC a set priority 0
Console#
Related Commands
match access-list ip (25-25)
25-26
© 2007 Foundry Networks, Inc.
March 2007
Chapter 26
Multicast Configuration
Multicasting is used to support real-time applications such as video conferencing or streaming audio.
A multicast server does not have to establish a separate connection with each client. It merely
broadcasts its service to the network, and any hosts that want to receive the multicast register with
their local multicast switch/router. Although this approach reduces the network overhead required by
a multicast server, the broadcast traffic must be carefully pruned at every multicast switch/router it
passes through to ensure that traffic is only passed on the hosts which subscribed to this service.
This switch uses IGMP (Internet Group Management Protocol) to query for any attached hosts that
want to receive a specific multicast service. It identifies the ports containing hosts requesting to join
the service and sends data out to those ports only. It then propagates the service request up to any
neighboring multicast switch/router to ensure that it will continue to receive the multicast service.
This procedure is called multicast filtering.
The purpose of IP multicast filtering is to optimize a switched network’s performance, so multicast
packets will only be forwarded to those ports containing multicast group hosts or multicast
routers/switches, instead of flooding traffic to all ports in the subnet (VLAN).
The CLI commands for this section are briefly described in the table that follows:
Command
Function
Mode
Page
ip igmp snooping
Enables IGMP snooping
GC
26-4
ip igmp snooping vlan static
Adds an interface as a member of a multicast group
GC
26-4
ip igmp snooping version
Configures the IGMP version for snooping
GC
26-5
show ip igmp snooping
Shows the IGMP snooping configuration
PE
26-5
show bridge multicast
Shows the IGMP snooping MAC multicast list
PE
26-6
ip igmp snooping querier
Allows this device to act as the querier for IGMP
snooping
GC
26-6
ip igmp snooping query-count
Configures the query count
GC
26-7
GC
26-7
Basic IGMP Commands
IGMP Querier Commands
ip igmp snooping query-interval Configures the query interval
December 2007
© 2007 Foundry Networks, Inc.
26-1
Foundry EdgeIron User Guide
Command
Function
Mode
Page
ip igmp snooping query-maxresponsetime
Configures the report delay
GC
26-8
ip igmp snooping router-portexpire-time
Configures the query timeout
GC
26-8
switchport multicast packet-rate to limit the amount of multicast packets received on a
port or trunk
IC
26-10
ip igmp snooping vlan mrouter
Adds a multicast router port
GC
26-11
show ip igmp snooping mrouter
Shows multicast router ports
PE
26-11
show vsrp aware
Displays VSRP information
PE
5-31
vsrp aware
Enables VSRP
GC
5-31
Multicast Router Commands
VSRP Commands
Configuring IGMP Parameters
You can configure the switch to forward multicast traffic intelligently. Based on the IGMP query and
report messages, the switch forwards traffic only to the ports that request multicast traffic. This
prevents the switch from broadcasting the traffic to all ports and possibly disrupting network
performance.
Command Usage
• IGMP Snooping – This switch can passively snoop on IGMP Query and Report packets
transferred between IP multicast routers/switches and IP multicast host groups to identify the IP
multicast group members. It simply monitors the IGMP packets passing through it, picks out the
group registration information, and configures multicast filters accordingly.
•
IGMP Query – A router, or multicast-enabled switch, can periodically ask their hosts if they want
to receive multicast traffic. If there is more than one router/switch on the LAN performing IP
multicasting, one of these devices is elected “querier” and assumes the role of querying the LAN
for group members. It then propagates the service requests on to any adjacent multicast
switch/router to ensure that it will continue to receive the multicast service.
Note: Multicast routers use this information, along with a multicast routing protocol such as DVMRP
or PIM, to support IP multicasting across the Internet.
26-2
© 2007 Foundry Networks, Inc.
March 2007
Multicast Configuration
USING THE WEB INTERFACE
Click IGMP, IGMP Configuration. Adjust the IGMP settings as required, and then click Apply.
•
IGMP Status – When enabled, the switch will monitor network traffic to determine which hosts
want to receive multicast traffic. This is also referred to as IGMP Snooping. (Default: Disabled)
•
Act as IGMP Querier – When enabled, the switch can serve as the Querier, which is responsible
for asking hosts if they want to receive multicast traffic. (Default: Disabled)
•
IGMP Query Count – Sets the maximum number of queries issued for which there has been no
response before the switch takes action to drop a client from the multicast group.
(Default: 2, Range: 2 - 10)
•
IGMP Query Interval – Sets the frequency (in seconds) at which the switch sends IGMP hostquery messages. (Default: 125, Range: 60 - 125)
•
IGMP Report Delay – Sets the time (in seconds) between receiving an IGMP Report for an IP
multicast address on a port before the switch sends an IGMP Query out of that port and removes
the entry from its list. (Default: 10, Range: 5 - 30)
•
Query Timeout – The time the switch waits after the previous querier stops before it considers
the router port (i.e., the interface which had been receiving query packets) to have expired.
(Default: 300 seconds, Range: 300 - 500)
•
IGMP Version – Sets the protocol version for compatibility with other devices on the network.
(Default: 2, Range: 1 - 2)
Notes: 1. All systems on the subnet must support the same version.
2. Some attributes are only enabled for IGMPv2, including IGMP Report Delay and IGMP
Query Timeout.
December 2007
© 2007 Foundry Networks, Inc.
26-3
Foundry EdgeIron User Guide
USING THE CLI
ip igmp snooping
Use this command to enable IGMP snooping on this switch. Use the no form to disable it.
Syntax
[no] ip igmp snooping
Default Setting
Enabled
Command Mode
Global Configuration
Example
The following example enables IGMP snooping.
Console(config)#ip igmp snooping
Console(config)#
ip igmp snooping vlan static
Use this command to add a port to a multicast group. Use the no form to remove the port.
Syntax
[no] ip igmp snooping vlan vlan-id static ip-address interface
• vlan-id - VLAN ID (Range: 1-4094)
• ip-address - IP address for multicast group
• interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
Default Setting
None
Command Mode
Global Configuration
Example
The following shows how to statically configure a multicast group on a port:
Console(config)#ip igmp snooping vlan 1 static 224.0.0.12 ethernet 1/5
Console(config)#
26-4
© 2007 Foundry Networks, Inc.
March 2007
Multicast Configuration
ip igmp snooping version
Use this command to configure the IGMP snooping version. Use the no form to restore the default.
Syntax
ip igmp snooping version {1 | 2}
no ip igmp snooping version
• 1 - IGMP Version 1
• 2 - IGMP Version 2
Default Setting
IGMP Version 2
Command Mode
Global Configuration
Command Usage
• All systems on the subnet must support the same version. If there are legacy devices in your
network that only support Version 1, you will also have to configure this switch to use Version 1.
• Some commands are only enabled for IGMPv2, including ip igmp query-max-response-time
and ip igmp router-port-expire-time.
Example
The following configures the switch to use IGMP Version 1:
Console(config)#ip igmp snooping version 1
Console(config)#
show ip igmp snooping
Use this command to show the IGMP snooping configuration.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
See “Configuring IGMP Parameters” on page 26-2 for a description of the displayed items.
Example
The following shows the current IGMP snooping configuration:
Console#show ip igmp snooping
Service status: Enabled
Querier status: Enabled
Query count: 2
Query interval: 125 sec
Query max response time: 10 sec
Query time-out: 300 sec
IGMP snooping version: Version 2
Console#
December 2007
© 2007 Foundry Networks, Inc.
26-5
Foundry EdgeIron User Guide
show mac-address-table multicast
Use this command to show known multicast addresses.
Syntax
show mac-address-table multicast [vlan vlan-id] [user | igmp-snooping]
• vlan-id - VLAN ID (1 to 4094)
• user - Display only the user-configured multicast entries.
• igmp-snooping - Display only entries learned through IGMP snooping.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
Member types displayed include IGMP or USER, depending on selected options.
Example
The following shows the multicast entries learned through IGMP snooping for VLAN 1:
Console#show mac-address-table multicast vlan 1 igmp-snooping
VLAN
M'cast IP addr. Member ports
Type
------------------ -----------------1
224.1.2.3
Eth1/11
IGMP
Console#
IGMP Querier Commands
ip igmp snooping querier
Use this command to enable the switch as an IGMP snooping querier. Use the no form to disable it.
Syntax
[no] ip igmp snooping querier
Default Setting
Enabled
Command Mode
Global Configuration
Command Usage
If enabled, the switch will serve as querier if elected. The querier is responsible for asking hosts
if they want to receive multicast traffic.
Example
Console(config)#ip igmp snooping querier
Console(config)#
26-6
© 2007 Foundry Networks, Inc.
March 2007
Multicast Configuration
ip igmp snooping query-count
Use this command to configure the query count. Use the no form to restore the default.
Syntax
ip igmp snooping query-count count
no ip igmp snooping query-count
count - The maximum number of queries issued for which there has been no response
before the switch takes action to solicit reports. (Range: 2-10)
Default Setting
2 times
Command Mode
Global Configuration
Command Usage
The query count defines how long the querier waits for a response from a multicast client before
taking action. If a querier has sent a number of queries defined by this command, but a client has
not responded, a countdown timer is started using the time defined by ip igmp snooping querymax-response-time. If the countdown finishes, and the client still has not responded, then that
client is considered to have left the multicast group.
Example
The following shows how to configure the query count to 10:
Console(config)#ip igmp snooping query-count 10
Console(config)#
ip igmp snooping query-interval
Use this command to configure the snooping query interval. Use the no form to restore the default.
Syntax
ip igmp snooping query-interval seconds
no ip igmp snooping query-interval
seconds - The frequency at which the switch sends IGMP host-query messages.
(Range: 60-125)
Default Setting
125 seconds
Command Mode
Global Configuration
Example
The following shows how to configure the query interval to 100 seconds:
Console(config)#ip igmp snooping query-interval 100
Console(config)#
December 2007
© 2007 Foundry Networks, Inc.
26-7
Foundry EdgeIron User Guide
ip igmp snooping query-max-response-time
Use this command to configure the snooping report delay. Use the no form of this command to
restore the default.
Syntax
ip igmp snooping query-max-response-time seconds
no ip igmp snooping query-max-response-time
seconds - The report delay advertised in IGMP queries. (Range: 5-30)
Default Setting
10 seconds
Command Mode
Global Configuration
Command Usage
• The switch must be using IGMPv2 for this command to take effect.
• This command defines the time after a query, during which a response is expected from a
multicast client. If a querier has sent a number of queries defined by the ip igmp snooping querycount, but a client has not responded, a countdown timer is started using an initial value set by
this command. If the countdown finishes, and the client still has not responded, then that client is
considered to have left the multicast group.
Example
The following shows how to configure the maximum response time to 20 seconds.
Console(config)#ip igmp snooping query-max-response-time 20
Console(config)#
Related Commands
ip igmp snooping version (26-5)
ip igmp snooping router-port-expire-time
Use this command to configure the snooping query-timeout. Use the no form of this command to
restore the default.
Syntax
ip igmp snooping router-port-expire-time seconds
no ip igmp snooping router-port-expire-time
seconds - The time the switch waits after the previous querier stops before it considers the
router port (i.e., the interface which had been receiving query packets) to have expired.
(Range: 300-500)
Default Setting
300 seconds
Command Mode
Global Configuration
26-8
© 2007 Foundry Networks, Inc.
March 2007
Multicast Configuration
Command Usage
The switch must be using IGMPv2 for this command to take effect.
Example
The following shows how to configure the default timeout to 300 seconds:
Console(config)#ip igmp snooping router-port-expire-time 300
Console(config)#
Related Commands
ip igmp snooping version (26-5)
Interfaces Attached to a Multicast Router
Multicast routers use the information obtained from IGMP Query, along with a multicast routing
protocol such as DVMRP, to support IP multicasting across the Internet. These routers may be
dynamically discovered by the switch or statically assigned to an interface on the switch.
USING THE WEB INTERFACE
You can use the Multicast Router Port Information page to display the ports on this switch attached
to a neighboring multicast router/switch for each VLAN ID.
Click IGMP, Multicast Router Port Information. Select the required VLAN ID from the scroll-down list
to display the associated multicast routers.
•
VLAN ID – ID of configured VLAN (1-4094).
•
Multicast Router List – Multicast routers dynamically discovered by this switch or those that are
statically assigned to an interface on this switch.
USING THE CLI
See “Specifying Interfaces Attached to a Multicast Router” on page 26-10.
December 2007
© 2007 Foundry Networks, Inc.
26-9
Foundry EdgeIron User Guide
Specifying Interfaces Attached to a Multicast Router
Depending on your network connections, IGMP snooping may not always be able to locate the IGMP
querier. Therefore, if the IGMP querier is a known multicast router/switch connected over the
network to an interface (port or trunk) on your switch, you can manually configure that interface to
join all the current multicast groups. This can ensure that multicast traffic is passed to all the
appropriate interfaces within the switch.
USING THE WEB INTERFACE
Click IGMP, Static Multicast Router Port Configuration. Specify the interfaces attached to a multicast
router, indicate the VLAN which will forward all the corresponding multicast traffic, and then click
Add. After you have completed adding interfaces to the list, click Apply.
•
Interface – Activates the Port or Trunk scroll down list.
•
VLAN ID – Selects the VLAN to propagate all multicast traffic coming from the attached multicast
router/switch.
•
Port or Trunk – Specifies the interface attached to a multicast router.
USING THE CLI
switchport multicast packet-rate
Use this command to limit the amount of multicast packets received on a port or trunk. Use the no
form of this command to disable this function.
Syntax
switchport multicast packet-rate rate-level
no switchport multicast
rate-level - 500-262143 packets per second.
Default Setting
Disabled
Command Mode
Interface Configuration (Ethernet)
26-10
© 2007 Foundry Networks, Inc.
March 2007
Multicast Configuration
Example
This example limits the multicast packet level to 3000 packets per second.
Console(config)#interface ethernet 1/9
Console(config-if)#switchport multicast packet-rate 3000
Console(config-if)#
ip igmp snooping vlan mrouter
Use this command to statically configure a multicast router port. Use the no form to remove the
configuration.
Syntax
[no] ip igmp snooping vlan vlan-id mrouter interface
• vlan-id - VLAN ID (Range: 1-4094)
• interface
• ethernet unit/port
- unit - This is device 1.
- port - Port number.
• port-channel channel-id (Range: 1-6)
Default Setting
No static multicast router ports are configured.
Command Mode
Global Configuration
Command Usage
Depending on your network connections, IGMP snooping may not always be able to locate the
IGMP querier. Therefore, if the IGMP querier is a known multicast router/switch connected over
the network to an interface (port or trunk) on your switch, you can manually configure that
interface to join all the current multicast groups.
Example
The following shows how to configure port 11 as a multicast router port within VLAN 1:
Console(config)#ip igmp snooping vlan 1 mrouter ethernet 1/11
Console(config)#
show ip igmp snooping mrouter
Use this command to display information on statically configured and dynamically learned multicast
router ports.
Syntax
show ip igmp snooping mrouter [vlan vlan-id]
vlan-id - VLAN ID (Range: 1-4094)
December 2007
© 2007 Foundry Networks, Inc.
26-11
Foundry EdgeIron User Guide
Default Setting
Displays multicast router ports for all configured VLANs.
Command Mode
Privileged Exec
Command Usage
Multicast router port types displayed include Static or Dynamic.
Example
The following shows the port in VLAN 1 that is attached to a multicast router:
Console#show ip igmp snooping mrouter vlan 1
VLAN
M'cast Router Ports Type
---------------------- ------1
Eth 1/11
Static
2
Eth 1/12
Dynamic
Console#
Displaying Port Members of Multicast Services
You can display the port members associated with a specified VLAN and multicast IP address.
USING THE WEB INTERFACE
Click IGMP, IP Multicast Registration Table. Select the VLAN ID and multicast IP address. The switch
will display all the ports that are propagating this multicast service.
•
VLAN ID – Selects the VLAN in which to display port members.
•
Multicast IP Address – The IP address for a specific multicast service
•
Multicast Group Port List – Ports propagating a multicast service; i.e., ports that belong to the
indicated VLAN group.
USING THE CLI
show mac-address-table multicast
Use this command to show known multicast addresses.
26-12
© 2007 Foundry Networks, Inc.
March 2007
Multicast Configuration
Syntax
show mac-address-table multicast [vlan vlan-id] [user | igmp-snooping]
• vlan-id - VLAN ID (1 to 4094)
• user - Display only the user-configured multicast entries.
• igmp-snooping - Display only entries learned through IGMP snooping.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
Member types displayed include IGMP or USER, depending on selected options.
Example
The following shows the multicast entries learned through IGMP snooping for VLAN 1:
Console#show mac-address-table multicast vlan 1 igmp-snooping
VLAN
M'cast IP addr. Member ports
Type
------------------ -----------------1
224.1.2.3
Eth1/11
IGMP
Console#
Adding Multicast Addresses to VLANs
Multicast filtering can be dynamically configured using IGMP Snooping and IGMP Query messages
as described in “Configuring IGMP Parameters” on page 26-2. For certain application that require
tighter control, you may need to statically configure a multicast service on the switch. First add all the
ports attached to participating hosts to a common VLAN, and then assign the multicast service to
that VLAN group.
Command Usage
• Static multicast addresses are never aged out.
•
When a multicast address is assigned to specific VLAN, the corresponding traffic can only be
forwarded to ports within that VLAN.
USING THE WEB INTERFACE
Click IGMP, IGMP Member Port Table. Specify the interface attached to a multicast service (via an
IGMP-enabled switch or multicast router), indicate the VLAN that will propagate the multicast
December 2007
© 2007 Foundry Networks, Inc.
26-13
Foundry EdgeIron User Guide
service, specify the multicast IP address, and then click Add. After you have completed adding ports
to the member list, click Apply.
•
Interface – Activates the Port or Trunk scroll down list.
•
VLAN ID – Selects the VLAN to propagate all multicast traffic coming from the attached multicast
router/switch.
•
Multicast IP – The IP address for a specific multicast service
•
Port or Trunk – Specifies the interface attached to a multicast router.
USING THE CLI
See “ip igmp snooping vlan static” on page 26-4.
26-14
© 2007 Foundry Networks, Inc.
March 2007
Chapter 27
Stacking Technology
Operational Concepts
EdgeIron 24GS or 48GS switches can be stacked together as described in the Foundry EdgeIron
Series Installation and Basic Configuration Guide. The stack functions as an integral system for easy
management through a common interface. It provides robust and reliable operation through a
centralized stacking topology in which one unit in the stack acts as the Master for configuration tasks
and firmware upgrade. All of the other units function in Slave mode, but can automatically take over
management of the stack if the Master unit fails.
For management purposes, the stack functions as single integrated system. The Master Unit
represents the whole stack for all of the normal configuration tasks, and can be accessed through
any port (on any switch in the stack) that is assigned to the management VLAN. This allows you to
use a single IP address to manage every unit in the stack. The Master unit processes each
management request and forwards information on the required task to the slave units for completion.
The EdgeIron 24GS or 48GS have two fixed stacking ports on the rear panel (i.e., one uplink port
and one downlink port). Each stacking port operates up to 10 Gbps each way in full duplex mode,
supporting a bandwidth of up to 20 Gbps, or a total stacking bandwidth of up to 40 Gbps when traffic
is flowing between two different source-destination pairs on each of the stacking ports. Note however
that overhead will have an impact on the throughput.
EdgeIron 24GS or EdgeIron 48GS can be stacked together, but the number of units you can have in
a stack depends on whether or not a 10GBASE module is installed in the units. Table 26.1 and Table
26.2 show the number of units permitted in a stack. If no optional 10GBASE modules are installed on
the units, then you can stack up to eight 24GS or eight 48GS units
December 2007
© 2007 Foundry Networks, Inc.
27-1
Foundry EdgeIron User Guide
Number of Stacking Units Without 10GBASE module Permitted in a Stack
Number of Units
in a Stack
Number of 10GBASE
modules in a Stack
1
Permitted
24GS
48GS
0
Yes
Yes
2
0
Yes
Yes
3
0
Yes
Yes
4
0
Yes
Yes
5
0
Yes
Yes
6
0
Yes
Yes
7
0
Yes
Yes
8
0
Yes
Yes
However, if you install a 10GBASE module in the units, you can have up to eight 24GS in a stack, but
only six 48GS in a stack.
Number of Stacking Units With 10GBASE module Permitted in a Stack
Number of Units
in a Stack
Number of 10GBASE
modules in a Stack
1
Permitted
24GS
48GS
1
Yes
Yes
2
2
Yes
Yes
3
3
Yes
Yes
4
4
Yes
Yes
5
5
Yes
Yes
6
6
Yes
Yes
7
7
Yes
No
8
8
Yes
No
Functionalities
When the stack is powered on (i.e., via either a cold start or software reset), each unit in the system
initiates the normal boot process. After the system completes the boot-up process, one unit in the
stack will be elected as the stack master, and the remaining units will operate in slave mode. The
stack master will manage the entire stack as a single entity via a single management IP address.
When any switch in the stack fails, the remaining switches will remain operational and isolate the
failed switch so that the only ports affected by the failure are on the failed switch.
27-2
© 2007 Foundry Networks, Inc.
March 2007
Stacking Technology
In a looped stack, the failure of one stack unit or cable will cause the stack topology to change.
However, after topology discovery completes and the system re-initiated, the stack will still operate
as a single stack.
In a non-looped stack, the failure of one stack unit or cable will cause the stack to be broken in two.
The Stack link LED on the unit that is no longer receiving traffic from the next unit up in the stack will
begin flashing to indicate that the stack link is broken. When the stack fails, a Master unit is selected
from the two stack segments, either the unit with the Master button depressed, or the unit with the
lowest MAC address if the Master button is not depressed on any unit. The stack reboots and
resumes normal operations. However, note that the IP address will be the same for both of the stack
segments. To resolve the conflicting IP addresses, you should manually replace the failed link or unit
as soon as possible.
Up
Up
Dow
Dow
n
Up
n
Up
Dow
Dow
n
Up
n
Up
Dow
Dow
n
Up
n
Up
Dow
Dow
n
n
non-looped topology stack
looped topology stack
Regardless of the stacking topology in use, if a unit fails, it will be isolated from the stack. However, if
the stack fails because of a faulty stacking cable, the looped stack will continue to function the same
as before, after rediscovering the new topology.
The major functions of the stacking management subsystem include:
1. Create and initiate the stack.
•
Master election
•
Topology discovery
•
Auto-ID assignment
•
Auto-image download
•
System initiation
2. Monitor and maintain the stack operations.
•
System configuration database synchronization – To support the backup master function, the
following configuration data is synchronized to each slave unit in a stack:
-
December 2007
Unit ID table
© 2007 Foundry Networks, Inc.
27-3
Foundry EdgeIron User Guide
-
Management VLAN IP address table
-
System up time
-
Event log
•
Topology monitoring
•
Auto or manual firmware upgrade to slave units, including main board and optional module
3. Single management IP address.
4. Monitor stack for redundancy and reliability.
Create and Initiate a Stack
The stack management subsystem provides various functions to create and initiate the stack when it
is powered up. The stack can be created, initiated, and enter normal operation within two minutes.
Master Election
When the stack is powered up and completes the boot-up process, the Master unit is elected within
0.5 seconds. Master election may be based on Master preemptive mode, Master push button, or
MAC address.
The Master unit will enter non-preemptive mode if it has been elected for more than 20 seconds.
Master unit election is based on following rules:
1. If only one unit enters Master non-preemptive mode, it be elected as the Master unit.
2. If no unit is in Master non-preemptive mode or multiple units are in preemptive mode, Master
election rule will depend on the following rules:
- If there is only one unit with the Master push button depressed, that unit will be elected as the
Master. Otherwise Master election will depend on the MAC address as described in rule 4.
- The unit with smallest MAC address shall be elected as the Master unit.
Topology Discovery
Once the Master unit has been elected, it will use the following procedure to build up the stack
topology within 1 second:
1. Collect hardware configuration and board information for each unit in the stack.
2. Build up the topology database for the whole stack based on the hardware configuration and
board information of each discovered unit.
Hardware configuration and board information collected from each unit includes the following
information:
27-4
Main Board
Optional Module
Model number and description
Type and status
Firmware version
Firmware version
Hardware version
Hardware version
CPU version
CPU version
© 2007 Foundry Networks, Inc.
March 2007
Stacking Technology
Main Board
Optional Module
Model number and description
Type and status
MAC address
Serial number
Serial number
EPLD* version
EPLD* version
*Electrically Programmable Logic Device, an integrated circuit that is
comprised of an array of programmable logic devices that do not come preconnected; the connections are programmed electrically by the user.
Only the Master unit can perform Topology Discovery. After the stack is up and running, the Master
unit will be able to detect any stack topology changes. Adding or removing units, stack cable failure,
or unit failure will cause the stack topology the change.
Auto Unit-ID Assignment
The unit ID for each switch in the stack is numbered from 1 to 8. These IDs are used for system
configuration and other management functions. Only the master unit can assign a unit ID to the
switches in the stack. The master unit records each ID in the Unit ID Table. Each entry of Unit ID
table contains the switch’s MAC address and the assigned Unit ID.
After the stack topology table has been created, the Master unit uses the Topology Table and Unit ID
Table to assign unit IDs to each unit in the stack according to following rules:
Unit ID Assignment for a New Stack
The Master unit ID table for a new stack is empty, and the Master unit assigns unit IDs based on the
stack Topology Table. The master Unit ID table is then updated and saved into flash when Unit ID
assignment is completed.
The following rules are used for Unit ID assignment for both loopback stacking topology and nonloopback stacking topologies:
Loopback stacking topology
•
ID 1 is assigned to the Master unit.
•
ID 2 is assigned to the unit directly connected to the Master’s downlink stack port.
•
ID n is assigned to the unit chained to position n from the Master unit’s downlink stack port.
Non-loopback stacking topology
•
The unit ID of the Master unit depends on its position in the stack.
•
ID 1 is assigned to the top most unit in the stack. (This unit has no other unit connected on
its uplink stack port.)
•
ID 2 is assigned to the unit directly connected to the downlink stack port on unit 1.
•
ID n is assigned to the unit chained to position n from the unit 1 downlink stack port.
December 2007
© 2007 Foundry Networks, Inc.
27-5
Foundry EdgeIron User Guide
Unit ID Assignment for a Pre-existing Stack
The Master will assign a unit ID to each unit based on the Master Unit ID Table. The Unit ID Table will
be updated if a new unit is added to the stack. The Master unit maintains and updates the Unit ID
Table when Unit ID assignment is completed. The Master then saves the updated Unit ID Table into
its flash memory, and also writes the Unit ID table to each unit in the stack during the database
synchronization stage.
For a pre-existing unit that already has its MAC address recorded in the Master Unit ID table, the
associated Unit ID for this MAC address is reassigned to the unit.
For a newly added unit, the unit ID is assigned according to the following rules
•
Give the unit a re-cycled ID according to the stack topology table if the model number is same.
•
Otherwise,
-
Give the unit an un-used ID if one is available.
-Else, use any available re-cycled ID. (This implies that the newly added unit’s model number
is different from that of any re-cycled unit.)
Note: A re-cycled ID is one that was assigned to a unit that is not present in the current stack.
Stacking Error States
A maximum of 8 switches can be stacked together. If the total number of units in the stack exceeds
this number, the stack master will display a “Topology Error” message on the console and “E” on the
Master unit’s 7-segment LED. The whole stack will be non-operative until the “Topology Error” is
resolved.
If more than 32 switch ASIC chips are included in the stack, the stack Master will also display a
“Topology Error” message on console and “E” on the Master unit’s 7-segment LED. The whole stack
will be non-operative until the “Topology Error” is resolved. (Refer to “Operational Concepts” on page
27-1 for information on the number of switch ASICs included in each type of switch.)
Image Checking
The main board runtime firmware version for each unit in the stack must be the same as the Master
unit’s runtime firmware. After Auto-ID assignment is completed, the Master unit checks the image
versions for consistency. If the firmware versions (i.e., runtime code) configured for bootup on any
slave units are not the same as those on the Master Unit, the stack shall operate in Special Stacking
Mode as follows:
27-6
•
The Master Unit enters Normal Operation Mode alone.
•
The Master Unit will be able to see all units in the stack and maintain the stack topology.
•
All of the slave units will be non-operative (i.e., all ports disabled). All management
commands directed to slave units will be applied to the Master unit’s database instead.
•
No management commands will be sent to slave except for the following commands:
-
Provision complete command
-
Stack Topology command
-
Copy command
© 2007 Foundry Networks, Inc.
March 2007
Stacking Technology
-
Database synchronization command originated by the Master unit
System Initialization
After the image versions have been checked, if they are consistent, the system will be initiated into
Normal Stacking Mode. Otherwise, the system will be initiated into Special Stacking Mode.
System Initialization for Normal Operation Mode
The Master unit initiates the stack’s functions based on the system configuration settings specified in
the configuration file set to boot up the system.
If the boot configuration file is not available, the Master will use the latest configuration file (based on
the date of the configuration file) for system initialization. If there is no configuration file available, the
Master will use the system default configuration to initiate the stack.
Note: The file named “Factory_Default_Config.cfg” contains all the system default settings. If
the system is booted with this file, the Master unit will also create a file named “startup1.cfg” that
contains system settings for stack initialization, including information about the unit identifier, MAC
address, and installed module type for each unit the stack. The configuration settings from the
factory defaults configuration file are copied to this file, which is then used to boot the stack.
If the configuration file contains information (i.e., MAC address and unit ID) for units that appear in
Unit ID table, the system will apply these configuration settings to those units. For units that do not
have configuration information, the system will assign default configuration settings to them.
System Initialization for Special Stacking Mode
Only the Master unit will be initiated based on the boot configuration file as described under System
Initialization for Normal Operation Mode on the previous page. All of the slave units will remain nonoperative (i.e., all ports disabled).
Special Stacking Mode
After the system completes initialization, the stack Master will enter Special Stacking Mode within
two minutes if the image versions of the stack are inconsistent.
Image Download
In Special Stacking Mode, the Master unit displays warning messages whenever you log into the
system through the CLI, Telnet, or web interface to request that the runtime image be downloaded.
The administrator can also use the CLI, web, or SNMP command to download the runtime image
from the Master unit to other units in the stack.
Auto Image Download
The boot image of the Master unit will be automatically downloaded from the Master unit to all the
slave units. (This mode is set as the system default, and is not user configurable.)
The salve units will make enough space available in flash memory to guarantee that the received
image is successfully saved based on following rules:
•
Delete the second image file if it exists.
December 2007
© 2007 Foundry Networks, Inc.
27-7
Foundry EdgeIron User Guide
•
Otherwise, delete old configuration files (based on date). This may require deleting multiple
configurations files to get enough space.
After the image has been downloaded, the whole stack will be automatically rebooted with the new
image following this procedure:
•
The Master unit sends the “Set Next Boot File Command” to each slave unit.
•
The Master unit submits a “Global Reset Command” to each unit to reboot the whole stack.
Manual Image Download
The administrator can use the CLI, web, or SNMP command to download the runtime image from a
remote Telnet server to any unit in the stack. (For information on manually downloading a runtime
image, refer to “Downloading System Software from a Server” on page 12-1.)
After the runtime image has been downloaded, use the CLI, web, or SNMP command to set the
newly downloaded image as the boot image. And then submit a global reset command to reboot the
whole stack. (For information on these procedures, see “Setting the Startup File” on page 12-6 and
“Resetting the System” on page 5-26.)
Management Functions in Special Stacking Mode
Management commands sent to the Master unit will function the same as under Normal Stacking
Mode. Configuration commands for slave units will only affect the Master unit's database, and will not
be sent to slave units.
•
The save configuration command will not save the startup configuration to slave units.
•
The “copy tftp” and “copy file” commands will function the same as under Normal Stacking
Mode.
•
The “restart” command will function the same as under Normal Stacking Mode.
Normal Operation Mode
The stack Master will complete system initialization and enter normal operation mode within two
minutes. The stack master will then monitor the stack and perform operations, including:
•
-
Add/remove units
-
Stack cable broken
•
Insert/remove optional module
•
System configuration database synchronization, including
•
27-8
Topology monitoring
-
Unit ID table
-
Management VLAN IP address table
-
System up time
-
Event log
Automatic or manual firmware upgrade to slave units, including main board or optional
module
© 2007 Foundry Networks, Inc.
March 2007
Stacking Technology
Topology Monitor
When the stack topology changes, the Master will be re-elected and the whole stacking system will
be re-initiated. Network traffic will be blocked before the stack enters normal operation state.
The following events will cause a stack topology change:
•
Add unit(s) to the stack.
•
Remove unit(s) from the stack.
•
Stack cable broken in a non-loop stacking mode.
•
Any unit fails.
Note: A break in a loop stacking cable will not cause a topology change. However, the topology
table will be rebuilt.
A topology change event will be reported when the stack enters normal operation by:
•
Logging the reason for a topology change
•
Sending a topology change trap
Adding a Unit to the Stack
The stack topology changes when a new unit is added to the stack.
•
A topology change will re-elect the Master unit based on rules described in “Master Election”
on page 27-4.
•
The Master unit will assign a Unit ID to the new unit based on the rules described in “Auto
Unit-ID Assignment” on page 27-5.
•
The Master unit will display an error message to the management console and enter a nonoperative state if the total number of units or switch ASIC devices exceeds the system
capacity as described under “Operational Concepts” on page 27-1.
Removing a Unit from the Stack
The stack topology changes when a unit is removed from the stack.
•
A topology change will re-elect the Master unit based on rules described in “Master Election”
on page 27-4.
•
A unit failure will be handled the same as a unit removed from the stack.
Note: If a unit is removed or a stack cable fails, the Stack Link LED on the front panel of the
adjacent units will flash amber (green) to indicate that the stack connection to the next unit up (down)
in the stack has failed.
Recovering from a Broken Stacking Cable in Non-loop Stacking Mode
The stack will break into two stacks when a stacking cable fails in non-loop stacking topology. The
new stacks will operate according to the rules describe in “Single IP Management” on page 27-12.
December 2007
© 2007 Foundry Networks, Inc.
27-9
Foundry EdgeIron User Guide
Monitor and Maintain Optional Module
The Master Unit will monitor the operations of optional modules installed in the stack.
•
The Master unit will detect if any optional module is inserted or removed from the Master.
•
Each unit in the stack will detect and notify the Master unit if an optional module is removed
from the unit.
•
Inserting or removing a module in the stack will not cause a stack topology change.
•
Removing an optional module will not effect the operation of other units or modules in the
stack.
Note: Optional modules are hot swappable (i.e., they can be inserted or removed without powering
down the switch).
Firmware of Optional Module
•
Operational Module firmware is bound with main board image; the optional module firmware
will be selected once the runtime image starts booting.
•
Each unit in the stack will detect and notify the Master unit if an optional module is inserted
into the unit.
•
The Master unit will isolate the inserted module and display a message requesting firmware
upgrade if newly added optional module firmware version is different from the current runtime
firmware.
Configuration of Optional Module
•
If current optional module of a given unit is removed and replaced with a new module of the
same type, the new optional module will inherit the original configuration.
•
If current optional module of the given unit is removed and replaced with a new module of the
different type, the configuration for the new optional module shall be reset to default value.
Optional Module Indication
When the optional module is installed or removed (i.e., swapped while the switch is powered on), the
stacking system will report the optional module status via the CLI, web, and SNMP interface as:
present – The Optional Module is operating normally.
not-present – The Optional Module is not installed.
isolated – The Optional Module is installed but not operating due to one of the following reasons:
27-10
•
Connector between the Master unit and optional module failed.
•
Diagnosis of optional module failed.
•
The stack has exceeded the maximum ASIC device number of 32 as described under
“Operational Concepts” on page 27-1.
•
The optional module has an older firmware version.
© 2007 Foundry Networks, Inc.
March 2007
Stacking Technology
The Master unit will report modules that have been isolated in the following way:
•
CLI command to “show system information”
•
Log event
•
Send trap
System Configuration Synchronization
The configuration file set to start on system bootup will be synchronized to slave units in normal
operation mode whenever you save the boot configuration file to flash memory.
To maintain stack operations after a topology change, the Master unit will synchronize the system
configuration, system up-time, and event log to other units, as indicated in the following subsections.
Database Synchronization to Slave Units
•
The Master unit synchronizes the Unit ID Table to slave units whenever this table is updated.
•
The Master unit synchronizes the IP Address Table for the management VLAN to slave units
whenever this table is updated.
•
The Master unit synchronizes the boot configuration file to the slave units whenever this file
is modified and saved to Flash.
•
The Master unit synchronizes the boot configuration file to slave units if the slave's own boot
configuration file is not identical to the master's.
•
The Master unit synchronizes the date and time to slave units every 30 seconds
Reconfigure Auto Unit-ID Re-assignment
The Unit ID will be reassigned automatically whenever the topology changes.
You can also renumber the Unit ID of each unit in the stack via the CLI, web or SNMP. You can
renumber the stack through the CLI using the switch renumber (5-23) command. The system will
be automatically rebooted after the stack’s Unit IDs are re-numbered.
Automatic Unit-ID Renumbering After a Topology Change
When the stack topology changes and master re-election is completed, the Master unit will re-assign
the Unit ID for each unit in the stack. Unit ID assignments will be performed as described in “Auto
Unit-ID Assignment” on page 27-5.
Manual Unit ID Renumbering
The Unit ID in a stack may become incontiguous after adding units to or removing them from the
stack. You can renumber the ID of each unit in the stack via the CLI, web or SNMP. You can
renumber the stack through the CLI using the switch renumber (5-23) command.
When the Unit IDs are renumbered, the Master unit erases its Unit ID Table and treats the stack as
a newly formed stack as described in “Auto Unit-ID Assignment” on page 27-5. The Master Unit reinitiates the system configuration and restarts the system after re-assigning the Unit IDs. Note that
the configuration settings will not change after the Unit IDs are renumbered.
December 2007
© 2007 Foundry Networks, Inc.
27-11
Foundry EdgeIron User Guide
Single IP Management
If a unit cannot detect a link on both the uplink and downlink stack ports, the unit will automatically
start operating as a standalone device.
When switches are connected together in a stack, the stack will be managed as a single entity via
the web, Telnet, and SNMP interface through a single IP address.
Select Management VLAN IP Address
Only the Management VLAN IP address configured for the Master unit can be used to manage the
stack via the CLI, Telnet, SNMP, or web interface. The IP address assigned to the slave units are
only activated if one of these units has to take over as Master in case of a system failure.
When a Stack Breaks into Two Stacks
When a stack breaks into two or more stacks, the IP address configured for the Master unit of each
newly formed stack will be used to manage each stack respectively.
Stacks Merged
When one or more stacks are merged into one stack, the stack will go through the Master Election
process to elect a new master as described in “Master Election” on page 27-4. The Management IP
address assigned to the Master unit will be used to manage the new stack.
Loop Stacking
A closed loop stacking system provides a redundant path to maintain the stack’s functions when one
of the following failure conditions occurs:
•
A stacking cable between any two units in a stack breaks
•
A stacking cable fails, such as an open or short-circuit failure of a pin on the cable
•
A single unit in the stack fails due to conditions such as a hardware failure or power loss
When using looped stacking, redundant paths across the stacking cables will be used to replace any
failed paths between units in the stack.
If a failure occurs only at a single point in the stack interconnections, the system will still be fully
manageable and continue providing backbone connectivity for all units in the stack.
The following characteristics are provided for Redundant Loop Stacking:
•
27-12
The system will recover normal operations within 30 seconds to minimize the impact on
network connectivity.
-
Topology table is rebuilt
-
Master unit is NOT re-elected
-
Unit ID of each unit in the stack is retained
-
The device ID (i.e, MAC address) of each unit is retained
-
L2 Address table is NOT flushed
•
The same Management IP Address is used to manage the whole stack
•
System configuration is retained
© 2007 Foundry Networks, Inc.
March 2007
Stacking Technology
•
System Date and Time are retained
•
System Up time is retained
Resilient Loop Stacking can interoperate with all other stacking units including:
•
EdgeIron 24GS and 48GS switch units
•
Short and long stack cables
•
Stacking interface slot
System Adaptation Data
Description
Maximum Capacity
Unit/port
Number of units per stack
8 units
Number of ports per unit
24GS: 25 ports (24 ports + 10G expansion module’s port)
48GS: 49 ports (48 ports + 10G expansion module’s port)
Number of ports on board per unit
24GS: 24 ports
48GS: 48 ports
Number of expansion module per unit
1 expansion module
Port number of optional slot
24GS: Port 25
48GS: Port 49
Link Aggregation
Number of static link aggregations
32 (static + 802.3ad)
Number of 802.3ad link aggregations
32 (static + 802.3ad)
Number of Gigabit port per link aggregations
8 (8 Gigabit port link aggregation)
Number of 10G ports per link aggregations
4 (4 10G port link aggregation)
VLAN
Number of VLANs
256 (802.1Q or 802.1v)
Number of 802.1Q VLANs
256
Number of 802.1v protocol VLANs
7 (deduct from 802.1Q VLANs)
Number of VIDs
4093 (1-4093, 4094 is reserved)
IGMP and Multicast Group
Number of multicast groups
512 (statically configured + dynamically learned)
Number of static multicast groups
64
Port Mirroring
Number of mirror ports per stack
December 2007
1
© 2007 Foundry Networks, Inc.
27-13
Foundry EdgeIron User Guide
Interface Type
Interface Number1
Ethernet ports
1-392 (48 ports + 10G module per unit, up to 8 stacked units)
Trunks
1001-1032 (up to 32 aggregated links)
RS232 Interface port
2001
Out Bound Management port
2002
802.1Q VLAN
3001-7095 (4K-1 VLANs)
Not used
10001-65535
1. Some values apply to a broader software platform, and are therefore not used for the 24GS and 48GS.
27-14
© 2007 Foundry Networks, Inc.
March 2007
Appendix A
Using Syslog
Overview
This appendix describes how to display Syslog messages and how to configure the Syslog facility,
and lists the Syslog messages that a Foundry EdgeIron switch can display during standard
operation.
A Foundry device’s software can write syslog messages to provide information at the following
severity levels:
•
Emergencies
•
Alerts
•
Critical
•
Errors
•
Warnings
•
Notifications
•
Informational
•
Debugging
The device writes the messages to a local buffer.
You also can specify the IP address or host name of up to five Syslog servers. When you specify a
Syslog server, the Foundry device writes the messages both to the system log and to the Syslog
server.
Using a Syslog server ensures that the messages remain available even after a system reload. The
Foundry device’s local Syslog buffer is cleared during a system reload or reboot, but the Syslog
messages sent to the Syslog server remain on the server.
The Syslog service on a Syslog server receives logging messages from applications on the local
host or from devices such as a Layer 2 Switch or Layer 3 Switch. Syslog adds a time stamp to each
received message and directs messages to a log file. Most Unix workstations come with Syslog
configured. Some third-party vendor products also provide Syslog for Windows.
Syslog uses UDP port 514 and each Syslog message thus is sent with destination port 514. Each
Syslog message is one line with Syslog message format. The message is embedded in the text
portion of the Syslog format. There are several subfields in the format. Keywords are used to
December 2007
© 2007 Foundry Networks, Inc.
A-1
Foundry EdgeIron User Guide
identify each subfield, and commas are delimiters. The subfield order is insensitive except that the
text subfield should be the last field in the message. All the subfields are optional.
Displaying Syslog Messages
To display the Syslog messages in the device’s local buffer, enter the following command at the
Privileged Exec level of the CLI:
Console#show logging ram
Syslog logging: Enable
History logging in RAM: level debugging
[3] 0:1:32 1/1/1
"VLAN 1 link-up notification."
level: 6, module: 6, function: 1, and event
[2] 0:1:32 1/1/1
"STP topology change notification."
level: 6, module: 6, function: 1, and event
[1] 0:1:32 1/1/1
"Unit 1, Port 23 link-up notification."
level: 6, module: 6, function: 1, and event
[0] 0:1:32 1/1/1
"System coldStart notification."
level: 6, module: 6, function: 1, and event
Console#
no.: 1
no.: 1
no.: 1
no.: 1
For information about the Syslog configuration information, time stamps, and dynamic and static
buffers, see “Enabling System Logs” on page 7-2.
Configuring the Syslog Service
The procedures in this section describe how to perform the following Syslog configuration tasks:
•
Specify a Syslog server. You can configure the Foundry device to use up to five Syslog servers.
(Use of a Syslog server is optional. The system can hold up to up to 2048 Syslog messages in
RAM memory and up to 4096 messages in Flash memory.)
•
Change the level of messages the system logs.
•
Display the Syslog configuration.
•
Clear the local Syslog buffer.
Syslog logging is disabled by default, with the following settings:
A-2
•
Messages of all severity levels (Emergencies through Debugging) are logged.
•
No Syslog server is specified.
© 2007 Foundry Networks, Inc.
December 2007
Displaying the Syslog Configuration
To display the Syslog parameters currently in effect on a Foundry EdgeIron device, enter the
following command from the Privileged Exec level of the CLI:
Console#show logging trap
Syslog logging: Enable
REMOTELOG status: disable
REMOTELOG facility type: local use 7
REMOTELOG level type: Debugging messages
REMOTELOG server ip address: 0.0.0.0
REMOTELOG server ip address: 0.0.0.0
REMOTELOG server ip address: 0.0.0.0
REMOTELOG server ip address: 0.0.0.0
REMOTELOG server ip address: 0.0.0.0
Console#
Syntax: show logging {flash | ram | trap}
The Syslog display shows the following configuration information.
This Field...
Displays...
Syslog logging
The state (enabled or disabled) of logging on the switch.
REMOTELOG Status
The state (enabled or disabled) of logging to a remote Syslog
server.
REMOTELOG Facility Type
A number that indicates the facility used by the syslog server to
dispatch log messages to an appropriate service.
REMOTELOG Level Type
One of the Syslog levels from 0 (Emergencies) to 7 (Debugging).
Messages sent include the selected level up through level 0.
REMOTELOG Server IP Address
Up to five IP addresses of Syslog servers.
Flash and RAM Buffers
The software provides two separate buffers:
•
Flash - Permanently stored in the switch.
•
RAM - Memory flushed on power reset.
Error messages that are logged to flash memory remain stored in the switch even after a power
reset. Up to 4096 log entries can be stored in the flash memory, with the oldest entries being
overwritten first when the available log memory (256 kilobytes) has been exceeded.
The switch can store up to 2048 log entries in temporary random access memory (RAM; i.e.,
memory flushed on power reset). The switch periodically copies log messages in RAM to flash
memory, depending on the error level limit configured. The flash error level limit must be equal to or
less than the RAM level limit.
December 2007
© 2007 Foundry Networks, Inc.
A-3
Foundry EdgeIron User Guide
The flash and RAM buffers are both displayed using the following commands:
Console#show logging ram
Syslog logging: Enable
History logging in RAM: level debugging
[3] 0:1:32 1/1/1
"VLAN 1 link-up notification."
level: 6, module: 6, function: 1, and event
[2] 0:1:32 1/1/1
"STP topology change notification."
level: 6, module: 6, function: 1, and event
[1] 0:1:32 1/1/1
"Unit 1, Port 23 link-up notification."
level: 6, module: 6, function: 1, and event
[0] 0:1:32 1/1/1
"System coldStart notification."
level: 6, module: 6, function: 1, and event
Console#
Console#show logging flash
Syslog logging: Enable
History logging in FLASH: level errors
[9] 13:30:42 2/28/4
"VLAN 1 link-up notification."
level: 6, module: 6, function: 1, and event
[8] 13:30:42 2/28/4
"STP topology change notification."
level: 6, module: 6, function: 1, and event
[7] 13:30:12 2/28/4
"Unit 1, Port 8 link-up notification."
level: 6, module: 6, function: 1, and event
[6] 13:30:8 2/28/4
"Unit 1, Port 8 link-down notification."
level: 6, module: 6, function: 1, and event
[5] 13:30:8 2/28/4
"VLAN 1 link-down notification."
level: 6, module: 6, function: 1, and event
[4] 13:20:6 3/3/4
"VLAN 1 link-up notification."
level: 6, module: 6, function: 1, and event
[3] 13:20:6 3/3/4
"STP topology change notification."
level: 6, module: 6, function: 1, and event
[2] 13:19:36 3/3/4
"Unit 1, Port 8 link-up notification."
level: 6, module: 6, function: 1, and event
[1] 13:19:31 3/3/4
"Unit 1, Port 6 link-down notification."
level: 6, module: 6, function: 1, and event
[0] 13:19:31 3/3/4
"VLAN 1 link-down notification."
level: 6, module: 6, function: 1, and event
Console#
A-4
no.: 1
no.: 1
no.: 1
no.: 1
no.: 1
no.: 1
no.: 1
no.: 1
no.: 1
no.: 1
no.: 1
no.: 1
no.: 1
no.: 1
© 2007 Foundry Networks, Inc.
December 2007
When you clear log entries, you can selectively clear the flash or RAM, or you can clear both. For
example, to clear only the RAM, enter the following command at the Privileged Exec level:
EdgeIron# clear logging ram
Syntax: clear logging [ram | flash]
You can specify ram to clear the RAM buffer or flash to clear the flash buffer. If you do not specify a
buffer, both buffers are cleared.
Time Stamps
The contents of the time stamp depends on whether the system time and date has been set
manually or by SNTP.
•
If the system clock has been set, the date and time are shown in the following format:
•
hh:mm:ss m/d/y
•
where:
•
hh – hours
•
mm – minutes
•
ss – seconds
•
m – month
•
d – day
•
y – year
For example, “22:34:15 2/28/4" means February 28, 2004 at 10:34 PM and 15 seconds.
•
If the system clock is not set, the time stamp shows the time and date since the device was
booted, starting from 00:00:00 1/1/1.
Example of Syslog Messages on a Device Whose Onboard Clock Is Set
The example shows the format of messages on a device whose onboard system clock has been set.
Each time stamp shows the month, the day, and the time of the system clock when the message was
generated. For example, the system time when the most recent message (the one at the top) was
generated was February 28, 2004 at 1:30 PM and 12 seconds.
Console#show logging ram
Syslog logging: Enable
History logging in RAM: level debugging
[11] 13:30:12 2/28/4
"Unit 1, Port 8 link-up notification."
level: 6, module: 6, function: 1, and event no.: 1
[10] 13:30:8 2/28/4
"Unit 1, Port 8 link-down notification."
level: 6, module: 6, function: 1, and event no.: 1
[9] 13:30:8 2/28/4
"VLAN 1 link-down notification."
level: 6, module: 6, function: 1, and event no.: 1
Displaying and Configuring Syslog Buffer Parameters Using the Web
December 2007
© 2007 Foundry Networks, Inc.
A-5
Foundry EdgeIron User Guide
Management Interface
To configure Syslog parameters using the Web management interface, use the following procedure:
1. Log on to the device using a valid user name and password for read-write access. The System
Information page is displayed.
2. Select Log from the System menu.
3. Select the System Logs link to display the following page:
4. Check or clear the check box next to System Log Status to enable or disable the Syslog service
on the device. The service is enabled by default.
5. Select the maximum message level you want the device to log to RAM and flash. All the levels
are logged to RAM by default.
6. Click Apply to save the changes to the device’s running-config file.
7. To enable logging to Syslog servers and view a list of the servers that have been defined, click
the Remote Logs link.
A-6
© 2007 Foundry Networks, Inc.
December 2007
8. Check or clear the check box next to Remote Log Status to enable or disable logging to Syslog
servers. The remote logging service is disabled by default.
9. Select the maximum message level you want the device to log to Syslog servers. All the levels
are logged by default.
Disabling or Re-Enabling Syslog
Syslog is enabled by default. To disable or re-enable it, use one of the following methods.
USING THE CLI
To disable it, enter the following command at the global CONFIG level:
EdgeIron(config)# no logging on
Syntax: [no] logging on
To re-enable logging, enter the following command:
EdgeIron(config)# logging on
This command enables local Syslog logging with the following defaults:
•
Messages of all severity levels (Emergencies through Debugging) are logged.
•
No Syslog server is specified.
Specifying a Syslog Server
To specify a Syslog server, enter the following command:
USING THE CLI
EdgeIron(config)# logging host 10.0.0.99
Syntax: [no] logging host <ip-address>
Using The Web Management Interface
See the section “Remote Logs Configuration” on page 7-5.
Specifying an Additional Syslog Server
USING THE CLI
To specify an additional Syslog server, enter the logging host <ip-addr> command again, as in the
following example. You can specify up to five Syslog servers.
EdgeIron(config)# logging host 10.0.0.99
Syntax: [no] logging host <ip-address>
December 2007
© 2007 Foundry Networks, Inc.
A-7
Foundry EdgeIron User Guide
Changing the Log Facility
The Syslog daemon on the Syslog server uses a facility to determine where to log the messages
from the Foundry device. The default facility for messages the Foundry EdgeIron device sends to the
Syslog server is “local use 7.” You can change the facility using the following command.
Note: You can specify only one facility. If you configure the Foundry device to use two Syslog
servers, the device uses the same facility on both servers.
EdgeIron(config)# logging facility 16
Syntax: [no] logging facility <type>
The <type> can be one of the following facility numbers:
•
16 – local use 0
•
17 – local use 1
•
18 – local use 2
•
19 – local use 3
•
20 – local use 4
•
21 – local use 5
•
22 – local use 6
•
23 – local use 7
USING THE WEB MANAGEMENT INTERFACE
See the section "Remote Logs Configuration" on page 7-1.
Clearing the Syslog Messages from the Local Buffer
To clear the Syslog messages stored in the Foundry device’s local buffer, use the following CLI
command:
EdgeIron# clear logging
Syntax: clear logging [flash | ram]
Syslog Messages
The table below lists all of the Syslog messages. The messages are listed by message level, in the
following order:
A-8
•
Emergencies (none)
•
Alerts
•
Critical (none)
•
Errors
© 2007 Foundry Networks, Inc.
December 2007
•
Warnings
•
Notifications
•
Informational
•
Debugging
Note: In the messages displayed %s is substitute with a string, and %1d is replaced with integer
values.
Message Level
Message
Explanation
Critical
%s create task fail
The created task has failed.
Error
%s switch to default
The switch has encountered an abnormal
case.
Critical
Allocate %s memory fail
Command to allocate memory has failed.
Critical
Free %s memory fail
Command to free memory has failed.
Informative
Unit %1d, fan %1d fail
A fan has failed.
Error
%s function fails
A software function has failed.
Informative
System coldStart notification
A coldstart has occurred.
Informative
System warmStart notification
A warmstart has occurred.
Informative
Unit %1d, Port %1d link-up notification
A link to a port has been established.
Informative
Unit %1d, Port %1d link-down notification
A link to a port has failed.
Informative
Trunk %1d link-up notification
A link to a trunk has been established.
Informative
Trunk %1d link-down notification
A link to a trunk has failed.
Informative
VLAN %1d link-up notification
A link to a VLAN has been established.
Informative
VLAN %1d link-down notification
A link to a VLAN has failed.
Informative
Authentication failure notification
The user authentication procedure for SNMP
has failed.
Informative
STA root change notification
The root of the spanning tree has changed.
Informative
STA topology change notification
The spanning tree topology has changed.
Informative
RMON rising alarm
A RMON warning has occurred and is
increasing in severity.
Informative
RMON falling alarm notification
A RMON warning has occurred and is
decreasing in severity.
Informative
Unit %1d, %s power change to %s
The power status of the device unit has
changed.
Informative
Loopback test failure
The loopback test has failed.
Informative
Fan Recover, unit=[%d], fanIndex=[%1d]
A fan has recovered from a failure condition.
Informative
Ipfilter reject, mode=[%1d.%1d.%1d.%1d]
The IP filter has rejected some data packets.
December 2007
© 2007 Foundry Networks, Inc.
A-9
Foundry EdgeIron User Guide
Message Level
Message
Explanation
Warning
DHCP request failed - will retry later
A DHCP request has failed and will attempt
resending the request later.
Warning
DHCP server responded
A response from a DHCP server has been
received.
Informative
SMTP connect host %s failure
The switch has failed to connect to the SMTP
host.
Informative
MainBoardVerMismatch:%s
There is a mismatch in the firmware version
specified.
Informative
ModuleVerMismatch:%s
The firmware version of the module
mismatches the device version.
Informative
ModuleInsertion:%s
An optional module was inserted in to the
device.
Informative
ModuleRemoval:%s
A module was removed from the device.
A-10
© 2007 Foundry Networks, Inc.
December 2007
Appendix B
Trap Messages
Trap Messages
Supported Trap Messages
Object Label
Object ID
Description
newRoot
1.3.6.1.2.1.17.0.1
The newRoot trap indicates that the sending
agent has become the new root of the Spanning
Tree; the trap is sent by a bridge soon after its
election as the new root, e.g., upon expiration of
the Topology Change Timer immediately
subsequent to its election.
topology Change
1.3.6.1.2.1.17.0.2
A topologyChange trap is sent by a bridge when
any of its configured ports transitions from the
Learning state to the Forwarding state, or from the
Forwarding state to the Discarding state. The trap
is not sent if a newRoot trap is sent for the same
transition.
coldStart
1.3.6.1.6.3.1.1.5.1
A coldStart trap signifies that the SNMPv2 entity,
acting in an agent role, is reinitializing itself and
that its configuration may have been altered.
warmStart
1.3.6.1.6.3.1.1.5.2
A warmStart trap signifies that the SNMPv2 entity,
acting in an agent role, is reinitializing itself such
that its configuration is unaltered.
linkDown
1.3.6.1.6.3.1.1.5.3
A linkDown trap signifies that the SNMP entity,
acting in an agent role, has detected that the
ifOperStatus object for one of its communication
links is about to enter the down state from some
other state (but not from the notPresent state).
This other state is indicated by the included value
of ifOperStatus.
linkUp
1.3.6.1.6.3.1.1.5.4
A linkUp trap signifies that the SNMP entity,
acting in an agent role, has detected that the
ifOperStatus object for one of its communication
links left the down state and transitioned into
some other state (but not into the notPresent
state). This other state is indicated by the included
value of ifOperStatus.
RFC 1493 Traps
SNMPv2 Traps
December 2007
© 2007 Foundry Networks, Inc.
B-1
Foundry EdgeIron User Guide
Supported Trap Messages
Object Label
Object ID
Description
authentication
Failure
1.3.6.1.6.3.1.1.5.5
An authenticationFailure trap signifies that the
SNMPv2 entity, acting in an agent role, has
received a protocol message that is not properly
authenticated. While all implementations of the
SNMPv2 must be capable of generating this trap,
the snmpEnableAuthenTraps object indicates
whether this trap will be generated.
risingAlarm
1.3.6.1.2.1.16.0.1
The SNMP trap that is generated when an alarm
entry crosses its rising threshold and generates
an event that is configured for sending SNMP
traps.
fallingAlarm
1.3.6.1.2.1.16.0.2
The SNMP trap that is generated when an alarm
entry crosses its falling threshold and generates
an event that is configured for sending SNMP
traps.
swPowerStatus
ChangeTrap
1.3.6.1.4.1.1991.6.10.45.2.1.0.1
This trap is sent when the power state changes.
swPort
SecurityTrap
1.3.6.1.4.1.1991.1.5.1.1.2.1.0.36
This trap is sent when the port is being intruded
on. This trap will only be sent when portSecAction
(1.3.6.1.4.1.259.6.10.51.1.17.2.1.1.3) is set to
trap.
swIpFilter
RejectTrap
1.3.6.1.4.1.1991.6.10.45.2.1.0.40
This trap is sent when an incorrect IP address is
rejected by the IP Filter.
swSmtp
ConnFailureTrap
1.3.6.1.4.1.1991.6.10.45.2.1.0.41
This trap is triggered if the SMTP system cannot
open a connection to the mail server successfully.
RMON Events (V2)
Private Traps
B-2
© 2007 Foundry Networks, Inc.
December 2007
Appendix C
Troubleshooting
Troubleshooting Chart
Troubleshooting Chart
Symptom
Action
Cannot connect using
Telnet, Web browser, or
SNMP software
•
Be sure to have configured the agent with a valid IP address,
subnet mask and default gateway.
•
Be sure that your management station has management VLAN
access to the switch (default is VLAN 1).
•
Check that you have a valid network connection to the switch and
that the port you are using has not been disabled.
•
Check network cabling between the management station and the
switch.
•
If you cannot connect using Telnet, you may have exceeded the
maximum number of concurrent Telnet sessions permitted. Try
connecting again at a later time.
•
Be sure to have set the terminal emulator program to VT100
compatible, 8 data bits, 1 stop bit, no parity and 9600 bps.
•
Check that the null-modem serial cable conforms to the pin-out
connections provided in Appendix B.
•
Set the switch to its default configuration. Make a direct
connection to the switch’s console port and power cycle the
switch. Immediately after powering on, press <Ctrl><u> to access
the system file menu. ]Select <D> to delete all user-defined
configuration files. Press <Q> to boot the switch.
Cannot access the on-board
configuration program via a
serial port connection
Forgot or lost the password
(Applicable to EdgeIron
2402CF, 4802CF and 24G
only.)
December 2007
© 2007 Foundry Networks, Inc.
C-1
Foundry EdgeIron User Guide
C-2
© 2007 Foundry Networks, Inc.
December 2007
Appendix D
Upgrading Firmware via the Serial Port
Note: The following procedure is only applicable to the EdgeIron 2402CF, 4802CF and 24G, 24GS,
and 48GS
The switch contains three firmware components that can be upgraded; the diagnostics (or
Boot-ROM) code, runtime operation code, and the loader code. The runtime code can be upgraded
via the switch’s RS-232 serial console port, via a network connection to a TFTP server, or using
SNMP management software. The diagnostics and loader code can be upgraded only via the
switch’s RS-232 serial console port.
Note: You can use the switch’s web interface to download runtime code via TFTP. Downloading
large runtime code files via TFTP is normally much faster than downloading via the switch’s serial
port.
You can upgrade switch firmware by connecting a PC directly to the serial Console port on the
switch’s front panel and using VT100 terminal emulation software that supports the XModem
protocol. (See “Required Connections” on page 2-2.)
Note: Before executing this procedure, contact Foundry Networks support for a password that will
be required in Step 4.
1. Connect a PC to the switch’s Console port using a null-modem or crossover RS-232 cable with a
female DB-9 connector.
2. Configure the terminal emulation software’s communication parameters to 9600 baud, 8 data
bits, 1 stop bit, no parity, and set flow control to none.
3. Power cycle the switch.
December 2007
© 2007 Foundry Networks, Inc.
D-1
Foundry EdgeIron User Guide
4. When the switch initialization screen appears, enter firmware-download mode by pressing
<Ctrl><u> immediately after power on. Screen text similar to that shown below displays:
File Name
--------------------------------$certificate
$logfile_1
Factory_Default_Config.cfg
diag_1000
r_20019
set-ip.cfg
--------------------------------[X]modem Download [D]elete File
[C]hange Baudrate [Q]uit
Select>
S/Up Type Size
---- ---- ---------0
7
20480
0
3
64
0
5
2574
1
1
116228
1
2
1536972
1
5
2690
---- ---- ---------[S]et Startup File
Create Time
----------00:38:34
00:00:02
00:00:12
00:00:00
00:00:01
00:40:44
----------
Note: You will need a password from Foundry Networks support for this step.
5. Press <C> to change the baud rate of the switch’s serial connection.
6. Press <B> to select the option for 115200 baud.
There are two baud rate settings available, 9600 and 115200. Using the higher baud rate
minimizes the time required to download firmware code files.
7. Set your PC’s terminal emulation software to match the 115200 baud rate. Press <Enter> to
reset communications with the switch.
Select>
Change baudrate [A]9600 [B]115200
Baudrate set to 115200
8. Check that the switch has sufficient flash memory space for the new code file before starting the
download.
You can store a maximum of only two runtime and two diagnostic code files in the switch’s flash
memory. Use the [D]elete File command to remove a runtime or diagnostic file.
9. Press <X> to start to download the new code file.
If using Windows HyperTerminal, click the “Transfer” button, and then click “Send File....” Select
the XModem Protocol and then use the “Browse” button to select the required firmware code file
from your PC system. The “Xmodem file send” window displays the progress of the download
procedure.
Note: The download file must be a valid binary software file from Foundry for the target switch.
10. After the file has been downloaded, you are prompted with “Update Image File:” to specify the
type of code file. Press <R> for runtime code, <D> for diagnostic code, or ,<L> for loader code.
Caution: If you select <L> for loader code, be sure the file is a valid loader code file for the switch. If
you download an invalid file, the switch will not be able to boot. Unless absolutely
necessary, do not attempt to download loader code files.
D-2
© 2007 Foundry Networks, Inc.
December 2007
11. Specify a name for the downloaded code file. File names are case-sensitive, should be from 1 to
31 characters, not contain slashes (\ or /), and the leading letter of the file name should not be a
period (.). (Valid characters: A-Z, a-z, 0-9, “.”, “-”, “_”)
For example, the following screen text shows the download procedure for a runtime code file:
Select>
Xmodem Receiving Start:
Image downloaded to buffer.
[R]untime
[D]iagnostic
[L]oader (Warning: you sure what you are doing?)
Update Image File:r
Diagnostic Image Filename : r_20019
Updating file system.
File system updated.
[Press any key to continue]
12. To set the new downloaded file as the startup file, use the [S]et Startup File menu option.
13. When you have finished downloading code files, use the [C]hange Baudrate menu option to
change the baud rate of the switch’s serial connection back to 9600 baud.
14. Set your PC’s terminal emulation software baud rate back to 9600 baud. Press <Enter> to reset
communications with the switch.
15. Press <Q> to quit the firmware-download mode and boot the switch.
December 2007
© 2007 Foundry Networks, Inc.
D-3
Foundry EdgeIron User Guide
D-4
© 2007 Foundry Networks, Inc.
December 2007
Appendix E
Pin Assignments
Console Port Pin Assignments
The DB-9 serial port on the switch’s front panel is used to connect to the switch for out-of-band
console configuration. The onboard menu-driven configuration program can be accessed from a
terminal or a PC running a terminal emulation program. The pin assignments used to connect to the
serial port are provided in the following tables.
Figure 27-1. DB-9 Console Port Pin Numbers
1
6
5
9
DB-9 Port Pin Assignments
EIA Circuit
CCITT
Signal
Description
Switch’s DB9
DTE Pin #
PC DB9 DTE
Pin #
BB
104
RxD (Received Data)
2
2
BA
103
TxD (Transmitted Data)
3
3
AB
102
SGND (Signal Ground)
5
5
No other pins are used.
December 2007
© 2007 Foundry Networks, Inc.
E-1
Foundry EdgeIron User Guide
Console Port to 9-Pin DTE Port on PC
Switch’s 9-Pin Serial Port
Null Modem
PC’s 9-Pin DTE Port
2 RXD
<---------TXD ------------
3 TXD
3 TXD
-----------RXD ---------->
2 RXD
5 SGND
-----------SGND ----------
5 SGND
No other pins are used.
Console Port to 25-Pin DTE Port on PC
Switch’s 9-Pin Serial Port
Null Modem
PC’s 25-Pin DTE Port
2 RXD
<---------TXD ------------
2 TXD
3 TXD
-----------RXD ---------->
3 RXD
5 SGND
-----------SGND ----------
7 SGND
No other pins are used.
E-2
© 2007 Foundry Networks, Inc.
December 2007
Glossary
10BASE-T
IEEE 802.3 specification for 10 Mbps Ethernet over two pairs of Category 3, 4, or 5 UTP cable.
100BASE-TX
IEEE 802.3u specification for 100 Mbps Fast Ethernet over two pairs of Category 5 UTP cable.
1000BASE-T
IEEE 802.3ab specification for Gigabit Ethernet over two pairs of Category 5, 5e 100-ohm UTP
cable.
1000BASE-X
IEEE 802.3 shorthand term for any 1000 Mbps Gigabit Ethernet based on
8B/10B signaling.
Access Control List (ACL)
ACLs can limit network traffic and restrict access to certain users or devices by checking each
packet for certain IP or MAC (i.e., Layer 2) information.
Auto-negotiation
Signalling method allowing each node to select its optimum operational mode (e.g., 10, 100, or 1000
Mbps and half or full duplex) based on the capabilities of the node to which it is connected.
Bandwidth
The difference between the highest and lowest frequencies available for network signals. Also
synonymous with wire speed, the actual speed of the data transmission along the cable.
BOOTP
Boot protocol used to load the operating system for devices connected to the network.
Class of Service (CoS)
CoS is supported by prioritizing packets based on the required level of service, and then placing
them in the appropriate output queue. Data is transmitted from the queues using weighted
round-robin service to enforce priority service and prevent blockage of lower-level queues. Priority
may be set according to the port default, the packet’s priority bit (in the VLAN tag), TCP/UDP port
number, IP Precedence bit, or DSCP priority bit.
December 2007
© 2007 Foundry Networks, Inc.
Glossary-1
Foundry EdgeIron User Guide
Collision
A condition in which packets transmitted over the cable interfere with each other. Their interference
makes both signals unintelligible.
Collision Domain
Single CSMA/CD LAN segment.
CSMA/CD
Carrier Sense Multiple Access/Collision Detect is the communication method employed by Ethernet
and Fast Ethernet.
Differentiated Services Code Point Service (DSCP)
DSCP uses a six-bit tag to provide for up to 64 different forwarding behaviors. Based on network
policies, different kinds of traffic can be marked for different kinds of forwarding. The DSCP bits are
mapped to the Class of Service categories, and then into the output queues.
Dynamic Host Control Protocol (DHCP)
Provides a framework for passing configuration information to hosts on a TCP/IP network. DHCP is
based on the Bootstrap Protocol (BOOTP), adding the capability of automatic allocation of reusable
network addresses and additional configuration options.
End Station
A workstation, server, or other device that does not act as a network interconnection.
Ethernet
A network communication system developed and standardized by DEC, Intel, and Xerox, using
baseband transmission, CSMA/CD access, logical bus topology, and coaxial cable. The successor
IEEE 802.3 standard provides for integration into the OSI model and extends the physical layer and
media with repeaters and implementations that operate on fiber, thin coax and twisted-pair cable.
Extensible Authentication Protocol over LAN (EAPOL)
EAPOL is a client authentication protocol used by this switch to verify the network access rights for
any device that is plugged into the switch. A user name and password is requested by the switch,
and then passed to an authentication server (e.g., RADIUS) for verification. EAPOL is implemented
as part of the IEEE 802.1X Port Authentication standard.
Fast Ethernet
A 100 Mbps network communication system based on Ethernet and the CSMA/CD access method.
Full Duplex
Transmission method that allows switch and network card to transmit and receive concurrently,
effectively doubling the bandwidth of that link.
GARP VLAN Registration Protocol (GVRP)
Defines a way for switches to exchange VLAN information in order to register necessary VLAN
members on ports along the spanning tree so that VLANs defined in each switch can work
automatically over a spanning tree network.
Glossary-2
© 2007 Foundry Networks, Inc.
December 2007
Glossary
Generic Attribute Registration Protocol (GARP)
GARP is a protocol that can be used by endstations and switches to register and propagate
multicast group membership information in a switched environment so that multicast data frames are
propagated only to those parts of a switched LAN containing registered endstations. Formerly called
Group Address Registration Protocol.
Generic Multicast Registration Protocol (GMRP)
GMRP allows network devices to register endstations with multicast groups. GMRP requires that any
participating network devices or endstations comply with the IEEE 802.1p standard.
Gigabit Ethernet
A 1000 Mbps network communication system based on Ethernet and the CSMA/CD access method.
Group Attribute Registration Protocol
See Generic Attribute Registration Protocol.
IEEE 802.1D
Specifies a general method for the operation of MAC bridges, including the Spanning Tree Protocol.
IEEE 802.1Q
VLAN Tagging – Defines Ethernet frame tags which carry VLAN information. It allows switches to
assign endstations to different virtual LANs, and defines a standard way for VLANs to communicate
across switched networks.
IEEE 802.1p
An IEEE standard for providing quality of service (QoS) in Ethernet networks. The standard uses
packet tags that define up to eight traffic classes and allows switches to transmit packets based on
the tagged priority value.
IEEE 802.1X
Port Authentication controls access to the switch ports by requiring users to first enter a user ID and
password for authentication.
IEEE 802.3
Defines carrier sense multiple access with collision detection (CSMA/CD) access method and
physical layer specifications.
IEEE 802.3ab
Defines CSMA/CD access method and physical layer specifications for 1000BASE-T Gigabit
Ethernet.
IEEE 802.3ac
Defines frame extensions for VLAN tagging.
IEEE 802.3u
Defines CSMA/CD access method and physical layer specifications for 100BASE-TX Fast Ethernet.
IEEE 802.3x
Defines Ethernet frame start/stop requests and timers used for flow control on full-duplex links.
December 2007
© 2007 Foundry Networks, Inc.
Glossary-3
Foundry EdgeIron User Guide
IEEE 802.3z
Defines CSMA/CD access method and physical layer specifications for 1000BASE Gigabit Ethernet.
IGMP Snooping
Listening to IGMP Query and IGMP Report packets transferred between IP Multicast Routers and IP
Multicast host groups to identify IP Multicast group members.
IGMP Query
On each subnetwork, one IGMP-capable device will act as the querier — that is, the device that asks
all hosts to report on the IP multicast groups they wish to join or to which they already belong. The
elected querier will be the device with the lowest IP address in the subnetwork.
Internet Control Message Protocol (ICMP)
Commonly used to send echo messages (i.e., Ping) for monitoring purposes.
Internet Group Management Protocol (IGMP)
A protocol through which hosts can register with their local router for multicast services. If there is
more than one multicast router on a given subnetwork, one of the routers is made the “querier” and
assumes responsibility for keeping track of group membership.
In-Band Management
Management of the network from a station attached directly to the network.
IP Multicast Filtering
A process whereby this switch can pass multicast traffic along to participating hosts.
IP Precedence
The Type of Service (ToS) octet in the IPv4 header includes three precedence bits defining eight
different priority levels ranging from highest priority for network control packets to lowest priority for
routine traffic. The eight values are mapped one-to-one to the Class of Service categories by default,
but may be configured differently to suit the requirements for specific network applications.
Layer 2
Data Link layer in the ISO 7-Layer Data Communications Protocol. This is related directly to the
hardware interface for network devices and passes on traffic based on MAC addresses.
Layer 3
Network layer in the ISO 7-Layer Data Communications Protocol. This layer handles the routing
functions for data moving from one open system to another.
Link Aggregation
See Port Trunk.
Link Aggregation Control Protocol (LACP)
Allows ports to automatically negotiate a trunked link with LACP-configured ports on another device.
Management Information Base (MIB)
An acronym for Management Information Base. It is a set of database objects that contains
information about a specific device.
Glossary-4
© 2007 Foundry Networks, Inc.
December 2007
Glossary
MD5
An algorithm that is used to create digital signatures. It is intended for use with 32 bit machines and
is safer than the MD4 algorithm, which has been broken. MD5 is a one-way hash function, meaning
that it takes a message and converts it into a fixed string of digits, also called a message digest.
Media Access Control (MAC)
A portion of the networking protocol that governs access to the transmission medium, facilitating the
exchange of data between network nodes.
Multicast Switching
A process whereby the switch filters incoming multicast frames for services for which no attached
host has registered, or forwards them to all ports contained within the designated multicast VLAN
group.
Network Time Protocol (NTP)
NTP provides the mechanisms to synchronize time across the network. The time servers operate in
a hierarchical-master-slave configuration in order to synchronize local clocks within the subnet and
to national time standards via wire or radio.
Out-of-Band Management
Management of the network from a station not attached to the network.
Per VLAN Spanning Tree (PVST)
Foundry proprietary for spanning tree applicable to instances of VLANs.
Per VLAN Rapid Spanning Tree (PVRST)
Foundry proprietary for rapid spanning tree applicable to instances of VLANs.
Port Mirroring
A method whereby data on a target port is mirrored to a monitor port for troubleshooting with a logic
analyzer or RMON probe. This allows data on the target port to be studied unobstructively.
Port Trunk
Defines a network link aggregation and trunking method which specifies how to create a single
high-speed logical link that combines several lower-speed physical links.
Priority
See “CSMA/CD” on page 2.
Private VLANs
Private VLANs provide port-based security and isolation between ports within the assigned VLAN.
Data traffic on downlink ports can only be forwarded to, and from, uplink ports.
Protected Extensible Authentication Protocol (PEAP)
A protocol proposed by Microsoft, Cisco and RSA Security for securely transporting authentication
data, including passwords, over 802.11 wireless networks. Like the competing standard Tunneled
Transport Layer Security (TTLS), PEAP makes it possible to authenticate wireless LAN clients
without requiring them to have certificates, simplifying the architecture of secure wireless LANs.
December 2007
© 2007 Foundry Networks, Inc.
Glossary-5
Foundry EdgeIron User Guide
Rapid Spanning Tree Protocol (RSTP)
RSTP reduces the convergence time for network topology changes to about 10% of that required by
the older IEEE 802.1D STP standard.
Remote Authentication Dial-in User Service (RADIUS)
RADIUS is a logon authentication protocol that uses software running on a central server to control
access to RADIUS-compliant devices on the network.
Remote Monitoring (RMON)
RMON provides comprehensive network monitoring capabilities. It eliminates the polling required in
standard SNMP, and can set alarms on a variety of traffic conditions, including specific error types.
Routing Information Protocol (RIP)
The RIP protocol seeks to find the shortest route to another device by minimizing the
distance-vector, or hop count, which serves as a rough estimate of transmission cost. RIP-2 is a
compatible upgrade to RIP. It adds useful capabilities for subnet routing, authentication, and
multicast transmissions.
Secure Shell (SSH)
A secure replacement for remote access functions, including Telnet. SSH can authenticate users
with a cryptographic key, and encrypt data connections between management clients and the switch.
Simple Mail Transfer Protocol (SMTP)
A standard host-to-host mail transport protocol that operates over TCP, port 25.
Simple Network Management Protocol (SNMP)
The application protocol in the Internet suite of protocols which offers network management
services.
Spanning Tree Protocol (STP)
A technology that checks your network for any loops. A loop can often occur in complicated or
backup linked network systems. Spanning tree detects and directs data along the shortest available
path, maximizing the performance and efficiency of the network.
Telnet
Defines a remote communication facility for interfacing to a terminal device over TCP/IP.
Terminal Access Controller Access Control System Plus (TACACS+)
TACACS+ is a logon authentication protocol that uses software running on a central server to control
access to TACACS-compliant devices on the network.
Transmission Control Protocol/Internet Protocol (TCP/IP)
Protocol suite that includes TCP as the primary transport protocol, and IP as the network layer
protocol.
Transport Layer Security (TLS)
Transport Layer Security (TLS) is a protocol that ensures privacy between communicating
applications and their users on the Internet. When a server and client communicate, TLS ensures
that no third party may eavesdrop or tamper with any message. TLS is the successor to the Secure
Sockets Layer (SSL).
Glossary-6
© 2007 Foundry Networks, Inc.
December 2007
Glossary
Trivial File Transfer Protocol (TFTP)
A TCP/IP protocol commonly used for software downloads.
Tunneled Transport Layer Security (TTLS)
A proposed wireless security protocol, developed by Funk Software and Certicom, that combines
network-based certificates with other authentication such as tokens or passwords. Also known as
EAP-TTLS.
User Datagram Protocol (UDP)
UDP provides a datagram mode for packet-switched communications. It uses IP as the underlying
transport mechanism to provide access to IP-like services. UDP packets are delivered just like IP
packets – connection-less datagrams that may be discarded before reaching their targets. UDP is
useful when TCP would be too complex, too slow, or just unnecessary.
Virtual LAN (VLAN)
A Virtual LAN is a collection of network nodes that share the same collision domain regardless of
their physical location or connection point in the network. A VLAN serves as a logical workgroup with
no physical barriers, and allows users to share information and resources as though located on the
same LAN.
XModem
A protocol used to transfer files between devices. Data is grouped in 128-byte blocks and
error-corrected.
December 2007
© 2007 Foundry Networks, Inc.
Glossary-7
Foundry EdgeIron User Guide
Glossary-8
© 2007 Foundry Networks, Inc.
December 2007
Index
Numerics
dot1x
global parameters 14-3, 14-6
port mode 14-9, 14-10
statistics 14-3, 14-11
downloading software 5-9, 12-1, 12-4, 26-10
DSCP, priority mapping 25-14, 25-15
dynamic addresses, displaying 20-3
1Q trunk 22-18
A
ACL
configuration guidelines 19-1
Extended IP 19-1, 19-4, 19-8
MAC 19-1, 19-4, 19-16–19-18
Standard IP 19-1, 19-4, 19-6
address table 20-1
E
edge port, STP 21-17, 21-19
error message logging 7-3
Event
Syslog A-2
B
F
BOOTP 5-21, 5-23, 5-24, 6-2
broadcast storm, threshold 17-24, 17-25
Buffer
Syslog A-8
Facility
Syslog A-8
firmware version, displaying 5-12
firmware, upgrading 5-9, 12-1, 12-4, 26-10
flow control, configuration 17-12, 17-17
C
calender set 8-6
Class of Service
configuring 25-1
Layer 3/4 mapping 25-9
port priority 25-2, 25-3
queue mapping 25-1, 25-4
community string 2-6, 10-3, 10-4
community VLANs 23-2
configuration settings, saving or restoring 5-9, 12-3, 12-4,
12-6, 26-10
console port pin assignments E-1
D
default priority, ingress port 25-2
default settings 2-9
DHCP 5-21, 5-23, 5-24, 6-2
December 2007
G
GARP timers, setting 22-17
GARP VLAN Registration Protocol See GVRP
GVRP 22-3, 22-17
GVRP, global setting 22-4
H
hardware version, displaying 5-12
HTTP, secure server 5-26, 5-28
HTTPS 5-26, 5-28
I
IEEE 802.1D 21-1
© 2007 Foundry Networks, Inc.
Index-1
Foundry EdgeIron User Guide
IEEE 802.1Q 22-3
IEEE 802.1w 21-1
IGMP snooping 26-2
IGMP, configuring 26-1
ingress filtering 22-18
IP address
BOOTP/DHCP service 5-21, 5-23, 5-24, 6-2
setting 5-19, 5-21, 5-24, 6-2
IP DSCP mapping 25-14, 25-15
IP port mapping 25-17, 25-18
IP precedence mapping 25-11, 25-12
L
LACP 18-3
link aggregation 18-1, 18-2
link type, STP 21-16
logging
configuring 7-3
enabling 7-3
syslog traps 7-7
to syslog servers 7-6
log-in
CLI 3-2
Web interface 4-2
logon authentication
RADIUS server 9-5, 9-13
TACACS server 9-5, 9-11, 9-13
logon authentication, sequence 9-8
M
main menu 4-3
mirror port, configuring 17-26
multicast
configuring 26-1
IGMP query 26-2
IGMP snooping 26-2
registration table 26-6, 26-12
router 26-9, 26-11
P
passwords
administrator setting 9-2
path cost method 21-9, 21-13
pin assignments
25-pin DTE port E-2
9-pin DTE port E-2
console port E-1
port configuration
autonegotiation 17-12, 17-15
capabilities 17-12, 17-16
flow control 17-12, 17-17
port priority
configuring 25-1, 25-3
default ingress 25-2
port security, configuring 17-20
Index-2
priority
default port ingress 25-2
IP DSCP 25-14, 25-15
IP port 25-17, 25-18
IP precedence 25-11, 25-12
Layer 3/4 mapping 25-9
priority, STP 21-9, 21-13
problems, troubleshooting C-1
prompt, configuring for CLI 3-11
protocol migration 21-19
Q
querier, IGMP snooping 26-2, 26-6
R
RADIUS 9-1, 9-5
rate limits, setting 17-29
remote logging 7-7
RSTP, global configuration 21-7
S
Secure Shell configuration 13-10, 13-11, 13-12
Secure Socket Layer See SSL
serial port, configuring 11-1
show marker 8-6
SNMP 10-1
community string 10-3, 10-4
enabling traps 10-4, 10-10
filtering IP addresses 16-1
Syslog A-2
trap manager 10-4, 10-8
snooping, IGMP 26-2
software downloads 5-9, 12-1, 12-4, 26-10
software version, displaying 5-12
Spanning Tree Protocol 21-1, 22-1, 23-1, 24-1, 25-1, 26-1
Spanning Tree Type 21-8
SSH, configuring 13-10, 13-11, 13-12
SSL 5-28
stacking
inserting optional modules 27-10
introduction 27-1
maximum stack size 27-1
renumbering units 27-11
single IP management 27-12
special stacking mode 27-7
system initialization 27-7
Stacking Technology 27-1
startup files
displaying 12-1, 12-7
setting 12-1, 12-6
statistics, switch 17-7, 17-31, 17-34
STP 21-10
configuring interfaces 21-17
edge port 21-17, 21-19
interface settings 21-5, 21-15
© 2007 Foundry Networks, Inc.
December 2007
Index
link type 21-16
path cost 21-13, 21-17, 21-18
path cost method 21-9
priority 21-9, 21-13
protocol migration 21-19
Syslog A-2
buffer A-8
changing facility A-8
server A-7
system clock, setting 8-2
System Logs 7-8
system software, downloading from server 5-9, 12-1,
12-4, 26-10
T
TACACS 9-1, 9-5
tagged frames, VLAN 22-3
time, setting 8-2
Trap
Syslog A-2
trap manager 2-7, 10-4, 10-8
troubleshooting C-1
trunk
configuration 18-1, 18-2
static 17-35
December 2007
U
untagged VLANs 22-3
upgrading software 5-9, 12-1, 12-4, 26-10, D-1
user password 9-2
V
VLANs
adding interfaces 22-11, 22-15
creating 22-9
current table 22-6
forbidden 22-12, 22-21
ingress filtering 22-20
interface configuration 22-17
protocol 24-1
W
Web interface
access requirements 4-1
configuration buttons 4-2
home page 4-2
menu list 4-3
panel display 4-3
© 2007 Foundry Networks, Inc.
Index-3
Foundry EdgeIron User Guide
Index-4
© 2007 Foundry Networks, Inc.
December 2007
">