byUBNT-ancheng12-10-201503:37 PM - edited 01-18-201611:24 AM
New EdgeMAX software version v1.3.0 for EdgeSwitch products (all current models ES-48-750W, ES-48-500W, ES-48-Lite, ES-24-500W, ES-24-250W, ES-24-Lite, and ES-16-150W) is available on our download site:
This release adds a "Basic" tab in the Web UI for more commonly used features to simplify the basic UI workflow, support for direct VLAN "trunk" port configuration, and other enhancements/fixes (details in release notes below), most of which are based on feedback, bug reports, etc. from community members. Thanks everyone for helping us make the products better!
[Release Notes v1.3.0]
Changes since v1.1.2
[Web UI] Add "Basic" tab in the UI to make some commonly used functions easier to access. Currently this includes Port Summary, VLAN (wizard), Port Channel (LAG), Port Mirroring, Firmware Upgrade, and Restart Switch:
Note that at the moment these are the same pages as the corresponding "original" pages (which can still be navigated using the other tabs). These can be adjusted in the future, e.g., different/more pages can be included, content can be modified for the "basic" context, etc. So please give it a try and let us know any feedback/suggestions.
[VLAN] Add "VLAN trunk port" support. Now the "switchport mode trunk" and "switchport mode access" interface configuration settings have been added, which may be more familiar to users who are used to switches from certain other vendors. Here is a summary of how VLAN can be configured now with the new changes:
"Original" VLAN configuration settings: By default, each interface is "switchport mode general", in which case the original VLAN configuration settings can still be used, for example:
In the above example, interface 0/11 would allow both tagged VLANs 101 and 102, while 0/12 would be untagged VLAN 101. (Note also that "switchport mode general" is the default, so setting it is not required and it's just shown here for clarity.)
New "trunk" configuration settings: Instead of the original settings, "switchport mode trunk" and "switchport mode access" can be used, for example:
In the above example, interface 0/11 is set to "trunk" mode, so it would allow all VLANs. Interface 0/12 is set to "access" mode with access VLAN 101, which means it is untagged VLAN 101, i.e., basically equivalent to the interface 0/12 settings in the previous "general" mode example (using the "original" VLAN settings).
The difference between 0/11 in "trunk" mode and the previous "general" mode example is that trunk mode implicitly means "all" VLANs, whereas in general mode each VLAN needs to be explicitly configured using the original VLAN settings (participation, tagging, etc.). Note that in either mode, VLAN 1 is untagged by default.
In addition to basic "trunk" mode, "allowed VLAN" and "native VLAN" can also be configured on a trunk port. For example:
would exclude VLAN 1 from the port and also make VLAN 102 untagged (all other VLANs are allowed and tagged).
The new trunk port functionality can also be configured in the Web UI "Basic > VLAN" page now. Here is an example screenshot:
The trunk port config for the ports is at the top of the VLAN wizard. When trunk mode is enabled for a port, "Exclude" would correspond to the "trunk allowed" setting, while "Untagged" would correspond to the "trunk native" setting.
The limitations of the original VLAN settings and trunk port support have been discussed with community members including @Ernani@paszczus@petecarlson , for example here.
[System] Fix some text encoding issue in log messages.
[System] Reduce logging verbosity for adding VLAN to MST instance.
[System] Make "enable" require password by default. I.e., the "aaa authentication enable enableList enable local" setting is now enabled by default. This means level-1 (read-only) user cannot go into "enable" mode by default. To disable this (so that "enable" does not require password), use the following configuration command:
[Web UI] Add "System > Port > SFP Information" page which displays detailed information about SFP modules, for example:
[Web UI] Fix edit issue with DNS server on the "System > Advanced Configuration > DNS > Configuration" page. Reported by @razrhere.
[Web UI] Fix login issue caused by special characters (e.g., "+") in user password. Reported by @nsemovhere.
[Web UI] Fix additional places ("System > Management Access > HTTPS" and "System > Management Access > SSH") in the Web UI where download/upload icons were reversed and causing confusion. Originally reported by @dn3033here.
[Web UI] Add Dashboard message indication when the Diffie-Hellman (DH) parameters files are being generated, for example after "reset to defaults" procedure has been performed. This operation takes a long time and consumes most/all of the CPU resources so it is good to provide an indication for the user that it is ongoing. (Note that the CPU usage does not affect the actual traffic switching which is done by dedicated switch chip, not the CPU.)
[Web UI] Fix button status issue on "Switching > Private VLAN > Interface" page.
[Web UI] Fix some text encoding issue in help text.
[Web UI] Add a column for port description to the "System > Port > Summary" page. Suggested by and discussed with @Psychorhere.
[Web UI] Clarify error message when failing to enable SSH due to missing keys. (The same for enabling HTTPS will be done as well but not yet in this beta release). Reported by and discussed with @telmateXmen@rjh2805@twinkie76yhere.
[Web UI] Add port description column to the "Switching > DHCP Snooping > Base > Interface Configuration" page. Suggested by @mikemolhere.
[Web UI] Remove password column on the "System > Advanced Configuration > Email Alerts > Server" page. Discussed with mikemol here.
[Web UI] Add missing help page for the "Switching > VLAN > Switchport Summary" page. Reported by @cxselph77here.
[Web UI] Add help page for the PoE configuration page
[Web UI] Clarify error message when enabling HTTPS without certificates (on "System > Management Access > HTTPS" page). Reported by and discussed with @telmateXmen@rjh2805@twinkie76yhere.
[CLI] Change the term "reset" to "restart" to make it more clear when restarting the switch. Suggested by @cxselph77here.
[CLI] Add the following CLI commands:
The command below can be used to clear entries from the event log (which is persistent):
These commands below can be used to clear the MAC addresses learned by the switch: