Table of Contents
Advertisement
RUGGEDCOM ROX II
CLI User Guide
Section 3.9.5
Configuring Secure Remote Syslog
Secure remote syslog encrypts all system logs sent to syslog servers using an Secure Sockets Layer (SSL)
certificate signed by a Certified Authority (CA).
IMPORTANT!
The client (RUGGEDCOM ROX II) and server certificates must by signed by the same CA.
The following sections describe how to enable and configure secure remote syslog:
•
Section 3.9.5.1, "Enabling/Disabling Secure Remote Syslog"
•
Section 3.9.5.2, "Viewing a List of Permitted Peers"
•
Section 3.9.5.3, "Adding a Permitted Peer"
•
Section 3.9.5.4, "Deleting a Permitted Peer"
Section 3.9.5.1
Enabling/Disabling Secure Remote Syslog
To configure a specific source IP address for all remote syslog messages, do the following:
1.
Make sure the CLI is in Configuration mode.
NOTE
Once secure remote system logging is enabled and a remote syslog server is configured, TCP
port 6514 is automatically opened.
2.
Enable or disable secure remote syslog by typing either:
Enabling
admin logging secure-remote-syslog enable
Disabling
no admin logging secure-remote-syslog enable
IMPORTANT!
All certificates must meet the following requirements:
• X.509 v3 digital certificate format
• PEM format
• RSA key pair, 512 to 2048 bits in length
3.
If secure remote syslog is enabled, specify a certificate to use for authentication with remote syslog server by
typing:
certificate certificate
Where:
• certificate is the name of the certificate
If the desired certificate is not listed, add it. For more information, refer to
Certificate".
Configuring Secure Remote Syslog
Device Management
Section 4.7.4.3, "Adding a
Chapter 3
65
Advertisement
Table of Contents
Troubleshooting
