This Quick Health Check document is briefly describing what might be checked to ensure the correct functionality of a SafeQ Terminal Server failover via WNLB . This document is working with an example of two network cards that are used for WNLB. Please note that customer environment and network infrastructure might be different.

Windows Network Load Balancing (WNLB) setup is described in Configuring WNLB Server Failover topic.

Table of contents

Checks in Network Load Balancing Manager

There are different types of situations that might occur:

1. WNLB Cluster is up and running and the traffic for Terminal Server is balanced among the SafeQ Terminal Servers

images/download/attachments/21955736/NLB_-_converged.png

This status in WNLB manager means that the traffic to the WNLB virtual IP address (in our case Terminal Server) is load balanced.

How to test: Please try to connect to the virtual IP address of the WNLB cluster via the Internet browser at https://<NLBvirtualIP>:5012 . You shall perform this test from all the subnets where MFPs with the embedded terminal are located.

Expected result: Terminal Server test page has to be displayed properly and links on the test page are functional.

Troubleshooting: If Terminal Server test page is not displayed properly, verify that YSoft SafeQ Terminal Server service is running on all the nodes that are part of WNLB cluster. If necessary, analyze the log files.

2. Stopping YSoft SafeQ Terminal Server service automatically unregisters node from WNLB

images/download/attachments/21955736/one_node_down.png

This status in WNLB manager means that one of the nodes is offline due to some error or due to the maintenance reasons. For example when Terminal Server service is stopped or when the server is not available.

How to test: Stop Terminal Server service on one of the nodes and try to connect to the virtual IP address of the WNLB cluster via the Internet browser at https://<NLBvirtualIP>:5012

Expected result: The node where the Terminal Server service has been stopped is automatically unregistered from WNLB as demonstrated on the picture above. It is possible to connect to the virtual IP address of the WNLB cluster via the Internet browser at https://<NLBvirtualIP>:5012

Troubleshooting: If node is not automatically unregistered, make sure that all the changes in system settings were applied as recommended in the Y Soft Help. Optionally see Terminal Server log files.

3. Server failure automatically unregisters node from WNLB

images/download/attachments/21955736/one_node_down.png

This status in WNLB manager means that one of the nodes is offline due to some error or due to the maintenance reasons. For example when Terminal Server service is stopped or when the server is not available.

How to test: Shutdown one server that is part of WNLB cluster and try to connect to the virtual IP address of the WNLB cluster via the Internet browser at https://<NLBvirtualIP>:5012

Expected result: The node which was disconnected/shut down is automatically unregistered from WNLB as demonstrated on the picture above. It is possible to connect to the virtual IP address of the WNLB cluster via the Internet browser at https://<NLBvirtualIP>:5012

Troubleshooting: If node is not automatically unregistered, verify the WNLB cluster configuration.

4. Start of YSoft SafeQ Terminal Server service automatically registers node in the WNLB

images/download/attachments/21955736/cluster_down.png

This status in WNLB manager means that Network Load Balancing Cluster is Down and Terminal Server does not accept any connections (i.g. both Terminal Servers are Offline).

How to test:

Stop Terminal Server service at least on one of the nodes to get a stopped state in WNLB manager
Start Terminal Server service on the node which is showing Stopped state in WNLB manager.

Expected result: In about one-two minutes the node that was unregistered from WNLB shall be registered again and it shall be in Converged state.

Troubleshooting: If node is not automatically registered, make sure that all the changes in system settings were applied as recommended in the Y Soft Help. Make sure that Terminal Server has established connection with the CML service. Optionally see Terminal Server log files.