If your network uses load balancers running on Linux hosts, create a discovery
behavior to ensure that Service Mapping
and Discovery discover them
correctly.
Before you begin
Make sure that Discovery is
activated.
Role required: sm_admin or admin
About this task
The discovery and mapping process begins with Discovery identifying the
host. After the host discovery is complete, Service Mapping starts
discovering and mapping applications running on this host.
The default discovery process identifies a configuration item (CI) as a Linux server
if it finds an SSH port in use. It may lead to incorrect discovery of load balancers
running on Linux as Linux servers. Create a discovery behavior to first discover
network devices using SNMP protocol. After Discovery has discovered
Unix-based load balancers correctly and created the appropriate CIs for them, you
can continue with discovering and mapping application services in Service Mapping.
Discovery performs discovery
through a
MID Server located in
the enterprise private network. A behavior determines:
- What MID Server Discovery is
using.
- What probes and patterns the chosen the MID Server is
running.
Procedure
-
Create a new behavior for discovering Unix-based load balancers:
-
Navigate to .
-
Click New.
-
Enter the name for this behavior.
-
Right-click on the header bar and click
Save.
-
Click New on the Discovery
Functionality tab.
-
Enter 1 in the Phase field.
-
Select SNMP only from the
Functionality definition list.
-
Select the relevant MID Servers in the
MID Servers area.
-
Check the Active check box.
-
Click Submit.
-
Create a discovery schedule for the newly defined behavior:
-
Navigate to .
-
Click New.
-
Fill in the fields as follows:
Table 1. Discovery Schedule Form for Discovery
| Field |
Description |
| Name |
Enter a unique, descriptive name for your schedule. |
| Discover |
Select Configuration
items. |
| MID Server selection method |
Select Use
behavior. |
| Behavior |
Select the behavior you created in step 1. |
| Active |
Select the check box to enable this schedule. If you clear the check box, the schedule is disabled, but you can still run a discovery manually from this form, using the configured
values. |
| Max run time |
Set a time limit for running this schedule. When the configured time elapses, the remaining tasks for the discovery are canceled, even if the scan is not complete. Use this field to limit
system load to a desirable time window. If no value is entered in this field, this schedule runs until complete. |
| Run and related fields |
Determines the run schedule of the discovery. Configure the frequency in the Run field and the other fields that appear to specify an exact time. Note: The run time
always uses the system time zone. If you add the optional Run as tz field, it has no effect on the actual runtime. |
-
Create an IP range for the discovery schedule:
Important: The IP range for the schedule must
correlate with the IP range of the MID Server that you
assigned to the behavior. The MID Server must also
have the appropriate application or the ALL
application.
-
On the Discovery IP Ranges tab, click New.
-
Enter the name for this IP range.
-
Configure the IP range by entering IP addresses in the
Starting IP and Ending
IP fields.
-
Click Submit.