Davide, Good spot! Yes, in the last release we changed the community from "public" to "clearwater", and I suspect we failed to update the Cacti documentation. I've raised https://github.com/Metaswitch/clearwater-docs/issues/11 to fix this. In the short term, yes, setting the rocommunity back to public will almost certainly fix this.
Thanks, Matt From: [email protected] [mailto:[email protected]] On Behalf Of Davide Cherubini Sent: 05 November 2013 04:02 To: [email protected] Subject: Re: [Clearwater] Cacti for Clearwater Hi Matt, I have masked the hostnames in the previous posts, they were correct. Sorry for the confusion. I am deploying on eu-west-1. BTW, I changed the rocommunity to (e.g.) 'public' in the snmpd.conf files and the SNMP error went away. Is the rocommunity parameter used for something else? I see the default value is 'rocommunity clearwater 0.0.0.0/0<http://0.0.0.0/0> -V clearwater(my deployment <name> is 'clearwater'). thanks, Davide
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
