Use the following commands to verify Layer 2 connectivity:

• Use the show vlan all-ports command to verify that all the necessary interfaces are in the same VLAN. The status should be active for the VLAN.

• Use the show port-channel compatibility-parameters command to verify that all of the ports in a port channel are configured the same for the speed, the duplex, and the trunk mode.

• Use the show running-config spanning-tree command to verify that the Spanning Tree Protocol (STP) is configured the same on all devices in the network.

• Use the show processes | include ER command to verify that nonessential Layer 2 processes are in the error state.

• Use the show mac address-table dynamic vlan command to determine if learning or aging is occurring at each node.

Answer the following questions to verify Layer 3 connectivity:

• Have you configured a default gateway?

• Have you configured the same dynamic routing protocol parameters throughout your routing domain or configured static routes?

• Are any IP access lists, filters, or route maps blocking route updates?

Use the following commands to verify your routing configuration:

• show ip arp

• show {ip | ipv6}

• show ipv6 neighbor

The syslog facility allows the device to send a copy of the message log to a host for more permanent storage. This feature allows you to examine the logs over a long period of time or if the device is not accessible.

This example shows how to configure the device to use the syslog facility on a Solaris platform. Although a Solaris host is being used, the syslog configuration on all UNIX and Linux systems is very similar.

Syslog uses the facility to determine how to handle a message on the syslog server (the Solaris system in this example) and the message severity. Different message severities are handled differently by the syslog server. They could be logged to different files or e-mailed to a particular user. Specifying a severity level on the syslog server determines that all messages of that level and greater severity (lower number) will be acted upon as you configure the syslog server.

Note

You should configure the syslog server so that the Cisco NX-OS messages are logged to a different file from the standard syslog file so that they cannot be confused with other non-Cisco syslog messages. Do not locate the logfile on the / file system. You do not want log messages to fill up the / file system. This example uses the following values: syslog client: switch1 syslog server: 172.22.36.211 (Solaris) syslog facility: local1 syslog severity: notifications (level 5, the default) File to log Cisco NX-OS messages to: /var/adm/nxos_logs

To configure the syslog feature on Cisco NX-OS, follow these steps:

1. switch# config terminal

2. switch(config)# logging server 192.0.2.1 6 facility local1

Use the show logging server command to verify the syslog configuration.

switch1# show logging server
Logging server:                 enabled
{172.22.36.211}
        server severity:        notifications
        server facility:        local1
        server VRF:             management

To configure a syslog server, follow these steps:

1. Modify /etc/syslog.conf to handle local1 messages. For Solaris, you must allow at least one tab between the facility.severity and the action (/var/adm/nxos_logs).

   local1.notice /var/adm/nxos_logs

2. Create the log file.

   touch /var/adm/nxos_logs
   
   

3. Restart the syslog process.

   /etc/init.d/syslog stop 
   /etc/init.d/syslog start
   
   syslog service starting.
   
   

4. Verify that the syslog process has started.

   ps -ef |grep syslogd
   
   

Test the syslog server by creating an event in Cisco NX-OS. In this case, port e1/2 was shut down and reenabled, and the following was listed on the syslog server. The IP address of the device is listed in brackets.

tail -f /var/adm/MDS_logs
Sep 17 11:07:41 [172.22.36.142.2.2] : 2013 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] : 2013 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] : 2013 Sep 17 11:17:39 pacific: %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configuring console from pts/0 (dhcp-171-71-49-125.cisco.com