Push vendor config file to ACS via API

[Dan Morphis]

Why are you doing the CPE config this way? A much easier approach is to
have a base config on all your CPEs, then use a provisioning script to set
the specific things (un/pw, wifi, port forwards,etc) for the CPE as it
comes online. Search the mailing list archives, I've posted provisioning
and external scripts that will accomplish this.

At any rate, what you have wouldn't really work, an OUI isn't a serial
number. OUI is Organizational Unique Identifier and only identifies a
vendor, not a specific device. So to go about things the way you want, you
would need to upload hundreds of configs, and then use a provisioning
script to push the f/w based on serial number.

On Wed, Oct 25, 2017 at 7:11 AM, Kris Germann - Portal Network Co. <
kgermann at portal.net.co> wrote:

> I’ve built a config generator for our routers that currently download a
> vendor config file to the users desktop, but I want to push it to our ACS
> using the API.
>
> Is the below correct?
>
> curl -i 'http://acsurl:7557/files/smartrg.conf' \
> -X PUT \
> --data @"./smartrg.conf" \
> --header "fileType: 3 Vendor Configuration File" \
> --header "oui: XXSerialNumberXX" \
> --header "Autogenerated Config"
>
> I wanted to see if there is a way to tag the upload with a serial number
> (or anything) so I can create a script later on to push that config to a
> device with serial number XXXX when it connects.
>
> _______________________________________________
> Users mailing list
> Users at lists.genieacs.com
> http://lists.genieacs.com/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.genieacs.com/pipermail/users/attachments/20171025/251b6706/attachment.html>