ClearCube R-Series Data Center Products - Manual (Page 131)

R-Series Data Center Products User’s Guide Troubleshooting • 107
Chapter 5. Troubleshooting
If you have any problems with your system, please check the following items prior to
calling for support.
PCoIP Issues
PCoIP Host on Different Subnet Than PCoIP Client Is
Unable to Wake Up from Various Power States
This issue is restricted to R3040S blades that contain V5120, V5220, and V5240
PCoIP host cards. When a PCoIP host system is shut down (S5) or is in hibernate (S4),
the PCoIP host transitions to receive a Wake-on-Lan (WOL) packet. Because the host
is no longer powered (or in low power mode depending on architecture), the TCP/IP
stack is no longer maintained. The PCoIP host will now only respond to a WOL
packet and will not respond to an ARP WHOHAS message from the local
gateway/router.
After the PCoIP host has been powered down for a short amount of time (typically 5
to 10 minutes), the entry for the PCoIP host in the gateway/router's ARP table will
decay. The gateway/router will now send an ARP WHOHAS message to determine
how to route the WOL packet. Because the PCoIP host cannot respond to the APR
WHOHAS message, a WOL packet will be lost.
The issue is seen under the following conditions
• The PCoIP host and client are not on the same subnet
• The PCoIP host has been in a sleep state for greater than approximately 5 to 10
minutes (gateway/router dependent)
The following list details multiple workarounds for this issue.
• Manually power on or power cycle the host.
• If you have a ClearCube Sentral server in your environment that is on the same
subnet as the host, use Sentral to wake up the host.
• Connect PCoIP host and clients in your environment using direct connections.
• Use a single subnet for PCoIP hosts and clients in your environment. If you use
multiple subnets, ensure that connected clients and hosts are on the same subnet.
• Use static IPs and permanent ARP table entries for each PCoIP host.