HP 6125G HP 6125G & 6125G/XG Blade Switches Fundamentals Configuration - Page 19

Configuring user privilege and command levels, Configuring a user privilege level

Page 19 highlights

# Use | include Vlan in the display ip routing-table command to filter in route entries that contain Vlan. 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 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 Level Privilege 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. 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 1 Monitor at this level are restored to the default settings. Commands at this level include debugging, terminal, refresh, and send. Includes service configuration commands, including routing configuration commands and commands for configuring services at different network levels. 2 System By default, commands at this level include all configuration commands except for those at manage level. Includes commands that influence the basic operation of the system and commands for configuring system support modules. 3 Manage 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. 13

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135

13
# 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
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
Level
Privilege
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.