Create a Wide-IP in the "Member list" does not appear any virtual server to associate.

Hi Rodrigo,

both commands will be used versus a local self IP address (not a floating self IP address!).

The self IP needs to be in "PortLockDown = allow-default" state.

Now you run "

bigip_add 

" to internally exchange certificates.

Now you run "

gtm_add 

" to finish the internal GTM related configuration exchange. To validate the iQuery communication you can use "

iqdump 

".

Track the GTM log facility by running "

tail -f /var/log/gtm

" in a second console.

If you are running your LinkController as redundant pair, this needs to be done between both units as well.

That´s why I mentioned the requirement for unit specific device certificates. Using the default "localhost.localdomain" certificate on both machines makes things even more complicated.

I haven´t touched the LinkController for a while. But it was always good practice, to create a "default_gateway_pool" and use it as next hop for default gateway configuration in the network settings. This used to trigger the creation of a "datacenter" object automatically, which is not available from the LinkController´s WebUI.

Thanks, Stephan