In systems where multiple Hot Servers(see 6.6.2.4.5.4) are available, the Serversin the Redundant Server Setcan share the load generated by Clientsby setting the ServiceLevelin the Healthysub-range based on the current load. Clients are expected to connect to the Server with the highest ServiceLevel. Clients shall not Failoverto a different Server in the Redundant Server Setof Serversas long as the Server is in the Healthysub-range. This is the normal behaviour for all Clients, when communicating with redundant Servers. Serverscan adjust their ServiceLevelbased on the number of Clientsthat are connected, CPU loading, memory utilization, or any other Server specific criteria.

For example in a system with 3 Servers, all Serversare initially at ServiceLevel255, but when a Client connects, the Server with the Client connection sets its level to 254. The next Client would connect to a different Server since both of the other Serversare still at 255.

It is up to the Server vendor to define the logic for spreading the load and the number of expected Clients, CPU load or other criteria on each Server before the ServiceLevelis decremented. It is envisioned that some Serverswould be able to accomplish this without any communication between the Servers.