The installations of the Instances and the Command Center (Metaconsole) must be hosted on servers that are connected in both directions.
The Instances do not need to communicate with each other at any time, for more details see Command Center Architecture.
Version NG 755 or earlier: you must configure the use of Command Center , you have all the relevant information there.
An Instance or node is a typical Pandora FMS installation, composed of a server and a Web Console.
A Command Center is an installation of Pandora FMS with a Command Center license.
You cannot use the Pandora FMS console and the Command Center at the same time.
It is necessary to have a server active to be able to carry out different operations related to the Command Center, such as “migration”, “self-provisioning”, execution of services, etc.
After activate the license of the Pandora FMS console, whatever the installation method, you must access the Pandora FMS console:
http://<dir_IP_or_URL>/pandora_console/
A welcome screen will appear to accept the license.
In order to activate the Command Center a Command Center license is required. If you activate the node license, the normal console will appear.
Starting with version 7.0 NG of Pandora FMS, a single license is available for an environment with Command Center. You can create as many Instances as you want, as long as the total number of agents within the Command Center is not exceeded.
This license is applied in the Command Center and can be synchronized in as many Instances as desired, thus allowing centralized management of the different agents that will be deployed in said Instances.
If nodes are needed that can remain disconnected from the Command Center for long periods of time, contact the Pandora FMS team.
In the Metasetup section, you can register and configure the Instances with which the Command Center will be linked.
To register a new Instance we must know a series of parameters regarding the Instance we want to manage. If it is the registration of an Instance that has not yet been registered with a license, the default data is:
http://<dir_IP_orURL>/pandora_console
Advanced fields
To guarantee connectivity between node and Command Center, we can manually configure the connection data.
pandora
pandora
pandora
3306
These fields indicate the configuration of the connection that the node will establish against the Command Center.
If it is a Pandora FMS installation where we have already includedor a valid license in the Instance, we will have to obtain said data from the setup of the Instance and its database.
In the view of the configured Instances we will see that the Instances can be modified, deactivated and deleted. There are some indicators that check certain information about the configuration of each Instance. These checks are performed when loading this view, but they can also be done individually by clicking on them.
The indicators are the following:
The first three indicators must appear green so that the Instance is properly linked and we begin to see its data. On the other hand, the Event Replication indicator only gives us information about this characteristic.
If database encryption is enabled, all nodes and the Command Center must use the same encryption_passphrase
configuration.
Version NG 755 or earlier: you must configure the use of Command Center, you have all the relevant information there.
The server packages must be installed on the system where the Command Center is installed in order to launch the Database maintenance script (pandora_db). You must ensure that it is correctly scheduled to run in cron every hour (as detailed in the following link.).
If you are going to use on-demand reports (sent by email), you need to schedule the cron extension to run just like you do in a console. Generally, this is done by putting the following line in the cron, adjusting the corresponding local paths:
/5 * * * * <user> wget -q -O - http://x.x.x.x/pandora_console/enterprise/extensions/cron/cron.php>> /var/www/pandora_console/log/console.log
For versions prior to 747 the route will be:
/var/www/pandora_console/pandora_console.log
Finally, to configure the SMTP for sending emails, you must edit the corresponding parameters in the email configuration section.
Access to the Instance API will be guaranteed with the following parameters:
In some parts of the Command Center there are accesses to the Instance Web Console; For example, in the event viewer, clicking on the agent associated with an event (if any) will take you to the view of that agent in the console of the Instance it belongs to.
For this type of access self-authentication is used. This authentication is performed by activating the token Setup → General setup → Auto login in node.
To configure the Command Center go to Setup → Metasetup.
Version NG 763 or later.
By possessing a valid Command Center license and having access to the internet, you will be able to update the Command Center automatically. This section will only be visible if Enable Warp Update is activated in General Settings.
Version NG 763 or later.
Offline patching may render your console unusable, it is recommended that you make a full backup of all files before applying any patches.
Click on the Warp Update Journal icon to see the updates made, version, date and time of application, user who requested and applied it, etc. This section will only be visible if Enable Warp Update is activated in General Settings.
Over time, you will accumulate many records which you can filter by expanding the Filter box and entering the keyword to search for.
Version NG 763 or later.
By default it is already configured to be able to update online. This section will only be visible if Enable Warp Update is activated in General Settings.
Please contact support before changing any of the following fields:
In Pandora FMS there is a system for monitoring the status of the console and the system in general.
In this configuration, a series of values must be established such as:
SSL
, SSLv2
, SSLv3
, STARTTLS
.You can make your custom translations (String translation icon) even with macro variables; This extension is fully described in the Translate string section.
File manager where images of the Command Center installation can be uploaded and deleted from the files in the folder.
The Command Center code reuses some images from the regular console code. These images will not be accessible from this manager and it will be necessary to access the installation manually to manage them.
All configuration related to data representation. Colors and resolution of the graphics, number of elements in the views pagination, etc. There is more information about visual settings in this link.
To learn more about authentication, visit the section Authentification.
Allows you to activate the use of the historical database in the Command Center (Enable historical database). To learn more about historical database setup visit Console Setup.
From version 774 of Pandora FMS the access configuration is incorporated to the OpenSearch.
A password policy can be established with limitations on the number of characters in passwords, expiration, temporary blocking of a user. To learn more about the password policy, visit the section Password policy.
In this section you will find general Command Center data such as the language, date/time settings or the customization of certain sections, among others.
They can be customized if we want the NetFlow sections, the tree view classified by tags, the visual console or the possibility of creating web checks from the Wizard to be activated or deactivated.
Notable fields:
public_url
.