# Muliple OUIs for same firmware, product class

**URL:** <https://forum.genieacs.com/t/muliple-ouis-for-same-firmware-product-class/1655>\
**Category:** Uncategorized\
**Created:** [April 20, 2021, 8:31pm UTC](https://forum.genieacs.com/t/muliple-ouis-for-same-firmware-product-class/1655 "2021-04-20T20:31:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![SummaCumWilly](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/summacumwilly/32/559_2.png) [@SummaCumWilly](https://forum.genieacs.com/u/SummaCumWilly)\
**Post date:** [April 20, 2021, 8:31pm UTC](https://forum.genieacs.com/t/muliple-ouis-for-same-firmware-product-class/1655/1 "2021-04-20T20:31:58Z")

</div>

# What am I doing wrong?

I uploaded, via the API, a device firmware image and included OUI, product class and the software version of the image. When I looked at my devices, I noticed there were actually multiple OUIs for that device, so I uploaded again the firmware for the other OUI, and I could then push it to the device. However, when I go to the firmware page, there is only one entry for the image.

Should I not use an OUI if the firmware is applicable to multiple OUIs?

---

<div class="post-metadata">

**Author:** ![JonasGhost](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/jonasghost/32/286_2.png) [@JonasGhost](https://forum.genieacs.com/u/JonasGhost)\
**Post date:** [April 20, 2021, 8:40pm UTC](https://forum.genieacs.com/t/muliple-ouis-for-same-firmware-product-class/1655/2 "2021-04-20T20:40:32Z")

</div>

Some CPE manufacture use multiple OUI for a product series, some allow it to fix that by a special configuration.  
Usually the oui is “burned into” the device, but it looks like, that this cpe is choosing the oui random.

---

<div class="post-metadata">

**Author:** ![akcoder](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/akcoder/32/11_2.png) [@akcoder](https://forum.genieacs.com/u/akcoder)\
**Post date:** [April 20, 2021, 11:38pm UTC](https://forum.genieacs.com/t/muliple-ouis-for-same-firmware-product-class/1655/3 "2021-04-20T23:38:23Z")

</div>

This is a known limitation of GenieACS. In 1.1 (not sure about 1.2 as we haven’t upgraded yet), the product class and OUI must match for the file to show up under the push file option. And filenames have to be unique. One work around for this is to put the oui in the firmware image name. Then you can cover the multiple ouis the vendor uses. Not optimal, but it works.

---

<div class="post-metadata">

**Author:** ![mjducharme](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/mjducharme/32/59_2.png) [@mjducharme](https://forum.genieacs.com/u/mjducharme)\
**Post date:** [April 21, 2021, 12:23am UTC](https://forum.genieacs.com/t/muliple-ouis-for-same-firmware-product-class/1655/4 "2021-04-21T00:23:50Z")

</div>

Unlike GenieACS 1.1.x, in GenieACS 1.2.x you can simply leave the OUI blank and then the file will show up in the push list for all OUI’s. Depending on your situation, this may or may not be a suitable workaround.

---

<div class="post-metadata">

**Author:** ![SummaCumWilly](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/summacumwilly/32/559_2.png) [@SummaCumWilly](https://forum.genieacs.com/u/SummaCumWilly)\
**Post date:** [April 21, 2021, 12:39pm UTC](https://forum.genieacs.com/t/muliple-ouis-for-same-firmware-product-class/1655/5 "2021-04-21T12:39:06Z")

</div>

Yeah, I just added the firmware from the UI with no OUI and that is exactly the behaviour – I was able to apply it to any of those Product types.no matter the device’s OUI.

(And sorry for not mentioning my version. I’m using 1.2.5)