Author: Paddy Murphy

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

Please note that an Alarm Severity Sync should be run before an Active Alarm Sync

Troubleshooting Checklist

  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. Is the correct discovered trap configuration value assigned to the Controller and Child elements?
  8. Is the correct http session manager configuration assigned to the controller?
  9. Is the correct alarm sync configuration assigned to the controller?

Run the following query on the Controller been investigated.

  select id, name, technology, software_version ip_address, port, link_down, login_credentials_id, http_session_manager_configuration_id, alarm_sync_setting_id, discovered_trap_configuration_id  from network_element where id = <network  element id>;
  

Verify that none of the following values are null:

Common Sync Errors

URL path or OID did not specified

Failed to connect/login to ...

TimeoutException : time out after retries

SocketTimeoutException : Read timed out

disabledAlarms = null, discoveredAlarms = 1

select * from network_element_sync_setting where job_type = 'ALARM_SEVERITY_SYNC'  and 
network_element_id = <network  element id>;

No discovered trap configuration for ...