Last Modified: Apr 10, 2019
Opened: Apr 04, 2017
If you click an instance of one of the following objects, the properties screen does not open, preventing you from editing the object: LDAP, AD, CRLDP, TACACS+, or RADIUS server.
Network Access, LDAP, AD, CRLDP, TACACS, and Radius server objects could not be edited.
This happens after importing or reimporting Access. This is due to the pool used by the object instance for LDAP, AD, CRLDP, TACACS, or Radius servers that don't exist in LTM. Thus, the route-domain used by the Network Access object does not exist in LTM.
To work around this issue, rediscover and reimport the BIG-IP device that the object belongs to (LDAP, AD, CRLDP, TACACS, or Radius server).
The LDAP, AD, CRLDP, TACACS+, and RADIUS server properties screens now open properly, allowing you to edit the objects.