Network Management

NPM Syslog not receiving Syslog messages from specific Cisco device

This article addresses an issue in NPM where the Syslog service is not receiving and collecting messages from specific Cisco devices.

First published date

10/29/2018 8:58 PM

Last published date

6/29/2022 7:57 PM

Overview

The NPM Syslog service is not receiving messages from a specific Cisco device that already has Syslog enabled.

Product section

Network Performance Monitor

Cause

N/A

Resolution

  1. Verify that the SolarWinds Syslog service is the only service on port 514:

    1. Click Start > Run, and then enter cmd.
    2. Enter netstat -aob.

  2. Log in to the Cisco device. (Steps 2 to 6 should be done by the device administrator.)

  3. Make a backup of the configuration by copying the "show run" result from the router.

  4. Log in to privilege mode and check how logging is configured on the router. The following are command options on how to configure the router syslog:

Router(config)#logging host <ip address>
or
Router(config)#logging <server ipaddress>

 

  1. Deactivate the logging first from the Cisco device using the following command:

    Router(config)#no logging <server ipaddress> 
or
Router(config)#no logging host <ip address>

     

  2. Reactive the logging using the following command:

    Router(config)#logging <server ipaddress> 
or
Router(config)#logging host <ip address>

     

  3.  Restart the syslog service on the Orion Service Manager.

  4. Wait for 5 to 10 minutes and verify that the Orion NPM server starts receiving syslog messages from the device.

 

Note: If the issue persists, run a Wireshark analysis to trace the packets or messages from the device going to the NPM server or syslog collector.  

  • "udp.port==514" 
  • "syslog"

This can also be an environmental issue where the NPM server cannot communicate with the device on the required network ports, which is generally caused by blocked communication in the network.