Re: [Netdisco] Find nodes by vendor (using MAC address OUI)?

[Sckolnick, G. <Gar...@uv...>]

Hi Oliver,

Perfect!  It works when we use the correct syntax -- 00:23:ae* -- and the Node Vendor Inventory also works.  (We're still learning the new UI.)

We did, however, encounter one issue.  When viewing the Node Vendor Inventory report and changing "Show 50 records" to "Show All records" we receive the following error:

DataTables warning: table id=data-table - Ajax error. For more information about this error, please see http://datatables.net/tn/7

Any ideas?

Also, on an unrelated note, are there instructions anywhere on the best way to migrate our DB on ND1 to ND2 (or merge the two)?  It'd be nice not to have to recreate all of the user accounts and to also hold onto the historical data.

Thanks all you do.

Regards,
~Gary


-----Original Message-----
From: Oliver Gorwits [mailto:ol...@cp...] 
Sent: Tuesday, December 23, 2014 10:22
To: net...@li...
Subject: Re: [Netdisco] Find nodes by vendor (using MAC address OUI)?

Hi Gary,

First of all, thanks for upgrading! It's rare that a Netdisco 1 feature doesn't exist in Netdisco 2. (The main reason would be that the feature was already broken or misguided in some way.)

On 2014-12-23 14:32, Sckolnick, Gary wrote:
> For example, on ND1 we
> can search Nodes for 0023ae and find all of the Dell devices on our 
> network.  The same search on ND2 returns "No matching records."

This should work fine but you'll need to give a little hint by specifying as a wildcard search and with colons:

00:23:ae*

Alternatively if you already know the vendor name, use the built-in Node Vendor Inventory report which is under the Reports -> Node menu.

I hope this helps, and do ask if you can't find anything else,

regards,
oliver.



> Our ND2 installation:
>
> Software 	Version
> App::Netdisco 	2.029014
> DB Schema 	v39
> Dancer 	1.3132
> Bootstrap 	2.3.1
> PostgreSQL 	PostgreSQL 8.4.20 on x86_64-redhat-linux-gnu, compiled by
> GCC gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4), 64-bit.
>  DBI 1.631, DBD::Pg 2.15.1
> SNMP::Info 	3.23
> Perl 	5.010001
>
>
> Thank you,
> ________________________
> Gary Sckolnick
> Network Engineer
> Information Services
> (802) 847-2541
> Gar...@UV...
> The University of Vermont Medical Center UVMHealth.org/MedCenter
>
>
>
> This message and any attachments may contain information that is
> confidential, privileged and/or protected from disclosure under state
> and federal laws.  If you received this message in error or through
> inappropriate means, please reply to this message to notify the 
> Sender
> that the message was received by you in error, and then permanently
> delete this message from all storage media, without forwarding or
> retaining a copy.
>
> 
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, 
> is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. 
> Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Netdisco mailing list
> net...@li...
> https://lists.sourceforge.net/lists/listinfo/netdisco-users


------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Netdisco mailing list
net...@li...
https://lists.sourceforge.net/lists/listinfo/netdisco-users


This message and any attachments may contain information that is confidential, privileged and/or protected from disclosure under state and federal laws.  If you received this message in error or through inappropriate means, please reply to this message to notify the Sender that the message was received by you in error, and then permanently delete this message from all storage media, without forwarding or retaining a copy.