Dell PowerConnect 6224, Command Line Interface Manual

Page: 169 / 1372

Using the CLI
169
• If authentication servers are used, the user can identify at least two remote
servers (the user may choose to configure only one server) and what
protocol to use with the server, or Radius. One of the servers is
primary and the other is the secondary server (the user is not required to
specify a secondary server). If the primary server fails to respond in a
configurable time period, the CLI automatically attempts to authenticate
the user with the secondary server.
• The user is able to specify what happens when both primary and secondary
servers fail to respond. In this case, the user is able to indicate that the CLI
should either use the local user accounts or reject all requests.
• Even if the user configures the CLI to fail login when the remote
authentication servers are down, the CLI allows the user to log in to the
serial interface authenticated by locally managed account data.
Syslogs
The CLI uses syslog support to send logging messages to a remote syslog
server. The user configures the switch to generate all logging messages to a
remote log server. If no remote log server exists, then the CLI maintains a
rolling log of at most the last 1000 critical system events.
The following rules and specifications apply:
• The CLI permits the user to configure a remote syslog server to which all
system logging messages are sent.
• Log messages are implementation-dependent but may contain debug
messages, security or fault events.
• If a log server is not specified by the user, the CLI maintains at most the
last 1000 critical system events. In this case, less important events are not
recorded.
Security Logs
Security logs are maintained to record all security events including the
following:
• User login.
• User logout.
• Denied login attempts.
• User attempt to exceed security access level.