HP 3100 v2 Series User manual
HPE 3100 v2 Switch Series
Fundamentals
Configuration Guide
Part number: 5998-5990s
Software version: Release 5213 and Release 5213P02
Document version: 6W101-20160506
© Copyright 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 trademarks of the Microsoft group of companies.
Adobe® andAcrobat® are trademarks ofAdobe 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
FIPS compliance················································································································································1
Logging in to the CLI··········································································································································1
Command conventions ······································································································································1
Using the undo form of a command···················································································································2
CLI views ···························································································································································2
Entering system view from user view·········································································································3
Returning to the upper-level view from any view ·······················································································3
Returning to user view from any other view·······························································································3
Accessing the CLI online help····························································································································4
Entering a command··········································································································································5
Editing a command line······························································································································5
Entering a STRING type value for an argument ························································································5
Abbreviating commands·····························································································································5
Configuring and using command keyword aliases·····················································································6
Configuring and using hotkeys···················································································································6
Enabling redisplaying entered-but-not-submitted commands····································································8
Understanding command-line error messages··································································································8
Using the command history function··················································································································8
Viewing history commands ························································································································9
Setting the command history buffer size for user interfaces······································································9
Controlling the CLI output ··································································································································9
Pausing between screens of output···········································································································9
Filtering the output from a display command···························································································10
Configuring user privilege and command levels ······························································································13
Configuring a user privilege level·············································································································13
Switching the user privilege level·············································································································16
Changing the level of a command············································································································19
Saving the running configuration ·····················································································································19
Displaying and maintaining CLI ·······················································································································19
Login overview······························································································20
Login methods at a glance·······························································································································20
FIPS compliance··············································································································································20
User interfaces·················································································································································21
User interface assignment ·······················································································································21
User interface identification······················································································································21
Logging in to the CLI·····················································································22
FIPS compliance··············································································································································22
Logging in through the console port for the first time·······················································································22
Configuring console login control settings································································································24
Configuring none authentication for console login (not supported in FIPS mode)···································25
Configuring password authentication for console login (not supported in FIPS mode)····························25
Configuring scheme authentication for console login···············································································26
Configuring common console login settings (optional)·············································································28
Logging in through Telnet (not supported in FIPS mode)················································································29
Configuring none authentication for Telnet login······················································································31
Configuring password authentication for Telnet login··············································································31
Configuring scheme authentication for Telnet login·················································································32
Configuring common settings for VTY user interfaces (optional)·····························································34
Using the device to log in to a Telnet server····························································································35
Setting the DSCP value for IP to use for outgoing Telnet packets···························································36
Logging in through SSH···································································································································37
Configuring the SSH server on the device·······························································································37
Using the device as an SSH client to log in to the SSH server································································39
Modem dial-in through the console port···········································································································40
ii
Setting up the configuration environment·································································································41
Configuring none authentication for modem dial-in (not supported in FIPS mode) ·································43
Configuring password authentication for modem dial-in (not supported in FIPS mode)··························44
Configuring scheme authentication for modem dial-in·············································································44
Configuring common settings for modem dial-in (optional)······································································46
Displaying and maintaining CLI login···············································································································47
Logging in to the Web interface ····································································49
FIPS compliance··············································································································································49
Configuring HTTP login····································································································································49
Configuring HTTPS login ·································································································································50
Displaying and maintaining Web login·············································································································52
HTTP login configuration example···················································································································53
Network requirements······························································································································53
Configuration procedure···························································································································53
HTTPS login configuration example ················································································································53
Network requirements······························································································································53
Configuration procedure···························································································································54
Logging in through SNMP·············································································56
Configuring SNMP login···································································································································56
Prerequisites············································································································································56
Configuring SNMPv3 settings··················································································································56
Configuring SNMPv1 or SNMPv2c settings·····························································································57
NMS login example··········································································································································57
Network requirements······························································································································57
Configuration procedure···························································································································58
Controlling user logins ··················································································59
FIPS compliance··············································································································································59
Controlling Telnet logins (not supported in FIPS mode) ··················································································59
Configuring source IP-based Telnet login control····················································································59
Configuring source/destination IP-based Telnet login control··································································59
Configuring source MAC-based Telnet login control················································································60
Telnet login control configuration example·······························································································60
Configuring source IP-based SNMP login control····························································································61
Configuration procedure···························································································································61
SNMP login control configuration example······························································································62
Configuring Web login control··························································································································63
Configuring source IP-based Web login control·······················································································63
Logging off online Web users···················································································································63
Web login control configuration example·································································································64
Configuring the login delay feature ··················································································································64
Configuring FTP····························································································65
FIPS compliance··············································································································································65
Using the device as an FTP client ···················································································································65
Establishing an FTP connection···············································································································65
Setting the DSCP value for IP to use for outgoing FTP packets······························································67
Managing directories on the FTP server··································································································67
Working with the files on the FTP server ·································································································67
Switching to another user account···········································································································68
Maintaining and troubleshooting the FTP connection··············································································68
Terminating the FTP connection··············································································································69
FTP client configuration example·············································································································69
Using the device as an FTP server··················································································································70
Configuring basic parameters··················································································································70
Configuring authentication and authorization···························································································71
Associating an SSL server policy with the FTP service···········································································72
FTP server configuration example···········································································································72
Displaying and maintaining FTP ······················································································································74
iii
Configuring TFTP··························································································75
FIPS compliance··············································································································································75
Prerequisites····················································································································································75
Using the device as a TFTP client ···················································································································75
Displaying and maintaining the TFTP client·····································································································76
TFTP client configuration example ··················································································································77
Managing the file system··············································································78
Storage medium naming rules·························································································································78
File name formats ············································································································································78
Managing files··················································································································································78
Displaying file information························································································································79
Displaying file contents ····························································································································79
Renaming a file········································································································································79
Copying a file ···········································································································································79
Moving a file·············································································································································79
Deleting/restoring a file ····························································································································79
Emptying the recycle bin··························································································································80
Managing directories········································································································································80
Displaying directory information···············································································································80
Displaying the current working directory··································································································80
Changing the current working directory ···································································································80
Creating a directory··································································································································81
Removing a directory·······························································································································81
Managing storage media ·································································································································81
Managing storage medium space············································································································81
Performing batch operations····························································································································81
Setting the file system operation mode············································································································82
File system management examples·················································································································82
Managing configuration files·········································································84
Overview··························································································································································84
Configuration types··································································································································84
Configuration file format and content·······································································································84
Next-startup configuration file redundancy·······························································································85
Startup with a configuration file················································································································85
Saving the running configuration ·····················································································································85
Saving configuration in different approaches···························································································86
Using automatic configuration backup after a software upgrade·····························································86
Configuring configuration rollback····················································································································87
Configuration task list·······························································································································87
Configuring configuration archive parameters ·························································································88
Enabling automatic configuration archiving······························································································88
Manually archiving running configuration·································································································89
Performing configuration rollback·············································································································89
Specifying a configuration file for the next startup ···························································································90
Backing up the next-startup configuration file to a TFTP server······································································90
Deleting the next-startup configuration file·······································································································90
Restoring the next-startup configuration file from a TFTP server····································································91
Displaying and maintaining a configuration file································································································91
Upgrading software·······················································································93
Software upgrade methods······························································································································93
Upgrading Boot ROM·······································································································································94
Upgrading the entire system software ·············································································································94
Upgrading software by installing hotfixes·········································································································94
Basic concepts·········································································································································95
Patch states ·············································································································································95
Hotfix configuration task list ·····················································································································98
Installation prerequisites ··························································································································98
Installing and running a patch in one step································································································98
iv
Installing a patch step-by-step ·················································································································99
Uninstalling a patch step-by-step···········································································································100
Displaying and maintaining software upgrade ·······························································································101
Software upgrade examples ··························································································································101
Upgrading the entire system software····································································································101
Hotfix configuration example··················································································································103
Managing the device···················································································104
Configuring the device name ·························································································································104
Changing the system time ·····························································································································104
Configuration guidelines·························································································································104
Configuration procedure·························································································································107
Enabling displaying the copyright statement··································································································107
Configuring banners·······································································································································108
Banner message input modes ···············································································································108
Configuration procedure·························································································································109
Configuring the exception handling method···································································································109
Rebooting the device ·····································································································································109
Rebooting devices immediately at the CLI·····························································································110
Scheduling a device reboot····················································································································110
Scheduling jobs··············································································································································111
Job configuration approaches················································································································111
Configuration guidelines·························································································································111
Scheduling a job in the non-modular approach······················································································112
Scheduling a job in the modular approach·····························································································112
Disabling Boot ROM access ··························································································································113
Configuring the port status detection timer ····································································································113
Configuring temperature thresholds for a device···························································································113
Clearing unused 16-bit interface indexes·······································································································114
Disabling password recovery capacity···········································································································114
Verifying and diagnosing transceiver modules ······························································································115
Verifying transceiver modules················································································································115
Diagnosing transceiver modules············································································································115
Displaying and maintaining device management···························································································116
Automatic configuration ··············································································118
Typical application scenario···························································································································118
How automatic configuration works ···············································································································118
Automatic configuration work flow··········································································································119
Using DHCP to obtain an IP address and other configuration information············································119
Obtaining the configuration file from the TFTP server ···········································································120
Executing the configuration file··············································································································122
Document conventions and icons·······························································123
Conventions···················································································································································123
Network topology icons··································································································································124
Support and other resources ······································································125
Accessing Hewlett Packard Enterprise Support ····························································································125
Accessing updates·········································································································································125
Websites ················································································································································126
Customer self repair·······························································································································126
Remote support······································································································································126
Documentation feedback ·······················································································································126
Index···········································································································128
1
Using the CLI
At the command-line interface (CLI), you can enter text commands to configure, manage, and
monitor your device.
Figure 1 CLI example
FIPS compliance
The device supports the FIPS mode that complies with NIST FIPS 140-2 requirements. Support for
features, commands, and parameters might differ in FIPS mode and non-FIPS mode. For more
information about FIPS mode, see Security Configuration Guide.
Logging in to the CLI
You can log in to the CLI in a variety of ways. For example, you can log in through the console port,
or by using Telnet or SSH. For more information about login methods, see "Logging in to the CLI."
Command conventions
Command conventions help you understand the syntax of commands. Commands in product
manuals comply with the conventions listed in Table 1.
Table 1 Command conventions
Convention Description
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars,
from which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select at least one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.
&<1-n> The argument or keyword and argument combination before the ampersand (&) sign
can be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
2
Command keywords are case insensitive.
The following example analyzes the syntax of the clock datetime time date command according
to Table 1.
Figure 2 Understanding command-line parameters
For example, to set the system time to 10:30:20, February 23, 2011, enter the following command
line at the CLI and press Enter:
<Sysname> clock datetime 10:30:20 2/23/2011
Using the undo form of a command
Most configuration commands have an undo form for canceling a configuration, restoring the default,
or disabling a feature. For example, the info-center enable command enables the information
center, and the undo info-center enable command disables the information center.
CLI views
Commands are grouped in different views by function. To use a command, you must enter the view
of the command.
CLI views are organized in a hierarchical structure, as shown in Figure 3. 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 the view of VLAN 100 and can configure attributes for
the VLAN.
You are placed in user view immediately after you are logged in to the CLI. The user view prompt is
<Device-name>, where the Device-name argument defaults to Sysname and can be changed by
using the sysname command. In user view, you can perform some basic operations, including display,
debug, file management, FTP, Telnet, clock setting, and reboot. For more information about the
sysname command, see Fundamentals Command Reference.
From user view, you can enter system view to configure global settings, including the daylight saving
time, banners, and hotkeys. The system view prompt is [Device-name].
From system view, you can enter different function views. For example, you can enter interface view
to configure interface parameters, enter VLAN view to add ports to the specific VLAN, enter user
interface view to configure login user attributes, or create a local user and enter local user view to
configure attributes for the local user.
To display all commands available in a view, enter a question mark (?) at the view prompt.
3
Figure 3 CLI view hierarchy
Entering system view from user view
Task Command
Enter system view from user 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.
NOTE:
In public key code view, use the public-key-code end command to return to the upper-level view
(public key view). In public key view, use the peer-public-key end command to return to system
view.
Returning to user view from any other view
You can return to user view from any other view by using the return command, instead of using the
quit command repeatedly. Pressing Ctrl+Z has the same effect.
To return to user view from any other view:
Task Command
Return to user view. return
4
Accessing the CLI online help
The CLI online help is context sensitive. You can enter a question mark at any point 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 keywords of all commands available
in the view. For example:
<Sysname> ?
User view commands:
archive Specify archive settings
backup Backup next startup-configuration file to TFTP server
boot-loader Set boot loader
bootrom Update/read/backup/restore bootrom
cd Change current directory
…
•Enter some keywords of a command and a question mark separated by a space to display
available keywords and arguments.
{Example 1: The question mark is in the place of a keyword, and the CLI displays all possible
keywords with a brief description for each keyword.
<Sysname> terminal ?
debugging Send debug information to terminal
logging Send log information to terminal
monitor Send information output to current terminal
trapping Send trap information to terminal
{Example 2: The question mark is in the place of an argument, and the CLI displays the
description of the argument.
<Sysname> system-view
[Sysname] interface vlan-interface ?
<1-4094> VLAN interface
[Sysname] interface vlan-interface 1 ?
<cr>
[Sysname] interface vlan-interface 1
The string <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 the string. For example:
<Sysname> f?
fixdisk
format
free
ftp
<Sysname> display ftp?
ftp
ftp-server
ftp-user
5
Entering a command
When you enter a command, you can use some keys or hotkeys to edit the command line, or use
abbreviated keywords or keyword aliases.
Editing a command line
You can use the keys listed in Table 2 or the hotkeys listed in Table 3 to edit a command line.
Table 2 Keys for editing a command line
Key Function
Common keys If the edit buffer is not full, pressing a common key inserts the character at
the position of the cursor and moves the cursor to the right.
Backspace Deletes the character to the left of the cursor and moves the cursor back
one character.
Left arrow key or Ctrl+B Moves the cursor one character to the left.
Right arrow key or Ctrl+F Moves the cursor one character to the right.
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 substitutes the complete
keyword for the incomplete one and displays what you entered in the
next line.
•If there is more than one match, you can press Tab repeatedly to
choose 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 STRING type value for an argument
Generally, a STRING type argument value can contain any printable character (in the ASCII code
range of 32 to 126) other than the question mark (?), quotation mark ("), backward slash (\), and
space. However, a specific STRING type argument might have more strict requirements. For
example, the domain name is of the STRING type. Invalid characters for it include the vertical bar (|),
slash (/), colon (:), asterisk (*), less-than sign (<), greater-than sign (>),and at sign(@), as well as the
question mark (?), quotation mark("), backward slash (\), and space. For more information about the
specific requirements for a STRING type argument, see the relevant command reference.
<Sysname> system-view
[Sysname] domain ?
STRING<1-24> Domain name
Abbreviating commands
You can enter a command line quickly by entering incomplete keywords that can uniquely identify the
complete command. In user view, for example, commands starting with an sinclude startup
saved-configuration and system-view. To enter system view, you only need to enter sy. To set the
configuration file to be used at the next startup, you can enter st s.
You can also press Tab to have an incomplete keyword automatically completed.
6
Configuring and using command keyword aliases
The command keyword alias function allows you to replace the first keyword of a non-undo
command or the second keyword of an undo command with your preferred keyword when you
execute the command. For example, if you configure show as the alias for the display keyword, you
can enter show to execute a display command.
Usage guidelines
•After you successfully execute a command by using a keyword alias, the system saves the
keyword, instead of its alias, to the running configuration.
•If you press Tab after entering part of an alias, the keyword is displayed.
•If a string you entered partially matches a keyword and an alias, the command indicated by the
alias is executed. To execute the command indicated by the keyword, enter the complete
keyword.
•If a string you entered exactly matches a keyword but partially matches an alias, the command
indicated by the keyword is executed. To execute the command indicated by the alias, enter the
complete alias.
•If you enter a string that partially matches multiple aliases, the system gives you a prompt.
Configuration procedure
To configure a command keyword alias:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enable the command
keyword alias function. command-alias enable By default, the command keyword
alias function is disabled.
3. Configure a command
keyword alias. command-alias mapping
cmdkey alias
By default, no command keyword
alias is configured.
You must enter the cmdkey and
alias arguments in their complete
form.
Configuring and using hotkeys
To facilitate CLI operation, the system defines some hotkeys and provides five configurable
command hotkeys. Pressing a command hotkey equals entering a command. For system-reserved
hotkeys, see Table 3.
To configure hotkeys:
Step Command Remarks
1. Enter system view. system-view N/A
7
Step Command Remarks
2. Configure hotkeys. hotkey { CTRL_G | CTRL_L |
CTRL_O | CTRL_T | CTRL_U }
command
By default:
•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. Display hotkeys. display hotkey [ | { begin |
exclude | include }
regular-expression ]
Optional.
Available in any view. See Table 3
for hotkeys reserved by the
system.
The hotkeys in Table 3 are defined by the device. If a hotkey is also defined by the terminal software
that you are using to interact with the device, the definition of the terminal software takes effect.
Table 3 Hotkeys reserved by the system
Hotkey Function
Ctrl+A Moves the cursor to the beginning of the 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 the 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+N Displays the next command in the command history buffer.
Ctrl+P Displays the previous command in the command history buffer.
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 to the right of the cursor.
Ctrl+Z Returns to user view.
Ctrl+] Terminates an incoming connection or a redirect 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.
Esc+N Moves the cursor down one line. This hotkey is available before you press Enter.
8
Hotkey Function
Esc+P Moves the cursor up one line. This hotkey is available before you press Enter.
Esc+< Moves the cursor to the beginning of the clipboard.
Esc+> Moves the cursor to the ending of the clipboard.
Enabling redisplaying entered-but-not-submitted commands
After you enable redisplaying entered-but-not-submitted commands:
•If you entered nothing at the command-line prompt before the system outputs system
information such as logs, the system does not display the command-line prompt after the
output.
•If you entered some information (except Yes or No for confirmation), the system displays a line
break and then display what you have entered after the output.
To enable redisplaying entered-but-not-submitted commands:
Step Command Remarks
4. Enter system view. system-view N/A
5. Enable redisplaying
entered-but-not-submitted
commands. info-center synchronous
By default, the feature is disabled.
For more information about this
command, see Network
Management and Monitoring
Command Reference.
Understanding command-line error messages
If a command line fails the syntax check, the CLI displays error messages.
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 can automatically save successfully executed commands to the command history buffer
for the current user interface. You can view them and execute them again, or set the maximum
number of commands that can be saved in the command history buffer.
9
A command is saved to the command history buffer in the exact format as it was entered. For
example, if you enter an incomplete command, the command saved in the command history buffer is
also incomplete; if you enter a commandby using a command keyword alias, the command saved in
the command history buffer also uses the alias.
If you enter a command in the same format repeatedly in succession, the system buffers the
command only once. If you enter a command repeatedly in different formats, 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 in the buffer.
By default, the command history buffer can save up to 10 commands for each user. To set the
capacity of the command history buffer for the current user interface, use the history-command
max-size command.
Viewing history commands
You can use arrow keys to access history commands in Windows 200x and Windows XPTerminal or
Telnet. In Windows 9x HyperTerminal, the arrow keys are invalid, and you must use Ctrl+P and
Ctrl+N instead.
To view command history, use one of the following methods:
Task Command
Display all commands in the command history
buffer. display history-command [ | { begin | exclude |
include } regular-expression ]
Display the previous history command. Up arrow key or Ctrl+P
Display the next history command. Down arrow key or Ctrl+N
Setting the command history buffer size for user interfaces
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter user interface view. user-interface { first-num1
[ last-num1 ] | { aux | vty }
first-num2 [ last-num2 ] } N/A
3. Set the maximum number of
commands that can be
saved in the command
history buffer.
history-command max-size
size-value
Optional.
By default, the command history
buffer can save up to 10
commands.
Controlling the CLI output
This section describes the CLI output control features that help you quickly identify the desired
output.
Pausing between screens of output
If the output being displayed is more than will fit on one screen, the system automatically pauses
after displaying a screen. By default, up to 24 lines can be displayed on a screen. To change the
10
screen length, use the screen-length screen-length command. For more information about this
command, see Fundamentals Command Reference. To control output, use keys in Table 5.
Table 5 Keys for controlling output
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.
To display all output at one time and refresh the screen continuously until the last screen is
displayed:
Task Command Remarks
Disable pausing between
screens of output for the current
session.
screen-length
disable
The default for a session depends on the
setting of the screen-length command in user
interface view. The default of the
screen-length command is pausing between
screens of output and displaying up to 24 lines
on a screen.
This command is executed in user view, and
takes effect only for the current session. When
you relog in to the device, the default is
restored.
Filtering the output from a display command
You can use one of the following methods to filter the output from a display command:
•Specify the |{ begin | exclude | include } regular-expression option at the end of the command.
•When the system pauses after displaying a screen of output, enter a forward slash (/), minus
sign (-), or plus sign (+) plus a regular expression to filter subsequent output. The forward slash
equals the keyword begin, the minus sign equals the keyword exclude, and the plus sign
equals the keyword include.
The following definitions apply to the begin, exclude, and include keywords:
•begin—Displays the first line that matches the specified regular expression and all lines that
follow.
•exclude—Displays all lines that do not match the specified regular expression.
•include—Displays all lines that match the specified regular expression.
A regular expression is a case-sensitive string of 1 to 256 characters that supports the special
characters in Table 6.
Table 6 Special characters supported in a regular expression
Character Meaning Remarks
^string Starting sign. Matches a line that
starts with string. For example, regular expression "^user" matches
a line beginning with "user", not "Auser".
string$ Ending sign. Matches a line that
ends with string. For example, regular expression "user$" only
matches a line ending with "user", not "userA".
11
Character Meaning Remarks
. Matches any single character, such
as a single character, a special
character, and a blank. For example, ".s" matches both "as" and "bs".
* Matches the preceding character or
character group zero or multiple
times.
For example, "zo*" matches "z" and "zoo"; "(zo)*"
matches "zo" and "zozo".
+ Matches the preceding character or
character group one or multiple
times
For example, "zo+" matches "zo" and "zoo", but
not "z".
| Matches the preceding or
succeeding character string For example, "def|int" only matches a character
string containing "def" or "int".
_
If it is at the beginning or the end of
a regular expression, it equals ^ or
$. In other cases, it equals comma,
space, round bracket, or curly
bracket.
For example, "a_b" matches "a b" or "a(b"; "_ab"
only matches a line starting with "ab"; "ab_" only
matches a line ending with "ab".
-
It connects two values (the smaller
one before it and the bigger one
after it) to indicate a range together
with [ ].
For example, "1-9" means 1 to 9 (inclusive); "a-h"
means a to h (inclusive).
[ ] Matches a single character
contained within the brackets.
For example, [16A] matches a string containing
any character among 1, 6, and A; [1-36A] matches
a string containing any character among 1, 2, 3, 6,
and A (- is a hyphen).
"]" can be matched as a common character only
when it is put at the beginning of characters within
the brackets, for example [ ]string]. There is no
such limit on "[".
( ) A character group. It is usually used
with "+" or "*".
For example, (123A) means a character group
"123A"; "408(12)+" matches 40812 or 408121212.
But it does not match 408.
\index
Repeats the character string
specified by the index. A character
string refers to the string within ()
before \. index refers to the
sequence number (starting from 1
from left to right) of the character
group before \. If only one character
group appears before \, index can
only be 1; if n character groups
appear before index, index can be
any integer from 1 to n.
For example, (string)\1 repeats string, and a
matching string must contain stringstring.
(string1)(string2)\2 repeats string2, and a
matching string must contain
string1string2string2. (string1)(string2)\1\2
repeats string1 and string2 respectively, and a
matching string must contain
string1string2string1string2.
[^] Matches a single character not
contained within the brackets.
For example, [^16A] means to match a string
containing any character except 1, 6 or A, and the
matching string can also contain 1, 6 or A, but
cannot contain only these three characters. For
example, [^16A] matches "abc" and "m16", but not
1, 16, or 16A.
\<string Matches a character string starting
with string. For example, "\<do" matches word "domain" and
string "doa".
string\> Matches a character string ending
with string. For example, "do\>" matches word "undo" and
string "abcdo".
12
Character Meaning Remarks
\bcharacter2
Matches character1character2.
character1 can be any character
except number, letter or underline,
and \b equals [^A-Za-z0-9_].
For example, "\ba" matches "-a" with "-" being
character1, and "a" being character2, but it does
not match "2a" or "ba".
\Bcharacter Matches a string containing
character, and no space is allowed
before character.
For example, "\Bt" matches "t" in "install", but not
"t" in "big top".
character1\w
Matches character1character2.
character2 must be a number,
letter, or underline, and \wequals
[A-Za-z0-9_].
For example, "v\w" matches "vlan" ("v" is
character1 and "l" is character2)and "service" ( "i"
is character2).
\W Equals \b. For example, "\Wa" matches "-a", with "-" being
character1, and "a" being character2, but does not
match "2a" or "ba".
\
Escape character. If a special
character listed in this table follows
\, the specific meaning of the
character is removed.
For example, "\\" matches a string containing "\",
"\^" matches a string containing "^", and "\\b"
matches a string containing "\b".
The following are several regular expression examples:
# Use |begin user-interface in the display current-configuration command to match the first line
of output that contains user-interface to the last line of output.
<Sysname> display current-configuration | begin user-interface
user-interface aux 0
user-interface vty 0 15
authentication-mode none
user privilege level 3
#
return
# Use | exclude Direct in 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
Routing Tables: Public
Destination/Mask Proto Pre Cost NextHop Interface
1.1.1.0/24 Static 60 0 192.168.0.0 Vlan1
# Use | include Vlan in the display ip routing-table command to filter in route entries that contain
Vlan.
<Sysname> display ip routing-table | include Vlan
Routing Tables: Public
Destination/Mask Proto Pre Cost NextHop Interface
192.168.1.0/24 Direct 0 0 192.168.1.42 Vlan999
13
Configuring user privilege and command levels
To avoid unauthorized access, the device defines the user privilege levels and command levels
in Table 7. User privilege levels correspond to command levels.A user who has been logged in with
a specific privilege level can use only the commands at that level or lower levels.
All commands are categorized into four levels: visit, monitor, system, and manage, and are identified
from low to high, respectively by 0 through 3.
Table 7 Command levels and user privilege levels
Lev
el Privileg
e Default set of commands
0 Visit
Includes commands for network diagnosis and commands for accessing an external
device. Configuration of commands at this level cannot survive a device restart. Upon
device restart, the commands at this level are restored to the default settings.
Commands at this level include ping, tracert, telnet and ssh2.
1 Monitor
Includes commands for system maintenance and service fault diagnosis. Commands
at this level are not saved after being configured. After the device is restarted, the
commands at this level are restored to the default settings.
Commands at this level include debugging, terminal, refresh, and send.
2 System
Includes service configuration commands, including routing configuration commands
and commands for configuring services at different network levels.
By default, commands at this level include all configuration commands except for those
at manage level.
3 Manage
Includes commands that influence the basic operation of the system and commands
for configuring system support modules.
By default, commands at this level involve the configuration commands of file system,
FTP, TFTP, Xmodem download, user management, level setting, and parameter
settings within a system, which are not defined by any protocols or RFCs.
Configuring a user privilege level
If the authentication mode on a user interface is scheme, configure a user privilege level for users
who access the interface by using the AAA module or directly on the user interface. For SSH users
who use public-key authentication, the user privilege level configured directly on the user interface
always takes effect. For other users, the user privilege level configured in the AAA module has
priority over the one configured directly on the user interface.
If the authentication mode on a user interface is none or password, configure the user privilege level
directly on the user interface.
For more information about user login authentication, see "Logging in to the CLI." For more
information aboutAAA and SSH, see Security Configuration Guide.
Configuring a user privilege level for users by using the AAA module
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter user interface view. user-interface { first-num1
[ last-num1 ] | { aux | vty }
first-num2 [ last-num2 ] } N/A
14
Step Command Remarks
3. Specify the scheme
authentication mode. authentication-mode scheme
By default, the authentication
mode for VTY users is password,
and no authentication is needed
for AUX users.
4. Return to system view. quit N/A
5. Configure the authentication
mode for SSH users as
password.For more information, see
Security Configuration Guide.
This task is required only for SSH
users who are required to provide
their usernames and passwords
for authentication.
6. Configure the user privilege
level by using the AAA
module.
•To use local authentication:
a. Use the local-user
command to create a
local user and enter local
user view.
b. Use the level keyword in
the
authorization-attribute
command to configure
the user privilege level.
•To use remote authentication
(RADIUS or HWTACACS):
Configure the user privilege
level on the authentication
server
User either approach.
For local authentication, if you do
not configure the user privilege
level, the user privilege level is 0.
For remote authentication, if you
do not configure the user privilege
level, the user privilege level
depends on the default
configuration of the authentication
server.
For more information about the
local-user and
authorization-attribute
commands, see Security
Command Reference.
For example:
# Configure the device to use local authentication for Telnet users on VTY 1 and set the user
privilege level to 3.
<Sysname> system-view
[Sysname] user-interface vty 1
[Sysname-ui-vty1] authentication-mode scheme
[Sysname-ui-vty1] quit
[Sysname] local-user test
[Sysname-luser-test] password simple 123
[Sysname-luser-test] service-type telnet
When users Telnet to the device through VTY 1, they must enter username test and password
12345678. After passing the authentication, the users can only use level-0 commands of level 0.
# Assign commands of levels 0 through 3 to the users.
[Sysname-luser-test] authorization-attribute level 3
Configuring the user privilege level directly on a user interface
To configure the user privilege level directly on a user interface that uses the scheme authentication
mode:
Step Command Remarks
1. Configure the authentication
type for SSH users as
publickey. For more information, see
Security Configuration Guide. Required only for SSH users who
use public-key authentication.
2. Enter system view. system-view N/A
Other manuals for 3100 v2 Series
1
Table of contents
Other HP Switch manuals
HP
HP FlexFabric 11908-V User manual
HP
HP 6125G Installation manual
HP
HP USB-C Travel Dock User manual
HP
HP ProCurve 6600-24G-4XG Assembly instructions
HP
HP 6125G User manual
HP
HP 5920 User manual
HP
HP 6125G User manual
HP
HP StorageWorks 9100 - Extreme Data Storage... User manual
HP
HP 6125G Installation manual
HP
HP ProCurve J4862A User manual
HP
HP ProCurve 5406zl User manual
HP
HP A5830 Series User manual
HP
HP StorageWorks 2/64 - Core Switch User manual
HP
HP ProCurve Series 2600 User manual
HP
HP HP 5120 series User manual
HP
HP Compaq Presario,Presario 1910 User manual
HP
HP HP 2530 Configuration guide
HP
HP PROCURVE 2910AL User manual
HP
HP FlexFabric 7900 Series Installation manual
HP
HP 2920 Series User manual
Popular Switch manuals by other brands
VXI
VXI TuffSet CT Switch System brochure
UTEPO
UTEPO UTP3-SW08-FP120 user manual
Grasslin
Grasslin talento 892 plus operating manual
Bühler technologies
Bühler technologies Nivotemp NT 61 Brief instructions
Cisco
Cisco 3750-24FS - Catalyst Switch - Stackable Specifications
Ubiquiti
Ubiquiti USW-24 quick start guide
United Electric Controls
United Electric Controls J120 Installation and maintenance instructions
GE
GE Zenith ZTS Series quick start guide
Huawei
Huawei S9700 Series Configuration guide
Elwa
Elwa ENS 2230 manual
TRENDnet
TRENDnet TK-205K - PS/2 KVM Switch Quick installation guide
Panasonic
Panasonic ZEQUO 2310 installation guide
