Last Modified: Nov 07, 2022
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, 184.108.40.206, 13.1.1, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 13.1.3, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 13.1.4, 188.8.131.52, 13.1.5, 184.108.40.206, 14.0.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 14.0.1, 184.108.40.206
Opened: Jun 01, 2018 Severity: 3-Major
The BIG-IP system posts a 'No Access' error message instead of the GTM Pool member's properties.
It makes the GSLB pool member'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 a GTM Pool member on that partition. -- The issue occurs when a GSLB Server discovers that GTM Pool member and displays it on its properties page. Note: This same error message displays for GSLB Server's virtual server properties accessed by navigating to GSLB :: servers :: [server] :: virtual servers :: [virtual server]. The differing issues have been fixed in differing releases. You can find information about the similar issue in the AskF5 Bug Tracker article for 710032.
Use either of the following workaroudns: -- Use TMSH to view or edit the properties of that GTM Pool member. -- Create partitions on the GTM device to match those appearing to be referenced in the object names.
Partition checking has been disabled on the GTM side, since a pool member owned by a server is always in the partition of that server (/Common).