Hello Peplink Collegues,
Lately, we have been doing a lot of factory resetting of our demo systems and reconfiguring them again for a variety of clients. As we are also testing new firmware, it is one of the ways to see how the devices behave with new firmware releases.
We are looking for a way to streamline & optimise the time it takes to configure all of the WAN connections.
These are what you get presented with currently when doing a manually cellular configuration
MAX HD4 MBX
Peplink SDX + 1 x Cellular
Peplink EPX + 5 x Cellular
When you have a multi-cellular system such as an MBX/PDX with only eight SIMs, it may not be too much an issue when deploying a single unit. For an EPX with thirty SIMs to configure, it takes considerable time to go through and do the initial configuration. The time to do this is considerably more with the new Cat-18 Chipsets. Now attempt to multiply that out for a fleet with a mixture of models.
We have considered creating templates (configure one model then save the config and upload), though this requires a template for each models variation. To push out a template, we would like something like InControl2 to as is done with Firewalls and Outbound policies.
What we currently manually do is:
- Choose LTE Only (3G is progressively getting shut down in Australia now and unless a client request 3G we disable it by default).
- Turn off all the frequencies bands except those used by the carriers in Australia (there are only six bands for LTE 4G used in Australia, a few more will get used for the upcoming LTE 5G).
Cat-12 ChipsetsNote: Band 40 is missing for Cat-12, this was a design oversight by the chipset vendor, not Peplink. It is not solvable without a complete chipset re-design/change by the vendor and can not get fixed through firmware in the cellular chipset. So check what bands you need for your region/locations before committing to a particular chipset.
Has anyone worked out a script for configuring the cellular options doing these in the EPX, SDX, PDX & MBX models yet? Is this worthy of a feature request and more considerable community discussion?
Happy to Help,