Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trying to change the "read-only" node through snmpset #376

Closed
vvsosed opened this issue Oct 5, 2022 · 0 comments
Closed

Trying to change the "read-only" node through snmpset #376

vvsosed opened this issue Oct 5, 2022 · 0 comments

Comments

@vvsosed
Copy link
Contributor

vvsosed commented Oct 5, 2022

If we call "snmpset -m ALL -v2c -c private 10.40.0.149 IF-MIB::ifOperStatus.4 i up" in the result we get:

MH-N366@00000000>show compare running-candidate 
+IF-MIB:IF-MIB {
+    ifTable {
+        ifEntry 4 {
+            ifOperStatus up;
+        }
+    }
+}

But ifOperStatus (in IF-MIB.yang) declared as "read-only" in yang model:

leaf ifOperStatus {
    type enumeration {
        enum "up" {
            value "1";
        }
        enum "down" {
            value "2";
        }
       ....
    }
    ...
    smiv2:max-access "read-only";
    smiv2:oid "1.3.6.1.2.1.2.2.1.8";
}

I consider that in this case, the clixon_snmp module must decline operation taking into account the smiv2:max-access value and also it mustn't prepare any changes in the candidate database

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants