2009-08-24 Miguel de Dios <miguel.dedios@artica.es>
* include/functions_menu.php, include/functions_html.php,
include/functions_events.php, include/functions_messages.php,
include/functions_modules.php, include/functions_exportserver.php,
include/functions_reporting.php, include/functions_filemanager.php,
include/pchart_graph.php, include/pandora_graph.php, include/auth/dev.php,
include/auth/ldap.php, include/auth/mysql.php, include/config.inc.php,
include/functions_networkmap.php, include/functions_servers.php,
include/FusionCharts/FusionCharts_Gen.php,
include/FusionCharts/FusionCharts.php,
include/functions_network_profiles.php, include/gettext.php,
include/functions_network_components.php, include/functions_visual_map.php,
include/fgraph2.php, include/Image/image_functions.php,
include/functions_config.php, include/help/en/help_plugin_parameters.php,
include/help/en/help_snmpcommunity.php, include/help/en/help_wmiquery.php,
include/help/en/help_postprocess.php,
include/help/en/help_prediction_source_module.php,
include/help/en/help_date_format.php, include/help/en/help_recontask.php,
include/help/en/help_alert-matches.php, include/help/en/help_tcp_send.php,
include/help/en/help_wmifield.php, include/help/en/help_duplicateconfig.php,
include/help/en/help_agent_status.php,
include/help/en/help_manage_alerts.php, include/help/en/help_wmikey.php,
include/help/en/help_alert_type.php,
include/help/en/help_network_component.php,
include/help/en/help_time_stamp-comparation.php,
include/help/en/help_eventview.php, include/help/en/help_timesource.php,
include/help/en/help_alert_validation.php,
include/help/en/help_map_builder.php,
include/help/en/help_alert_recovery.php,
include/help/en/help_module_type.php,
include/help/en/help_planned_downtime.php,
include/help/en/help_serverlag.php, include/help/en/help_alerts.php,
include/help/en/help_snmpwalk.php,
include/help/en/help_module_definition.php,
include/help/en/help_plugin_definition.php,
include/help/en/help_wminamespace.php, include/help/en/help_snmpoid.php
include/help/en/help_manageconfig.php,
include/help/es/help_alert_validation.php,
include/help/es/help_plugin_parameters.php,
include/help/es/help_snmpcommunity.php, include/help/es/help_wmiquery.php,
include/help/es/help_map_builder.php, include/help/es/help_postprocess.php,
include/help/es/help_date_format.php,
include/help/es/help_alert_recovery.php,
include/help/es/help_prediction_source_module.php,
include/help/es/help_module_type.php,
include/help/es/help_planned_downtime.php,
include/help/es/help_alert-matches.php, include/help/es/help_recontask.php,
include/help/es/help_alerts.php, include/help/es/help_serverlag.php,
include/help/es/help_snmpwalk.php,
include/help/es/help_module_definition.php,
include/help/es/help_tcp_send.php, include/help/es/help_duplicateconfig.php,
include/help/es/help_wmifield.php, include/help/es/help_manage_alerts.php,
include/help/es/help_wmikey.php, include/help/es/help_plugin_definition.php,
include/help/es/help_alert_type.php, include/help/es/help_snmpoid.php,
include/help/es/help_wminamespace.php,
include/help/es/help_network_component.php,
include/help/es/help_time_stamp-comparation.php,
include/help/es/help_manageconfig.php, include/help/es/help_timesource.php,
include/config_process.php, include/functions_ui.php, include/htmlawed.php,
include/functions_custom_graphs.php, include/fgraph.php,
include/functions_incidents.php, include/functions.php,
include/functions_agents.php, include/functions_db.php,
include/functions_themes.php, include/streams.php,
include/functions_fsgraph.php, include/functions_alerts.php,
include/functions_reports.php, include/functions_extensions.php,
include/functions_ui_renders.php: change comments blocks for delete the
warnings to construct phpDoc Files, give a struct and order in the
phpDoc files.
git-svn-id: https://svn.code.sf.net/p/pandora/code/trunk@1881 c3f86ba8-e40f-0410-aaad-9ba5e7f4b01f
2009-08-25 19:39:28 +02:00
|
|
|
<?php
|
|
|
|
/**
|
|
|
|
* @package Include/help/en
|
|
|
|
*/
|
|
|
|
?>
|
2013-04-04 16:22:26 +02:00
|
|
|
<h1>Recon Tasks </h1>
|
|
|
|
|
|
|
|
If you choose to edit or create a new task of network recon, then you should fill in the required fields in order the task could be processed properly. <br><br>
|
|
|
|
|
|
|
|
<b>Task name</b><br>
|
|
|
|
|
|
|
|
Name of the discovery task. It's only a descriptive value to could distinguish the task in case it would have several of them with different values of filter or template. <br><br>
|
|
|
|
|
|
|
|
<b>Recon server</b><br>
|
|
|
|
|
|
|
|
Recon Server assigned to the task. If you have several Recon Servers, then you have to select here which of them you want to do the recon task. <br><br>
|
|
|
|
|
|
|
|
<b>Mode</b><br>
|
|
|
|
|
|
|
|
Task Mode to choose between "Network Scanning" and "Script Custom". The first mode is the conventional network recognition task, and the second is the manner in which the task is associated with a custom script<br><br>
|
|
|
|
|
|
|
|
<b>Network</b><br>
|
|
|
|
|
|
|
|
Network where you want to do the recognition. Use the network format/ bits mask. <b>CIDR</b>. For example 192.168.1.0/24 is a class C that includes the 192.168.1.0 to 192.168.1.255 adress. <br><br>
|
|
|
|
|
|
|
|
<b>Interval</b>
|
|
|
|
<br>
|
|
|
|
Repetition interval of systems search. Do not use intervals very shorts so Recon explores a network sending one Ping to each address. If you use recon networks very larges (for example a class A) combined with very short intervals (6 hours) you will be doing that Pandora FMS will be always bomb the network with pings, overloading it and also Pandora FMS unnecessarily.<br><br>
|
|
|
|
|
|
|
|
<b>Module template</b><br>
|
|
|
|
|
|
|
|
Plugins template to add to the discovered systems. When it detects a system that fits with the parameters for this task (OS, Ports), it will register it and will assign all the included modules in the defined plugin template. <br><br>
|
|
|
|
|
|
|
|
<b>OS</b><br>
|
|
|
|
|
|
|
|
Operative system to recognize. If you select one instead of any (Any) it will only be added the systems with this operative system.Consider that in some circumstances Pandora FMS can make a mistake when detecting systems, so this kind of "guess" is done with statistic patterns, that depending on some other factors could fail (networks with filters, security software, modified versions of the systems).To could use this method with security, you should have installed Xprobe2 in your system. <br><br>
|
|
|
|
|
|
|
|
<b>Ports</b><br>
|
|
|
|
|
|
|
|
Define some specific ports or an specific range, e.g: 22,23,21,80-90,443,8080.If you use this field,only the detected hosts that will have at least one of the ports here mentioned will be detected and added to the system. If one host is detected but it has not at least one of the ports opened, then it will be ignored. This, along with the filter by OS kind allows to detect the systems that are interesting for us,e.g: detecting that it is a router because it has the ports 23 and 57 opened and the system detect it as a "BSD" kind. <br><br>
|
|
|
|
|
|
|
|
<b>Group</b><br>
|
|
|
|
|
|
|
|
It is the group where we should add the discovered systems. It will must assign the new systems to one group. If it has already one specific group to locate the unclassified agents, then it could be a good idea to assign it there. <br><br>
|
|
|
|
|
|
|
|
<b>Incident</b><br>
|
|
|
|
|
|
|
|
Shows if by discovering new systems it create an incident or not. It will create one incident by task, not one for detected machine,summarizing all the detected new systems, and it will create it automatically in the group previously defined. <br><br>
|
|
|
|
|
|
|
|
<b>SNMP Default community</b><br>
|
|
|
|
|
|
|
|
Default SNMP community to use to discover the computers.<br><br>
|
|
|
|
|
|
|
|
<b>Comments</b><br>
|
|
|
|
|
|
|
|
Comments about discovery network task.<br><br>
|
|
|
|
|
|
|
|
<b>OS detection</b><br>
|
|
|
|
|
|
|
|
When choosing this option the scan will detect the OS.<br><br>
|
|
|
|
|
|
|
|
<b>Name resolution</b><br>
|
|
|
|
|
|
|
|
When choosing this option, the agent will be created with the name the computer, long as it is configured in the equipment, if not create the agent with the IP name.<br><br>
|
|
|
|
|
|
|
|
<b>Parent detection</b><br>
|
|
|
|
|
|
|
|
Selecting this option will detect in exploring whether computers connected to others and created as children.<br><br>
|
|
|
|
|
|
|
|
<b>Parent recursion</b><br>
|
|
|
|
|
|
|
|
Indicates the maximum number of recursion with which agents will be able to generate as parents and children, after scan.<br><br>
|
|
|
|
|
|
|
|
|