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: New install failed to find a number of devices.
Recommendations for determining failure points and cleaning up
database? (Oliver Gorwits)
2. Re: Sub-interface folding in Port view (Oliver Gorwits)
3. Re: Can we add custom tags? Trying to get phone extensions
mapped (Oliver Gorwits)
--- Begin Message ---
Hi David
The different errors you describe all relate to the "Device Modules" tab
entries, that is, the hardware components reported by the device. Invalid
parent means the report is somehow inconsistent with itself, and the
uninitialized error, while a bug in Netdisco, also points to some weird
data back from the device.
Unfortunately we don't have a feature in Netdisco to disable Entity
gathering (which would just skip this stuff and allow the rest to
continue). I've made a ticket for it:
https://github.com/netdisco/netdisco/issues/1126
The other option is to share with me the output of an snmpwalk if the
device will allow it, and I can see if I can reproduce the issue(s) and fix
them: https://github.com/netdisco/netdisco/wiki/Snapshot#share-a-snapshot
Oh, I guess the other hack you could do locally is copy "worker_plugins"
config from the default and remove the "Discover::Entities" item to disable
it. https://github.com/netdisco/netdisco/blob/master/share/config.yml
I also opened a ticket for the uninitialized value bug
https://github.com/netdisco/netdisco/issues/1127
Kind regards
Oliver.
On Tue, 14 Nov 2023 at 04:06, David Bertagni <dberta...@brynmawr.edu> wrote:
> Hi,
>
> Apologies if this is noted elsewhere and I missed it...
>
> I have an old instance, v2.39.19, on an old Ubuntu distribution that I'm
> replacing with a new from scratch instance, v2.68.1. I decided to not
> migrate anything but the basic configuration and allowed the new instance
> to find devices with a single seed to my core Juniper stack. It found
> _most_ of them, but I had to manually discover a dozen or so and I'm
> wondering how best to clean up the manual discovery as they all came up
> with "invalid parent" errors and a few reported this error:
> "Use of uninitialized value in sprintf at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Entities.pm
> line 109."
>
> I'm primarily a Juniper shop with some legacy HP and newer Aruba-CX type
> switches. I'm getting ready to deploy Extreme's universal switch line, as
> product becomes available.
>
> I'm not sure exactly why discovery failed as it was pretty random from my
> end. The switches are all configured identically and some were found while
> others skipped even on the same network.
>
> Happy to provide logs and other output as I'd like to get this instance up
> clean before retiring out the old.
>
> Thanks,
> David Bertagni
> Bryn Mawr College
>
>
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
>
--- End Message ---
--- Begin Message ---
Hi James,
To your second question first... see the setting
https://github.com/netdisco/netdisco/wiki/Configuration#table_pagesize and
the setting
https://github.com/netdisco/netdisco/wiki/Configuration#table_showrecordsmenu
Now, that is a great idea about the folding. I can see for aggregate links
it might also be nice. For the aggregates, we already know what the
interface groupings are. For what you describe, Netdisco needs some way to
work out the hierarchy (parent/child relation) of the interfaces, either by
SNMP for example in the ifStack MIB, or else some way you set a rule in
config. I've created a ticket here for you and anyone else to jot down
ideas while we work it out: https://github.com/netdisco/netdisco/issues/1128
Another option you have is to hide the interfaces if they're really not
useful/interesting. You don't say whether the parent or child interfaces
have the connected nodes and devices, for instance. Anyway, there is the
setting
https://github.com/netdisco/netdisco/wiki/Configuration#hide_deviceports
which allows you to set a rule to hide. You can see in the example in the
doc you set a port name and it should be possible to pick the ones you want
(subinterfaces or not) with the right regexp. Remember to include "op:and"
to combine rules in an ACL.
Hope this helps,
Kind regards
Oliver.
On Wed, 1 Nov 2023 at 12:41, James Dore <james.d...@new.ox.ac.uk> wrote:
> Hi -
>
> I'd like to tidy up the way our netdisco install deals with the sub-
> interfaces of our Juniper switches. When I view the Port information
> for a switch, I get one line each per physical interface and related
> sub-interface, e.g.
>
> ge-0/0/0
> ge-0/0/0.0 <- sub interface of ge-0/0/0
> ge-0/0/1
> ge-0/0/1.0 <- sub interface 1 of ge-0/0/1
> ge-0/0/1.1 <- sub interface 2 of ge-0/0/1
> etc
>
> - I'd like to be able to have a more hierachical list of ports and
> their sub-interfaces, for instance hiding the sub-interfaces until a
> link is clicked, similar to expanding a directory tree e.g.
>
> ge-0/0/0
> + ge-0/0/0.0
> ge-0/0/1
> + ge-0/0/1.0
> ge-0/0/1.1
>
> Can this be done? Otherwise there's a doubling up of information on the
> page. When the display only defaults to showing 10 lines, I can only
> see five ports without more faffing about! (can I alter the default
> number of lines displayed too?)
>
> Cheers,
> James
>
> --
> James Dore (He/Him)
> IT Technical Officer
> New College, Oxford, OX1 3BN
> 01865 279252 (Mon-Fri 0830-1600) - 01865 612345 All other
> www.new.ox.ac.uk
>
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Hi Ricardo
I've not seen any work on this, but we have a ticket here if you'd like to
add comment/interest/info: https://github.com/netdisco/netdisco/issues/973
Kind regards
Oliver.
On Tue, 24 Oct 2023 at 17:20, Ricardo Stella <ste...@rider.edu> wrote:
> Has anyone figured something out for this?
>
> It was suggested to look at using hooks, but not sure where to take this.
> I think it would be a great feature request - being able to search for
> specific fields like phone extensions in this case, or other fields from
> LLDP (ie AP name - for some reason this one is not showing up in connected
> nodes/devices)
>
> TIA.
>
> On Mon, Jan 3, 2022 at 1:49 PM Ricardo Stella <ste...@rider.edu> wrote:
>
>>
>> I've asked before back in March on how to get phone extensions via LLDP
>> but it seems that you would need discover_phones enabled, and iour
>> phones do not have SNMP enabled.
>>
>> In any case, the information is getting pulled as part of the
>> "remote_type" - Is there a way to map the contents (and ideally a
>> substring) into a custom field that can be displayed and/or searched for?
>>
>> Doing a discover -DIQ you can see remote_type includes the necessary
>> information: "reqDN 1177" whereas 1177 is the phone's extension. If we can
>> do this, we could map the model number of the phone as well "MINET_6920"
>> whereas 6920 is the model.
>>
>> [17616] 2022-01-03 18:27:52 debug [10.1.1.118] neigh - 10.10.7.142 with
>> ID [10.10.7.142] on GigabitEthernet1/0/13
>> SELECT me.ip, me.alias, me.subnet, me.port, me.dns, me.creation
>> FROM device_ip me
>> WHERE me.alias = '10.10.7.142' AND me.ip = '10.10.7.142'
>> SELECT me.ip, me.alias, me.subnet, me.port, me.dns, me.creation
>> FROM device_ip me
>> WHERE alias = '10.10.7.142'
>> SELECT me.ip, me.creation, me.dns, me.description, me.uptime, me.contact,
>> me.name, me.location, me.layers, me.num_ports, me.mac, me.serial,
>> me.chassis_id, me.model, me.ps1_type, me.ps2_type, me.ps1_status,
>> me.ps2_status, me.fan, me.slots, me.vendor, me.os, me.os_ver, me.log,
>> me.snmp_ver, me.snmp_comm, me.snmp_class, me.snmp_engineid, me.vtp_domain,
>> me.last_discover, me.last_macsuck, me.last_arpnip, to_char( me.creation,
>> 'YYYY-MM-DD HH24:MI' ), to_char( me.last_arpnip, 'YYYY-MM-DD HH24:MI' ),
>> to_char( me.last_discover, 'YYYY-MM-DD HH24:MI' ), to_char(
>> me.last_macsuck, 'YYYY-MM-DD HH24:MI' ), extract( epoch
>> FROM age( now( ), me.creation ) ), extract( epoch
>> FROM age( now( ), me.last_arpnip ) ), extract( epoch
>> FROM age( now( ), me.last_discover ) ), extract( epoch
>> FROM age( now( ), me.last_macsuck ) ), replace( age( timestamp
>> 'epoch' + me.uptime / 100 * interval '1 second', timestamp '1970-01-01
>> 00:00:00-00' ) ::text, 'mon', 'month' )
>> FROM device me
>> WHERE me.ip = '10.10.7.142'
>> [17616] 2022-01-03 18:27:52 debug is_discoverable: 10.10.7.142 matches
>> phone_platforms but discover_phones is not enabled
>> [17616] 2022-01-03 18:27:52 debug [10.1.1.118] neigh - skip: 10.10.7.142
>> of type [regDN 1177,MINET_6920,ver: 01.05.03.027,PxE: 6.5,03/01/2022
>> 13:27:23 +0000] excluded by discover_* config
>> UPDATE device_port
>> SET is_uplink = true, manual_topo = false, remote_id = '10.10.7.142',
>> remote_ip = '10.10.7.142', remote_port = 'LAN port', remote_type = 'regDN
>> 1177,MINET_6920,ver: 01.05.03.027,PxE: 6.5,03/01/2022 13:27:23 +0000'
>> WHERE ip = '10.1.1.118' AND port = 'GigabitEthernet1/0/13'
>> SELECT me.ip, me.port, me.creation, me.descr, me.up, me.up_admin,
>> me.type, me.duplex, me.duplex_admin, me.speed, me.speed_admin, me.name,
>> me.mac, me.mtu, me.stp, me.remote_ip, me.remote_port, me.remote_type,
>> me.remote_id, me.is_master, me.slave_of, me.manual_topo, me.is_uplink,
>> me.vlan, me.pvid, me.lastchange
>> FROM device_port me
>> WHERE me.ip = '10.1.1.118' AND me.port = 'GigabitEthernet1/0/13'
>>
>> Thanks in advance - Ricardo.
>>
>> --
>> °(((=((===°°°(((================================================
>>
>
>
> --
> °(((=((===°°°(((================================================
> _______________________________________________
> Netdisco mailing list
> 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
