Chapter 4: System Logging
2.
Transfer
logs.tgz
from the appliance to a client using
scp
/
pscp
(see
).
>
scp admin@
<applianceIP>
:logs.tgz .
3.
If you have configured NTP, transfer the
ntp.log
file from the appliance to a client.
>
scp admin@
<applianceIP>
:ntp.log .
Deleting System Logs
Once you have exported the log files to a client, you can clear the appliance's syslog directory. This process
creates an archive of all the stored logs before deleting the original files.
CAUTION!
Ensure that you have retrieved a copy of
ntp.log
before you run
syslog
cleanup
. It is not archived with the rest of the logs.
To delete the stored system logs:
Use
syslog cleanup
(see
).
lunash:>
syslog cleanup
lunash:>syslog cleanup
WARNING !!
This command creates an archive of the current logs then deletes ALL THE LOG FILES.
If you are sure that you wish to proceed, then type 'proceed', otherwise type 'quit'.
> proceed
Proceeding...
Creating tarlogs then deleting all log files...
The tar file containing logs is now available via scp as filename "logs_cleanup_20170301_
1443.tgz".
Please copy "logs_cleanup_20170301_1443.tgz" to a client machine with scp.
Deleting log files ...
restart the rsyslogd service if it's running
Stopping syslog:
[ OK
]
Starting syslog:
[ OK
]
Command Result : 0 (Success)
Remote System Logging
Remote system logging allows you to send logs from your SafeNet Luna Network HSM to a central syslog
server on the network.
You can use the LunaSH
syslog remotehost
commands to specify the central syslog server (see
).
>
"Configuring a Remote Syslog Server" on the next page
>
"Customizing Remote Logging Severity Levels" on page 53
SafeNet Luna Network HSM 7.3 Appliance Administration Guide
007-013576-005 Rev. A 13 December 2019 Copyright 2001-2019 Thales
51