ePMP 1000 Release 2.4 adds the following features:
eFortify™ Enhancements:
New ePTP mode of operation: The release introduces a new mode of operation for point-to-point configuration providing significantly lower latency than other modes. Currently not available for DFS bands.
Improvements to VoIP performance
Ability to configure the Max MCS independently in each direction
eCommand™ Enhancements:
eAlign: The release introduces eAlign (found under the Tools menu), a tool to aid with link alignment
Session Time per SM on the AP (under Monitor->Wireless)
Improvements to the throughput chart on the GUI dashboard (under “Home”)
WARNING: Please note that the ePTP mode of operation is not available for DFS band/regions, yet. Use caution while switching a remote radio (far side of a link) to ePTP mode when operating on a DFS channel. The radio may not register to the local radio (near side of the link) resulting in a stranded radio. A site visit may be required to switch the remote radio out of this mode.
ePTP mode uses a slightly different mechanism than TDD mode. In order to ensure a reliable and stable link and keep the latency low, we have restricted the range of the link. 24 km is the limit for a 40 MHz channel.
We are experiencing multiple issues including the non-existent AP list.
We updated a few of our SM's and lost contact with them. After running out to each house, the Seperate Wireless Management IP dropped the Gateway. Just dropped it. Non existent. So that was fun.
Tried to also use a SM as a Spectrum Analyzer but the IP changed to the DHCP server IP of 192.168.100.1 subnet 255.255.255.0 and gateway of the public address. If I would have saved, we would have lost access to another SM.
Attempting to change the network addresses (bridged static, and nat static) to match to prevent issues then didnt allow to save changes as the reason the gateway didnt match. As the DHCP of the bridge mode picked up the 192 address and the gateway of the public address.
Also, it would be cool if you guys skipped the firware releases that have direct relationships to unlicensed frequencies. Makes it seem like 2.4 is for 2.4 equipment for some.
Sorry for all the troubles. The issues mentioned are quite worrisome and I would like to help. Can we arrange for a remote access session Monday(sorry I’m travelling until then). I’d like to get to the bottom of it with your help. Please drop me a note at sriram@cambiumnetworks.com and I’ll take a look.
As for the release numbering, its just a coincidence.
Can you please tell us what issues you are seeing? It will help us root cause and fix. If you'd like, you can private message me or email me directly at sriram@cambiumnetworks.com or you can contact our support team at http://www.cambiumnetworks.com/support/contact-support
There are several improvements made in Release 2.4 which we want you to take advantage of. But if issues are preventing you from using that release, please let us know what they are so they can be addressed.
Sriram: As mentioned in another thread here, the bridging/neighbor/ARP table seems to be lacking any info on LAN-connected devices. Also noted elsewhere I believe is that the 'Available APs' list is empty.
Also, I noticed that the names of MIR profiles are all truncated by one character in SNMP on an AP, except 'default', so we have: