Troubleshooting Guide

Table Of Contents
show syslog host <1–10>
9. (Optional) Remove the server certificate name:
no syslog host <1–10> secure-forwarding mode tls server-cert-name
10. (Optional) Set secure-forwarding mode to none for a particular host:
default syslog host <1–10> secure-forwarding mode
Next steps
After configuring secure forwarding on the switch, set the syslog server to be able to see the log
messages on the interactive syslog viewer.
For SSH secure syslog, on the winsyslog server, enter the host IP or the IP of the PC and set
the port to 601 which is a default port for TCP and set the protocol type to RFC3195.
For TLS secure syslog, on the rsyslog server, configure the server to use TLS method and
install the root certificate on the server in the switch.
Variable definitions
Use the data in the following table to use the syslog host command.
Variable
Value
host <1–10> Specifies the ID for the syslog host. The range is 1–10.
address WORD<0–46> Configures a host location for the syslog host. WORD <0–46> is the IPv4 or
IPv6 address of the UNIX system syslog host in the format A.B.C.D or
x:x:x:x:x:x:x:x. You can log system log messages to external system log hosts
with both IPv4 and IPv6 addresses with no difference in functionality or
configuration using ACLI.
enable Enables the syslog host. Use the no operator before this parameter, no syslog
host enable to disable syslog host. The default is disabled.
secure-forwarding Adds protected syslog using SSH remote port forwarding for host.
Use the data in the following table to use the syslog host secure-forwarding command.
Variable
Value
host <1–10> Creates and configures a host instance. Use the no operator before
this parameter, no syslog host to delete a host instance.
mode [none | ssh | tls server-cert-
name WORD<1-64>]
Specifies the mode of secure forwarding of syslog on the host. The
default mode is none, that is, both ssh and tls modes are disabled
by default.
Note:
Certificate validation is done only if the server-cert-name is
configured.
Table continues…
Configuring secure forwarding
January 2017 Troubleshooting 51
Comments on this document? infodev@avaya.com