Updating the parameters of an existing trap and sending partial parameters to the trap
We have created a list of traps (notifications) that our application exposes and describes in the MIB file.
Today we find ourselves in a situation where we need to update the MIB and add an additional (optional) parameter to the hook (update objects) so that in the end we will have an existing notification with one more parameter.
My question (because I really don't know what the SNMP manager will do):
- If my client hasn't installed the updated MIB with the updated objects in the trap and I send a new parameter, what happens on the client side of the SNMP manager?
- What happens if a client installs a new MIB and I send a trap without a new parameter?
Intuitively, as a developer, I would expect everything to be OK, which means that for (1) it will be visible that the trap is visible (the new parameter is shown without OID translation or not shown at all) and for (2) the trap will be visible , and there will be no problems.
Also, in general, when a trap message definition has a parameter, is it required or optional?
source to share
The exact behavior depends on the manager.
In general, it is best not to modify objects in the published MIB. You must create a new trap containing an additional parameter. When you need to send without an additional parameter, use the old notification object. When you need to send an additional parameter, use a new object.
source to share