Send netdisco-users mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics: 1. Re: Trashing the DB to start again (Oliver Gorwits) 2. Re: Multiple interfaces on routers (Oliver Gorwits) 3. Re: Detect device as Checkpoint (Oliver Gorwits)
--- Begin Message ---Hi all, If you do not have root/postgres user access, there is another way: DROP OWNED BY netdisco; then run netdisco-deploy. https://github.com/netdisco/netdisco/wiki/Database-TipsThis assumes your netdisco DB user is "netdisco. And as mentioned by others, make sure you have a working restore copy if you need it!regards, oliver. On 2017-12-14 17:41, Hans Erasmus wrote:Thank you guys. I am not familiar with prostgre or netdisco (yet) so I wanted the safest way to do it. Thanks for all the help! Regards Hans On Thu, 14 Dec 2017 at 18:50 Andy Ruhl <[email protected]> wrote:On Wed, Dec 13, 2017 at 7:41 PM, Sanjeev Gupta <[email protected]> wrote:(top posting, sorry). This should work: Drop the netdisco database from postgresql Recreate: postgres:~$ createdb -O netdisco netdisco Intialise the new database: ~/bin/netdisco-deployI would rename it (log in with netdisco-do psql): ALTER DATABASE name RENAME TO new_name Then create the database again as stated above. When you're really sure you don't want the old database, drop it: DROP DATABASE name (<--- Make sure you drop the renamed one and not the "netdisco" one) Andy------------------------------------------------------------------------------Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot [1] _______________________________________________ Netdisco mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/netdisco-users [2]Links: ------ [1] http://sdm.link/slashdot [2] 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 [email protected] https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---On 2017-12-14 17:44, Hans Erasmus wrote:I started running a discover all job, which will take about a week. But I can already see that the duplicate devices has decreased during this discovery and we are on day 1. So I will keep you posted as we go along but thus far all looks good. Thanks for the trouble you guys are having updating the code and helping us out.Good to hear :-)I was reluctant to implement a "delete all" button because the list in the Duplicate Devices report is *all* devices, including (probably) the ones you want to keep. Also it's a bit of a guess based on the serial number and other properties, so I was cautious in case there are legitimate (?!) cases we aren't aware of.regards, Oliver.Regards Hans On Wed, 13 Dec 2017 at 20:17 Hans Erasmus <[email protected]> wrote:HI Oliver So here is the output: [netdisco@v-netdisco-tst-lnx1 ~]$ bin/localenv cpanmhttps://cpan.metacpan.org/authors/id/O/OL/OLIVER/App-Netdisco-2.036012_003.tar.gz[1] --> Working onhttps://cpan.metacpan.org/authors/id/O/OL/OLIVER/App-Netdisco-2.036012_003.tar.gz[1] Fetchinghttps://cpan.metacpan.org/authors/id/O/OL/OLIVER/App-Netdisco-2.036012_003.tar.gz[1] ... OK Configuring App-Netdisco-2.036012_003 ... OK ==> Found dependencies: aliased, Plack::Handler::Twiggy, Plack::Middleware::Debug, Env::Path, SNMP::Info --> Working on aliased Fetching http://www.cpan.org/authors/id/E/ET/ETHER/aliased-0.34.tar.gz [2] ... OK Configuring aliased-0.34 ... OK Building and testing aliased-0.34 ... OK Successfully installed aliased-0.34 --> Working on Plack::Handler::Twiggy Fetching http://www.cpan.org/authors/id/M/MI/MIYAGAWA/Twiggy-0.1025.tar.gz [3] ... OK Configuring Twiggy-0.1025 ... OK ==> Found dependencies: Test::Requires --> Working on Test::Requires Fetchinghttp://www.cpan.org/authors/id/T/TO/TOKUHIROM/Test-Requires-0.10.tar.gz[4] ... OK Configuring Test-Requires-0.10 ... OK Building and testing Test-Requires-0.10 ... OK Successfully installed Test-Requires-0.10 Building and testing Twiggy-0.1025 ... OK Successfully installed Twiggy-0.1025 --> Working on Plack::Middleware::Debug Fetchinghttp://www.cpan.org/authors/id/M/MI/MIYAGAWA/Plack-Middleware-Debug-0.16.tar.gz[5] ... OK Configuring Plack-Middleware-Debug-0.16 ... OK ==> Found dependencies: Text::MicroTemplate --> Working on Text::MicroTemplate Fetchinghttp://www.cpan.org/authors/id/K/KA/KAZUHO/Text-MicroTemplate-0.24.tar.gz[6] ... OK Configuring Text-MicroTemplate-0.24 ... OK Building and testing Text-MicroTemplate-0.24 ... OK Successfully installed Text-MicroTemplate-0.24 Building and testing Plack-Middleware-Debug-0.16 ... OK Successfully installed Plack-Middleware-Debug-0.16 --> Working on Env::Path Fetching http://www.cpan.org/authors/id/D/DS/DSB/Env-Path-0.19.tar.gz [7] ... OK Configuring Env-Path-0.19 ... OK Building and testing Env-Path-0.19 ... OK Successfully installed Env-Path-0.19 --> Working on SNMP::Info Fetching http://www.cpan.org/authors/id/O/OL/OLIVER/SNMP-Info-3.38.tar.gz [8] ... OK Configuring SNMP-Info-3.38 ... OK Building and testing SNMP-Info-3.38 ... OK Successfully installed SNMP-Info-3.38 (upgraded from 3.37) Building and testing App-Netdisco-2.036012_003 ... OK Successfully installed App-Netdisco-2.036012_003 8 distributions installed [netdisco@v-netdisco-tst-lnx1 ~]$ [netdisco@v-netdisco-tst-lnx1 ~]$ [netdisco@v-netdisco-tst-lnx1 ~]$ [netdisco@v-netdisco-tst-lnx1 ~]$ [netdisco@v-netdisco-tst-lnx1 ~]$ bin/netdisco- netdisco-backend netdisco-backend-fg netdisco-daemon netdisco-daemon-fg netdisco-db-deploy netdisco-deploy netdisco-do netdisco-rancid-export netdisco-sshcollector netdisco-web netdisco-web-fg [netdisco@v-netdisco-tst-lnx1 ~]$ bin/netdisco-deploy This is the Netdisco II deployment script. Before we continue, the following prerequisites must be in place: * Database added to PostgreSQL for Netdisco * User added to PostgreSQL with rights to the Netdisco Database * "~/environments/deployment.yml" file configured with Database dsn/user/pass * A full backup of any existing Netdisco database data * Internet access (for OUIs and MIBs) You will be asked to confirm all changes to your system. So, is all the above in place? [y/N]: y Would you like to deploy the database schema? [y/N]: y DBIx::Class::Schema::Versioned::_on_connect(): Versions out of sync. This is 45, your database contains version 44, please call upgrade on your Schema. at /home/netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 95 DBIx::Class::Schema::Versioned::upgrade_single_step(): DB version (44) is lower than the schema version (45). Attempting upgrade. DB schema update complete. Download and update vendor MAC prefixes (OUI data)? [y/N]: y OUI update complete. Download and update MIB files? [y/N]: y MIBs update complete. [netdisco@v-netdisco-tst-lnx1 ~]$ [netdisco@v-netdisco-tst-lnx1 ~]$ [netdisco@v-netdisco-tst-lnx1 ~]$ [netdisco@v-netdisco-tst-lnx1 ~]$ [netdisco@v-netdisco-tst-lnx1 ~]$ bin/netdisco-daemon netdisco-daemon netdisco-daemon-fg [netdisco@v-netdisco-tst-lnx1 ~]$ bin/netdisco-daemon ? Error: undefined action ?. Must be called with an action:[start|stop|restart|reload|status|foreground|show_warnings|get_init_file|help]at /home/netdisco/perl5/lib/perl5/Daemon/Control.pm line 690. [netdisco@v-netdisco-tst-lnx1 ~]$ bin/netdisco-daemon --help Syntax: /home/netdisco/perl5/bin/netdisco-backend[start|stop|restart|reload|status|foreground|show_warnings|get_init_file|help][netdisco@v-netdisco-tst-lnx1 ~]$ bin/netdisco-daemon status Netdisco Backend [Running] [netdisco@v-netdisco-tst-lnx1 ~]$ [netdisco@v-netdisco-tst-lnx1 ~]$ [netdisco@v-netdisco-tst-lnx1 ~]$ [netdisco@v-netdisco-tst-lnx1 ~]$ bin/netdisco-daemon restart Netdisco Backend [Stopped] config watcher: watching /home/netdisco/environments for updates. Netdisco Backend [Started] [netdisco@v-netdisco-tst-lnx1 ~]$ Running the Admin > Duplicate devices, I see 328 Entries, so it seems to work quite well. Question, do you have an idea for delete all button? :-) Thanks again for this! Regards Hans On Sat, 9 Dec 2017 at 21:00 Hans Erasmus <[email protected]> wrote: Hi Oliver Will do so on Monday. Thanks for letting me know. I will be submitting the feature request for a Ruijie class probably withon a month or so. Will try this and let you know! Thanks again! Have a nice weekend Hans On Sat, 09 Dec 2017, 14:31 Oliver Gorwits, <[email protected]> wrote: Hi Hans We have a new version of Netdisco on CPAN in "development/testing" release status which has significantly rewritten device discovery and deduplication code. If you would like to try it out: ~netdisco/bin/localenv cpanmhttps://cpan.metacpan.org/authors/id/O/OL/OLIVER/App-Netdisco-2.036012_003.tar.gz[1] You should also run ~netdisco/bin/netdisco-deploy after, to update the DB schema, and then restart the backend daemon. Either remove all devices or remove duplicate devices through the Admin menu report "Duplicate Devices". Then future discover jobs will hopefully not throw up duplicates! Do let me know how you get on. regards, oliver. On 2017-08-22 08:26, Hans Erasmus wrote:Oh and I should add, where this thing is really showing is in the Network Maps (drawing of device). It will show that one routerhas40 connections to the USR-BB, where in fact, it will only haveone.Regards Hans On Tue, 22 Aug 2017 at 09:22 Hans Erasmus<[email protected]>wrote:Hi Oliver No need to apologise. This is something one of our guru's hasbeenseeing for the past 10 years, and his fix was to assign a typeofprimary key to the device once it is discovered. I will get more detail on it and post it if you are interested. So thebehaviouris not new, and therefore not surprising. It is just way outof myleague to even try and attempt a fix for this.Please can you tell me what the Duplicate Devices report (intheAdminmenu) shows? Are all the duplicates listed there? Well, I see a lot of duplicates on this list (293 to be exactbutthe discovery is still running) like our PC LAB routers whichhavemultiple interfaces with multiple subnets connected to it. For instance: 1 x /27 containing the Switch IP segment (SW MGMT) 1 x /24 containing the LAB PC segment (End Users) 1 x /31 containing the Uplinks to the User Backbone 1 or 2 (sometimes more) /30 interconnects between LAB routers to ensure redundancy (multiple paths).Also, can you let me know why you think "practically" this ishappening? Well, in layman's terms, what happens is that as Netdisco goes through the network whilst discovering, it will come across anIPof say 1.1.1.1 on a router. This IP could possibly be the gateway for 1.1.1.0/24 [9] [3]. Now, taking the example above,let saythis /24 is the end-user segment. This same router couldpossiblycontain, like in our case, a different routed segment to servicetheswitch segment. Let call this 1.1.2.0/27 [10] [4]. So the routermusthave 1.1.2.1 configured as the gateway so the switches knowswhereto go. Only using these two segments as an example, we can clearly seethatone router could contain two different network segments and actas aGateway for both, and the one segment will not necessarily know about the other. This helps in containing outages created byloopsetc. btw. In the eyes of Netdisco, these are two totallydifferentdevices, as these two segments do not overlap, or are not partofone another in any shape or form. And these two segments couldhavebeen physically living across campus from each other. SoNetdisco(and any other discoverer worth it's salt) would handle these segments separately. It will add 1.1.1.1 as a device, and add 1.1.2.1 as a device. But in reality, it is the same device. Somaybenetdisco could, when it discovers a new segment, first inspect whether anything on that segment has been found on any of the already discovered device's address tables, and only append theliston that discovered device, not add a new device, I don't know?Justthrowing out ideas here. To answer your last question, no, we do not make use of anyVRF's.Sorry if this explanation is not explanatory enough. Regards Hans On Tue, 22 Aug 2017 at 08:44 Oliver Gorwits <[email protected]>wrote:Hi Hans On 2017-08-22 06:40, Hans Erasmus wrote:When a router comes up that has more than one interface (ouruserbackbone has 40 x /31's), netdisco will list that device asdiscovered40 times.We have started to look at this issue, but are being cautiousinautomatically de-duplicating in case there are scenarios where multiple devices should remain. Please can you tell me what the Duplicate Devices report (intheAdmin menu) shows? Are all the duplicates listed there? Also, can you let me know why you think "practically" this is happening? Finally, are you using VRFs? Many thanks, and apologies for the hassle this is causing. regards, oliver.Is there any way (a script perhaps) in which we can tell netdisco that it is the same device all along? Maybe havesome sortof intelligent "check" whether the device discovered has thesame nameor any other details as any of the devices in the listalready,andthen flag it and ignore it from there? Just a thought. Regards Hans------------------------------------------------------------------------------Check out the vibrant tech community on one of the world'smostengaging tech sites, Slashdot.org! http://sdm.link/slashdot[11] [1]_______________________________________________ Netdisco mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/netdisco-users[12] [2]------------------------------------------------------------------------------Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot[11] [1]_______________________________________________ Netdisco mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/netdisco-users[12] [2]Links: ------ [1] http://sdm.link/slashdot [11] [2] https://lists.sourceforge.net/lists/listinfo/netdisco-users[12][3] http://1.1.1.0/24 [9] [4] http://1.1.2.0/27 [10]------------------------------------------------------------------------------Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot [11] _______________________________________________ Netdisco mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/netdisco-users [12]Links: ------ [1] https://cpan.metacpan.org/authors/id/O/OL/OLIVER/App-Netdisco-2.036012_003.tar.gz [2] http://www.cpan.org/authors/id/E/ET/ETHER/aliased-0.34.tar.gz [3] http://www.cpan.org/authors/id/M/MI/MIYAGAWA/Twiggy-0.1025.tar.gz[4] http://www.cpan.org/authors/id/T/TO/TOKUHIROM/Test-Requires-0.10.tar.gz[5] http://www.cpan.org/authors/id/M/MI/MIYAGAWA/Plack-Middleware-Debug-0.16.tar.gz[6] http://www.cpan.org/authors/id/K/KA/KAZUHO/Text-MicroTemplate-0.24.tar.gz[7] http://www.cpan.org/authors/id/D/DS/DSB/Env-Path-0.19.tar.gz [8] http://www.cpan.org/authors/id/O/OL/OLIVER/SNMP-Info-3.38.tar.gz [9] http://1.1.1.0/24 [10] http://1.1.2.0/27 [11] http://sdm.link/slashdot [12] https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---Hi Cedric, On 2017-12-13 15:27, Delaunay Cedric wrote:Hi all, I try to ensure netdisco detect our physical checkpoint firewalls but I'm unable to make it run...You probably want the "ssh collector" helper script, which can retrieve ARP entries from the firewall:https://metacpan.org/pod/distribution/App-Netdisco/bin/netdisco-sshcollector together with the standard Discover, it should be enough. regards, oliver.On first try, discover dectects it as layer2 device so I applyed this patch : http://netdisco-users.narkive.com/tTHHPnmv/checkpoint-firewall-no-arp-cache-polling-since-upgrade-from-ipso-to-gaia-os#post3 This is better as it now detect interfaces but it stops on SNMP::Info's mib and never use checkpint's mib. here is a delete/discover of the device. does anybody as an idee to help me ? Thanks a lot Cedric [netdisco@server ~]$ /home/netdisco/bin/netdisco-do delete -d 10.0.1.2 -DI [24983] 2017-12-13 15:25:39 info delete: started at Wed Dec 13 16:25:39 2017 [24983] 2017-12-13 15:25:39 info delete: finished at Wed Dec 13 16:25:39 2017 [24983] 2017-12-13 15:25:39 info delete: status done: Deleted device 10.0.1.2. [netdisco@server ~]$ /home/netdisco/bin/netdisco-do discover -d 10.0.1.2 -DI [25868] 2017-12-13 15:25:42 info discover: started at Wed Dec 13 16:25:42 2017 [25868] 2017-12-13 15:25:42 debug [10.0.1.2] try_connect with ver: 2, class: SNMP::Info, comm: SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance : .1.3.6.1.2.1.1.3.0 SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve method. SNMP::Info::_global(uptime) Timeout at /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/SNMP.pm line 176. [25868] 2017-12-13 15:25:45 debug [10.0.1.2] try_connect with ver: 1, class: SNMP::Info, comm: SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance : .1.3.6.1.2.1.1.3.0 SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve method. SNMP::Info::_global(uptime) Timeout at /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/SNMP.pm line 176. [25868] 2017-12-13 15:25:48 debug [10.0.1.2] try_connect with ver: 2, class: SNMP::Info, comm: SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance : .1.3.6.1.2.1.1.3.0 SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0 SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve method. SNMP::Info::_global(layers) NOSUCHINSTANCE at /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/SNMP.pm line 176. SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 : .1.3.6.1.2.1.1.1.0 SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve method. Device doesn't implement sysServices but did return sysDescr. Might give unexpected results. at /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/SNMP.pm line 155. SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 : .1.3.6.1.2.1.1.2.0 SNMP::Info 3.34 SNMP::Info::device_type() layers:00000000 id:2620 sysDescr:"Linux ckp-iutsm1 2.6.18-92cpx86_64 #1 SMP Fri Apr 7 13:55:39 IDT 2017 x86_64" SNMP::Info::_load_attr ip_index : IP-MIB::ipAdEntIfIndex : .1.3.6.1.2.1.4.20.1.2 SNMP::Info::_load_attr interfaces : IF-MIB::ifIndex : .1.3.6.1.2.1.2.2.1.1 SNMP::Info::_load_attr ip_netmask : IP-MIB::ipAdEntNetMask : .1.3.6.1.2.1.4.20.1.3 [25868] 2017-12-13 15:25:48 debug [10.0.1.2] device - aliased as XXXXXXXXXX ............... [25868] 2017-12-13 15:25:48 debug [10.0.1.2] device - aliased as YYYYYYYYYY [25868] 2017-12-13 15:25:48 debug resolving 23 aliases with max 50 outstanding requests SNMP::Info::_validate_autoload_method(vtp_d_name) Unable to resolve method. SNMP::Info::_global contact : SNMPv2-MIB::sysContact.0 : .1.3.6.1.2.1.1.4.0 SNMP::Info::_global name : SNMPv2-MIB::sysName.0 : .1.3.6.1.2.1.1.5.0 SNMP::Info::_global location : SNMPv2-MIB::sysLocation.0 : .1.3.6.1.2.1.1.6.0 SNMP::Info::_global ports : IF-MIB::ifNumber.0 : .1.3.6.1.2.1.2.1.0 SNMP::Info::_validate_autoload_method(mac) Unable to resolve method. SNMP::Info::_validate_autoload_method(ps1_type) Unable to resolve method. SNMP::Info::_validate_autoload_method(ps2_type) Unable to resolve method. SNMP::Info::_validate_autoload_method(ps1_status) Unable to resolve method. SNMP::Info::_validate_autoload_method(ps2_status) Unable to resolve method. SNMP::Info::_validate_autoload_method(fan) Unable to resolve method. SNMP::Info::_validate_autoload_method(slots) Unable to resolve method. SNMP::Info::_validate_autoload_method(vendor) Unable to resolve method. SNMP::Info::_validate_autoload_method(os) Unable to resolve method. SNMP::Info::_validate_autoload_method(os_ver) Unable to resolve method. SNMP::Info::_validate_autoload_method(model) Unable to resolve method. SNMP::Info::_validate_autoload_method(serial) Unable to resolve method. [25868] 2017-12-13 15:25:48 debug [10.0.1.2] device - removed 0 aliases [25868] 2017-12-13 15:25:48 debug [10.0.1.2] device - added 23 new aliases SNMP::Info::_load_attr i_type : IF-MIB::ifType : .1.3.6.1.2.1.2.2.1.3 SNMP::Info::_validate_autoload_method(i_ignore) Unable to resolve method. SNMP::Info::_load_attr i_description : IF-MIB::ifDescr : .1.3.6.1.2.1.2.2.1.2 SNMP::Info::_load_attr i_mtu : IF-MIB::ifMtu : .1.3.6.1.2.1.2.2.1.4 SNMP::Info::_load_attr orig_i_speed : IF-MIB::ifSpeed : .1.3.6.1.2.1.2.2.1.5 SNMP::Info::_load_attr i_mac : IF-MIB::ifPhysAddress : .1.3.6.1.2.1.2.2.1.6 SNMP::Info::_load_attr i_up : IF-MIB::ifOperStatus : .1.3.6.1.2.1.2.2.1.8 SNMP::Info::_load_attr i_up_admin : IF-MIB::ifAdminStatus : .1.3.6.1.2.1.2.2.1.7 SNMP::Info::_load_attr i_name : IF-MIB::ifName : .1.3.6.1.2.1.31.1.1.1.1 SNMP::Info::_validate_autoload_method(i_duplex) Unable to resolve method. SNMP::Info::_validate_autoload_method(i_duplex_admin) Unable to resolve method. SNMP::Info::_validate_autoload_method(i_stp_state) Unable to resolve method. SNMP::Info::_validate_autoload_method(i_vlan) Unable to resolve method. SNMP::Info::_load_attr i_lastchange : IF-MIB::ifLastChange : .1.3.6.1.2.1.2.2.1.9 SNMP::Info::_validate_autoload_method(agg_ports) Unable to resolve method. SNMP::Info::_global load_uptime : DISMAN-EVENT-MIB::sysUpTimeInstance : .1.3.6.1.2.1.1.3.0 SNMP::Info::_global snmpEngineTime : SNMP-FRAMEWORK-MIB::snmpEngineTime.0 : .1.3.6.1.6.3.10.2.1.3.0 [25868] 2017-12-13 15:25:48 debug [10.0.1.2] interfaces - removed 0 interfaces [25868] 2017-12-13 15:25:48 debug [10.0.1.2] interfaces - added 14 new interfaces SNMP::Info::_validate_autoload_method(i_ssidlist) Unable to resolve method. SNMP::Info::_validate_autoload_method(v_name) Unable to resolve method. SNMP::Info::_validate_autoload_method(v_index) Unable to resolve method. SNMP::Info::_validate_autoload_method(i_vlan) Unable to resolve method. SNMP::Info::_validate_autoload_method(i_vlan_membership) Unable to resolve method. SNMP::Info::_validate_autoload_method(i_vlan_type) Unable to resolve method. [25868] 2017-12-13 15:25:49 debug [10.0.1.2] vlans - removed 0 device VLANs [25868] 2017-12-13 15:25:49 debug [10.0.1.2] vlans - added 0 new device VLANs [25868] 2017-12-13 15:25:49 debug [10.0.1.2] vlans - removed 0 port VLANs [25868] 2017-12-13 15:25:49 debug [10.0.1.2] vlans - added 0 new port VLANs SNMP::Info::_validate_autoload_method(peth_power_watts) Unable to resolve method. SNMP::Info::_validate_autoload_method(peth_power_status) Unable to resolve method. [25868] 2017-12-13 15:25:49 debug [10.0.1.2] power - 0 power modules SNMP::Info::_validate_autoload_method(e_index) Unable to resolve method. [25868] 2017-12-13 15:25:49 debug [10.0.1.2] modules - removed 0 chassis modules [25868] 2017-12-13 15:25:49 debug [10.0.1.2] modules - 0 chassis components (added one pseudo for chassis) [25868] 2017-12-13 15:25:49 debug [10.0.1.2] neigh - setting manual topology links SNMP::Info::_validate_autoload_method(hasLLDP) Unable to resolve method. SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method. SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method. SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method. SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method. SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method. SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method. [25868] 2017-12-13 15:25:49 debug [10.0.1.2] neigh - CDP/LLDP not enabled! [25868] 2017-12-13 15:25:49 info discover: finished at Wed Dec 13 16:25:49 2017 [25868] 2017-12-13 15:25:49 info discover: status done: Ended discover for 10.0.1.2 [netdisco@berger2 ~]$ Delaunay Cedric - [email protected] ------------------------------------------------------------------------------ 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 [email protected] 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 [email protected] https://lists.sourceforge.net/lists/listinfo/netdisco-users
