Pandora: Pandora Migration 6.0 to 7.0

From Pandora FMS Wiki
Jump to: navigation, search

1 Quick guide to migrate features from Pandora FMS 6.0 to version 7.0

Some of the major features that have been changed in version 7.0 NG, as well as the actions to be carried out are these:

1.1 Network Maps

In Pandora FMS 7.0 NG, the classic network maps have been improved and updated. This means that all the previous network maps will be lost during migration and they must be created once again. In the new version, you may link the union between different monitored device interfaces.

Mig1.JPG
Mig2.JPG

These connections must be configured via the network recon itself, but in case it is not executed, and you have to set the connections manually, it can be done like this:

Mig3.JPG

1.2 L2 Recon tasks

The standard Recon task (Network sweep) includes the function that was carried out by the custom SNMP L2 Recon script. This script will still work on version 7.0 NG after version migration, although the embedded changes within Network Sweep mode that improve interface links between different network devices will not be incorporated into the SNMP L2 Recon script.

Mig4.JPG

1.3 Renaming agents

This is a feature that clients have been requesting. In previous versions this change had to be performed on the console and the config file, making it a tedious task depending on the number of elements to be modified.

To solve this problem a new element known as Alias has been developed. From now on, two elements will coexist when naming an agent, the name as sole identifier and the alias.

Mig5.JPG

On installations migrated from version 6 to version 7, this element remains the same:

Mig6.JPG

From now on, if you want to modify the visible agent name, just modify the Alias to see it displayed on all views:

Mig7.JPG
Mig8.JPG

Agent name calculation on agents created from now on on version 7.0NG will be done through a set of random sentences. That means that if there are two machines with the same hostname, there will be two agents with different agent names but the same Alias on Pandora FMS console.

If you wish to avoid this situation (e.g., if the agent software and vmware plugin is installed in the Pandora FMS environment on VMs and you wish to have the data from both sources on the same logic agent) you may indicate the agent to behave as in previous versions and create an agent with the same Alias and agent Name. To do this, enter the following parameters in the agent software's config file:


#agent_name 5fa9bdc9ad26a4d0e87d0f0d15ed786c3bd487441b2d5e8d7c42b90e8389797d
#agent_name_cmd __rand__

That way, the agent will be created with the same name as always, and with the information received from both sources. You may still change the alias from the console if necessary and the information will appear as usual.

In case you update the agent or satellite servers the config files in use need to be saved, if not, and they are deleted, a new randomly-labeled agent will be generated and the stored history data will be lost, unless the two parameters above are entered in the new configuration.

1.4 New Pandora FMS agents

The default information Pandora FMS agents report from now on has been changed and unified in Pandora FMS 7.0 NG version.

These are the new modules that will generate reports:

Linux agent

Mig9.JPG


Windows agent

Mig10.JPG


Agents will keep the same configuration in their modules after migration, provided it is not a new agent. Modules included in version 7.0 will not be added automatically.

Here is the configuration you have to add in the above mentioned case:

Linux agent

# Could change depending on linux distro and vmstat command version
module_begin
module_name CPU Load
module_type generic_data
module_interval 1
module_exec vmstat 1 2 | tail -1 | awk '{ print $13 }'
module_max 100
module_min 0
module_description User CPU Usage (%)
module_min_warning 70
module_max_warning 90
module_min_critical 91
module_max_critical 100
module_unit %
module_group System
module_end

# Could change depending on linux distro and vmstat command version
module_begin
module_name CPU IOWait
module_type generic_data
module_interval 1
module_exec vmstat 1 2 | tail -1 | awk '{ print $16 }'
module_min_warning 10
module_min_critical 16
module_unit %
module_description Too much IOwait means IO bottleneck and performance problems. Check also LoadAVG.
module_group System
module_end

# Get load average
module_begin
module_name Load Average
module_type generic_data
module_exec cat /proc/loadavg | cut -d -f1
module_description Average process in CPU (Last minute)
module_group System
module_end

# Basic info about TCP Connection
module_begin
module_name TCP_Connections
module_type generic_data
module_exec netstat -an | grep tcp | grep -v LIST | wc -l
module_description Total number of TCP connections active
module_group Networking
module_end

# This plugin detects all disk and report used space (%)
module_plugin pandora_df_used
# This plugin detects system free memory and used swap (in %)
module_plugin pandora_mem_used
# This plugin will get the network usage (bytes/sec)
module_plugin pandora_netusage

Windows agent

# CPU Load using WMI 
module_begin
module_name CPU Load
module_type generic_data
module_wmiquery SELECT LoadPercentage FROM Win32_Processor
module_wmicolumn LoadPercentage
module_max 100
module_min 0
module_description User CPU Usage (%)
module_min_warning 70
module_max_warning 90
module_min_critical 91
module_max_critical 100
module_unit %
module_group System
module_end

# Basic info about TCP Connection
module_begin
module_name TCP_Connections
module_type generic_data 
module_exec netstat -an | find /c /v "estab"
module_description Total number of TCP connections active
module_group Networking
module_end

# Example plugin to retrieve drive usage
module_plugin cscript.exe //B "%ProgramFiles%\Pandora_Agent\util\df_percent_used.vbs"

# Example plugin to retrieve memory usage
module_plugin cscript.exe //B "%ProgramFiles%\Pandora_Agent\util\mem_percent_used.vbs"

# Example plugin to retrieve network usage
module_plugin cscript.exe //B "%ProgramFiles%\Pandora_Agent\util\network.vbs"

1.5 Update Manager / Rolling Release

Pandora FMS 0.7 NG enables users to make database changes thanks to OUM packets that are subsequently distributed. Go to the Update Manager Online or Offline section, depending whether there is a connection or not.

Template warning.png

Offline updating is only available in Pandora FMS Enterprise versions.

 



1.5.1 Update Manager Online

Go to this section via Update Manager > Update Manager Online.

Mig11.JPG

If you are installing a new version, a message like this will appear:

Mig12.JPG

Click “Update to the latest version”:

Mig13.JPG

When the update is accepted, the following package is downloaded and applied. If the package also contains database changes, the following message will appear before the changes are applied in order for the database to be backed up and ensure that, in case of error when applying new scripts, the previous database status is recoverable.

Mig14.JPG

When MR is applied, the database changes are made and once the process has finished, the updated and applied version should appear:

Mig15.JPG

1.5.2 Update Manager Offline

Template warning.png

Offline updating is only available in Pandora FMS Enterprise versions.

 


To access this section, go to Update Manager > Update Manager Online.

Mig16.JPG

Upload the package in the appearing option:

Mig17.JPG

Once the package is applied, the following message will appear:

Mig18.JPG

If the package implies database changes, these are applied and the following message will appear when it is finished:

Mig19.JPG

To find out which version you are using, a new field has been added at the console footer that tells you which MR or database version it is, and whether the changes have been applied:

Mig20.JPG

1.6 New alert templates

New templates have been added for this release:

Mig21.JPG

They come installed on Pandora FMS 7.0 NG, but migrations from previous versions will not be applied, to respect previous configurations.

1.7 Interface monitoring nomenclature

Monitoring nomenclature by which network interface monitoring modules are currently created has been modified, so that their information can be easily sorted out by their interface name.

The following nomenclature was used in previous versions:

Mig22.JPG

This is the new format:

Mig23.JPG

In order to fully take advantage of Pandora FMS 7.0 NG's new features on Enterprise maps, interface graphs, etc., modify module names through the following SQL queries:

UPDATE tagente_modulo SET nombre = CONCAT(REPLACE(nombre, 'ifOperStatus_', ), '_ifOperStatus') WHERE nombre LIKE('ifOperStatus_%');
UPDATE tagente_modulo SET nombre = CONCAT(REPLACE(nombre, 'ifInOctets_', ), '_ifInOctets') WHERE nombre LIKE('ifInOctets_%'); 
UPDATE tagente_modulo SET nombre = CONCAT(REPLACE(nombre, 'ifOutOctets_', ), '_ifOutOctets') WHERE nombre LIKE('ifOutOctets_%');

To configure satellite server modules manually in the configuration file, the modules must be renamed in the satellite configuration files (NOTE: if remote configuration is enabled, update them on the server, and modify the .md5, or delete them from the server, rename them on the satellite and resent them).

Execute this from the server in case remote configuration is disabled:

sed -i -e 's/ifOperStatus_\(.*\)/\1_ifOperStatus/' /etc/pandora/conf/*.conf 
sed -i -e 's/ifInOctets_\(.*\)/\1_ifInOctets/' /etc/pandora/conf/*.conf 
sed -i -e 's/ifOutOctets_\(.*\)/\1_ifOutOctets/' /etc/pandora/conf/*.conf
sed -i -e 's/ifOperStatus_\(.*\)/\1_ifOperStatus/' /var/spool/pandora/data_in/conf/*.conf 
sed -i -e 's/ifInOctets_\(.*\)/\1_ifInOctets/' /var/spool/pandora/data_in/conf/*.conf 
sed -i -e 's/ifOutOctets_\(.*\)/\1_ifOutOctets/' /var/spool/pandora/data_in/conf/*.conf

After applying these changes, apply them on the satellite server config. To do this, modify the .md5 file on each agent by inputting a random value on each one of them.


echo 1 >/var/spool/pandora/data_in/md5/*.md5