User`s manual

User’s Manual 157
clients that have a private key corresponding to the public keys stored on the switch can gain
access. The following exchanges take place during this process:
• The client sends its public key to the switch.
• The switch compares the client's public key to those stored in memory.
• If a match is found, the switch uses the public key to encrypt a random sequence of bytes, and
sends this string to the client.
• The client uses its private key to decrypt the bytes, and sends the decrypted bytes back to the
switch.
• The switch compares the decrypted bytes to the original bytes it sent. If the two sets match,
this means that the client's private key corresponds to an authorized public key, and the client
is authenticated.
Note: To use SSH with only password authentication, the host public key must still be given to the client,
either during initial connection or manually entered into the known host file. You do not need to configure the
client’s keys.
15.3.6 Event Logging Commands
The following table lists the even logging commands.
Command Function Mode
logging on Controls logging of error messages GC
logging history Limits syslog messages saved to switch memory based on severity GC
logging host Adds a syslog server host IP address that will receive logging
messages
GC
logging facility Sets the facility type for remote logging of syslog messages GC
logging trap Limits syslog messages saved to a remote server based on severity GC
clear logging Clears messages from the logging buffer PE
show logging Displays the state of logging configuration PE
15.3.7 SMTP Alert Commands
Configures SMTP event handling, and forwarding of alert messages to the specified SMTP servers and
email recipients.
Command Function Mode
logging sendmail host SMTP servers to receive alert messages GC
logging sendmail level Severity threshold used to trigger alert messages GC
logging sendmail source-email Email address used for “From” field of alert messages GC