Use this dialog box to configure a Closest Server rule. Click OK 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 Configuration in the left pane, click the Configuration tab, click the Management Zone Settings panel to open it, click Infrastructure Management section to open it, then click Closest Server Rules. 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 Rule Logic 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.
Option |
Explanation |
---|---|
DNS Name Filter |
Matches DNS names that meet the filter criteria. You can specify an exact filter or use a question mark (?) or an asterisk (*) as a wildcard to match one or more characters in the DNS name. A ? matches one character and an * matches one or more characters. Examples:
|
IP Address /n |
Matches IP addresses that fall within the specified CIDR (Classless Inter-Domain Routing) block. With CIDR, the dotted decimal portion of the IP address is interpreted as a 32-bit binary number that has been broken into four 8-bit bytes. The number following the slash (/n) is the prefix length, which is the number of shared initial bits, counting from the left side of the address. The /n number can range from 0 to 32, with 8, 16, 24, and 32 being commonly used numbers. Examples:
|
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, Authentication, and Join Proxy):
Task |
Steps |
Additional Details |
---|---|---|
Add a server to a list (Rule Construction dialog box only) |
|
By default, ZENworks Servers support all functions (Collection, Content, Configuration, Authentication, and Join Proxy). Therefore, all ZENworks Servers are available for selection in any of the server lists. Satellites, however, can be configured for specific roles (Collection, Content, Imaging, Authentication, and Join Proxy). This has the following implications:
Satellite roles are configured in the Server Hierarchy panel on the Configuration tab. |
Reorder the list |
|
Placement in the list determines the order in which servers are contacted. The first list item (server, group, or L4 switch) is contacted first, then the second, and so forth. You can order the items in the lists differently. This allows you to spread the workload initiated by devices by placing different servers higher in one list than in the other lists. For example:
|
Remove a server from a list (Rule Construction dialog box only) |
|
|
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, Authentication, and Join Proxy):
Task |
Steps |
Additional Details |
---|---|---|
Create a server group |
|
|
Add servers to a group |
|
|
Reorder the list |
|
Placement in the list determines the order in which servers are contacted. The first list item (server, group, or L4 switch) is contacted first, then the second, and so forth. You can order the items in the lists differently. This allows you to spread the workload initiated by devices by placing different servers higher in one list than in the other lists. For example:
|
Copy a group from one list to another list |
|
When a group is copied from one list to another, and the name of the group in the source list, already exists in the target list, then:
Also, it is not possible to copy a source list group with some servers in it to a target list that does not contain the same servers. |
Remove servers from a group |
|
The servers are not removed from the server list, only from the group. |
Remove a group |
|
The group’s servers are not removed, only the group. |
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.
Task |
Steps |
Additional Details |
---|---|---|
Create an L4 switch definition |
|
|
Add servers to an L4 switch definition |
|
|
Reorder the list |
|
Placement in the list determines the order in which servers are contacted. The first list item (server, group, or L4 switch) is contacted first, then the second, and so forth. You can order the items in the lists differently. This allows you to spread the workload initiated by devices by placing different servers higher in one list than in the other lists. For example:
|
Remove servers from an L4 switch definition |
|
The servers are not removed from the server list, only from the L4 switch definition. |
Remove an L4 switch definition |
|
The L4 switch definition's servers are not removed, only the definition. |
NOTE:L4 switches are not supported for Join Proxy satellite servers.
Specify the number of ZENworks servers whose data must be sent to the managed devices at a time. The available options are:
Unlimited: By default, the contact information about all the servers listed in the effective rule’s lists are sent to the managed devices. In addition, unless they are excluded in the effective rule, the servers listed in the default rule are appended to the servers listed in the effective rule.
Limit to <a_numeric_value_that_you_specify> Servers per list: If you want to balance bandwidth between the server and the managed devices, specify the number of servers whose data must be sent to the managed devices at a time.
While calculating the Limit Servers Returned to Agent value, ZENworks considers a group or an L4 switch as a single unit, regardless of the number of servers contained within the group or L4 switch. This is because groups and L4 switches are used to balance traffic among the servers contained within them. For more information on groups, see Groups.
For more information on L4 switches, see L4 Switches.
NOTE:You can also configure the Limit Servers Returned to Agent setting in the Closest Server Default rule. The limits that you set in the Closest Server rule override the limits that you set in the Closest Server Default rule.
For trademark and copyright information, see Legal Notices.