Subject says it all.
My understanding was that SNMP templates are simply copied to the particular device instance within IMC when they are used. So there should not be something left behind like a use counter or lock so deleting should not be a problem.
I have not found a hint as to why this fails. The documentation typically tells me only things I see with naked eye anyway...(sigh).
And actually I do not see a process how I could reduce a possible counter by one. There is no such thing as a removal procedure turning a device into a template "non-user". Currently I would simply convert a device in to SNMPv3 use and then delete the old SNMPv2 template.
I suspect a silly bug...and I also suspect this exists for ages but nobody really cared....
Hints appreciated !
if a template is used by any device, it cannot be deleted globally.
Please ensure the template is not used by any devices. Globally change all devices templates using the batch operation and selecting a new template.
thanks for responding !
In fact we were sure we had no remaining devices on SNMPv2.
And the batch job cannot compensate for the fact that there is no spot where the used template is actually shown.
We found the solution though:
We looked at the data by REST API data and found the device details here do show the access templates being used for each device.
And this way we found we were correct.
But the data helped in a different way: we saw the boolean attribute autodiscovertemplate for each SNMP template.
That brought us to looking closer at the autodiscovery dialogues and we discovered many templates being used there.
Deleting them sets the autodiscoverytemplate flag to FALSE on each and then we could delete the snmp templates.
I admit I have never looked at the autodiscovery much closer in any training and when do you have so many devices at hand that templates get really relevant in training (or support) ??
May be you can put that in the KDB !
I suspect that was not your radar too :-)
Hello Holger, that is a very creative way to investigate the bug and for sure I am sending this to R&D to be fixed.
Thank you very much
To be honest the bug is still not clearly defined.
From the Rest-API explorations we did not see an actual relation between devices and the templates justifying a deletion being denied and as this is a copy only operation anyway there is no real need.
Since we now got rid of the V2 templates I was curious what happens if I allocate a new V2 template and let a v2 device be configured using this new v2 template.
I did that that and the device works and afterwards the v2 template could successfully be deleted.
So a device is not actually keeping a template busy contrary to the message text. Only in connection with an active periodic autodiscovery a deletion denial makes sense.
So my earlier perceived need for template infos with respect to a particular device is gone. May be they had actually implemented something like this otherwise... I am sure with IMC the coding folks were always way better than the documentation folks... :-)
------------------------------Kind RegardsPaolaOriginal Message:Sent: Nov 29, 2023 10:50 AMFrom: HZ55Subject: IMC PLAT 7.3 E0710 but I am sure way earlier too: cannot delete SNMP templates: "template XYZ is in use"
Original Message:Sent: Nov 02, 2023 05:53 AMFrom: pbitSubject: IMC PLAT 7.3 E0710 but I am sure way earlier too: cannot delete SNMP templates: "template XYZ is in use"
------------------------------Kind RegardsPaolaOriginal Message:Sent: Oct 24, 2023 11:03 AMFrom: HZ55Subject: IMC PLAT 7.3 E0710 but I am sure way earlier too: cannot delete SNMP templates: "template XYZ is in use"
© Copyright 2024 Hewlett Packard Enterprise Development LPAll Rights Reserved.