Bug ID 710032: 'No Access' error when viewing GSLB Server's virtual server that has a name indicating a partition that does not exist on that BIG-IP system.

Last Modified: Jul 12, 2023

Affected Product(s):
BIG-IP DNS(all modules)

Known Affected Versions:
13.1.0,,,,,,,, 14.0.0,,

Fixed In:

Opened: Mar 13, 2018

Severity: 3-Major


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.

Fix Information

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).

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips