I am updating my display keys for an SNMP table, which raised alarms based on the severity of the incoming trap.
I want to update the DK of the table so that the values are unique, but when deploying I have existing alarms which use the old DKs which won't update. Is there any way to get around this whilst deploying?
Updating this kind of driver is typically a new driver range because it breaks as you stated compatibility. The suggested way forward is creating new elements. I know this isn't always the way forward.
My suggestion would be to before deploying and changing the production version is to change all elements using the production driver to <no trending> and <no monitoring> basically removing the trend and alarm template.
Then change the production version (note I assume here the only thing that was done was the display key changes, for other big major changes like port adaptions elements require re-configuration) to the new driver. Then validate the alarm and trend templates (since your DK's will have changed check the filters in the configured alarm and trend templates) and assign the new trend/alarm templates.