This question was originally posted on DCIM Support by Naveed Zafar on 2018-09-20
"Not receiving alerts from Netbotz 570 Appliance from the policy defined in Struxreware DCE"
We have a struxureware DCE appliance from where we monitor our Netbotz, ATS, UPS and PDUs. This appliance has a default notification policy. This policy applies to every devices that we add on Struxureware DCE appliance.
I have added the new Netbotz rack monitor 570 appliance on Struxureware. I can see that netbotz under device view but unable to find the device under the discover tab in notification policy. The default policy is not getting applied on to the new Netbotz 570. Therefore we are not receiving any email alerts from the new Netbotz using Struxureware dce.
I have setup the Email server on the new Netbotz and when I click send test email it says “Unable to send test email”
"Can we integrate the netbotz 570 with Struxureware dce appliance server 7.4.x"
I can see all the netbotz devices under the Environmental device group. When I am in the Device View and want to see the status of the device by double clicking on it, it opens internet explorer and prompt for proxy settings. I am able to see other devices from Struxureware DCE by double clicking in the device view on the device in struxureware.
This answer was originally posted on DCIM Support by Steven Marchetti on 2018-09-20
The NetBotz 3xx, 4xx, and 5xx devices differ from the SNMP and Modbus devices that DCE monitors. The monitoring scheme it uses goes all the way back to NetBotz Central which is the predecessor to DCE. The NetBotz / Central alerting configuration allowed Central to configure the NetBotz devices but left the alerting up to the NetBotz itself basically putting the intelligence "at the edge" so to speak. This way if Central went down, the devices were still able to alert for themselves.
Add to this the fact that a NetBotz device has many more alerting options than DCE such as relay outputs, beacons, modem alerts, etc, it made sense to keep that paradigm when updating the system. It is still this way today. DCE does not alert for a NetBotz 3xx, 4xx, or 5xx device and it is up to the device itself, whether configured through Advanced View or DCE, to alert for itself. The only alert DCE will send is if it loses communications with a NetBotz device and that will be sent to any user that has an e-mail configured with his login account that also has the rights to NetBotz devices within DCE.
As for being unable to launch to the device properly, It is possible that it is due to the browser that you're using and DCE through it's preferences, allows you to use a different browser. What happens more often is that customers put a NetBotz device on the DCE private LAN and there is a known issue when attempting to launch to a NetBotz device on that private LAN. If you need to see the web page and it is on the private LAN, you'd need to put your computer on that LAN. What is easier to do is right click the device and launch Advanced View. You not only get to see everything you can see on the web page but also get full configuration of the device.
This comment was originally posted on DCIM Support by Naveed Zafar on 2018-09-21
Thanks Steve for your help so far. I have managed to launch the netbotz 570 using Advance View client. However I have noticed when I try to launch using mozila firefox it says "504 Gateway timeout" and when I launch it using google chrome it ask for user name and password and then display nothing on the page.
I am fixing up the alerting query that I have raised for Netbotz 570 and will let you know how it goes.
One more question I want to ask with this netbotz 570.
We have a beacon light with us and want to configure it. What options do we have with beacon the light alerting and how can we configure it.
I want the light to be ON when the alarm is raised on netbotz for example
when the rack door is open, when there is a leak on the datacentre and
when the netbotz is turned off. Is there anything else that we can setup.
This comment was originally posted on DCIM Support by Steven Marchetti on 2018-09-21
Is the NetBotz appliance on the private LAN of DCE?
For alerting, first connect the beacon. You can look at k-base FA226040. Although this is for configuring an e-mail alert action, the steps for creating the alert action for a beacon is very similar in that once the action is created, you need to associate it with an alert profile then that profile with a temperature sensor. You'll want to configure the beacon alert action and if there are none available, you click new and create one:
In the image above, I'd already created 0_Beacon. Please note this may not be available if you have not yet connected the beacon. As you're creating the alert, you have to name it, you can set it (as with any alert) to trigger based on any or all alert severities. You need to select the beacon, what state it should be when there is an alert and what state it may change to when the alert is cleared.
Please note that if you have more than 1 threshold triggering the beacon (or any output such as a relay) and any one of them returns to normal, the beacon state will change to it's return to normal state as configured in the image above. If you have 10 alerts triggering, you only need 1 alert to clear. Because of this, you may want to configure the alert profile / sequence to repeat. If it's already on, turning it on again will do nothing but if something turns it off, you can make sure that any still active alert turns it back on:
There are so many ways to configure it, I can't give you a 1 size fits all answer.
This comment was originally posted on DCIM Support by spezialist on 2018-10-07
Dear Naveed Zafar,
Tell us, please, did you solve your question or not?
Discuss challenges and get support in energy and automation with 30,000+ experts and peers.
Over 10,000+ support articles are available to help you find answers to your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!