CUCM 9.11 to 9.12 upgrade "Partitions Aligned"

[fredmerzjr]

I have a customer who wants to verify if their CUCM 9.1.1 disks Partitions are Aligned prior to proceeding with the 9.1.2 upgrade. Is there a TAC approved procedure that can be performed prior to the upgrade to validate the CUCM Partitions are Aligned?

[Jaime Valencia]

When you log via CLI or to CCMAdmin, does it says they're unaligned?? If no, they're aligned.

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

[Aman Soi]

Hi,

As far as I know when u login through GUI in Application Administration page , u get the message Partitions UnAligned/Aligned.

Let other members also share their ideas.

regds,

aman

[fredmerzjr · Accepted solution]

Cisco TAC provided the following procedure:

• •1)      Shutdown the vm
• •2)      Logged in using root username/password for ESXi
• •3)      cd /vmfs/volume
• •4)      ls (to list all my datastores)       Now find the datastore that you used to install the Vms
• •5)      cd    Example in my lab : cd datastore2
• •6)      ls  (list all the VMs in the datastore)
• •7)      cd “VM name”      USE quotes if your VM name contains any spaces
• •8)      ls   (you should see a file with .vmdk extension. IT Will word flat before it)
• •9)      fdisk –lu  < filename-flat.vmdk>    

The output will be something like this.  The key is too look for partition to start at “128”  This one does.   If its something like 63. Then its not aligned.

                  Device Boot      Start         End      Blocks  Id System

CUCM 10.0 Sub-flat.vmdkp1   *       128  29753343  14876608   83  Linux

Partition 1 has different physical/logical endings:

     phys=(1023, 254, 63) logical=(1852, 15, 19)

CUCM 10.0 Sub-flat.vmdkp2      29753344  59506687  14876672   83  Linux

Partition 2 has different physical/logical beginnings (non-Linux?):

     phys=(1023, 254, 63) logical=(1852, 15, 20)

Partition 2 has different physical/logical endings:

     phys=(1023, 254, 63) logical=(3704, 30, 38)

CUCM 10.0 Sub-flat.vmdkp3      59506688  60030975    262144   83  Linux

Partition 3 has different physical/logical beginnings (non-Linux?):

     phys=(1023, 254, 63) logical=(3704, 30, 39)

Partition 3 has different physical/logical endings:

     phys=(1023, 254, 63) logical=(3736, 192, 40)

CUCM 10.0 Sub-flat.vmdkp4      60030976 167766794  53867909+   5  Extended

Partition 4 has different physical/logical beginnings (non-Linux?):

     phys=(1023, 254, 63) logical=(3736, 192, 41)

Partition 4 has different physical/logical endings:

     phys=(1023, 254, 63) logical=(10442, 254, 63)

CUCM 10.0 Sub-flat.vmdkp5      60031104  64159680   2064288+  82  Linux swap

CUCM 10.0 Sub-flat.vmdkp6      64159744 167766794  51803525+  83  Linux

Unknown value(s) for: cylinders (settable in the extra functions menu)

[Rob Huffman]

Hi Fred,

Thanks for providing this excellent info +5

You can see a reference to this in a 9.1.1 bug;

With the resolution of CSCug40943, the "show hardware" CLI command now  also provides specific details for disk partitions (partitions are  aligned when start sector value is evenly divisibly by 64). This DDTS is  to update the documentation to reflect the addition of this information  to the "show hardware" output.

Further, with the related  enhancement CSCug69836 "Include partition alignment check in "VMware  Installation" CLI & GUI", the VMware Installation information line  now explicitly indicates whether the disk partitions are aligned or  unaligned.

From;

Partition alignment/OVA deployment information missing from CLI DOC

CSCug77072

Cheers!

Rob

"Seek it out and ye shall find  " 

- OneRepublic

[Aman Soi]

Hi Rob,

thanks for sharing additional info on associated bugs[+5]

regds,

aman