====== Topology Rediscovery Sync Failures ======

Author: Paddy Murphy

This wiki was created to assist if you encounter issues with Topology Rediscovery Sync.


===== Troubleshooting Checklist =====

Run the following query on the Controller been investigated.
    select id, name, technology, assigned_technology_id, ip_address, port, link_down, login_credentials_id, http_session_manager_configuration_id, remote_discovery_configuration_id, software_version from network_element where id = <network  element id>;

  - Verify that you can login into the Controller and successfully reach a landing page with data. Some Controllers can only be accessed through a [[support:tunneling|tunnel]]
  - Is the Controller link down?  [[onboarding:snmpmanager:introduction_to_link_polling_and_types|link down functionality]]
  - Is the software version supported. -- check supported technologies & software versions here [[https://docs.google.com/spreadsheets/d/1MWddwE7AitjY1khgNXU6USs8bVP54W5UKb-Byxps4qo/edit#gid=2021934505 | here]]
  - Are the assigned login credentials correct and not null at the controller level? [[support:login_credentials_for_controllers|Controller Login values]]
  - Is the correct IP address assigned to the controller?
  - Does the Controller require a port number i.e. 8080? This can be verified by logging into controller.
  - Are the technology & assigned technology id values correct?
  - Is the correct http session manager configuration assigned to the controller?
  - Is the correct remote discovery configuration assigned to the controller?
  - Has there been recent UI changes to Controller login page? -- This can be verified through testing the "Topology Discovery - Initial Script" with the controller IP address. If topology was previously working and the script fails there has likely been a UI change

===== Common Exceptions  =====

Query to return recent Topology Failures for a controller

  select  gdsh . *, gdsf . * from general_discovery_sync_history gdsh left join general_discovery_sync_failure gdsf ON gdsf.id = gdsh.error_id where gdsh.job_type = 'TOPOLOGY_SYNC' and gdsh.success = 0 and gdsh.network_element_id = <network element id> order by gdsh.id desc limit 10;

    
The error_msg field contains the exception message that was thrown during the topology failure


Exception list with known fixes or reason exception was thrown. Please note that this is not a complete issue of possible fixes/causes and should only be used as a guide when troubleshooting issues.

=== java.net.ConnectException: Connection refused (Connection refused) ===
  * Port number not assigned in network element database
  * Controller UI issues 
  * Topology not supported for technology

=== javax.net.ssl.SSLHandshakeException: ===
  * Incorrect login credentials value
  * Recent Controller UI Change, “Topology Discovery - Initial Script” & “Topology Discovery - Get Full Discovery Script” scripts will need to be updated

=== java.lang.NullPointerException: Cannot invoke method getTechology() on null object ===
  * Incorrect login credentials value
  * Unsupported software version
  * Recent Controller UI Change, “Topology Discovery - Initial Script” & “Topology Discovery - Get Full Discovery Script” scripts will need to be updated


=== java.lang.NullPointerException: Cannot get property 'safeLoginScript' on null object ===
  * Login Script for affected technology needs to be modified

=== java.lang.Exception: Error getting basic system info for IP … ===
  * Incorrect login credentials value
  * Controller UI issue

=== org.jsoup.HttpStatusException: HTTP error fetching URL. Status=404, … ===
  * Unsupported Software Version

=== java.net.SocketTimeoutException: connect timed out ===
  * Controller connection issues