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: Device fails to discover (Christian Ramseyer)
2. Re: Netdisco pooling arp from Aruba CX 8325 (Christian Ramseyer)
3. Re: Device fails to discover (Andy Ruhl)
--- Begin Message ---
Hi Andy
You can find the OIDs queried for serials with something like this:
netdisco-do discover -IS -d <ip> -D 2>&1 | grep -i serial
On some random Cisco here I get:
SNMP::Info::_load_attr e_serial :
ENTITY-MIB::entPhysicalSerialNum(42894) : .1.3.6.1.2.1.47.1.1.1.1.11.42894
SNMP::Info::_load_attr e_serial : ENTITY-MIB::entPhysicalSerialNum :
.1.3.6.1.2.1.47.1.1.1.1.11
The .42894 is the entity mib index for the chassis, which Netdisco
somehow figured out from the whole list of serials for cards, PSU etc.
You can look at the SNMP::Info action in isolation by running
netdisco-do show -IS -d <ip> -e e_serial
With this or by using snmpwalk, you can maybe see how the output between
the working/non-working devices differs? Maybe you can also share what
vendor/model this is so other people with the same gear can try?
Sorry not really a solution, but I hope it helps in debugging a bit further.
Cheers
Christian
On 02.12.20 23:19, Andy Ruhl wrote:
> I have a lot of devices which are failing to discover. I can't tell
> why it's happening.
>
> I ran discover with -DISQ to find the exact error but the output
> doesn't really tell me anything. The output sort of diverges in places
> and I don't understand why. They don't lead up to the same point the
> same way.
>
> For example, one device fails, and another works fine. Same model
> device, same firmware. The error is always this:
>
> [23047] 2020-12-02 22:17:22 info discover: status error: discover
> cancelled: x.x.x.x failed to return valid serial
>
> I tried updating Netdisco, the snmp packages on the OS (Linux) and
> rebooting the switch. None of this worked.
>
> If anyone has any ideas, I would appreciate it.
>
> Andy
>
>
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
--- End Message ---
--- Begin Message ---
Hi Igal
This is a very common problem with many device types, the ancient SNMP
standard MIBs for ARP don't work very well with the modern networking
world. The typical Netdisco workaround is to use the SSHCollector to SSH
into the device and return the output of "show arp" or a similar command.
This requires a little platform-specific piece of code. There doesn't
seem one to be for Aruba yet, but you can find examples here:
https://github.com/netdisco/netdisco/tree/master/lib/App/Netdisco/SSHCollector/Platform
Once you have this bit, check out the specific device_auth for the "tag:
sshexample" in the doc. With this you pass the username, password and
other SSH options to the device:
https://github.com/netdisco/netdisco/wiki/Configuration#device_auth
Once set up, the regular discovery process will then use the SSH backend
for ARP records.
Disclaimer: I have not touched a single Aruba device in my life and
don't know if they even support SSH, but if they do that should be the
way to go.
Cheers
Christian
On 29.11.20 10:26, Zuntz Igal wrote:
> Hi,
>
> We have Aruba CX 8325 switch is working as L2/L3 device.
>
> Arpnip on this switch appears to work successfully (no errors appear in
> the cli, and from tcpdump the data looks valid), however, the IP
> addresses from the vlans this switch routes on L3 are missing from
> netdisco (but can be found at the switch arp table).
>
> Any suggestion?
>
> Igal
>
>
>
>
>
>
>
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
--- End Message ---
--- Begin Message ---
Thank you. Unfortunately it's a device issue for whatever reason.
Really bizarre.
Andy
On Thu, Dec 3, 2020 at 1:38 AM Christian Ramseyer <ramse...@netnea.com> wrote:
>
> Hi Andy
>
> You can find the OIDs queried for serials with something like this:
>
> netdisco-do discover -IS -d <ip> -D 2>&1 | grep -i serial
>
> On some random Cisco here I get:
>
> SNMP::Info::_load_attr e_serial :
> ENTITY-MIB::entPhysicalSerialNum(42894) : .1.3.6.1.2.1.47.1.1.1.1.11.42894
>
> SNMP::Info::_load_attr e_serial : ENTITY-MIB::entPhysicalSerialNum :
> .1.3.6.1.2.1.47.1.1.1.1.11
>
> The .42894 is the entity mib index for the chassis, which Netdisco
> somehow figured out from the whole list of serials for cards, PSU etc.
>
> You can look at the SNMP::Info action in isolation by running
>
> netdisco-do show -IS -d <ip> -e e_serial
>
> With this or by using snmpwalk, you can maybe see how the output between
> the working/non-working devices differs? Maybe you can also share what
> vendor/model this is so other people with the same gear can try?
>
> Sorry not really a solution, but I hope it helps in debugging a bit further.
>
> Cheers
> Christian
>
> On 02.12.20 23:19, Andy Ruhl wrote:
> > I have a lot of devices which are failing to discover. I can't tell
> > why it's happening.
> >
> > I ran discover with -DISQ to find the exact error but the output
> > doesn't really tell me anything. The output sort of diverges in places
> > and I don't understand why. They don't lead up to the same point the
> > same way.
> >
> > For example, one device fails, and another works fine. Same model
> > device, same firmware. The error is always this:
> >
> > [23047] 2020-12-02 22:17:22 info discover: status error: discover
> > cancelled: x.x.x.x failed to return valid serial
> >
> > I tried updating Netdisco, the snmp packages on the OS (Linux) and
> > rebooting the switch. None of this worked.
> >
> > If anyone has any ideas, I would appreciate it.
> >
> > Andy
> >
> >
> > _______________________________________________
> > 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
