ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

ntservices alarm level generated for stopped service not the configured level


Article ID: 187696


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


Some alarms from ntservices probe are being generated with a severity of minor for 'expected state' alarms that should be major.  From the ntservices probe Configure GUI there are not alarm overrides configured for the 'expected state' alarm and the default WrongState message level is set to major.



A custom alarm was defined with the "Default for" property set to wrong_state and a level set to minor which appears alphabetically before the WrongState message available when the ntservices probe is installed.  The probe expects only 1 message to have a "Default for" property set to wrong_state and will use the first it finds in the list of messages unless the message to use for the 'expected state' is explicitly overridden in the profile configuration.
Note that it is not possible to set the "Default for" to the same value for multiple messages from the ntservices probe's Configure GUI opened from Infrastructure Manager or from the probe's Configure page opened from Admin Console.  It is possible to do this from the probe's Raw Configure GUI, by manually modifying the ntservices.cfg file and adding new sections for alarms, or by deploying an ntservices Configuration Only package where there are multiple messages defined with the multiple messages that have the same token key value setting in the <messages> section.


Release : 9.2.0 or later

Component : UIM NTSERVICES any version


Set the "Default for" property for any custom alarms to blank.  This can be done from the ntservices probe's Configure GUI opened from Infrastructure Manager or the probe's Raw Configure GUI.  For any profile that should use the custom alarm instead of the default alarm, override the message in the profile setting the message to the appropriate custom alarm.
For any profile that should use the default message, there is no need to override the message for the profile.
The alarm levels will then be the expected values for the profiles associated with the alarm messages: