F5 Logo MyF5
Search
  1. MyF5 Home
  2. BIG-IQ: Sizing Guidelines
  3. Resizing Disk Space on BIG-IQ Virtual Edition
Manual Chapter : Resizing Disk Space on BIG-IQ Virtual Edition

Applies To:

Show Versions Show Versions

BIG-IQ Centralized Management

  • 8.3.0, 8.2.0, 8.1.0
Manual Chapter

Resizing Disk Space on BIG-IQ Virtual Edition

BIG-IQ Virtual Edition Disk Space Overview

BIG-IQ Virtual Edition (VE) uses
Logical Volume Management
 (LVM) to allow you to use utilities to resize file systems. Additional disk space is useful when you need more storage on your BIG-IQ system for things such as logging or database files.
Here is an example of an initial installation of BIG-IQ 5.2 VE with a single installation slot created on volume HD1.1 

  [root@bigiq-console-test-large:Active:Standalone] ~ # tmsh show sys software 
  
  ----------------------------------------------------
  Sys::Software Status
  Volume  Product  Version     Build  Active    Status
  ----------------------------------------------------
  HD1.1    BIG-IQ    5.2.0  0.0.5741     yes  complete
The size of each file system is determined by a configuration file within the BIG-IQ installation image. (For details, refer to
Default Filesystem Sizes
 on
support.f5.com
.)
You can use the command
lvs
 to see the file structure on your BIG-IQ VE. The response shows all of the default logical volumes created, along with their size, in kilobytes.
Here is an example of an a typical BIG-IQ 5.2 VE file system. 

  [root@bigiq-console-test-large:Active:Standalone] ~ # lvs --unit=k
  LV            VG        Attr      LSize        Pool Origin Data%  Move Log Cpy%Sync Convert
  dat.log.1     vg-db-sda -wi-ao---  7168000.00k
  dat.maint.1   vg-db-sda -wi-a----   307200.00k
  dat.share.1   vg-db-sda -wi-ao--- 10240000.00k
  dat.swapvol.1 vg-db-sda -wi-ao---  1048576.00k
  set.1._config vg-db-sda -wi-ao---  3321856.00k
  set.1._usr    vg-db-sda -wi-ao---  3452928.00k
  set.1._var    vg-db-sda -wi-ao--- 10485760.00k
  set.1.root    vg-db-sda -wi-ao---   450560.00k
When you upgrade to version 5.3 or 5.4, BIG-IQ, one of the installation steps creates a new slot using the
create-volume
 parameter. Another installation step reveals the resulting file structure.
Here is an example from a typical BIG-IQ 5.2 to 5.3 upgrade: 

  [root@bigiq-console-test-large:Active:Standalone] ~ # tmsh install sys software image BIG-IQ-5.3.0.0.0.1119.iso create-volume volume HD1.2
[root@bigiq-console-test-large:Active:Standalone] ~ # tmsh show sys software
 
-----------------------------------------------------------------
Sys::Software Status
Volume  Product  Version     Build  Active                 Status
-----------------------------------------------------------------
HD1.1    BIG-IQ    5.2.0  0.0.5741     yes               complete
HD1.2    BIG-IQ    5.3.0  0.0.1119      no  installing 10.000 pct
The following example illustrates what the logical volumes look like after you install the new BIG-IQ software.

 [root@bigiq-console-test-large:Active:Standalone] ~ # lvs --unit=k
  LV            VG        Attr      LSize        Pool Origin Data%  Move Log Cpy%Sync Convert
  dat.log.1     vg-db-sda -wi-ao---  7168000.00k
  dat.maint.1   vg-db-sda -wi-a----   307200.00k
  dat.share.1   vg-db-sda -wi-ao--- 10240000.00k
  dat.swapvol.1 vg-db-sda -wi-ao---  1048576.00k
  set.1._config vg-db-sda -wi-ao---  3321856.00k
  set.1._usr    vg-db-sda -wi-ao---  3452928.00k
  set.1._var    vg-db-sda -wi-ao--- 10485760.00k
  set.1.root    vg-db-sda -wi-ao---   450560.00k
  set.2._config vg-db-sda -wi-a----  3321856.00k
  set.2._usr    vg-db-sda -wi-a----  3452928.00k
  set.2._var    vg-db-sda -wi-a---- 10485760.00k
  set.2.root    vg-db-sda -wi-a----   450560.00k
Each installation volume has their own
root
,
/usr
,
/config
, and
/var
 filesystems. The filesystems are mounted on logical volumes named using the following naming convention:
vg--db--sda-set.<installation slot>.<filesystem alias>
.
This table illustrates the mapping structure.
Installation Slot
Logical Volume
Mount Point
Notes
Shared
dat.log.1
/var/log
Shared across all installation slots
Shared
dat.share.1
/shared
Shared across all installation slots
HD1.1
set.1._config
/config
Slot 1 only
HD1.1
set.1._usr
/usr
Slot 1 only
HD1.1
set.1._var
/var
Slot 1 only
HD1.1
set.1.root
/
Slot 1 only
HD1.2
set.2._config
/config
Slot 2 only
HD1.2
set.2._usr
/usr
Slot 2 only
HD1.2
set.2._var
/var
Slot 2 only
HD1.2
set.2.root
/
Slot 2 only

Default filesystem sizes

The BIG-IQ installation image contains the information used to configure logical volumes with default sizes. These default sizes are referred to as
plans
. If you install a new BIG-IQ version and the existing logical volumes in the target installation slot are not at least as large as the default size, then the installation process deletes and recreates the entire slot with the default logical volume sizes spelled out in the plan for the installation image. If you want to see the sizes defined in the plan for your BIG-IQ system, you can use a script named
imageplan
.
Here is an example of the plans defined for a BIG-IQ 5.1 installation: 

  [root@bigiq-console-test-large:Active:Standalone] ~ # imageplan /shared/images/BIG-IQ-5.1.0.0.0.631.iso
product BIG-IQ version 5.1.0 build 0.0.631 (BIGIQ510) selected
Standard plan
  Mount point: /, Size: 300000k
  Mount point: /usr, Size: 2350000k
  Mount point: /config, Size: 1048576k
  Mount point: /var, Size: 10485760k
Tiny plan
  Mount point: /, Size: 300000k
  Mount point: /usr, Size: 2350000k
  Mount point: /config, Size: 1048576k
  Mount point: /var, Size: 10485760k
Here is an example of the plans defined for a BIG-IQ 5.2 installation: 

  [root@bigiq-console-test-large:Active:Standalone] ~ # imageplan /shared/images/BIG-IQ-5.2.0.0.0.5741.iso
product BIG-IQ version 5.2.0 build 0.0.5741 (BIGIQ520) selected
Standard plan
  Mount point: /, Size: 450000k
  Mount point: /usr, Size: 3450000k
  Mount point: /config, Size: 3320000k
  Mount point: /var, Size: 10485760k
Tiny plan
  Mount point: /, Size: 450000k
  Mount point: /usr, Size: 3450000k
  Mount point: /config, Size: 500000k
  Mount point: /var, Size: 10485760k
As illustrated in these examples, for BIG-IQ version 5.1 and 5.2, the Standard and Tiny plans use the same sizes for the
/
,
/usr
, and
/var
 mount points. The size for the
/config
 mount point often changes for each plan.
When you install BIG-IQ software, the installation process reads the plan for the version you are installing and then uses either the Standard or the Tiny plan depending upon the total disk size available in the target installation slot.

File system details

This table describes the contents of a folder structure on a typical BIG-IQ VE.
File System
Contains
Notes
/shared
Shared across all installation volumes:
  • ucs backups
    /shared/ucs_backups
  • BIG-IQ and BIG-IP installation ISO images
    /shared/images
  • ssh keys,
    known_hosts
     files, etc.
    /shared/ssh
  • core files
    /shared/core
Consider resizing this disk if there are many UCS backups (for example, if you have lots of BIG-IP devices to manage) or software installation images, or if the size of the BIG-IQ UCS file itself, which contains data from
/var/config
could be too large for a successful upgrade.
/var/log
Processes logging data shared across all installation volumes:
  • restjavad logs
    /var/log/restjavad*
  • database logs
    /var/log/tokumx.log.*
  • configuration search index logs
    /var/log/searchd/eslognode*
  • data collection device logs
    /var/log/elasticsearch/eslognode*
Consider resizing this disk if the default log rotation policies do not handle actual logging volume.
/ (root)
Linux operating system components and configuration
/usr
BIG-IQ installation binary and configuration components
/var
BIG-IQ data:
  • restjavad configuration data
    /var/config/rest/toku/data
  • restjavad
    configuration search indexes
    /var/config/rest/searchd/data
  • data collection device indexes
    /var/config/rest/elasticsearch/data
Consider resizing this disk if the database or index growth will exceed current disk capacity.

What factors should I consider before resizing my disks for an upgrade?

The commands for extending the file system on your BIG-IQ VE are very straightforward, but there are a things you should consider before proceeding.

Questions to ask before you resize

  • Do you have enough disk space on the BIG-IQ VE to install the BIG-IQ software?
  • How big are the volumes needed by the software you want to install?
  • How big are the volumes on your current BIG-IQ installation?
  • Do you have an open slot to install the software on?

Check the disk space on the BIG-IQ VE

Before you create new slots and size them appropriately, you need to check that there is sufficient physical disk space on the VE. You can use the
pvs
 command to check. For example:

[root@bigiq-console-test-large:Active:Standalone] ~ # 
pvs

  PV         VG        Fmt  Attr PSize   PFree
  /dev/sda3  vg-db-sda lvm2 a--  498.50g 446.82g
This device has 446 Gigs of free disk space. That would be more than sufficient for a standard 5.4 install (30G +5G + 5G + 10G = 50G)
Once you know how much room you need and if there is room on the VE you are installing on, you can start extending the disk. Remember that the volume sizes on the target slot must be at least as big as the volumes on your current slot. So if you have extended the volume sizes on your current installation, you will need larger volumes than the minimum sizes specified in the image plan for the software image you are installing. You need to use the larger of the two values from the checks you just completed. For example, if the
imageplan
 script shows a
/var
 size of 10G is needed for the software you want to install, but the
show sys software
 check shows a
/var
 size of 30G for the version you currently have installed, then you need the
/var
 volume to be sized at 30G, not 10G.

Check the volume sizes required by the software you want to install

F5 has created a script that reads the size requirements from the software image you plan to install and then creates them for you on a new installation slot. To use this script:
  1. Copy the software image to the /shared/images folder on the BIG-IQ system you plan to upgrade: 
    
 [root@bigiq-test:Active:Standalone] ~ # 
    cp  <big-iq-software-image>.iso /shared/images/<big-iq-software-image>.iso
  2. Run the
    imageplan
     script on the software image to determine the filesystem sizes required: 
    
 [root@bigiq-test:Active:Standalone] ~ # 
    ./imageplan /shared/images/<big-iq-software-image>.iso
    
product BIG-IQ version 5.3.0 build 0.0.1119 (BIGIQ530) selected
Standard plan
  Mount point: /, Size: 450000k
  Mount point: /usr, Size: 3450000k
  Mount point: /config, Size: 3320000k
  Mount point: /var, Size: 10485760k
Tiny plan
  Mount point: /, Size: 450000k
  Mount point: /usr, Size: 3450000k
  Mount point: /config, Size: 500000k
  Mount point: /var, Size: 10485760k
Now you know the size requirements for the image you plan to install.

Check the volume sizes on your current BIG-IQ installation

You need to know the volume sizes for your current installation, because if any of the volumes have been extended, you must likewise extend the volumes on the installation slot before you upgrade. Otherwise, the install process can result in loss of data. To check the volume sizes of the existing installation, you can use the tmsh command
show sys software
 . For example:

    [root@bigiq-test:Active:Standalone] config # 
tmsh show sys software

 
----------------------------------------------------
Sys::Software Status
Volume  Product  Version     Build  Active    Status
----------------------------------------------------
HD1.1    BIG-IQ    5.2.0  0.0.5567     yes  complete
 
[root@bigiq-test:Active:Standalone] config # lvs --unit=k
  LV            VG        Attr      LSize        Pool Origin Data%  Move Log Cpy%Sync Convert
  dat.log.1     vg-db-sda -wi-ao---  7168000.00k
  dat.maint.1   vg-db-sda -wi-a----   307200.00k
  dat.share.1   vg-db-sda -wi-ao--- 10240000.00k
  dat.swapvol.1 vg-db-sda -wi-ao---  1048576.00k
  set.1._config vg-db-sda -wi-ao---   503808.00k
  set.1._usr    vg-db-sda -wi-ao---  3452928.00k
  set.1._var    vg-db-sda -wi-ao--- 31457280.00k
  set.1.root    vg-db-sda -wi-ao---   450560.00k
The system response shows you the volume sizes of your current installation. The key volumes with their sizes are listed below:
  • /config (.5G)
  • /usr (3.5G)
  • /var (30G)
  • /root (.5G)
The slot you upgrade to must have volumes that are at least as big as those on the slot your software is currently installed on. This is especially significant if you decided to extend one of the volumes on your current installation. So if your /var is extended to 30G, you must have at least that much space on the new slot before you install software.

Check to see if you have an open slot to install the software on

Before you can install new software, you need an open slot. You can use the lvs command to determine how many slots there are on your BIG-IQ VE. For example:

[root@bigiq-console01:Active:Standalone] config # 
lvs --unit=k

  LV            VG        Attr      LSize        Pool Origin Data%  Move Log Cpy%Sync Convert
  dat.log.1     vg-db-sda -wi-ao---  8388608.00k
  dat.maint.1   vg-db-sda -wi-a----   307200.00k
  dat.share.1   vg-db-sda -wi-ao--- 33554432.00k
  dat.swapvol.1 vg-db-sda -wi-ao---  1048576.00k
  set.1._config vg-db-sda -wi-a----   503808.00k
  set.1._usr    vg-db-sda -wi-a----  3452928.00k
  set.1._var    vg-db-sda -wi-a---- 10485760.00k
  set.1.root    vg-db-sda -wi-a----   450560.00k
  set.2._config vg-db-sda -wi-ao---  3481600.00k
  set.2._usr    vg-db-sda -wi-ao---  3584000.00k
  set.2._var    vg-db-sda -wi-ao--- 16003072.00k
  set.2.root    vg-db-sda -wi-ao---   512000.00k
  set.3._config vg-db-sda -wi-a----  3321856.00k
  set.3._usr    vg-db-sda -wi-a----  3452928.00k
  set.3._var    vg-db-sda -wi-a---- 10485760.00k
  set.3.root    vg-db-sda -wi-a----   450560.00k
Each instance of set.n represents a slot on the VE. So in this example the VE has 3 installation slots (set.1, set.2, and set.3).

Resizing disk volumes for a BIG-IQ upgrade (an example work flow)

The work flow for extending your disk volumes so that you can successfully upgrade to a new version of BIG-IQ and preserve your current data is listed below:
  • If you need more physical disk space, attend to that first.
  • If you have the disk space and an open slot, then F5 has a script that you can use to create the new volumes required for the image you plan to install.
    addvol
     reads the image plan for the software you plan to install and creates the volumes required.
  • If you have extended the disk space on your current installation, you need to increase the volume size as needed.
  • If you need an extra slot, you can add it as part of the installation command. The
    create_volume
     parameter adds a new slot to your VE and (if you've set up the volume sizes correctly) when the software upgrades, all of your data fits without any disk resizing. Resizing disks in the middle of an upgrade can cause you to lose data.
The following example tasks step you through the work flow for extending your disk size as part of an upgrade. In this scenario, you check the disk space first, then you create the volumes for the software you plan to install, then you extend a volume to account for an extension you performed on your current installation, and finally, you install the software, adding a new installation slot as part of the process.

Download disk size tools

F5 has created several scripts that are useful if you need to resize your disk volumes as part of the upgrade process.
  • On a BIG-IQ system or DCD with version 6.0 or later installed, these scripts are available in the
    /usr/bin
     folder. Because this folder is already in your path definition, you can use these scripts directly.
  • To use these scripts with BIG-IQ systems or DCDs running version 8.x, you must first download them. Complete the following steps to download these scripts.
  1. Log in to
    downloads.f5.com
    .
  2. Navigate to BIG-IQ Centralized Management, look for the BIQ-IQ release you are working with, and click
    I Accept
     to accept the EULA.
  3. Click
    F5_Networks_Disk_Size_Tools.tar
    .
    After a brief pause, the Download Locations screen opens.
  4. Click a download location to start the download.
  5. When the download completes, extract the contents of the archive.
    Three files will extract:
    • addvol
    • imageplan
    • resizevol
Before you can run these scripts, you need to copy them to the
/usr/bin
 folder of the device you are resizing.

Check the amount of free disk space on your BIG-IQ VE

  • Before you can use this work flow to check the amount of free disk space on your BIG-IQ VE, you must download the
    imageplan
     script from
    F5.downloads.com
    . For details on downloading this script, refer to
    Downloading disk size tools
     on
    support.f5.com
    .
Before you create new slots and size them appropriately, you need to check that there is sufficient physical disk space on the BIG-IQ VE.
  1. Use SSH to log in to your DCD as root.
  2. Use the
    pvs
     command to check how much disk space is available for new slots and volumes.
     
    
[root@bigiq-console-test-large:Active:Standalone] ~ # 
    pvs
    
  PV         VG        Fmt  Attr PSize   PFree
  /dev/sda3  vg-db-sda lvm2 a--  498.50g 446.82g
    The command response tells you how much free disk space is available.
    This device has 446 Gigs of free disk space. That would be more than sufficient for a standard 8.0 install (30G +5G + 5G + 10G = 50G)
If the amount of disk space available is less than the amount you need before you can install your software, you must increase the free space before you can proceed. Refer to the hypervisor vendor documentation for the work flow to increase the amount of available disk space on your VE.

Create correctly sized volumes

Before you create correctly sized volumes you need to:
  • Download the
    resizevol
     script from
    F5.downloads.com
    . For details on downloading this script, refer to
    Downloading disk size tools
     on
    support.f5.com
    .
  • Know the volume names that you want to extend, and the size that you want to extend them to.
If you need to increase the volume size of a disk volume, you can use the
resizevol
 script.
  1. Use SSH to log in to your BIG-IQ as
    root
    .
  2. Use the
    resizevol
     script to increase size of the volume on the new installation slot to the required size.
    The volume sizes required depend on a number of factors. See
    What volume sizes should I use?
     on
    support.f5.com
     for details.
    Here is an example of the
    resizevol
     script being used to resize the
    /var
     volume to 30 GB.
    
# 
    ./resizevol /var 30000000
    
Requested size 30000000k is less than current size 30003200.00k on /dev/vg-db-sda/set.1._var, skipping
Resizing logical volumes. OK (y/n)? y
Requested size 30000000k is less than current size 30003200.00k, skipping
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
set.2./var: 11/655360 files (0.0% non-contiguous), 79696/2621440 blocks
  Rounding size to boundary between physical extents: 28.61 GiB
  Extending logical volume set.2._var to 28.61 GiB
  Logical volume set.2._var successfully resized
resize2fs 1.41.12 (17-May-2010)
Resizing the filesystem on /dev/vg-db-sda/set.2._var to 7500800 (4k) blocks.
The filesystem on /dev/vg-db-sda/set.2._var is now 7500800 blocks long.
# lvs --unit=k
  LV            VG        Attr      LSize        Pool Origin Data%  Move Log Cpy%Sync Convert
  dat.log.1     vg-db-sda -wi-ao---  7168000.00k
  dat.maint.1   vg-db-sda -wi-a----   307200.00k
  dat.share.1   vg-db-sda -wi-ao--- 10240000.00k
  dat.swapvol.1 vg-db-sda -wi-ao---  1048576.00k
  set.1._config vg-db-sda -wi-ao---   503808.00k
  set.1._usr    vg-db-sda -wi-ao---  3452928.00k
  set.1._var    vg-db-sda -wi-ao--- 30003200.00k
  set.1.root    vg-db-sda -wi-ao---   450560.00k
  set.2._config vg-db-sda -wi-a----  3321856.00k
  set.2._usr    vg-db-sda -wi-a----  3452928.00k
  set.2._var    vg-db-sda -wi-a---- 30003200.00k
  set.2.root    vg-db-sda -wi-a----   450560.00k
    The script extends the size of the volume you identify (
    /var
     in this example) to the size you enter (30GB in this example).

Check the volume sizes on your current BIG-IQ installation

The slot you upgrade to must have volumes that are at least as big as those on the slot that your software is currently installed. This is especially significant if you decided to extend one of the volumes on your current installation. So if your
/var
 volume is extended to 30G, you must have at least that much space on the new slot before you install software. Otherwise, the install process can result in loss of data.
  1. Use SSH to log in (as
    root
    ) on the BIG-IQ you plan to upgrade.
  2. Use the
    tmsh
     command
    show sys software
     to check the volume sizes of the existing installation.
    
    [root@bigiq-test:Active:Standalone] config # 
    tmsh show sys software
    
 
----------------------------------------------------
Sys::Software Status
Volume  Product  Version     Build  Active    Status
----------------------------------------------------
HD1.1    BIG-IQ    7.1.0  0.0.1511     yes  complete
 
[root@bigiq-test:Active:Standalone] config # lvs --unit=k
  LV            VG        Attr      LSize        Pool Origin Data%  Move Log Cpy%Sync Convert
  dat.log.1     vg-db-sda -wi-ao---  7168000.00k
  dat.maint.1   vg-db-sda -wi-a----   307200.00k
  dat.share.1   vg-db-sda -wi-ao--- 10240000.00k
  dat.swapvol.1 vg-db-sda -wi-ao---  1048576.00k
  set.1._config vg-db-sda -wi-ao---   503808.00k
  set.1._usr    vg-db-sda -wi-ao---  3452928.00k
  set.1._var    vg-db-sda -wi-ao--- 31457280.00k
  set.1.root    vg-db-sda -wi-ao---   450560.00k
    The system response shows you the volume sizes of your current installation. The key volumes with their sizes are listed below:
    • /config
       (.5G)
    • /usr
      (3.5G)
    • /var
       (30G)
    • /root
       (.5G)

Increase the size of a disk volume

Before you can increase the size of the disk volumes on your BIG-IQ VE:
  • You need the
    resizevol
     script on the BIG-IQ VE on which you want to increase the size of the disk volumes.
    • On a BIG-IQ system or DCD with version 7.0 or later installed, these scripts are available in the
      /usr/bin
       folder. Because this folder is already in your path definition, you can use these scripts directly.
    • To use these scripts with BIG-IQ systems or DCDs running version 8.x, you must first download them. For details on downloading this script, refer to
      Downloading disk size tools
       on
      support.f5.com
      .
  • You need to know the volume names that you want to extend and the size that you want to extend them to.
If you need to increase the volume size of a disk volume on your installation slot so that you can install without losing any data, you can use the
resizevol
 script.
  1. Use SSH to log in (as
    root
    ) to the device you plan to upgrade.
  2. Shut down BIG-IQ by typing:
    shutdown -h now
  3. Provision the disk space you need for the BIG-IQ VE system.
  4. Start up the BIG-IQ VE guest instance.
    For information about disk starting a guest instance, refer to the documentation from your hypervisor or cloud vendor.
  5. Use the
    resizevol
     script to increase the size of the volumes for the new installation slot to the required size.
    The volume sizes required depend on these two factors:
    • The volume sizes required by the software you want to install. For details, see
      Check the volume sizes required by the software you want to install
       on
      support.f5.com
      .
    • The volume sizes your current installation uses. For details, see
      Check the volume sizes on your current BIG-IQ installation
       on
      support.f5.com
      .
    Here is an example of the
    resizevol
     script being used to resize the
    /var
     volume to 30 Gb.
    
# 
    ./resizevol /var 30000000
    
Requested size 30000000k is less than current size 30003200.00k on /dev/vg-db-sda/set.1._var, skipping
Resizing logical volumes. OK (y/n)? y
Requested size 30000000k is less than current size 30003200.00k, skipping
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
set.2./var: 11/655360 files (0.0% non-contiguous), 79696/2621440 blocks
  Rounding size to boundary between physical extents: 28.61 GiB
  Extending logical volume set.2._var to 28.61 GiB
  Logical volume set.2._var successfully resized
resize2fs 1.41.12 (17-May-2010)
Resizing the filesystem on /dev/vg-db-sda/set.2._var to 7500800 (4k) blocks.
The filesystem on /dev/vg-db-sda/set.2._var is now 7500800 blocks long.
# lvs --unit=k
  LV            VG        Attr      LSize        Pool Origin Data%  Move Log Cpy%Sync Convert
  dat.log.1     vg-db-sda -wi-ao---  7168000.00k
  dat.maint.1   vg-db-sda -wi-a----   307200.00k
  dat.share.1   vg-db-sda -wi-ao--- 10240000.00k
  dat.swapvol.1 vg-db-sda -wi-ao---  1048576.00k
  set.1._config vg-db-sda -wi-ao---   503808.00k
  set.1._usr    vg-db-sda -wi-ao---  3452928.00k
  set.1._var    vg-db-sda -wi-ao--- 30003200.00k
  set.1.root    vg-db-sda -wi-ao---   450560.00k
  set.2._config vg-db-sda -wi-a----  3321856.00k
  set.2._usr    vg-db-sda -wi-a----  3452928.00k
  set.2._var    vg-db-sda -wi-a---- 30003200.00k
  set.2.root    vg-db-sda -wi-a----   450560.00k
    The script extends the size of the volume you specify (
    /var
    in this example) to be the size you want (30Gb in this example).
  6. Save the configuration changes by typing:
    tmsh save /sys config
  7. Restart BIG-IQ by typing:
    reboot
  8. When the BIG-IQ restarts, use SSH to log in (as
    root
    ). Verify the directory was successfully extended to the size you specified by typing the tmsh command:
    tmsh show /sys disk directory
    For more information about extending the disk space on a BIG-IQ, refer to K30902515.
Now that the volumes are correctly sized, you can proceed with the installation.

Use TMSH to install BIG-IQ to a new slot

Before you can install a BIG-IQ device to a new slot, you must have:
  • Downloaded the software image from
    F5.downloads.com
    .
  • Correctly sized the volumes on the slot you plan to install the new version on.
This task explains how to use a
tmsh
 command to install BIG-IQ software to a new volume as part of the upgrade process command. The process performs these steps:
  • Creates a UCS backup from the current system and saves it in the
    /shared
     folder.
  • Installs a new BIG-IQ image on a new slot.
  • When the new image is installed on the new slot, it copies that data was saved in
    /shared
     into the new database running on the new slot.
  1. Use SSH to log in to your BIG-IQ as root.
  2. Use the
    tmsh
    install
     command to upgrade your software.
    The following example uses the create-volume parameter so the process creates a new slot and then begins installing the software on it.
    
# tmsh install sys software image  BIG-IQ-7.1.0-0.0.1511.iso create-volume volume HD1.2
    The process upgrades your BIG-IQ system and restores the data from the current version.
  3. After the installation is complete, you can use the
    tmsh
    show sys software
     command to check to see that the upgrade was successful and that the
    /var
     file system is the correct size (30M).
     
    
# tmsh show sys software
 
----------------------------------------------------
Sys::Software Status
Volume  Product  Version     Build  Active    Status
----------------------------------------------------
HD1.1    BIG-IQ    6.1.0  0.0.1224     yes  complete
HD1.2    BIG-IQ    7.1.0  0.0.1511      no  complete
  
# lvs --unit=k
  LV            VG        Attr      LSize        Pool Origin Data%  Move Log Cpy%Sync Convert
  dat.log.1     vg-db-sda -wi-ao---  7168000.00k
  dat.maint.1   vg-db-sda -wi-a----   307200.00k
  dat.share.1   vg-db-sda -wi-ao--- 10240000.00k
  dat.swapvol.1 vg-db-sda -wi-ao---  1048576.00k
  set.1._config vg-db-sda -wi-ao---   503808.00k
  set.1._usr    vg-db-sda -wi-ao---  3452928.00k
  set.1._var    vg-db-sda -wi-ao--- 30003200.00k
  set.1.root    vg-db-sda -wi-ao---   450560.00k
  set.2._config vg-db-sda -wi-a----  3321856.00k
  set.2._usr    vg-db-sda -wi-a----  3452928.00k
  set.2._var    vg-db-sda -wi-a---- 30003200.00k
  set.2.root    vg-db-sda -wi-a----   450560.00k
Contact Support Contact Support

Have a Question?

Support and Sales >

About F5

Education

F5 Sites

Support Tasks




©2023 F5, Inc. All rights reserved.


Trademarks Policies Privacy California Privacy Do Not Sell My Personal Information