If a node is added and managed via SNMPv3 credentials (via the SM or WI), listing resources errors with X node is down, unreachable or public isn't a valid community string; like it's trying to use SNMPv2 credentials. Doing this from the SM works just fine. This behavior is not seen when managing the node via SNMPv2. Does anyone else have this issue?
