Navisphere Command Line Interface (CLI) Reference - VMware Communities

LUN Expansion (MetaLUN) Commands-lus lunnumber|WWNSpecifies the LUN number or World Wide Name of the LUNs youwant to add to the LUN or metaLUN (expansion LUNs). Use onlyone of the identifiers per LUN with the -lus command. Use themetalun -list command to determine the number or WWN of theLUNs (see “metalun -list” on page 341).Note: Expansion LUNs cannot be participating in a SnapView (snapshotor clones), MirrorView, or SAN Copy session.The optional switches are:-autoassign 0|1 (Not supported on AX4-5 series systems runningNavisphere Manager)Enables or disables autoassign for a metaLUN. Specify 1 to enableautoassign and 0 to disable it. If you do not specify an autoassignvalue, it defaults to the value of the base LUN.Autoassign controls the ownership of the LUN when an SP failsin a storage system with two SPs. With autoassign enabled, if theSP that owns the LUN fails and the server tries to access that LUNthrough the second SP, the second SP assumes ownership of theLUN to enable access. The second SP continues to own the LUNuntil the failed SP is replaced and the storage system is poweredup. Then, ownership of the LUN returns to its default owner. Ifautoassign is disabled in the previous situation, the second SPdoes not assume ownership of the LUN, and access to the LUNdoes not occur.If you are running failover software on a Windows or UNIXserver connected to the storage system, you must disableautoassign for all LUNs that you want to fail over to the workingSP when an SP fails.-bindoffset sector-number (Not supported on AX4-5 series systemsrunning Navisphere Manager)Note: Available only if the preservedata switch is set to 0.EMC does not recommend using a metaLUN bindoffset value if the baseLUN already has one.Automatically aligns the logical sector number of the metaLUNto a stripe boundary on the base LUN. The value to enter is thenumber of sectors by which user data is offset due to file systemor paritition metadata.333