photocopying, recording, taping or storage in an information retrieval system – without prior written permission of the
copyright owner.
The trademarks, logos and servi ce marks (“M arks”) displ ayed he rein are the pro perty of Fou ndry or othe r third p arties.
You are not permitted to use these Marks without the prior written consent of Foundry or such appropriate third party.
Foundry Networks, BigIron, FastIron, IronView, JetCore, NetIron, ServerIron, TurboIron, IronWare, EdgeIron,
IronPoint, AccessIron, 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.
F-Secure is a trademark of F-Se cure Corporat ion. All other trademar ks mentio ned in this doc ument are the property of
ISTOF FEATURES .....................................................................................................................................1-2
OWTO GET HELP ........................................................... ....... ...... ...... ....... ....................................... .........1-5
OMMAND HELP ............................................ ................................................... ..........................................2-4
This guide describes how to configure the AccessIron routers in typical scenarios using information presented in
the configurations and user guides.
Audience
This manual is desi gned f or system ad ministrat ors with a working kn owledg e of Layer 2 and Layer 3 switchin g and
routing.
If you are using a Foundry Layer 3 Switch, you should be familiar with the following protocols if applicable to your
network – IP, RIP, OSPF, BGP4, PIM, and VRRP.
Nomenclature
This guide uses the following typographical conventions to show information:
Italichighlights the title of another publication and occasionally emphasizes a word or phrase.
Boldhighlights a CLI command.
Bold Italichighlights a term that is being defined.
Underline
Capitalshighlights field names and buttons that appear in the Web management interface.
NOTE: A note emphasizes an important fact or calls your attention to a dependency.
WARNING: A warning calls your attention to a possible hazard that can cause injury or death.
CAUTION:A caution calls your attention to a possible hazard that can damage equipment.
highlights a link on the Web management interface.
The following Foundry Networks documents supplement the information in this guide.
•Release Notes
Printed release notes provide th e latest i nformatio n. If releas e notes a re provide d with you r product, fo llow th e
instructions contained within them instead of those provided in other documentation.
•Foundry AR-Series AR1202 and AR1204 Installation Guide
This guide is designed to assist users with the initial installation and deployment of the Foundry AR1202 two-
port and AR1204 four-port router. The guide provides a brief overview of the installation and initial
configuration proces se s.
•Foundry AR-Series AR1202 and AR1204 Quick Installation Guide
This detailed guide provides an abbreviated install guide for those experienced with installing Foundry
AccessIron routers.
•Foundry AR-Series Rack-Mounted Router Installation Guide
This guide is designed to assist users with the initial installation and deployment of Foundry rack-mounted
routers. The guide provides a brief overview of the installation and initial configuration processes.
BGP4 Multi-homing
Bundle Tracking
MLPPP Bundle Thresholding
LAN Interface Load Sharing with Failover
Security/
Management
Stateful Packet Inspection Firewall with:
Layer-3 mode (router and NAT)
Policy-based NAT/PAT
Policy-based filters
URL and application content filtering
Time and rate limiting
Denial of Service protection
Network attack detection
Application Level Gateway support
Packet-level logging and syslog support
Table 1.1: Feature Supported in AccessIron Devices (Continued)
Getting Started
CategoryFeatureAR1202
AR1204
AR1208
AR1216
Timed Access List
AR3201-T-CL
AR3202-T-CL
AR3201-T-CH
AR3202-T-CH
How to Get Help
Foundry Networks technical support will ensure that the fast and easy access that you have come to expect from
your Foundry Networks products will be maintained.
Web Access
•http://www.foundrynetworks.com
Email Access
Technical requests can also be sent to the following email address:
•support@foundrynet.com
Teleph one Access
•1.877.TURBOCALL (887.2622) United States
•1.408.586.1881Outside the United States
Warranty Cove rage
Contact Foundry Networks using a ny of the methods listed above for informati on about t he sta ndard and extended
warranties.
This chapter introduces the Command Line Interface (CLI) hierarchy and the conventions used to describe it. It
also introduces the CLI navigation keys and methods, as well as the available help screens.
Command Types
This guide contains two types of commands: transition, or mode change, commands and standard commands.
Transition commands do not affect the syst em configuration, they are used to ga in access to lower- or next-level
commands in the CLI hierarchy. Following each transition command is a brief description, a syntax and usage
example, a list of next-level commands, and a list of systems for which the command is applicable.
NOTE: In certain instances, transition commands will select an interface for configuration and access next-level
commands. For example, the configure interface bundle dallas command accesses the configure interface bundle mode and selects or creates the bundle dallas.
Stan da rd comma nds a re u sed t o conf igure t he syst em. Fo llowing ea ch st and ard co mman d is a brie f desc ript ion, a
list of parameters and definitions, a syntax and usage example, a list of related commands, and a list of systems
for which the command is applicable.
Context-Sensitive Commands
Some commands are context-sensitive. Once a module, bundle, or Ethernet port has been selected for
configuration, all further configuration applies only to the selected interface. Table 2.1: shows a context-sensitive
command string for a AR1208 system. In this example, T1 link 1 remains selected for configuration until you exit
from the Foundry-AR1208/con fig ure / mo dul e/t1 # prom pt.
Table 2.1: Context-Sensitive Command Sequence
Context-Sensitive Command StringExample
1 Go into the configuration mode.
1 Specify the type of interface (T1).Foundry-AR1208/configure#module t1
Foundry-AR1208#configure terminal
1 Choose the specific interface (T1 link 1).Foundry-AR1208/configure#module t1 1
1 From now on, al l con figurat ion co mman ds
are for T1 link 1 until y ou exi t from mo dule
configuration or choose another T1 link.
NOTE: Command strings that require identification of a specific interface are context-sensitive.
Command Conventions
Each command is briefly described and then followed by the complete syntax, which is essentially a map of the
command that shows mandatory and optional parameters.
The following tables provide details of the conventions used for syntaxes and examples.
Table 2.2: Syntax Conventions
For SyntaxesWhat it means
normal type Within syntaxes, “normal type” represents required words
that must be entered by the user — except when follo wed by
a parameter setting that is enclosed in angled brackets. In
that case, only enter the parameter setting enclosed in the
angled brackets .
Example 1: Normal type only.
In this example, the user enters the word or argument
(module) appearing in the syntax in “normal type.”
Syntax:
module
Command execution:
module
Example 2: Normal type word or argument that is followed
by a second normal type word or argument, which is
followed by a p aram eter setting enclose d i n a ngl ed bra ck et s .
In this example, the user enters the first word or argument
“connections,” appearing in normal type, and then only
enters the value “4” of the second word or argument.
Syntax:
connections connections < n >
Command execution:
connections 4
In other words, the first occurence of “connections” must be
entered because it is not followed by a setting enclosed in
angled brackets. The second occurence of the word
“connections” must NOT be entered bec au se it is followed
by a setting enclosed in angled brackets. This value of the
setting must be entered to execute the command.
[ a | b | c ] Normal brackets “[ ]” indicate optional keywords or
arguments.
A vertical bar “ | “ separates individual settings.
Example:
In this example, the user enters the word “timeout;” must
specify either for “tcp” or “udp” for a protocol type; and
optionally enters a timeout value “n.”
Syntax:
timeout protocol_ty pe < tcp | udp > [ s econds < n > ]
Command execution:
timeout udp 3600
< #Angled brackets. All parameter settings are enclosed in
angled brackets. The user is directed to choose an
appropriate setting. In some cases, the parameter name
accompanies the required setting.
[ ]Optional parameter settings in each syntax are indicated by
normal brackets.
Table 2.3: Example Conventions
For ExamplesWhat it means
normal type Prompts and comman ds that are p art of th e main prompt a re
shown in normal type.
Examples:
Foundry-AR1208#
Foundry-AR1208/show#
bold typeAll character strings that a user must enter to execute a
command are in bold type.
Example:
Foundry-AR1208# configure term
Abbreviated Commands
You may enter commands by typing the first few characters of each word in a command string. The Foundry
system recognizes the unique abbreviated entry and executes the command exactly as if you had entered it fully.
For example, to view the currently running system configuration, you may type show configuration running at
the Foundry# prompt. You may also type discon run to get the same result. Similarly, you may abbreviate the
optional parameter names required by some commands.
For example, a typical entry may be as follows:
mlppp mrru 1600 sequence short seg_threshold 1000 differential_delay 100 discriminator 10.1.100.22
To save time, you may type the following equivalent abbreviated string:
mlppp m 1600 seq short seg 1000 diff 100 dis 10.1.100.22
The Tab, Esc, and Ctrl keyboard keys may be used to:
•Move backwards or forwards in the CLI
•Edit entered command strings
•Or acceler ate the command entry process
Navigation Keys
You may use the Tab key to quickly enter each word of a command without typing its full name. For example, to
enter the configure command, you may type its first two letters and then press Tab to complete the entire word.
Then, you may specify an item to configure by pressing the Spacebar and then pressing Tab repeatedly until the
desired sub-command appears. Repeat this sequence for each successive sub-command string until the entire
command string appears.
You may also use the other keystrokes shown in during command entry. For example, to back up the cursor
without deleting any charac ters, type Ctrl-B. To repeat the last command that yo u entered , type Ctrl-P. T o go back
several commands, type Ctrl-P repeatedly until the desired previous command appears. Or, you may go directly
back to the main CLI# prompt from anywhere in the command hierarchy by typing Ctrl-Z.
Figure 2.1Navigation Keys
# help edit
key stroke -- action
---------- -- ----- TAB -- command completion
Esc-B -- go back one word
Esc-F -- forward one word
Esc-DEL -- delete one word left to cursor
BackSpace -- go back and delete one char
Ctrl-A -- start of line
Ctrl-B / <- -- go back one char
Ctrl-D / DEL -- delete a char
-- go up one level if empty command
Ctrl-E -- end of line
Ctrl-F / -# -- forward one char
Ctrl-K -- delete line ahead of cursor
Ctrl-L -- refresh line
Ctrl-N / DN ARROW -- next command in history
Ctrl-P / UP ARROW -- previous command in history
Ctrl-U -- delete entire line
Ctrl-W -- delete one word left to cursor
#
Command Help
Command help is availa ble for navi gating the C LI command hi erarchy and for assist ance w ith specific command s.
You may obtain help by using any of the three commands described below.
Help
Type help at the main CLI prompt to see the basic Foundry system help information. Or, type help followed by a
command name to view information about that command. shows the help screen.
# help
? -- display commands under this tree
exit [level] -- exit (level nos ) from the current tree
-- 'exit' from "top level" terminates CLI
Ctrl-Z -- exit to top level
tree -- display tree under current node
type 'help edit' to see editing features
type 'help <cmd#' to get help for that command
#
Tree
You may view a tree that shows all CLI commands, or a tree that shows only the commands associated with the
current command mode (or th e rout ing mode for example). Figure 2.3 sh ow s two comma nd tree ex am ple s. If y ou
type tree at the main (Foundry-AR1208# or equivalent) prompt, the entire list of system commands appears. If
you type tree within a com ma nd mo de, such as Foundry-AR3201-CH/clear# tree, the com mand s associa ted with
this command mode are displayed.
To view help information for a command cate gory, specific command, or a parameter, type the associated word
followed by a space and a question mark (?). For example, if you type a question mark at the main command
prompt, the system command categories appear. Shows a display of these top-level commands.
DESCRIPTION
COMMANDS -- Any of the following commands can be used
clear -- access clear commands
configure -- configure from ( flash / network / terminal )
debug -- accesses debug commands
dir -- directory of files in flash
erase -- access erase filesystem commands
file -- access file commands
mtrace -- multicast trace route to source address
password -- Change the user password
ping -- invoke ping
reboot -- reboot the system
reload -- reboot the system
save -- save configuration to ( local / network )
show -- access show commands
tclsh -- To invoke TCL shell
telnet -- open a telnet connection
test -- access test commands
trace -- trace route to destination address or host name
write -- write to terminal/network/flash
#
NOTE: The default parameters for specific commands appear in parenthesis.
Global Commands
All show, ping, and save commands are available from any level of the CLI. For example, the global show
commands allow the user to view current configuration settings, alarms, or tests without exiting the configure
mode. In Figure 2.5 on page 2-7, a user has displayed a bundle summary while configuring a new bundle.
Similarly, the ping and save commands are available at any level of the CLI command. The ping command
verifies connectivity between the Foundry system and other network hosts; access to the save commands from
anywhere in the CLI ensur es that your c onfigurati ons may be save d periodically.
This command configures the autonomous system path filter for BGP.
AS path access li sts are used for matching the AS path attribute in a BGP route. An AS path access lis t s ucce eds
if any “permit” line in the list m atches, o r fails if a ny “deny” l ine matc hes. Matchin g proceed s sequen tially an d stops
at the first match.
The regular expressio n p a ram ete r is an a s path regular expression. (For regular expressio n syntax, see “AS Path
Regular Expressions” on page 13-1.) Note that the regular expression must be enclosed in quotation marks. The
AS number is the smallest element of a Foundry regular expression. It is an integer ranging from 0 to 65536; the
Foundry regular expression matcher is AS number-based.
Any number of AS path access list lines may be declared. They are evaluated in the order declared. If neither
permit nor deny is specified, the default is “permit.”
Parameter Description
access_listAccess list number
Range is 1 - 199.
numberSequence to insert or delete from an existing AS path entry.
Range is 0 - 65535.
action
denyDeny AS path.
permitPermit AS path.
regular_expressionRegular expression to match the AS paths.
Enter a quot ed string.
Refer to “AS Path Regular Expressions” on page 13-1 for more
information about regular expressions.
syntax:
[ no ] policy as_path access_list < n > number < n > action < deny | permit > regular_expression < “string” >
This command accesses next-level commands for adding extended or standard community lists.
Community list s are used for m atchin g the “com muni ty” attrib ute in a BGP rou te. A comm unity list su cceed s if any
“permit” line in the list matches, or fails if any “deny” line matches. Matching proceeds sequentially and stops at
the first match. A line in a community list is normally said to match if the route being tested contains at least all of
the communities listed in the line. That is, it may contain additional communities as well. If the exact-match
keyword is used, then it must contai8n exactly the same communities as listed.
The communities pa rameter can be:
•local_as
•no_advertise
•no_export
•aa:nn (an integer between 0 and 65,535)
•community (an integer between 1 and 4294967295
Note that “exact_m atc h” is su ppo rted in the community_list as well as at the route_map lev el. If n ei ther permit nor
deny is specified, the default is pe rmi t. If n o community is specified, any route w il l b e ma tch ed, regardless of what
communities are present. The route will even be matched if the community path attribute is not present. Any
number of community list lines may be declared. They are evaluated in the order declared.
This command configures the IP access list for routes.
Ip access lists are used for matching any type of route prefix. An IP access list is said to succeed if any “permit”
line in the list matc hes, or fails, if any “deny” line matches. Matching proceeds sequentially and stops at the first
match. A line in an IP access list is said to match according to the rules listed below.
•network netmask
Matches addresses as fo llow s: The bi t s in t he add ress p art of the ro ute be ing ma sked that ar e not c overed by
“one” bits in net mask must be equal to the corresponding bits in network. The “one” bits in net mask are
sometimes referred to as “don’t care” bits, because the policy engine does not care what their values are.
•network netmask mask maskmask
Matches addresses as follows: The first pair of parameters (network, maskmask) match the address part of
the route just as in the previous (network netmask) form. The second pair of parameters (mask, maskmask)
are used to match against the mask part of the route being matched in a similar fashion. That is, the route is
matched if the address part matches and the bits in the mask that are not covered by “one” bits in net mask
are equal to the corresponding bits in mask.
If neither permit nor deny is specified, the default is permit. All kinds of access_list entries may be mixed freely
within a list, and there are no restrictions on what the access_list number may be. Any number of IP access list
lines may be declared. They are evaluated in the order declared.
Parameter Description
access_listAccess list number
The range is 1 - 99
numberSequence to insert to or delete from an existing access list entry.
The range is 0 - 65535.
action
denyRoute map deny set operation.
permitRoute map permit set operation.
networkNetwork route (IP address in dotted notation)
netmaskNetwork mask as wildcard bits (IP address in dotted notation)
maskNetwork route’s mask (IP address in dotted notation)
maskmaskWildcard mask for network route’s mask ( in dotted notation)
syntax:
[ no ] policy ip_access_list access_list < n > number < n > action < deny | permit > [ network < IP address > ] [
netmask < IP address > ] [ mask < IP address > ] [ maskmask < IP address > ]