Navisphere Command Line Interface (CLI) Reference - VMware Communities

LUN Expansion (MetaLUN) CommandsConcatenate expansion requirements and recommendationsAll LUNs within a concatenated metaLUN component must be thesame size and RAID type, but can differ from the size and RAID typeof LUNs within other components.Note: EMC does not recommend that you expand LUN capacity byconcatenating LUNs of different RAID types. Do this only in an emergencysituation when you need to add capacity to a LUN and you do not haveLUNs of the same RAID type or the disk capacity to bind new ones.Concatenating metaLUN components with a variety of RAID types couldimpact the performance of the resulting metaLUN. Once you expand a LUN,you cannot change the RAID type of any of its components withoutdestroying the metaLUN. Destroying a metaLUN unbinds all LUNs in themetaLUN, and therefore causes data to be lost.Syntaxmetalun - expand is used with naviseccli (described on page 37) tocreate a new metaLUN or expand an existing metaLUN. There are twodistinct versions of this command, one for Navisphere Manager andone for Navisphere Express. When using this command withNavisphere Express, the syntax is simpler and does not requirebinding the destination LUN first. The process is different withNavisphere Manager and requires you to bind the destination LUNbefore running the command.Note: The following command syntax works only with Navisphere Manager.To create a new metaLUN, the following command switches arevalid:metalun - expand -base number|WWN -lus number|WWN[-autoassign 0|1] [-bindoffset sector-number] [-cap capacity][-defaultowner A|B] [-elszm elementSizeMultiplier][-expansionrate low|medium|high|ASAP|value][-name metaLUNname] [-preservedata 1|0] [-nogrow] [-o][-sq tb|gb|mb|bc] [-type C|S]To expand a metaLUN, the following command switches are valid:metalun - expand -base number|WWN -lus number|WWN [-typeC|S] [-sq tb|gb|mb|bc] [-cap number] [-nogrow] [-o]331