Splunk Search

Port flapping MAC search

sSiDs
New Member

Hi team!

Couldn't find any info about it....but how make a proper search string to see what MAC address was on flapping port if port is down now

 

 

Time	Event
6/8/21
10:19:25.000 AM	
Jun  8 10:19:25 192.168.200.55 2011: Jun  8 10:20:53.436: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/31, changed state to down
host = 192.168.200.55source = udp:514sourcetype = cisco:ios
6/8/21
10:19:24.000 AM	
Jun  8 10:19:24 192.168.200.55 2010: Jun  8 10:20:52.429: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/31, changed state to down
host = 192.168.200.55source = udp:514sourcetype = cisco:ios
6/7/21
7:46:20.000 PM	
Jun  7 19:46:20 192.168.200.55 2008: Jun  7 19:47:47.892: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/31, changed state to up
host = 192.168.200.55source = udp:514sourcetype = cisco:ios
6/7/21
7:46:20.000 PM	
Jun  7 19:46:20 192.168.200.55 2007: Jun  7 19:47:46.892: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/31, changed state to up
host = 192.168.200.55source = udp:514sourcetype = cisco:ios
6/7/21
7:46:17.000 PM	
Jun  7 19:46:17 192.168.200.55 2004: Jun  7 19:47:43.858: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/31, changed state to down
host = 192.168.200.55source = udp:514sourcetype = cisco:ios
6/7/21
7:46:15.000 PM	
Jun  7 19:46:15 192.168.200.55 2003: Jun  7 19:47:42.862: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/31, changed state to down
host = 192.168.200.55source = udp:514sourcetype = cisco:ios
6/7/21
7:46:13.000 PM	
Jun  7 19:46:13 192.168.200.55 2001: Jun  7 19:47:41.411: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/31, changed state to up
host = 192.168.200.55source = udp:514sourcetype = cisco:ios
6/7/21
7:46:13.000 PM	
Jun  7 19:46:13 192.168.200.55 2000: Jun  7 19:47:40.408: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/31, changed state to up
host = 192.168.200.55source = udp:514sourcetype = cisco:ios
6/7/21
7:46:10.000 PM	
Jun  7 19:46:10 192.168.200.55 1997: Jun  7 19:47:37.458: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/31, changed state to down
host = 192.168.200.55source = udp:514sourcetype = cisco:ios
6/7/21
7:46:09.000 PM	
Jun  7 19:46:09 192.168.200.55 1996: Jun  7 19:47:36.452: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/31, changed state to down
host = 192.168.200.55source = udp:514sourcetype = cisco:ios
6/7/21
4:46:12.000 PM	
Jun  7 16:46:12 192.168.200.55 1994: Jun  7 16:47:40.209: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/31, changed state to up
host = 192.168.200.55source = udp:514sourcetype = cisco:ios
6/7/21
4:46:12.000 PM	
Jun  7 16:46:12 192.168.200.55 1993: Jun  7 16:47:39.206: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/31, changed state to up
host = 192.168.200.55source = udp:514sourcetype = cisco:ios

 

 

Labels (1)
0 Karma

venkatasri
SplunkTrust
SplunkTrust

Hi @sSiDs 

You do not have MAC address in events, I am assuming Host as MAC and following query would be help to find flapping port.

 source is your port,  further if you have host to MAC address mapping in a lookup (aka csv) file then that can be enriched using | lookup command.

index=index_name sourcetype=cisco:ios "changed state to down"
| table _time source host

 -------------

An upvote would be appreciated if it helps!

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...