Setting Up Unleashed Multi-Site Manager as a Virtual Machine

You can setup Unleashed Multi-Site Manager as a virtual machine, where, the VM image is a VMWare EXSI image that integrates the software with CentOS 6.10.
Minimum hardware requirements:
  • 8 GB memory
  • 4*1 processors
  • 50 GB hard disk
You can only use VMWare EXSI images to create a VM, and it is recommend to use EXSI version 6.5.
  1. Login to the VMware ESXI interface and go to Virtual Machines.

    Registering the VM

  2. Click Create/Register VM.
    The New virtual machine page appears.

    Creating a VM

  3. Select Deploy virtual machine from an OVF or OVA file and click Next.
  4. Type the name virtual machine and select the VM_UMM_2.2.0.0.40.ova file.

    Selecting the OVA File

  5. Click Next.
    Continue to click Next for the consequent screens, and click Finish to complete the VM creation.

    After you power off the device, you can edit the VM settings. You can change settings for the CPU, memory and hard disk according to your lab requirement.

    Editing VM Settings

  6. Power on the VM and wait several minutes to login to Unleashed Multi-Site Manager.

    After you login, you can do the following:

  7. Using SSH, establish a connection with Unleashed Multi-Site Manager to change the time zone and date. See the following example.

    [root@localhost ~]# date

    Fri Jun 29 04:14:46 EDT 2018

    [root@localhost ~]# tzselect

    Please identify a location so that time zone rules can be set correctly.

    Please select a continent or ocean.

    1) Africa

    2) Americas

    3) Antarctica

    4) Arctic Ocean

    5) Asia

    6) Atlantic Ocean

    7) Australia

    8) Europe

    9) Indian Ocean

    10) Pacific Ocean

    11) none - I want to specify the time zone using the Posix TZ format.

    #? 5

    Please select a country.

    1) Afghanistan 18) Israel 35) Palestine

    2) Armenia 19) Japan 36) Philippines

    3) Azerbaijan 20) Jordan 37) Qatar

    4) Bahrain 21) Kazakhstan 38) Russia

    5) Bangladesh 22) Korea (North) 39) Saudi Arabia

    6) Bhutan 23) Korea (South) 40) Singapore

    7) Brunei 24) Kuwait 41) Sri Lanka

    8) Cambodia 25) Kyrgyzstan 42) Syria

    9) China 26) Laos 43) Taiwan

    10) Cyprus 27) Lebanon 44) Tajikistan

    11) East Timor 28) Macau 45) Thailand

    12) Georgia 29) Malaysia 46) Turkmenistan

    13) Hong Kong 30) Mongolia 47) United Arab Emirates

    14) India 31) Myanmar (Burma) 48) Uzbekistan

    15) Indonesia 32) Nepal 49) Vietnam

    16) Iran 33) Oman 50) Yemen

    17) Iraq 34) Pakistan

    #? 9

    Please select one of the following time zone regions.

    1) Beijing Time

    2) Xinjiang Time

    #? 1

    The following information has been given:

    China

    Beijing Time

    Therefore TZ='Asia/Shanghai' will be used. 
    			 

    Local time is now: Fri Jun 29 16:14:59 CST 2018.

    Universal Time is now: Fri Jun 29 08:14:59 UTC 2018.

    Is the above information OK?

    1) Yes

    2) No

    #? 1

    You can make this change permanent for yourself by appending the line 
    			  TZ='Asia/Shanghai'; export TZ 
    			 to the file '.profile' in your home directory; then log out and log in again. 
    			 

    Here is that TZ value again, this time on standard output so that you 
    			 can use the /usr/bin/tzselect command in shell scripts: 
    			 Asia/Shanghai 
    			 

    [root@localhost ~]# vi /etc/sysconfig/clock //change to ZONE="Asia/Shanghai"

    [root@localhost ~]# rm -rf /etc/localtime

    [root@localhost ~]# ln -s /usr/share/zoneinfo/Asia/Shanghai /etc/localtime

    [root@localhost ~]# cat /etc/sysconfig/clock

    ZONE="Asia/Shanghai"

    [root@localhost ~]# date -s 7/12/2018

    Thu Jul 12 00:00:00 CST 2018

    [root@localhost ~]# date -s 11:34:30

    Thu Jul 12 11:34:30 CST 2018

    [root@localhost ~]# date

    Thu Jul 12 11:34:32 CST 2018

  8. If you have modified the VM settings (refer Step 6), then you can change the size of the linux hard disk as well. See the following example.

    [root@localhost ~]# df -h

    Filesystem Size Used Avail Use% Mounted on

    /dev/mapper/VolGroup-lv_root 44G 7.5G 35G 19% /

    tmpfs 7.8G 0 7.8G 0% /dev/shm

    /dev/sda1 485M 32M 428M 7% /boot

    [root@localhost ~]# fdisk -l

    Disk /dev/sda: 322.1 GB, 322122547200 bytes

    255 heads, 63 sectors/track, 39162 cylinders

    Units = cylinders of 16065 * 512 = 8225280 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes

    Disk identifier: 0x00057088

    Device Boot Start End Blocks Id System

    /dev/sda1 * 1 64 512000 83 Linux

    Partition 1 does not end on cylinder boundary.

    /dev/sda2 64 6528 51915776 8e Linux LVM

    Disk /dev/mapper/VolGroup-lv_root: 47.8 GB, 47789899776 bytes

    255 heads, 63 sectors/track, 5810 cylinders

    Units = cylinders of 16065 * 512 = 8225280 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes

    Disk identifier: 0x00000000

    Disk /dev/mapper/VolGroup-lv_swap: 5368 MB, 5368709120 bytes

    255 heads, 63 sectors/track, 652 cylinders

    Units = cylinders of 16065 * 512 = 8225280 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes

    Disk identifier: 0x00000000

    [root@localhost ~]# fdisk /dev/sda

    WARNING: DOS-compatible mode is deprecated. It's strongly recommended to 
    			  switch off the mode (command 'c') and change display units to 
    			  sectors (command 'u'). 
    			 

    Command (m for help): n

    Command action

    e extended

    p primary partition (1-4)

    p

    Partition number (1-4): 3

    First cylinder (6528-39162, default 6528):

    Using default value 6528

    Last cylinder, +cylinders or +size{K,M,G} (6528-39162, default 39162):

    Using default value 39162

    Command (m for help): t

    Partition number (1-4): 3

    Hex code (type L to list codes): 8e

    Changed system type of partition 3 to 8e (Linux LVM)

    Command (m for help): wq

    The partition table has been altered! 
    			 

    Calling ioctl() to re-read partition table.

    WARNING: Re-reading the partition table failed with error 16: Device or resource busy. 
    			 

    The kernel still uses the old table. The new table will be used at 
    			  the next reboot or after you run partprobe(8) or kpartx(8) 
    			 

    Syncing disks. 
    			 

    [root@localhost ~]# fdisk -l

    Disk /dev/sda: 322.1 GB, 322122547200 bytes

    255 heads, 63 sectors/track, 39162 cylinders

    Units = cylinders of 16065 * 512 = 8225280 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes

    Disk identifier: 0x00057088

    Device Boot Start End Blocks Id System

    /dev/sda1 * 1 64 512000 83 Linux

    Partition 1 does not end on cylinder boundary.

    /dev/sda2 64 6528 51915776 8e Linux LVM

    /dev/sda3 6528 39162 262139965 8e Linux LVM

    Disk /dev/mapper/VolGroup-lv_root: 47.8 GB, 47789899776 bytes

    255 heads, 63 sectors/track, 5810 cylinders

    Units = cylinders of 16065 * 512 = 8225280 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes

    Disk identifier: 0x00000000

    Disk /dev/mapper/VolGroup-lv_swap: 5368 MB, 5368709120 bytes

    255 heads, 63 sectors/track, 652 cylinders

    Units = cylinders of 16065 * 512 = 8225280 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes

    Disk identifier: 0x00000000

    [root@localhost ~]# reboot

    Broadcast message from root@localhost.localdomain

    (/dev/pts/0) at 16:22 ...

    The system is going down for reboot NOW! 
    			 

    [root@localhost ~]#

    login as: root

    root@172.18.42.209's password:

    Last login: Fri Jun 29 16:19:13 2018 from 172.18.169.4

    [root@localhost ~]# partprobe

    Warning: the kernel failed to re-read the partition table on /dev/sda (Device or resource busy). As a result, it may not reflect all of your changes until after reboot. 
    			 

    [root@localhost ~]# partprobe /dev/sda3

    [root@localhost ~]# pvcreate /dev/sda3

    Physical volume "/dev/sda3" successfully created 
    			 

    [root@localhost ~]# df -h

    Filesystem Size Used Avail Use% Mounted on

    /dev/mapper/VolGroup-lv_root 44G 7.5G 35G 19% /

    tmpfs 7.8G 0 7.8G 0% /dev/shm

    /dev/sda1 485M 32M 428M 7% /boot

    [root@localhost ~]# vgextend VolGroup /dev/sda3

    Volume group "VolGroup" successfully extended 
    			 

    [root@localhost ~]# vgdisplay

     --- Volume group —

    VG Name VolGroup

    System ID

    Format lvm2

    Metadata Areas 2

    Metadata Sequence No 4

    VG Access read/write

    VG Status resizable

    MAX LV 0

    Cur LV 2

    Open LV 2

    Max PV 0

    Cur PV 2

    Act PV 2

    VG Size 299.50 GiB

    PE Size 4.00 MiB

    Total PE 76672

    Alloc PE / Size 12674 / 49.51 GiB

    Free PE / Size 63998 / 249.99 GiB

    VG UUID 5YlcZA-1N5n-M1kd-cK2c-8UNP-Losa-DPKyst

    [root@localhost ~]# lvresize -L +249.99G /dev/VolGroup/lv_root

    Rounding size to boundary between physical extents: 249.99 GiB

    Extending logical volume lv_root to 294.50 GiB

    Logical volume lv_root successfully resized

    [root@localhost ~]# resize2fs /dev/VolGroup/lv_root

    resize2fs 1.41.12 (17-May-2010)

    Filesystem at /dev/VolGroup/lv_root is mounted on /; on-line resizing required

    old desc_blocks = 3, new_desc_blocks = 19

    Performing an on-line resize of /dev/VolGroup/lv_root to 77201408 (4k) blocks.

    The filesystem on /dev/VolGroup/lv_root is now 77201408 blocks long.

    [root@localhost ~]# df -h

    Filesystem Size Used Avail Use% Mounted on

    /dev/mapper/VolGroup-lv_root 290G 7.6G 268G 3% /

    tmpfs 7.8G 0 7.8G 0% /dev/shm

    /dev/sda1 485M 32M 428M 7% /boot

  9. Restart Unleashed Multi-Site Manager. Issue the commands as shown in the following example.

    [root@localhost ~]# cd /home/UMM/

    [root@localhost UMM]# ./restart.sh

    Restarting UMM... 
    			 

    After a few minutes, you will be able to login to the Unleashed Multi-Site Manager interface.