container system {
container works {
config false;
list works_l1 {
tailf:secondary-index snmp {
tailf:index-leafs name;
tailf:sort-order snmp;
}
key name;
leaf name { type string; }
list works_l2 {
key name;
leaf name { type string; }
}
}
}
container fails {
list fails_l1 {
tailf:secondary-index snmp {
tailf:index-leafs name;
tailf:sort-order snmp;
}
key name;
leaf name { type string; }
list fails_l2 {
key name;
leaf name { type string; }
tailf:callpoint cp1;
}
}
}
}
When I run snmpwalk on this schema, it works for the works container, but fails for the fails container. I tried playing with the tailf:secondary-index however I can (put it inside the inner list fails_l2 for example) but non works.
The difference between container works and fails is just the config false (for works).
In fails/fails_l1/fails_l2/cp1 I return the next entry successfully
It is interesting that you are having more difficulty with the config true container but I think more information is necessary. You don’t show a callpoint for the config false container. It sounds like you are correctly returning the next entry for the config true container so is that same logic running for the config false? (but again it is not shown so I’m wondering what data the snmpwalk is returning for the config false container).
I forgot to add the tailf:callpoint for container works
Because this is config false the callpoint is over the whole list (I’ve edited my original question)
I can’t seem to edit my original question.
I wanted to add that callpoint.
Also leaf-a under /system/fails/fails_l1/fails_l2/leaf-a.
And not as in the container fails, in the list fails_l2 only.
I do correctly return the appropriate values for both lists. I do see the correctly in the CLI, for example.
These are the logs I get from devel.log and snmp.log:
