Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - glenns

#1
Hi Guys,

I thought some of you might find this useful, I've been working on a method to get temperature monitoring on our windows machines and this is working really well.

First you'll need to install Open Hardware Monitor on the machine you wish to monitor.
(http://openhardwaremonitor.org/downloads/)
Once installed this will collect temperature, voltage, fan speed etc (depending on your hardware sensors) and make all this information available via WMI  :)

You will need the WMI Subagent in your agent config: SubAgent = wmi.nsm

You will then need to create some DCI's to collect the information, for example:
WMI.Query(root\OpenHardwareMonitor,SELECT * FROM Sensor WHERE Instanceid=3849, Value)



The value of InstanceID can be found using another tool, WMI Explorer. (https://wmie.codeplex.com/)

With WMI Explorer connect to the machine running Open Hardware Monitor, goto the root\OpenHardwareMonitor namespace, select the Sensor class and find the instance value of the Monitor you wish to collect information on.



I have been trying to make some WMI queries that will work from templates.  By using a more complex SQL query to filter the results without having to lookup the InstanceID, I've had some success with the following example.

WMI.Query(root\OpenHardwareMonitor,SELECT * FROM Sensor WHERE Name LIKE "'%CPU%'" AND SensorType="'Temperature'" AND Index=0 , Value)

Hope you find this useful,
#2
Feature Requests / Drivers for TP-Link Switches
May 06, 2015, 12:55:43 PM
Hi Guys, I'm new to this but would love to get my TP Link Switches to work.

I'm currently using a TL-SG2452 and TL-SG3424P but the generic driver will not retrieve the FDB or any other significant information.  If I hunt through the MIB using the explorer I can find the values under these OID's for the TL-SG2452

.1.3.6.1.4.1.11863.1.1.15.2.3.2.2.1.1  -- Mac Addresses
.1.3.6.1.4.1.11863.1.1.15.2.3.2.2.1.3  -- Port Number


I'm happy to provide any information I can to get this working but writing a driver is a beyond me.

Cheers
#3
General Support / Re: MAC Vendor lookup Script
April 29, 2015, 06:57:44 PM
Ok, little more testing and I've managed to do it.

Requires nmap on server, used an External Parameter in the agent config :

ExternalParameter = MAC.Check(*):nmap -sP -n $1 | grep MAC

Created a template DCI to read MAC.Check(%{node_primary_ip}) via the server as a proxy node, applied the template, bobs your uncle... all working   ;D

Once again , really impressed with NetXMS, this is going to be a fun tool to learn.

#4
General Support / MAC Vendor lookup Script
April 29, 2015, 11:50:28 AM
Hi All,

A couple of weeks ago I started looking for alternatives to PRTG and have settled on netXMS, its fantastic guys. Really impressed.

One thing i'm trying to archive is a MAC vendor lookup, I'll explain.  When I run an auto discovery in PRTG it will find each device on the network and poll for information, without SNMP an agent or WMI connection it will show the node vendor information determined by it's MAC address.  I know this is not 100% accurate but can help sorting devices when first scanning a new network.

So with a simple script i can poll each node for it's MAC address but is there any way I could perform a lookup via an api (http://www.macvendors.com/api) or some other means to detemine the device vendor and store it in a DCI or in the nodes comments??

Thanks in advance

Glenn