Send netdisco-users mailing list submissions to
netdisco-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
netdisco-users-requ...@lists.sourceforge.net
You can reach the person managing the list at
netdisco-users-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: Switch from SNMPv2 to SNMPv3 (Dean, Barry)
--- Begin Message ---
Thanks for this. It certainly looks like a better option than letting people
loose with SQL 😃 I’ll try it.
Thanks
Barry Dean BSc (Hons) (He/Him)
Network Services Team Leader
Network Services Team
IT Services
[cid:image001.png@01D8ADA1.B41CDD00] Start a Teams Chat with Barry
Dean<https://teams.microsoft.com/l/chat/0/0?users=b...@liverpool.ac.uk>
University of Liverpool I IT Services I Brownlow Hill I Liverpool I L69 3GG
Tel: 0151 795 9540
[UoL - Logo - CMYK - small]
From: Oliver Gorwits <oli...@cpan.org>
Sent: 11 August 2022 14:18
To: Dean, Barry <b...@liverpool.ac.uk>
Cc: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] Switch from SNMPv2 to SNMPv3
Hi Barry
I hope you can do this more easily using the configuration file.
If you set up device_auth with two tagged stanzas, one for v2 and one for v3,
then use "no" and "only" options, you can control what is used for each.
So as a test, take one device IP, add it to the "no" option for the v2 stanza,
and to the "only" option for the v3 stanza, and restart the backend (or test at
command line with ~/bin/netdisco-do discover -d 1.2.3.4 -D).
Netdisco should spot that it can then only use the v3 stanza in the config for
the device, and flip over to using it.
If it does not, I'd like to fix that bug :-)
regards
Oliver.
On Thu, 11 Aug 2022 at 14:11, Dean, Barry
<b...@liverpool.ac.uk<mailto:b...@liverpool.ac.uk>> wrote:
I have a number of devices that have been detected and discovered using SNMPv2
and this is reflected in the snmp_ver column in the device table as well as the
entry in the community table.
I’d like to flip them over to using SNMPv3. (There is nearly 500 of them!)
The only way I know to do this is to update the community table with the name
of the SNMPv3 credential set defined in deployment.yml. Which is OK, but not
all of my team are comfortable with SQL!
Is there another way, short of my writing a script to do it? A dropdown
selection on the device Details page would be the ideal, but I’ll take anything
I can get!
I have visions of someone forgetting the WHERE clause on the UPDATE and finding
myself pulling the old community table out of the backup!
Thanks
Barry Dean BSc (Hons) (He/Him)
Network Services Team Leader
Network Services Team
IT Services
[cid:image001.png@01D8ADA1.B41CDD00] Start a Teams Chat with Barry
Dean<https://teams.microsoft.com/l/chat/0/0?users=b...@liverpool.ac.uk>
University of Liverpool I IT Services I Brownlow Hill I Liverpool I L69 3GG
Tel: 0151 795 9540
[UoL - Logo - CMYK - small]
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net<mailto:netdisco-users@lists.sourceforge.net>
https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
