intellectual property laws. Dell™ and the Dell logo are trademarks of Dell Inc. in the United States and/or other
jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
2014 - 07
Rev. A00
Page 3
Contents
1 About this Guide..................................................................................................31
IP Prefix Lists......................................................................................................................................109
This guide describes the protocols and features the Dell Networking Operating System (OS) supports and
provides configuration instructions and examples for implementing them. This guide supports the Z9000
platform.
The Z9000 platform is available with Dell Networking OS version 8.3.11.1 and beyond.
Though this guide contains information on protocols, it is not intended to be a complete reference. This
guide is a reference for configuring protocols on Dell Networking systems. For complete information
about protocols, refer to related documentation, including IETF requests for comments (RFCs). The
instructions in this guide cite relevant RFCs. The Standards Compliance chapter contains a complete list
of the supported RFCs and management information base files (MIBs).
Audience
This document is intended for system administrators who are responsible for configuring and maintaining
networks and assumes knowledge in Layer 2 and Layer 3 networking technologies.
Conventions
This guide uses the following conventions to describe command syntax.
Keyword
parameterParameters are in italics and require a number or word to be entered in the CLI.
{X}Keywords and parameters within braces must be entered in the CLI.
[X]Keywords and parameters within brackets are optional.
x|yKeywords and parameters separated by a bar require you to choose one option.
x||yKeywords and parameters separated by a double bar allows you to choose any or
Keywords are in Courier (a monospaced font) and must be entered in the CLI as
listed.
all of the options.
Related Documents
•Dell Networking OS Command Reference
•Installing the System
•Dell Quick Start Guide
•Dell Networking OS Release Notes
About this Guide
31
Page 32
2
Configuration Fundamentals
The Dell Networking Operating System (OS) command line interface (CLI) is a text-based interface you
can use to configure interfaces and protocols.
The CLI is largely the same for the Z9000, S6000, S4810, and S4820T except for some commands and
command outputs. The CLI is structured in modes for security and management purposes. Different sets
of commands are available in each mode, and you can limit user access to modes using privilege levels.
In Dell Networking OS, after you enable a command, it is entered into the running configuration file. You
can view the current configuration for the whole system or for a particular CLI mode. To save the current
configuration, copy the running configuration to another location.
NOTE: Due to differences in hardware architecture and continued system development, features
may occasionally differ between the platforms. Differences are noted in each CLI description and
related documentation.
Accessing the Command Line
Access the CLI through a serial console port or a Telnet session.
When the system successfully boots, enter the command line in EXEC mode.
NOTE: You must have a password configured on a virtual terminal line before you can Telnet into
the system. Therefore, you must use a console connection when connecting to the system for the
first time.
telnet 172.31.1.53
Trying 172.31.1.53...
Connected to 172.31.1.53.
Escape character is '^]'.
Login: username
Password:
Dell>
CLI Modes
Different sets of commands are available in each mode.
A command found in one mode cannot be executed from another mode (except for EXEC mode
commands with a preceding do command (refer to the do Command section).
You can set user access rights to commands and command modes using privilege levels;
The Dell Networking OS CLI is divided into three major mode levels:
•EXEC mode is the default mode and has a privilege level of 1, which is the most restricted level. Only a
limited selection of commands is available, notably the show commands, which allow you to view
system information.
32
Configuration Fundamentals
Page 33
•EXEC Privilege mode has commands to view configurations, clear counters, manage configuration
files, run diagnostics, and enable or disable debug operations. The privilege level is 15, which is
unrestricted. You can configure a password for this mode; refer to the Configure the Enable Password
section in the Getting Started chapter.
•CONFIGURATION mode allows you to configure security features, time settings, set logging and
SNMP functions, configure static ARP and MAC addresses, and set line cards on the system.
Beneath CONFIGURATION mode are submodes that apply to interfaces, protocols, and features. The
following example shows the submode command structure. Two sub-CONFIGURATION modes are
important when configuring the chassis for the first time:
•INTERFACE submode is the mode in which you configure Layer 2 and Layer 3 protocols and IP
services specific to an interface. An interface can be physical (Management interface, 1 Gigabit
Ethernet, or 10 Gigabit Ethernet, or synchronous optical network technologies [SONET]) or logical
(Loopback, Null, port channel, or virtual local area network [VLAN]).
•LINE submode is the mode in which you to configure the console and virtual terminal lines.
NOTE: At any time, entering a question mark (?) displays the available command options. For
example, when you are in CONFIGURATION mode, entering the question mark first lists all available
commands, including the possible submodes.
The CLI modes are:
EXEC
EXEC Privilege
CONFIGURATION
AS-PATH ACL
CONTROL-PLANE
CLASS-MAP
DCB POLICY
DHCP
DHCP POOL
ECMP-GROUP
EXTENDED COMMUNITY
FRRP
INTERFACE
GIGABIT ETHERNET
10 GIGABIT ETHERNET
40 GIGABIT ETHERNET
INTERFACE RANGE
LOOPBACK
MANAGEMENT ETHERNET
NULL
PORT-CHANNEL
TUNNEL
VLAN
VRRP
IP
IPv6
IP COMMUNITY-LIST
IP ACCESS-LIST
STANDARD ACCESS-LIST
EXTENDED ACCESS-LIST
MAC ACCESS-LIST
LINE
AUXILLIARY
CONSOLE
VIRTUAL TERMINAL
LLDP
LLDP MANAGEMENT INTERFACE
The Dell Networking OS prompt changes to indicate the CLI mode.
The following table lists the CLI mode, its prompt, and information about how to access and exit the CLI
mode. Move linearly through the command modes, except for the end command which takes you
directly to EXEC Privilege mode and the exit command which moves you up one command mode level.
NOTE: Sub-CONFIGURATION modes all have the letters “conf” in the prompt with more modifiers
to identify the mode and slot/port information.
Table 1. Dell Networking OS Command Modes
CLI Command ModePromptAccess Command
EXEC
EXEC Privilege
CONFIGURATION
NOTE: Access all of the
following modes from
CONFIGURATION mode.
Dell>
Dell#
Dell(conf)#
Access the router through the
console or Telnet.
•From EXEC mode, enter the
enable command.
•From any other mode, use
the end command.
•From EXEC privilege mode,
enter the configure
command.
•From every mode except
EXEC and EXEC Privilege,
enter the exit command.
34
Configuration Fundamentals
Page 35
CLI Command ModePromptAccess Command
AS-PATH ACL
Gigabit Ethernet Interface
10 Gigabit Ethernet Interface
Interface Group
Interface Range
Loopback Interface
Management Ethernet Interface
Null Interface
Port-channel Interface
Tunnel Interface
VLAN Interface
STANDARD ACCESS-LIST
EXTENDED ACCESS-LIST
IP COMMUNITY-LIST
Dell(config-as-path)#ip as-path access-list
Dell(conf-if-gi-0/0)#
Dell(conf-if-te-0/1–2)#
interface (INTERFACE modes)
interface (INTERFACE modes)
Dell(conf-if-group)#interface(INTERFACE
modes)
Dell(conf-if-range)#
Dell(conf-if-lo-0)#
Dell(conf-if-ma-0/0)#
Dell(conf-if-nu-0)#
Dell(conf-if-po-1)#
Dell(conf-if-tu-1)#
Dell(conf-if-vl-1)#
Dell(config-std-nacl)#
interface (INTERFACE modes)
interface (INTERFACE modes)
interface (INTERFACE modes)
interface (INTERFACE modes)
interface (INTERFACE modes)
interface (INTERFACE modes)
interface (INTERFACE modes)
ip access-list standard (IP
ACCESS-LIST Modes)
Dell(config-ext-nacl)#
ip access-list extended (IP
ACCESS-LIST Modes)
Dell(config-community-
ip community-list
list)#
AUXILIARY
CONSOLE
VIRTUAL TERMINAL
STANDARD ACCESS-LIST
EXTENDED ACCESS-LIST
MULTIPLE SPANNING TREE
Per-VLAN SPANNING TREE Plus
PREFIX-LIST
RAPID SPANNING TREE
REDIRECT
ROUTE-MAP
Dell(config-line-aux)#
Dell(config-line-
line (LINE Modes)
line (LINE Modes)
console)#
Dell(config-line-vty)#
line (LINE Modes)
Dell(config-std-macl)#mac access-list standard
(MAC ACCESS-LIST Modes)
Dell(config-ext-macl)#mac access-list extended
(MAC ACCESS-LIST Modes)
Dell(config-mstp)#protocol spanning-tree
mstp
Dell(config-pvst)#protocol spanning-tree
pvst
Dell(conf-nprefixl)#ip prefix-list
Dell(config-rstp)#protocol spanning-tree
rstp
Dell(conf-redirect-list)# ip redirect-list
Dell(config-route-map)#route-map
Configuration Fundamentals
35
Page 36
CLI Command ModePromptAccess Command
ROUTER BGP
BGP ADDRESS-FAMILY
Dell(conf-router_bgp)#router bgp
Dell(conf-router_bgp_af)#
(for IPv4)
Dell(confrouterZ_bgpv6_af)# (for IPv6)
ROUTER ISIS
ISIS ADDRESS-FAMILY
Dell(conf-router_isis)#router isis
Dell(conf-router_isisaf_ipv6)#
ROUTER OSPF
ROUTER OSPFV3
Dell(conf-router_ospf)#router ospf
Dell(confipv6router_ospf)#
ROUTER RIP
SPANNING TREE
TRACE-LIST
CLASS-MAP
CONTROL-PLANE
Dell(conf-router_rip)#router rip
Dell(config-span)#protocol spanning-tree 0
Dell(conf-trace-acl)#ip trace-list
Dell(config-class-map)#class-map
Dell(conf-controlcpuqos)#
DCB POLICYDell(conf-dcb-in)# (for input
policy)
Dell(conf-dcb-out)# (for
output policy)
address-family {ipv4
multicast | ipv6 unicast}
(ROUTER BGP Mode)
address-family ipv6
unicast (ROUTER ISIS Mode)
ipv6 router ospf
control-plane-cpuqos
dcb-input for input policy
dcb-output for output policy
DHCP
DHCP POOL
Dell(config-dhcp)#ip dhcp server
Dell(config-dhcp-pool-name)#
ECMP
Dell(conf-ecmp-groupecmp-group-id)#
EIS
FRRP
Dell(conf-mgmt-eis)#management egress-
Dell(conf-frrp-ring-id)#protocol frrp
LLDPDell(conf-lldp)# or
Dell(conf-if—interfacelldp)#
LLDP MANAGEMENT INTERFACE
LINE
Dell(conf-lldp-mgmtIf)#
Dell(config-line-console)
or Dell(config-line-vty)
36
pool (DHCP Mode)
ecmp-group
interface-selection
protocol lldp
(CONFIGURATION or INTERFACE
Modes)
management-interface (LLDP
Mode)
line console orline vty
Configuration Fundamentals
Page 37
CLI Command ModePromptAccess Command
MONITOR SESSION
OPENFLOW INSTANCE
PORT-CHANNEL FAILOVERGROUP
PRIORITY GROUP
PROTOCOL GVRP
QOS POLICY
VLT DOMAIN
VRRP
Grubgrub>Press the Esc key when the
UPLINK STATE GROUP
Dell(conf-mon-sesssessionID)#
Dell(conf-of-instance-of-id)#
Dell(conf-po-failovergrp)#
Dell(conf-pg)#priority-group
Dell(config-gvrp)#protocol gvrp
Dell(conf-qos-policy-outets)#
Dell(conf-vlt-domain)#vlt domain
Dell(conf-if-interface-
type-slot/port-vrid-vrrpgroup-id)#
Dell(conf-uplink-stategroup-groupID)#
monitor session
openflow of-instance
port-channel failovergroup
qos-policy-output
vrrp-group
following line appears on the
console during a system boot:
Hit any key to stop
autoboot:
uplink-state-group
The following example shows how to change the command mode from CONFIGURATION mode to
PROTOCOL SPANNING TREE.
You can enter an EXEC mode command from any CONFIGURATION mode (CONFIGURATION,
INTERFACE, SPANNING TREE, and so on.) without having to return to EXEC mode by preceding the EXEC
mode command with the
The following example shows the output of the do command.
--- 0 Management online S4810 S4810 9.4(0.0) 64
1 Member not present
2 Member not present
3 Member not present
4 Member not present
5 Member not present
6 Member not present
7 Member not present
8 Member not present
9 Member not present
10 Member not present
11 Member not present
-- Power Supplies -Unit Bay Status Type FanStatus
-------------------------------------------------------------------------- 0 0 absent absent
0 1 up UNKNOWN up
-- Fan Status -Unit Bay TrayStatus Fan0 Speed Fan1 Speed
--- 0 0 up up 9120 up 9120
0 1 up up 9120 up 9120
Speed in RPM
Dell(conf)#
Undoing Commands
When you enter a command, the command line is added to the running configuration file (runningconfig).
To disable a command and remove it from the running-config, enter the no command, then the original
command. For example, to delete an IP address configured on an interface, use the no ip address ip-address command.
NOTE: Use the help or ? command as described in Obtaining Help.
Example of Viewing Disabled Commands
Dell(conf)#interface tengigabitethernet 4/17
Dell(conf-if-te-4/17)#ip address 192.168.10.1/24
Dell(conf-if-te-4/17)#show config
!
interface tenGigabitEthernet 4/17
ip address 192.168.10.1/24
no shutdown
Dell(conf-if-te-4/17)#no ip address
Dell(conf-if-te-4/17)#show config
!
interface tenGigabitEthernet 4/17
no ip address
no shutdown
38
Configuration Fundamentals
Page 39
Layer 2 protocols are disabled by default. To enable Layer 2 protocols, use the no disable command.
For example, in PROTOCOL SPANNING TREE mode, enter no disable to enable Spanning Tree.
Obtaining Help
Obtain a list of keywords and a brief functional description of those keywords at any CLI mode using
the
? or help command:
•To list the keywords available in the current mode, enter ? at the prompt or after a keyword.
•Enter ? after a prompt lists all of the available keywords. The output of this command is the same for
the help command.
Dell#?
cd Change current directory
clear Reset functions
clock Manage the system clock
configure Configuring from terminal
copy Copy from one file to another
debug Debug functions
--More--
•Enter ? after a partial keyword lists all of the keywords that begin with the specified letters.
Dell(conf)#cl?
class-map
clock
Dell(conf)#cl
•Enter [space]? after a keyword lists all of the keywords that can follow the specified keyword.
Dell(conf)#clock ?
summer-time Configure summer (daylight savings) time
timezone Configure time zone
Dell(conf)#clock
Entering and Editing Commands
Notes for entering commands.
•The CLI is not case-sensitive.
•You can enter partial CLI keywords.
– Enter the minimum number of letters to uniquely identify a command. For example, you cannot
enter cl as a partial keyword because both the clock and class-map commands begin with the
letters “cl.” You can enter clo, however, as a partial keyword because only one command begins
with those three letters.
•The TAB key auto-completes keywords in commands. Enter the minimum number of letters to
uniquely identify a command.
•The UP and DOWN arrow keys display previously entered commands (refer to Command History).
•The BACKSPACE and DELETE keys erase the previous letter.
•Key combinations are available to move quickly across the command line. The following table
describes these short-cut key combinations.
Short-Cut Key
Combination
CNTL-AMoves the cursor to the beginning of the command line.
Action
Configuration Fundamentals
39
Page 40
Short-Cut Key
Combination
CNTL-BMoves the cursor back one character.
CNTL-DDeletes character at cursor.
CNTL-EMoves the cursor to the end of the line.
CNTL-FMoves the cursor forward one character.
CNTL-ICompletes a keyword.
CNTL-KDeletes all characters from the cursor to the end of the command line.
CNTL-LRe-enters the previous command.
CNTL-NReturn to more recent commands in the history buffer after recalling commands
CNTL-PRecalls commands, beginning with the last command.
CNTL-RRe-enters the previous command.
CNTL-UDeletes the line.
CNTL-WDeletes the previous word.
CNTL-XDeletes the line.
CNTL-ZEnds continuous scrolling of command outputs.
Action
with CTRL-P or the UP arrow key.
Esc BMoves the cursor back one word.
Esc FMoves the cursor forward one word.
Esc DDeletes all characters from the cursor to the end of the word.
Command History
Dell Networking OS maintains a history of previously-entered commands for each mode. For example:
•When you are in EXEC mode, the UP and DOWN arrow keys display the previously-entered EXEC
mode commands.
•When you are in CONFIGURATION mode, the UP or DOWN arrows keys recall the previously-entered
CONFIGURATION mode commands.
Filtering show Command Outputs
Filter the output of a show command to display specific information by adding | [except | find |
grep | no-more | save]
The variable specified_text is the text for which you are filtering and it IS case sensitive unless you
use the ignore-case sub-option.
Starting with Dell Networking OS version 7.8.1.0, the grep command accepts an ignore-case suboption that forces the search to case-insensitive. For example, the commands:
specified_text after the command.
40
Configuration Fundamentals
Page 41
•show run | grep Ethernet returns a search result with instances containing a capitalized
“Ethernet,” such as interface GigabitEthernet 0/0.
•show run | grep ethernet does not return that search result because it only searches for
instances containing a non-capitalized “ethernet.”
•show run | grep Ethernet ignore-case returns instances containing both “Ethernet” and
“ethernet.”
The grep command displays only the lines containing specified text. The following example shows this
command used in combination with the show linecard all command.
Dell(conf)#do show system brief | grep 0
0 not present
NOTE: Dell Networking OS accepts a space or no space before and after the pipe. To filter a phrase
with spaces, underscores, or ranges, enclose the phrase with double quotation marks.
The except keyword displays text that does not match the specified text. The following example shows
this command used in combination with the
2 not present
3 not present
4 not present
5 not present
6 not present
The find keyword displays the output of the show command beginning from the first occurrence of
specified text. The following example shows this command used in combination with the
show
linecard all command.
Example of the find Keyword
Dell(conf)#do show system brief | find 0
0 not present
1 not present
2 online online E48TB E48TB 1-1-463 48
3 not present
4 not present
5 online online E48VB E48VB 1-1-463 48
6 not present
7 not present
The display command displays additional configuration information.
The no-more command displays the output all at once rather than one screen at a time. This is similar to
the terminal length command except that the no-more option affects the output of the specified
command only.
The save command copies the output to a file for future reference.
Configuration Fundamentals
41
Page 42
NOTE: You can filter a single command output multiple times. The save option must be the last
option entered. For example: Dell# command | grep regular-expression | except
Dell Networking OS notifies all users when there are multiple users logged in to CONFIGURATION mode.
A warning message indicates the username, type of connection (console or VTY), and in the case of a VTY
connection, the IP address of the terminal on which the connection was established. For example:
•On the system that telnets into the switch, this message appears:
% Warning: The following users are currently configuring the system:
User "<username>" on line console0
•On the system that is connected over the console, this message appears:
% Warning: User "<username>" on line vty0 "10.11.130.2" is in configuration
mode
If either of these messages appears, Dell Networking recommends coordinating with the users listed in
the message so that you do not unintentionally overwrite each other’s configuration changes.
42
Configuration Fundamentals
Page 43
3
Data Center Bridging (DCB)
Data center bridging (DCB) is supported on the platform.
NOTE:
SNMP Support for PFC and Buffer Statistics Tracking
Buffer Statistics Tracking (BST) feature provides a mechanism to aid in Resource Monitoring and Tuning
of Buffer Allocation. The support for Max Use Count mode in Buffer Statistics is introduced in Dell
Networking OS 9.3(0.). Max Use Count mode provides the maximum value of the counters accumulated
over a period of time. This feature is supported in Z9000.
Priority Flow Control (PFC) provides a link level flow control mechanism, which is controlled
independently for each frame priority. The goal of this mechanism is to ensure zero loss under
congestion in DCB networks.
The SNMP support for monitoring PFC and BST counters and statistics is introduced in Dell Networking
OS 9.3(0.1). The enhancement is made on F10-FPSTATS MIB with additional tables to display the PFC and
BST counters and statistics.
The following new tables are added in F10-FPSTATS MIB in Dell Networking OS 9.3(0.1):
•fpEgrQBuffSnapshotTable
•fpIngPgBuffSnapshotTable
•fpStatsPerPgTable
•pfcPerPrioTable
fpEgrQBuffSna
pshotTable
fpIngPgBuffSna
pshotTable
fpStatsPerPgTa
ble
pfcPerPrioTabl
e
Data Center Bridging (DCB)
This table fetches the BST statistics at Egress Port with respect to the buffer used.
This table displays the Snapshot of the Buffer cells used by Unicast and Multicast
Data and Control Queues.
This table fetches the BST statistics at the Ingress Port with respect to the Shared
Cells and the Headroom cells used per Priority Group. The snapshot of the Ingress
Shared cells used and the Ingress Headroom cells used per Priority Group, when
PFC is enabled, will be displayed in this table. This table is indexed by stack-unit
index, port number and the priority group number.
This table fetches the Allocated Min cells, Shared cells and Headroom cells per
Priority Group, the mode in which the buffer cells are allocated - Static or Dynamic
and the Used Min Cells, Shared cells and Headroom cells per Priority Group. The
table fetches a value of 0 if the mode of allocation is Static and a value of 1 if the
mode of allocation is Dynamic. This table is indexed by stack-unit number, port
number and priority group number.
This table fetches the number of PFC frames transmitted (PFC Requests) and the
number of PFC frames received (PFC Indications) per priority on a per port basis.
This table is indexed by the stack-unit index, port number and priority.
43
Page 44
4
Getting Started
This chapter describes how you start configuring your system.
When you power up the chassis, the system performs a power-on self test (POST) during which the line
card status light emitting diodes (LEDs) blink green. The system then loads the Dell Networking Operating
System (OS). Boot messages scroll up the terminal window during this process. No user interaction is
required if the boot process proceeds without interruption.
When the boot process completes, the RPM and line card status LEDs remain online (green) and the
console monitor displays the EXEC mode prompt.
For details about using the command line interface (CLI), refer to the Accessing the Command Line
section in the Configuration Fundamentals chapter.
Console Access
The has two management ports available for system access: a serial console port and an out-of-bounds
(OOB) port. The Z9000 has a primary management (Ethernet) port and an RJ-45/RS-232 console port.
Serial Console
The RJ-45/RS-232 console port is labeled on the Z9000 chassis. It is in the upper right-hand side, as you
face the I/O side of the chassis.
Figure 1. RJ-45 Console Port
1.RJ-45 Console Port
44
Getting Started
Page 45
Accessing the Console Port
To access the console port, follow these steps:
For the console port pinout, refer to Accessing the RJ-45 Console Port with a DB-9 Adapter.
1.Install an RJ-45 copper cable into the console port.Use a rollover (crossover) cable to connect the
S4810 console port to a terminal server.
2.Connect the other end of the cable to the DTE terminal server.
3.Terminal settings on the console port cannot be changed in the software and are set as follows:
•9600 baud rate
•No parity
•8 data bits
•1 stop bit
•No flow control
Pin Assignments
You can connect to the console using a RJ-45 to RJ-45 rollover cable and a RJ-45 to DB-9 female DTE
adapter to a terminal server (for example, a PC).
The pin assignments between the console and a DTE terminal server are as follows:
Table 2. Pin Assignments Between the Console and a DTE Terminal Server
Console PortRJ-45 to RJ-45
Rollover Cable
SignalRJ-45 PinoutRJ-45 PinoutDB-9 PinSignal
RTS188CTS
NC276DSR
TxD362RxD
GND455GND
GND545GND
RxD633TxD
NC724DTR
CTS817RTS
RJ-45 to RJ-45
Rollover Cable
RJ-45 to DB-9
Adapter
Terminal Server
Device
Accessing the CLI Interface and Running Scripts Using
SSH
Z9000
In addition to the capability to access a device using a console connection or a Telnet session, you can
also use SSH for secure, protected communication with the device. You can open an SSH session and run
commands or script files. This method of connectivity is supported with S4810, S4820T, and Z9000
switches and provides a reliable, safe communication mechanism.
Getting Started
45
Page 46
Entering CLI commands Using an SSH Connection
You can run CLI commands by entering any one of the following syntax to connect to a switch using the
preconfigured user credentials using SSH:
ssh username@hostname <CLI Command>
or
echo <CLI Command> | ssh admin@hostname
The SSH server transmits the terminal commands to the CLI shell and the results are displayed on the
screen non-interactively.
Executing Local CLI Scripts Using an SSH Connection
You can execute CLI commands by entering a CLI script in one of the following ways:
ssh username@hostname <CLIscript.file>
or
cat < CLIscript.file > | ssh admin@hostname
The script is run and the actions contained in the script are performed.
Following are the points to remember, when you are trying to establish an SSH session to the device to
run commands or script files:
•There is an upper limit of 10 concurrent sessions in SSH. Therefore, you might expect a failure in
executing SSH-related scripts.
•To avoid denial of service (DoS) attacks, a rate-limit of 10 concurrent sessions per minute in SSH is
devised. Therefore, you might experience a failure in executing SSH-related scripts when multiple
short SSH commands are executed.
•If you issue an interactive command in the SSH session, the behavior may not really be interactive.
•In some cases, when you use an SSH session, when certain show commands such as show tech-
support
truncated and not displayed. This may cause one of the commands to fail for syntax error. In such
cases, if you add few newline characters before the failed command, the output displays completely.
Execution of commands on CLI over SSH does not notice the errors that have occurred while executing
the command. As a result, you cannot identify, whether a command has failed to be processed. The
console output though is redirected back over SSH.
produce large volumes of output, sometimes few characters from the output display are
46
Getting Started
Page 47
Default Configuration
A version of Dell Networking OS is pre-loaded onto the chassis; however, the system is not configured
when you power up for the first time (except for the default hostname, which is Dell). You must
configure the system using the CLI.
Configuring a Host Name
The host name appears in the prompt. The default host name is Dell.
•Host names must start with a letter and end with a letter or digit.
•Characters within the string can be letters, digits, and hyphens.
To create a host name, use the following command.
•Create a host name.
CONFIGURATION mode
hostname name
Example of the hostname Command
Dell(conf)#hostname R1
R1(conf)#
Accessing the System Remotely
You can configure the system to access it remotely by Telnet or SSH.
•The Z9000 has a dedicated management port and a management routing table that is separate from
the IP routing table.
•You can manage all Dell Networking products in-band via the front-end data ports through interfaces
assigned an IP address as well.
Accessing the Z-Series and Remotely
Configuring the system for Telnet is a three-step process, as described in the following topics:
1.Configure an IP address for the management port. Configure the Management Port IP Address
2.Configure a management route with a default gateway. Configure a Management Route
3.Configure a username and password. Configure a Username and Password
Configure the Management Port IP Address
To access the system remotely, assign IP addresses to the management ports.
1.Enter INTERFACE mode for the Management port.
CONFIGURATION mode
interface ManagementEthernet slot/port
•slot: the range is from 0 to 7.
Getting Started
47
Page 48
•port: the range is 0.
2.Assign an IP address to the interface.
INTERFACE mode
ip address ip-address/mask
•ip-address: an address in dotted-decimal format (A.B.C.D).
•mask: a subnet mask in /prefix-length format (/ xx).
3.Enable the interface.
INTERFACE mode
no shutdown
Configure a Management Route
Define a path from the system to the network from which you are accessing the system remotely.
Management routes are separate from IP routes and are only used to manage the system through the
management port.
To configure a management route, use the following command.
•Configure a management route to the network from which you are accessing the system.
CONFIGURATION mode
management route ip-address/mask gateway
– ip-address: the network address in dotted-decimal format (A.B.C.D).
– mask: a subnet mask in /prefix-length format (/ xx).
– gateway: the next hop for network traffic originating from the management port.
Configuring a Username and Password
To access the system remotely, configure a system username and password.
To configure a system username and password, use the following command.
•Configure a username and password to access the system remotely.
CONFIGURATION mode
– level: is the privilege level, is 15 by default, and is not required
– encryption-type: specifies how you are inputting the password, is 0 by default, and is not
required.
* 0 is for inputting the password in clear text.
* 7 is for inputting a password that is already encrypted using a DES hash. Obtain the encrypted
password from the configuration file of another Dell Networking system.
* 5 is for inputting a password that is already encrypted using an MD5 hash. Obtain the
encrypted password from the configuration file of another Dell Networking system.
Configuration File Management
Files can be stored on and accessed from various storage media. Rename, delete, and copy files on the
system from EXEC Privilege mode.
Copy Files to and from the System
The command syntax for copying files is similar to UNIX. The copy command uses the format copy source-file-url destination-file-url.
NOTE: For a detailed description of the copy command, refer to the Dell Networking OS Command Reference.
•To copy a local file to a remote system, combine the file-origin syntax for a local file location with the
file-destination syntax for a remote file location.
•To copy a remote file to Dell Networking system, combine the file-origin syntax for a remote file
location with the file-destination syntax for a local file location.
The running-configuration contains the current system configuration. Dell Networking recommends
coping your running-configuration to the startup-configuration.
The commands in this section follow the same format as those commands in the Copy Files to and from
the System section but use the filenames startup-configuration and running-configuration. These
commands assume that current directory is the internal flash, which is the system default.
•Save the running-configuration to the startup-configuration on the internal flash of the primary RPM.
EXEC Privilege mode
copy running-config startup-config
•Save the running-configuration to the internal flash on an RPM.
EXEC Privilege mode
copy running-config rpm{0|1}flash://filename
•Save the running-configuration to an FTP server.
EXEC Privilege mode
NOTE: When copying to a server, a host name can only be used if a DNS server is configured.
Configure the Overload Bit for a Startup Scenario
For information about setting the router overload bit for a specific period of time after a switch reload is
implemented, refer to the Intermediate System to Intermediate System (IS-IS) section in the Dell Networking OS Command Line Reference Guide.
Viewing Files
You can only view file information and content on local file systems.
To view a list of files or the contents of a file, use the following commands.
•View a list of files on the internal flash.
EXEC Privilege mode
dir flash:
•View the running-configuration.
EXEC Privilege mode
show running-config
•View the startup-configuration.
EXEC Privilege mode
show startup-config
Example of the dir Command
The output of the dir command also shows the read/write privileges, size (in bytes), and date of
modification for each file.
Configuration files have three commented lines at the beginning of the file, as shown in the following
example, to help you track the last time any user made a change to the file, which user made the
changes, and when the file was last saved to the startup-configuration.
In the running-configuration file, if there is a difference between the timestamp on the “Last
configuration change” and “Startup-config last updated,” you have made changes that have not been
saved and are preserved after a system reboot.
Example of the show running-config Command
Dell#show running-config
Current Configuration ...
! Version 9.4(0.0)
! Last configuration change at Tue Mar 11 21:33:56 2014 by admin
! Startup-config last updated at Tue Mar 11 12:11:00 2014 by default
!
boot system stack-unit 0 primary system: B:
boot system stack-unit 0 secondary tftp://10.16.127.35/dt-maa-s4810-2
boot system stack-unit 0 default tftp://10.16.127.35/dt-maa-s4810-2
boot system gateway 10.16.130.254
!
Page 57 - Under Managing the File System, the word external Flash must be
removed
Page 57 - The output of show file-systems must be modified as follows.
The Dell Networking system can use the internal Flash, external Flash, or remote devices to store files.
The system stores files on the internal Flash by default but can be configured to store files elsewhere.
To view file system information, use the following command.
•View information about each file system.
EXEC Privilege mode
show file-systems
The output of the show file-systems command in the following example shows the total capacity,
amount of free memory, file structure, media type, read/write privileges for each storage device in use.
You can change the default file system so that file management commands apply to a particular device
or memory.
To change the default directory, use the following command.
•Change the default directory.
EXEC Privilege mode
cd directory
In the following example, the default storage location is changed to the external Flash of the primary
RPM. File management commands then apply to the external Flash rather than the internal Flash. The
bold lines show that no file system is specified and that the file is saved to an external flash.
Dell#cd slot0:
Dell#copy running-config test
Dell#copy run test
!
7419 bytes successfully copied
Dell#dir
Directory of slot0:
5 ---- 0 Jan 01 1970 00:00:00 BT
6 ---- 0 Jan 01 1970 00:00:00 200702~1VSN
7 ---- 0 Jan 01 1970 00:00:00 G
8 ---- 0 Jan 01 1970 00:00:00 F
9 ---- 0 Jan 01 1970 00:00:00 F
slot0: 127772672 bytes total (21927936 bytes free)
Enabling Software Features on Devices Using a Command
Option
This capability to activate software applications or components on a device using a command is
supported on the S4810, S4820T, and S6000, platforms.
Starting with Release 9.4(0.0), you can enable or disable specific software functionalities or applications
that need to run on a device by using a command attribute in the CLI interface. This capability enables
effective, streamlined management and administration of applications and utilities that run on a device.
You can employ this capability to perform an on-demand activation or turn-off of a software component
or protocol. A feature configuration file that is generated for each image contains feature names denotes
whether this enabling or disabling method is available for such features. In 9.4(0.0), you can enable or
disable the VRF application globally across the system by using this capability.
You can activate VRF application on a device by using the feature vrf command in CONFIGURATION
mode.
NOTE: The no feature vrf command is not supported on any of the platforms.
Getting Started
53
Page 54
To enable the VRF feature and cause all VRF-related commands to be available or viewable in the CLI
interface, use the following command. You must enable the VRF feature before you can configure its
related attributes.
Dell(conf)# feature vrf
Based on whether VRF feature is identified as supported in the Feature Configuration file, configuration
command feature vrf becomes available for usage. This command will be stored in running-configuration
and will precede all other VRF-related configurations.
NOTE: The MXL and Z9000 platforms currently do not support VRF. These platforms support only
the management and default VRFs, which are available by default. As a result, the feature vrf
command is not available for these platforms.
To display the state of Dell Networking OS features:
Dell#show feature
Example of show feature output
For a particular target where VRF is enabled, the show output is similar to the following:
Feature State
------------------------------
VRF enabled
View Command History
The command-history trace feature captures all commands entered by all users of the system with a time
stamp and writes these messages to a dedicated trace log buffer.
The system generates a trace message for each executed command. No password information is saved
to the file.
To view the command-history trace, use the show command-history command.
NOTE: To upgrade Dell Networking Operating System (OS), refer to the Release Notes for the
version you want to load on the system.
54
Getting Started
Page 55
Using HTTP for File Transfers
Stating with Release 9.3(0.1), you can use HTTP to copy files or configuration details to a remote server.
Use the copy source-file-url http://host[:port]/file-path command to transfer files to an external server.
This functionality to transport files using HTTP to a remote server is supported on MXL, I/O Aggregator,
S4810, S4820, S6000, and Z9000 platforms.
Enter the following source-file-url keywords and information:
•To copy a file from the internal FLASH, enter flash:// followed by the filename.
•To copy the running configuration, enter the keyword running-config.
•To copy the startup configuration, enter the keyword startup-config.
•To copy a file on the external FLASH, enter usbflash:// followed by the filename.
Using Hashes to Validate Software Images
You can use the MD5 message-digest algorithm or SHA256 Secure Hash Algorithm to validate the
software image on the flash drive, after the image has been transferred to the system, but before the
image has been installed. The validation calculates a hash value of the downloaded image file on system’s
flash drive, and, optionally, compares it to a Dell Networking published hash for that file.
The MD5 or SHA256 hash provides a method of validating that you have downloaded the original
software. Calculating the hash on the local image file, and comparing the result to the hash published for
that file on iSupport, provides a high level of confidence that the local copy is exactly the same as the
published software image. This validation procedure, and the verify {md5 | sha256} command to support
it, can prevent the installation of corrupted or modified images.
The verify {md5 | sha256} command calculates and displays the hash of any file on the specified local
flash drive. You can compare the displayed hash against the appropriate hash published on i-Support.
Optionally, the published hash can be included in the verify {md5 | sha256} command, which will display
whether it matches the calculated hash of the indicated file.
To validate a software image:
1.Download Dell Networking OS software image file from the iSupport page to the local (FTP or TFTP)
server. The published hash for that file is displayed next to the software image file on the iSupport
page.
2.Go on to the Dell Networking system and copy the software image to the flash drive, using the copy
command.
3.Run the verify {md5 | sha256} [ flash://]img-file [hash-value] command. For example, verify sha256
flash://FTOS-SE-9.5.0.0.bin
4.Compare the generated hash value to the expected hash value published on the iSupport page.
To validate the software image on the flash drive after the image has been transferred to the system, but
before the image has been installed, use the verify {md5 | sha256} [ flash://]img-file [hash-value]
command in EXEC mode.
•md5: MD5 message-digest algorithm
•sha256: SHA256 Secure Hash Algorithm
Getting Started
55
Page 56
•flash: (Optional) Specifies the flash drive. The default is to use the flash drive. You can just enter the
image file name.
•hash-value: (Optional). Specify the relevant hash published on i-Support.
•img-file: Enter the name of the Dell Networking software image file to validate
Examples: Without Entering the Hash Value for Verification
MD5
Dell# verify md5 flash://FTOS-SE-9.5.0.0.bin
MD5 hash for FTOS-SE-9.5.0.0.bin: 275ceb73a4f3118e1d6bcf7d75753459
SHA256
Dell# verify sha256 flash://FTOS-SE-9.5.0.0.bin
SHA256 hash for FTOS-SE-9.5.0.0.bin:
e6328c06faf814e6899ceead219afbf9360e986d692988023b749e6b2093e933
Examples: Entering the Hash Value for Verification
MD5
Dell# verify md5 flash://FTOS-SE-9.5.0.0.bin 275ceb73a4f3118e1d6bcf7d75753459
MD5 hash VERIFIED for FTOS-SE-9.5.0.0.bin
SHA256
Dell# verify sha256 flash://FTOS-SE-9.5.0.0.bin
e6328c06faf814e6899ceead219afbf9360e986d692988023b749e6b2093e933
SHA256 hash VERIFIED for FTOS-SE-9.5.0.0.bin
56
Getting Started
Page 57
5
Management
Management is supported on the Z9000 platform.
This chapter describes the different protocols or services used to manage the Dell Networking system.
Configuring Privilege Levels
Privilege levels restrict access to commands based on user or terminal line.
There are 16 privilege levels, of which three are pre-defined. The default privilege level is 1.
LevelDescription
Level 0Access to the system begins at EXEC mode, and EXEC mode commands are
limited to enable, disable, and exit.
Level 1Access to the system begins at EXEC mode, and all commands are available.
Level 15Access to the system begins at EXEC Privilege mode, and all commands are
available.
Creating a Custom Privilege Level
Custom privilege levels start with the default EXEC mode command set. You can then customize privilege
levels 2-14 by:
•restricting access to an EXEC mode command
•moving commands from EXEC Privilege to EXEC mode
•restricting access
A user can access all commands at his privilege level and below.
Removing a Command from EXEC Mode
To remove a command from the list of available commands in EXEC mode for a specific privilege level,
use the privilege exec command from CONFIGURATION mode.
In the command, specify a level greater than the level given to a user or terminal line, then the first
keyword of each command you wish to restrict.
Moving a Command from EXEC Privilege Mode to EXEC Mode
To move a command from EXEC Privilege to EXEC mode for a privilege level, use the privilege exec
command from CONFIGURATION mode.
In the command, specify the privilege level of the user or terminal line and specify all keywords in the
command to which you want to allow access.
Management
57
Page 58
Allowing Access to CONFIGURATION Mode Commands
To allow access to CONFIGURATION mode, use the privilege exec level level configure
command from CONFIGURATION mode.
A user that enters CONFIGURATION mode remains at his privilege level and has access to only two
commands, end and exit. You must individually specify each CONFIGURATION mode command you
want to allow access to using the privilege configure level level command. In the command,
specify the privilege level of the user or terminal line and specify all the keywords in the command to
which you want to allow access.
Allowing Access to the Following Modes
This section describes how to allow access to the INTERFACE, LINE, ROUTE-MAP, and ROUTER modes.
Similar to allowing access to CONFIGURATION mode, to allow access to INTERFACE, LINE, ROUTE-MAP,
and ROUTER modes, you must first allow access to the command that enters you into the mode. For
example, to allow a user to enter INTERFACE mode, use the privilege configure level level interface gigabitethernet command.
Next, individually identify the INTERFACE, LINE, ROUTE-MAP or ROUTER commands to which you want
to allow access using the privilege {interface | line | route-map | router} level level command. In the command, specify the privilege level of the user or terminal line and specify all
the keywords in the command to which you want to allow access.
To remove, move or allow access, use the following commands.
The configuration in the following example creates privilege level 3. This level:
•removes the resequence command from EXEC mode by requiring a minimum of privilege level 4
•moves the capture bgp-pdu max-buffer-size command from EXEC Privilege to EXEC mode by
requiring a minimum privilege level 3, which is the configured level for VTY 0
•allows access to CONFIGURATION mode with the banner command
•allows access to INTERFACE and LINE modes are allowed with no commands
•Remove a command from the list of available commands in EXEC mode.
CONFIGURATION mode
Dell(conf)#do show run priv
!
privilege exec level 3 capture
privilege exec level 3 configure
privilege exec level 4 resequence
privilege exec level 3 capture bgp-pdu
privilege exec level 3 capture bgp-pdu max-buffer-size
privilege configure level 3 line
privilege configure level 3 interface
Dell(conf)#do telnet 10.11.80.201
[telnet output omitted]
Dell#show priv
Current privilege level is 3.
Dell#?
capture Capture packet
configure Configuring from terminal
disable Turn off privileged commands
enable Turn on privileged commands
exit Exit from the EXEC
ip Global IP subcommands
monitor Monitoring feature
mtrace Trace reverse multicast path from destination to source
ping Send echo messages
quit Exit from the EXEC
show Show running system information
[output omitted]
Dell#config
[output omitted]
Dell(conf)#do show priv
Current privilege level is 3.
Dell(conf)#?
end Exit from configuration mode
exit Exit from configuration mode
interface Select an interface to configure
line Configure a terminal line
linecard Set line card type
Dell(conf)#interface ?
fastethernet Fast Ethernet interface
gigabitethernet Gigabit Ethernet interface
loopback Loopback interface
managementethernet Management Ethernet interface
null Null interface
port-channel Port-channel interface
range Configure interface range
sonet SONET interface
tengigabitethernet TenGigabit Ethernet interface
vlan VLAN interface
Dell(conf)#interface gigabitethernet 1/1
Dell(conf-if-gi-1/1)#?
end Exit from configuration mode
exit Exit from interface configuration mode
Dell(conf-if-gi-1/1)#exit
Dell(conf)#line ?
Management
59
Page 60
aux Auxiliary line
console Primary terminal line
vty Virtual terminal
Dell(conf)#line vty 0
Dell(config-line-vty)#?
exit Exit from line configuration mode
Dell(config-line-vty)#
Dell(conf)#interface group ?
fortyGigE FortyGigabit Ethernet interface
gigabitethernet GigabitEthernet interface IEEE 802.3z
tengigabitethernet TenGigabit Ethernet interface
vlan VLAN keyword
Dell(conf)# interface group vlan 1 - 2 , tengigabitethernet 0/0
Dell(conf-if-group-vl-1-2,te-0/0)# no shutdown
Dell(conf-if-group-vl-1-2,te-0/0)# end
Applying a Privilege Level to a Username
To set the user privilege level, use the following command.
•Configure a privilege level for a user.
CONFIGURATION mode
username username privilege level
Applying a Privilege Level to a Terminal Line
To set a privilege level for a terminal line, use the following command.
•Configure a privilege level for a user.
CONFIGURATION mode
username username privilege level
NOTE: When you assign a privilege level between 2 and 15, access to the system begins at EXEC
mode, but the prompt is
hostname#, rather than hostname>.
Configuring Logging
The Dell Networking OS tracks changes in the system using event and error messages.
By default, Dell Networking OS logs these messages on:
•the internal buffer
•console and terminal lines
•any configured syslog servers
To disable logging, use the following commands.
•Disable all logging except on the console.
CONFIGURATION mode
no logging on
•Disable logging to the logging buffer.
CONFIGURATION mode
no logging buffer
60
Management
Page 61
•Disable logging to terminal lines.
CONFIGURATION mode
no logging monitor
•Disable console logging.
CONFIGURATION mode
no logging console
Audit and Security Logs
This section describes how to configure, display, and clear audit and security logs.
The following is the configuration task list for audit and security logs:
•Enabling Audit and Security Logs
•Displaying Audit and Security Logs
•Clearing Audit Logs
Enabling Audit and Security Logs
You enable audit and security logs to monitor configuration changes or determine if these changes affect
the operation of the system in the network. You log audit and security events to a system log server,
using the
Audit Logs
logging extended command in CONFIGURATION mode.
The audit log contains configuration events and information. The types of information in this log consist
of the following:
•User logins to the switch.
•System events for network issues or system issues.
•Users making configuration changes. The switch logs who made the configuration changes and the
date and time of the change. However, each specific change on the configuration is not logged. Only
that the configuration was modified is logged with the user ID, date, and time of the change.
•Uncontrolled shutdown.
Security Logs
The security log contains security events and information. RBAC restricts access to audit and security logs
based on the CLI sessions’ user roles. The types of information in this log consist of the following:
•Establishment of secure traffic flows, such as SSH.
•Violations on secure flows or certificate issues.
•Adding and deleting of users.
•User access and configuration changes to the security and crypto parameters (not the key
information but the crypto configuration)
Important Points to Remember
Management
61
Page 62
When you enabled RBAC and extended logging:
•Only the system administrator user role can execute this command.
•The system administrator and system security administrator user roles can view security events and
system events.
•The system administrator user roles can view audit, security, and system events.
•Only the system administrator and security administrator user roles can view security logs.
•The network administrator and network operator user roles can view system events.
NOTE: If extended logging is disabled, you can only view system events, regardless of RBAC user
role.
Example of Enabling Audit and Security Logs
Dell(conf)#logging extended
Displaying Audit and Security Logs
To display audit logs, use the show logging auditlog command in Exec mode. To view these logs,
you must first enable the logging extended command. Only the RBAC system administrator user role can
view the audit logs. Only the RBAC security administrator and system administrator user role can view the
security logs. If extended logging is disabled, you can only view system events, regardless of RBAC user
role. To view security logs, use the
Example of the show logging auditlog Command
For information about the logging extended command, see Enabling Audit and Security Logs
show logging command.
Dell#show logging auditlog
May 12 12:20:25: Dell#: %CLI-6-logging extended by admin from vty0 (10.14.1.98)
May 12 12:20:42: Dell#: %CLI-6-configure terminal by admin from vty0
(10.14.1.98)
May 12 12:20:42: Dell#: %CLI-6-service timestamps log datetime by admin from
vty0 (10.14.1.98)
Example of the show logging Command for Security
For information about the logging extended command, see Enabling Audit and Security Logs
Dell#show logging
Jun 10 04:23:40: %STKUNIT0-M:CP
user admin on line vty0 ( 10.14.1.91 )
%SEC-5-LOGIN_SUCCESS: Login successful for
Clearing Audit Logs
To clear audit logs, use the clear logging auditlog command in Exec mode. When RBAC is
enabled, only the system administrator user role can issue this command.
Example of the clear logging auditlog Command
Dell# clear logging auditlog
Configuring Logging Format
To display syslog messages in a RFC 3164 or RFC 5424 format, use the logging version [0 | 1}
command in CONFIGURATION mode. By default, the system log version is set to 0.
62
Management
Page 63
The following describes the two log messages formats:
•0 – Displays syslog messages format as described in RFC 3164, The BSD syslog Protocol
•1 – Displays syslog message format as described in RFC 5424, The SYSLOG Protocol
Example of Configuring the Logging Message Format
Dell(conf)#logging version ?
<0-1> Select syslog version (default = 0)
Dell(conf)#logging version 1
Setting Up a Secure Connection to a Syslog Server
You can use reverse tunneling with the port forwarding to securely connect to a syslog server.
Pre-requisites
To configure a secure connection from the switch to the syslog server:
1.On the switch, enable the SSH server
Dell(conf)#ip ssh server enable
Management
63
Page 64
2.On the syslog server, create a reverse SSH tunnel from the syslog server to FTOS switch, using
following syntax:
ssh -R <remote port>:<syslog server>:<syslog server listen port>
user@remote_host -nNf
In the following example the syslog server IP address is 10.156.166.48 and the listening port is
5141. The switch IP address is 10.16.131.141 and the listening port is 5140
3.Configure logging to a local host. locahost is “127.0.0.1” or “::1”.
If you do not, the system displays an error when you attempt to enable role-based only AAA
authorization.
Dell(conf)# logging localhost tcp port
Dell(conf)#logging 127.0.0.1 tcp 5140
Log Messages in the Internal Buffer
All error messages, except those beginning with %BOOTUP (Message), are log in the internal buffer.
For example, %BOOTUP:RPM0:CP %PORTPIPE-INIT-SUCCESS: Portpipe 0 enabled
Configuration Task List for System Log Management
There are two configuration tasks for system log management:
•Disable System Logging
•Send System Messages to a Syslog Server
Disabling System Logging
By default, logging is enabled and log messages are sent to the logging buffer, all terminal lines, the
console, and the syslog servers.
To disable system logging, use the following commands.
•Disable all logging except on the console.
CONFIGURATION mode
no logging on
•Disable logging to the logging buffer.
CONFIGURATION mode
no logging buffer
•Disable logging to terminal lines.
CONFIGURATION mode
no logging monitor
•Disable console logging.
CONFIGURATION mode
no logging console
64
Management
Page 65
Sending System Messages to a Syslog Server
To send system messages to a specified syslog server, use the following command. The following syslog
standards are supported: RFC 5424 The SYSLOG Protocol, R.Gerhards and Adiscon GmbH, March 2009,
obsoletes RFC 3164 and RFC 5426 Transmission of Syslog Messages over UDP.
•Specify the server to which you want to send system messages. You can configure up to eight syslog
servers.
To configure a UNIX System as a syslog server, use the following command.
•Configure a UNIX system as a syslog server by adding the following lines to /etc/syslog.conf on the
UNIX system and assigning write permissions to the file.
– Add line on a 4.1 BSD UNIX system. local7.debugging /var/log/ftos.log
– Add line on a 5.7 SunOS UNIX system. local7.debugging /var/adm/ftos.log
In the previous lines, local7 is the logging facility level and debugging is the severity level.
Changing System Logging Settings
You can change the default settings of the system logging by changing the severity level and the storage
location.
The default is to log all messages up to debug level, that is, all system messages. By changing the severity
level in the logging commands, you control the number of system messages logged.
To specify the system logging settings, use the following commands.
•Specify the minimum severity level for logging to the logging buffer.
CONFIGURATION mode
logging buffered level
•Specify the minimum severity level for logging to the console.
CONFIGURATION mode
logging console level
•Specify the minimum severity level for logging to terminal lines.
CONFIGURATION mode
logging monitor level
•Specify the minimum severity level for logging to a syslog server.
CONFIGURATION mode
logging trap level
•Specify the minimum severity level for logging to the syslog history table.
CONFIGURATION mode
Management
65
Page 66
logging history level
•Specify the size of the logging buffer.
CONFIGURATION mode
logging buffered size
NOTE: When you decrease the buffer size, Dell Networking OS deletes all messages stored in
the buffer. Increasing the buffer size does not affect messages in the buffer.
•Specify the number of messages that Dell Networking OS saves to its logging history table.
CONFIGURATION mode
logging history size size
To view the logging buffer and configuration, use the show logging command in EXEC privilege mode,
as shown in the example for
To view the logging configuration, use the show running-config logging command in privilege
mode, as shown in the example for Configure a UNIX Logging Facility Level.
Display the Logging Buffer and the Logging Configuration.
Display the Logging Buffer and the Logging
Configuration
To display the current contents of the logging buffer and the logging settings for the system, use the
show logging command in EXEC privilege mode. When RBAC is enabled, the security logs are filtered
based on the user roles. Only the security administrator and system administrator can view the security
logs.
Example of the show logging Command
Dell#show logging
syslog logging: enabled
Console logging: level Debugging
Monitor logging: level Debugging
Buffer logging: level Debugging, 40 Messages Logged, Size (40960 bytes)
Trap logging: level Informational
%IRC-6-IRC_COMMUP: Link to peer RPM is up
%RAM-6-RAM_TASK: RPM1 is transitioning to Primary RPM.
%RPM-2-MSG:CP1 %POLLMGR-2-MMC_STATE: External flash disk missing in 'slot0:'
%CHMGR-5-CARDDETECTED: Line card 0 present
%CHMGR-5-CARDDETECTED: Line card 2 present
%CHMGR-5-CARDDETECTED: Line card 4 present
%CHMGR-5-CARDDETECTED: Line card 5 present
%CHMGR-5-CARDDETECTED: Line card 8 present
%CHMGR-5-CARDDETECTED: Line card 10 present
%CHMGR-5-CARDDETECTED: Line card 12 present
%TSM-6-SFM_DISCOVERY: Found SFM 0
%TSM-6-SFM_DISCOVERY: Found SFM 1
%TSM-6-SFM_DISCOVERY: Found SFM 2
%TSM-6-SFM_DISCOVERY: Found SFM 3
%TSM-6-SFM_DISCOVERY: Found SFM 4
%TSM-6-SFM_DISCOVERY: Found SFM 5
%TSM-6-SFM_DISCOVERY: Found SFM 6
%TSM-6-SFM_DISCOVERY: Found SFM 7
%TSM-6-SFM_SWITCHFAB_STATE: Switch Fabric: UP
%TSM-6-SFM_DISCOVERY: Found SFM 8
%TSM-6-SFM_DISCOVERY: Found 9 SFMs
%CHMGR-5-CHECKIN: Checkin from line card 5 (type EX1YB, 1 ports)
%TSM-6-PORT_CONFIG: Port link status for LC 5 => portpipe 0: OK portpipe 1: N/A
%CHMGR-5-LINECARDUP: Line card 5 is up
66
Management
Page 67
%CHMGR-5-CHECKIN: Checkin from line card 12 (type S12YC12, 12 ports)
%TSM-6-PORT_CONFIG: Port link status for LC 12 => portpipe 0: OK portpipe 1: N/A
%CHMGR-5-LINECARDUP: Line card 12 is up
%IFMGR-5-CSTATE_UP: changed interface Physical state to up: So 12/8
%IFMGR-5-CSTATE_DN: changed interface Physical state to down: So 12/8
To view any changes made, use the show running-config logging command in EXEC privilege
mode, as shown in the example for Configure a UNIX Logging Facility Level.
Configuring a UNIX Logging Facility Level
You can save system log messages with a UNIX system logging facility.
To configure a UNIX logging facility level, use the following command.
•Specify one of the following parameters.
CONFIGURATION mode
logging facility [facility-type]
– auth (for authorization messages)
– cron (for system scheduler messages)
– daemon (for system daemons)
– kern (for kernel messages)
– local0 (for local use)
– local1 (for local use)
– local2 (for local use)
– local3 (for local use)
– local4 (for local use)
– local5 (for local use)
– local6 (for local use)
– local7 (for local use)
– lpr (for line printer system messages)
– mail (for mail system messages)
– news (for USENET news messages)
– sys9 (system use)
– sys10 (system use)
– sys11 (system use)
– sys12 (system use)
– sys13 (system use)
– sys14 (system use)
– syslog (for syslog messages)
– user (for user programs)
– uucp (UNIX to UNIX copy protocol)
Example of the show running-config logging Command
To view nondefault settings, use the show running-config logging command in EXEC mode.
You can configure Dell Networking OS to filter and consolidate the system messages for a specific line by
synchronizing the message output.
Only the messages with a severity at or below the set level appear. This feature works on the terminal and
console connections available on the system.
1.Enter LINE mode.
CONFIGURATION mode
line {console 0 | vty number [end-number] | aux 0}
Configure the following parameters for the virtual terminal lines:
•number: the range is from zero (0) to 8.
•end-number: the range is from 1 to 8.
You can configure multiple virtual terminals at one time by entering a number and an end-number.
2.Configure a level and set the maximum number of messages to print.
•level severity-level: the range is from 0 to 7. The default is 2. Use the all keyword to
include all messages.
•limit: the range is from 20 to 300. The default is 20.
To view the logging synchronous configuration, use the show config command in LINE mode.
Enabling Timestamp on Syslog Messages
By default, syslog messages do not include a time/date stamp stating when the error or message was
created.
To enable timestamp, use the following command.
•Add timestamp to syslog messages.
CONFIGURATION mode
Specify the following optional parameters:
– You can add the keyword localtime to include the localtime, msec, and show-timezone. If
you do not add the keyword localtime, the time is UTC.
– uptime: To view time since last boot.
If you do not specify a parameter, Dell Networking OS configures uptime.
To view the configuration, use the show running-config logging command in EXEC privilege mode.
To disable time stamping on syslog messages, use the no service timestamps [log | debug]
command.
File Transfer Services
With Dell Networking OS, you can configure the system to transfer files over the network using the file
transfer protocol (FTP).
One FTP application is copying the system image files over an interface on to the system; however, FTP is
not supported on virtual local area network (VLAN) interfaces.
For more information about FTP, refer to RFC 959, File Transfer Protocol.
NOTE: To transmit large files, Dell Networking recommends configuring the switch as an FTP
server.
Configuration Task List for File Transfer Services
The configuration tasks for file transfer services are:
•Enable FTP Server (mandatory)
•Configure FTP Server Parameters (optional)
•Configure FTP Client Parameters (optional)
Enabling the FTP Server
To enable the system as an FTP server, use the following command.
To view FTP configuration, use the show running-config ftp command in EXEC privilege mode.
After you enable the FTP server on the system, you can configure different parameters.
To specify the system logging settings, use the following commands.
•Specify the directory for users using FTP to reach the system.
CONFIGURATION mode
ftp-server topdir dir
The default is the internal flash directory.
•Specify a user name for all FTP users and configure either a plain text or encrypted password.
CONFIGURATION mode
Configure the following optional and required parameters:
– username: enter a text string.
– encryption-type: enter 0 for plain text or 7 for encrypted text.
– password: enter a text string.
NOTE: You cannot use the change directory (cd) command until you have configured ftp-server topdir.
To view the FTP configuration, use the show running-config ftp command in EXEC privilege mode.
Configuring FTP Client Parameters
To configure FTP client parameters, use the following commands.
•Enter the following keywords and slot/port or number information:
– For a Gigabit Ethernet interface, enter the keyword GigabitEthernet then the slot/port
information.
– For a loopback interface, enter the keyword loopback then a number between 0 and 16383.
– For a port channel interface, enter the keywords port-channel then a number from 1 to 255 for
TeraScale and ExaScale.
– For a SONET interface, enter the keyword sonet then the slot/port information.
– For a 10-Gigabit Ethernet interface, enter the keyword TenGigabitEthernet then the slot/port
information.
– For a VLAN interface, enter the keyword vlan then a number from 1 to 4094.
– For a 40-Gigabit Ethernet interface, enter the keyword fortyGigE then the slot/port information.
CONFIGURATION mode
ip ftp source-interface interface
•Configure a password.
CONFIGURATION mode
ip ftp password password
70
Management
Page 71
•Enter a username to use on the FTP client.
CONFIGURATION mode
ip ftp username name
To view the FTP configuration, use the show running-config ftp command in EXEC privilege mode,
as shown in the example for Enable FTP Server.
Terminal Lines
You can access the system remotely and restrict access to the system by creating user profiles.
Terminal lines on the system provide different means of accessing the system. The console line (console)
connects you through the console port in the route processor modules (RPMs). The virtual terminal lines
(VTYs) connect you through Telnet to the system. The auxiliary line (aux) connects secondary devices
such as modems.
Denying and Permitting Access to a Terminal Line
Dell Networking recommends applying only standard access control lists (ACLs) to deny and permit
access to VTY lines.
•Layer 3 ACLs deny all traffic that is not explicitly permitted, but in the case of VTY lines, an ACL with
no rules does not deny traffic.
•You cannot use the show ip accounting access-list command to display the contents of an
ACL that is applied only to a VTY line.
To apply an IP ACL to a line, Use the following command.
•Apply an ACL to a VTY line.
LINE mode
ip access-class access-list
Example of an ACL that Permits Terminal Access
To view the configuration, use the show config command in LINE mode.
Dell(config-std-nacl)#show config
!
ip access-list standard myvtyacl
seq 5 permit host 10.11.0.1
Dell(config-std-nacl)#line vty 0
Dell(config-line-vty)#show config
line vty 0
access-class myvtyacl
Dell Networking OS Behavior: Prior to Dell Networking OS version 7.4.2.0, in order to deny access on a
VTY line, apply an ACL and accounting, authentication, and authorization (AAA) to the line. Then users are
denied access only after they enter a username and password. Beginning in Dell Networking OS version
7.4.2.0, only an ACL is required, and users are denied access before they are prompted for a username
and password.
Management
71
Page 72
Configuring Login Authentication for Terminal Lines
You can use any combination of up to six authentication methods to authenticate a user on a terminal
line.
A combination of authentication methods is called a method list. If the user fails the first authentication
method, Dell Networking OS prompts the next method until all methods are exhausted, at which point
the connection is terminated. The available authentication methods are:
enable
line
local
none
radius
tacacs+
1.Configure an authentication method list. You may use a mnemonic name or use the keyword
default. The default authentication method for terminal lines is local and the default method list is
empty.
2.Apply the method list from Step 1 to a terminal line.
CONFIGURATION mode
login authentication {method-list-name | default}
3.If you used the line authentication method in the method list you applied to the terminal line,
configure a password for the terminal line.
LINE mode
Prompt for the enable password.
Prompt for the password you assigned to the terminal line. Configure a password
for the terminal line to which you assign a method list that contains the line
authentication method. Configure a password using the password command from
LINE mode.
Prompt for the system username and password.
Do not authenticate the user.
Prompt for a username and password and use a RADIUS server to authenticate.
Prompt for a username and password and use a TACACS+ server to authenticate.
password
Example of Terminal Line Authentication
In the following example, VTY lines 0-2 use a single authentication method, line.
Dell(conf)#aaa authentication login myvtymethodlist line
Dell(conf)#line vty 0 2
Dell(config-line-vty)#login authentication myvtymethodlist
Dell(config-line-vty)#password myvtypassword
Dell(config-line-vty)#show config
line vty 0
password myvtypassword
login authentication myvtymethodlist
line vty 1
password myvtypassword
login authentication myvtymethodlist
line vty 2
password myvtypassword
EXEC time-out is a basic security feature that returns Dell Networking OS to EXEC mode after a period of
inactivity on the terminal lines.
To set time out, use the following commands.
•Set the number of minutes and seconds. The default is 10 minutes on the console and 30 minutes
on VTY. Disable EXEC time out by setting the time-out period to 0.
LINE mode
exec-timeout minutes [seconds]
•Return to the default time-out values.
LINE mode
no exec-timeout
Example of Setting the Time Out Period for EXEC Privilege Mode
The following example shows how to set the time-out period and how to view the configuration using
the show config command from LINE mode.
Dell(conf)#line con 0
Dell(config-line-console)#exec-timeout 0
Dell(config-line-console)#show config
line console 0
exec-timeout 0 0
Dell(config-line-console)#
Using Telnet to get to Another Network Device
To telnet to another device, use the following commands.
NOTE: On the Z9000 platform, the system allows 120 Telnet sessions per minute, allowing the login
and logout of 10 Telnet sessions, 12 times in a minute. If the system reaches this non-practical limit,
the Telnet service is stopped for 10 minutes. You can use console and SSH service to access the
system during downtime.
•Telnet to the peer RPM. You do not need to configure the management port on the peer RPM to be
able to telnet to it.
EXEC Privilege mode
telnet-peer-rpm
•Telnet to a device with an IPv4 or IPv6 address.
EXEC Privilege
telnet [ip-address]
If you do not enter an IP address, Dell Networking OS enters a Telnet dialog that prompts you for one.
Enter an IPv4 address in dotted decimal format (A.B.C.D).
Management
73
Page 74
Enter an IPv6 address in the format 0000:0000:0000:0000:0000:0000:0000:0000. Elision of zeros
is supported.
Example of the telnet Command for Device Access
Dell# telnet 10.11.80.203
Trying 10.11.80.203...
Connected to 10.11.80.203.
Exit character is '^]'.
Login:
Login: admin
Password:
Dell>exit
Dell#telnet 2200:2200:2200:2200:2200::2201
Trying 2200:2200:2200:2200:2200::2201...
Connected to 2200:2200:2200:2200:2200::2201.
Exit character is '^]'.
FreeBSD/i386 (freebsd2.force10networks.com) (ttyp1)
login: admin
Dell#
Lock CONFIGURATION Mode
Dell Networking OS allows multiple users to make configurations at the same time. You can lock
CONFIGURATION mode so that only one user can be in CONFIGURATION mode at any time (Message
2).
You can set two types of lockst: auto and manual.
•Set auto-lock using the configuration mode exclusive auto command from
CONFIGURATION mode. When you set auto-lock, every time a user is in CONFIGURATION mode, all
other users are denied access. This means that you can exit to EXEC Privilege mode, and re-enter
CONFIGURATION mode without having to set the lock again.
•Set manual lock using the configure terminal lock command from CONFIGURATION mode.
When you configure a manual lock, which is the default, you must enter this command each time you
want to enter CONFIGURATION mode and deny access to others.
Viewing the Configuration Lock Status
If you attempt to enter CONFIGURATION mode when another user has locked it, you may view which
user has control of CONFIGURATION mode using the show configuration lock command from
EXEC Privilege mode.
You can then send any user a message using the send command from EXEC Privilege mode.
Alternatively, you can clear any line using the
console session, the user is returned to EXEC mode.
Example of Locking CONFIGURATION Mode for Single-User Access
Dell(conf)#configuration mode exclusive auto
BATMAN(conf)#exit
3d23h35m: %RPM0-P:CP %SYS-5-CONFIG_I: Configured from console by console
clear command from EXEC Privilege mode. If you clear a
74
Management
Page 75
If another user attempts to enter CONFIGURATION mode while a lock is in place, the following appears
on their terminal (message 1): % Error: User "" on line console0 is in exclusive configuration mode.
If any user is already in CONFIGURATION mode when while a lock is in place, the following appears on
their terminal (message 2): % Error: Can't lock configuration mode exclusively since
the following users are currently configuring the system: User "admin" on line
vty1 ( 10.1.1.1 ).
NOTE: The CONFIGURATION mode lock corresponds to a VTY session, not a user. Therefore, if you
configure a lock and then exit CONFIGURATION mode, and another user enters CONFIGURATION
mode, when you attempt to re-enter CONFIGURATION mode, you are denied access even though
you are the one that configured the lock.
NOTE: If your session times out and you return to EXEC mode, the CONFIGURATION mode lock is
unconfigured.
Recovering from a Forgotten Password on the Z9000
System
If you configure authentication for the console and you exit out of EXEC mode or your console session
times out, you are prompted for a password to re-enter.
If you forget your password, use the following commands.
1.Log onto the system using the console.
2.Power-cycle the chassis by disconnecting and.then reconnecting the power cord.
3.Press Esc when prompted to abort the boot process.
(during bootup)
hit any key
NOTE: You must enter the CLI commands. The system rejects them if they are copied and
pasted.
4.The Grub menu displays.
Enter c to get to the Grub boot load command line grub> prompt.
5.Set the system parameters to ignore the enable password when the system reloads and reboot the
environment.
grub>set stconfigignore=true
grub>save_env stconfigignore
grub>reboot
6.The Z9000 boots up with the factory default configuration. The default Dell Networking OS system
prompt displays when the system boot up is complete.
NOTE: Do not press any keys during the boot-up process.
7.Copy the startup-config into the running-config.
EXEC Privilege mode
copy flash://startup-config running-config
Management
75
Page 76
8.Display the content of the startup-config.
EXEC Privilege mode
show running-config
9.Remove the previous authentication configuration.
config t
10. Set the new authentication parameters. The remainder of the previous configuration is preserved.
no enable password
enable password [newpassword]
exit
11. Save the running-config to the startup-config in flash by default.
write-mem
12. Save the running-config.
EXEC Privilege mode
copy running-config startup-config
Recovering from a Forgotten Enable Password on the Z9000
Use the following commands if you forget the enable password.
1.Log onto the system using the console.
2.Power-cycle the chassis by switching off all of the power modules and then switching them back on.
3.Press any key to abort the boot process. You enter grub on the Z9000, as indicated by the grub>
prompt.
(during bootup)
hit any key
NOTE: You must enter the CLI commands. The system rejects them if they are copied and
pasted.
4.The Grub menu displays. Enter c to get to the Grub boot load command line grub> prompt.
5.Set the system parameters to ignore the enable password when the system reloads and save the
environment.
uBoot mode
grub>setenv enablepwdignore=true
grub>save_env enablepwdignore
6.Reload the system.
uBoot mode
reset
7.Configure a new enable password.
CONFIGURATION mode
enable {secret | password}
76
Management
Page 77
8.Save the running-config to the startup-config.
EXEC Privilege mode
copy running-config startup-config
Recovering from a Failed Start on the Z9000 System
A system that does not start correctly might be attempting to boot from a corrupted Dell Networking OS
image or from a mis-specified location.
In this case, you can restart the system and interrupt the boot process to point the system to another
boot location. Use the set command, as described in the following steps. For details about the set
command, its supporting commands, and other commands that can help recover from a failed start, the
GRUB chapter in the Dell Networking OS Command Line Reference Guide.
1.Power-cycle the chassis (pull the power cord and reinsert it).
2.Press the ESC key when the following message appears: Press Esc to stop autoboot...
(during bootup)
Press ESC key
3.Use the arrow keys to select “Force10 Boot” from the list, then press the “C” key to enter GRUB CLI
mode. The command prompt changes to
GRUB mode
4.Set the Primary Boot Parameter.
GRUB mode
grub>.
set primary_boot=’f10boot location’
5.(Optional) Set the Secondary and Default Boot parameters.
GRUB mode
set secondary_boot=’f10boot location’
set default_boot=’f10boot location’
6.Save all variables individually.
GRUB mode
save_env primary_boot
save_env secondary_boot
save_env default_boot
NOTE: This command must be used once for each environment variable. If this step is not
completed, the chassis reboots continually.
7.Reboot the chassis.
GRUB mode
reboot
Management
77
Page 78
Restoring the Factory Default Settings
Restoring the factory-default settings deletes the existing NVRAM settings, startup configuration, and all
configured settings such as, stacking or fanout.
Z9000MXL Switch
To restore the factory default settings, use the restore factory-defaults stack-unit {0-5 |
all} {clear-all | nvram}
CAUTION: There is no undo for this command.
Important Points to Remember
•When you restore all the units in a stack, these units are placed in standalone mode.
•When you restore a single unit in a stack, only that unit is placed in standalone mode. No other units
in the stack are affected.
•When you restore the units in standalone mode, the units remain in standalone mode after the
restoration.
•After the restore is complete, the units power cycle immediately.
The following example illustrates the restore factory-defaults command to restore the factory default
settings.
Dell#restore factory-defaults stack-unit 0 nvram
command in EXEC Privilege mode.
***********************************************************************
* Warning - Restoring factory defaults will delete the existing *
* persistent settings (stacking, fanout, etc.) *
* After restoration the unit(s) will be powercycled immediately. *
* Proceed with caution ! *
***********************************************************************
Proceed with factory settings? Confirm [yes/no]:yes
-- Restore status --
Unit Nvram Config
------------------------
0 Success
Power-cycling the unit(s).
....
Restoring Factory Default Environment Variables
The Boot line determines the location of the image that is used to boot up the chassis after restoring
factory default settings. Ideally, these locations contain valid images, using which the chassis boots up.
While restoring factory-default settings, you can either use a flash boot procedure or a network boot
procedure to boot the device.
When you use the flash boot procedure to boot the device, the boot loader checks if the primary or the
secondary partition contains a valid image. If the primary partition contains a valid image, then the
primary boot line is set to A: and the secondary and default boot lines are set to a Null String. If the
78
Management
Page 79
secondary partition contains a valid image, then the primary boot line is set to B: and the secondary and
default boot lines are set to a Null String. If both the partitions contain invalid images, then primary,
secondary, and default boot line values are set to a Null string.
When you use the Network boot procedure to boot the device, the boot loader checks if the primary
partition contains a valid image. If a valid image exists on the primary partition and the secondary partition
does not contain a valid image, then the primary boot line is set to A: and the secondary and default boot
lines are set to a Null string. If the secondary partition also contains a valid image, then the primary boot
line value is set to the partition that is configured to be used to boot the device in a network failure
scenario. The secondary and default boot line values are set to a Null string.
Important Points to Remember
•The Chassis remains in boot prompt if none of the partitions contain valid images.
•To enable TFTP boot after restoring factory default settings, you must stop the boot process in BLI.
In case the system fails to reload the image from the partition, perform the following steps:
1.Power-cycle the chassis (pull the power cord and reinsert it).
2.Press any key to abort the boot process (while the system prompts to).
3.Press c to get into the grub mode.
You immediately enter the grub mode, which is indicated by the grub> prompt.
4.Assign the new location of the FTOS image to be used when the system reloads.
To boot from flash partition A:
grub> set primary_boot="f10boot flash0"
To boot from flash partition B:
grub> set primary_boot="f10boot flash1"
To boot from network:
grub> set primary_boot="f10boot tftp://10.16.127.35/FTOS-ZB.bin"
5.Assign an IP address and netmask to the Management Ethernet interface.
grub> set ipaddr="10.16.151.239"
grub> set netmask="255.255.0.0"
6.Assign an IP address as the default gateway for the system.
grub> set gatewayip="10.16.151.254"
7.Save the modified environmental variables.
grub> save_env environment_variables
NOTE: Repeat this step for all the environment variables.
8.Reload the system.
Management
79
Page 80
grub> reboot
80
Management
Page 81
6
802.1X
802.1X is supported on the Z9000 platform.
802.1X is a method of port security. A device connected to a port that is enabled with 802.1X is
disallowed from sending or receiving packets on the network until its identity can be verified (through a
username and password, for example). This feature is named for its IEEE specification.
802.1X employs extensible authentication protocol (EAP) to transfer a device’s credentials to an
authentication server (typically RADIUS) using a mandatory intermediary network access device, in this
case, a Dell Networking switch. The network access device mediates all communication between the
end-user device and the authentication server so that the network remains secure. The network access
device uses EAP-over-Ethernet (EAPOL) to communicate with the end-user device and EAP-overRADIUS to communicate with the server.
NOTE: The Dell Networking Operating System (OS) supports 802.1X with EAP-MD5, EAP-OTP, EAPTLS, EAP-TTLS, PEAPv0, PEAPv1, and MS-CHAPv2 with PEAP.
The following figures show how the EAP frames are encapsulated in Ethernet and RADIUS frames.
Figure 2. EAP Frames Encapsulated in Ethernet and RADUIS
802.1X
81
Page 82
Figure 3. EAP Frames Encapsulated in Ethernet and RADUIS
The authentication process involves three devices:
•The device attempting to access the network is the supplicant. The supplicant is not allowed to
communicate on the network until the authenticator authorizes the port. It can only communicate
with the authenticator in response to 802.1X requests.
•The device with which the supplicant communicates is the authenticator. The authenticator is the
gate keeper of the network. It translates and forwards requests and responses between the
authentication server and the supplicant. The authenticator also changes the status of the port based
on the results of the authentication process. The Dell Networking switch is the authenticator.
•The authentication-server selects the authentication method, verifies the information the supplicant
provides, and grants it network access privileges.
Ports can be in one of two states:
•Ports are in an unauthorized state by default. In this state, non-802.1X traffic cannot be forwarded in
or out of the port.
•The authenticator changes the port state to authorized if the server can authenticate the supplicant.
In this state, network traffic can be forwarded normally.
NOTE: The Dell Networking switches place 802.1X-enabled ports in the unauthorized state by
default.
The Port-Authentication Process
The authentication process begins when the authenticator senses that a link status has changed from
down to up:
1.When the authenticator senses a link state change, it requests that the supplicant identify itself using
an EAP Identity Request frame.
2.The supplicant responds with its identity in an EAP Response Identity frame.
82
802.1X
Page 83
3.The authenticator decapsulates the EAP response from the EAPOL frame, encapsulates it in a
RADIUS Access-Request frame and forwards the frame to the authentication server.
4.The authentication server replies with an Access-Challenge frame. The Access-Challenge frame
requests that the supplicant prove that it is who it claims to be, using a specified method (an EAPMethod). The challenge is translated and forwarded to the supplicant by the authenticator.
5.The supplicant can negotiate the authentication method, but if it is acceptable, the supplicant
provides the Requested Challenge information in an EAP response, which is translated and
forwarded to the authentication server as another Access-Request frame.
6.If the identity information provided by the supplicant is valid, the authentication server sends an
Access-Accept frame in which network privileges are specified. The authenticator changes the port
state to authorized and forwards an EAP Success frame. If the identity information is invalid, the
server sends an Access-Reject frame. If the port state remains unauthorized, the authenticator
forwards an EAP Failure frame.
Figure 4. EAP Port-Authentication
802.1X
83
Page 84
EAP over RADIUS
802.1X uses RADIUS to shuttle EAP packets between the authenticator and the authentication server, as
defined in RFC 3579.
EAP messages are encapsulated in RADIUS packets as a type of attribute in Type, Length, Value (TLV)
format. The Type value for EAP messages is 79.
Figure 5. EAP Over RADIUS
RADIUS Attributes for 802.1 Support
Dell Networking systems include the following RADIUS attributes in all 802.1X-triggered Access-Request
messages:
Attribute 31Calling-station-id: relays the supplicant MAC address to the authentication server.
Attribute 41NAS-Port-Type: NAS-port physical port type. 15 indicates Ethernet.
Attribute 61NAS-Port: the physical port number by which the authenticator is connected to
the supplicant.
Attribute 81Tunnel-Private-Group-ID: associate a tunneled session with a particular group of
users.
Configuring 802.1X
Configuring 802.1X on a port is a one-step process.
For more information, refer to Enabling 802.1X.
Related Configuration Tasks
•Configuring Request Identity Re-Transmissions
•Forcibly Authorizing or Unauthorizing a Port
•Re-Authenticating a Port
•Configuring Timeouts
•Configuring a Guest VLAN
•Configuring an Authentication-Fail VLAN
84
802.1X
Page 85
Important Points to Remember
•Dell Networking OS supports 802.1X with EAP-MD5, EAP-OTP, EAP-TLS, EAP-TTLS, PEAPv0, PEAPv1,
and MS-CHAPv2 with PEAP.
•All platforms support only RADIUS as the authentication server.
•If the primary RADIUS server becomes unresponsive, the authenticator begins using a secondary
RADIUS server, if configured.
•802.1X is not supported on port-channels or port-channel members.
Enabling 802.1X
Enable 802.1X globally.
Figure 6. 802.1X Enabled
1.Enable 802.1X globally.
CONFIGURATION mode
802.1X
85
Page 86
dot1x authentication
2.Enter INTERFACE mode on an interface or a range of interfaces.
INTERFACE mode
interface [range]
3.Enable 802.1X on the supplicant interface only.
INTERFACE mode
dot1x authentication
Examples of Verifying that 802.1X is Enabled Globally and on an Interface
Verify that 802.1X is enabled globally and at the interface level using the show running-config |
find dot1x command from EXEC Privilege mode.
In the following example, the bold lines show that 802.1X is enabled.
Dell#show running-config | find dot1x
dot1x authentication
!
[output omitted]
!
interface TenGigabitEthernet 2/1
no ip address
dot1x authentication
no shutdown
!
Dell#
To view 802.1X configuration information for an interface, use the show dot1x interface command.
In the following example, the bold lines show that 802.1X is enabled on all ports unauthorized by default.
If the authenticator sends a Request Identity frame, but the supplicant does not respond, the
authenticator waits 30 seconds and then re-transmits the frame.
The amount of time that the authenticator waits before re-transmitting and the maximum number of
times that the authenticator re-transmits are configurable.
NOTE: There are several reasons why the supplicant might fail to respond; for example, the
supplicant might have been booting when the request arrived or there might be a physical layer
problem.
To configure re-transmissions, use the following commands.
•Configure the amount of time that the authenticator waits before re-transmitting an EAP Request
Identity frame.
INTERFACE mode
dot1x tx-period number
The range is from 1 to 65535 (1 year)
The default is 30.
•Configure a maximum number of times the authenticator re-transmits a Request Identity frame.
INTERFACE mode
dot1x max-eap-req number
The range is from 1 to 10.
The default is 2.
The example in Configuring a Quiet Period after a Failed Authentication shows configuration information
for a port for which the authenticator re-transmits an EAP Request Identity frame after 90 seconds and
re-transmits a maximum of 10 times.
Configuring a Quiet Period after a Failed Authentication
If the supplicant fails the authentication process, the authenticator sends another Request Identity frame
after 30 seconds by default, but you can configure this period.
NOTE: The quiet period (dot1x quiet-period) is a transmit interval for after a failed
authentication; the Request Identity Re-transmit interval (dot1x tx-period) is for an unresponsive
supplicant.
To configure a quiet period, use the following command.
•Configure the amount of time that the authenticator waits to re-transmit a Request Identity frame
after a failed authentication.
INTERFACE mode
dot1x quiet-period seconds
The range is from 1 to 65535.
The default is 60 seconds.
802.1X
87
Page 88
Example of Configuring and Verifying Port Authentication
The following example shows configuration information for a port for which the authenticator retransmits an EAP Request Identity frame:
•after 90 seconds and a maximum of 10 times for an unresponsive supplicant
•re-transmits an EAP Request Identity frame
The bold lines show the new re-transmit interval, new quiet period, and new maximum re-transmissions.
IEEE 802.1X requires that a port can be manually placed into any of three states:
•ForceAuthorized — an authorized state. A device connected to this port in this state is never
subjected to the authentication process, but is allowed to communicate on the network. Placing the
port in this state is same as disabling 802.1X on the port.
•ForceUnauthorized — an unauthorized state. A device connected to a port in this state is never
subjected to the authentication process and is not allowed to communicate on the network. Placing
the port in this state is the same as shutting down the port. Any attempt by the supplicant to initiate
authentication is ignored.
•Auto — an unauthorized state by default. A device connected to this port in this state is subjected to
the authentication process. If the process is successful, the port is authorized and the connected
device can communicate on the network. All ports are placed in the Auto state by default.
To set the port state, use the following command.
•Place a port in the ForceAuthorized, ForceUnauthorized, or Auto state.
INTERFACE mode
You can configure the authenticator for periodic re-authentication.
After the supplicant has been authenticated, and the port has been authorized, you can configure the
authenticator to re-authenticate the supplicant periodically. If you enable re-authentication, the
supplicant is required to re-authenticate every 3600 seconds, but you can configure this interval. You can
configure a maximum number of re-authentications as well.
To configure re-authentication time settings, use the following commands.
•Configure the authenticator to periodically re-authenticate the supplicant.
INTERFACE mode
dot1x reauthentication [interval] seconds
The range is from 1 to 65535.
The default is 3600.
•Configure the maximum number of times that the supplicant can be re-authenticated.
INTERFACE mode
dot1x reauth-max number
The range is from 1 to 10.
The default is 2.
Example of Re-Authenticating a Port and Verifying the Configuration
802.1X
89
Page 90
The bold lines show that re-authentication is enabled and the new maximum and re-authentication time
period.
If the supplicant or the authentication server is unresponsive, the authenticator terminates the
authentication process after 30 seconds by default. You can configure the amount of time the
authenticator waits for a response.
To terminate the authentication process, use the following commands.
•Terminate the authentication process due to an unresponsive supplicant.
INTERFACE mode
dot1x supplicant-timeout seconds
The range is from 1 to 300.
The default is 30.
•Terminate the authentication process due to an unresponsive authentication server.
INTERFACE mode
dot1x server-timeout seconds
The range is from 1 to 300.
The default is 30.
Example of Viewing Configured Server Timeouts
The example shows configuration information for a port for which the authenticator terminates the
authentication process for an unresponsive supplicant or server after 15 seconds.
90
802.1X
Page 91
The bold lines show the new supplicant and server timeouts.
Dell(conf-if-Te-0/0)#dot1x port-control force-authorized
Dell(conf-if-Te-0/0)#do show dot1x interface TenGigabitEthernet 0/0
Enter the tasks the user should do after finishing this task (optional).
Configuring Dynamic VLAN Assignment with Port
Authentication
Dell Networking OS supports dynamic VLAN assignment when using 802.1X.
The basis for VLAN assignment is RADIUS attribute 81, Tunnel-Private-Group-ID. Dynamic VLAN
assignment uses the standard dot1x procedure:
1.The host sends a dot1x packet to the Dell Networking system
2.The system forwards a RADIUS REQEST packet containing the host MAC address and ingress port
number
3.The RADIUS server authenticates the request and returns a RADIUS ACCEPT message with the VLAN
assignment using Tunnel-Private-Group-ID
The illustration shows the configuration on the Dell Networking system before connecting the end user
device in black and blue text, and after connecting the device in red text. The blue text corresponds to
the preceding numbered steps on dynamic VLAN assignment with 802.1X.
802.1X
91
Page 92
Figure 7. Dynamic VLAN Assignment
1.Configure 8021.x globally (refer to Enabling 802.1X) along with relevant RADIUS server configurations
(refer to the illustration inDynamic VLAN Assignment with Port Authentication).
2.Make the interface a switchport so that it can be assigned to a VLAN.
3.Create the VLAN to which the interface will be assigned.
4.Connect the supplicant to the port configured for 802.1X.
5.Verify that the port has been authorized and placed in the desired VLAN (refer to the illustration in
Dynamic VLAN Assignment with Port Authentication).
Guest and Authentication-Fail VLANs
Typically, the authenticator (the Dell system) denies the supplicant access to the network until the
supplicant is authenticated. If the supplicant is authenticated, the authenticator enables the port and
places it in either the VLAN for which the port is configured or the VLAN that the authentication server
indicates in the authentication data.
NOTE: Ports cannot be dynamically assigned to the default VLAN.
92
802.1X
Page 93
If the supplicant fails authentication, the authenticator typically does not enable the port. In some cases
this behavior is not appropriate. External users of an enterprise network, for example, might not be able
to be authenticated, but still need access to the network. Also, some dumb-terminals, such as network
printers, do not have 802.1X capability and therefore cannot authenticate themselves. To be able to
connect such devices, they must be allowed access the network without compromising network security.
The Guest VLAN 802.1X extension addresses this limitation with regard to non-802.1X capable devices
and the Authentication-fail VLAN 802.1X extension addresses this limitation with regard to external users.
•If the supplicant fails authentication a specified number of times, the authenticator places the port in
the Authentication-fail VLAN.
•If a port is already forwarding on the Guest VLAN when 802.1X is enabled, the port is moved out of
the Guest VLAN and the authentication process begins.
Configuring a Guest VLAN
If the supplicant does not respond within a determined amount of time ([reauth-max + 1] * tx-period, the
system assumes that the host does not have 802.1X capability and the port is placed in the Guest VLAN.
NOTE: For more information about configuring timeouts, refer to Configuring Timeouts.
Configure a port to be placed in the Guest VLAN after failing to respond within the timeout period using
the dot1x guest-vlan command from INTERFACE mode. View your configuration using the show config command from INTERFACE mode or using the show dot1x interface command from EXEC
Privilege mode.
If the supplicant fails authentication, the authenticator re-attempts to authenticate after a specified
amount of time.
NOTE: For more information about authenticator re-attempts, refer to Configuring a Quiet Period
after a Failed Authentication.
You can configure the maximum number of times the authenticator re-attempts authentication after a
failure (3 by default), after which the port is placed in the Authentication-fail VLAN.
Configure a port to be placed in the VLAN after failing the authentication process as specified number of
times using the dot1x auth-fail-vlan command from INTERFACE mode. Configure the maximum
number of authentication attempts by the authenticator using the keyword max-attempts with this
command.
Example of Configuring Maximum Authentication Attempts
View your configuration using the show config command from INTERFACE mode, as shown in the
example in Configuring a Guest VLAN or using the show dot1x interface command from EXEC
Privilege mode.
802.1x information on Te 2/1:
-----------------------------
Dot1x Status: Enable
Port Control: FORCE_AUTHORIZED
Port Auth Status: UNAUTHORIZED
Re-Authentication: Disable
Untagged VLAN id: None
This chapter describes access control lists (ACLs), prefix lists, and route-maps.
•Access control lists (ACLs), Ingress IP and MAC ACLs , and Egress IP and MAC ACLs are supported on
the Z9000 platform.
At their simplest, access control lists (ACLs), prefix lists, and route-maps permit or deny traffic based on
MAC and/or IP addresses. This chapter describes implementing IP ACLs, IP prefix lists and route-maps.
For MAC ACLS, refer to Layer 2.
An ACL is essentially a filter containing some criteria to match (examine IP, transmission control protocol
[TCP], or user datagram protocol [UDP] packets) and an action to take (permit or deny). ACLs are
processed in sequence so that if a packet does not match the criterion in the first filter, the second filter
(if configured) is applied. When a packet matches a filter, the switch drops or forwards the packet based
on the filter’s specified action. If the packet does not match any of the filters in the ACL, the packet is
dropped (implicit deny).
The number of ACLs supported on a system depends on your content addressable memory (CAM) size.
For more information, refer to User Configurable CAM Allocation and CAM Optimization. For complete
CAM profiling information, refer to Content Addressable Memory (CAM).
Starting from the release 9.4.(0.0), you can configure ACLs on VRF instances. In addition to the existing
qualifying parameters, Layer 3 ACLs also incorporate VRF ID as one of the parameters. Using this new
capability, you can also configure VRF based ACLs on interfaces.
NOTE: You can apply Layer 3 VRF-aware ACLs only at the ingress level.
You can apply VRF-aware ACLs on:
•VRF Instances
•Interfaces
In order to configure VRF-aware ACLs on VRF instances, you must carve out a separate CAM region. You
can use the cam-acl command for allocating CAM regions. As part of the enhancements to support
VRF-aware ACLs, the cam-acl command now includes the following new parameter that enables you to
allocate a CAM region:
The order of priority for configuring user-defined ACL CAM regions is as follows:
•V4 ACL CAM
•VRF V4 ACL CAM
•L2 ACL CAM
With the inclusion of VRF based ACLs, the order of precedence of Layer 3 ACL rules is as follows:
•Port/VLAN based PERMIT/DENY Rules
Access Control Lists (ACLs)
vrfv4acl.
95
Page 96
•Port/VLAN based IMPLICIT DENY Rules
•VRF based PERMIT/DENY Rules
•VRF based IMPLICIT DENY Rules
NOTE: In order for the VRF ACLs to take effect, ACLs configured in the Layer 3 CAM region must
have an implicit-permit option.
You can use the ip access-group command to configure VRF-aware ACLs on interfaces. Using the ip
access-group
for configuring ACLs on interfaces. The VRF range is from 1 to 63. These ACLs use the existing V4 ACL
CAM region to populate the entries in the hardware and do not require you to carve out a separate CAM
region.
NOTE: You can configure VRF-aware ACLs on interfaces either using a range of VLANs or a range of
VRFs but not both.
command, in addition to a range of VLANs, you can also specify a range of VRFs as input
IP Access Control Lists (ACLs)
In Dell Networking switch/routers, you can create two different types of IP ACLs: standard or extended.
A standard ACL filters packets based on the source IP packet. An extended ACL filters traffic based on the
following criteria:
•IP protocol number
•Source IP address
•Destination IP address
•Source TCP port number
•Destination TCP port number
•Source UDP port number
•Destination UDP port number
For more information about ACL options, refer to the Dell Networking OS Command Reference Guide.
For extended ACL, TCP, and UDP filters, you can match criteria on specific or ranges of TCP or UDP
ports. For extended ACL TCP filters, you can also match criteria on established TCP sessions.
When creating an access list, the sequence of the filters is important. You have a choice of assigning
sequence numbers to the filters as you enter them, or the Dell Networking Operating System (OS) assigns
numbers in the order the filters are created. The sequence numbers are listed in the display output of the
show config and show ip accounting access-list commands.
Ingress and egress Hot Lock ACLs allow you to append or delete new rules into an existing ACL (already
written into CAM) without disrupting traffic flow. Existing entries in the CAM are shuffled to
accommodate the new entries. Hot lock ACLs are enabled by default and support both standard and
extended ACLs and on all platforms.
NOTE: Hot lock ACLs are supported for Ingress ACLs only.
CAM Usage
The following section describes CAM allocation and CAM optimization.
•User Configurable CAM Allocation
96
Access Control Lists (ACLs)
Page 97
•CAM Optimization
User Configurable CAM Allocation
User configurable CAM allocations are supported on the Z9000 platform.
Allocate space for IPV6 ACLs by using the cam-acl command in CONFIGURATION mode.
The CAM space is allotted in filter processor (FP) blocks. The total space allocated must equal 13 FP
blocks. (There are 16 FP blocks, but System Flow requires three blocks that cannot be reallocated.)
Enter the ipv6acl allocation as a factor of 2 (2, 4, 6, 8, 10). All other profile allocations can use either
even or odd numbered ranges.
If you want to configure ACL's on VRF instances, you must allocate a CAM region using the vrfv4acl
option in the cam-acl command.
Save the new CAM settings to the startup-config (use write-mem or copy run start) then reload the
system for the new settings to take effect.
CAM Optimization
The CAM optimization command is supported on the Z9000 platform.
When you enable this command, if a policy map containing classification rules (ACL and/or dscp/ ipprecedence rules) is applied to more than one physical interface on the same port-pipe, only a single
copy of the policy is written (only one FP entry is used). When you disable this command, the system
behaves as described in this chapter.
Test CAM Usage
The test cam-usage command is supported on the Z9000 platform.
This command applies to both IPv4 and IPv6 CAM profiles, but is best used when verifying QoS
optimization for IPv6 ACLs.
To determine whether sufficient ACL CAM space is available to enable a service-policy, use this
command. To verify the actual CAM space required, create a class map with all the required ACL rules,
then execute the test cam-usage command in Privilege mode. The following example shows the
output when executing this command. The status column indicates whether you can enable the policy.
Example of the test cam-usage Command
Dell#test cam-usage service-policy input TestPolicy linecard all
Linecard|Portpipe|CAM Partition|Available CAM|Estimated CAM per Port|Status
You can assign one IP ACL per interface with Dell Networking OS. If you do not assign an IP ACL to an
interface, it is not used by the software in any other capacity.
The number of entries allowed per ACL is hardware-dependent. For detailed specification on entries
allowed per ACL, refer to your line card documentation.
If counters are enabled on ACL rules that are already configured, those counters are reset when a new
rule which is inserted or prepended or appended requires a hardware shift in the flow table. Resetting the
counters to 0 is transient as the proginal counter values are retained after a few seconds. If there is no
need to shift the flow in the hardware, the counters are not disturbed. This is applicable to the following
features:
•L2 Ingress Access list
•L2 Egress Access list
NOTE: IP ACLs are supported over VLANs in Dell Networking OS version 6.2.1.1 and higher.
ACLs and VLANs
There are some differences when assigning ACLs to a VLAN rather than a physical port.
For example, when using a single port-pipe, if you apply an ACL to a VLAN, one copy of the ACL entries is
installed in the ACL CAM on the port-pipe. The entry looks for the incoming VLAN in the packet. Whereas
if you apply an ACL on individual ports of a VLAN, separate copies of the ACL entries are installed for each
port belonging to a port-pipe.
When you use the log keyword, the CP has to log the details about the packets that match. Depending
on how many packets match the log entry and at what rate, the CP might become busy as it has to log
these packets’ details. However, the other processors (RP1 and RP2) are unaffected. This option is
typically useful when debugging some problem related to control traffic. We have used this option
numerous times in the field and have not encountered problems so far.
ACL Optimization
If an access list contains duplicate entries, Dell Networking OS deletes one entry to conserve CAM space.
Standard and extended ACLs take up the same amount of CAM space. A single ACL rule uses two CAM
entries whether it is identified as a standard or extended ACL.
Determine the Order in which ACLs are Used to Classify Traffic
When you link class-maps to queues using the service-queue command, Dell Networking OS matches
the class-maps according to queue priority (queue numbers closer to 0 have lower priorities).
As shown in the following example, class-map cmap2 is matched against ingress packets before cmap1.
ACLs acl1 and acl2 have overlapping rules because the address range 20.1.1.0/24 is within 20.0.0.0/8.
Therefore (without the keyword order), packets within the range 20.1.1.0/24 match positive against
cmap1 and are buffered in queue 7, though you intended for these packets to match positive against
cmap2 and be buffered in queue 4.
In cases such as these, where class-maps with overlapping ACL rules are applied to different queues, use
the order keyword to specify the order in which you want to apply ACL rules. The order can range from
0 to 254. Dell Networking OS writes to the CAM ACL rules with lower-order numbers (order numbers
98
Access Control Lists (ACLs)
Page 99
closer to 0) before rules with higher-order numbers so that packets are matched as you intended. By
default, all ACL rules have an order of 255.
Example of the order Keyword to Determine ACL Sequence
Dell(conf)#ip access-list standard acl1
Dell(config-std-nacl)#permit 20.0.0.0/8
Dell(config-std-nacl)#exit
Dell(conf)#ip access-list standard acl2
Dell(config-std-nacl)#permit 20.1.1.0/24 order 0
Dell(config-std-nacl)#exit
Dell(conf)#class-map match-all cmap1
Dell(conf-class-map)#match ip access-group acl1
Dell(conf-class-map)#exit
Dell(conf)#class-map match-all cmap2
Dell(conf-class-map)#match ip access-group acl2
Dell(conf-class-map)#exit
Dell(conf)#policy-map-input pmap
Dell(conf-policy-map-in)#service-queue 7 class-map cmap1
Dell(conf-policy-map-in)#service-queue 4 class-map cmap2
Dell(conf-policy-map-in)#exit
Dell(conf)#interface te 10/0
Dell(conf-if-te-10/0)#service-policy input pmap
IP Fragment Handling
Dell Networking OS supports a configurable option to explicitly deny IP fragmented packets, particularly
second and subsequent packets.
It extends the existing ACL command syntax with the fragments keyword for all Layer 3 rules applicable
to all Layer protocols (permit/deny ip/tcp/udp/icmp).
•Both standard and extended ACLs support IP fragments.
•Second and subsequent fragments are allowed because a Layer 4 rule cannot be applied to these
fragments. If the packet is to be denied eventually, the first fragment would be denied and hence the
packet as a whole cannot be reassembled.
•Implementing the required rules uses a significant number of CAM entries per TCP/UDP entry.
•For IP ACL, Dell Networking OS always applies implicit deny. You do not have to configure it.
•For IP ACL, Dell Networking OS applies implicit permit for second and subsequent fragment just prior
to the implicit deny.
•If you configure an explicit deny, the second and subsequent fragments do not hit the implicit permit
rule for fragments.
•Loopback interfaces do not support ACLs using the IP fragment option. If you configure an ACL
with the fragments option and apply it to a Loopback interface, the command is accepted but the
ACL entries are not actually installed the offending rule in CAM.
IP Fragments ACL Examples
The following examples show how you can use ACL commands with the fragment keyword to filter
fragmented packets.
Example of Permitting All Packets on an Interface
The following configuration permits all packets (both fragmented and non-fragmented) with destination
IP 10.1.1.1. The second rule does not get hit at all.
Dell(conf)#ip access-list extended ABC
Dell(conf-ext-nacl)#permit ip any 10.1.1.1/32FTOS(conf-ext-nacl)#
deny ip any
Access Control Lists (ACLs)
99
Page 100
10.1.1.1./32 fragments
Dell(conf-ext-nacl)
Example of Denying Second and Subsequent Fragments
To deny the second/subsequent fragments, use the same rules in a different order. These ACLs deny all
second and subsequent fragments with destination IP 10.1.1.1 but permit the first fragment and nonfragmented packets with destination IP 10.1.1.1.
Dell(conf)#ip access-list extended ABC
Dell(conf-ext-nacl)#deny ip any 10.1.1.1/32 fragments
Dell(conf-ext-nacl)#permit ip any 10.1.1.1/32
Dell(conf-ext-nacl)
Layer 4 ACL Rules Examples
The following examples show the ACL commands for Layer 4 packet filtering.
Permit an ACL line with L3 information only, and the fragments keyword is present:
If a packet’s L3 information matches the L3 information in the ACL line, the packet's FO is checked.
•If a packet's FO > 0, the packet is permitted.
•If a packet's FO = 0, the next ACL entry is processed.
Deny ACL line with L3 information only, and the fragments keyword is present:
If a packet's L3 information does match the L3 information in the ACL line, the packet's FO is checked.
•If a packet's FO > 0, the packet is denied.
•If a packet's FO = 0, the next ACL line is processed.
Example of Permitting All Packets from a Specified Host
In this first example, TCP packets from host 10.1.1.1 with TCP destination port equal to 24 are permitted.
All others are denied.
Example of Permitting Only First Fragments and Non-Fragmented Packets from a Specified Host
In the following example, the TCP packets that are first fragments or non-fragmented from host 10.1.1.1
with TCP destination port equal to 24 are permitted. Additionally, all TCP non-first fragments from host
10.1.1.1 are permitted. All other IP packets that are non-first fragments are denied.
Dell(conf)#ip access-list extended ABC
Dell(conf-ext-nacl)#permit tcp host 10.1.1.1 any eq 24
Dell(conf-ext-nacl)#permit tcp host 10.1.1.1 any fragment
Dell(conf-ext-nacl)#deny ip any any fragment
Dell(conf-ext-nacl)
Example of Logging Denied Packets
To log all the packets denied and to override the implicit deny rule and the implicit permit rule for TCP/
UDP fragments, use a configuration similar to the following.
deny ip any any fragment
Dell(conf)#ip access-list extended ABC
Dell(conf-ext-nacl)#permit tcp any any fragment
100
Access Control Lists (ACLs)
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.