1-6
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 1 Overview
Troubleshooting with Logs
Logging server: enabled
{192.0.2.1}
server severity: notifications
server facility: local1
Step 2
Configure the syslog server.
a.
Modify /etc/syslog.conf to handle local1 messages. For Solaris, t at least one tab needs to be
between the facility.severity and the action (/var/adm/nxos_logs).
#Below is for the NX-OS logging
local1.notice /var/adm/nxos_logs
b.
Create the log file.
#
touch /var/adm/nxos_logs
c.
Restart the syslog.
#
/etc/init.d/syslog stop
#
/etc/init.d/syslog start
syslog service starting.
d.
Verify that the syslog has started.
#
ps -ef |grep syslogd
root 23508 1 0 11:01:41 ? 0:00 /usr/sbin/syslogd
Step 3
Test the syslog server by creating an event in the Cisco Nexus 1000V. In this case, port e1/2 was 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/nxos_logs
Sep 17 11:07:41 [172.22.36.142.2.2] : 2004 Sep 17 11:17:29 pacific:
%PORT-5-IF_DOWN_INITIALIZING: %$VLAN 1%$ Interface e 1/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:
%$VLAN 1%$ Interface e 1/2 is up in mode access
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)
Troubleshooting with Logs
The Cisco Nexus 1000V generates many types of system messages on the switch and sends them to a
syslog server. These messages can be viewed to determine what events might have led up to the current
problem condition that you are facing.
Viewing Logs
Use the following commands to access and view logs in the Cisco Nexus 1000V.
switch#
show logging ?
console Show console logging configuration
info Show logging configuration
internal syslog syslog internal information
last Show last few lines of logfile
level Show facility logging configuration
logfile Show contents of logfile