Cacti tool is an open-source web-based network monitoring and system monitoring graphing solution for IT business. Cacti enable a user to poll services at regular intervals to create graphs on resulting data using RRDtool. Generally, it is used to graph time-series data of metrics such as network bandwidth utilization, CPU load, running processes, disk space, etc.
In this how-to, we are going to show you how to install and set up a complete network monitoring application called Cacti using Net-SNMP tool on RHEL, CentOS and Fedora systems using YUM and DNF package manager tool.
Cacti Required Packages
The Cacti required the following packages to be installed on your Linux operating systems like RHEL / CentOS / Fedora.
Apache : A Web server to display network graphs created by PHP and RRDTool.
MySQL : A Database server to store cacti information.
PHP : A script module to create graphs using RRDTool.
PHP-SNMP : A PHP extension for SNMP to access data.
NET-SNMP : A SNMP (Simple Network Management Protocol) is used to manage the network.
RRDTool : A database tool to manage and retrieve time series data like CPU load, Network Bandwidth, etc.
Note: The installation instructions were shown here are written based on CentOS 7.5 Linux distribution.
Installing Cacti Required Packages on RHEL / CentOS / Fedora
First, we need to install following dependency packages one-by-one using the default package manager tool as shown.
# yum install mysql mysql-server [On RHEL/CentOS 6]
MariaDB
is a community-developed fork of the MySQL database project and
provides a replacement for MySQL. Previously the official supported
database was MySQL under RHEL/CentOS and Fedora.
Recently, RedHat makes a new transaction from MySQL to MariaDB, as MariaDB is the default implementation of MySQL in RHEL/CentOS 8/7 and Fedora 19 onwards.
We need to configure MySQL for Cacti, to do this we need to secure a newly installed MySQL server and then we will create Cacti database with user Cacti. If you’re MySQL is already installed and secured, then don’t need to do it again.
# mysql_secure_installation
Create MySQL Cacti Database
Login into MySQL server with a newly created password and create Cacti database with user Cacti and set the password for it.
On RHEL/CentOS 6 and Fedora 18-12
[root@tecmint ~]# mysql -u root -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 3
Server version: 5.1.73 Source distribution
Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> create database cacti;
Query OK, 1 row affected (0.00 sec)
mysql> GRANT ALL ON cacti.* TO cacti@localhost IDENTIFIED BY 'tecmint';
Query OK, 0 rows affected (0.00 sec)
mysql> FLUSH privileges;
Query OK, 0 rows affected (0.00 sec)
mysql> quit;
Bye
On RHEL/CentOS 8/7 and Fedora 19 Onwards
[root@tecmint ~]# mysql -u root -p
Enter password:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 3
Server version: 5.5.41-MariaDB MariaDB Server
Copyright (c) 2000, 2014, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> create database cacti;
Query OK, 1 row affected (0.00 sec)
MariaDB [(none)]> GRANT ALL ON cacti.* TO cacti@localhost IDENTIFIED BY 'tecmint';
Query OK, 0 rows affected (0.00 sec)
MariaDB [(none)]> FLUSH privileges;
Query OK, 0 rows affected (0.00 sec)
MariaDB [(none)]> quit;
Bye
Install Cacti Tables to MySQL
Find out the database file path using RPM command, to install cacti tables into newly created Cacti database, use the following command.
# rpm -ql cacti | grep cacti.sql
Sample Output:
/usr/share/doc/cacti-1.2.6/cacti.sql
OR
/usr/share/doc/cacti/cacti.sql
Now we’ve of the location of Cacti.sql file, type the following command to install tables, here you need to type the Cacti user password.
[root@tecmint ~]# mysql -u cacti -p cacti < /usr/share/doc/cacti-0.8.8b/cacti.sql
Enter password:
Configure MySQL settings for Cacti
Open the file called /etc/cacti/db.php with any editor.
# vi /etc/cacti/db.php
Make the following changes and save the file. Make sure you set password correctly.
/* make sure these values reflect your actual database/host/user/password */
$database_type = "mysql";
$database_default = "cacti";
$database_hostname = "localhost";
$database_username = "cacti";
$database_password = "your-password-here";
$database_port = "3306";
$database_ssl = false;
Configuring Firewall for Cacti
On RHEL/CentOS 6 and Fedora 18-12
[root@tecmint ~]# iptables -A INPUT -p udp -m state --state NEW --dport 80 -j ACCEPT
[root@tecmint ~]# iptables -A INPUT -p tcp -m state --state NEW --dport 80 -j ACCEPT
[root@tecmint ~]# service iptables save
Open file called /etc/httpd/conf.d/cacti.conf with your choice of editor.
# vi /etc/httpd/conf.d/cacti.conf
You need to enable access to Cacti application for your local network or per IP level. For example, we’ve enabled access to our local LAN network 172.16.16.0/20. In your case, it would be different.
Alias /cacti /usr/share/cacti
<Directory /usr/share/cacti/>
Order Deny,Allow
Deny from all
Allow from 172.16.16.0/20
</Directory>
In the latest version of Apache (ex: Apache 2.4), you may need to change according to the following settings.
Alias /cacti /usr/share/cacti
<Directory /usr/share/cacti/>
<IfModule mod_authz_core.c>
# httpd 2.4
Require all granted
</IfModule>
<IfModule !mod_authz_core.c>
# httpd 2.2
Order deny,allow
Deny from all
Allow from all
</IfModule>
</Directory>
Finally, restart the Apache service.
[root@tecmint ~]# service httpd restart [On RHEL/CentOS 6 and Fedora 18-12]
[root@tecmint ~]# systemctl restart httpd.service [On RHEL/CentOS 8/7 and Fedora 19 onwards]
Setting Cron for Cacti
Open file /etc/cron.d/cacti.
# vi /etc/cron.d/cacti
Uncomment the following line. The poller.php script runs every 5mins and collects data of known host which is used by Cacti application to display graphs.
Finally, Cacti is ready, just go to http://YOUR-IP-HERE/cacti/ & follow the installer instruction through the following screens. Enter the default login details and hit Enter button.
User: admin
Password: admin
Cacti User Login
Next, change default Cacti password.
Accept Cacti License Agreement
Next, the screen shows Pre-installation Checks for Cacti installation, please correct the suggested settings in your /etc/php.ini file as shown and restart Apache after making changes.
Cacti Pre-installation Checks
Similarly, you also need to grant access to the MySQL TimeZone
database for user Cacti, so that the database is populated with global
TimeZone information.
mysql> use mysql;
mysql> GRANT SELECT ON mysql.time_zone_name TO cacti@localhost;
mysql> flush privileges;
Cacti MySQL Pre-Installation Checks
Please choose the installation Type as “New Install“.
Select Cacti Installation Type
Make sure all the following directory permissions are correct before continuing.
Cacti Directory Permission Checks
Make sure all of these Critical Binary Locations and Versions values are correct before continuing.
Critical Binary Locations and Versions
Please choose the default Data Source Profile to be used for polling sources.
Select Data Source Profile
Please, choose the Device Templates that you wish to use after the Cacti Install.
Select Cacti Device Templates
Set the Server Collation in your MySQL configuration file /etc/my.cnf under the [mysqld] section as shown.
Ada beberapa cara yang bisa teman-teman bisa coba untuk mengatasi
login page hotspot tidak otomati muncul, yang akan saya bahas pada
tutorial kali ini.
1. Kesalahan Konfigurasi DNS Server
Untuk membuat sebuah server hotspot teman-teman terlebih dahulu harus
membuat sebuah DHCP Server agar ketika ada device yang terhubung ke
Access Point bisa mendapatkan IP secara otomatis dari DHCP Server, bagi
teman-teman yang masih pemula terkadang ada saja konfigurasi yang
terlewat salah satunya DNS Server pada menu DHCP tidak di isi. Bagi
teman-teman yang membuat DHCP Server baru melalui DHCP Setup memang
kolom DHCP Server akan kosong jadi harus dtambahkan secara manual.
Untuk menambahkan DHCP Server caranya, buka menu IP –> DHCP Server –> pindah ke tab Networks, kemudian
pilih IP Server hotspot teman-teman. kemudian isi DNS Server, dan
biasanya menggunakan IP Gateway, seperti pada gambar dibawah ini:
2. Kesalahan Urutan NAT
Fungsi NAT pada mikrotik salah satunya berfungsi untuk meredirect,
login page tidak otomatis muncul bahkan sama sekali tidak muncul
walaupun sudah diketikan IP Server hotspot di browser, bisa terjadi
karena urutan default untuk Hotspot berubah, bisa karena kesalahan
seting atau penambahan rule baru di Firewall NAT. Untuk mengatasi
berubahnya urutan NAT untuk hotspot teman-teman bisa membuat ulang
server hotspot, dengan begitu urutan di Firewall NAT akan berbuah
menjadi default.
Caranya,buka menu IP –> Hotspot –> di tab server pilih server
hotspot kemudian klik kanan lalu remove. Setelah server hotspot di hapus
tambahkan server hotspot baru dengan konfigurasi sama seperti
sebelumnya, dengan begitu NAT untuk hotspot kembali ke default. Dan
pastikan rule tersebut berada di paling atas.
3. Tidak ada Koneksi Internet
Login page tidak otomatis muncul bisa karena tidak ada koneksi
internet, sebelumnya silahkan cek terlebih dahulu apakah Mikrotik
teman-teman memiliki koneksi internet atau tidak. hehe
4. Bug pada RouterOS
Pihak Mikrotik sendiri secara berkala melakukan pembaharuan atau
penambahan fiture, hal tersebut demi memperbaiki bug/error dan
meningkatkan keamanan pada RouterOS. Ada beberapa versi RouterOS dimana
login page tidak otomatis muncul itu karena Bug pada RouterOS
teman-teman bukan karena kesalahan setingan/konfigurasi, untuk mengatasi
hal tersebut teman-teman harus mendowngrade ke versi sebelumhya, atau mengUpgrade ke versi terbaru.
Berikut versi RouterOS yang terdapat Bug pada Hotspot:
Versi 6.45.6
Versi 6.46.2
Teman teman bisa menggunakan RouterOS versi 6.44.6 long term, yang saya pakai tidak ada kendala pada login page Hotspot yang tidak muncul otomatis.
Nah itulah 4 Cara Mengatasi Login Page Hotspot tidak Otomatis Muncul, bagi teman-teman yang telah mencoba ke-4 cara tersebut namun gagal, bisa berdiskusi di kolom komentar. Semoga bermanfaat.
Jack Wallen shows you how to make working with CentOS 7 iptables much easier with the help of an ncurses-based GUI.
If you manage a CentOS 7 GUI-less server, you probably
know that managing the firewall can be a bit of a hassle. Wouldn't it be
nice if there was a handy, ncurses-based tool to make this process a
bit easier? Oh wait, there is. That tool is system-config-firewall-tui.
With this tool, you can easily set a service/interface/port as trusted,
to allow incoming traffic to that port. Only those trusted elements will
be allowed in.
Out of the box, system-config-firewall-tui isn't
installed. I'm going to walk you through the process of installing the
tool, enabling it to run, and then using it to open a port or two. I'll
be demonstrating on CentOS7, but this tool is also available for Fedora
as well. This tool directly manages iptables rules, so having a simple
to use frontend for that is pretty important for some users. Don't get
me wrong, system-config-firewall-tui doesn't give you the massive power
of iptables (for that you really need to dive into the deep waters of
iptables), but it does make the basic task of opening ports (via
iptables) quick and easy.
Let's install and use system-config-firewall-tui.
Installation
The installation of the tool is pretty straightforward. Open up a terminal window and issue the command:
sudo yum install system-config-firewall-tui
That will install the tool. However, when you go to run the command sudo system-config-firewall-tui, you'll be warned that firewalld is running, thus preventing the tool from opening. To get around this, issue the commands:
The ncurses interface will open (Figure A).
You should immediately notice that the firewall isn't enabled. Tab to
the [ ] Enabled section and tap the keyboard spacebar to enable the
firewall. Figure A
You must enable the firewall to continue.
With the firewall enabled, you can now tab down to Customize. In the new window (Figure B), you can scroll through the list of services to allow through the firewall. Figure B
Our list of available services.
After you've enabled your services, tab down to Forward. This is not
port forwarding, rather the "Next" button. In the next screen (Figure C), you can add, edit, or remove additional ports. Figure C
Adding additional ports to be considered trusted.
If you tab to Add and hit Enter on your keyboard, you can then add a
single port or port range, as well as a protocol. Do note, the protocol
(tcp/udp) is required. Once you've taken care of that, tab to OK.
After you've added a custom port/protocol, tab down to Forward. In the
resulting window (Figure D), you can list an interface as trusted.
Figure D
Setting a trusted interface.
Enable as many interfaces as you need to be trusted and tab down to
Forward. In the next screen, you can enable ports for port forwarding.
Tab to Add and hit Enter on your keyboard. In the resulting screen (Figure E), enter the necessary source and destination information. Figure E
Setting up port forwarding.
In the next screen, you can mark ICMP types that should be rejected (Figure F). Enable each, from the list, and then tab to Forward, and tap your keyboard Enter key. Figure F
Rejecting ICMP types.
In the next window (Figure H), you can add custom rules if necessary. Figure H
Adding custom rules.
Tab to Forward and hit Enter. Once you've finished with the custom
rules, tab to OK and hit Enter. In the resulting screen, tab to Close
and hit Enter. You will find yourself on the first screen where you can
enable the firewall. Tab to OK and you will be warned that the new rules
will override the current set. Tab to Yes and tap Enter on your
keyboard. You've just created a new rule to the iptable chain, all with
the help of a user-friendly ncurses GUI. If you issue the command sudo
iptables -L you should see your new rules listed.
An easier route
Although system-config-firewall-tui isn't quite as flexible as working
directly with iptables, if you're not ready to take the plunge into
those deeper waters, this GUI is a much easier route to working with the
firewall system on CentOS 7. Give system-config-firewall-tui a go and
see if it doesn't turn into your go-to for the platform.
Pagi ini saya selesai memindahkan sistem dan database MySQL Server
dari sistem lama berupa server fisik IBM X Series 3400 ke Server
(sementara) HP Proliant ML. Server lama menggunakan sistem operasi
openSUSE 11.0 sedangkan server baru menggunakan SUSE Linux Enterprise
Server (SLES) 11 JeOS yang menjadi Xen Hypervisor Guest. Sistem fisik
dari HP Proliant ML ini menggunakan SLES 11 yang dioptimasi untuk
menjadi Xen Hypervisor host.
Mengingat database MySQL Server ini merupakan data yang paling urgent
dan digunakan oleh semua department, saya agak paranoid memindahkannya.
Proses ujicoba dilakukan selama 2 minggu dengan berbagai metode antara
lain :
Proses Dump SQL. Cara ini gagal karena salah satu
program aplikasi yaitu program aplikasi penggajian menggunakan data yang
dienkripsi. Data yang dienkripsi ini menggunakan karakter dan simbol
khusus yang membuat proses dumping menjadi kacau. Daripada satu group
perusahaan nggak gajian lebih baik saya batalkan opsi ini 🙂
Proses Sinkronisasi Database. Proses ini pernah
saya lakukan sewaktu memindahkan data SQL Server ke MySQL namun cara ini
juga tidak saya ambil karena prosesnya lama dan sinkronisasi hanya
berjalan pada tabel, sementara view, stored procedure dan trigger tidak
ikut serta.
Replikasi Database. Metodenya adalah menggunakan
model master & slave. Setiap perubahan data pada database master
akan langsung direplikasi ke database slave. Opsi ini tidak saya ambil
karena saya harus mengubah konfigurasi sistem. Opsi ini tetap menjadi
pilihan jika cara lain mengalami kegagalan
Manual Copy. Cara ini saya ambil karena salah satu
staff IT pernah berhasil melakukannya pada salah satu group perusahaan.
Metodenya menggunakan perintah rsync.
Berikut adalah detail proses pemindahan menggunakan sistem manual copy yang saya lakukan :
Siapkan server baru. Install sistem operasi dalam
modus seminimal mungkin, itu sebabnya saya menggunakan SLES dengan basis
JeOS (Just Enough Operating System), yang bahkan lebih minimalis
daripada sekedar install Text Mode
Install package MySQL Database Server di server baru. Saya melakukan instalasi dari DVD SLES 11 menggunakan perintah : zypper in mysql. Instalasi dapat juga dilakukan menggunakan yast
Jalankan Service MySQL Database Server di server baru. Jalankan dengan perintah : service mysql start.
Pada saat pertama kali dijalankan, MySQL akan membuat struktur data
untuk pertama kali. Setelah selesai, matikan kembali service MySQL
tersebut dengan perintah : service mysql stop
Shut down Service MySQL Induk. Kebetulan pada hari
Minggu malam tidak ada jadwal kegiatan yang menggunakan database, jadi
saya bisa ssh ke kantor untuk melakukan perintah service mysql stop dan kemudian melakukan rsync data ke server baru.
Salin Data. Saya menggunakan perintah rsync
untuk menyalin seluruh isi folder /var/lib/mysql dan kemudian
memindahkannya ke server baru. Sebagai tindakan berjaga-jaga, saya
menempatkan data ini tidak langsung ke /var/lib/mysql di server baru
melainkan di salah satu sub folder /srv. Sebagai catatan, saya juga menyalin file konfigurasi MySQL server lama yang ada di /etc/my.cnf.
Saat pertama kali mencoba, saya menyalin keseluruhan isi folder namun
ternyata service MySQL tidak dapat dijalankan. Saya mengulang proses
pemindahan namun membiarkan sub folder mysql (yang berisi tabel mysql,
user, hak akses dll) tidak tersentuh. Ternyata cara ini berhasil.
Service MySQL bisa dijalankan dan program aplikasi bisa mengaksesnya,
hanya saja saya perlu melakukan sinkronisasi data user dan hak akses
karena saya tidak menimpa folder data MySQL.
Setelah service MySQL Server berjalan dengan baik, ternyata masih ada
1 masalah tersisa, yaitu user tidak bisa menghapus atau membuat view
dengan pesan : Error code 13. Googling beberapa workaround tanpa hasil,
saya melakukan investigasi permission folder masing-masing database dan
ternyata ada database yang hak akses Read/Writenya dipegang oleh root.
Saya mengubah permission aksesnya dan masalahnya dapat terselesaikan.
Saat ini MySQL database server sudah dipergunakan sebagaimana biasanya.
I wondered about the idea to raise a voip on mikrotik. Who remembers,
in older versions of the routeros there was a module for voip, then it
was cut out, which is a pity. It is no longer possible to raise an
asterisk on the routeros, however there is an opportunity to raise a
virtual router with openwrt in the metarouter mode, from here we will
proceed.
Long searches led me to the openwrt.wk.cz
website (available only via ipv6), from where the openwrt image for
mt-mips was downloaded. All experiments conducted on the 2011UAS-2HnD.
Since not everyone has ipv6, I made a mirror for installing packages
from it ( ms1.nserver.us/openwrt.wk.cz
.), Where the necessary packages lie. By the way, during the search,
it was not possible to find a full-fledged article on this topic, not
only in Russian, but also in any other.
So, download the image for mips ( openwrt-mr-mips-rootfs.tar.gz ) or for ppc ( openwrt-mr-ppc-rootfs.tar.gz
). Fill the image in our mikrotik, in Files, go to MetaROUTER and do
the import of the image. I allocated 48 meters of memory and 24 meters
of hdd, yes ... yes ... do not be surprised ... an asterisk will work on
such hardware, tested, created trunks and made calls without problems.
We add the interface to the virtual router, the easiest way is to create
a dynamic one and add it to your local bridge. It looks like this to
me:
in the preinstalled image, the network interface is configured to
receive network settings via dhcp, and if you have everything in order
with the localhost, the virtual router will get the network address, if
not, edit the / etc / config / network file and restart the network.
Next, go to the console:
change the password to root, and see what address is received. All subsequent actions are best done by connecting via ssh.
Having connected via ssh, first edit /etc/opkg.conf, bringing it to the following form for mips:
edit /etc/asterisk/manager.conf, change the admin password to the panel and start the asterisk
/etc/init.d/asterisk start
that's all, now you can go to metarouter_address
: 8088 / and set up an asterisk through the GUI. Present codecs alaw,
ulaw, gsm. If you need to add codecs, look at the list of existing
packages and install the necessary one via opkg. Ready packages under
1.8 asterisk a decent amount, up to chan_dahdi. For home use quite
tolerably can work.
Everything was done as an experiment, although in principle, it could
work for the house, and you can not install the GUI for an asterisk.
PS: I understand perfectly well that this is a perversion, but I wanted to share such an experiment.
Why is it needed? Any high end and most advanced infrastructure equipment have to work on electricity basically so no matter how niche the equipment it, proper power management system is very important for the equipment to function well and as expected. If the power solution is not designed properly there might be outages in the network due to power fluctuation. Generally the power that comes in from the Grid comes as AC. For that to be suitable to the IT equipment in our data centers, we need DC power. We also need backup power generation mechanism in case the grid fails. For all this we need a very good UPS and it should be able to take over instantly.
Our power management system is so advanced that it manages and monitors the UPS installed and we have also got systems that manage power rack wise separately. These solutions are so resilient that you will not feel a pinch even if the entire grid goes down for over 24 hours. So you can relax and sit back once you have installed and setup our solution.
We are partnered with product manufacturers like Emerson (Liebert), APC (Schneider) and CyberPower for the power management equipment like UPS, generators and other supporting equipment.
The Components Desktop and Workstation UPS
The need for a UPS is very high and critical for desktops as compared to a laptop as the desktop don’t have inbuilt power management system for a backup if in case the main power supply switches off due to some unexpected reason. So if the power goes off and there is no backup power, the data that is not saved while an associate is working would be lost and it might also cause a big monetary loss to the business based on the kind of data being processed. Hence Desktop UPS helps protecting data at a workstation level and we can use this solution either if we want some machines to have an extra backup in a huge infrastructure or we have small business and we don’t need a network level UPS.
Rack Mount UPS
Rack Mount UPS are majorly used in Datacenters where certain racks need special attention as they might be hosting the most critical business data and the uptime expected for such server is comparatively higher than the other servers. The key features of a Rack Mount UPS are :
Line Interactive technology Higher AC input range Protects the rack from voltage fluctuations, short circuit and overcharging of batteries. These UPS are also compatible with generators mostly.
So all these features and the requirement of the business calls for a rack mount UPS at the correct places just to be sure that there is a backup mechanism when the main UPS fails.
Network UPS
Network UPS is generally used in a Non rack environment and the best solution when you have a lot of scattered equipment and have to supply backup power to all the equipment from a single point. It provides power to all the equipment ranging from desktops, servers, routers, firewalls and other IT equipment. APC Smart UPS, Liebert GXT series and there are few more excellent network UPS.
The key features of Network UPS are:
Single or multiple phase online UPS Easy installation Centralized management of power to the entire system Provides generator’s capability Wider range of input voltage
All these rich features make the Network UPS a perfect option where we don’t have the rack environment and still looking to provide backup power as well as DC power to the equipment.
Battery Monitoring System (BMS)
Battery Monitoring System monitors the voltage, temperature, charge status, health status, coolant flow and current in the battery. So a good battery monitoring system means better management. Our solution integrates a battery monitoring system in the power management so that the engineers are aware when a battery is about to fail or malfunctions. This also helps them take proactive measures and in timely maintenance as we know the status of the batteries any time and we can act accordingly if required.
UPS Monitoring System
A UPS monitoring system collects the data from UPS and also generates alarms whenever the UPS starts to malfunction. The systems can also connect over TCP/ IP remotely now so it can be a remote monitoring system too hence one system can monitor multiple UPS. Our solution also provides UPS monitoring system as a part of power management solution.
Large Facility UPS
A large Facility UPS is nothing but mother of all UPS to put it in simplest termsJ. Now to get to the technical part of it, it has capacity to manage the whole datacenter from a single set of equipment. However for resilience dual UPS solution is recommended so that if one fails another can takeover. These UPS provide power up to the range of Mega Watt and generally directly connected to the Grid and based on the requirement and the budget we can connect them to the main power line coming into the Data Center.
These are usually deployed in Huge Data Centers or big corporate offices where the users work on hundreds of machines simultaneously and to provide backup to them we need larger devices.
So as we saw the power management systems are the same old systems anymore. These are highly advanced, reliable and improved power management systems that also provide proactive monitoring and diagnosis of the power equipment we use in the environment. Source : http://aboveinfranet.com/solutions/it-infrastructure-company/power-management-ac-power-ups/
