Forwarding of system messages can be set up with the “hmc addsyslog” command. In the simplest case, it is sufficient to specify the remote syslog destination:

$ hmc addsyslog hmc03 server01
$

By default UDP is used as the protocol. All messages are forwarded to the remote syslog destination specified. An overview of the configured remote syslog destinations can be obtained using “hmc lssyslog”:

$ hmc lssyslog hmc03
SERVER    TYPE  DISCARD
server01  udp   
$

If the specified hostname (in this case server01) cannot be resolved on the HMC, no forwarding to the destination occurs.

If the TCP protocol is to be used for forwarding instead of UDP, this can be specified when adding the remote syslog destination. To do this, simply specify the desired protocol (udp, tcp or tls) after the server name (or IP address):

$ hmc addsyslog hmc03 server02 tcp
$

A new listing shows that server02 was added with protocol tcp:

$ hmc lssyslog hmc03
SERVER    TYPE  DISCARD
server01  udp   
server02  tcp   
$

Occasionally you don’t want to forward messages that contain a certain character string to a destination. For this purpose, the HMC offers the option of configuring a filter when setting up a forwarding. A filter consists of one or more character strings. Messages that contain one of these character strings are not forwarded to the target system. For example, if messages with the character string “:info” are not to be forwarded to the new destination server03, then the forwarding can be set up as follows:

$ hmc addsyslog hmc03 server03 :info
$

In addition, the protocol to be used can still be specified after the server name!

The filter to use for a remote syslog destination can also be changed later, see: Changing the syslog Filter for a Remote Syslog Destination.