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. Avaya phones serial nr and new mibs ? (?ern? Lubom?r (UNP-RPA))
2. Re: Avaya phones serial nr and new mibs ? (Oliver Gorwits)
3. Re: Avaya phones serial nr and new mibs ? (Jethro R Binks)
4. Re: Avaya phones serial nr and new mibs ? (Oliver Gorwits)
5. Re: Access Point Client Count report gets empty when macsuck
is run by WWW GUI (Christian Ramseyer)
6. Re: Access Point Client Count report gets empty when macsuck
is run by WWW GUI (Jirka Novak)
--- Begin Message ---
Hi.
We have several Avaya VoIP phone and would like to get inventory in Netdisco2.
I tried to add new mib into ~/netdisco-mibs/ but discover is still not able to
get serial number.
No SN even for mibs included in Netdisco package aka Avaya 46xx and 96xx
New mibs for 16xx are on:
ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/1600/16xxmib15.txt
Any idea why netdisco can not read SN from Avaya ? The value can be read via
snmpget.
Thx.
Lubomir
--- End Message ---
--- Begin Message ---
Hi Lubomír,
On 2017-02-02 08:13, Černý Lubomír wrote:
We have several Avaya VoIP phone and would like to get inventory in
Netdisco2.
I tried to add new mib into ~/netdisco-mibs/ but discover is still not
able to get serial number.
In Netdisco, telephones are treated as "nodes" that are end-devices such
as workstations or printers. This page explains the difference between
nodes and devices:
https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod#Understanding-Nodes-and-Devices
So Netdisco only gets details such as serial number from the devices.
Nodes are only an IP/MAC-address entry.
I think Netdisco could possibly treat phones as devices (it's not common
for phones to have SNMP enabled, though), but it would need support in
the SNMP::Info library first.
regards,
oliver.
No SN even for mibs included in Netdisco package aka Avaya 46xx and
96xx
New mibs for 16xx are on:
ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/1600/16xxmib15.txt [1]
Any idea why netdisco can not read SN from Avaya ? The value can be
read via snmpget.
Thx.
Lubomir
Links:
------
[1] ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/1600/16xxmib15.txt
------------------------------------------------------------------------------
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 ---
VoIP handsets are also "device-like" in other ways as well: they often run
LLDP, take in tagged and untagged VLANs, and often have a pass-through
port for a connected PC so they are a bit bridgy-like too. But agree they
often don't run SNMP so you can't necessarily get at the info that might
be in them!
Here, I get the handsets number via its LLDP announcements, which I can
see from the switch.
Because they LLDP but don't SNMP, they show up as Inaccessible neighbours
in Netdisco (for me).
Jethro.
. . . . . . . . . . . . . . . . . . . . . . . . .
Jethro R Binks, Network Manager,
Information Services Directorate, University Of Strathclyde, Glasgow, UK
The University of Strathclyde is a charitable body, registered in
Scotland, number SC015263.
On Thu, 2 Feb 2017, Oliver Gorwits wrote:
> Hi Lubomír,
>
> On 2017-02-02 08:13, Černý Lubomír wrote:
> > We have several Avaya VoIP phone and would like to get inventory in
> > Netdisco2.
> >
> > I tried to add new mib into ~/netdisco-mibs/ but discover is still not
> > able to get serial number.
>
> In Netdisco, telephones are treated as "nodes" that are end-devices such
> as workstations or printers. This page explains the difference between
> nodes and devices:
>
> https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod#Understanding-Nodes-and-Devices
>
> So Netdisco only gets details such as serial number from the devices.
> Nodes are only an IP/MAC-address entry.
>
> I think Netdisco could possibly treat phones as devices (it's not common
> for phones to have SNMP enabled, though), but it would need support in
> the SNMP::Info library first.
>
> regards,
> oliver.
>
> > No SN even for mibs included in Netdisco package aka Avaya 46xx and
> > 96xx
> >
> > New mibs for 16xx are on:
> > ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/1600/16xxmib15.txt [1]
> >
> > Any idea why netdisco can not read SN from Avaya ? The value can be
> > read via snmpget.
> >
> > Thx.
> >
> > Lubomir
> >
> >
> >
> > Links:
> > ------
> > [1] ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/1600/16xxmib15.txt
> >
> > ------------------------------------------------------------------------------
> > 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-02 09:47, Jethro R Binks wrote:
VoIP handsets are also "device-like" in other ways as well: they often
run
LLDP, take in tagged and untagged VLANs, and often have a pass-through
port for a connected PC so they are a bit bridgy-like too. But agree
they
often don't run SNMP so you can't necessarily get at the info that
might
be in them!
Yes good point, it's worth looking at the default discover_no_type
setting:
https://metacpan.org/source/OLIVER/App-Netdisco-2.034002/share/environments/deployment.yml#L59
that ignores phones and wireless APs that might be offering LLDP/CDP but
no SNMP.
As an aside to anyone choosing to discover these as devices, just check
that your Netdisco is configured to scale (DB memory, number of workers,
etc) if you have many!
regards,
oliver.
Here, I get the handsets number via its LLDP announcements, which I can
see from the switch.
Because they LLDP but don't SNMP, they show up as Inaccessible
neighbours
in Netdisco (for me).
Jethro.
. . . . . . . . . . . . . . . . . . . . . . . .
.
Jethro R Binks, Network Manager,
Information Services Directorate, University Of Strathclyde, Glasgow,
UK
The University of Strathclyde is a charitable body, registered in
Scotland, number SC015263.
On Thu, 2 Feb 2017, Oliver Gorwits wrote:
Hi Lubomír,
On 2017-02-02 08:13, Černý Lubomír wrote:
> We have several Avaya VoIP phone and would like to get inventory in
> Netdisco2.
>
> I tried to add new mib into ~/netdisco-mibs/ but discover is still not
> able to get serial number.
In Netdisco, telephones are treated as "nodes" that are end-devices
such
as workstations or printers. This page explains the difference between
nodes and devices:
https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod#Understanding-Nodes-and-Devices
So Netdisco only gets details such as serial number from the devices.
Nodes are only an IP/MAC-address entry.
I think Netdisco could possibly treat phones as devices (it's not
common
for phones to have SNMP enabled, though), but it would need support in
the SNMP::Info library first.
regards,
oliver.
> No SN even for mibs included in Netdisco package aka Avaya 46xx and
> 96xx
>
> New mibs for 16xx are on:
> ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/1600/16xxmib15.txt [1]
>
> Any idea why netdisco can not read SN from Avaya ? The value can be
> read via snmpget.
>
> Thx.
>
> Lubomir
>
>
>
> Links:
> ------
> [1] ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/1600/16xxmib15.txt
>
> ------------------------------------------------------------------------------
> 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 ---
--- Begin Message ---
On 25.01.17 16:50, Jirka Novak wrote:
> I checked netdisco-daemon.log and I see that when macsuck runs for WLC
> host, it reports 0 found addresses. But when I run it with netdisco-do
> -D from CLI, it reports correct count of found addresses.
Hi Jirka
I also have this problem on our Airespace devices. So far I was able to
track it down to
App/Netdisco/Core/Macsuck.pm
-> _walk_fwtable()
-> $fw_mac = $snmp->fw_mac
coming back empty when executed from the Netdisco daemon. Other data
like $fw_port = $snmp->fw_port seems to be returned from the device just
fine at the same time.
This seems very strange since it should use the same code and settings
as when using the CLI.
I've also tried to increase snmptimeout (10 * 1000000) and snmpretries
(5) to no avail after Oliver suspected in #netdisco that this might help.
Maybe one of the seasoned devs on the list can make sense out of this,
otherwise I'll try to further track down the cause next week.
Christian
--- End Message ---
--- Begin Message ---
Hi Christian,
> I also have this problem on our Airespace devices. So far I was able to
> track it down to
>
> App/Netdisco/Core/Macsuck.pm
> -> _walk_fwtable()
> -> $fw_mac = $snmp->fw_mac
>
> coming back empty when executed from the Netdisco daemon. Other data
> like $fw_port = $snmp->fw_port seems to be returned from the device just
> fine at the same time.
>
> This seems very strange since it should use the same code and settings
> as when using the CLI.
>
> I've also tried to increase snmptimeout (10 * 1000000) and snmpretries
> (5) to no avail after Oliver suspected in #netdisco that this might help.
>
> Maybe one of the seasoned devs on the list can make sense out of this,
> otherwise I'll try to further track down the cause next week.
yesterday I track it to exactly same point with same result. I have one
more observation - when I restart netdisco-daemon service, it reads
clients correctly a few times. "a few times" is random - I seen it only
once, two or three times, than it stops to read it again.
I double checked SNMP communication and I'm pretty sure that SNMP code
asks for same OIDs and receives same answers from WLC during successful
and unsuccessful run.
Therefore it leads me to idea that there is some kind of concurrency or
sequence issue in code. But I'm not able to decide whether it is in SNMP
or Netdisco related part of code.
Sincerely yours,
Jirka Novak
--- 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
