Can the SILO feature be used for separating the environments in Big IQ?
Hi all, I am working on an existing environment of a few F5 Big IP LTMs and I am onboarding them on Big IQ. Many object names are duplicated and I know that I can create a silo in order to isolate the selected device and fix the situation. So my question is: what if I create a few silos and use them to separate the environments and keep them as they are, instead of fixing the names? It almost looks like when in a silo, the device is not really managed by the Big IQ, is it correct? Thank you in advance.BIG-IP Next HA Pair Onboarding REST API
I've been playing around with BIG-IP Next in my home lab for the past few days and have managed to successfully onboard an HA pair of BIG-IP Next instances via the BIG-IP Next Central Manager GUI. I am now trying to do the same thing, but this time with the REST API. However, when I attempt to do this, I receive the following error when checking the onboarding task from Postman : "failure_reason": "failed to save details about new onboarding node (address 10.1.0.242)", I am using the following JSON documented under the 'Deploy an Onboarding Manifest' heading (I have just substituted the property values to reflect my lab environment) andI am sending the API call to the Central Manager management IP. https://clouddocs.f5.com/products/big-iq/mgmt-api/v0.0.1/ApiReferences/bigip_public_api_ref/r_openapi-next.html#operation/DeployOnboardingManifest Out of interest, has anyone managed to get this working?
