Information Technology Reference
In-Depth Information
Table24-5 Troubleshooting Suggestions (continued)
Error Message
Possible Reasons
Actions
Syslog Analyzer:
logging is enabled
in the
IOS/Catalyst
device to send
messages to
Essentials but is
not working.
Syslog Analyzer:
logging is enabled
in the
IOS/Catalyst
device to send
messages to
Essentials but is
not working.
Messages sent to
the Essentials
server by network
devices are logged
by a process
independent of the
Syslog Analyzer.
For Solaris, the
logging process is
syslogd. For
Windows NT, it is
the Essentials
syslog service.
The problem may
be that the syslog
daemons are not
running properly.
Connect to the network device and generate
a syslog message as follows:
1.
Telnet to the device and log in. The
prompt changes to host>.
2.
Type
enale
and the enable password.
The prompt changes to host#.
3.
Type
configure terminal
. You are now
in configuration mode, and the prompt
changes to host (config)#.
4.
Ensure that logging is enabled by
entering
logging on
.
5.
Specify the IP address of the Essential
server to receive the router syslog
messages; for example, type
logging
123.45.255.90
.
6.
Type
end
.
For Solaris, view the file pointed to by the
line “local7.info” in the file
/etc/syslog.conf (default
/var/log/syslog_info). If this file does not
exist, create one, and make sure that it is
accessible by syslogd.
For Windows NT, view the file in
C:\Program Files \CSCOpx\log\syslog.log
Send an HUP signal to syslogd (
kill -HUP
`cat
/etc/syslog.pid`
).
Syslog Analyzer:
logging is enabled
in the
IOS/Catalyst
device to send
messages to
Essentials but is
not working.
Syslog Analyzer:
logging is enabled
in the
IOS/Catalyst
device to send
messages to
Essentials but is
not working.
(continued)
If the syslog message is not there, check
that the syslog daemons are running
properly.
For Solaris, type
/usr/ucb/ps -aux | grep
syslogd
.
For Windows NT, go to Control Panel and
ensure that Essentials syslog service is in
“Started” state.
