Ubiquiti publicly rolls out UNMS Beta
-
Saw the email earlier might give it a go Monday/Tuesday
-
I did mine on Debian 9.1, and they both requires 2 GB on the system. If you do 1 GB, it throws an error and stops the process. I gave it 3 GB to hold both and they both seemed content.
-
@jaredbusch said in Ubiquiti officially rolls out UNMS:
The announcement says that you can manage Access Points. But does not state UniFi ones.
The website suggests it supports (or will support) Unifi APs and even mentions the Amplifi series. That would be nice for helping manage family members home stuff easily when necessary.
This really looks like a central console for all of their devices to eventually fold into. No more Unifi controller for this, Edge web GUI for that, etc. One big controller to rule them all. Pretty sleek if they can keep it from growing too bloated over time.
-
@bigbear ABout to make a backup of the current VM and upgrade. so answers coming soon to some of the other questions.
But here is how I configured the VM.
-
1 GB runs pretty badly. I would do 2 GB or more for multiple sites.
-
Breaking changes
- It has been recommended for a while to have at least 2GB RAM for UNMS. This version can utilize them and it's highly probable that this version will not work with 1 GB even if your instance is running with 1 GB now.
- It is important to use at least airMAX FW 8.4.3+ or 6.1.3+. UNMS discovery will require these versions because previous versions don't have reliable UNMS connector.
- UNMS 0.11.0 doesn't support attribute –ssl-cert-ca and it's necessary to generate one full-chain certificate.
Added
- Add AirCube dashboard screen.
- Add AirCube backups screen.
- Add AirCube clients screen.
- Add airMAX stations screen.
- Add support for OpenStreetMap.
- Add integration to UBNT FW API for automatic FW download.
- Add NGINX reverse proxy.
- Add support for unknown device type which represents devices in problematic state. These devices have refresh button which should fix connection problem or provide steps hot fix connection. This should replace necessity of any manual update of data in PostgreSQL DB.
- Add integration to UBNT news. It's possible to see important UBNT news in UNMS UI.
- Add Let's Encrypt certificate warning note to installation wizard.
- Add columns hostname, SSID and ram to devices list.
- Add EdgeSwitch IP to devices list.
- Add error to event log when SSL cert renewal fails.
Changed
- Completely new UNMS/devices communication layer which has a significantly better performance per one CPU core.
- Upgrade to uWebSockets, NodeJS 9.1 and it's new V8 engine.
- Upgrade communication profiles and add a new minimal communication profile for low data usage.
- Remove unnecessary country in an address autocomplete.
- Return HTTP code 401 for non-existing user.
- Extend help for device refresh action.
- Change EdgeRouter backup filetype extension to tar.gz.
- Change minimal support version for EdgeSwicth to 1.7.3.
- Fill in a default username ubnt to all login forms.
- Improve device deleted event log format.
- Don't download FW during UNMS installation.
- Don't allow blocking of switched ports.
- Hide elevation input in sites/clients form.
- Round ONU signal strength.
- Modify colour spectrum and range for signal mini graphs.
- Switch signal graph to line graph.
- Show device alias name in logs and outages if exists.
- Show only sites in clients panel.
- Show error message when auto backup before UNMS update fails.
- Show missing toaster message for backups.
- Change outages default value in filter to 48h.
- Change username minimal length from 4 to 1.
- Improve Google Maps API key documentation.
- Devices menu item name dynamically change by wireless mode Stations/AccessPoint.
- Rename endpoints to clients.
Fixed
- Fix airMAX signal statistics.
- Fix airMAX excessive backups creation.
- Fix airMAX model detection.
- Fix airMAX menu rendering.
- Fix airRouter HP model recognition.
- Fix AirCube in demo mode.
- Fix AirCube PoE tag.
- Fix OLT reconnection.
- Fix OLT interfaces rendering.
- Fix OLT PON filter.
- Fix ONU restart.
- Fix ONU upgrade.
- Fix ONU speed values.
- Fix EdgeSwitch reboot.
- Fix EdgeRouter DHCP configuration.
- Fix EdgeRouter switch configuration.
- Fix EdgeRouter OSPF configuration.
- Fix EdgeRouter interfaces rendering.
- Fix EdgeRouter bridge connection status.
- Fix EdgeRouter FW upgrade (removing old FW).
- Fix devices backups CRC computation.
- Fix rendering of last-seen attribute.
- Fix background UNMS tasks and improve their performance.
- Fix multiple bugs which could lead to server crash.
- Fix custom UNMS device settings.
- Fix support for R5T.
- Fix support fo EPS16.
- Fix FW update tasks.
- Fix unread counts in left menu.
- Fix selecting a period in logs filter.
- Fix google maps endpoints markers.
- Fix UNMS settings form (Device ping address, backup maintenance options, etc.).
- Fix site status synchronisation.
- Fix refreshing of tasks upgrade status.
- Fix rendering of discovery popups.
Known issues which will be fixed in 0.11.1
- UNMS 0.11.0 doesn't support attribute –ssl-cert-ca and it's necessary to generate one full-chain certificate for a custom certificate.
- Problems with SMTP configuration.
- EdgeSwitch in UNMS discovery doesn't have FW version.
- Support for airMAX FW 8.5.x+.
- UNMS show 127.0.0.1 address instead of real one for all radios without "default route" in routing table.
- Bad sorting by SSID.
-
So, no UniFi yet.
-
But it looks like EdgeSwitch is in now. I have one I can test with that.
-
Ah, EdgeSwitch firmware 1.7.3 is still in beta
Will not be able to test as the switch is in production.
-
@jaredbusch said in Ubiquiti officially rolls out UNMS:
Ah, EdgeSwitch firmware 1.7.3 is still in beta
Will not be able to test as the switch is in production.
Might install it tomorrow as it looks like I'm off due to snow and working from home. Might try the beta firmware on the switch under my desk and see what happens lol
-
@hobbit666 said in Ubiquiti officially rolls out UNMS:
@jaredbusch said in Ubiquiti officially rolls out UNMS:
Ah, EdgeSwitch firmware 1.7.3 is still in beta
Will not be able to test as the switch is in production.
Might install it tomorrow as it looks like I'm off due to snow and working from home. Might try the beta firmware on the switch under my desk and see what happens lol
I have never had the beta firmware for any of the routers or switches cause a fail, but it is still not something I would do in production.
-
@jaredbusch it only powers my pc and other pc so it's ok to risk.
-
Website still show as beta?
Might leave it now until support for EdgeSwitch and Unifi came aboard. -
@hobbit666 said in Ubiquiti officially rolls out UNMS:
Website still show as beta?
No one ever said it was not beta. I said officially rolls out.
-
-
@jaredbusch said in Ubiquiti officially rolls out UNMS:
@hobbit666 said in Ubiquiti officially rolls out UNMS:
Website still show as beta?
No one ever said it was not beta. I said officially rolls out.
To normal people, officially released (or rolled out) means past beta. A beta release being "not released yet." The beta is released to the public, but the product is not. So you could say "UNMS Beta Officially Rolled Out", but not that "UNMS Officially Rolled Out".
If it was me having said it, you'd call it a term from "Scottland". People definitely universally use the term released to mean... well released. That the vendor sees the final product as now on the market.
-
@scottalanmiller said in Ubiquiti officially rolls out UNMS:
@jaredbusch said in Ubiquiti officially rolls out UNMS:
@hobbit666 said in Ubiquiti officially rolls out UNMS:
Website still show as beta?
No one ever said it was not beta. I said officially rolls out.
To normal people, officially released (or rolled out) means past beta. A beta release being "not released yet." The beta is released to the public, but the product is not. So you could say "UNMS Beta Officially Rolled Out", but not that "UNMS Officially Rolled Out".
If it was me having said it, you'd call it a term from "Scottland". People definitely universally use the term released to mean... well released. That the vendor sees the final product as now on the market.
The "public beta" state is a commonly accepted officially rolled out state for software products.
Many software products never leave "beta" and are officially out for years.
-
Title updated to make @scottalanmiller happy.
-
@jaredbusch said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti officially rolls out UNMS:
@jaredbusch said in Ubiquiti officially rolls out UNMS:
@hobbit666 said in Ubiquiti officially rolls out UNMS:
Website still show as beta?
No one ever said it was not beta. I said officially rolls out.
To normal people, officially released (or rolled out) means past beta. A beta release being "not released yet." The beta is released to the public, but the product is not. So you could say "UNMS Beta Officially Rolled Out", but not that "UNMS Officially Rolled Out".
If it was me having said it, you'd call it a term from "Scottland". People definitely universally use the term released to mean... well released. That the vendor sees the final product as now on the market.
The "public beta" state is a commonly accepted officially rolled out state for software products.
Many software products never leave "beta" and are officially out for years.
I don't know any product of that sort or anyone who uses that term. Do you have an example? And, I can tell you, if you show something in beta, it means it isn't released. So it's confusing to say that there is released beta products. They are competing terms. Released meaning "released" and beta meaning "not released." Public beta literally means an unreleased product that the public can test to see if they want it once released.
-
@jaredbusch said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti officially rolls out UNMS:
@jaredbusch said in Ubiquiti officially rolls out UNMS:
@hobbit666 said in Ubiquiti officially rolls out UNMS:
Website still show as beta?
No one ever said it was not beta. I said officially rolls out.
To normal people, officially released (or rolled out) means past beta. A beta release being "not released yet." The beta is released to the public, but the product is not. So you could say "UNMS Beta Officially Rolled Out", but not that "UNMS Officially Rolled Out".
If it was me having said it, you'd call it a term from "Scottland". People definitely universally use the term released to mean... well released. That the vendor sees the final product as now on the market.
The "public beta" state is a commonly accepted officially rolled out state for software products.
Many software products never leave "beta" and are officially out for years.
If it's out and maintained for years - is it really beta at that point?
Frankly - what's the line in the sand that changes something from Beta to not Beta?
