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

Report Writer problem

I've setup a report that I would like to show all the discards over a period time.

Fields I have selected are

Node name
IP address
Interface Name
Recieve Discards - Sum
Transmit Discards - Sum

I have filtered the results based on

Date is greater than
Receive discards greater than 0
Transmit discards greater than 0

When I run the report it only shows one subnet when I know full well our other subnets have interfaces with discards, graphs show this other subnets with discards. Eventually I want to filter it based on IP address but to start I wanted an overall picture.

Have I missed anything in the config of the report, as far as I can see there are no IP restrictions within the report.

Any help would be much appreciated

Thanks

Jon

IT Infrastructure Manager
Pilgrim Hospital
UK

Find more posts tagged with

Accepted answers

All comments

Network_Guru

Hi Jon,

I tried to create a similar report where one of the filters was being used in a similar format as yours. I wanted it to show only nodes with less than 100% uptime for the previous week. I ran into the same sort of thing as this. I mentioned it to Solarwinds support, and I was told this is an advanced SQL query which requires a "mutually exclusive" (or something to that effect) in order to display the results correctly.
I am not an SQL guru, so I was never able to get this to work, although it sounds quite straight forward to do, and would be a much better report than including the nodes with no errors or in my case 100% uptime.

Any DBA's out there?

-=Cheers=-
NG

iunderwo

quote:Originally posted by jonchill

I've setup a report that I would like to show all the discards over a period time.

Fields I have selected are

Node name
IP address
Interface Name
Recieve Discards - Sum
Transmit Discards - Sum

I have filtered the results based on

Date is greater than
Receive discards greater than 0
Transmit discards greater than 0

What do you see when you toggle the receive and transmit discard filtering action? This should work properly because this query only selects interface information where there are any recorded discards. Also be sure that it's a historic error report.

I run a similar query which yields the following SQL:

//SQL Start
SELECT Nodes.Caption AS NodeName,
Interfaces.IfName AS Internal_Interface_Name,
SUM(InterfaceErrors.In_Discards) AS SUM_of_Receive_Discards,
SUM(InterfaceErrors.Out_Discards) AS SUM_of_Transmit_Discards,
Interfaces.AdminStatus AS AdminStatus

FROM
(Nodes INNER JOIN Interfaces ON (Nodes.NodeID = Interfaces.NodeID)) INNER JOIN InterfaceErrors ON (Interfaces.InterfaceID = InterfaceErrors.InterfaceID)

WHERE
( DateTime BETWEEN 38188 AND 38189 )
AND
(
(Nodes.Caption LIKE 'DSL::%') AND
(
(InterfaceErrors.In_Discards > 25) OR
(InterfaceErrors.Out_Discards > 25)) AND
(Interfaces.AdminStatus = 1)
)

GROUP BY Nodes.Caption, Interfaces.IfName, Interfaces.AdminStatus

ORDER BY 1 ASC
//SQL Stop

By looking at the query, I should only be selecting any errored intervals which have more than 25 discards on either Xmit or Recv.

In your filter, you should have it setup like this:

* Where ALL conditions apply
*-- Date is greater than
*-- Where ANY conditions apply
*---- Recv discards > 0
*---- Xmit discards > 0

The likelihood of having both transmit and recive discards in a given interval on a given interface is not impossible, but quite unlikely.

If you're using a time frame, then you only need to ensure the last 3 lines of the example are in the filter:

* Where ANY conditions apply
*-- Recv discards > 0
*-- Xmit discards > 0

And, set the time filter accordingly. It should work then.

// Ian Underwood - Service Management
// Level 3 Communications