[Xymon] Xymon PowerShell Windows client

[Brandon Dale]

Hi Zak,

I want to be able to see the network traffic in/out on each NIC on my windows machines running the new PowerShell client, I have never really looked into how this worked in bbwin but if I look at a few example machines I see the following:


1.       On a Linux machine I get Network Traffic and TCP/IP Statics graphs on the trends page

a.       Raw data contains [ifstat] and [netstat] information



2.       On a windows machine running BBWin 0.13 I only get a TCP/IP Statics graph on the trends page

a.       [ifstat] is blank

b.      [netstat] contains data e.g


[netstat]

ipPacketsReceived=53513930
ipReceivedHeaderErrors=0
ipReceivedAddressErrors=355513
ipDatagramsForwarded=0
ipUnknownProtocolsReceived=2158
ipReceivedPacketsDiscarded=1266110
ipReceivedPacketsDelivered=52167159
ipOutputRequests=31961136
ipRoutingDiscards=0
ipDiscardedOutputPackets=5221
ipOutputPacketNoRoute=0
ipReassemblyRequired=730696
ipReassemblySuccessful=199056
ipReassemblyFailures=0
ipDatagramsSuccessfullyFragmented=0
ipDatagramsFailingFragmentation=0
ipFragmentsCreated=0

ipv6PacketsReceived=7895
ipv6ReceivedHeaderErrors=0
ipv6ReceivedAddressErrors=0
ipv6DatagramsForwarded=0
ipv6UnknownProtocolsReceived=0
ipv6ReceivedPacketsDiscarded=5199
ipv6ReceivedPacketsDelivered=7908
ipv6OutputRequests=2596918
ipv6RoutingDiscards=0
ipv6DiscardedOutputPackets=0
ipv6OutputPacketNoRoute=2
ipv6ReassemblyRequired=0
ipv6ReassemblySuccessful=0
ipv6ReassemblyFailures=0
ipv6DatagramsSuccessfullyFragmented=0
ipv6DatagramsFailingFragmentation=0
ipv6FragmentsCreated=0




3.       On a windows machine running PowerShell client v1.98 I don't get any network related graphs however I seem to have data available:

a.       [ifstat] contains data e.g


[ifstat]

fe80::25a5:b99d:55cd:951f%12 2655878237 519887923

10.250.100.163 2655878237 519887923



a.       [netstat] contains data e.g



[netstat]

PacketsReceived=3387463

ReceivedHeaderErrors=0

ReceivedAddressErrors=51034

DatagramsForwarded=0

UnknownProtocolsReceived=0

ReceivedPacketsDiscarded=146872

ReceivedPacketsDelivered=3219450

OutputRequests=950747

RoutingDiscards=0

DiscardedOutputPackets=102

OutputPacketNoRoute=0

ReassemblyRequired=83643

ReassemblySuccessful=27881

ReassemblyFailures=0

DatagramsSuccessfullyFragmented=0

DatagramsFailingFragmentation=0

FragmentsCreated=0

PacketsReceived=1266

ReceivedHeaderErrors=0

ReceivedAddressErrors=0

DatagramsForwarded=0

UnknownProtocolsReceived=0

ReceivedPacketsDiscarded=618

ReceivedPacketsDelivered=1264

OutputRequests=11680

RoutingDiscards=0

DiscardedOutputPackets=0

OutputPacketNoRoute=2

ReassemblyRequired=0

ReassemblySuccessful=0

ReassemblyFailures=0

DatagramsSuccessfullyFragmented=0

DatagramsFailingFragmentation=0

FragmentsCreated=0


The netstat data in the PowerShell client doesn't seem to have the ip / ipv6 infront of the values so they are listed twice in the example above. So I'm not sure what graphs should I be expecting to get under trends with the PowerShell client for network traffic?

At the moment I'm guessing the ifstat data isn't in a format xymon will automatically graph and add to the trends page and the same for the netstat data possibly just because it has duplicate values for ipv4 and ipv6.

Regards,


Brandon

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of zak.beck at accenture.com
Sent: Friday, 13 February 2015 8:53 PM
To: xymon-developer at lists.sourceforge.net; xymon at xymon.com
Subject: [Xymon] Xymon Powershell Windows client

Hi all,

Today I have uploaded a new version of the Xymon Powershell client to SVN (in sandbox/WinPSClient). We (Accenture) are very pleased to be contributing these changes to the open source community. I've been working on this now for around 8 months on and off and hopefully the changes made will be of benefit to everyone!

Whilst making changes, we have focussed mainly on making it work, improving reliability and most importantly improving performance.

In most cases, on our 64 bit OS virtual machines, a data collection now takes around 5 seconds. On heavily loaded (CPU load or event log load) servers, the script is now considerably faster than originally. Key to this has been reducing the amount of WMI usage as this was a major culprit.

We have also implemented some new features, largely based on our in-house requirements but hopefully useful to others:

*         Showing the process owner and command line in [procs]. This has been implemented using c# code, compiled at runtime.
*         Adding Active Directory replication test, Terminal Services sessions test
*         Ability to restart any stopped Windows service
*         Client self-update
*         Dirsize and dirtime checks (which were originally external scripts)

Some things have changed slightly; for example, the local configuration which was registry-based is now XML-based (you can still use registry settings if you prefer).  In the SVN repository I have also uploaded a Word document which describes how to install and the configuration options.

I have uploaded all the revisions we have made to SVN so there is a history of development. Whilst we will endeavour to continue contributing changes and improvements in coming months, this is an open source project and as such we are not offering any formal support. If anyone wishes to bugfix, branch or whatever, please do so!
Zak Beck
Accenture
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20150304/6f46eb32/attachment.html>