Hysteresis

[aorange]

My previous thread got blocked with no answers so here is a new one... I am becoming more and more convinced that there is a bug preventing hysteresis to be correctly configured using CTRL in 3.10 SP2

I am doing something as simple as:

Code: Select all

float fHighHigh = 42.78;
float fHyst = 0.1;

dpSet(dp + ".Value:_alert_hdl.5._l_limit",      fHighHigh,             
      dp + ".Value:_alert_hdl.5._hyst_type",    DPATTR_HYST_VALUE,             
      dp + ".Value:_alert_hdl.5._l_hyst_limit", (fHighHigh * fHyst));

I am using 5 alert ranges and according to the help "The hysteresis values are entered relative to the limiting value", i.e. my code should yield a lower hyst limit of ~47.1 for range 5. In my case I end up with a negative value of 38.5

The documentation is also very confusing as the _alert_hdl section of the help file states that the type of _u_hyst_limit is a boolean whilst _u_hyst_limit is a var. I am guessing this is a typo?

PS. I have sent this via the official support channels... if anyone has a quick answer however, I would appreciate it as I am still waiting for support to resolve the last issue I sent.

[leoknipp]

Hello Mr. Garcia!

We didn't get the official service request. Maybe the service request didn't contain the necessary information that it can be assigned to ETM.
Can you please tell us the SR-number for the service request, then we can have a look at it.

Best Regards
Leopold Knipp
Senior Support Specialist

[aorange]

Hi Leopold,

I now have the service request number (Service-Request= 1-2854634921). Sorry to flood you with these issues but I am also having problems with the pt sum alert generation scripts, I haven't been able to narrow it down sufficiently to produce a description that will allow you to reproduce the problem but in short, the sum alert DPs are not being parameterised correctly when generating sum alerts for the whole tree (I have a topology with nearly 9000 nodes), it works correctly however when doing a few branches at the time.