1-17
Step 2: Create a subdirectory named
Device
under directory
/var/log/
, and create file
info.log
under
the
Device
directory to save logs of
Device
.
# mkdir /var/log/Device
# touch /var/log/Device/info.log
Step 3: Edit file
/etc/syslog.conf
and add the following contents.
# Device configuration messages
local4.info /var/log/Device/info.log
In the above configuration,
local4
is the name of the logging facility used by the log host to receive logs.
info
is the information level. The Unix system will record the log information with severity level equal to
or higher than
informational
to file
/var/log/Device/info.log
.
Be aware of the following issues while editing file
/etc/syslog.conf
:
z
Comments must be on a separate line and begin with the # sign.
z
No redundant spaces are allowed after the file name.
z
The logging facility name and the information level specified in the
/etc/syslog.conf
file must be
identical to those configured on the device using the
info
-
center loghost
and
info-center source
commands; otherwise the log information may not be output properly to the log host.
Step 4: After log file
info.log
is created and file
/etc/syslog.conf
is modified, you need to issue the
following commands to display the process ID of
syslogd
, kill the
syslogd
process and then restart
syslogd
using the
–r
option to make the modified configuration take effect.
# ps -ae | grep syslogd
147
# kill -HUP 147
# syslogd -r &
After the above configurations, the system will be able to record log information into the log file.
Outputting Log Information to a Linux Log Host
Network requirements
z
Send log information to a Linux log host with an IP address of 1.2.0.1/16;
z
Log information with severity higher than informational will be output to the log host;
z
All modules can output log information.
Figure 1-3
Network diagram for outputting log information to a Linux log host
Configuration procedure
Before the configuration, make sure that there is a route between Device and PC.
Summary of Contents for S7902E
Page 82: ...1 4 DeviceA interface tunnel 1 DeviceA Tunnel1 service loopback group 1 ...
Page 200: ...1 11 DeviceB display vlan dynamic No dynamic vlans exist ...
Page 598: ...ii ...
Page 1757: ...4 9 ...
Page 1770: ...6 4 ...
Page 2017: ...2 11 Figure 2 3 SFTP client interface ...
Page 2238: ...1 16 DeviceA cfd linktrace service instance 1 mep 1001 target mep 4002 ...