Controller cannot accept Arbitrary Parameters via cfcreate-service|bind-service-c.
Controller doesn’t support the use of cfupdate-service.
The BIG-IP data group cf-ctlr-data-group, found in the same partition that the controller manages, needs verification if the controller crashes. There should be a one to one mapping of tier 2 VIPs to data group records with the same name. If the record is missing for a VIP the controller will not rebuild the BIG-IP to the correct state it was in before the crash. This is because the controller crashed before the updated data group got written out. This condition requires manual intervention. Update the data group with the missing VIP’s name as key and virtual address and port as data. The data must follow this format: {“bindAddr”:”ADDRESS”,”port”:PORT}. Encode the data as base64.
JSESSIONID cookie session persistence will not work for BIG-IP v11.6.1 and will cause Connection Reset by Peer connection errors. Correct this by disabling session persistence, set session_persistence to false in the controller config.
The BIG-IP Controller controls one (1) partition on the BIG-IP device.
Controller configurations are global: they apply to all L7 (HTTP) LTM objects in the designated BIG-IP partition.
This release supports custom policies and profiles for L7 virtual servers only.
Configured health monitor objects apply to all pools (both L4 and L7 routes).
SSL profile(s) defined in the application manifest do not attach to the HTTP virtual server.
Modification of a Controller-owned policy resulting in a state change may cause traffic flow interruptions. If the modification changes the state to ‘published’, the Controller will delete the policy and recreate it with a ‘legacy’ status.
You cannot change the default route domain for a partition managed by an F5 controller after the controller has deployed. To specify a new default route domain, use a different partition.