nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

FEATURE REQUEST - Case # - 00401024

dhiraj92

Feature Request for interface Discards with following information:

Node name, IP address , interface, location.
Count of packet discarded with exact time interval details.
Type (TCP/UDP) of discarded packets.
Source of discarded packets.

Find more posts tagged with

Status: None

Comments

brscott

Not sure there is a way to do either of the last two... At least on ifInDiscards, since they didn't make it far enough up the stack to be in a newflow or packet capture.

On ifOutDiscards it's only theoretically possible, but I don't think anything exposes that information.

It might be a close approximation to use TCP retransmissions to correlate the source of the dropped packets, but it's not a direct packet-for-packet mapping to the dropped packets, just a numbers correlation.

Who knows... these soalrwinds programers are quite amazing. Maybe they could map two netflows on either side of the interface in question and detect the exact dropped packets.

dhiraj92

Thanks for your reply.