Shulou(Shulou.com)06/02 Report--

Reference KB: http://support.citrix.com/article/CTX133877

When multiple streaming NIC is assigned to a PVS server, the following symptoms occur on the Provisioning Services (PVS) server.

Example

An environment with five streaming NIC has the following symptoms:

When displaying the PVS console where the connected device is clicked, the following symptoms may be experienced:

Server timeout error 4002

List the abnormal delays of 3 to 4 minutes for connected devices

The PVS console stops responding

Images added by the user

Solution

Watch out! Before using the Registry Editor, refer to the disclaimer at the end of this article.

Complete the following to resolve this issue:

1. On the PVS Server computer, under the HKLM\ software\ citrix\ provisioningServices\ Manager key, create the registry DWORD RelayedRequestReplyTimeoutMilliseconds and set it to 50 ms.

Note: make sure you choose decimal, not hexadecimal.

2. Create a DWORD RelayedRequestTryTimes and set it to 1.

The default value is 2.

3. Open the PVS server console and select the Show Connected Devices command to test.

Cause of the problem

When you run the Show Connected Devices command from the PVS console, it sends the request to each interface bound to the streaming service, to each target device, with a default timeout of 5000 milliseconds per NIC, resulting in a search time of 10 seconds per device.

Example:

5 NIC,1 currently connected target devices will return Show Connected Device within 50 seconds.

You can clearly see in the flow log that it is searching for each IP address assigned to the stream service:

2012-05-25 10 GetRelayedRequestTryTimes-= 2 2012-05-25 10 GetRelayedRequestTryTimes-= 2 2012-05-25 10 DEBUG CManagerConfig:: GetRelayedRequestReplyTimeoutMilliseconds-= 5000 2012-05-31 14 1414 0x00000fdc 47470 [0x00000e7c] DEBUG CManagerConfig:: GetServerIpGroupTryTimes-= 2 2012-05-31 14 1414 GetRelayedRequestTryTimes 46470 [0x00000e7c] DEBUG CManagerConfig:: GetServerReplyTimeoutMilliseconds-= 50000 2012-05-31 1414 GetRelayedRequestTryTimes 46470 [0x00000e7c] debugging CManagerReplyReceiver:SendMessageToServer,requestId = 0

2012-05-31 14 TryEachIpAddressIteratively 47V 46486 [0x00000e7c] debug in CManagerReplyReceiver:

2012-05-31 14-14-47-41-86 [0x00000e7c] DEBUG will try to send a request to ip address = 2887 140615 Jing port = 6911

2012-05-31 14 47 46486 [0x00000e7c] debug CManagerReplyReceiver:sendMessageAndWaitForResult

2012-05-31 14 ID 47RV 46501 [0x00000e7c] DEBUG adds a future to request ID 0

2012-05-31 1414 47 46501 [0x00000e7c] DEBUG to, about to send 80 bytes

2012-05-31 14 47 46501 [0x00000e7c] DEBUG sends 80-byte message

2012-05-31 14 47V 56516 [0x00000e7c] DEBUG futureResult.get failed, error = 121,

2012-05-31 14 47RV 56516 [0x00000e7c] error remote request timeout

2012-05-31 14 RemoteRequestTimedOut 4715 0x00000e7c] DEBUG for requestId = 0, return result =-32718 (RemoteRequestTimedOut). wait for.

2012-05-31 14 4715 56532 [0x00000e7c] number of entries in the DEBUG futureMap = 0

2012-05-31 14 ip address 47 0x00000e7c 56532 [0x00000e7c] DEBUG will attempt to send a request to port = 6911

2012-05-31 14 4715 56532 [0x00000e7c] debug CManagerReplyReceiver:sendMessageAndWaitForResult

2012-05-31 14 ID 47 ID 4715 56532 [0x00000e7c] DEBUG adds a future to request ID 0

2012-05-31 14 47 56532 [0x00000e7c] DEBUG to, about to send 80 bytes

2012-05-31 14 47 56532 [0x00000e7c] DEBUG sends 80-byte message

2012-05-31 14 4806547 [0x00000e7c] DEBUG futureResult.get failed, error = 121,

2012-05-31 14 4806547 [0x00000e7c] ERROR remote request timed out

2012-05-31 14 result 4806547 [0x00000e7c] DEBUG for requestId = 0, return result =-32718 (RemoteRequestTimedOut). wait for.

2012-05-31 14 4806547 [0x00000e7c] number of entries in the DEBUG futureMap = 0

2012-05-31 14 ip address 4806547 [0x00000e7c] DEBUG will attempt to send a request to port = 6911

2012-05-31 14 sendMessageAndWaitForResult 4806547 [0x00000e7c] debug in CManagerReplyReceiver: sendMessageAndWaitForResult

2012-05-31 14 ID 4815 06547 [0x00000e7c] DEBUG adds future to request ID 0

2012-05-31 14 4815 06547 [0x00000e7c] DEBUG to, about to send 80 bytes

2012-05-31 14 4815 06547 [0x00000e7c] DEBUG sends 80 bytes of 80 byte messages

2012-05-31 14 48V 16562 [0x00000e7c] DEBUG futureResult.get failed, error = 121,

2012-05-31 14 48purl 16562 [0x00000e7c] error remote request timeout

2012-05-31 14 result 48V 16562 [0x00000e7c] DEBUG for requestId = 0, return result =-32718 (RemoteRequestTimedOut). wait for.

Number of entries in 2012-05-31 14 4815 0x00000e7c 16562 [entry] DEBUG futureMap = 0

2012-05-31 14 ip address 1440 48 ip address 16562 [0x00000e7c] DEBUG will attempt to send a request = 2887139847 Magi port = 6911

2012-05-31 14 sendMessageAndWaitForResult 48lo 16562 [0x00000e7c] debug in CManagerReplyReceiver: sendMessageAndWaitForResult

2012-05-31 14 ID 4815 0x00000e7c 16562 [0x00000e7c] DEBUG adds a future to request ID 0

2012-05-31 1414 48purl 16562 [0x00000e7c] DEBUG to, about to send 80 bytes

2012-05-31 14 48 16562 [0x00000e7c] DEBUG sends 80 bytes of 80 byte messages

2012-05-31 14 4815 26577 [0x00000e7c] DEBUG futureResult.get failed, error = 121,

2012-05-31 14Flux 48Rd 26577 [0x00000e7c] error remote request timeout

2012-05-31 14 RemoteRequestTimedOut 4815 [0x00000e7c] DEBUG for requestId = 0, the result returned is-32718 (RemoteRequestTimedOut). wait for.

The number of entries in 2012-05-31 14 4814 0x00000e7c 26577 [0x00000e7c] DEBUG futureMap = 0

2012-05-31 14 ip address 4815 0x00000e7c [0x00000e7c] DEBUG will attempt to send a request to ip address = 2887139591

2012-05-31 14 48V 26577 [0x00000e7c] debug CManagerReplyReceiver:sendMessageAndWaitForResult

2012-05-31 14 ID 48RV 26577 [0x00000e7c] DEBUG adds the future to request ID 0

2012-05-31 14 48Rd 26577 [0x00000e7c] DEBUG to, about to send 80 bytes

2012-05-31 14 48 26577 [0x00000e7c] DEBUG sends 80 bytes of 80 byte messages

2012-05-31 14 48A 36592 [0x00000e7c] DEBUG futureResult.get failed, error = 121,

2012-05-31 14Flux 48RV 36592 [0x00000e7c] error remote request timeout

2012-05-31 14 RemoteRequestTimedOut 4815 [0x00000e7c] DEBUG for requestId = 0, return result =-32718 (RemoteRequestTimedOut). wait for.

Number of entries in 2012-05-31 14 4815 356 92 [0x00000e7c] DEBUG futureMap = 0

2012-05-31 14 ip address 48A 0x00000e7c 36592 [0x00000e7c] DEBUG will attempt to send a request to port = 6911

2012-05-31 14 48V 36592 [0x00000e7c] debug CManagerReplyReceiver:sendMessageAndWaitForResult

2012-05-31 14 ID 48A 0x00000e7c 36592 [0x00000e7c] DEBUG adds a future to request ID 0

2012-05-31 14 4815 [0x00000e7c] DEBUG to, about to send 80 bytes

2012-05-31 14 4814 36592 [0x00000e7c] DEBUG sends 80-byte message

2012-05-31 14 dispatchPacket 48V 37247 [0x000030fc] debug CManagerReplyReceiver::

2012-05-31 14 id 48 id 37247 [0x000030fc] DEBUG header opcode =-2147221501, request id = 0

2012-05-31 14 ManagedServer 48 0x000030fc 37247 [0x000030fc] DEBUG process ManagedServer reply

2012-05-31 14 DEBUG in 48 0x000030fc 37247 [0x000030fc] CREMoteManagedServer:: handleReply

2012-05-31 14 id 4815 0x000030fc 37247 [0x000030fc] DEBUG handles the reply of request id = 0

2012-05-31 14 requestId 48 requestId 37263 [0x000030fc] DEBUG found the future of requestId

2012-05-31 14 48 37263 [0x000030fc] DEBUG transforms the reply status of rebalancing reply. Default is successful.

2012-05-31 14 harvestReplyDataFromMessage in DEBUG:: harvestReplyDataFromMessage in 2012-05-31 14 DEBUG 48 DEBUG 37278 [0x000030fc] CREMoteManagedServer

2012-05-31 14 requestId 48 requestId 37278 [0x000030fc] DEBUG reply is used for rebalancing request, requestId = 0

2012-05-31 14 48V 37278 [0x000030fc] the debug value from the reply is 21

2012-05-31 14 requestId 48 requestId 37278 [0x000030fc] DEBUG entry is added to the data result graph of requestId = 0

2012-05-31 14 requestId 48 requestId 37294 [0x00000e7c] result = 0 (success) success. wait for.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.