ePMP Software Release 5.9.1 is now available

When upgrading the radio firmware from versions earlier than 5.7.2 to version 5.9.1, the Separate Wireless Management Interface may lose its Subnet Mask configuration.

Recommended Workaround:
Prior to the upgrade, disable the Separate Wireless Management Interface. Once the upgrade is complete, re-enable it. This process can be efficiently performed using a cnMaestro template.

1 Like

4 posts were split to a new topic: Speed improvement in 5.9.1

Hi Jacob,

Networking configured as such:

Bridged+Static IP
Ethernet Port Security = Disabled
Management VLAN ID configured, priority = 7
Management VLAN Access = Ethernet and Wireless
Data VLAN = Disabled
No Membership VLANs or VLAN Mapping entries

I don’t think the rest is likely to be relevant, but…

IPv6 = Disabled
ARP-NAT = Disabled
STP = Disabled
DHCP Server Below SM = Disabled
LLDP = Enabled
LLDP Mode = Rx+Tx
Broadcast/Multicast Traffic Shaping = all disabled

On the station side of the PTP link is the default gateway on the ethernet side of the radio or the wireless side?

The gateway is on the ethernet side for the station side of the link

That is likely the issue. There is some bizarre bridge filtering in place on ePMP radios when they are set to station mode. They aren’t a pure bridge. Try disabling acceleration via the cli and see if that helps:

config set cambiumAccelerationEngine 3
config commit 
reboot

That could explain some of the behavior we have seen. Looking at some other forum posts, it seems the recommendation is if you’re using MPLS or VPLS, its best to disable this setting?

There’s really no harm in trying it out disabled to see if it resolves your issues.

1 Like

Thank you so much for that tip…

Disabling acceleration and rebooting both ends of the links solved the original issue.
We tried this on a few other f425 links where one end had lost comms, and it fixed them too.
We had one ring of sites with all f425s where radius on the tiks started timing out randomly, disabling acceleration fixed those too…

As well as a one-off where the Master lost contact instead of the slave. Also fixed.

This saved us a lot of headache…

4 Likes

A post was split to a new topic: 200-series radio with PPPOE not getting IP from 4500 on 5.9.1

Same issues here followed with boot loop. Any updates on your end?

What firmware does the F300 need to be on to connect to the 4500?

The SMs should be matched to the AP, so both should be 5.9.1 (or the 5.9.2 Release Candidate) :+1: