Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Check entry point connectivity

Log in to subscribe to topics and get notified when content changes.

Check entry point connectivity

A service deployment owner or an application owner tests that Service Mapping can connect to the devices that are expected to make up this business service. This feature is not available on instances using Edge Encryption.

Before you begin

Run either horizontal or top-down discovery on the host for which you want to check connectivity.

Role required: sm_admin or sm_app_owner

About this task

Fresh install deployments do not have the Service Map Planner module. The improved planning functionality is provided as an integral part of the new Service Mapping user interface. For more information, see KB0689681: Features replacing deprecated Service Planner in Service Mapping.

You can check if Service Mapping can connect to hosts to identify any connectivity-related issues. You can investigate the problem source, fix it, and run the connectivity check again to verify that you are ready to create an actual business service. The most common causes of connectivity problems are missing or wrong credentials for a host.

You can check connectivity of entry points you defined for a planned business service. An entry point is the way clients access a business service. Service Mapping starts the mapping process from this point. You can also check connectivity of hosts connected to specified entry points.

As part of defining entry points for a business service, you enter their IP addresses. When you run this test, Service Mapping checks the corresponding record in the CMDB [cmdb_ci] for information on credentials for IP addresses you defined. By default, Service Mapping checks the IP address that you defined for the entry point, but you can add additional ID addresses during the procedure.

To check connectivity of hosts connected to entry point IP addresses, you must specify the number of levels to check as Hop Count. Service Mapping uses information on TCP and Netflow connections stored in the CMDB tables, to find hosts connected to the IP address.
Table 1. Tables containing data collected using traffic-based methods
Table Source Used by Service Mapping to
Flow Connection [sa_flow_connection] Netflow and VCP logs Discover dependencies, add connections during top-down discovery.
TCP Connection [cmdb_tcp] netstat and lsof commands Discover connections during top-down discovery.


  1. Navigate to Service Mapping > Service Map Planner > Phases.
  2. Select the phase which contains the planned business service.
  3. Click the name of the planned business service.
  4. On the Planned Entry Points tab, click the check boxes next to the entry points whose credentials you want to check.
  5. Click Check Connectivity.
    The Check IP Address Connectivity window opens displaying the IP address you defined for the entry points.
  6. If necessary, modify or add IP addresses in the IP Address(es) field.
    Use comma without whitespace to separate multiple IP addresses.
  7. Select the number of levels to check in the Hop Count list.
    The number of hops performed by the actual test depends on the ability of Service Mapping to connect to hosts in the next level. If you use Netflow to collect data, you can see CIs on all levels even if Service Mapping cannot connect to them.
  8. Click OK.
    The Connectivity Test page opens.
  9. Verify that the status of the test is Completed.
  10. Review the result of the test:
    • If the status and the message state that the IP address is found, Service Mapping can connect to this host.

    • If the status is Info, there is a possibility that there is a connectivity problem or that this host is not in the CMDB.
    • If the status is Not found, either there is a connectivity problem or this host is not in the CMDB.
  11. Click the IP address to read the full message. Use this information to troubleshoot connectivity issues.
    To troubleshoot, you may need to:
    • Run discovery on a problematic CI either from Discovery or Service Mapping.
    • Define missing or wrong credentials for this CI.
  12. Perform this procedure on the same entry points to verify that Service Mapping does not experience the same connectivity issues.