When i download a conf file from a max transit for use as a default config in our environment,
the device name and device id also get saved. The result is conflicts when creating VPN-tunnels, all devices get the same device id. Is this something you can choose not to add to the config file?
Do you add the ânewâ devices to InControl and ensure they are online (when viewed via InContorl), then apply the config file? My understanding is that the Device-ID is assigned when they communicate with InControl - so applying the config after this, should not over-ride the ID pushed via InControl.
However, if the device has not communicated with InControl then it wonât have a Device-ID and therefore will use the one assigned by the config file.
@Steve: Generally, yes. When cloning devices this way, itâs best to let them go online as âthemselvesâ first. Device name will still be overwritten in this case by the cloned config, but the device site ID will be pulled from the IC2 db.
In case of issue, as of 2.8.4 weâve added the ability to change an existing devices site ID from the device-level overview page.
This is after i have uppload the conf via web admin. The Local ID have changed. If i try to edit the local id from here it just get back to the one from the config after creating a tunnel via ICA.