|
New Features | | |
Supports manual alarm ignorance function. | |
Supports ISP Data Statis function for MTFi device.
| |
Supports SIM card statistics in Traffic Summary on the detailed page of MTFi. | | Supports part of functions management of switch, including Port Management, VLAN Management, SYSLOG Settings, SNMP Settings, NTP Settings, DNS Settings and so on. | |
Supports AP location bind function in Layout and sub group layout configuration. | |
Supports automatic and manual plan of Radio 3. | |
Modifies the operation log function. More user operation logs can be recorded. | |
Supports configuration log of Device View. | |
Supports detailed log search function, including Daily Clients, Daily Traffic and Hourly Client. | | Supports rate limit settings and dual-SIM-card switchover for MTFi device. | | Supports cluster deployment. | | Supports MTFi device indoor deployment. Deletes bus assets information. | | Supports default group creation and WiFi configuration when new tenants are added. |
Changes | | | The system menu has been adjusted. In version 3.1, some pages can be displayed by a click on second-level menu, including DASHBOARD, ALARM, CLIENT, GROUPS and so on. | |
The DASHBOARD has been set as the first page which users will see after login. | |
The group and device data displayed in the map on page DASHBOARD will not be displayed in aggregation. AP that has bound with a location will be displayed in the map. If the MTFi device which has been bound with a location is in a group, the group will be displayed in the map. | |
It moves the report in version 3.0.1 to ANALYSIS in Monitoring. And statistics data in the last 30 days are available. | | Group type icon and Add Device function are created on GROUPS page. When MTFi device is created, users can add sub groups. | | Sub group of common AP can be bound with the location in the map. | | The CWMP Keepalive settings has been deleted. | | The basic and statistics data can be kept for 32 days. |
Fixed Bugs
| | | Solves the problem that after the user is offline, the status of it in the system is still online. | | Solves the problem that if Google map cannot be displayed, part of the pages cannot be initialized. | |
Solves the problem that sometimes the device connecting with private cloud cannot be redirected to the private cloud sever through public cloud server. | |
Solves the problem that after the system has been successfully upgraded, the system still displays a prompt that the operation fails. | | Solves the problem that the database backup function cannot be enabled. | | Solves the problem that the public cloud delivers configuration to devices in an extremely slow speed. |
Limitations
| | | | | | | In bridge mode, the VLAN ID of SSID could not be ‘VLAN233’ if there is an SSID working in NAT mode on the same AP. Reason: VLAN233 will be used as the internal VLAN if one or more SSID work in NAT mode. | | | Device with dual power supply ports | For devices with dual power supply ports, like AP740-I, only going online through LAN1 is supported by MACC. | | | Details page loading slowly | The problem of switch results in the long execution time when MACC delivers CLI commands by CWMP. It takes around 0.5 seconds to search a common item and 0.8 seconds to save a common configuration. | | | Takes long time to search data. | When the data of historical users, connection logs and etc. reach to a million count, the corresponding search operation will take a long time (around 10 seconds).Both big data and server performance cause the problem. | | | | The released version MTFI_3.0(1)B3_MTFI-M520-OVERSEAUNIVERSAL does not support Load Balance Mode. |
|
|