Last Modified: Nov 07, 2022
See more info
Known Affected Versions:
13.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 14.0.0, 184.108.40.206, 220.127.116.11
14.1.0, 18.104.22.168, 22.214.171.124
Opened: Mar 13, 2018
The BIG-IP system posts a 'No Access' error message instead of the virtual server's properties.
It makes the GSLB Server's virtual server's properties page unavailable in this case.
-- At least two BIG-IP systems in a sync group. -- One of the BIG-IP systems has a partition that does not exist on the other with an LTM virtual server on that partition. -- The issue occurs when a GSLB Server discovers that LTM virtual server and displays it on its virtual server page. Note: This same error message displays for GSLB pool member properties accessed by navigating to GSLB :: pools :: [pool] :: members :: Member : Address. The differing issues have been fixed in differing releases. You can find information about the similar issue in the AskF5 Bug Tracker article for 722734.
Use either of the following workaroudns: -- Use TMSH to view or edit the properties of that virtual server. -- Create partitions on the GTM device to match those appearing to be referenced in the object names.
Partition checking has been disabled for virtual servers on the GTM side, since a virtual server owned by a server is always in the partition of that server (/Common).