Forum Discussion
KaiTT
Nimbostratus
Nimbostratusr5600 disk size
Hi All,
We are planning to configure r5600 as one tenant soon.
The vCPU will allocate all 12 of them, and the virtual disk will allocate the maximum size of 434GB.
When I checked Tenant default allocation disk, it was a little different from the iSeries.
| i7800 | r5600 (One Tenant) | |
| /shared | 40 GB | 15 GB |
| /var | 3 GB | 4.5 GB |
| /config | 3.2 GB | 3.2 GB |
| /var/log | 20 GB | 2.9 GB |
It seems that /shared and /var/log disk space is much less than that of the iSeries.
Has anyone experienced a lack of disk space because they didn't expand the disk space in the tenant?
Thanks.
Hi KaiTT,
I worked on a client setup having multiple r10900 with with multi tenacy but no such disk space issues so far.
r5600 has 1024 GB SSD 2.0 = 1x 1TB M.2 SSD
These are default allocation in case you need to change these partitiotn size can increase and decrease based on the requirements and can be customize.
r5600 can have handle upto 8 multi tenacy, if reuire more go for r5800 or r5900Please note that Increasing the disk size on the BIG-IP VE is irreversible because F5 does not support disk shrinking.
Please note you must shut down the BIG-IP VE during the disk provisioning steps, and the system will not be available for traffic processing. You should perform this procedure during a suitable maintenance window. Increasing the disk size on the BIG-IP VE is irreversible because F5 does not support disk shrinking. Increasing the disk size beyond 1.9 TB may render the system unbootable. F5 recommends the extended disk space should not exceed 1.9TB.
https://wtit.com/f5-products/f5-big-ip-r5600-r5800-r5900-hardware-datasheet/
https://clouddocs.f5.com/training/community/rseries-training/html/rseries_multitenancy.html
K000137433: Extending disk space for BIG-IP tenants running on F5 VELOS and rSeries
https://my.f5.com/manage/s/article/K14952
https://my.f5.com/manage/s/article/K000137433
Hope that Helps
š
ā
