amrhossam

Okay, so what is the status "warning"? and what is the difference between it and "unknown"? and why does email alerts that used to come to me when the node was down now come saying node is "warning"? never down, only warning then up again. even when i disconnect some device i get it as warning while i know it is…

I guess if it would be changed it should be either an URL or the link with the work "Click Here" only, so i can place it in the email the way I want. It is written in an unprofessional way with no punctuation and uncomplete sentence. I have an issue with the alert acknowledgement which is when i click on the link to ask…

I have the same exact issue mentioned above here. Suddenly out of no where the email alerts that i have set to alert me whenever a node status "is not equal to up" started sending me "Node status is warning" instead of "Down" and then it goes up again. Note that the same alert was working fine and i have not changed…

Auto detection doesnt work on Blackberry 9700 too.

btw i opened a case 4 days ago and still did not get any response :)

I have checked the documentation but i still do not understand, why could be the status unknown? what does that indicate, does it indicate that it is unreachable? What if an application status is unknown by APM or interface status unknown, what does that mean?

Okay, I now understand that I get the status "Warning" when there is a high packet loss rate and that I can change the time interval for this. What if I get the status "Warning" message instead of "Down" when I know the node is down? For example if I shutdown a switch or a server and I get an email saying that the node…

Thanks vaiper, but this is not something that happens sometimes, its something that happens always, i mean every APM alert i receive and most interface alerts are "unknown", so it is not an error that occurred in traffic or something that happens sometimes with the poller, and the same thresholds and trigger times used to…

So what kind of problem could this be? How can I troubleshoot/solve it?

This is the exact same issue I am facing. This feature would be really useful. Why cant we use "is not" 172.16.20.*? I mean, if the logic was "IP Address matches 172.16.20.*" it works fine, and it selects all the nodes that are in this subnet, why cant there be its opposite, "Does not match", so that i can apply the…