Skip to main content

 

How to Increase vIDM appliance disk space

Issue/Introduction

This resource provides instructions on how to increase the disk size of all VMware Identity Manager (vIDM) nodes.

Symptoms:
After a series of upgrades, the VMware Identity Manager (vIDM) appliances may not have the correct disk size for the updated version.


Resolution

What is generally observed is when the vIDM appliance has been updated several times, it still features the disk layout from the initial non-Photon installation:

The Photon versions features disk space pictured below:

To increase the disk size, please take the following steps:

Within vCenter, extend Hard disk 1 to 60GB and Hard disk 2 and 3 to 20GB (if Hard disk 4is present, it can be ignored).

NOTE: You cannot change the Hard Disk size if there are current snapshots. Take snapshots after the next step.

Take a snapshot of the VM.

Login as "root" to your appliance let Linux rescan for the disk changes:

echo 1 > /sys/class/block/sda/device/rescan
echo 1 > /sys/class/block/sdb/device/rescan
echo 1 > /sys/class/block/sdc/device/rescan

Verify with fdisk -l


Kindly select the options below depending on if we are extending the root, SDB or SDC

To Extend Root Partition:

To Extend Data Partition - SDB & SDC:

Now you can extend the root partition by following steps below:

This step is applicable only for the root partition

cfdisk /dev/sda

1. Using arrow keys select  /dev/sda4,

2. Using tab key Or shift tab select [ Resize ] then enter
3. Enter the free size available

  • For Example we selected 2M in the screenshot below:

4. Using tab key select [ Write ]

5. type "yes"

6. Press tab to [ Quit ] 


Next, you must resize the file system with "resize2fs" to use the new space:

[before resize2fs]
df -h | grep "sda4"
/dev/sda4 8.8G 3.9G 4.5G 47% /

[run resize2fs]
resize2fs /dev/sda4

[after resize2fs]
df -h | grep "sda4"
/dev/sda4 12G 3.9G 7.3G 35% /


Extend data partition - sdb & sdc:

To resize the two data partitions which are LVMs and the steps are different here versus root partition:

Use "pvresize" to let LVM know that the physical disk size has changed:

[before pvresize]
pvdisplay /dev/sdc /dev/sdb
  --- Physical volume ---
  PV Name               /dev/sdc
  VG Name               tomcat_vg
  PV Size               10.00 GiB / not usable 4.00 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              2559
  Free PE               0
  Allocated PE          2559
  PV UUID               xxxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx

  --- Physical volume ---
  PV Name               /dev/sdb
  VG Name               db_vg
  PV Size               10.00 GiB / not usable 4.00 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              2559
  Free PE               0
  Allocated PE          2559
  PV UUID               xxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx

[run pvresize]
pvresize /dev/sdb /dev/sdc

[after pvresize]
pvdisplay /dev/sdc /dev/sdb
  --- Physical volume ---
  PV Name               /dev/sdc
  VG Name               tomcat_vg
  PV Size               <20.00 GiB / not usable 0
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              5119
  Free PE               2560
  Allocated PE          2559
  PV UUID               xxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx

  --- Physical volume ---
  PV Name               /dev/sdb
  VG Name               db_vg
  PV Size               <20.00 GiB / not usable 0
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              5119
  Free PE               2560
  Allocated PE          2559
  PV UUID               xxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx

Extend the logical volumes with "lvextend" to use the new space:

[before lvextend]
lvdisplay /dev/tomcat_vg/horizon /dev/db_vg/db
  --- Logical volume ---
  LV Path                /dev/tomcat_vg/horizon
  LV Name                horizon
  VG Name                tomcat_vg
  LV UUID                xxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx
  LV Write Access        read/write
  LV Creation host, time sc-xxx-xxx-xxx, 2019-09-12 15:55:24 +0000
  LV Status              available
  # open                 1
  LV Size                <10.00 GiB
  Current LE             2559
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:1

  --- Logical volume ---
  LV Path                /dev/db_vg/db
  LV Name                db
  VG Name                db_vg
  LV UUID                xxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx
  LV Write Access        read/write
  LV Creation host, time sc-xxx-xxx-xxx, 2019-09-12 15:55:23 +0000
  LV Status              available
  # open                 1
  LV Size                <10.00 GiB
  Current LE             2559
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0

[run lvextend]
lvextend -l +100%FREE /dev/tomcat_vg/horizon
lvextend -l +100%FREE /dev/db_vg/db

[after lvextend]
lvdisplay /dev/tomcat_vg/horizon /dev/db_vg/db
  --- Logical volume ---
  LV Path                /dev/tomcat_vg/horizon
  LV Name                horizon
  VG Name                tomcat_vg
  LV UUID                xxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx
  LV Write Access        read/write
  LV Creation host, time sc-xxx-xxx-xxx, 2019-09-12 15:55:24 +0000
  LV Status              available
  # open                 1
  LV Size                <20.00 GiB
  Current LE             5119
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:1

  --- Logical volume ---
  LV Path                /dev/db_vg/db
  LV Name                db
  VG Name                db_vg
  LV UUID                xxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx
  LV Write Access        read/write
  LV Creation host, time sc-xxx-xxx-xxx, 2019-09-12 15:55:23 +0000
  LV Status              available
  # open                 1
  LV Size                <20.00 GiB
  Current LE             5119
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0

 

 

Finally, use "resize2fs" to extend the file system on the two LVs:

 

[before resize2fs]
df -h | grep "mapper"
/dev/mapper/db_vg-db           9.8G 1014M  8.3G  11% /db
/dev/mapper/tomcat_vg-horizon  9.8G  7.1G  2.2G  78% /opt/vmware/horizon

[run resize2fs]
resize2fs /dev/tomcat_vg/horizon
resize2fs /dev/db_vg/db

[after resize2fs]
df -h | grep "mapper"
/dev/mapper/db_vg-db            20G 1019M   18G   6% /db
/dev/mapper/tomcat_vg-horizon   20G  7.2G   12G  39% /opt/vmware/horizon

Labels:

Comments

Post a Comment

Popular posts from this blog

  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
Post a Comment
Read more

57 Tips Every Admin Should Know

Active Directory 1. To quickly list all the groups in your domain, with members, run this command: dsquery group -limit 0 | dsget group -members –expand 2. To find all users whose accounts are set to have a non-expiring password, run this command: dsquery * domainroot -filter “(&(objectcategory=person)(objectclass=user)(lockoutTime=*))” -limit 0 3. To list all the FSMO role holders in your forest, run this command: netdom query fsmo 4. To refresh group policy settings, run this command: gpupdate 5. To check Active Directory replication on a domain controller, run this command: repadmin /replsummary 6. To force replication from a domain controller without having to go through to Active Directory Sites and Services, run this command: repadmin /syncall 7. To see what server authenticated you (or if you logged on with cached credentials) you can run either of these commands: set l echo %logonserver% 8. To see what account you are logged on as, run this command: ...
Post a Comment
Read more
  The Guardrails of Automation VMware Cloud Foundation (VCF) 9.0 has redefined private cloud automation. With full-stack automation powered by Ansible and orchestrated through vRealize Orchestrator (vRO), and version-controlled deployments driven by GitOps and CI/CD pipelines, teams can build infrastructure faster than ever. But automation without guardrails is a recipe for risk Enter RBAC and policy enforcement. This third and final installment in our automation series focuses on how to secure and govern multi-tenant environments in VCF 9.0 with role-based access control (RBAC) and layered identity management. VCF’s IAM Foundation VCF 9.x integrates tightly with enterprise identity providers, enabling organizations to define and assign roles using existing Active Directory (AD) groups. With its persona-based access model, administrators can enforce strict boundaries across compute, storage, and networking resources: Personas : Global Admin, Tenant Admin, Contributor, Viewer Projec...
Post a Comment
Read more