Differences

This shows you the differences between two versions of the page.

--- support:add_new_mdc_sync [2022/10/06 17:16] – 10.91.110.100
+++ support:add_new_mdc_sync [2023/06/22 15:54] (current) – 10.91.110.100
@@ Line 6: / Line 6: @@
 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.
-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.
 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.
+==== 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:1616 .1.3.6.1.4.1.331
+=== Teko V4 ===
+  snmpwalk -v1 -c admins 50.229.75.130:1616 .1.3.6.1.4.1.6626.6000
+=== SOLID REL6 ===
+  snmpwalk -c public -v1 166.144.210.28:8002 .1.3.6.1.4.1.35043
 ==== Snmp Manager Steps ====
 An entry is required  in the discovery_profile table with the correct port number and read/write community for device.
@@ Line 79: / Line 91: @@
 === 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 successful request below:
+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:
   {"tags":{"entryPointId":"23755"},"httpCredentials":{"useHttps":false,"internalPort":8000,"externalPort":8000},"snmpCredentials":{"snmpVersion":"2","readCommunity":"public","writeCommunity":"private","internalPort":8001,"externalPort":8001},"sshCredentials":{"internalPort":8000,"externalPort":8000},"host":"166.144.206.175","port":8000,"technology":"ANDREWS_IONE","technologyVersion":"mdc2.8.3.13","requester":"SCO_Customer","requesterSite":"sco_site","discoveryType":"CONFIGURATION","timeout":300000,"payload":[],"priority":5}
+=== Ping Latency Widget is blank ===
+Syncs are running but Ping Latency widget is blank.
+{{:support:blank_ping_latency_layout.png?400|}}
+The network_element.discovered_name of the Controller needs to match the name in widget.
+In the example above the discovered_name should be "solid_controller"

Sidebar

Internal Errigal Collaboration Wiki

Differences

Sidebar

Internal Errigal Collaboration Wiki

User Tools

Site Tools

Differences

Page Tools