Disk capacity on F5 rSeries

Forums Technical Forums
1

A customer of mine has F5 iSeries with LTM, DNS, APM, and ASM/AFM licenses. Disk capacity is 465 GB. He purchased F5 rSeries on which to set up a tenant, and the disk capacity reserved for tenants is only 294 GB.

I believe the new devices lack space, since the /config folder on the old ones is 75% full.

This is the output on rSeries:

df -h /var/F5/system/cbip-disks

Filesystem Size Used Avail Use% Mounted on

/dev/mapper/partition_tenant-root 294G 36G 244G 13% /var/F5/system/cbip-disks

What do you think about that?

2

Hi @romolo82

We would need more info - source iSeries model? Are all modules provisioned and in use?  Target rSeries HW model,  how was the tenant deployed - etc?

iSeries --> Fixed LVM partitions/shared volume inside TMOS (more static, traditional).

rSeries --> Per-tenant sparse virtual disks managed by F5OS (dynamic, efficient, higher density).

3

Hi, here some informations.

Source iSeries model: BIG-IP i2800. Provisioned and used modules:

afm

apm

asm

avr

fps

gtm

host

ilx

ltm

tmos

Hardware Version Information

Name HD1

Type physical-disk

Model WDC WD5003ABYZ-011FA0

Parameters -- --

Size 465.76G

Firmware Version 01.01S03

Media Type HDD

Hardware Version Information

Name aom

Type aom

Model F5 BMC

Active Firmware 8.00

Backup Firmware 6.04

Boot loader version 3.02

Hardware Version Information

Name cpld

Type cpld

Model F5 CPLD

Parameters -- --

version 0x26

Hardware Version Information

Name cpus

Type base-board

Model Intel(R) Pentium(R) CPU D1508 @ 2.20GHz

Parameters -- --

cache size 3072 KB

cores 4 (physical:2)

cpu MHz 2201.000

cpu sockets 1

cpu stepping 3

Hardware Version Information

Name hsb_lbb0

Type net

Model F5 High Speed Bridge LBB device

Parameters -- --

version Build: 4.3.2 lab 0

Hardware Version Information

Name qa0

Type coproc

Model Cave Creek SKU3 C1 Crypto/Compression Coprocessor

Parameters -- --

version QA API: 1.7.0-30, FW: 1.7.0

Platform

Name BIG-IP i2800

BIOS Revision OBJ-0614-xx BIOS: 3.10.032.0 ME: 3.0.3.23 03/03/2019

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::.

Destination rSeries: r2800. Only one tenant:

MOPSIF5TMOS01a# show tenants tenant mopsiadcvm01a

state type BIG-IP

state image BIGIP-17.1.2.2-0.0.12.ALL-F5OS.qcow2.zip.bundle

state mgmt-ip 10.184.120.112

state vcpu-cores-per-node 8

state memory 24576

state storage size 150

state running-state deployed

state trust-mode true

state appliance-mode disabled

state status Running

state primary-slot 1

state image-version “BIG-IP 17.1.3.1 0.0.6”

Thanks!

4

hi @romolo82 ,

I recommend you check out these docs, they should provide guidance on disk sizing and expansion