Firmware upgrades - does the share really have to be in the same domain?

stuartd

The documentation for updating firmware states:

Looking for folks that use APEs across multiple domains if this is really true, or whether we can just set up a central share that can be accessed with some jiggery-pokery on firewall rules and pre-loading of domains via the 'hosts ' file?

Alternatively, if SolarWInds allows it, we could just access the share as an IP e.g. \\10.20.30.40\upgrades

shyde

Our APE is on the same domain so can't answer for sure, our servers are domain-less. I believe it works in our case because both servers have matching local user accounts/passwords. I think it would work for you so long as there is IP connectivity and the user account running orion has access to the file store.

One concern I'd have is that if the file is not in the same domain maybe different geo-location there could be some bandwidth or latency issues.

When I look up the job history for ones done by the APE (our repository is on the main engine) I notice that the copy / installed command sent to the device is going to the APE. So from what I can tell in the background the APE is downloading the firmware temporarily from the main engine and then uploading it to the end device. I can't verify this 100% its an observation. I wish that Solarwinds would allow the firmware repository to just be local to each engine, it doesn't take that much space...