Network Virtualization software Installed on LGs but get errors when running tests with NV enabled


Looking to a POC using Network Virtualization in Performance Center by enabling the NV insights and with Virtual location as “3G Typical”.

The below error message is displayed after starting the test:

Error: Service client "MShunraService" failed to post a message ,reason - target process/thread doesn't exist.                [MsgId: MERR-29738]

Error: Service client with id=303 failed to post a message ,reason - target process/thread doesn't exist.    [MsgId: MERR-29739]

Error: Communication error: The Client failed to send packet. The socket has been shut down.     [MsgId: MERR-10343]

Error: Client (-connection_id=)(-server_type=8)(-server_name=caw0211aa012)(-server_port=54345)(-server_fd_primary=2)(-user_extra_data=NAME)(-use_default_configuration_path) is not responding.      [MsgId: MERR-29992]

Anyone else come across this before or knows why this error may occur in order to determine the root cause. Thanks.

  • Hi, NV is now included in LR and PC as a standard feature, please re-submit your question under the PC production section, I will then ask someone from the PC team to review and respond. When you resubmit your question, please indicate what version of PC are you using. Thank you. 

  • Hi Sharon,

    Thanks for the reply.

    I have posted in Performance Center User Discussions with version numbers also included. 


    Much appreciated,


  • Hi, Have you raised a support case for this problem? please send me the support ticket ID so I can connect the appropriate engineer to this case. 



  • Hi Sharon,

    Thanks for your reply. Ticket number SD02531489. 

    I can suggest to the team to "try a custom Virtual Location with "0" latency and unlimited bandwidth". The output.mdb log file for the associated error (above) was sent to the Customer Support Engineer assigned to this ticket. I've yet to hear back so I thought I would ask in the community forum. 

    Very much appreciated,


  • Verified Answer

    The issue here was the NV driver did not support the network Maximum Transmission Unit MTU 9001 for Ethernet protocol which came as default when using an AWS EC2 server as the Load Generator host.

    The fix was to change the (MTU) on the host servers from 9001 to 1500. 

    Command to check the MTU number: netsh interface ipv4 show subinterface

    Command to change the MTU number to 1500: netsh interface ipv4 set subinterface "Ethernet" mtu=1500