Differences

This shows you the differences between two versions of the page.

--- networking:monitoring:wattbox [2015/08/28 14:47]
jcooper created
+++ networking:monitoring:wattbox [2015/08/29 17:11] (current)
jcooper
@@ Line 1: / Line 1: @@
-====== Zabbix NMS Host ======
+====== WattBox ======
-**Home**: http://www.zabbix.com/
+**Home**: http://www.snapav.com/t-Power-WattBox.aspx/
-**Downloads**: http://www.zabbix.com/download.php
+**Documentation**: http://www.av-iq.com/avcat/images/documents/dataSheet/2312.pdf
-**Documentation**: https://www.zabbix.com/documentation/2.4/manual/installation/requirements
+Evaluating the WattBox WB-200-IPCE-3 I found it to be a capable remote controlled per port surge suppressor.
-**Wiki**: http://www.zabbix.org/wiki
+  * It has the ability to use ICMP to determine if a device/Internet is accessible and do an auto power off/on of a port.  I.E. reboot Cable Modem/DSL to attempt reconnect of Internet.
-**Forums**: https://www.zabbix.com/forum/
+  * You can schedule unattended power cycle of the ports.
-**HowTo - Server**: http://tecadmin.net/install-zabbix-on-ubuntu/
+  * It also can send email alerts on conditions.
-**HowTo - Agent**: http://tecadmin.net/install-zabbix-agent-on-centos-rhel/
+:!: I was not able to make the email option work on Zimbra or Gmail accounts.  Does not appear to support encryption.  It did work with mail.sonoracomm.com.
-See also **[[networking:monitoring:zabbix]]**
+===== Setup =====
-===== Add a Host to Monitor =====
+http://www.dailymotion.com/video/x16znav_wattbox-wb-200-ipce-3-tutorial_tech
-http://tecadmin.net/add-host-zabbix-server-monitor/
+:!: Default credentials User:admin Password: <none, leave "Password" field blank>
-https://www.zabbix.com/documentation/2.4/manual/config/hosts/host
+  * The "Power on Delay" settings are connected to the auto power cycle function triggered by the result of the ICMP availability of a host.  The delay is the amount of time the port will be without power.  Handy for devices that need to be in a certain condition (booted up) before another device comes on.
-===== Customize Trigger =====
+  * Auto Reboot must be enabled on the WattBox, disabled by default.
-https://www.zabbix.com/forum/showthread.php?t=19921
+https://www.youtube.com/watch?v=HDx6FiR_La4
-Use Case: You have a monitored device on a circuit that is having issues.  Rather than have constant alerts due to packet loss etc. modify the alert to minimize the churning until the circuit can be stabilized then return to the stock template.
+:!: The videos and documentation will tell you to install the configuration software. This is to find the device on your network. Determine the devices IP address via DHCP log etc. and use your browser making the install unnecessary.
-  * Clone the template with the problem alert.  Use "Full Clone" to take advantage of the previous configuration.  Rename appropriately to appear next to original in template list.
+  * WattBox has their own DynDNS system so you can remotely access the device via HTTP (port configurable) if you forward the port to your WattBox.
-  * Remove original template and attach new cloned template.
-https://www.zabbix.com/documentation/2.4/manual/config/templates/template
+===== Firmware Updates =====
-  * Create/Clone the problem alert in the cloned template then modify for appropriate level
+:!: Firmware updates can only be done with the configuration software.
-IE: Circuit is flaky, you know it and fix is down the road.  "Response time is too high" alert is set to trigger if over 200ms for 10 minutes and triggers several times a day.  Modify for 400ms and then when an alerts is sent there could be something to investigate.
+https://www.onaisle8.com/wcsstore/ExtendedSitesCatalogAssetStore/attachments/documents/PowerManagement/SoftwareAndFirmware/WB-IP_FirmwareUpdateInstructions.pdf
+===== OVRC =====
-Configuration -> Host -> Triggers (on problem host) -> Disable "Problem Trigger" -> Click Problem Trigger -> Clone Problem Trigger -> Rename Problem Trigger -> Edit expression and Description -> Add
+:!: This device is also OVRC capable in that it touches base with the OVRC mother ship and can be managed from www.ovrc.com.  An OVRC account is necessary.
+:!: Creating and account at OVRC you will be asked if you are a reseller at SnapAV or Aisle8 and if you say No you will be stopped from creating an account.  However, if you say yes you can still setup an account with any valid email address.
+  * With an OVRC account you can have multiple "Accounts" each with there own devices to be managed.
-==== Trigger Dependencies ====
+  * All settings available with the web interface are also configurable via the OVRC panel
+  * To add a device just enter the MAC address of a device that is online.  It will be detected and then you enter the S/N.
-https://www.zabbix.com/documentation/2.4/manual/config/triggers/dependencies
-Sometimes the availability of one host depends on another. A server that is behind some router will become unreachable if the router goes down. With triggers configured for both, you might get notifications about two hosts down - while only the router was the guilty party.

Virtual Architects Support Wiki

User Tools

Site Tools

Differences

Page Tools