Topology Rediscovery Sync Failures

Author: Paddy Murphy

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

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>;

1. Verify that you can login into the Controller and successfully reach a landing page with data. Some Controllers can only be accessed through a tunnel
2. Is the Controller link down? link down functionality
3. Is the software version supported. – check supported technologies & software versions here here
4. Are the assigned login credentials correct and not null at the controller level? Controller Login values
5. Is the correct IP address assigned to the controller?
6. Does the Controller require a port number i.e. 8080? This can be verified by logging into controller.
7. Are the technology & assigned technology id values correct?
8. Is the correct http session manager configuration assigned to the controller?
9. Is the correct remote discovery configuration assigned to the controller?
10. 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

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.

• Port number not assigned in network element database
• Controller UI issues
• Topology not supported for technology

• Incorrect login credentials value
• Recent Controller UI Change, “Topology Discovery - Initial Script” & “Topology Discovery - Get Full Discovery Script” scripts will need to be updated

• 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

• Login Script for affected technology needs to be modified

• Incorrect login credentials value
• Controller UI issue

• Unsupported Software Version

• Controller connection issues