Pandora: Documentation en: IPAM
1 IPAM Extension
This is an Enterprise feature. With the IPAM extension we can manage the IP of our networks, discover the hosts of a subnet and detect their availability changes (whether they respond to ping or not) or hostname (obtained through dns). We can also detect their operating system. The IPAM extension uses a recon script (dependent on the recon server) to perform all the logic underneath. The management of IP's is independent of whether or not it has agents installed on those machines or an agent with remote monitors on that IP. You can optionally "associate" an agent to the IP and manage that IP, but it does not affect the monitoring you are doing.
1.1 IPs Detection
We can configure a network (via a network and a network mask) so that the recognition of your addresses is executed automatically from time to time or only manually. This mechanism uses the recon server, but manages it automatically. For its correct operation it is important to make sure that you have the xprobe and fping packages installed. In case of having any doubt, you can check the documentation about installing Pandora FMS for more details about that aspect.
1.2 IPs with installed agents
The first time you detect the network, after creating it in the IPAM control panel, Pandora will look for the IPs of that network. If it detects that the IP is operational, it will manage it. If it doesn't respond to ping, it'll leave it unmanaged. Any managed IP that changes state (stop responding to ping) will generate an event in the system. You can manually manage as many IPs as you want, editing them to give you an alias/hostname, a description or even force their operating system.
Special mention should be made of the fact that when IPAM detects an IP that has a software agent installed and has that IP assigned to it, it makes it possible to identify it explicitly, as in the case of ip 70.125 of this screenshot:
And if we click on the detail view of the agent:
Network IP addresses administration and operation are splitted in two views: icon views and edition view.
1.3.1 Icon view
This view reports information on the network, including stats on the percentage and number of occupied IP addresses (only for 'managed' addresses). We can also export to Excel/CSV the filtered list.
Addresses will be shown as icons, large or small. This icons will render the following information:
From version 5.1 SP1, if the IP is reserved it will have a light blue background, and if it's not, the background color will be white.
Each IP address has in the bottom right position a link to edit it (with administration rights). In the bottom left position, there is a small icon showing the detected OS. On disabled addresses, instead the OS icon, you will see this icon:
When you click on the main icon, a modal window will be opened showing all the IP information, including associated agent and OS, setup for that IP and other information, like creation date, last user edition or last time it was checked by server. In this view you can also do a manual, realtime check to see if that IP respond to ping.
From 5.1 SP1 version
Also, for the easy management of the free IP's, there is a button that will show a dialogue box with the next free IP to reserve or manage.
1.3.2 Edit view
If you have enough permission, you will have access to setup view, where IP address are shown as a list. You can filter to show only the IP's you are interested into, make changes on them and update all of them at once.
Some fields, are automatically filled by the recon script, like hostname, if it have a Pandora FMS agent and the operating system. You can mark that fields as "manual" and edit them.
Other fields you can modify are: - Activate events on an IP address. When availability on this address change (answer or stop to answer) or the hostname change, a new event will be generated.
When an address is created, it always will generate an event.
- Mark as managed an IP Address. This address are those we will acknowledge as assigned in our network and managed in the system. We will be able to filter the IPs to show only those that we have marked as managed.
- Disable. Disabled IP addresses are not checked by the recon script.
- Comments. A free field to add comments on each address.
1.4 Massive operations view
There is another tab to manage the IPs in a massive way, helping the user with the management of big groups of IPs.
On both views you can sort by IP, Hostname and by the last update.
You can filter by a text substring, which will match in IP, hostname or comments of each IP in the system. Enabling the checkbox near to search box, it will force an exact match by IP.
By default, not responding hosts are not shown, but you can change the filter.
You can also show only the managed IP addresses.
1.6 Subnetwork calculator
IPAM includes a tool to calculate IPv4 and IPv6 subnetworks.
In this tool, you can, using an IP address and a netmask, obtain the information of that network:
- Network (Address/Bitmask)
- The Wildcard mask
- The network Address
- Broadcast Address
- First valid IP
- Last valid IP
- Number of IPs in the network
These fields are given in address format (decimal for IPv4 and hexadecimal for IPv6) and binary format.
1.7 Users ACL
When configuring any network, by default in previous installations of the system, all the users will have total access to the IPAM tool, but now, you can define a list of users who can manage the network. All the users with administrator permissions can access all the networks.
1.8 Recon task creation
The IPAM module uses the Recon Server subsystem underneath. The IPAM-type tasks that we can see on the recon server are created by the IPAM module and should not be "manually" created or deleted.