Hi all,
I’m trying to go from a driver range that has primary snmp connection/secondary http connection to the other way around.
I noticed that the order of the port settings was incorrect/validator was complaining about order, so I fixed that:
However, now when I try to change from the old version to the new version, the ports are still mixed up. See old version below:
New version with incorrect ports:
But when creating a new element, the ports are correct:
Any idea why the ports aren’t carried over to the new connection? Is this intended behavior or should this be addressed? It could be that the port is already locked to the element.xml perhaps?
Hi Alex,
This is intended behavior. The port settings of the existing element are saved in element.xml. If you change the driver range then these settings are read out from the xml. It sees that the main port was set to 161 so fills this in for the main port, similar like it’s finding 8082 for the second port.
There is no automatic adaptation of these settings as a new driver might as well have added or removed ports or switched to a different purpose of the port usage.
This is also the reason why a new driver range is needed to indicate that the existing elements will not be compatible without doing some modifications to it (in this case the portsettings need to be modified).
P.S. I see that the original driver is using SNMPv2, while the new driver range is SNMPv1. Is this intended?
Hi Alex,
What Laurens means is that this type of change is considered a “major change” as it causes impact. In this case, the impact is caused because you make changes to the connections which are not automatically updated when an existing element is updated to use your new version.
Hi Laurens,
Thanks for the feedback. When you say “no automatic adaptation”, you mean it will always keep the ports when changing the version on an existing element?
Also when you say new driver range, specifically do you mean a major range change?