# Disable the output of log, trap, and debugging information of all modules on channel loghost.
[Sysname] info-center source default channel loghost debug state off log state off trap
state off
CAUTION:
Because the default system configurations for different channels are different, you need to first disable the
output of log, trap, and debugging information of all modules on the specified channel (loghost in this
example) first. Then configure the output rule as needed so that unnecessary information will not be
output.
# Configure the information output rule. Allow log information of ARP and IP modules with severity equal
to or more severe than informational to be output to the log host. (The source modules that are allowed
to output information depend on the switch model.)
[Sysname] info-center source arp channel loghost log level informational state on
[Sysname] info-center source ip channel loghost log level informational state on
Configure the log host
2.
The following configurations were performed on SunOS 4.0 which has similar configurations to the UNIX
operating systems implemented by other vendors.
Step 1: Log in to the log host as a root user.
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 more severe than informational to file /var/log/Device/info.log.
NOTE:
Be aware of the following issues while editing file /etc/syslog.conf:
Comments must be on a separate line and begin with the pound sign (#).
•
No redundant spaces are allowed after the file name.
•
•
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.
53
Need help?
Do you have a question about the S3100V2-52TP and is the answer not in the manual?