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: Netdisco an VRF's (Oliver Gorwits)
2. Re: Netdisco an VRF's (Sassan Dibadj)
3. Re: Netdisco an VRF's (Sassan Dibadj)
4. Re: Netdisco an VRF's (Oliver Gorwits)
--- Begin Message ---
On 2017-02-20 09:00, Cardinal-Richards, Emma wrote:
In the meantime... I've got Netdisco to discover the ARP information
from our multiple data centre VRFs using the method as described in
the attached older Netdisco mailing list post.
Thanks Emma! It seems this NXOS script never made it into the main
distribution so I've created a ticket to get that done:
https://github.com/netdisco/netdisco/issues/298
regards,
oliver.
Regards,
Emma
-----Original Message-----
From: Oliver Gorwits [mailto:oli...@cpan.org]
Sent: 19 February 2017 11:52
To: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] Netdisco an VRF's
Hi Sassan,
The short answer is that Netdisco is not VRF-aware so I don't think
there's a way to get this to work.
It has long been on the wishlist but is a significant patch and we've
not had anyone step forward to try. I can give some pointers if anyone
is interested (I suggest opening a ticket or wiki page on github to
discuss, but only if there is genuinely the time to commit to
implementing).
As an aside, Netdisco caches the community last used to successfully
connect to a device, so this is why you have not be able to test
collecting per-VRF IPs by editing deployment.yml. The way to do this
is
to delete the device then re-discover and re-arpwalk.
regards,
oliver.
On 2017-02-14 14:49, Sassan Dibadj wrote:
> We are currently transitioning to having two main VRF's for our
> network here and since about November netdisco is no longer pulling IP
> arp information on the non-default VRF.
>
> I did some research and added as second context along with a second
> community name and I am able to pull the second VRF's IP's via
> snmpwalk when querying the other community name.
>
> I updated the netdisco deployment.yml to include the new community
> name and even tried making it the first one it tries but it seems like
> I still only get back IP ARP information on the default VRF.
>
> We are running Cisco 7k Nexus platform and this is what I added to the
> cores.
>
> snmp-server context clinical vrf clinical
>
> snmp-server community xxxxxxxx ro
>
> snmp-server mib community-map xxxxxx context clinical
>
> SNMP walk I was using is below. If I use the regular community name it
> pulls the default VRF's ARP and if I change it to the new community
> name it pulls the non-default VRF's IP's.
>
> snmpwalk -mALL -v1 -c xxxxxx xxx.xxx.xxx.xx .1.3.6.1.2.1.4.22
>
> Is there something I can do to make netdisco pull this info again?
>
> Thank you,
>
> -------------------------
>
> UT Southwestern
>
> Medical Center
>
> The future of medicine, today.
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
Hi Christian,
That's very nice! I´ve also tested it and it works fine! Thanks a mil
for this litte "christmas" present.
That makes the nexus discovery with vrf more easy and thus doesn´t
require a complex snmp config.
Sebastian
-----Ursprüngliche Nachricht-----
Von: Christian Ramseyer [mailto:r...@networkz.ch]
Gesendet: Mittwoch, 9. Dezember 2015 20:58
An: Sebastian Rösch <roe...@alcera.de>
Cc: Jeroen van Ingen <j.vaningensche...@utwente.nl>;
netdisco-users@lists.sourceforge.net
Betreff: Re: [Netdisco] Best way to discover Cisco Nexus N5K
On 08/12/15 13:42, Sebastian Rösch wrote:
exactly, currently I have different snmp communites for each vrf.
My favorite way would be to fetch the addresses with the ssh
collector, because you there is a command in nexus for showing all
vrf´s content:
"show ip arp vrf all". That would be great... because I could remove
all the additional devices I´ve just added for arpnipping the
different vrf´s.
But so far I wasn´t able to add another device type as described here,
I´m not very familiar with all that perl stuff.....
http://search.cpan.org/~oliver/App-Netdisco/bin/netdisco-sshcollector
What do I need to do for this?
Hi Sebastian & List
Here is a module that I just made and tested on a N5kC5596Up. You must
store the file in lib/perl5/App/Netdisco/SSHCollector/Platform/NXOS.pm
(there's already all the other platform-specific .pm files there),
then reference it in deployment.yml like this:
sshcollector:
- hostname: 'n5.example.com'
user: whatever
password: topsecret
platform: NXOS
Maybe Olvier or another Netdisco dev can add it to the distro for
future releases.
Hope that helps
Christian
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Thank you Oliver, that caused it to refresh the clinical IP's.
I'm going to look into the ssh collector some more and see if I can get it to
do both with that.
Thank you for the help.
-----Original Message-----
From: Oliver Gorwits [mailto:oli...@cpan.org]
Sent: Sunday, February 19, 2017 5:52 AM
To: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] Netdisco an VRF's
Hi Sassan,
The short answer is that Netdisco is not VRF-aware so I don't think there's a
way to get this to work.
It has long been on the wishlist but is a significant patch and we've not had
anyone step forward to try. I can give some pointers if anyone is interested (I
suggest opening a ticket or wiki page on github to discuss, but only if there
is genuinely the time to commit to implementing).
As an aside, Netdisco caches the community last used to successfully connect to
a device, so this is why you have not be able to test collecting per-VRF IPs by
editing deployment.yml. The way to do this is to delete the device then
re-discover and re-arpwalk.
regards,
oliver.
On 2017-02-14 14:49, Sassan Dibadj wrote:
> We are currently transitioning to having two main VRF's for our
> network here and since about November netdisco is no longer pulling IP
> arp information on the non-default VRF.
>
> I did some research and added as second context along with a second
> community name and I am able to pull the second VRF's IP's via
> snmpwalk when querying the other community name.
>
> I updated the netdisco deployment.yml to include the new community
> name and even tried making it the first one it tries but it seems like
> I still only get back IP ARP information on the default VRF.
>
> We are running Cisco 7k Nexus platform and this is what I added to the
> cores.
>
> snmp-server context clinical vrf clinical
>
> snmp-server community xxxxxxxx ro
>
> snmp-server mib community-map xxxxxx context clinical
>
> SNMP walk I was using is below. If I use the regular community name it
> pulls the default VRF's ARP and if I change it to the new community
> name it pulls the non-default VRF's IP's.
>
> snmpwalk -mALL -v1 -c xxxxxx xxx.xxx.xxx.xx .1.3.6.1.2.1.4.22
>
> Is there something I can do to make netdisco pull this info again?
>
> Thank you,
>
> -------------------------
>
> UT Southwestern
>
> Medical Center
>
> The future of medicine, today.
>
>
> ----------------------------------------------------------------------
> -------- Check out the vibrant tech community on one of the world's
> most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Thank you, I did manage to get it working using the sshcollector method and the
NXOS.pm
Just checked this morning and all is well again.
Thank you all for the guidance.
-----Original Message-----
From: Cardinal-Richards, Emma [mailto:e.cardinal-richa...@ucl.ac.uk]
Sent: Monday, February 20, 2017 3:01 AM
To: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] Netdisco an VRF's
In the meantime... I've got Netdisco to discover the ARP information from our
multiple data centre VRFs using the method as described in the attached older
Netdisco mailing list post.
Regards,
Emma
> -----Original Message-----
> From: Oliver Gorwits [mailto:oli...@cpan.org]
> Sent: 19 February 2017 11:52
> To: netdisco-users@lists.sourceforge.net
> Subject: Re: [Netdisco] Netdisco an VRF's
>
> Hi Sassan,
>
> The short answer is that Netdisco is not VRF-aware so I don't think
> there's a way to get this to work.
>
> It has long been on the wishlist but is a significant patch and we've
> not had anyone step forward to try. I can give some pointers if anyone
> is interested (I suggest opening a ticket or wiki page on github to
> discuss, but only if there is genuinely the time to commit to
> implementing).
>
> As an aside, Netdisco caches the community last used to successfully
> connect to a device, so this is why you have not be able to test
> collecting per-VRF IPs by editing deployment.yml. The way to do this
> is to delete the device then re-discover and re-arpwalk.
>
> regards,
> oliver.
>
> On 2017-02-14 14:49, Sassan Dibadj wrote:
> > We are currently transitioning to having two main VRF's for our
> > network here and since about November netdisco is no longer pulling
> > IP arp information on the non-default VRF.
> >
> > I did some research and added as second context along with a second
> > community name and I am able to pull the second VRF's IP's via
> > snmpwalk when querying the other community name.
> >
> > I updated the netdisco deployment.yml to include the new community
> > name and even tried making it the first one it tries but it seems
> > like I still only get back IP ARP information on the default VRF.
> >
> > We are running Cisco 7k Nexus platform and this is what I added to
> > the cores.
> >
> > snmp-server context clinical vrf clinical
> >
> > snmp-server community xxxxxxxx ro
> >
> > snmp-server mib community-map xxxxxx context clinical
> >
> > SNMP walk I was using is below. If I use the regular community name
> > it pulls the default VRF's ARP and if I change it to the new
> > community name it pulls the non-default VRF's IP's.
> >
> > snmpwalk -mALL -v1 -c xxxxxx xxx.xxx.xxx.xx .1.3.6.1.2.1.4.22
> >
> > Is there something I can do to make netdisco pull this info again?
> >
> > Thank you,
> >
> > -------------------------
> >
> > UT Southwestern
> >
> > Medical Center
> >
> > The future of medicine, today.
> >
> >
> > --------------------------------------------------------------------
> > ---------- Check out the vibrant tech community on one of the
> > world's most engaging tech sites, SlashDot.org!
> > http://sdm.link/slashdot
> >
> > _______________________________________________
> > Netdisco mailing list
> > netdisco-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
> ----------------------------------------------------------------------
> -------- Check out the vibrant tech community on one of the world's
> most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
On 2017-02-22 15:03, Sassan Dibadj wrote:
Thank you, I did manage to get it working using the sshcollector
method and the NXOS.pm
Just checked this morning and all is well again.
That's great to hear, thanks.
(and thanks again to Emma for reminding us of the script!)
regards,
oliver.
Thank you all for the guidance.
-----Original Message-----
From: Cardinal-Richards, Emma [mailto:e.cardinal-richa...@ucl.ac.uk]
Sent: Monday, February 20, 2017 3:01 AM
To: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] Netdisco an VRF's
In the meantime... I've got Netdisco to discover the ARP information
from our multiple data centre VRFs using the method as described in
the attached older Netdisco mailing list post.
Regards,
Emma
-----Original Message-----
From: Oliver Gorwits [mailto:oli...@cpan.org]
Sent: 19 February 2017 11:52
To: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] Netdisco an VRF's
Hi Sassan,
The short answer is that Netdisco is not VRF-aware so I don't think
there's a way to get this to work.
It has long been on the wishlist but is a significant patch and we've
not had anyone step forward to try. I can give some pointers if anyone
is interested (I suggest opening a ticket or wiki page on github to
discuss, but only if there is genuinely the time to commit to
implementing).
As an aside, Netdisco caches the community last used to successfully
connect to a device, so this is why you have not be able to test
collecting per-VRF IPs by editing deployment.yml. The way to do this
is to delete the device then re-discover and re-arpwalk.
regards,
oliver.
On 2017-02-14 14:49, Sassan Dibadj wrote:
> We are currently transitioning to having two main VRF's for our
> network here and since about November netdisco is no longer pulling
> IP arp information on the non-default VRF.
>
> I did some research and added as second context along with a second
> community name and I am able to pull the second VRF's IP's via
> snmpwalk when querying the other community name.
>
> I updated the netdisco deployment.yml to include the new community
> name and even tried making it the first one it tries but it seems
> like I still only get back IP ARP information on the default VRF.
>
> We are running Cisco 7k Nexus platform and this is what I added to
> the cores.
>
> snmp-server context clinical vrf clinical
>
> snmp-server community xxxxxxxx ro
>
> snmp-server mib community-map xxxxxx context clinical
>
> SNMP walk I was using is below. If I use the regular community name
> it pulls the default VRF's ARP and if I change it to the new
> community name it pulls the non-default VRF's IP's.
>
> snmpwalk -mALL -v1 -c xxxxxx xxx.xxx.xxx.xx .1.3.6.1.2.1.4.22
>
> Is there something I can do to make netdisco pull this info again?
>
> Thank you,
>
> -------------------------
>
> UT Southwestern
>
> Medical Center
>
> The future of medicine, today.
>
>
> --------------------------------------------------------------------
> ---------- Check out the vibrant tech community on one of the
> world's most engaging tech sites, SlashDot.org!
> http://sdm.link/slashdot
>
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
----------------------------------------------------------------------
-------- Check out the vibrant tech community on one of the world's
most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
