Query regarding Firmware reconciliation to CPE

[Manny Veloso]

We try to keep the following in the firmware filename:

* vendor (CA_PBCA in our case)
* version
* customer (if custom to a customer)
* build number
* device type

As a side note, you may or may not be able to rename a firmware file and
have it work. For some vendors the name is significant, and the current FW
will use the name of the firmware file to validate (and reject) the image.

-- 
Manny Veloso

Sr. Solutions Engineer
Smartrg.com




On 8/13/15, 2:25 AM, "Users on behalf of Zaid Abdulla"
<users-bounces at lists.genieacs.com on behalf of zaid at genieacs.com> wrote:

>On Tue, Aug 4, 2015, at 07:35 AM, Prashant Upadhyaya wrote:
>> I was looking for some best practices for Firmware file for CPE.
>> Eg. should I invent a file like <VersionNumberOfFirmware>.bin so that
>> the version number can be easily dug out from filename itself, or is
>> there any better choice.
>> Perhaps the CPE guys can educate from their fielded experience.
>> 
>> Further are there any nuances in firmware reconcilation eg. only if
>> the CPE is at a lower version than what is available at ACS should the
>> firmware be upgraded etc.
>
>There are no best practices that I know of. But sticking to one naming
>convention is more important than the exact convention you'll follow.
>
>Here's a few suggestions from my experience:
>
>- Include the hardware model to avoid potential name conflicts.
>
>- Custom builds should be marked as such.
>
>- Unless two image files are identical byte by byte, they should never
>have the same version number. So when doing rapid test builds with minor
>tweaks for testing and feedback always use distinct version numbers.
>
>Zaid
>_______________________________________________
>Users mailing list
>Users at lists.genieacs.com
>http://lists.genieacs.com/mailman/listinfo/users