Implementing Syslog With The Cli - Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual

Mds 9000 family
Hide thumbs Also See for 9134 - MDS Multilayer Fabric Switch:
Table of Contents

Advertisement

System Messages
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
You should avoid using PCs that have IP addresses randomly assigned to them by DHCP. The switch
Note
continues to use the old IP address unless you manually change it; however the Device Manager prompts
you if it does detect this situation. UNIX workstations have a built-in syslog server. You must have root
access (or run the Cisco syslog server as setuid to root) to stop the built-in syslog daemon and start the
Cisco syslog server.

Implementing Syslog with the CLI

To configure a syslog server using the CLI, follow these steps:
Configure the Cisco MDS switch:
Step 1
switch1# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
switch1(config)# logging server 172.22.36.211 6 facility local1
To display the configuration:
switch1# show logging server
Logging server: enabled
{172.22.36.211}
Step 2
Configure the syslog server:
Test the syslog server by creating an event on the Cisco MDS switch . In this case, port fc1/2 was
Step 3
bounced and the following was listed on the syslog server. Notice that the IP address of the switch is
listed in brackets.
# tail -f /var/adm/MDS_logs
Sep 17 11:07:41 [172.22.36.142.2.2] : 2004 Sep 17 11:17:29 pacific:
%PORT-5-IF_DOWN_INITIALIZING: %$VSAN 1%$ Interface fc1/2 is down (Initializing)
Sep 17 11:07:49 [172.22.36.142.2.2] : 2004 Sep 17 11:17:36 pacific: %PORT-5-IF_UP:
%$VSAN 1%$ Interface fc1/2 is up in mode TE
Sep 17 11:07:51 [172.22.36.142.2.2] : 2004 Sep 17 11:17:39 pacific:
%VSHD-5-VSHD_SYSLOG_CONFIG_I: Configuring console from pts/0
(dhcp-171-71-49-125.cisco.com)
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
1-12
server severity: notifications
server facility: local1
a.
Modify /etc/syslog.conf to handle local1 messages. For Solaris, there needs to be at least one
tab between the facility.severity and the action (/var/adm/MDS_logs).
#Below is for the MDS 9000 logging
local1.notice /var/adm/MDS_logs
Create the log file.
b.
#touch /var/adm/MDS_logs
Restart syslog.
c.
# /etc/init.d/syslog stop
# /etc/init.d/syslog start
syslog service starting.
Verify syslog started.
d.
# ps -ef |grep syslogd
root 23508 1 0 11:01:41 ? 0:00 /usr/sbin/syslogd
Chapter 1
Troubleshooting Overview
OL-9285-05

Hide quick links:

Advertisement

Table of Contents

Troubleshooting

loading

Table of Contents