Some important information about the vrosyslog can be logged on the UNIX host of the internal network through the syslog mechanism. The log function can be implemented by setting the IP address of the log host on the vro and making necessary settings on the corresponding UNIX host.
When the vro。 is running, the vro sends logs to the log host. Logs include information packages for Link creation failure to filter log information. By logging on to the log host, the system administrator can learn about log events and analyze logs. Logs can help administrators locate and troubleshoot faults, and help administrators manage network security.
1. configuration on the vro
Table 3-19 set the log host
Show loghost
No loghost cancels the log host'
Loghost-ip-address
For example, the router sends log information to a UNIX workstation whose IP address is 202.38.160.1.
Quidway (config) # loghost 202.38.160.1
2. configuration on a UNIX host
The following configuration example shows that the configuration operations on UNIX operating systems of other vendors are basically the same on SunOS 4.0.
Step 1: run the following command as the root user
# Mkdir/var/log/Quidway
# Touch/var/log/Quidway/config
# Touch/var/log/Quidway/securityR | w :/
Step 2. edit the file/etc/syslog. conf as the root user and add the following options/action combinations (selector/action pairs ). % X
# Quidway configuration messages/
Local4.crit/var/log/Quidway/config
# Quidway security messages
Local5.notice/var/log/Quidway/security
Note the following issues when editing/etc/syslog. conf:
! The comment can only contain independent lines and start with a character.
! The selection/Action combination must be separated by a tab and cannot be entered with spaces.
! No extra space is allowed after the file name.
Step 3: When the log file config and security are created and/etc/syslog. after the conf file is modified, run the following command to send the system daemon syslogd an HUP signal to make syslogd re-read its configuration file/etc/syslog. conf.
# Ps-AE | grep syslogd
147©
# Kill-HUP 147
After performing the preceding operations, the router can record the information in the corresponding log file.