LiveAction currently support Linux Red Hat Enterprise Linux 6.X and CENTOS 6.X. The recommended version is 6.4 or 6.5 based on the Linux releases.

Transcription

1 LiveAction Linux Installation Guide Installing LiveAction 4.0 for the first time Requirements Linux OS: LiveAction currently support Linux Red Hat Enterprise Linux 6.X and CENTOS 6.X. The recommended version is 6.4 or 6.5 based on the Linux releases. The Linux OS should also be installed with a GUI such as GNOME to run the management console for the server. Hardware and Performance: The hardware and performance specification for Linux is the same as the Windows version, please refer to the user guide for more details. Installing the LiveAction Server The Linux version of the LiveAction server is packaged as an RPM and is distributed as a self-contained shell script (.sh) file with the RPM package embedded in it. Currently, installation must be handled by the root user or a non-root user that has used the su or sudo command to gain root privileges. The file needs to be copied onto the Linux computer.

2 To install, type chmod +x LiveActionServer-3_1_8-1.x86_64.sh Then type./liveactionserver-3_1_8-1.x86_64.sh Hit return when it asks to enter the data directory. Default is /var/liveaction/data/3.1 Relevant Linux Paths RPM LiveAction Server Installation: /opt/liveactionserver/3.1 Common Data Area: /var/liveaction/common Default Data Directory: /var/liveaction/data/3.1 LiveAction Server Daemon Startup Script: /etc/init.d/liveactionservice PID Directory: /var/run/liveaction Running the Management Console The management console must also be run using root. A warning message will be displayed if the management console is run by a non-root user. The following script will launch the management console: /opt/liveactionserver/3.1.8/lamanagementconsole This will start up the LiveAction Server Management Console GUI. To start the LiveAction Server daemon, click on Manage Start Service.

3 To stop the LiveAction Server Daemon, click on Manage Shutdown Service.

4 The LiveAction Server daemons can also be started and stopped via command line. This is done via the root user account. service LiveActionService start service LiveActionService stop service LiveActionService restart Note: If the LiveAction server daemon did not start up properly, verify that the hostname for the device is also statically configured to the loopback IP address in the /etc/hosts file. cat /etc/hosts localhost localhost.localdomain hostname Note: The service LiveActionService stop' command can be used to forcefully terminate the daemon if you cannot connect to the service via the management console. Loading the LiveAction Permanent License 1. Copy the license key from your LiveAction representative to a desktop location accessible by the LiveAction Server. 2. Start the LiveAction Management Console as shown above. 3. Follow the Licensing Assistant instructions to load the valid license file. 4. Activate the LiveAction permanent license via off-line mode by registering the license via using a different PC that does have Internet access. (Please see the LiveAction User Guide if the LiveAction server has an internet connection). 5. From the LiveAction Management Console license tab, select Activate License. 6. Select Activate Offline, and then click Next. 7. The License Number and Activation Key will be displayed. This information must be sent to the LiveAction customer representative to complete off-line activation. Click Copy to store the information and paste it into a text file to send to the LiveAction representative. 8. Click Cancel to exit the License Activation Assistant. You can continue to use the LiveAction software for up to seven days prior to completing the activation process. 9. Using another computer that does have an Internet connection, your contact information and saved License Number and Activation key and send it to your LiveAction representative. Your license will be processed and a permanent key sent to you. 10. When you receive the new Activation Key file, copy it to a location accessible by the LiveAction server machine. 11. Start the LiveAction Management console and select the License tab. Select Upgrade License to restart the Licensing Assistant. 12. Select I have a valid license file, and then click Next. 13. On the License Location screen, browse to locate the Activation Key file that you saved. 14. Click Finish to complete license activation. Note: After loading the permanent license, you have seven days to activate it before LiveAction stops operating. However, you can still activate your license any time after the seven days to permanently restore LiveAction operation.

5 Configuring the Firewall If a firewall is active on the server, the following ports need to be opened. UDP 2055 NetFlow polling UDP 6343 sflow polling TCP 7000 LiveAction Client TCP 8092 Web start launch page (if using the Web Start client) Port configuration is handled by the root user or a non-root user that has used the su or sudo command to gain root privileges. Type: iptables I INPUT p udp -dport 2055 j ACCEPT iptables I INPUT p udp -dport 6343 j ACCEPT iptables I INPUT p tcp -dport syn j ACCEPT iptables I INPUT p tcp -dport syn j ACCEPT

6 Installing the LiveAction Client Any client can be used with the Linux LiveAction server including the Windows installed client, webstart client and Mac OS client. Use the following steps to install and run the Windows version of the LiveAction client via the web start for details on how to install the other clients, please refer to the User Guide. Type in your Windows browser. In this example, the httpserver.port is using the default value, Type if the httpserver.secure value is True. The values for httpserver.port and httpserver.secure are defined in the LiveAction Server Properties tab. Click on the Launch Client in the header bar at the top of the web page or click on Launch LiveAction Client text in the body of the web page.

7 Install LiveAction Client Default settings are used during installation. Depending on your client configuration, you may be asked to install a Java run-time environment installer. Click on Run to proceed. Enter your Client credentials to log in to the LiveAction Client. LiveAction will use your log in credentials to load your most recent saved LiveAction client configuration. Click on OK to start the LiveAction client. Your LiveAction Client upgrade is now complete.

8

9 Performance Tuning of Linux Server and Node Suggested Linux settings to improve LiveAction performance have been tested and are listed below. These settings will not take effect until the system is rebooted. Please refer to reference website for more details: Swap and Cache Performance These settings helps swapping and cache performance. Add to /etc/sysctl.conf file # lower use of swap space vm.swappiness = 10 # hold more data in cache vm.dirty_background_ratio = 50 # % of total memory). Start writing dirty pages to disk in background. vm.dirty_ratio = 80 # % of total memory). Start writing dirty pages to disk. vm.dirty_writeback_centisecs = 1000 # how often the checks for dirty page writeout occurs. vm.dirty_expire_centisecs = 3000 # how long a dirty page can be in cache before writeout.

10 File System Performance *WARNING* Please create a backup of /etc/fstab prior to making the following changes! Incorrectly modifying this file can cause the Linux system to fail startup. Quick Explanation of /etc/fstab The /etc/fstab handles the mounting of Linux partitions and applies the specified mount options. The format in the /etc/fstab file is: DEVICE MOUNTPOINT FILESYSTEMTYPE MOUNTOPTIONS DUMP# CHECK# DEVICE can be in the form of a long UUID string or typically a /dev/sdax MOUNTPOINT is where the device will be placed FILESYSTEMTYPE will be ext4 MOUNTOPTIONS is where the performance options will be applied to. These only apply to this partition DUMP# and CHECK# can be left as 1 2 This greatly depends on how the customer has partitioned their system, when they installed CentOS. For the sake of simplicity, just remove the noexec,nosuid,nodev options. They are mostly for security reasons. LiveAction mostly does its heavy reading/writing on a single location (/var/liveaction/). The idea behind the mount option changes is to improve the read/write performance on that specific partition. If the customer has a separate partition for /var then you can improve the /var partition s performance. If the customer has created a single root (/) partition for the entire OS, then the entire OS will be affected. o It s not a best-practice, but it s not overly terrible to do. Apply the mount options to wherever the /var partition is. If /var is not explicitly identified then it will be part of the root (/) partition. Purpose of proposed mount options: defaults Contains all the default settings for mounting a disk properly. Do not forget this! noatime Linux updates the file it is reading, identifying when it was last access. Noatime stops you from doing these unnecessary disk writes. commit=10 System holds on to the file for about 10s before writing to disk. journal_ioprio=4 There are two IOs for an EXT4 partition (journaling and disk IO). This option makes diskio slightly higher in priority. data=writeback Fastest option for handling disk IO with a small tradeoff on data integrity. noexec (optional for security) Do not apply this on root (/) partition!! Prevents the execution of files on the specified partition. nodev (optional for security) Do not apply this on root (/) partition!! Prevents the creation of device files on the specified partition. nosuid (optional for security) Do not apply this on root (/) partition!! Prevents the assignment and use of suid flags on files for the specified partition. Example 1 Separate /var partition: Apply security options if you want! UUID=87f0fb9c ac-8ba1-15ea774b74ff /var ext4 defaults,noatime,commit=10,data=writeback,journal_ioprio=4,noexec,nodev,nosuid 1 2 Example 2 No separate /var partition: Do NOT apply security options! You will have a bad time. UUID=87f0fb9c ac-8ba1-15ea774babcd / ext4 defaults,noatime,commit=10,data=writeback,journal_ioprio=4 1 2

11 Note: The UUID is a unique identifier for the partition. Some folks do not use that, which is fine. In the cases where UUID is not used then it would generally look like this (with maybe different partition numbers): /dev/sda1 / ext4 MOUNTOPTIONS 1 1 /dev/sda2 /var ext4 MOUNTOPTIONS 1 2 The only thing you need to pay attention to is the second column, which should state what the desired mount point is. If you don t see a separate partition for /var, then your only option is to apply it on the root (/) partition.