HP ProCurve 6120G/XG, Руководство по настройке

Страница: 536 / 662

Troubleshooting
Unusual Network Activity
Switch does not detect a client’s public key that does appear in the
switch’s public key file (
show ip client-public-key ). The client’s public key
entry in the public key file may be preceded by another entry that does not
terminate with a new line (CR). In this case, the switch interprets the next
sequential key entry as simply a comment attached to the preceding key entry.
Where a public key file has more than one entry, ensure that all entries
terminate with a new line (CR). While this is optional for the last entry in the
file, not adding a new line to the last entry creates an error potential if you
either add another key to the file at a later time or change the order of the keys
in the file.
An attempt to copy a client public-key file into the switch has failed
and the switch lists one of the following messages.
Download failed: overlength key in key file.
Download failed: too many keys in key file.
Download failed: one or more keys is not a valid RSA
public key.
The public key file you are trying to download has one of the following
problems:
■ A key in the file is too long. The maximum key length is 1024 characters,
including spaces. This could also mean that two or more keys are merged
together instead of being separated by a <CR><LF>.
■ There are more than ten public keys in the key file.
■
One or more keys in the file is corrupted or is not a valid rsa public key.
Client ceases to respond (“hangs”) during connection phase.
The
switch does not support data compression in an SSH session. Clients will often
have compression turned on by default, but will disable it during the negotia­
tion phase. A client which does not recognize the compression-request
FAILURE response may fail when attempting to connect. Ensure that
compression is turned off before attempting a connection to prevent this
problem.
C-18