ePMP Software Release 4.7 is now available

Products ePMP
74

Sorry, I did not get a notification of your other post.

IF cnmaestro had a update pending then this would make sense, but this is sounding like either a hold over in 4.7-STA or something funny is interacting and forcing a web update, which ignores your on-prem server.
I wish we could disable the web update in config though, it is too easy to bit flip a register thus gain an unintended web update.

75

I’ve seen performance improvements with 4.7 mentioned in the forums.
.

.

76

What improvements exactly?

77

The 4.7.0.1-RC6 Beta with the critical bug-fixes has been released.

Thank you.

1 Like
78

Oops! That page is private.

79

You need to join the ePMP Beta program to get access:

2 Likes
80

Hi Chad have you already tried the new 4.7.0.1-RC6? what were the results? did your issues were fixed?

81

We are not trying release candidates. We spent considerable time getting everything back to 4.6.1 and I think that is where the network will likely stay for the rest of this hardware’s life.

1 Like
82

Does anyone have some field data using 4.7.0.1-RC6

83

There is a known memory leak in 4.7.0 for the DPI feature, this is not yet confirmed in 4.7.1rc6 but there is issues surrounding DPI in 4.7.1rc6.
We are still lab testing 4.7.1rc6 but it is not going well, odd issues in the lab mean major issues in the field. Funny thing is that we are having a hard time quantifying these issues as they come and go fast enough that we are not seeing the cause and the syslogs are as helpful as ever! Some more verbosity would be nice!

84

Hi all, so to roll back anything from 4.7 is not possible? I have a few weird things happening with some subscribers but do not know if its software related.

85

Anyone have issues rolling back from 4.7

86

@DigitalMan2020, the only possible bug was in RC6 and fixed in RC7. So if you have already stable 4.7.0 then it should be smooth.

87

Okay thank you… I was just wondering because someone on the forum said that they could not roll back from 4.7

89

So, we have next downgrade restrictions:

Downgrade below 4.7 is not supported for Force 200L.
Downgrade below 4.7 is not supported for boards with soft country lock set.
Downgrade below 4.7 is not supported for boards with flexible mode selected.
Downgrade below 4.7 is not supported for boards with Port Forwarding configured containing ports 22(SSH), 161(SNMP), 80(HTTP), 443(HTTPS)
TR-069 option is not supported in SW versions below 4.7.0.
Downgrade from 4.7.0 for F300-13/F300-19/F300-19R Maxrp is supported to 4.6.4 only.

90

Not sure if anyone has posted this (minor) issue but we updated an epmp 3000 radio to 4.7 and have a device name missing in the monitor → wireless tab.

91

I will also comment that since upgrading the epmp 3000 radio to 4.7 we are seeing higher frame utilization on throughput averages that had lower utilization before 4.7.

92

We reported that earlier. I tracked it down to “device names longer than 32 characters”. They’ve fixed it in 4.7.0.1 but making the name 31 characters should fix it too.

93

We found that 4.7.0 would wait a long time before adding the SM name to the monitor-wireless page. upgrading to 4.7.0.1 fixed that as far as we can see.

94

Hi this version of FW (4.7) is realy crap for N radios (Force 180/200, ePMP 1000 connectorized/integrated radio). After few days device stop passing traffic, web management is unreachable, only icmp work…

Only powercycle solve this issue, we have a lot of cases…

1 Like