×

Join the Conversation

Without signing in, you're just watching from the sidelines. Sign in or Register to connect, share, and be part of the Splunk Community.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Ask a Question
thaecker
New Member
Member since: ‎10-14-2010
‎06-05-2020
Community Statistics
Posts 2
Solutions 0
Karma Given 0
Karma Received 0
Member Since ‎10-14-2010
View All

Re: host=GMTS instead of hostname when using Cisco...

by in Security
‎10-18-2010 10:42 AM
‎10-18-2010 10:42 AM
I think it is the regex used in Manager >> Fields >> Field transformations >> syslog-host: :\d\d\s+(?:\d+\s+|(?:user|daemon|local.?).\w+\s+)*[?(\w[\w.-]{2,})]?\s Seems like only events related to ciscos "login on-failure log" contain the GMTS string, it happens to all of them. An example event where splunk was able to determine the correct host information is: <189>39428: 0.0.0.0: 039424: Oct 18 12:29:48.547: %SYS-5-CONFIG_I: Configured from console by username on vty0 (10.10.10.11) ... View more

host=GMTS instead of hostname when using Cisco Swi...

by in Security
‎10-14-2010 11:03 AM
‎10-14-2010 11:03 AM
Hi everybody, i configured a Cisco switch with "login on-failure log" to log failed authentications to my splunk server. Unfortunately, these events have host=GMTS in splunk instead of the real hostname (host=switchname). Other events from the same switch do not have this problem. These events look like: <189>38677: switchname: 038673: Oct 14 12:11:02.419: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: username] [Source: 10.10.10.10] [localport: 22] at 12:11:02 GMTS Thu Oct 14 2010 Is there a way to fix this? Many thanks in advance. ... View more
Contact Me
Online Status
Offline
Date Last Visited
‎06-05-2020 02:02 AM