Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Slow network response of the SafeSync for Enterprise (SSFE) 2.0 server when hosted in Microsoft Hyper-V server

    • Updated:
    • 24 Apr 2014
    • Product/Version:
    • SafeSync for Enterprise 2.0
    • Platform:
    • Ubuntu 10.04 64-bit
Summary
The SSFE 2.0 server may experience performance issues, such as slow network and server response, when installed in the Microsoft Hyper-V server. 
Details
Public
To resolve the issue:
  1. Replace the existing Legacy Network Adapters.
    1. Turn off the SSFE server hosted in Hyper-V.
    2. On the Hyper-V Manager, right-click the SFFE server icon and select Settings.
    3. Remove all Legacy Network Adapter hardware. In the Settings window, select the Legacy Network Adapter from the left panel then click the Remove button.
      Removing network adapters
    4. Add two new Network Adapters. In the Settings window, click Add Hardware, select Network Adapter, and then click Add
      Adding network adapters
      Make sure that the Network Adapters are "Not connected" as shown below.
      Adding network adapters
  2. Install and load Hyper-V drivers for storage and networking.
    1. Log in to the SSFE shell.
    2. Edit /etc/initramfs-tools/modules using any text editor and add the following lines to the end of it:
      hv_vmbus
      hv_storvsc
      hv_blkvsc
      hv_netvsc
      Edit initramfs modules
    3. Run the command "update-initramfs –u" to install and load the Hyper-V drivers for storage and networking.
    4. Reboot the SFFE server.
    5. Confirm that the new drivers are loaded by running the "lsmod" command after rebooting.
      Confirm new drivers
  3. Update the MAC address inside Ubuntu OS with the correct MAC address of the newly added network interface controllers (NICs).
    1. Take note of the MAC address of the two new NICs and on the Hyper-V Manager:
      1. Right-click the SSFE icon and go to Settings > Network Adapter 1 > Advanced Features. Note the MAC address generated for the frontend0 NIC. You will use this in Steps 3.c and 3.d
      2. Right-click the SSFE icon and go to Settings > Network Adapter 2 > Advanced Features. Note the MAC Address generated for the database0 NIC. You will use this in Steps 3.c and 3.d
        Update NIC MAC address
    2. Log in to the SSFE shell.
    3. Edit /etc/udev/rules.d/99-osdp-net.rules. Look for the following two lines and update the MAC addresses accordingly:
      SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="{Network adapter1’s Mac} ", ATTR{type}=="1", KERNEL=="eth*", NAME="frontend0"
      SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="{ Network adapter2’s Mac }", ATTR{type}=="1", KERNEL=="eth*", NAME="database0"
    4. Edit /etc/udev/rules.d/70-persistent-net.rules. Look for the following lines and modify "eth2" and "eth3" to "eth0" and "eth1" respectively. Use the MAC address as a reference.
      SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="{ Mac } ", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
      SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="{ Mac} ", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"
    5. Reboot the SSFE server.
    6. Log in to the SSFE server shell and run the "ifconfig" command to confirm that all network adapters are detected. Database0, frontend0, and lo should be listed.
  4. Connect the new Network Adapters to the appropriate networks.
    1. On the Hyper-V Manager, right-click the SSFE server icon and select Settings.
    2. Select the Network Adapters one at a time and connect them to the appropriate Virtual Switch. The frontend0 NIC should be connected to the production network while the database0 NIC should be connected to a private switch.
      Connect the network adapters to a virtual switch
    3. On the SSFE server shell, run the "/etc/init.d/networking restart" command.
    4. Test the connection of the networks. Ping the SSFE server from a workstation. You should be able to connect immediately.
      Your connection would actually depend on your network latency.
Premium
Internal
Rating:
Category:
Configure; Troubleshoot; Deploy; Install
Solution Id:
1099492
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.