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: wap_platforms and phone_platforms (Oliver Gorwits)
--- Begin Message ---
Hi,
You shouldn't need to mess with wap_platforms or wap_capabilities, if the
APs are fairly modern.
This is more likely that Netdisco doesn't recognise them as devices or they
are not responding to SNMP sufficiently. This is why the inaccessible icon
... nothing to do with AP and more to do with device discovery.
Simplest approach is to ignore them and allow the AP clients to appear on
the upstream switch port:
https://github.com/netdisco/netdisco/wiki/Configuration#macsuck_unsupported
regards
Oliver
On Wed, 4 Aug 2021 at 22:52, Ricardo Stella <[email protected]> wrote:
>
> Figure I ask before reinventing the wheel. Our Aruba APs don't seem to be
> recognized as access points. They only show a device is inaccessible
> icon. No entries for discover_waps so default of true should be in effect.
>
> For example, c_platform returns "ArubaOS (MODEL: 315), Version Aruba AP"
>
> Tried adding the whole string to test to deployment.yml but doesn't seem
> to work:
>
> wap_platforms:
> - 'ArubaOS (MODEL: 315), Version Aruba AP'
>
> Am I missing something? Thanks in advance.
>
> --
> °(((=((===°°°(((================================================
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
