User Tools
support:add_new_mdc_sync
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| support:add_new_mdc_sync [2022/10/06 16:46] – created 10.91.110.100 | support:add_new_mdc_sync [2023/06/22 15:54] (current) – 10.91.110.100 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== MDC Syncs Setup Instructions ====== | + | ====== MDC Sync Setup Instructions ====== |
| Author: Paddy Murphy | Author: Paddy Murphy | ||
| Line 6: | Line 6: | ||
| Performance and Configuration syncs need to be set up to populate widgets in EMS-Nova. | Performance and Configuration syncs need to be set up to populate widgets in EMS-Nova. | ||
| Instruction below are for a SEO environment where snmp port forwarding is used. | Instruction below are for a SEO environment where snmp port forwarding is used. | ||
| - | You will still need to verify the snmp port is correct where port forwarding is not used. | + | You will still need to verify the snmp settings are correct where port forwarding is not used. |
| Syncs are set up at the controller level. | Syncs are set up at the controller level. | ||
| Before you start you will need a connection to the rdf database. | Before you start you will need a connection to the rdf database. | ||
| Line 12: | Line 12: | ||
| RDF database server is defined in ansible env_configuration under [rdf-db] group in the hosts.ini file. | RDF database server is defined in ansible env_configuration under [rdf-db] group in the hosts.ini file. | ||
| + | ==== Verify you can do a SNMP Walk on device ==== | ||
| + | The majority of syncs use snmp, verify you can do a snmp walk before proceeding. | ||
| + | See example snmp walk commands for common technologies below. Remove SNMP port if it is not required. | ||
| + | === IONE === | ||
| + | snmpwalk -c public -v1 152.44.175.18: | ||
| + | | ||
| + | === Teko V4 === | ||
| + | snmpwalk -v1 -c admins 50.229.75.130: | ||
| + | | ||
| + | === SOLID REL6 === | ||
| + | snmpwalk -c public -v1 166.144.210.28: | ||
| + | | ||
| ==== Snmp Manager Steps ==== | ==== Snmp Manager Steps ==== | ||
| An entry is required | An entry is required | ||
| Line 27: | Line 39: | ||
| select * from orchestrator.element where entry_point_id | select * from orchestrator.element where entry_point_id | ||
| - | If element is missing it can be added by making a simple edit to the element in EMS System -> Edit System -> General Information. Adding a space to the " | + | If element is missing it can be added by making a simple edit to the element in EMS System -> Edit System -> General Information. Adding a space to the " |
| The element ID in orchestrator.element is used to set up the syncs. | The element ID in orchestrator.element is used to set up the syncs. | ||
| Line 53: | Line 65: | ||
| * customer_site_id – reference correct customer site in orchestrator.customer_site | * customer_site_id – reference correct customer site in orchestrator.customer_site | ||
| * element_id | * element_id | ||
| - | * schedule_id – reference id in orchestrator.schedule an hourly schedule would be suitable for Performance or Configuration syncs, the NEVER schedule can be used to stop the schedule | + | * schedule_id – reference id in orchestrator.schedule an hourly schedule would be suitable for Performance or Configuration syncs, the NEVER schedule can be used to stop the schedule, |
| - | Once a sync has been enabled you can check the results with the following queries | + | === Verify that Sync has run === |
| + | |||
| + | Once a sync has been enabled you can check the results with the following queries. If everything is set up correctly the sync should appear in the active_task and move to the completed_task. A five minute sync is useful for testing purposes. | ||
| failed task | failed task | ||
| Line 65: | Line 79: | ||
| | | ||
| ==== Gotchas ==== | ==== Gotchas ==== | ||
| + | |||
| + | === Unsupported Software Version | ||
| + | Sync has been set up and should have run but there are no entries in the task tables. | ||
| + | Supported versions can be checked in the following folder of the relevant branch of [[https:// | ||
| + | |||
| + | src/ | ||
| + | This information is usually in the …ParamaterPocessor.java file | ||
| + | Check the isCompatible method in this file it may allow a sync to work if software_version contains mdc i.e " | ||
| + | === Config errors === | ||
| + | Sync entries are appearing in the failed_task due to Max tries exceeded... | ||
| + | Check the orginal_request JSON data in the orchestrator.failed_task table and verify the values are correct. See example of a successful request below: | ||
| + | {" | ||
| + | === Ping Latency Widget is blank === | ||
| + | Syncs are running but Ping Latency widget is blank. | ||
| + | {{: | ||
| + | The network_element.discovered_name of the Controller needs to match the name in widget. | ||
| + | In the example above the discovered_name should be " | ||
support/add_new_mdc_sync.1665071177.txt.gz · Last modified: 2022/10/06 16:46 by 10.91.110.100
Page Tools
