NetXMS Support Forum

Got it thank you. I'll put this over on my other thread that I started.

Just upgraded to version 2.1 from 2.07.

Regarding the "Windows" Template:

If I edit it, after restarting the Core service, the "Windows" template goes back to default and I lose my customization's
If I delete it, after restart, it comes back with the default settings.

PERFECT!! Thank you! I checked the "View all alarm categories" and can now see the alarms.

Do you have any ideas on the "Windows" template? Or perhaps I'll post a new topic ... ?

If I edit it, after restarting the Core service, the "Windows" template goes back to default.
If I delete it, after restart, it comes back with the default settings.

I think this is what you are looking for. If not, it should get you started. I did not find a " time resolved" field, only the last time the alarm was changed. Which I am assuming, if it was resolved or terminated, that would be the last time it was changed. I added in the source object name, as I thought that would be useful.

select object_properties.name as 'Node Name', alarms.alarm_id as 'Alarm ID', alarms.message as 'Message', DATEADD(S,alarms.creation_time, '1970-01-01') as 'Date Created',DATEADD(S,alarms.last_change_time, '1970-01-01') as 'Date Last Changed',
CONVERT(varchar, (alarms.last_change_time-alarms.creation_time) / 86400) + ':' + CONVERT(varchar, DATEADD(s, (alarms.last_change_time-alarms.creation_time), 0), 108) as 'Age DD:HH:MM:SS'
from alarms
inner join object_properties on object_properties.object_id=alarms.source_object_id
where alarms.alarm_state > 1
order by alarms.last_change_time desc

I am trying to upgrade from version 2.0.7 to 2.1. I am on Windows Server 2008 R2 with MSSQL. I have done the following steps:
1. nxdbmgr check (no errors)
2. run installer with /silent (no errors)
3. NetXMS Core starts (no errors)
4. NetXMS Management Console starts (no errors)

I run into an issue where I select to view alarms on a device and the table (in Management Console) is blank. If I look directly into the table, there are alarms that should be shown. The other odd thing is the Templates. I have a "Windows" template that I have added DCI's to and after the upgrade there is another "Windows" template which seems to be the default that would be installed with Core. So I end up with two "Windows" templates.

The following troubleshooting steps were done with the same result as the above:

1. Upgraded to 2.0.8 then to 2.1
2. Detached netxms_db, created a new db, performed upgrade, attached prior netxms_db and ran nxdbmgr.exe upgrade -t. I did not see any errors and it said it completed successfully.
3. Deleted all rows from "alarms" table prior to upgrade

Right now I am cloning my 2.0.7 environment so that I can work on the issue without impacting my production monitoring. I think my next step will be to export the database without collected data, initialize, import the database without collected data, then upgrade.

If there are any suggestions, please let me know. I'll update if I find anything.

I was up against my upcoming maintenance window and decided to put in something quick and dirty based on your suggestion.

I separated the email and agent action Event Processing Policies
I added an unmanaged node, "Patch".
Set a custom attribute on the "Patch" node, "PatchTime".
If I set "PatchTime" on node "Patch" to something other than 0, that means I am in maintenance mode and do not want to see email alerts
In the email event processing policies I added this to the Filtering Script:

$patch = FindNodeObject($node, "Patch");
$patchtime = GetCustomAttribute($patch, "PatchTime");
if ($patchtime == 0) return true;
else
return false;


I can manually change the value easy enough and this meets my needs on a basic level. However, I am planning on taking this further and walking from the topmost parent down to the node with a similar (or same) custom attribute setup. That way I can be granular with my "maintenance light" mode. Open to any further suggestions for improvements/functionality.

I'm looking for a good way to mute email notifications and still perform actions on the server.

Here is the situation: I have a large group of Windows servers that perform very similar functions. After a reboot, there are two of the same services on each server that do not start. I have an action in NetXMS that will start the service when it is down and that works. When I do monthly down time on the servers, I put them into maintenance mode, but then of course, the service restart actions do not process. I only put the servers into maintenance mode to mute the notifications, meaning, I don't care if there are alarms generated during the downtime as long as I don't receive email alerts.

1) I could just change the configuration to an invalid STMPServer. But I will lose alerts on servers not in maintenance
2) Create two Event Processing Policies for each service, one that starts the service and another that sends the email. Group the start and email policies together with a stop processing event in the middle of them
3) Get clever with scripting
4)

Thank you for any suggestions/assistance.

Expanding on this, you can do it manually by right clicking on any node in the Objects tree (Entire Network if so desired) and there is an option for Maintenance. You can Enter, Leave or Schedule maintenance. I do this when I am updating my servers or otherwise taking them offline. Usually I will schedule maintenance for the group I am working on but set it for twice what my maintenance window is. My procedure is to leave maintenance when I am done (hopefully early) but if I forget, it will happen on it's own. That way if go over my time, I don't start getting a bunch of alarms

To do it automatically, choose Configuration/Scheduled Tasks. Here you can create a scheduled task to enter maintenance mode and then another task to leave maintenance mode. I have a few servers that update on their own or have a monitored process that resets on a schedule, so I use scheduled tasks for those instances.

I would like to be able to add comments to scheduled tasks. Ideally, they would show in a column on the Scheduled Tasks tab, but it would also be functional if they were only visible when editing the scheduled task. My need is to have a convenient way to document the what and why of the task.

Thank you

I got it working.

One thing that kept tripping me up is that when I would make a change to the discovery script and then Force DCI poll, it would say that it was unsupported. So I would make more changes and that would be unsupported. I probably had it working earlier and just needed to be patient for NetXMS to do it's thing.

I had to still see if it was Windows 2003 because newer versions use both services but only the MpsSvc is the firewall.

Thank you for the reply.

My original template script worked, it just took longer than expected to apply. How often is it checked to see if a template should be automatically applied? The active discovery interval?

Can you see a way to make it work so I only need one template?

I'm new to NetXMS and it is working well for our needs. I am tweaking our DCI's now and have a question.

I have Windows 2003, 2008, and 2012 servers. I have a template setup to add DCI's to the servers and that works fine. I am monitoring the windows firewall service and the name is different on 2003 ("SharedAccess") compared to 2008/2012 ("MpsSvc"). I would like to use the same template/DCI and detect if it is on 2003. I tried using an instance discovery script, but that did not work.

The script I used was:
if($node->sysDescription like "*2003*") {
$1 = "SharedAccess"
else $1 = "MpsSvc"
}
return true;

As an alternative, I tried to make separate templates with Auto apply rules. I tried this for the rule:
return $node->sysDescription like "*2003*";
and that is not working as I expect.

Any suggestions would be appreciated. Thank you.

Gary