InfoScale™ 9.0 Installation Guide - Solaris
- Section I. Planning and preparation
- Introducing Arctera InfoScale
- Licensing Arctera InfoScale
- System requirements
- Preparing to install
- Mounting the ISO image
- Setting up ssh or rsh for inter-system communications
- Obtaining installer patches
- Disabling external network connection attempts
- Verifying the systems before installation
- Setting up the private network
- Setting up shared storage
- Synchronizing time settings on cluster nodes
- Creating a root user
- Configuring LLT interconnects to use Jumbo Frames
- Creating the /opt directory
- Planning the installation setup for SF Oracle RAC systems
- Making the IPS publisher accessible
- Preparing zone environments
- Section II. Installation of Arctera InfoScale
- Installing Arctera InfoScale using the installer
- Installing Arctera InfoScale using response files
- Installing Arctera InfoScale using operating system-specific methods
- Completing the post installation tasks
- Section III. Uninstallation of Arctera InfoScale
- Uninstalling Arctera InfoScale using the installer
- About removing Arctera InfoScale
- Removing the Replicated Data Set
- Uninstalling InfoScale packages using the installer
- Uninstalling Arctera InfoScale using the pkgrm or pkg uninstall command
- Manually uninstalling InfoScale packages on non-global zones on Solaris 11
- Removing the Storage Foundation for Databases (SFDB) repository
- Uninstalling Arctera InfoScale using response files
- Uninstalling Arctera InfoScale using the installer
- Section IV. Installation reference
- Appendix A. Installation scripts
- Appendix B. Tunable files for installation
- About setting tunable parameters using the installer or a response file
- Setting tunables for an installation, configuration, or upgrade
- Setting tunables with no other installer-related operations
- Setting tunables with an un-integrated response file
- Preparing the tunables file
- Setting parameters for the tunables file
- Tunables value parameter definitions
- Appendix C. Troubleshooting installation issues
Configuring LLT interconnects to use Jumbo Frames
You can configure LLT interconnects to enable Jumbo Frames by increasing the maximum transmission unit (MTU) for physical systems and logical domains.
For physical systems enable Jumbo Frames at interface and LLT-level.
For logical domains enable jumbo Frames for LLT inside the logical domain. You need to ensure that Jumbo Frames are enabled for the virtual network (vnet), virtual switch (vsw) and the backend physical interface. If a physical switch is used between any cluster nodes to connect the interconnect, ensure that MTU value of switch is also set to a value that matches with other network components.
Physical systems
- Enable Jumbo frames at interface level.
- Set MTU value to 9000 or more.
- If IP is configured on a datalink, you will have to remove the IP before setting the MTU.
- Solaris 11: # dladm set-linkprop -p mtu=9000 <datalink>
If LLT is configured over UDP, set MTU for the IP interface
# ipadm set-ifprop -p mtu=4000 <interface>
- Verify that MTU is set to desired value for datalink.
# dladm show-link <datalink>
- Verify that MTU is set to desired value for the IP interface.
# ipadm show-ifprop -p mtu <interface>
- Enable Jumbo Frames at LLT-level.
Logical Domains
- Set MTU at virtual switch level.
Set MTU to 9000 or more while creating a virtual switch.
# ldm add-vsw mtu=9000 <vswitch-name> <io-ldom>
If virtual switch is already created, set MTU to the desired value.
# ldm set-vsw mtu=9000 <vswitch-name>
If vnets are already bound to this switch, you will have to reboot the node.
- Stop the logical domain.
- In some cases, you may have to set the mtu at virtual network layer.
# ldm set-vnet mtu=9000 <VIRTUAL-NETWORK-INTERFACE> <ldom>
- Verify that MTU is set to desired value for the datalink at control domain.
# dladm show-link <DATALINK>
- Verify that mtu is set to desired value for the virtual switch.
# ldm list-services <io-ldom>
- Verify that MTU is set at desired value for the virtual network interface.
# ldm list-bindings <ldom>
- Verify that MTU is set at datalink inside the logical domain.
# dladm show-link <datalink>
- Enable Jumbo Frames at LLT level.
For configuring LLT link with MTU size = 9000, change the "link" line in llttab as follows:
Solaris 11: link net1 /dev/net/net1 - ether - 9000