You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also in my case, the root node IF-MIB (which in turn includes ifAdminStatus) was initially declared as "config true".
In our current implementation, we decided to put all IF-MIB values inside the state database and prohibit any ability to change it outside. Because of that, I decided to rewrite "config true" to "config false" for the IF-MIB container.
After, if we call "snmpset -m ALL -v2c -c private 10.40.0.149 IF-MIB::ifAdminStatus.4 i up" in the result we get empty transaction. Also, I tried to rewrite smiv2:max-access to "read-only" but the result was the same.
I propose that if the node is declared as "config false", the clixon_snmp module must decline "snmpset" operation and must not create an empty transaction.
The text was updated successfully, but these errors were encountered:
Yang node ifAdminStatus (in generated IF-MIB.yang) initially is declared as "read-write":
Also in my case, the root node IF-MIB (which in turn includes ifAdminStatus) was initially declared as "config true".
In our current implementation, we decided to put all IF-MIB values inside the state database and prohibit any ability to change it outside. Because of that, I decided to rewrite "config true" to "config false" for the IF-MIB container.
After, if we call "snmpset -m ALL -v2c -c private 10.40.0.149 IF-MIB::ifAdminStatus.4 i up" in the result we get empty transaction. Also, I tried to rewrite smiv2:max-access to "read-only" but the result was the same.
I propose that if the node is declared as "config false", the clixon_snmp module must decline "snmpset" operation and must not create an empty transaction.
The text was updated successfully, but these errors were encountered: