YSoft SafeQ Embedded Terminal for Ricoh ESA is communicating directly to the "YSoft SafeQ CML" with some exceptions when support from "YSoft SafeQ Terminal Server" service is required. Therefore, standard procedures for the loadbalancing and failover via Microsoft Cluster Server or Failover using Windows Network Load Balancing Services (NLB) does not apply for this type of embedded terminal.

If you have the failover enabled, MFP will obtain the list of IP addresses for all the CML nodes after the first successful authentication. If the primary CML becomes unavailable, embedded terminal will automatically find another CML according to strategy selected in configuration. Then the embedded terminal will use the resolved CML as the primary until it becomes unavailable or until some preconfigured time interval passes. Then another server is found and selected as primary in dependency on selected failover strategy. With some strategies the MFP may automatically switch back to a preferred CML if you restore its functionality. The server can be resolved as active only if both YSoft SafeQ CML and YSoft SafeQ Terminal Server are responding to MFP requests.

Limitations

1	This failover configuration does not provide Load-balancing.
2	This failover is applicable only on the CML (not on ORS).

Enabling failover support for YSoft SafeQ Embedded Terminal for Ricoh ESA

1

Log in to the SafeQ Web Interface with sufficient rights to administer printers (for example, "admin")

Go to System > System settings and set srte-enterprise-mode property to enabled.
If enabled, Ricoh Embedded Terminal is running in the enterprise mode, i.e. the terminal application connects to multiple server nodes in the YSoft SafeQ cluster.

2

Save the configuration and restart the CML service on all the nodes and reinstall all the devices with YSoft SafeQ Embedded Terminal for Ricoh ESA.

Configuring failover on YSoft SafeQ Embedded Terminal for Ricoh ESA

1	Log in to the SafeQ Web Interface with sufficient rights to administer printers (for example, "admin")
2	Go to System > System settings from the menu
3	Set srteFailoverStrategy property to required strategy. The option determines how the primary server is resolved in case when the current server becomes unavailable. The strategies are described in following section.
4	Set srteFailoverCheckInterval property to required value. It sets the maximal time (in minutes) after which the primary CML server is resolved according to selected strategy. The minimal allowed value of this property is one.
5	Save the configuration and reinstall all the devices with YSoft SafeQ Embedded Terminal for Ricoh ESA.

Strategies for server selection in YSoft SafeQ Embedded Terminal for Ricoh ESA

1

Default strategy

With this strategy the MFP will always check for the CML server with fastest response. The servers are checked for their availability in parallel and the first CML server which responses is taken as the primary for all ongoing communication.

2

Primary node preferred

With this strategy the "primary node" is always preferred. In this scenario, the "primary node" is the CML from which the MFP was originally installed. If the "primary node" is not available, another server is selected using the default strategy described above. If the "primary node" becomes available, the MFP will connect to it when the current one becomes unavailable or after the preconfigured time interval passes.

How to verify the correct functionality

1	Authenticate at the YSoft SafeQ Embedded Terminal for Ricoh ESA with the valid account. Authentication must not fail.
2	Log in to the YSoft SafeQ Embedded Terminal for Ricoh ESA Web Configuration Interface at 'http://MFP_IP:8080/sqet/Login' (where MFP_IP is the MFP's IP address). Please note the HTTP address is case-sensitive. Enter the login code. (The default is 14569.)
3	Verify that you see the IP address of all your CMLs in the list.
4	Optionally you can stop the CML which is listed as the first. Then verify that authentication is still working. In the YSoft SafeQ Embedded Terminal for Ricoh ESA Web Configuration Interface you will see that the order of the servers has switched.