F5 BIG-IQ Centralized Management Disk Space Management Version 5.4
Table of Contents Table of Contents BIG-IQ Virtual Edition Disk Space Overview...5 File System Details... 7 Default File System Sizes... 9 Resizing VE Disk Volume Workflows... 11 What factors should I consider before installing BIG-IQ software?... 11 Determining the correct volume sizes for your new BIG-IQ installation... 12 Download disk size tools... 12 Create correctly sized volumes... 12 What disk size tasks should I perform before an upgrade?... 13 Download disk size tools... 14 Check the amount of free disk space on your BIG-IQ VE... 14 How do I get BIG-IQ to email me if disk space is low?...15 Check the volume sizes required by the software you want to install...16 Check the volume sizes on your current BIG-IQ installation... 17 Create correctly sized volumes on the new installation slot... 18 Increase the size of a disk volume... 18 Check to see if you have an open slot to install the software on...20 Install BIG-IQ to a new slot...20 Legal Notices... 23 Legal notices...23 3
Table of Contents 4
BIG-IQ Virtual Edition Disk Space Overview F5 BIG-IQ Centralized Management 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. If your BIG-IQ VE is part of a data collection device (DCD) cluster, you can view statistics about the resources each node uses by checking the BIG-IQ data collection cluster health. If your deployment does not include a DCD cluster, you can use tmsh commands to check the resources used by the BIG-IQ VE. For details about checking available disk space on nodes in a DCD cluster, refer to Check disk space usage for DCD nodes on support.f5.com. Here is an example that uses a tmsh command to check an initial installation of BIG-IQ version 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 File System 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 version 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 Each installation volume has its own root, /usr, /config, and /var file systems. The file systems are mounted on logical volumes named using the following naming convention: vg--db--sdaset.<installation slot>.<file system 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
BIG-IQ Virtual Edition Disk Space Overview Installation Slot Logical Volume Mount Point Notes 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 6
File System Details This table describes the contents of a folder structure on a typical BIG-IQ VE. File System Contains Notes /shared /var/log Shared across all installation volumes: UCS backups /shared/ucs_backups BIG-IQ and BIG-IP system installation ISO images /shared/images SSH keys, known_hosts files, etc. / shared/ssh core files /shared/core 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 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. Because each use case is unique, it is difficult to provide a recommended metric for this folder. However, if the /shared folder is more than 70% full, consider increasing the disk size by 50%. You can use the free disk space command (df -h) to determine how much space is available. Consider resizing this disk if the default log rotation policies do not handle actual logging volume. / (root) Linux operating system components and configuration /usr /var BIG-IQ installation binary and configuration components 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. Because each use case is unique, it is difficult to provide a recommended metric for this folder. However, if the /var folder is more than 70% full, consider increasing the disk size by 50%. You can use the free disk space command (df -h) to determine how much space is available. DCDs use the /var directory differently than a BIG-IQ does. Refer to the F5 BIG-IQ Centralized Management DCD Sizing Guide for details.
File System Details 8
Default File System 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 specified 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 version 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 this example for BIG-IQ version 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.
Default File System Sizes 10
Resizing VE Disk Volume Workflows The workflow for extending your disk volumes depends on whether you are performing a new installation or upgrading to a new version of BIG-IQ. If you are installing a new BIG-IQ system: Determine how much disk space you have. If you need more physical disk space, attend to that first. Determine how much space you need on each of the volumes your BIG-IQ system uses. Create the correct volume sizes. If you want to facilitate upgrading this BIG-IQ system in the future, create an installation slot. If you are upgrading a BIG-IQ system: Determine how much disk space you have. If you need more physical disk space, attend to that first. Determine how much disk space is required for the software you plan to install. F5 has a script that you can use to determine the correct volume sizes for the software you plan to install. imageplan reads the image plan for the software you plan to install and reports it on screen. If you have the disk space and an open slot, you can use an F5 script 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 can use an F5 script that increases volume size as needed. resizevol sets the volume size to the value you specify. 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 using addvol and resizevol) 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. There are two sets of example tasks that guide you through the workflow for extending your disk size. Choose the example workflow that corresponds to your situation. What factors should I consider before installing BIG-IQ software? Before you install a BIG-IQ system you should make sure of a couple things about the virtual disk on which your BIG-IQ system resides, so that all goes as planned when you install your software. Questions to ask before you install 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? Before you create new slots and size them appropriately, check whether there is sufficient physical disk space on the VE. For details on evaluating your free disk space, refer to What disk size tasks should I perform before an upgrade? on support.f5.com. The two base BIG-IQ VE sizes that you can install yield a physical disk space of either 95 or 500 GB. However, it you plan to use more than 95 GB of that disk space, you need to allocate that space to the volumes you plan to use.
Resizing VE Disk Volume Workflows Determining the correct volume sizes for your new BIG-IQ installation When you install BIG-IQ VE, you need to know how big the volumes should be to handle the amount of data you intend to store. The volume size requirements can vary significantly, depending on how you use the BIG-IQ system. If you are installing a BIG-IQ system, the volume sizes you need also depend on how you plan to manage your BIG-IP devices and how many you plan to manage. The /var volume is used to store BIG-IQ local databases. In a typical system managing 600 BIG-IP devices, you can expect about 20 GB total disk space used. This size can vary greatly depending on the services discovered and type of objects being managed. Snapshots are stored in this volume, so if you schedule a lot of snapshots, your requirements will increase. For our scale testing, we found that 50GB was sufficient. If you schedule a large number of snapshots, that need could increase to 100GB. The /shared volume is used to store the backups; both for the BIG-IP devices you manage and the BIG-IQ itself. Larger amounts of disk space can be needed here, depending on how many devices you manage, how often they are backed up, and how many of these backups you opt to retain. You can specify how many backups you want to keep for each managed device. The storage auto-purges older backups if that number is exceeded. This feature can help prevent you from accidentally exhausting the available disk space. For our scale testing, we found that 300GB was sufficient for managing 600 BIG-IP devices. 100GB was sufficient for managing 200 BIG-IP devices or less. To err on the side of caution, 300GB is a good guideline. If you are installing a DCD, the volume sizes you need depend on the number of BIG-IP devices you are collecting data for, as well as the number of DCDs in your cluster. Refer to the F5 BIG-IQ Centralized Management DCD Sizing Guide for additional detail. 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 5.4.0 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 versions prior to version 5.4.0, you must first download them. 1. Log in to downloads.f5.com. 2. Navigate to BIG-IQ Centralized Management, v5.4.0, and click I Accept to accept the EULA. 3. Click F5_Networks_Disk_Size_Tools.zip. After a brief pause, the Download Locations screen opens. 4. Click a download location to start the download. 5. When the download completes, unzip the file. Three files will extract to the folder you designate: addvol imageplan resizevol Before you can run these scripts, you need to copy them to the device you are resizing. 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. 12
F5 BIG-IQ Centralized Management Disk Space Management 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 DCD 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). What disk size tasks should I perform before an upgrade? Before you upgrade a BIG-IQ system you should make sure of a couple things about the virtual disk on which your BIG-IQ system resides, so that all goes as planned when you upgrade your software. Questions to ask before you upgrade Do you have enough disk space on the BIG-IQ VE to install the BIG-IQ software? Before you create new slots and size them appropriately, you need to check whether there is sufficient physical disk space on the VE. 13
Resizing VE Disk Volume Workflows 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? F5 has created a script that reads the size requirements from the software image you plan to install. You need to know the volume sizes for your current installation. 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. Before you can install new software, you need an open slot. 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 5.4.0 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 versions prior to version 5.4.0, you must first download them. 1. Log in to downloads.f5.com. 2. Navigate to BIG-IQ Centralized Management, v5.4.0, and click I Accept to accept the EULA. 3. Click F5_Networks_Disk_Size_Tools.zip. After a brief pause, the Download Locations screen opens. 4. Click a download location to start the download. 5. When the download completes, unzip the file. Three files will extract to the folder you designate: addvol imageplan resizevol Before you can run these scripts, you need to copy them to the device you are resizing. Check the amount of free disk space on your BIG-IQ VE You need to check that there is sufficient physical disk space on the BIG-IQ VE so that you can create new volumes and size them appropriately. 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 version 5.4 install (30G +5G + 5G + 10G = 50G). However, you also must consider how much space your current installation uses. If you have extended the size of the volumes for your current installation, you must consider that as well. 14
F5 BIG-IQ Centralized Management Disk Space Management If the amount of disk space available is less than the amount you need so that you can install your software, you must increase the free space before you can proceed. Refer to the hypervisor vendor documentation for the workflow to increase the amount of available disk space on your VE. How do I get BIG-IQ to email me if disk space is low? To get an email if the BIG-IQ VE runs low on disk space, you complete three tasks: Specify an SMTP server to send email alerts. Set up email addresses for low disk space alerts. Set up a low disk space alert. Specify an SMTP server to send email alerts You specify an SMTP server so F5 BIG-IQ Centralized Management can send email to alert specified people when a certain condition happens, such as when an SSL certificate is about to expire. 1. At the top of the screen, click System. 2. On the left, click SMTP Configuration. 3. On the SMTP Configuration screen, if there is no mail server set up, click the Add button. 4. In the Name field, type a name for this SMTP configuration. 5. In the SMTP Server Host and SMTP Server Port fields, type the SMTP server and TCP port. By default, SMTP uses TCP 25. 6. In the From Email Address field, type the email address from which to send the alert email. 7. From the Encryption list, select the type of encryption to use for the email. 8. To require a user name and password, from the Use Auth list, select Yes, and type the required user name and password. 9. To verify that you can reach the server you configured, click the Test Connection button. 10. Click the Save & Close button at the bottom of the screen. You can now specify email recipients and set up the alert conditions that prompt BIG-IQ to send an email when a certain event happens on a managed device. Set up email addresses for low disk space alerts Before you can set up the BIG-IQ to email alerts, you need to have set up an SMTP mail server. You can add a list of email recipients to which BIG-IQ sends notifications for low disk space alerts. 1. At the top of the screen, click System. 2. On the left, click THIS DEVICE > Email Notification Recipients. 3. Near the top of the screen, click the Create button. 4. In the Name and Email Address fields, type the name and email address of the person you want to receive the low disk space alert. 5. In the Description field, you can type an optional description to help identify this user. 6. Select the check box next System Alerts. 7. To add another email recipient, click +. 8. Click the Save & Close button at the bottom of the screen to save your changes. Set up a low disk space alert You can set up an alert that sends an email to notify you when disk space on the BIG-IQ VE is low. 1. At the top of the screen, click Monitoring. 15
Resizing VE Disk Volume Workflows 2. On the left, click ALERTS & NOTIFICATIONS. 3. At the top of the screen, click the Settings button. 4. If the device you are managing is a BIG-IQ, under Disk Usage Alert Conditions, select Enabled next to the BIG-IQ Used disk space is above threshold for a device alert, then specify the Threshold at which you want to be notified. 5. If the device you are managing is a BIG-IQ, under Disk Usage Alert Conditions, select Enabled next to the Used disk space is above threshold for a DCD alert, then specify the Threshold at which you want to be notified. 6. Click the Save & Close button at the bottom of the screen. Check the amount of free disk space on your BIG-IQ VE You need to check that there is sufficient physical disk space on the BIG-IQ VE so that you can create new volumes and size them appropriately. 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 version 5.4 install (30G +5G + 5G + 10G = 50G). However, you also must consider how much space your current installation uses. If you have extended the size of the volumes for your current installation, you must consider that as well. If the amount of disk space available is less than the amount you need so that you can install your software, you must increase the free space before you can proceed. Refer to the hypervisor vendor documentation for the workflow to increase the amount of available disk space on your VE. Check the volume sizes required by the software you want to install Before you check the required volume sizes using the imageplan script, you need to: Confirm that the imageplan script is on the device you plan to update. On a BIG-IQ system or DCD with version 5.4.0 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 versions prior to version 5.4.0, you must first download them. For details on downloading this script, refer to Downloading disk size tools on support.f5.com. Download the software that you plan to install. When you upgrade a BIG-IQ VE, you need to know the volume sizes required by the software you plan to install. F5 has created a script that reads the size requirements from the software image you plan to install. Use this script so you can be confident that your VE volume sizes are sufficient before you upgrade your BIG-IQ software. 1. Use SSH to log in to the device you are going to upgrade as root. 2. Copy the software image to the /shared/images folder on the BIG-IQ system you plan to upgrade. # cp <big-iq-software-image>.iso /shared/images/<big-iq-software-image>.iso 3. Run the imageplan script on the software image to determine the file system sizes required. 16
F5 BIG-IQ Centralized Management Disk Space Management #./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, but 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 on. 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. So the next thing you need to do is check the size of your existing installation. Check the volume sizes on your current BIG-IQ installation When you upgrade a BIG-IQ VE, you need to know the volume sizes for your current installation, because if any of the volumes have been extended, you must 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 BIG-IQ installation, you can use a tmsh command. 1. Use SSH to log in (as root) to the device 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 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 where your software is currently installed. This is especially significant if you decided to extend one of the volumes 17
Resizing VE Disk Volume Workflows on your current installation. So if your /var volume is extended to 30G, you must have at least that much space available on the new slot, before you install software. Create correctly sized volumes on the new installation slot Before you can use this workflow to create new installation volumes, you need the addvol script on the BIG-IQ device you want to create the volumes on. On a BIG-IQ system or DCD with version 5.4.0 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 versions prior to version 5.4.0, you must first download them. For details on downloading this script, refer to Downloading disk size tools on support.f5.com. If you are planning to upgrade a BIG-IQ VE, you can use the addvol script to create new volumes on the BIG-IQ VE that are sized correctly for the version you plan to install. 1. Download the image file that you plan to install from downloads.f5.com. 2. Use SSH to log in (as root) to the device you plan to upgrade, and copy the image file to the / shared/images folder. 3. Use the addvol script to create the file systems defined in the image plan for the software you plan to install. The script creates the correctly sized volume, but does not install any software. In this example, the image file for BIG-IQ version 5.3.0 is used. #./addvol HD1.2 /shared/images/big-iq-5.3.0.0.0.1119.iso create volume HD1.2 for image /shared/images/big-iq-5.3.0.0.0.1119.iso product BIG-IQ version 5.3.0 build 0.0.1119 (BIGIQ530) selected Creating new location sda, 2... info: zero sblock for member device; /dev/vg-db-sda/set.2.root info: zero sblock for member device; /dev/vg-db-sda/set.2._usr info: zero sblock for member device; /dev/vg-db-sda/set.2._config info: zero sblock for member device; /dev/vg-db-sda/set.2._var [root@bigiq-test: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--- 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---- 10485760.00k set.2.root vg-db-sda -wi-a---- 450560.00k The script reads the image plan and creates new volumes for /config, /usr, /var, and /root based on the requirements defined in the plan. 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. 18
F5 BIG-IQ Centralized Management Disk Space Management On a BIG-IQ system or DCD with version 5.4.0 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 versions prior to version 5.4.0, 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 to your DCD as root. 2. Use SSH to log in (as root) to the device you plan to upgrade. 3. 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). 19
Resizing VE Disk Volume Workflows Now that the volumes are correctly sized, you can proceed with the installation. Check to see if you have an open slot to install the software on In order to install new software, you need an open slot. You can use a bash command to determine whether your BIG-IQ VE has any open slots. 1. Use SSH to log in, as root, to the device you are upgrading. 2. Use the lvs command to determine how many slots there are on your BIG-IQ VE. # 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 three installation slots (set.1, set.2, and set.3). If the BIG-IQ VE has only one slot, then you need to add an new slot when you install the upgrade. 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. On a BIG-IQ system or DCD with version 5.4.0 installed, you can use the user interface to add a new volume as part of the upgrade process,with BIG-IQ systems or DCDs running versions prior to version 5.4.0, you can upgrade BIG-IQ using a tmsh 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. Note: The following example uses the create-volume parameter so the process creates a new slot and then begins installing the software on it. 20
F5 BIG-IQ Centralized Management Disk Space Management # tmsh install sys software image BIG-IQ-5.3.0.0.0.1119.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 5.2.0 0.0.5567 yes complete HD1.2 BIG-IQ 5.3.0 0.0.1119 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 21
Resizing VE Disk Volume Workflows 22
Legal Notices Legal notices Publication Date This document was published on February 9, 2018. Publication Number MAN-0689-00 Copyright Copyright 2018, F5 Networks, Inc. All rights reserved. F5 Networks, Inc. (F5) believes the information it furnishes to be accurate and reliable. However, F5 assumes no responsibility for the use of this information, nor any infringement of patents or other rights of third parties which may result from its use. No license is granted by implication or otherwise under any patent, copyright, or other intellectual property right of F5 except as specifically described by applicable user licenses. F5 reserves the right to change specifications at any time without notice. Trademarks For a current list of F5 trademarks and service marks, see http://www.f5.com/about/guidelines-policies/ trademarks. All other product and company names herein may be trademarks of their respective owners. Patents This product may be protected by one or more patents indicated at: https://f5.com/about-us/policies/ patents. Link Controller Availability This product is not currently available in the U.S. Export Regulation Notice This product may include cryptographic software. Under the Export Administration Act, the United States government may consider it a criminal offense to export this product from the United States. RF Interference Warning This is a Class A product. In a domestic environment this product may cause radio interference, in which case the user may be required to take adequate measures. FCC Compliance This equipment has been tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This unit generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a
Legal Notices residential area is likely to cause harmful interference, in which case the user, at his own expense, will be required to take whatever measures may be required to correct the interference. Any modifications to this device, unless expressly approved by the manufacturer, can void the user's authority to operate this equipment under part 15 of the FCC rules. Canadian Regulatory Compliance This Class A digital apparatus complies with Canadian ICES-003. Standards Compliance This product conforms to the IEC, European Union, ANSI/UL and Canadian CSA standards applicable to Information Technology products at the time of manufacture. 24
Index Index A alert conditions specifying 15 alerts configuring SMTP for 15 available disk space creating correct size 12 B BIG-IQ software about correct volume sizes for 12 about installing 11 C current installation checking volume size 17 D disk size tools downloading 12, 14 disk space about alerts for low space 15 about default file size for VE 9 about resizing for VE 5, 7 checking available 14, 16 creating correct size 12 details of folder structure contents 7 disk usage specifying alerts for 15 disk volume creating correct size 12 increasing size 18 increasing size of disk 18 disk volume workflows about resizing for VE 11 disk volumes downloading tools for resizing 12, 14 E email notification about setting up for low space 15 email recipients configuring for alerts 15 F free disk space checking available 14, 16 I installation installation (continued) checking current volume sizes 17 installation considerations for BIG-IQ software 11 installation volumes creating right-sized 18 L low disk space about creating alerts 15 configuring email alerts 15 N new installation slot creating right-sized volumes on 18 new slot installing to 20 notification about setting up for low space 15 O open slot checking for 20 S SMTP configuring for alerts 15 software installation checking for open slot 20 installing to a new slot 20 software upgrade checking volume sizes 16 system alerts specifying 15 system disk space checking available 14, 16 system upgrade about deciding disk size tasks 13 about planning for 13 and questions to ask first 13 V VE disk space about default file size 9 about resizing 5, 7 details of folder structure contents 7 VE disk volume about resizing 11 VE upgrade checking volume sizes 16 virtual disk and questions to ask before upgrade 13 25
Index volume creating correct disk size 12 volume size increasing for disk volume 12 volume sizes about correct for BIG-IQ installation 12 checking for current installation 17 checking required 16 volumes creating on new installation slot 18 26