RMS SNMP Settings ID is not consistent

Hi,

I would like to know whether this is the intended behavior. We begin with a freshly reset RUTX08 that has just been adopted into the RMS. Then go to Configure Device > Services > SNMP > SNMP Settings. Unfold both options, unfold both “Update” panes and click on “Get configuration fom device” in both fields. Here are screenshots from my RMS:

Please note that the “ID/Name” is “general” in the first pane, while it is “cfg” and some hex number in the second. Is this the intended behavior? I think that the ID of the SNMP service (if you want it to be exposed to customer in the first place” should be consistent in all dialogs. To me this looks like in the frist pane, a user-friendly name “general” is shown while in the second case, an internal ID leaks out that was never meant to be shown to the customer.

I might expand this thread to another issue I have been experiencing with not being able to write the “General SNMP configuration” (the one where the allegedly internal ID is shown) to a new router. But I need a bit more time to reproduce this. If I don’t get back to the thread I was unable to reproduce that issue.

Greetings, Marc Haber

Here is the additional issue: The numeric configuration ID seems to differ from router to router. It usually ends on 48a, and since I tend to only look at the end of IDs, I missed that. On one of my test routers it is cfg0be48a, on another it is cfg0fe48a.

This prevents customers from having this part of SNMP configuration in a configuration template. For example, in my fleet, the e-mail address is almost always the same. I’d have that in a template and only overwrite it for routers where other people are respnsible. I cannot do that since applying that template always ends up in “object not found” on all routers but the one I pulled the template from. Setting the ID to “general” manually also doesn’t work.

Is this REALLY the intended behavior? Or is this a bug?

Greetings,

This is the expected behaviour. The API returns the configuration ID or name differently depending on the endpoint.

Best Regards,
Justinas

So SNMP cannot be sensibly configured via the RMS. I do not need to understand this but I must accept it.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.