Page tree
Skip to end of metadata
Go to start of metadata



1. SNMP and MIBs - Installation and Configuration

To implement the monitoring system, the first step is to install SNMP and MIBs in all the systems to be monitored.

Below is described each system used by each resource in a common island setup:


Sugested hostname

Dom0Debian 7vms
LDAPDebian 7ldap
FlowvisorDebian 7flowvisor
OCFDebian 8ocf
OMFUbuntu 12.04omf
NetFPGA1CentOS 5netfpga1
NetFPGA2CentOS 5netfpga2
NetFPGA3CentOS 5netfpga3
VPN ClientDebian 7vpn

If you have a different setup you have to change this in order to correctly describe your own environment



Download and install the SNMP and MIBs for each one of the systems:

(For Debian systems, is necessary to add the non-free repositories before installation)

Debian systems
nano /etc/apt/sources.list
vim /etc/apt/sources.list 
deb .... main non-free
deb-src .... main non-free
Debian-based systems
apt-get install snmpd -y
apt-get install snmp-mibs-downloader -y
RHEL-based systems
yum install net-snmp -y
yum install net-snmp-utils -y


To configure the SNMP service  in each system, backup and clean the snmpd.conf file:
cd /etc/snmp
cp snmpd.conf snmpd.conf.ori
cat /dev/null > snmpd.conf

And apply the following default configuration:

rocommunity FIBRE-BR
syslocation [Institution, City, UF]
syscontact [E-mail]
agentaddress [SERVER_IP]:161 


  • rocommunity- This field must be filled with FIBRE's default community, which is FIBRE-BR.
  • syslocation - This field should be filled with the server's location. Like the instituion, the state and the city where the infrastructure is located.
  • syscontact - This field should be filled with the sysadmin's e-mail.
  • agentaddress - This field should be completed with the ip address of the FIBRE control network inthe system (10.x.0.y), and port 161.

Example for RNP Dom0:

rocommunity FIBRE-BR
syslocation RNP, Brasília, DF


After finishing the configuration, restart the snmp service:
service snmpd restart

2. Monitoring Agents - Installation and Configuration

To deploy an advanced monitoring of some essencial island resources, a monitoring agent must be installed on them.

Additionally, the current version of the Pronto SW firmware don't support the monitoring agent.

In short, the agent don't need to be installed on the DNS, Perfsonar, and on the Pronto SW.

For each other system, download and install the agent as follows:

Debian 7
dpkg -i zabbix-release_3.0-1+wheezy_all.deb
apt-get update
apt-get install -y zabbix-agent
Debian 8
dpkg -i zabbix-release_3.0-1+jessie_all.deb
apt-get update
apt-get install -y zabbix-agent
Ubuntu 12.04
sudo dpkg -i zabbix-release_2.2-1+precise_all.deb
sudo apt-get update
sudo apt-get install zabbix-agent
CentOS 5+
rpm -ivh zabbix-agent-3.0.4-1.el5.i386.rpm


Edit the agent configuration file for each resource system:

vim /etc/zabbix/zabbix_agentd.conf
# or:
nano /etc/zabbix/zabbix_agentd.conf

And change the according to your environment. The Proxy IP address follow the pattern: 10.[id].0.160:


Server=,,[VMServer IP address],[Proxy IP address]

ServerActive=,,[VMServer IP address],[Proxy IP address]






Save the changes and exit the editor;

Delete a config file that will be substituted:

rm -f /etc/zabbix/zabbix_agentd.d/userparameter_mysql.conf


Download the "etc-zabbix.tar.gz " file from the to the /etc/zabbix/ folder on the agent host and extract it:

cd /etc/zabbix/
tar -zxvf etc-zabbix.tar.gz


For the OCF VM only, is necessary to create a read-only user in the MySQL database:

mysql -u root -p
[mysql pasword]

create database zabbix character set utf8 collate utf8_bin;

grant SELECT on zabbix.* to zabbix@localhost identified by 'zabbixpw';

SELECT User,Host FROM mysql.user;


Finally, and for all nodes, restart the monitoring agent service and enable startup on system initialization:

/etc/init.d/zabbix-agent restart

# or:

service zabbix-agent restart

# For CentOS systems:

chkconfig zabbix-agent on

# For Debian systems:

systemctl enable zabbix-agent
systemctl start zabbix-agent


3. Local Proxy - Installation and Configuration

For this installation, use the template zproxy-template.tar.gz available at this address:

Download it where Xen creates its VMs.

Where does the hypervisor creates its VMs?

To verify where the hypervisor is creating its VMs, verify this file: /etc/xen-tools/xen-tools.conf.

The value of the variable dir is the destiny where the VMs are being created.

cd (directory)/domains


Due to the Island's firewall constraints, it might be necessary to use the internal address to download. In case of need use this address:

And extract it´s contents:

tar zxf zproxy-template170124.tar.gz

And access the directory.

cd zproxy.template


Changing directory name

It might be interesting to change the directory name for this pattern:


After that it's necessary to rename and edit and rename this file: zproxy.template 


It's necessary to edit the following lines:

The variable disk refers where the VM's disk is located. Below is an example of configuration: 

disk = [

Also it's necessary to configure the network, the vif variable is responsible for this task.

Control Bridge name

Pay attention to the name of your control bridge, also it's necessary to change the mac address.

Example of configuration:

vif = [ 'ip=,mac=00:00:0a:00:00:33,bridge=br_control' ]

It's a good practice to use this pattern for MAC address generation:

MAC address:


Where XX stands for the Island's ID and YY stands for the service IP, both in hexadecimal form

The next step of editing the file it's to change the name of the VM.

Edit this line:

name = ''

This edition consists in just replace template to the name of the institution.


name = ''

After editing, move and rename it to /etc/xen:

mv /etc/xen/

And create a symbolic link at the directory called auto:

cd /etc/xen/auto

ln -s ../

The next step is to access the console of the VM:

xm create -c (name of the vm)

To start using the VM use the following credentials:

VM credentials

Login: root

Password: zproxy



4. Related Documents


Below are the documents related to the monitoring solution choosed for the FIBRE NOC Monitoring:

FIBRE 2016-05 - Avaliação Ferramentas de Gerência v1.0.pdf

FIBRE 2016-06 - Novo Monitoramento v1.0.pdf

FIBRE 2017-02 - FIBRE Monitoramento v1.0.pdf


  • No labels