TRENDnet TL2-FG142, Руководство пользователя

Страница: 24 / 134

© Copyright 2019 TRENDnet. All Rights Reserved.
TRENDnet User’s Guide
TL2-FG142
19
them contains more than one. The following description defines these
privilege level groups in details:
System: Contact, Name, Location, Timezone, Daylight Saving Time, Log.
Security: Authentication, System Access Management, Port (contains
Dot1x port, MAC based and the MAC Address Limit), ACL, HTTPS, SSH, ARP
Inspection, IP source guard.
IP: Everything except 'ping'.
Port: Everything except 'VeriPHY'.
Diagnostics: 'ping' and 'VeriPHY'.
Maintenance: CLI- System Reboot, System Restore Default, System
Password, Configuration Save, Configuration Load and Firmware Load.
Web- Users, Privilege Levels and everything in Maintenance.
Debug: Only present in CLI.
Privilege
Levels Every group has an authorization Privilege level for the following sub
groups: configuration read-only, configuration/execute read-write,
status/statistics read-only, status/statistics read-write (e.g. for clearing of
statistics). User Privilege should be same or greater than the authorization
Privilege level to have the access to that group.
Button
Click to save changes.
Click to undo any changes made locally and revert to previously saved values.
4.3.5.3Authentication Method Configuration
This page allows you to configure how a user is authenticated when he logs into the
switch via one of the management client interfaces.
The table has one row for each client type and a number of columns, which are:
Items Description
Client The management client for which the configuration below applies.
Methods Method can be set to one of the following values:
no: Authentication is disabled and login is not possible.
local: Use the local user database on the switch for authentication.
radius: Use remote RADIUS server(s) for authentication.
: Use remote server(s) for authentication.
Methods that involves remote servers are timed out if the remote servers
are offline. In this case the next method is tried. Each method is tried from
left to right and continues until a method either approves or rejects a user.
If a remote server is used for primary authentication it is recommended
to configure secondary authentication as 'local'. This will enable the
management client to login via the local user database if none of the
configured authentication servers are alive.
Button
Click to save changes.
Click to undo any changes made locally and revert to previously saved values.
4.3.5.4SSH Configuration
Configure SSH on this page.