User Tools
support:alarm_sync_failures
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| support:alarm_sync_failures [2024/03/08 16:06] – 10.91.120.100 | support:alarm_sync_failures [2025/01/08 17:27] (current) – [Common Sync Errors] 10.91.120.100 | ||
|---|---|---|---|
| Line 32: | Line 32: | ||
| === URL path or OID did not specified === | === URL path or OID did not specified === | ||
| * Missing or incorrect disabled_alarm_parse_script_id in assigned alarm sync setting | * Missing or incorrect disabled_alarm_parse_script_id in assigned alarm sync setting | ||
| - | * verify that the alarms sync path contains a valid entry for the disabled alarm. | + | * verify that the script assigned in retrieve_path_script_id |
| * If technology does not support disabled alarms assign a "NO DISABLED ALARMS" | * If technology does not support disabled alarms assign a "NO DISABLED ALARMS" | ||
| Line 42: | Line 42: | ||
| === TimeoutException : time out after retries === | === TimeoutException : time out after retries === | ||
| * Incorrect login_credentials_id assigned to controller. | * Incorrect login_credentials_id assigned to controller. | ||
| + | * If error message contains OID check if snmp values are correct and manually run command | ||
| * UI issues on the controller login page, confirm & report to customer | * UI issues on the controller login page, confirm & report to customer | ||
support/alarm_sync_failures.1709914001.txt.gz · Last modified: 2024/03/08 16:06 by 10.91.120.100
Page Tools
