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 - sharpspro

#16
Guys,

I'm looking to create a script that will only show drives within a certain size range. For example only show drives that are between 500Gb and 1,000GB or 1,000GB and 1,500GB.

The reason being is that i want to setup thresholds differently on drives. Smaller drives i would like to have a higher percentage free than huge drives. The bigger the drive gets the lower i want the percentage free to alert on the threshold.
#17
I currently have 113 Server reporting
#18
Just want to share how I got my issue resolved. I created Tabled DCIs on a template that applied to all server nodes. I created Tabled DCIs for FileSystem.Volumes, System.InstalledProducts, System.Processes and System.Services.

So I removed the Table DCIs from all nodes it was applied to and have not had an issue since. I think I should have changed the polling time from 60 sec to something less frequently, since its pulling so much info each poll.

The CPU is back to normal as well. I liked the Table DCIs but not sure if this is ready or I just configured it wrong.

Thanks!
#19
I have NetXMS running on a Windows Server 2008r2 and having an issue since I updated to version 2.0-M1.

1. What seems to happen after a day of running, it will be maxed out on RAM and CPU. When this happens the notifications go crazy constantly poping up in task bar. Notification shows ("NODE NAME": Node status changed to WARNING) it will say warning, minor, major or critical and flashes quickly.

2. Within the NetXMS console the HEAP size at the bottom is jumping up and down.

Any ideas on this? Will updating to 2.0-M2 fix this issue? Looks like the change log shows that this version addresses a NetXMS crashing on some versions of Windows.

Thanks in advance!! :)

#20
Hi Victor,

Thanks for the reply! When will that version 2.0-M3 be available?

Thanks!
#21
The issue I see with this is when a CD disk does not report its value as ERROR and starts reporting the value as "0". An example of this would be when a CD/DVD is put into the drive and the reported value changes from ERROR to 0 (zero) space available and the threshold alert will be sent.


My question is, is there a way to exclude CD/DVD drives completely with this filter? Or is there another work around to get this accomplished?

Below is how I have the scrpit currently:
if (rindex($1,":")>0)
{
// if(length($1)>3) return false;
if (rindex($1,"A:")>0) return false;
value = AgentReadParameter($node, "FileSystem.Total(" . $1 . ")");
return (value != null) && (value > 0);
//return %(true, $1);
}
return false;
#22
That worked great. Thank you so much!
#23
That script worked great. Is there a way to add to it?

I would like for the drives that do not have drive letters to NOT show up e.g. "Percentage of free space on file system \\?\Volume{xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx}\" ----instead I only want it to show valid drives e.g. "Percentage of free space on file system C:\"

I will continue to search on this but any help is appreciated.
#24
General Support / Node down and situation setup
March 18, 2015, 03:16:49 AM
I'm trying to get NetXMS to email me when a PRIMARY interface NODE is down and not the SECONDARY interface NODE. I created a node called NIC01 and a node called NIC02. The secondary NIC02 will not work if the primary NIC01 is down. I want NIC02 to report only if NIC01 is still up.

I used the following link and other posts and could not get it figured out. https://www.netxms.org/forum/configuration/node-down-config-question/

Below is what i have now:

1. Open Situations and Create situation called "NodeDown"

2. Using the SYS_NODE_DOWN event in Event Configuration

3. Open Event Processing Policy

4. Created  Event Processing Policy
- Event: SYS_NODE_DOWN
- Situtation object: NodeDown
- Instance: %n
- Attribute: NAME: status  VALUE: 1

5. Created  Event Processing Policy
- Event: SYS_NODE_DOWN
- Filtering Script: SEE BELOW

sub main()
{
   s1 = FindSituation("NodeDown", "NIC01");
   isDownA = (s1 != null) ? s1->status : 0;
   s2 = FindSituation("NodeDown", "NIC02");
   isDownB = (s2 != null) ? s2->status : 0;
   return s1 && s2;
}

What am I missing? Do i need that 2nd Policy at step 5? or do I add the script on the first policy, where i defined the situation.

Any help on this would be great. I love NetXMS and I have been tasked with figuring this out. Figuring this part out would be a great achievement for me.

Thanks for any help on this
Cheers!
#25
I'm tring to create a DCI to monitor all server's network interface adaptors. I can get this to work but needs to be setup for each server. I would like the DCI to scan for all Network Adaptors (Instances) and report the Bytes or bits per sec on each. Below is what i have tried so far and I believe I am close to having this figured out but need some advice. I know how to set it up for incoming/outgoing and also the conversion to Bytes to bits but I need DCIs that can report all the interfaces and the network traffic.

1. Open the "Data Collection Configuration" for the template
2. Create a new parameter.
3. On the "General" tab. PARAMETER: Net.Interface.BytesIn64(*) DATA TYPE: Unsigned Interger 64 bit
4. On the "Instance Discovery" tab. INSTANCE DISCOVERY: Agent List. LIST NAME: Net.InterfaceList

Any help is greatly Appreciated.
Thanks! Russ