After element creation we noticed that the newly created element was not polling. After some investigation the element settings seem to be incorrect. When retrieved with the client test tool we can see that the port type is set to SNMPV2 instead of HTTP.
element settings:
We are currently using DataMiner (9.6.13.0-8820-CU1). Is this a know issue or do you know anything that can explains this behavior?
Wannes Wittevrongel [SLC] [DevOps Advocate] Selected answer as best 28th October 2020
Wannes, How are you creating the element ? I'm able to create a double HTTP connection elements through Cube and through Automation script (engine.SynchronousAddElement call) with no problems. I'm using 10.0.0 so i'm not discarding possible issues. My suggestion would be to:
- Review Protocol and check if Port Settings are as intended. Cube should be able to pick it up and create the element according to what you set on the new element wizard.
- If creating an element from AutomationScript make sure you are setting elementPortInfo.ProtocolType "http" in order to not have that connection created with snmpv2. Here is an example of code that creates an element through automation script with 2 different http interfaces:
David Pernes [SLC] Edited answer 28th October 2020