Reinitializing Certain Parameters

Due to the inner mechanism of servers, and that of BPM Express for Hardware, certain parameters have a tendency to trigger alerts far too frequently.

Generally, these alerts do not indicate a grave problem, and are more of a nuisance to administrators who have to deal with them all the time. Error Count and Corrected Error Count are such parameters. Reinitializing these parameters automatically reduces the triggering of such “ignorable” alerts.

For this reason, BPM Express for Hardware has configured Error Count and Corrected Error Count to be re-initialized every 24hrs by default. This time-frame is customizable. Basically, here’s what happens:

●When BPM Express for Hardware detects the parameter Error Count for the first time, it notes the number of errors encountered, and keeps that “1st discovered” number as a base–count.

●After which, each time it discovers an Error Count greater than this recorded base-count (which becomes its “threshold”, it triggers an alert through the Status parameter of that class. This, as you can tell, happens far too often. It is the same with Corrected Error Count.

●Now, configured by default to “re-initialize” every 24hrs, it is programmed to take the last recorded Error Count/Corrected Error Count as the new “base-count or threshold” for the fresh round after reset. This is the inner mechanism, the display shows that on reset the count is zero, and if it increases to one, an alarm is triggered.

Example

▪Let’s say the very first discovered Error Count for Logical Disk is 40.

▪Now onwards, every time, BPM Express for Hardware “discovers” the Logical disk, and it meets an Error Count of any value greater than 40, the Status parameter of that instance will trigger an alert.

▪Remember it is programmed for reintialization every 24hrs. So, suppose during the last “collect” just before the reset takes place, the Error Count is ‘48’, BPM Express for Hardware will record ‘48’ as the “base-count” for the next round after re-initialization.

▪Hence after 24hrs (or the time you set: 6hrs, or 1hour etc), the base-count/threshold for Error Count will be 48, and so on and so forth.