NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MR5200 won't attach to n77 after firmware update - multiple questions!
I have a number of MR5200 that I use for testing locally on a local network... The old firmware (NTGX55_10.29.11.00) worked really well on my band 3 / n77 5G NSA setup however a newer firmware that g...
Sorry to hear the latest update cause some issues on your devices. We will investigate
Could you please advise which carrier you are using?
As for downgrading failure to older release using local update file, this is by design. Upgrade setting is enabled by default and can't be disabled by end users.
dotbill wrote:
I have a number of MR5200 that I use for testing locally on a local network... The old firmware (NTGX55_10.29.11.00) worked really well on my band 3 / n77 5G NSA setup however a newer firmware that got pushed onto one of the devices (NTGX55_12.03.09.00) doesn't seem to associate to the n77 band anymore.
Doing a good amount of digging - I've got hold of the old firmware file (the secc.cwe file - which I've renamed to .spk per other forum posts) - however trying to reload it on the "updated" device gets an Error Code 16 in the web admin firmware uploader. Any thoughts here?
The second thing I'd like to do is disable software update on these devices - there doesn't appear to be an option - is there a hidden setting?
The third thing I'd like to do is get this issue fixed - I've tried the official support and its taken a week, and I'm barely past the "can you confirm that you've tried the sim in another device" question..
I've got hold of the model.json off devices with the old / new firmware - you can see the one that works here:
"diagInfo": [ {
"lteAttached": true,
"nr5gAttached": true,
"endcEnabledConfig": true,
"ltesigValid":true,
"ltesigRssi":"-68 dBm",
"ltesigRsrp": "-85 dBm",
"ltesigRsrq": "-7 dB",
"ltesigSnr": "29 dB",
"nr5gsigValid": true,
"nr5gsigRsrp": "-92 dBm",
"nr5gsigRsrq": "-11 dB",
"nr5gsigSnr": "17 dB"
},{}],and the one that doesnt here:
"diagInfo": [ {
"lteAttached": true,
"nr5gAttached": false,
"endcEnabledConfig": true,
"ltesigValid":true,
"ltesigRssi":"-64 dBm",
"ltesigRsrp": "-82 dBm",
"ltesigRsrq": "-8 dB",
"ltesigSnr": "29 dB",
"nr5gsigValid": true,
"nr5gsigRsrp": "-32768 dBm",
"nr5gsigRsrq": "-32768 dB",
"nr5gsigSnr": "-3276 dB"
},{}],
Something definitely looks "not right here". From the base station side - the netgear is sending in measurement reports for the NR radio - it just doesn't bring up the userplane on it.
As a final issue - I've noticed some MTU issues when using these devices... I noticed a setting in the model for mtuChangeEnabled - any ideas about that?
Any enthusiasts here that have some friendly pointers? For the application I have, the netgear works really well - this "auto updated" disaster is a bit of a pain!
Carrier is bluewave (234 / 73). Operates on band 3 and band n77 as 5G NSA.
As a further update - I've discovered that the MR5200 advertises that it can work on band n77 but doesn't list any available bandwidths (for those aware - the field "channelBWs-DL fr1" in the UE Capabilities reply..
However on band n78 it lists (5/10/15/20/40 MHz).
This suggests that you've either deliberately crippled the device working in a band that it previously worked - or, there is a bug where it wasn't tested fully..
Any chance of pushing this forwards as:
- not being able to revert software updates
- not being able to stop software updates
- not being able to join a band that I could previously
- not being able to use my devices anymore because of the above three statements is a little troubling!
Cheers
Our internal test result showed that 3A4+n77A4 was Passed and could achieve more than 2.5 Gbps DL TP.
Can you help to capture a QXDM log for us to check why B3+n77 failed on your side?
Thanks
John
I don't have QXDM available - though if you are able to send me tooling / instructions I'll happily collect any debug you would like. Equally - I thought that QXDM logs could only come from a modem directly connected - in the instance of the netgear, since there is serial available, would need your guidance on this.
I was viewing this from the eNodeB / gNodeB perspective on the PHY/MAC/RRC layers.
To pass onto your engineers - this is the output for band 77 (and then later band 78) for the capabilities of the device - note the difference in supported bands which appears to be a regression. ie. it was functioning fine before the latest update.
In the next three code blocks, I've included the exert from the specific channel answer (n77), then the capability enquiry, and then the answer - I've had to attach the response as a text file due to size.
channelBWs-DL fr1: { scs-15kHz '0000000000'B, scs-30kHz '0000000000'B, scs-60kHz '0000000000'B }, channelBWs-UL fr1: { scs-15kHz '0000000000'B, scs-30kHz '0000000000'B, scs-60kHz '0000000000'B },The request follows
{ message c1: ueCapabilityEnquiry: { rrc-TransactionIdentifier 0, criticalExtensions c1: ueCapabilityEnquiry-r8: { ue-CapabilityRequest { nr, eutra-nr }, nonCriticalExtension { nonCriticalExtension { nonCriticalExtension { nonCriticalExtension { nonCriticalExtension { requestedFreqBandsNR-MRDC-r15 { bandInformationEUTRA: { bandEUTRA 3 }, bandInformationNR: { bandNR 77 } }, nonCriticalExtension { eutra-nr-only-r15 true, nonCriticalExtension { requestedCapabilityNR-r15 { } } } } } } } } } } }This is the response from the Netgear device
see attached file