HPE FlexNetwork 5510 HI Series User manual

HPE FlexNetwork 5510 HI Switch Series
Fundamentals
Configuration Guide
P
art number: 5200-0067a
Software
version: Release 11xx
Document version: 6W101-20161221

© Copyright 2015, 2016 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.

i
Contents
Using the CLI ··················································································1
CLI views ···································································································································1
Entering system view from user view·························································································2
Returning to the upper-level view from any view··········································································2
Returning to user view············································································································2
Accessing the CLI online help·········································································································2
Using the undo form of a command·································································································3
Entering a command·····················································································································3
Editing a command line ··········································································································3
Entering a text or string type value for an argument ·····································································4
Abbreviating commands ·········································································································4
Configuring and using command aliases····················································································4
Configuring and using command hotkeys···················································································5
Enabling redisplaying entered-but-not-submitted commands ·························································6
Understanding command-line error messages···················································································7
Using the command history function ································································································7
Command buffering rules········································································································8
Repeating commands in the command history buffer for a line·······················································8
Controlling the CLI output··············································································································9
Pausing between screens of output ··························································································9
Numbering each output line from a display command···································································9
Filtering the output from a display command············································································· 10
Saving the output from a display command to a file···································································· 12
Viewing and managing the output from a display command effectively ··········································13
Saving the running configuration··································································································· 13
Login overview ··············································································14
Logging in through the console port for the first device access·················15
Logging in to the CLI·······································································17
CLI overview····························································································································· 17
User lines ·························································································································· 17
Login authentication modes··································································································· 18
User roles·························································································································· 18
FIPS compliance························································································································ 18
Logging in through the console port locally······················································································ 19
Disabling authentication for console login················································································· 19
Configuring password authentication for console login································································ 20
Configuring scheme authentication for console login·································································· 20
Configuring common AUX line settings···················································································· 21
Logging in through Telnet············································································································ 22
Configuring Telnet login on the device····················································································· 23
Using the device to log in to a Telnet server ·············································································27
Logging in through SSH ·············································································································· 28
Configuring the device as an SSH server················································································· 28
Using the device to log in to an SSH server·············································································· 30
Logging in through a pair of modems····························································································· 30
Displaying and maintaining CLI login ····························································································· 33
Accessing the device through SNMP··················································35
Controlling user access ···································································36
FIPS compliance························································································································ 36
Controlling Telnet/SSH logins······································································································· 36
Configuration procedures······································································································ 36
Configuration example ········································································································· 36

ii
Controlling SNMP access············································································································ 37
Configuration procedure ······································································································· 37
Configuration example ········································································································· 38
Configuring command authorization······························································································· 39
Configuration procedure ······································································································· 39
Configuration example ········································································································· 40
Configuring command accounting ································································································· 41
Configuration procedure ······································································································· 42
Configuration example ········································································································· 42
Configuring RBAC··········································································44
Overview·································································································································· 44
Permission assignment ········································································································ 44
Assigning user roles ············································································································ 46
FIPS compliance························································································································ 47
Configuration task list·················································································································· 47
Creating user roles····················································································································· 47
Configuring user role rules··········································································································· 47
Configuration restrictions and guidelines·················································································· 48
Configuration procedure ······································································································· 48
Configuring feature groups··········································································································· 49
Configuring resource access policies····························································································· 49
Configuring the interface policy of a user role ···········································································49
Configuring the VLAN policy of a user role ··············································································· 50
Configuring the VPN instance policy of a user role····································································· 50
Assigning user roles ··················································································································· 51
Enabling the default user role feature······················································································ 51
Assigning user roles to remote AAA authentication users···························································· 51
Assigning user roles to local AAA authentication users······························································· 51
Assigning user roles to non-AAA authentication users on user lines··············································52
Configuring temporary user role authorization·················································································· 53
Configuration guidelines ······································································································· 53
Configuring user role authentication························································································ 54
Obtaining temporary user role authorization ············································································· 55
Displaying RBAC settings············································································································ 55
RBAC configuration examples······································································································ 55
RBAC configuration example for local AAA authentication users ··················································55
RBAC configuration example for RADIUS authentication users···················································· 57
RBAC temporary user role authorization configuration example (HWTACACS authentication) ··········· 60
RBAC temporary user role authorization configuration example (RADIUS authentication)················· 64
Troubleshooting RBAC ··············································································································· 67
Local users have more access permissions than intended ··························································67
Login attempts by RADIUS users always fail ············································································67
Configuring FTP·············································································69
FIPS compliance························································································································ 69
Using the device as an FTP server································································································ 69
Configuring basic parameters································································································ 69
Configuring authentication and authorization ············································································70
Manually releasing FTP connections······················································································· 71
Displaying and maintaining the FTP server··············································································· 71
FTP server configuration example ·························································································· 71
Using the device as an FTP client ·································································································72
Establishing an FTP connection····························································································· 72
Managing directories on the FTP server ·················································································· 74
Working with files on the FTP server······················································································· 74
Changing to another user account·························································································· 75
Maintaining and troubleshooting the FTP connection ·································································75
Terminating the FTP connection····························································································· 76
Displaying command help information ····················································································· 76
Displaying and maintaining FTP client····················································································· 76
FTP client configuration example···························································································· 76

iii
Configuring TFTP···········································································79
FIPS compliance························································································································ 79
Configuring the device as an IPv4 TFTP client················································································· 79
Configuring the device as an IPv6 TFTP client················································································· 80
Managing the file system ·································································81
FIPS compliance························································································································ 81
Storage medium naming rules······································································································ 81
File name formats ······················································································································ 81
Managing files··························································································································· 82
Displaying file information ····································································································· 82
Displaying the contents of a text file························································································ 82
Renaming a file··················································································································· 83
Copying a file ····················································································································· 83
Moving a file······················································································································· 83
Compressing/decompressing a file ························································································· 83
Archiving/extracting files······································································································· 83
Deleting/restoring a file········································································································· 84
Deleting files from the recycle bin··························································································· 84
Calculating the file digest······································································································ 84
Managing directories ·················································································································· 85
Displaying directory information ····························································································· 85
Displaying the current working directory··················································································· 85
Changing the current working directory···················································································· 85
Creating a directory ············································································································· 85
Removing a directory··········································································································· 85
Managing storage media············································································································· 86
Repairing a storage medium·································································································· 86
Formatting a storage medium································································································ 86
Mounting or unmounting a storage medium·············································································· 87
Partitioning a USB disk········································································································· 87
Setting the operation mode for files and folders ··············································································· 88
Managing configuration files ·····························································89
Overview·································································································································· 89
Configuration types·············································································································· 89
Startup configuration loading process······················································································ 89
Configuration file formats······································································································ 90
Startup configuration file selection ·························································································· 91
Configuration file content organization and format ····································································· 91
FIPS compliance························································································································ 91
Enabling configuration encryption·································································································· 92
Displaying configuration differences between configuration files·························································· 92
Saving the running configuration··································································································· 93
Restrictions and guidelines···································································································· 93
Using different methods to save the running configuration··························································· 93
Configuring configuration rollback ································································································· 94
Configuration task list··········································································································· 94
Configuring configuration archive parameters··········································································· 95
Enabling automatic configuration archiving··············································································· 96
Manually archiving the running configuration ············································································96
Rolling back configuration····································································································· 96
Configuring configuration commit delay·························································································· 97
Specifying a next-startup configuration file······················································································ 98
Backing up the main next-startup configuration file to a TFTP server ··················································· 99
Restoring the main next-startup configuration file from a TFTP server·················································· 99
Deleting a next-startup configuration file······················································································· 100
Displaying and maintaining configuration files················································································ 100
Upgrading software ······································································ 102
Overview································································································································ 102

iv
Software types·················································································································· 102
Software file naming conventions ························································································· 102
Comware image redundancy and loading procedure································································ 102
System startup process ······································································································ 103
Upgrade methods ···················································································································· 104
Upgrade procedure summary····································································································· 104
Preparing for the upgrade·········································································································· 105
Preloading the Boot ROM image to Boot ROM ·············································································· 105
Specifying startup images and completing the upgrade ··································································· 105
Specifying startup images for all devices in bulk······································································ 105
Specifying startup images for devices one by one···································································· 106
Displaying and maintaining software image settings ······································································· 107
Software upgrade examples······································································································· 108
Example of software upgrade through a reboot······································································· 108
Patch installation example··································································································· 109
Performing an ISSU······································································ 111
Overview································································································································ 111
ISSU methods ·················································································································· 111
ISSU commands··············································································································· 111
Feature and software version compatibility···················································································· 112
Preparing for ISSU··················································································································· 112
Identifying availability of ISSU and licensing requirements························································· 112
Verifying the device operating status····················································································· 112
Preparing the upgrade images····························································································· 112
Identifying requirements for a patch or an upgrade to a middle version········································ 112
Identifying the ISSU method································································································ 113
Verifying feature status······································································································· 113
Determining the upgrade procedure······················································································ 113
Understanding ISSU guidelines···························································································· 114
Logging in to the device through the console port···································································· 114
Saving the running configuration ·························································································· 114
Performing an ISSU by using issu commands ··············································································· 114
Upgrading a multichassis IRF fabric······················································································ 114
Upgrading a single-chassis IRF fabric ··················································································· 116
Performing an ISSU by using install commands············································································· 117
ISSU task list···················································································································· 117
Decompressing an .ipe file·································································································· 117
Installing or upgrading software images················································································· 117
Uninstalling feature or patch images ····················································································· 118
Rolling back the running software images ·············································································· 118
Aborting a software activate/deactivate operation···································································· 119
Committing software changes······························································································ 119
Verifying software images··································································································· 119
Removing inactive software images······················································································ 120
Displaying and maintaining ISSU ································································································ 120
Troubleshooting ISSU··············································································································· 121
Failure to execute the issu load/issu run switchover/issu commit/install activate/install deactivate
command························································································································· 121
ISSU examples for using issu commands····················································································· 121
Software image upgrade to a compatible version····································································· 121
Software image upgrade to an incompatible version ································································ 123
Software image rollback example························································································· 125
ISSU examples for using install commands··················································································· 128
Software image upgrade example ························································································ 128
Software image rollback example························································································· 130
Managing the device····································································· 132
Device management task list······································································································ 132
Configuring the device name······································································································ 132
Configuring the system time······································································································· 133
Specifying the system time source························································································ 133

v
Setting the system time ······································································································ 133
Enabling displaying the copyright statement·················································································· 134
Configuring banners ················································································································· 134
Banner types···················································································································· 134
Banner input modes··········································································································· 134
Configuration procedure ····································································································· 135
Setting the table capacity mode·································································································· 136
Rebooting the device················································································································ 136
Configuration guidelines ····································································································· 137
Rebooting devices immediately at the CLI·············································································· 137
Scheduling a device reboot ································································································· 137
Scheduling a task····················································································································· 137
Configuration guidelines ····································································································· 137
Configuration procedure ····································································································· 138
Schedule configuration example··························································································· 139
Disabling password recovery capability ························································································ 143
Specifying the preferred airflow direction ······················································································ 143
Setting the port status detection timer ·························································································· 144
Configuring CPU usage monitoring······························································································ 144
Setting memory thresholds ········································································································ 144
Configuring the temperature alarm thresholds ··············································································· 146
Disabling all USB interfaces······································································································· 146
Verifying and diagnosing transceiver modules ··············································································· 147
Verifying transceiver modules······························································································ 147
Diagnosing transceiver modules··························································································· 147
Specifying an ITU channel number for a transceiver module ···························································· 148
Restoring the factory-default settings and states············································································ 148
Displaying and maintaining device management configuration·························································· 149
Using Tcl···················································································· 151
Tcl usage guidelines and restrictions ··························································································· 151
Executing Comware commands in Tcl configuration view ································································ 151
Using Python··············································································· 153
Entering the Python shell··········································································································· 153
Executing a Python script ·········································································································· 153
Python usage example·············································································································· 153
Network requirements········································································································ 153
Configuration procedure ····································································································· 153
Verifying the configuration··································································································· 154
Comware V7 extended Python API·················································· 155
Importing and using the Comware V7 extended Python API····························································· 155
Comware V7 extended Python API functions················································································· 155
CLI class ························································································································· 155
Transfer class··················································································································· 157
API get_self_slot··············································································································· 158
API get_standby_slot········································································································· 158
Using automatic configuration························································· 160
Overview································································································································ 160
Automatic configuration task list·································································································· 160
Configuring the file server ··································································································· 161
Preparing the files for automatic configuration········································································· 161
Configuring the DHCP server ······························································································ 162
Configuring the DNS server································································································· 163
Configuring the gateway····································································································· 163
Selecting the interfaces used for automatic configuration·························································· 164
Starting and completing automatic configuration······································································ 164
Automatic configuration examples······························································································· 164
Automatic configuration using TFTP server ············································································ 164
Automatic configuration using HTTP server and Tcl script························································· 169

vi
Automatic configuration using HTTP server and Python script ··················································· 170
Automatic IRF setup ·········································································································· 171
Document conventions and icons ···················································· 174
Conventions···························································································································· 174
Network topology icons ············································································································· 175
Support and other resources··························································· 176
Accessing Hewlett Packard Enterprise Support·············································································· 176
Accessing updates··················································································································· 176
Websites ························································································································· 177
Customer self repair ·········································································································· 177
Remote support ················································································································ 177
Documentation feedback ···································································································· 177
Index························································································· 179

1
Using the CLI
At the command-line interface (CLI), you can enter text commands to configure, manage, and
monitor the device. The following text is displayed when you access the CLI:
******************************************************************************
* Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP *
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<Sysname>
You can use different methods to log in to the CLI, including through the console port, Telnet, and
SSH. For more information about login methods, see "Login overview."
CLI views
Commands are grouped in different views by function. To use a command, you must enter its view.
CLI views are hierarchically organized, as shown in Figure 1. Each view has a unique prompt, from
which you can identify where you are and what you can do. For example, the prompt
[Sysname-vlan100] shows that you are in VLAN 100 view and can configure attributes for that
VLAN.
Figure 1 CLI views
You are placed in user view immediately after you log in to the CLI. The user view prompt is
<Device-name>, where Device-name indicates the device name. The device name is Sysname by
default. You can change it by using the sysname command.
In user view, you can perform the following tasks:
•
Perform basic operations including display, debug, file management, FTP, Telnet, clock setting,
and reboot.
•
Enter system view. The system view prompt is [Device-name].
In system view, you can perform the following tasks:
•
Configure settings that affect the device as a whole, such as the daylight saving time, banners,
and hotkeys.
•
Enter different function views. For example, you can perform the following tasks:
VLAN view
Interface
view
……
System
view
User view User line
view
Local user
view

2
Enter interface view to configure interface parameters.
Enter VLAN view to add ports to the VLAN.
Enter user line view to configure login user attributes.
To display all commands available in a view, enter a question mark (?) at the view prompt.
Entering system view from user view
Task
Command
Enter system view. system-view
Returning to the upper-level view from any view
Task
Command
Return to the upper-level view from any view. quit
Executing the quit command in user view terminates your connection to the device.
In public key view, use the peer-public-key end command to return to system view.
Returning to user view
To return directly to user view from any other view, use the return command or press Ctrl+Z.
Task
Command
Return directly to user view. return
Accessing the CLI online help
The CLI online help is context sensitive. Enter a question mark at any prompt or in any position of a
command to display all available options.
To access the CLI online help, use one of the following methods:
•
Enter a question mark at a view prompt to display the first keyword of every command available
in the view. For example:
<Sysname> ?
User view commands:
access-list acl
archive Archive configuration
backup Backup the startup configuration file to a TFTP server
boot-loader Software image file management
…
•
Enter a space and a question mark after a command keyword to display all available keywords
and arguments at the position.
If the question mark is in the place of a keyword, the CLI displays all possible keywords,
each with a brief description. For example:
<Sysname> terminal ?
debugging Enable to display debugging logs on the current terminal

3
logging Display logs on the current terminal
monitor Enable to display logs on the current terminal
If the question mark is in the place of an argument, the CLI displays the description for the
argument. For example:
<Sysname> system-view
[Sysname] interface vlan-interface ?
<1-4094> Vlan-interface interface number
[Sysname] interface vlan-interface 1 ?
<cr>
[Sysname] interface vlan-interface 1
<1-4094> is the value range for the argument. <cr> indicates that the command is complete
and you can press Enter to execute the command.
•
Enter an incomplete keyword string followed by a question mark to display all keywords starting
with that string. For example:
<Sysname> q?
quit
<Sysname> display ftp?
ftp
ftp-server
ftp-user
Using the undo form of a command
Most configuration commands have an undo form for the following tasks:
•
Canceling a configuration.
•
Restoring the default.
•
Disabling a feature.
For example, the info-center enable command enables the information center. The undo
info-center enable command disables the information center.
Entering a command
When you enter a command, you can perform the following tasks:
•
Use keys or hotkeys to edit the command line.
•
Use abbreviated keywords or keyword aliases.
Editing a command line
To edit a command line, use the keys listed in Table 1 or the hotkeys listed in Table 3. When you are
finished, you can press Enter to execute the command.
Acommand line can have up to 512 characters, including keywords, arguments, spaces, and special
characters.
Table 1 Command line editing keys
Keys
Function
Common keys If the edit buffer is not full, pressing a common key inserts a character atthe
cursor and moves the cursor to the right. The edit buffer can store up to 511

4
Keys
Function
characters. Unless the buffer is full, all common characters that you enter
before pressing Enter are saved in the edit buffer.
Backspace Deletes the character to the left of the cursor and moves the cursor back
one character.
Left arrow key (←) Moves the cursor one character to the left.
Right arrow key (→) Moves the cursor one character to the right.
Up arrow key (↑) Displays the previous command in the command history buffer.
Down arrow key (↓) Displays the next command in the command history buffer.
Tab
If you press Tab after entering part of a keyword, the system automatically
completes the keyword.
•If a unique match is found, the system displays the complete keyword.
•If there is more than one match, press Tab multiple times to pick the
keyword you want to enter.
•If there is no match, the system does not modify what you entered but
displays it again in the next line.
Entering a text or string type value for an argument
A text type argument value can contain printable characters except a question mark (?).
A string type argument value can contain any printable characters except for the following
characters:
•
Question mark (?).
•
Quotation mark (").
•
Backward slash (\).
•
Space.
A specific argument might have more requirements. For more information, see the relevant
command reference.
To enter a printable character, you can enter the character or its ASCII code in the range of 32 to 126.
Abbreviating commands
You can enter a command line quickly by entering incomplete keywords that uniquely identify the
complete command. In user view, for example, commands starting with an sinclude startup
saved-configuration and system-view. To enter the command system-view, you only need to
type sy. To enter the command startup saved-configuration, type st s.
You can also press Tab to complete an incomplete keyword.
Configuring and using command aliases
After you configure an alias for a command, you can enter the alias to execute the command. For
example, you can configure the alias siprt for the display ip routing-table command. Then, to
execute the command, you only need to enter siprt.
Usage guidelines
After you successfully execute a command by using its alias, the system saves the command,
instead of its alias, to the running configuration.

5
The command string represented by an alias can include up to nine parameters. Each parameter
starts with the dollar sign ($) and a sequence number in the range of 1 to 9. For example, you can
configure the alias shinc for the command display ip $1 | include $2. Then, to execute the display
ip routing-table | include Static command, you can enter shinc routing-table Static. To execute
the display ip interface | include GigabitEthernet1/0/1 command, you can enter shinc interface
GigabitEthernet1/0/1.
To use a command alias for a command that has parameters, you must specify a value for each
parameter. If you fail to do this, the system informs you that the command is incomplete and displays
the command string represented by the alias.
Table 2 lists the system-defined command aliases.
Table 2 System-defined command aliases
Alias
Command
access-list acl
end return
erase delete
exit quit
hostname
sysname
logging info-center
no undo
show display
write save
Configuration procedure
To configure a command alias:
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Configure a command alias. alias alias command By default, the device has a set of
system-
defined command aliases,
as shown in Table 2.
3. (Optional.) Display command
aliases.display alias [alias ]
This command is available in any
view.
Configuring and using command hotkeys
The system defines the hotkeys shown in Table 3 and provides five configurable command hotkeys.
Pressing a command hotkey is the same as entering a command.
If a hotkey is also defined by the terminal software you are using to interact with the device, the
terminal software definition takes effect.
To configure a command hotkey:
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Assign acommand
hotkey { ctrl_g | ctrl_l | ctrl_o |
The following are the defaults:

6
Step
Command
Remarks
to a hotkey.
ctrl_t | ctrl_u } command
•Ctrl+G is assigned the display
current-configuration command.
•Ctrl+L is assigned the
display ip
routing-table command.
•Ctrl+O is assigned the undo debugging
all command.
•No command is assigned to Ctrl+T or
Ctrl+U.
3. (Optional.) Display
hotkeys. display hotkey This command is available in any view.
Table 3 System-reserved hotkeys
Hotkey
Function
Ctrl+A Moves the cursor to the beginning of a line.
Ctrl+B Moves the cursor one character to the left.
Ctrl+C Stops the current command.
Ctrl+D Deletes the character at the cursor.
Ctrl+E
Moves the cursor to the end of a line.
Ctrl+F
Moves the cursor one character to the right.
Ctrl+H Deletes the character to the left of the cursor.
Ctrl+K Aborts the connection request.
Ctrl+R Redisplays the current line.
Ctrl+V Pastes text from the clipboard.
Ctrl+W Deletes the word to the left of the cursor.
Ctrl+X Deletes all characters to the left of the cursor.
Ctrl+Y Deletes all characters from the cursor to the end of the line.
Ctrl+Z Returns to user view.
Ctrl+] Terminates the current connection.
Esc+B Moves the cursor back one word.
Esc+D Deletes all characters from the cursor to the end of the word.
Esc+F Moves the cursor forward one word.
Enabling redisplaying entered-but-not-submitted commands
Your input might be interrupted by system information output. If redisplaying
entered-but-not-submitted commands is enabled, the system redisplays your input after finishing the
output. You can then continue entering the command line.
To enable redisplaying entered-but-not-submitted commands:
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Enable redisplaying info-center synchronous
By default, the system does not redisplay

7
Step
Command
Remarks
entered-but-not-sub
mitted commands.
entered-but-not-submitted commands.
For more information about this command, see
Network Management and Monitoring
Command Reference.
Understanding command-line error messages
After you press Enter to submit a command, the command line interpreter examines the command
syntax.
•
If the command passes syntax check, the CLI executes the command.
•
If the command fails syntax check, the CLI displays an error message.
Table 4 Common command-line error messages
Error message
Cause
% Unrecognized command found at '^' position. The keyword in the marked position is invalid.
% Incomplete command found at '^' position. One or more
required keywords or arguments are
missing.
% Ambiguous command found at '^' position.
The entered character sequence matches more than
one command.
% Too many parameters.
The entered character sequence contains excessive
keywords or arguments.
% Wrong parameter found at '^' position. The argument in the marked position is invalid.
Using the command history function
The system automatically saves commands successfully executed by a login user to the following
two command history buffers:
•
Command history buffer for the user line.
•
Command history buffer for all user lines.
Table 5 Comparison between the two types of command history buffers
Item
Command history buffer for a user
line
Command history buffer for all
user lines
What kind of
commands are saved
in the buffer?
Commands
successfully executed by the
current user of the user line.
Commands successfully executed
by all login users.
Cleared when the
user logs out? Yes. No.
How to view buffered
commands? Use the display history-command
command. Use the display history-command all command.
How to recall buffered
commands?
•(Method 1.) Navigate to the command
in the buffer and press Enter
. To
navigate to a command in the buffer:

In Windows 200xor Windows XP
You cannot call buffered commands.

8
Item
Command history buffer for a user
line
Command history buffer for all
user lines
HyperTerminal or Telnet, use the up
or down arrow key (↑ or ↓).
In Windows 9xHyperTerminal, use
Ctrl+P and Ctrl+N.
•(Method 2.) Use the repeat command.
For more information, see "Repeating
commands in the command history
buffer for a line."
How to set the buffer
size?
Use the history-command max-size
size-value command in user line view to set
the buffer size.
By default, the buffer can store up to 10
commands.
You cannot set the buffer size.
By default, the buffer can store up to
1024 commands.
How to dis
able the
buffer?
Setting the buffer size to 0 disables the
buffer. You cannot disable the buffer.
Command buffering rules
The system follows these rules when buffering commands:
•
Buffering a command in the exact format in which the command was entered. For example, if
you enter an incomplete command, the buffered command is also incomplete. If you enter a
command with a command keyword alias, the buffered command also uses the alias.
•
If you enter a command in the same format multiple times in succession, the system buffers the
command only once. If you enter a command in different formats multiple times, the system
buffers each command format. For example, display cu and display current-configuration are
buffered as two entries but successive repetitions of display cu create only one entry.
•
To buffer a new command when a buffer is full, the system deletes the oldest command entry in
the buffer.
Repeating commands in the command history buffer for a
line
You can recall and execute commands in the command history buffer for the current user line
multiple times.
To repeat commands in the command history buffer for the current user line:
Task
Command
Remarks
Repeat commands in the
command history buffer
for the current user line.
repeat [number ] [ count
times ] [ delay seconds ]
This command is available in any view.
However, to repeat a command, you must first
enter the view for the command.
To repeat
multiple commands, you must first enter the
view for the first command.
This command executes commands in the
order they were executed.
The system waits for your interaction when it
repeats an interactive command.

9
Controlling the CLI output
This section describes the CLI output control features that help you identify the desired output.
Pausing between screens of output
The system automatically pauses after displaying a screen if the output is too long to fit on one
screen. You can use the keys described in "Output controlling keys" to display more information or
stop the display.
By default, up to 24 lines can be displayed on a screen. You can change the limit by using the
screen-length screen-length command. For more information about this command, see
Fundamentals Command Reference.
You can also disable pausing between screens of output for the current session. Then, all output is
displayed at one time and the screen is refreshed continuously until the final screen is displayed.
Output controlling keys
Keys
Function
Space Displays the next screen.
Enter Displays the next line.
Ctrl+C Stops the display and cancels the command execution.
<PageUp> Displays the previous page.
<PageDown> Displays the next page.
Disabling pausing between screens of output
To disable pausing between screens of output, execute the following command in user view:
Task
Command
Remarks
Disable pausing
between screens of
output for the current
session.
screen-length
disable
By default, a session uses the screen-length
screen-length command settings in user line view.
This command is a one-time command and takes effect
only for the current session.
Numbering each output line from a display command
You can use the | by-linenum option to prefix each display command output line with a number for
easy identification.
Each line number is displayed as a 5-character string and might be followed by a colon (:) or hyphen
(-). If you specify both | by-linenum and | begin regular-expression for a display command, a
hyphen is displayed for all lines that do not match the regular expression.
To number each output line from a display command:
Task
Command
Number each output line from a display command. display command |by-linenum
For example:
# Display system time information, numbering each output line.

10
<Sysname> display clock | by-linenum
1: 06:14:21 UTC Sat 01/01/2011
Filtering the output from a display command
You can use the | { begin | exclude | include } regular-expression option to filter the display
command output.
•
begin—Displays the first line matching the specified regular expression and all subsequent
lines.
•
exclude—Displays all lines not matching the specified regular expression.
•
include—Displays all lines matching the specified regular expression.
•
regular-expression—Acase-sensitive string of 1 to 256 characters, which can contain the
special characters described in Table 6.
The required filtering time increases with the complexity of the regular expression. To abort the
filtering process, press Ctrl+C.
Table 6 Special characters supported in a regular expression
Characters
Meaning
Examples
^ Matches the beginning of a line. "^u" matches all lines beginning with "u". A line
beginning with "Au" is not matched.
$ Matches the end of a line. "u$" matches all lines ending with "u".
A line
ending with "uA" is not matched.
. (period) Matches any single character. ".s" matches "as" and "bs".
* Matches the preceding
character or
string zero, one, or multiple times. "zo*" matches "z" and "zoo", and "(zo)*" matches
"zo" and "zozo".
+ Matches the preceding
character or
string one or multiple times. "zo+" matches "zo" and "zoo", but not "z".
| Matches the preceding or succeeding
string. "def|int" matches a line containing "def" or "int".
( )
Matches the string in the
parentheses, usually used together
with the plus sign (+) or asterisk sign
(*).
"(123A)" matches "123A".
"408(12)+" matches "40812" and "408121212",
but not "408".
\N
Matches the preceding strings in
parentheses, with the Nth string
repeated once.
"(string)\1
" matches a string containing
"stringstring".
"(string1)(string2)\2" matches a string containing
"string1string2string2".
"(string1)(string2)\1\2
" matches a string
containing " string1string2string1string2".
[ ] Matches
a single character in the
brackets.
"[16A]" matches a string containing 1, 6, or A;
"[1-36A]" matches a string containing 1, 2, 3, 6, or
A (- is a hyphen).
To match the character "]", putit immediately after
"[", for example, []abc]. There is no such limit on
"[".
[^] Matches a single character that is not
in the brackets.
"[^16A]"
matches a string that contains one or
more characters except for 1, 6, or A, such as
"abc". A match can also contain 1, 6, or A (such
as "m16"), but it cannot
contain these three
characters only (such as 1, 16, or 16A).

11
Characters
Meaning
Examples
{n} Matches the preceding character n times. The number n
must be a
nonnegative integer. "o{2}" matches "food", but not "Bob".
{n,} Matches the preceding character n
times or more. The number nmust be
a nonnegative integer. "o{2,}" matches "foooood", but not "Bob".
{n,m}
Matches the preceding character nto
mtimes or more. The numbers nand
mmust be nonnegative integers and
ncannot be greater than m.
" o{1,3}" matches "fod", "food", and "foooood", but
not "fd".
\<
Matches a string that starts with the
pattern following \
<. A string that
contains the pattern is also a match if
the characters preceding the pattern
are not digits, letters, or underscores.
"\<do" matches "domain" and "doa".
\>
Matches a string that ends with the
pattern preceding \
>. A string that
contains the pattern is also a match if
the characters following the pattern
are not digits, letters, or underscores.
"do\>" matches "undo" and "cdo".
\b Matches a word that starts with the pattern following \b or ends with the
pattern preceding \b.
"er\b" matches "never", but not "verb" or "erase".
"\ber" matches "erase", but not "verb" or "never".
\B
Matches a word that contains the
pattern but does not start or end with
the pattern. "er\B" matches "verb", but not "never" or "erase".
\w Same as [A-Za-z0-9_]
, matches a
digit, letter, or underscore. "v\w" matches "vlan"and "service".
\W Same as [^A-Za-z0-9_]
, matches a
character that is not a digit, letter, or
underscore. "\Wa" matches "-a", but not "2a" or "ba".
\
Escape character. If a special
character listed in this table follows \,
the specific meaning of the character
is removed.
"\\" matches a string containing "\", "\^" matches a
string containing "^", and "\\b" matches a string
containing "\b".
For example:
# Use |begin line for the display current-configuration command to match the first line of output
that contains line to the last line of output.
<Sysname> display current-configuration | begin line
line class aux
user-role network-admin
#
line class vty
user-role network-operator
#
line aux 0
user-role network-admin
#
line vty 0 63
authentication-mode scheme

12
user-role network-operator
#
ssh server enable
#
return
# Use | exclude Direct for the display ip routing-table command to filter out direct routes and
display only the non-direct routes.
<Sysname> display ip routing-table | exclude Direct
Destinations : 12 Routes : 12
Destination/Mask Proto Pre Cost NextHop Interface
2.2.2.0/24 OSPF 10 2 1.1.2.2 Vlan 2
# Use | include snmp for the display current-configuration command to filter in entries that
contain snmp.
<Sysname> display current-configuration | include snmp
snmp-agent
snmp-agent community write private
snmp-agent community read public
snmp-agent sys-info version all
snmp-agent target-host trap address udp-domain 192.168.1.26 params securityname public
Saving the output from a display command to a file
A display command shows certain configuration and operation information of the device. Its output
might vary over time or with user configuration or operation. You can save the output to a file for
future retrieval or troubleshooting.
Use one of the following methods to save the output from a display command:
•
Save the output to a separate file. Use this method if you want to use one file for a single
display command.
•
Append the output to the end of a file. Use this method if you want to use one file for multiple
display commands.
To save the output from a display command to a file, use one of the following commands in any view:
Task
Command
Save the output from a display command to a separate file. display command > filename
Append the output from a display command to the end of a file. display command >> filename
For example:
# Save system time information to a separate file named clock.txt.
<Sysname> display clock > clock.txt
# Verify that the system time information is saved to file clock.txt.
<Sysname> more clock.txt
06:03:58 UTC Sat 01/01/2014
# Append system time information to the end of file clock.txt.
<Sysname> display clock >> clock.txt