We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am not very very old, just plain old, and I suspect there is a historic reason in the product heritage, however ...
Layer3/Aruba.pm (for the wireless controller products), generates the OS name "airos". However, these days, that seems wrong.
This was perhaps correct once upon a time, but for some years Aruba have referred to the wireless operating system as "ArubaOS" or "AOS".
These days, the name "AirOS" is used by (some?) Ubiquity products, which is what Layer2/Ubiquiti.pm returns under some circumstances.
I'd suggest Aruba.pm should be changed to return "aos" or "arubaos" (the latter being nearer to "arubaos-cx", as used for the OS-CX products).
This all somewhat relates to #469.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I am not very very old, just plain old, and I suspect there is a historic reason in the product heritage, however ...
Layer3/Aruba.pm (for the wireless controller products), generates the OS name "airos". However, these days, that seems wrong.
This was perhaps correct once upon a time, but for some years Aruba have referred to the wireless operating system as "ArubaOS" or "AOS".
These days, the name "AirOS" is used by (some?) Ubiquity products, which is what Layer2/Ubiquiti.pm returns under some circumstances.
I'd suggest Aruba.pm should be changed to return "aos" or "arubaos" (the latter being nearer to "arubaos-cx", as used for the OS-CX products).
This all somewhat relates to #469.
The text was updated successfully, but these errors were encountered: