SNMPv3: non-persistence of access configuration for a newly added user group after restarting Beam

Questions / Help
1

When trying to configure access control for snmpv3, I created a new user with a new user group and then used the ``snmp_view_based_acm_mib:add_access`` function to add access for newly configured user group, and I was able to use this user using a mib browser.

But after restarting Beam, I wasn’t able to use this user that I configured before. I tried this with both dets as well as mnesia as the ``mib_storage`` and found this issue regardless of the database chosen for persistence.

Then I found that the vacmAccessTable didn’t contain this information after restarting the VM even though the user was present in vacmSecurityToGroupTable, which means the user information was persistent whereas the access information wasn’t. I couldn’t find anything regarding this behaviour in the official documentation.

Is this a design choice? How should new user groups (with persistent access) be added without modifying the existing configuration files?

1 Like
2

Hi, did you do anything after the call add_access? There is a note in the source code that following the add_access, you should call snmpa_vacm:dump_table().
Could you try it, if you haven’t and tell me if it helps?

Best regards,
Konrad

2 Likes
3

Thanks a lot, Whaileee. It worked.

2 Likes
4

Great, thanks for the writing about it. Sounds like we need a documentation enhancement

Best regards,
Konrad

1 Like