Firmware 8.3.0 RC 4

[sitloongs]

@gabrielmongefranco ,

Can you please create a ticket here and attach a diagnostic report to allow support team to check on the issue ?

Step to obtain a diagnostic report :

Obtaining a Diagnostic Report from a Peplink Balance or Pepwave MAX Device

At times you may be requested by Support to provide a Diagnostic Report. Or, when opening a new ticket, you can also attach one together with descriptions and reproducibility of your issue. Please follow the steps below to obtain a Diagnostic Report from a Peplink or Pepwave device: Connect to the Web Admin Interface with a web browser. Go to Status > Device. Click the Download button next to the Diagnostic Report field. A prompt will appear for saving the file containing the Diagnostic Re…

[gabrielmongefranco]

Thanks @sitloongs - Ticket #23010958

I attached the diagnostic report and log. I will try to get some screenshots or video recording.

[sitloongs]

@gabrielmongefranco ,

Thank you and we will follow-up using the ticket and update again.

[Hootan]

8.3 Firmware has a very very useful feature which is Weighted Balance on the SF tunnels.
looking forward to see this feature on the IC2 configurations also.

[Steve_Mitchell]

I wasn’t able to leave the unit in the current network as it was too unreliable. I will try factory resetting it again and build the configuration by hand again and see if it happens again. I have an MBX Mini 5G with the same configuration running 8.3.0 b4 that is working flawlessly with the same equipment around it (2x Starlinks, 2x AP One AX) so I know it’s specific to the BR2 either with 8.3.0 or the hardware is bad.

[Dave_Wilson]

Purchased a 2 VWan license and the firmware only shows me one.

Heres an older firmware showing both…

[padaco-daniel]

Anyone else trying to use SIM Injector on two Cellular modems while there is no other connection active? We have several Balance 310-5G in the field, which are only running dual cellular connections.

With 8.2.1 when we set ‘Use RemoteSIM only’ on both Cellulars, it will first inject one of the two and once one of them is connected properly and online/connected in FusionSIM the second Cellular will start injecting and afterwards both are online with RemoteSIM.

If the RemoteSIM switches/fails it will first switch back to a random internal SIM, normally A, if that’s the only slot that has a physical SIM. In the FW before 8.3.0 you could not set priority while using RemoteSIM.

So now running 8.3.0 RC4, when we set RemoteSIM to Priority 1, and SIM A to Priority 2, it will switch to the RemoteSIM, but when both Cellulars are set to RemoteSIM P1/SIM A P2 sometimes only one of them will switch to RemoteSIM. Rebooting the device one of them will randomly connect.

On units where we have an extra connection like a MAX Adapter in Failover, we try the same setting and it will sometimes work on both Cellulars at the same time and sometimes it will only connect on one of them and the other will stay connected to SIM A, which is set to Priority 2. So far the only solid way I have found with 8.3.0 to have both SIMs injected, is to have an extra internet connection, like the MAX Adapter (or any fixed connection) in failover and set both internal Cellulars to RemoteSIM only, so disable the internal SIMs. Which will result in disconnect on those Cellulars if the RemoteSIM fails but at least it will keep running on the failover connection.

This can’t be the way it’s supposed to work right? For the units that don’t have any failover methods, we have switched back to 8.2.1 for now.

[TK_Liew]

Please help to open a ticket for us to check. Thanks.

[TK_Liew]

This is not expected. Can you help to open a ticket for us to check?

[padaco-daniel]

Done.

[padaco-daniel]

It seems the issue was not related to 8.3.0 after all. Something else was causing the issues with FusionSIM, we are still diagnosing it, but 8.3.0 works fine now with the priorities set as intended.