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. Simultaneous V1/2 and V3 confiugration in the deployment.yml
file (Damian R. Cleveland)
2. Re: Simultaneous V1/2 and V3 confiugration in the
deployment.yml file (Oliver Gorwits)
3. Re: Simultaneous V1/2 and V3 confiugration in the
deployment.yml file (Damian R. Cleveland)
--- Begin Message ---
Good day,
I'm currently using v1/2 but need to move to v3.
I'd like to gracefully migrate to v3 by leaving the deployment.yml file's v1/2
config in place while handling device config changes on a platform by platform
basis. Is this possible? If so, do I just begin the v3 configuration below the
v1/2 block?
Here is my current config:
device_auth:
- tag: All Segments
only:
- 192.168.42.0/24
community: ************
write: false
read: true
Thanks
-------
Damian Cleveland
Networking Engineering
Institute For Defense Analyses, Princeton, NJ
Office:609-279-6265
Mobile:609-235-8870
--------
--- End Message ---
--- Begin Message ---
Hi Damian
Because Netdisco caches the working community, you need to prevent use of
the tag and I suggest to use "no:[x.x.x.x,y.y.y.y]" to do that as you
migrate. Netdisco will then try the other tags, find that v3 works, and use
(and cache) that.
For troubleshooting you can run netdisco-do at the command line and add -D
for debug and SHOW_COMMUNITY=1 environment for details of the device_auth
processing. You can also run netdisco-do dumpconfig -e device_auth to check
your config is parsed OK.
regards
oliver.
On Thu, 3 Jul 2025 at 15:32, Damian R. Cleveland <dcl...@idaccr.org> wrote:
> Good day,
>
> I'm currently using v1/2 but need to move to v3.
>
> I'd like to gracefully migrate to v3 by leaving the deployment.yml file's
> v1/2 config in place while handling device config changes on a platform by
> platform basis. Is this possible? If so, do I just begin the v3
> configuration below the v1/2 block?
>
> Here is my current config:
>
> device_auth:
> - tag: All Segments
> only:
> - 192.168.42.0/24
>
> community: ************
> write: false
> read: true
>
> Thanks
> -------
> Damian Cleveland
> Networking Engineering
> Institute For Defense Analyses, Princeton, NJ
> Office:609-279-6265
> Mobile:609-235-8870
> --------
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Thanks for the guidance, Oliver.
So, currently all of my devices(Cisco, Barracuda, Palo Alto, etc.) are
configured with community ********.
I wan't to first change my Palos to v3. So first I make the necessary changes
on the Palos. Now I need make ND compatible.
Do I add the v3 information to the end of the "device_auth:" section like so?
device_auth:
- tag: All Segments
only:
- [ http://192.168.42.0/24 | 192.168.42.0/24 ]
community: ************
write: false
read: true
- ***v3 details***
*************
*************
And when you say "no:[x.x.x.x,y.y.y.y]," is this the IP address of the device
no longer using v2?
Thank you
-------
Damian Cleveland
Networking Engineering
Institute For Defense Analyses, Princeton, NJ
Office:609-279-6265
Mobile:609-235-8870
--------
From: "Oliver Gorwits" <oli...@cpan.org>
To: "Damian R. Cleveland" <dcl...@idaccr.org>, "netdisco-users"
<netdisco-users@lists.sourceforge.net>
Sent: Thursday, July 3, 2025 11:15:51 AM
Subject: Re: [Netdisco] Simultaneous V1/2 and V3 confiugration in the
deployment.yml file
Hi Damian
Because Netdisco caches the working community, you need to prevent use of the
tag and I suggest to use "no:[x.x.x.x,y.y.y.y]" to do that as you migrate.
Netdisco will then try the other tags, find that v3 works, and use (and cache)
that.
For troubleshooting you can run netdisco-do at the command line and add -D for
debug and SHOW_COMMUNITY=1 environment for details of the device_auth
processing. You can also run netdisco-do dumpconfig -e device_auth to check
your config is parsed OK.
regards
oliver.
On Thu, 3 Jul 2025 at 15:32, Damian R. Cleveland < [ mailto:dcl...@idaccr.org |
dcl...@idaccr.org ] > wrote:
Good day,
I'm currently using v1/2 but need to move to v3.
I'd like to gracefully migrate to v3 by leaving the deployment.yml file's v1/2
config in place while handling device config changes on a platform by platform
basis. Is this possible? If so, do I just begin the v3 configuration below the
v1/2 block?
Here is my current config:
device_auth:
- tag: All Segments
only:
- [ http://192.168.42.0/24 | 192.168.42.0/24 ]
community: ************
write: false
read: true
Thanks
-------
Damian Cleveland
Networking Engineering
Institute For Defense Analyses, Princeton, NJ
Office:609-279-6265
Mobile:609-235-8870
--------
_______________________________________________
Netdisco mailing list
[ mailto:netdisco-users@lists.sourceforge.net |
netdisco-users@lists.sourceforge.net ]
[ https://sourceforge.net/p/netdisco/mailman/netdisco-users/ |
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
