Syslogs send by Summit-Switch are not displayed in Netsight Syslog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-27-2017 11:30 AM
I configured a X460 with syslog, as stated in https://extremeportal.force.com/ExtrArticleDetail?an=000074214 - everything works fine, in Netsight Alarms and Events, I can see the syslogs of this device.
Exactly the same configuration doesn't work with X440.
In our firewall system I can see, that syslog traffic is send to NetSight, but they won't appear.
Do I need to configure something in Netsight or where is the problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-15-2017 11:38 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-27-2017 03:27 PM
New messages should be written in the file /var/logs/syslog
If you ssh into EMC you'd do a "tail -f /var/log/syslog" to see new incoming messages.
Do that and and force some syslog message from the X440 and let us know whether you'd see that in the CLI output.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-27-2017 03:27 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-27-2017 03:27 PM
The firewall can see, that syslog traffic is routed to our Netsight, but nothing is shown inside the syslog-file - so neither in the Console/OneView.
This is the switch-configuration:
I connected a device and with the booting, there are logs for netlogin, vlan, etc.
Log Target : syslog; 1.2.3.4:514 (vr VR-Default), local0 Enabled : yes Filter Name : DefaultFilter Match regex : Any Severity : Info (through Critical) Format : PRI Mmm DD HH:MM:SS HOSTNAME TAG: Does anyone has suggestions?
Other switches are working fine with the same config (X440, X460, X670...).
IP connectivity is given, otherwise the firewall wouldn't see passing syslog-packets.
Seems to be an Netsight related issue.