NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dotbill
Jul 23, 2021Tutor
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...
dotbill
Jul 25, 2021Tutor
Carrier is bluewave (234 / 73). Operates on band 3 and band n77 as 5G NSA.
dotbill
Jul 26, 2021Tutor
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
- JohnPengJul 26, 2021NETGEAR Expert
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
- dotbillJul 26, 2021Tutor
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