Hi Dojo,
We have an interesting case where an element(say IP 1.1.1.1) is active on DMA X(DM 9.0CU24) but does not come out of timeout on DMA Y(DM 10.1 CU0).
The element has driver ETL systems Vulcan VCN-10(type:serial) and on X, it uses v1.0.1.5 and on Y, it uses v1.0.1.8.
Both X and Y are in same subnet, same default gateway and no firewall restrictions and no driver issues. Wireshark capture on Y only indicates HTTP 200 and not any data flow as the device is a serial device. However from Y, I can ping the element as well as access its web GUI. On Y, StreamViewer shows timeout as response for all groups and the element cards are all greyed out as well.
We have ensured the element configuration remains the same on both X and Y(the driver version is different of course - in fact, using 1.0.1.5 on Y also results in timeout only).
To avoid double polling, we stopped the element on X but on Y it still remains in timeout. We tried enabling some parameter values on Y but no success.
Can you please advice what else we can check ? Could the DataMiner version be the problem ? Thanks in advance.
Shot in the dark, but in version 1.0.2.x you have a 'Polling IP Configuration Page' where you can fill an IP of CPU 1 or 2. Would that be filled on your side? Checking in the driver dynamic IP is used... On my side driver works and only CPU 1 is filled with an IP.