Use this dialog box to configure a Closest Server rule. Click
when you are finished to save the rule definition and close the dialog box.Specify a name for the rule. It displays in the Closest Server Rules listing in ZENworks Control Center. To access this listing, click
in the left pane, click the tab, click the panel to open it, click section to open it, then click . All defined rules for the current level are displayed there.Select this check box if you do not want to append the default rule. The Closest Server rules feature first uses the servers specified in the rule, then proceeds to any other servers listed in the Closest Server Default rule if the specified servers are not available to the managed device. Therefore, to obtain content only from the servers specified in the rule, select this check box to exclude all other servers.
Using the
fields, create the rule expression.An expression consists of a criteria option, operator, and value. For example:
DNS Name Filter equal to *.novell.com
DNS Name Filter is the criteria option, equal to is the operator, and *.novell.com is the value. In the above example, the Closest Server rule is applied only to devices whose DNS name ends with .novell.com.
If necessary, you can use NOT to perform a logical negation of the expression. For example:
NOT DNS Name Filter equal to *.novell.com
In the above example, the Closest Server rule is applied only to devices whose DNS name does not end with .novell.com.
You can use more than one expression for the rule. For example:
DNS Name Filter equal to provo.novell.com or IP Address equal to 123.45.678.12/24
The criteria options you can use are listed below.
Each of the server lists can include individual servers, groups of servers, and L4 switch servers. The following sections provide the tasks you can perform to manage each of these.
You can perform the following tasks to manage individual servers in any of the server lists (Collection, Content, Configuration, and Authentication):
You can use a group to randomize connections to servers. Each time the server list is sent to a device, it is randomized so that not all devices receive the same ordered list.
For example, assume the server list contains the following:
Server 1
Group 1 (Server 2, Server 3, Server 4)
Server 5
One device might receive the following list: Server 1, Server 3, Server 2, Server 4, Server 5.
Another device might receive a different list: Server 1, Server 4, Server 3, Server 2, Server 5.
In all cases, Server 1 is listed first and Server 5 is listed last, but the order of the servers in Group 1 is randomized.
You can perform the following tasks to manage server groups in any of the server lists (Collection, Content, Configuration, and Authentication):
If you have ZENworks Servers or Satellites that are clustered behind an L4 switch, you can define the L4 switch and add the servers to the definition. This enables the L4 switch to continue to balance the traffic among those servers.
For trademark and copyright information, see Legal Notices.