The Microsoft Platform protocol is currently using the deprecated DMS_GET_INFO call to retrieve element data, specifically the secondary polling IP. In order to fix this issue I tried using a parameter of type pollingip in order to parse the IP's and return the second. However the pollingip parameter only returns the first IP address, and the ip type parameter returns only the first IP address along with the port number(as shown in the image below). This behavior was consistent across various DMAs with this protocol. So far I haven't been able to find another way to retrieve this IP without using the deprecated DMS class. Thank you in advanced for any insight on this topic.
A parameter of type pollingip will contain multiple IP addresses separated by a semicolon if the connector has more than one interface.
If this is not the case for the Microsoft Platform 6.0.0.7 connector, most likely there is something wrong with the secondary interface configuration. The thing that jumps out straight away is the fact that the SSH interface has the port set to an invalid value (i.e. 0 which is reserved by IANA and should not be used for normal TCP communications).
This interface will not get initialized in DataMiner and will not be working at all. As a result, it will also be missing from the content of the pollingip parameter.
That is odd, I have tried the same and as soon as I changed the default port to a valid value (e.g. 22) and created a new element with the adapted connector version, I noticed that the interface got correctly initialized. As a result, the pollingip parameter had the value 127.0.0.1;127.0.0.5 which are the correct values of both interfaces.
Hey Jeroen, that’s a good catch. Unfortunately, we had already tried to remove/change the configurations of the element for this reason. We also tried duplicating the elements, deleting and recreating elements, and hosting the connector on different DMA’s. No luck with this yet.