You can establish advisory minimum and maximum RPC authentication bounds for each fileset. As with the File Server RPC authentication bounds, the FLDB holds a pair of bounds for each fileset. One set of bounds governs communications with Cache Managers that are in the same cell as the File Server within which the fileset resides; the other set of bounds controls communications with Cache Managers in foreign cells. While these advisory bounds are not currently enforced (although they may be in a future release of DFS), they do serve to bias the initial RPC authentication level when a Cache Manager attempts to access that fileset. The advisory bounds work as follows.
When the Cache Manager contacts a Fileset Location (FL) Server to ascertain the location (or locations) of a given fileset, the information returned by the FL Server includes that fileset's lower and upper RPC bounds. The Cache Manager compares its initial RPC authentication level to the range set by the advisory bounds. If the initial level falls within that range, the Cache Manager begins negotiations with a File Server using the initial level. However, if the initial level is above or below the range, the Cache Manager adjusts its initial level to match the closest bound level. (If the File Server requests that the Cache Manager lower its authentication level below the minimum level specified for the Cache Manager, the Cache Manager refuses communications with that File Server.) The Cache Manager then uses the modified initial level to begin negotiations with a File Server.
You establish the fileset advisory RPC authentication level bounds by using the fts setprotectlevels command. You can check if a given fileset has advisory bounds and display the bound level values by either using the fts lsfldb command or the fts lsft command.