Escolar Documentos
Profissional Documentos
Cultura Documentos
Manual
Release 6.0.0
LogPoint
1 LogPoint Installation 2
1.1 Fresh Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 LogPoint Release Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Console Configuration 6
2.1 reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 poweroff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3 change-ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.4 change-date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.5 start-support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.6 stop-support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.7 repodir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.8 ethbonding (LACP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.9 uploadpatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.10 route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.11 tcpdump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.12 addfwports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.13 rmfwports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.14 iptables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.15 mount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.16 umount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.17 zfs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.18 zpool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.19 gdisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.20 sgdisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.21 grub-install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.22 LP Diag Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.22.1 Show Help Texts for LP Diag Commands . . . . . . . . . . . . . . . . . . . . 10
2.22.2 Enable LP Diag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.22.3 Disable LP Diag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.22.4 Check Status of LP Diag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.23 ifup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.24 ifdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3 System Requirements 12
3.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4 Supported Browsers 13
i
Welcome to LogPoint Installation Manual, Release 6.0.0
The Installation Manual of LogPoint contains information on how to install LogPoint, its various
system requirements and console configuration.
Refer to this manual if you are using LogPoint for the first time.
CONTENTS 1
CHAPTER
ONE
LOGPOINT INSTALLATION
3. The installer detects the number of Hard Disk Drive(s) (HDD) present in the system and provides
various options of disk layout accordingly. The available types of disk layout according to the
number of HDD are:
Number of HDD Disk Layout
1 Normal or Single
2 Mirror
3 or More RAIDZ
Note:
• When selecting the RAIDZ mode, the first three disks will be used for OS and Application
installation. The remaining disks, if any, can be used to extend the disk space or used as
L2ARC (Level 2 Adjustable Replacement Cache) or ZIL (ZFS Intent Log) for enhancing
the read/write performance of ZFS. This can be done using ZFS commands.
• The ZFS (Zettabyte File System) used in the LogPoint, itself provides software-defined so-
lution for disk based redundancy (Mirror, RAIDZ). Hence, it is not recommended to use
hardware based RAID. Doing so will limit the ZFS to perform self healing on checksum
failures.
2
Welcome to LogPoint Installation Manual, Release 6.0.0
The first reboot of the installer occurs. At this point, the user needs to either manually eject the
installation DVD, or, select the option to boot from hard drive from the Boot Manager during the
bare metal installations. Not doing so will force the system to boot from the DVD again.
Note: A blank screen might appear in the terminal after the second reboot of the system, on completion
of the installation on a bare-metal environment. The terminal can be changed using ALT + F2 or ALT +
Left or Right direction key. This issue, however, does not affect the installation process in any way.
5. After the installation process completes, login using the following credentials.
Username: li-admin
Password: changeme
Note: The system reboots in order to complete the installation of LogPoint v6.0.0.
Click the logpoint logo on the upper left corner of the LogPoint user interface that displays the currently
installed version of LogPoint. The About pop-up panel also contains information on where to find the
product documentation and how to contact LogPoint Support.
TWO
CONSOLE CONFIGURATION
After successfully installing LogPoint, you can now access the system through the console using the
username li-admin. You can either use a default password or ssh to access the system. But, ssh li-
admin user will need an ssh pair. Once the access is granted, you need to change the password using
passwd command.
You can create and use ssh pair for li-admin by following the steps given below.
Configuring SSH pair for li-admin
1. Create an ssh pair in LogPoint using the command ssh-keygen -t rsa.
2. Copy the public key to authorized keys, using command cp id_rsa.pub ~/.ssh/authorized_keys.
3. Move the private key into a remote device. You can use scp as well. Use command scp -i id_rsa
li-admin@<destination_ip>:<path_in_remote_device>.
4. Now, you can ssh into LogPoint from remote device. Use command ssh -i <id_rsa_path> li-
admin@<LogPoint_Server_IP>.
Note: li-admin users can view the README.txt file in home folder of their LogPoint.
2.1 reboot
2.2 poweroff
2.3 change-ip
You can change the system IP using change-ip command. You can change primary interface for multiple
interfaces using:
6
Welcome to LogPoint Installation Manual, Release 6.0.0
2.4 change-date
You can change the time and date of your system using change-date command. Provide the date-time
in yyyy-mm-dd hh:mm:ss or yyyy/mm/dd hh:mm:ss format.
2.5 start-support
You can enable remote connection for support using start-support command. Use this command to
permit support team to access your system. The start-support command starts the support connection
and keeps the support-port open for specified amount of time. If the time is not specified, then the
support-port is opened for 1 hour only.
The syntax for start-support command is
For example:
The syntax for start support connection with 1 hour timeout
start-support 1
start-support infinite
2.6 stop-support
Once your issues are fixed, you can disable support, using stop-support command.
2.7 repodir
You can bind multiple interfaces in LogPoint to use a common virtual interface using LACP feature.
Also, you can execute ethbonding command to bind the interfaces.
To add bond:
2.4. change-date 7
Welcome to LogPoint Installation Manual, Release 6.0.0
To remove bond and to get the original interfaces intact, follow the syntax:
Note: The li-admin user has to manually reboot the system for the changes to take effect.
2.9 uploadpatch
You can use uploadpatch to upload the specified patch. It is recommended that you use the uploadpatch
command in case of large sized patch file as this type of file might not be uploaded from GUI due to
time out limits.
2.10 route
You can use route command to show and manipulate the IP routing table.
2.11 tcpdump
2.12 addfwports
You can use addfwports command to add custom firewall ports that are required for some installations
specific requirement.
2.13 rmfwports
You can use rmfwports to remove custom firewall ports that are added using addfwports.
2.14 iptables
You can use iptables command to add or delete firewall rules in LogPoint to support all the combination
of arguments. These configurations are temporary, and will last until new configurations are generated.
2.15 mount
You can use mount command to attach the filesystem found on a device to the big file tree.
2.9. uploadpatch 8
Welcome to LogPoint Installation Manual, Release 6.0.0
2.16 umount
You can use umount command to detach or free the the loop device (if any) associated with mount.
Note: You can mount and unmount the remote Network File System (NFS) and Common Internet File
System (CIFS) using the mount and umount commands.
2.17 zfs
You can use the zfs command to configure ZFS datasets within a ZFS storage pool. A dataset is identified
by a unique path within the ZFS namespace.
2.18 zpool
You can use the zpool command to configure ZFS storage pools. A storage pool is a collection of devices
that provides physical storage and data replication for ZFS datasets. All datasets within a storage pool
share the same space.
2.19 gdisk
You can use the gdisk command to create and manipulate the Interactive GUID partition table (GPT).
It will automatically convert an old-style Master Boot Record (MBR) partition table or BSD disk label
stored without an MBR carrier partition to the newer Globally Unique Identifier (GUID) Partition Table
(GPT) format, or will load a GUID partition table.
2.20 sgdisk
You can create and manipulate the Command-line GUID partition table (GPT) manipulator for Linux
and Unix using the sgdisk command.
2.21 grub-install
The command grub-install lets you generate a GRUB core image using grub-mkimage and installs it
in LogPoint. You must specify the device name on which you want to install GRUB. For example:
grub-install INSTALL_DEVICE
Note: The device name INSTALL_DEVICE is an OS device name or a GRUB device name.
2.16. umount 9
Welcome to LogPoint Installation Manual, Release 6.0.0
LP Diag is a script that extracts various information from LogPoint. You can add a cron job (scheduled
task) that runs periodically to fetch the diagnostic statistics to the machine.
lpdiag -h
where,
H = Frequency in hour(s) and value must be between 1-23
M = Frequency in minute(s) and value must be between 1-59
R = Retention period in second(s). Retention period is the time
˓→duration for which the diagnostic
information is stored in the system.
Examples:
lpdiag -e -H 10 -R 21600
lpdiag -e -M 30 -R 21600
lpdiag -d
Note:
• The options -e and -d cannot be specified at the same time.
• The options -H and -M cannot be specified at the same time.
lpdiag -s
2.23 ifup
The command ifup brings a network interface up, making it available to transmit and receive data.
2.24 ifdown
The command ifdown takes a network interface down, placing it in a state where it cannot transmit or
receive data.
2.23. ifup 11
CHAPTER
THREE
SYSTEM REQUIREMENTS
If you are performing a comprehensive evaluation of LogPoint for production deployment, we recom-
mend that you use hardware typical of your production environment. This hardware should meet or
exceed the recommended hardware capacity specifications below.
CPU Minimum Quad-core
Memory Minimum 8 GB
Disk Minimum 100 GB
Note:
• Depending upon log volume, hardware requirements are subject to change.
• Performance might be degraded a little in Virtual Environments as compared to Bare-metal instal-
lations.
• The ZFS (Zettabyte File System) used in the LogPoint, itself provides software-defined solution
for disk based redundancy (Mirror, RAIDZ). Hence, it is not recommended to use hardware based
RAID. Doing so will limit the ZFS to perform self healing on checksum failures.
12
CHAPTER
FOUR
SUPPORTED BROWSERS
LogPoint will work with a variety of Internet browsers, but it is best supported by the following:
• Safari Version 9.0
• Google Chrome Version 49
• Firefox Version 45
• Internet Explorer 11
Note: Browser requests from Internet Explorer 5 (IE5) are not supported in order to handle a specific
security vulnerability.
13