In order to take advantage of the network efficiencies gained from using larger packets on a high performance network, you may want to enable JumboFrames in your network. This article describes the process for a Delphix Engine. This article uses the example of a Delphix Engine deployed in a VMware on-premise solution.
First and foremost, you must know what MTU is needed for your network. You may need to contact your Network team to find the proper value to use for MTU. In this example, I have set the MTU to 9000 which is traditional (or at least reasonably common) for JumboFrames. The idea is to match the MTU in use in your network. Technically JumboFrames is when the MTU is anything larger than 1500. Your network admins may have set their MTU to some other value, so it is imperative to discover this value prior to attempting the configuration.
Before making changes to the Delphix Engine, you need to first configure the virtual network interface from the virtualization product side. For VMware we have a document titled Customizing the Delphix Engine System Settings which describes the process of changing the configuration of the Delphix Engine virtual machine. In that document, you want to pay attention to the parts about networking configuration.
You need to perform the Delphix Engine side actions using the CLI and you should do so from the Engine Console. If you set an incorrect MTU, you will not be able to communicate to the Engine across the network. That is why it is critical to make these changes from the Engine Console. This allows you to recover from an errant network config. For VMware on-prem, you would open something like the VSphere Client or the VMware Web Client and open the system console to access a "virtual" console for the Engine.
Applicable Delphix Versions
- Click here to view the versions of the Delphix engine to which this article applies
Major Release All Sub Releases 6.0 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168
22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124
126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11 ,18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11
18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124 , 126.96.36.199, 188.8.131.52
184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11
After making the changes on the VMware side, you need to tell the Delphix Engine to start using jumbo frames. Since changing network settings from a network connection does not make much sense and could be problematic, you have to make these changes from a command line (CLI) login on the VMware console for the engine being changed.
Anytime you login to the Delphix Setup interface (whether via the GUI or the CLI) you must do so using an account that has sysadmin privileges. By default the engine is deployed with a single such account actually called "sysadmin", but you can add other sysadmin accounts and you can even remove the default account if desired.
After logging into the Delphix Setup CLI from the VMware console, you navigate to the network interfaces area.
my.delphix.engine > network interface
From here you can type
ls to get a list of network interfaces. For each desired interface, you need to select the interface.
my.delphix.engine network interface> ls Objects NAME MACADDRESS MTU ens160 02:dc:00:00:d2:f5 1500 my.delphix.engine network interface> select ens160
After selecting the interface, you can do an
ls to get all of the configuration details about the interface. For jumbo frames you are interested in MTU. To configure jumbo frames you will update, set the MTU, and then commit the change.
my.delphix.engine network interface 'ens160'> ls Properties type: NetworkInterface name: ens160 addresses: 0: type: InterfaceAddress address: 10.43.18.69/16 addressType: DHCP enableSSH: true sessionInUse: false state: OK device: ens160 macAddress: 02:dc:00:00:d2:f5 mtu: 1500 mtuRange: 68-9000 reference: NETWORK_INTERFACE-ens160 state: OK Operations update refresh my.delphix.engine network interface 'ens160'> update my.delphix.engine network interface 'ens160' update *> set mtu=9000 my.delphix.engine network interface 'ens160' update *> commit
Assuming that the chosen MTU is correct, you should be able to connect to the Delphix Engine GUI interface appropriate to the engine. If you are not able to connect to the UI after the change, then something went wrong. You may need to check with your Networking group to confirm that the MTU is correct. You may also want to revert the MTU using the same procedure above. Remember that for JumboFrames to work, all nodes in the network path must be configured for JumboFrames. (i.e. all switches, routers, firewalls etc.) It is not sufficient for just the end nodes of a conversation to be configured for JumboFrames.