Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Solved
Go to Solution
Accepted Solutions
Link copied. Please paste this link to share this article on your social media post.
Hi Matthias,
There is no bug that I am aware of that would cause the system to send for some alerts and not others.
The first thing I would suggest is verifying not only that the UPS saw the issue but that DCE saw the issue. Is the event you're looking for listed in DCE under alarm history?
With APC units, there is what is called "Priority Scanning" which should allow DCE to see the alerts almost immediately. This is noted in k-base FA271584. With a 3rd party device, DCE will not see the event until the next polling sequence. If that is set to 5 minutes, that means that the alarm could occur and last 4:59 and then clear and potentially not get noticed by DCE. Again, alarm history should verify this.
Something else you may want to look at is the policy and actions you're associating with the device(s) that failed to send. Verify the device is actually in the policy you think it is. Verify there is no delay if you click Add alarm actions:
You may also want to verify that the alarm action is properly set up to send to send to the proper e-mail address and for all the different severities it may encounter:
You may also want to validate that for the device in question, the specific device alarm is enabled:
If it is a manually created threshold, make sure it is set up properly as well. Please also make sure that the device itself is not in maintenance mode.
You may also want to check your server or your spam folder. Perhaps something was blocked or sent to the wrong place.
To troubleshoot, you can always try to run a packet capture while testing the UPS in this warning state. This will show you what DCE is or is not sending. You can also try to send to a different e-mail address from this profile...one that is known to work with a different profile.
Thanks,
Steve
Link copied. Please paste this link to share this article on your social media post.
Hi Matthias,
There is no bug that I am aware of that would cause the system to send for some alerts and not others.
The first thing I would suggest is verifying not only that the UPS saw the issue but that DCE saw the issue. Is the event you're looking for listed in DCE under alarm history?
With APC units, there is what is called "Priority Scanning" which should allow DCE to see the alerts almost immediately. This is noted in k-base FA271584. With a 3rd party device, DCE will not see the event until the next polling sequence. If that is set to 5 minutes, that means that the alarm could occur and last 4:59 and then clear and potentially not get noticed by DCE. Again, alarm history should verify this.
Something else you may want to look at is the policy and actions you're associating with the device(s) that failed to send. Verify the device is actually in the policy you think it is. Verify there is no delay if you click Add alarm actions:
You may also want to verify that the alarm action is properly set up to send to send to the proper e-mail address and for all the different severities it may encounter:
You may also want to validate that for the device in question, the specific device alarm is enabled:
If it is a manually created threshold, make sure it is set up properly as well. Please also make sure that the device itself is not in maintenance mode.
You may also want to check your server or your spam folder. Perhaps something was blocked or sent to the wrong place.
To troubleshoot, you can always try to run a packet capture while testing the UPS in this warning state. This will show you what DCE is or is not sending. You can also try to send to a different e-mail address from this profile...one that is known to work with a different profile.
Thanks,
Steve
Link copied. Please paste this link to share this article on your social media post.
Hi Steve, sorry for the delay, but the affected UPS was not reachable for a long time. I have checked all the described steps and they are configured correctly. However, the UPS sometimes generates the message "UPS: On battery power in response to an input power problem" several times a day and no alert is generated. The alert always occours only for some seconds and even only some of them are detected by the DCE. But for none of the events an alarm is generated. Other UPSs send mails, so the server mail settings are correct.
Link copied. Please paste this link to share this article on your social media post.
Hi Matthias,
I'm not sure I fully understand your response. You mention this device does not alert through DCE but others do. You also show this image:
Is this an image of alerts for the UPS in question or are you showing the other device that does alert?
Exactly how long are these on-battery events if you look at the device log (on the device itself)?
Is DCE actually seeing the event of UPS on battery and not e-mailing or is it just not seeing the event at all?
If you look under the device menu, SNMP Device Communications Settings, then SNMP scan settings for this specific device, is it set up with a check mark for priority scanning?
If you look in the logs for the device itself, do you see any errors about SNMP access?
Steve
Link copied. Please paste this link to share this article on your social media post.
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.