If a Virtual Exinda user is experiencing slowness of traffic, it could be resulting from choosing an incorrect interface type. This article lists out the checks needed to confirm whether this is the root cause for traffic slowness, and steps for fixing the same.
To determine whether the issue is resulting from an incorrect interface type (E1000 instead of VMXNET 3), check it in VMWare, or confirm the below:
- This error like this is found in sysdumps : e1000 0000:02:00.0 eth0: checksum_partial proto=81
- See if there is any multicast traffic displaying in the traffic capture (if the first byte of IP address is between 224 and 239 (included), it's a multicast address).
If there is any such multicast traffic, confirm that you (customer) can also see the multicast traffic on Realtime, which implies that it is not internal-to-internal.
If the above is confirmed, it indicates an incorrect interface type for the Exinda on VMWare (E1000 instead of VMXNET 3). This could happen when during the deployment some OVA template was used instead of ISO image, or when you (customer) have manually used SHELL to configure interfaces and add them to the bridge.
VMXNET 3 provides better performance on VMWare virtual Exinda. To fix the issue, make the following changes:
- Redeploy the Exinda from ISO image
- Change the interface type for Exinda to VMXNET3.
- Set the Guest OS to CentOS 6
Steps for the same are as follows:
- Download the ISO image from 7.4.13 release notes and upload to the VMWare datastore:
Release notes: Exinda Network Orchestrator 7.4.13 – GFI Support
- Go to VMWare server: (Recommended reference to sizing and resource management can be found here)
- Add a new virtual appliance
- For Select a Guest OS: Guest OS family: Linux Guest: OS Version: CentOS 6 (64-bit)
- Customizing hardware:
- CPUs: at least 4
- RAM: at least 6G
- Hard disk space: at least 250G
- NICs: Add in pairs(recommend 4 interfaces unless you need more bridges) and Adapter Type: VMXNET 3
Under CD Drive, select Datastore ISO File
In the Select File dialogue, navigate to the ISO file you uploaded and select it
Make sure the Drive is connected
Boot the VM to start the imaging of the Exinda
Let the process run until it completes
Disconnect the CD and boot up the Exinda
Note: If you do not have sufficient hard-disk space and you are not using services like edge cache and WAN memory, you can add less disk space than 250G, and take some of the allocated space for those services and add to monitor (database).
If the above does not resolve the issue, contact a support agent and provide the Sysdump and Traffic Capture files for investigation and resolution.