From 9227e8cde8281045181169f0d77d548452558ef1 Mon Sep 17 00:00:00 2001 From: Oliver Gorwits Date: Mon, 3 Oct 2016 21:26:31 +0100 Subject: [PATCH] note on how to force change the community string --- Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod b/Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod index 1d87c703..cfe9e29c 100644 --- a/Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod +++ b/Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod @@ -135,6 +135,17 @@ A side panel appears in the web page with debug information. Be sure to turn this off when you're done (stop and start without the environment variable) otherwise secrets could be leaked to end users. +=head1 Change the SNMP commnuity string for a Device + +If you change the SNMP community string in use on a Device, and update +Netdisco's configuration to match, then everything will continue to work fine. + +However, if the Device happens to support two community strings then Netdisco +can become "stuck" on the wrong one, as it caches the last-known-good +community string to improve performance. To work around this, delete the +device (either in the web GUI or using C at the command line), +and then re-discover it. + =head1 Neighbor Relations on Juniper EX The LLDP configuration should look like: