ianhoskins

updated

15 years ago

0

1244

December 15th, 2011 13:00

Metalun base identification

What is the best way to find the base lun of a meta lun?  I originally thought it was the lun with the lowest id, but migrations screw that theory up.

  • kelleg

    6 Operator

    4537 Posts

    418

    0

    Posted December 16th, 2011 13:00

    I just created a 4 component strippedmetaLUN using LUNs 300, 301, 302 and 303. I expanded using LUN 303. This is the results of the naviseccli metalun -list command (minus extra stuff). It takes the meta base LUN (303) and renumbers the LUN Number to 24530 - the Number is the important part  - LUN Name can be anything. It then takes the next component LUN, re-numbers the Number to 24531 (component 302) and so on (301, then 300). So the lowest "MetaLUN Number" is the metaLUN base LUN.

    MetaLUN Number:  303

    MetaLUN Name:  LUN 303

    Element Size Multiplier:  4

    Components:

    Number of LUNs:  4

    LUNs:

    LUN Number:  24530

    LUN Name:  LUN 303  <---- this is the meta base LUN - note that the LUN number above is 24530 - this is the lowest number of the four component LUNs.

    LUN WWN:  60:06:01:60:8B:C9:22:00:06:D6:89:4D:2D:28:E1:11

    RAID Type:  RAID5

    LUN Number:  24537

    LUN Name:  LUN 300

    LUN WWN:  60:06:01:60:8B:C9:22:00:D4:66:8E:E5:2C:28:E1:11

    RAID Type:  RAID5

    LUN Number:  24535

    LUN Name:  LUN 301

    LUN WWN:  60:06:01:60:8B:C9:22:00:3A:4B:3E:04:2D:28:E1:11

    RAID Type:  RAID5

    LUN Number:  24531

    LUN Name:  LUN 302 - this is the second component LUN - note that its new LUN Number is 24531 (line above)

    LUN WWN:  60:06:01:60:8B:C9:22:00:E8:59:57:10:2D:28:E1:11

    RAID Type:  RAID5

    glen

  • kelleg

    6 Operator

    4537 Posts

    418

    1

    Posted December 15th, 2011 14:00

    Please see page 13 in the following for a complete explanation of the base component.

    White Paper EMC CLARiiON MetaLUNs - A Detailed Review.pdf

    http://powerlink.emc.com/km/live1/en_US/Offering_Technical/White_Paper/H1024.1_clariion_metaluns_cncpt_wp_ldv.pdf

    Alt-Click to follow the link

    glen

  • 418

    0

    Posted December 16th, 2011 05:00

    OK, so it is saying the the MetaLun Number should match one of the component LUN IDs and that will be the base... here is an example from naviseccli getall.... MetaLune Number is 166, but all the component LUNs are in the 6xx.  Am I looking at the wrong ID?

    MetaLUN Number:  166

    MetaLUN Name:  META 166

    MetaLUN WWN:  60:06:01:60:04:61:21:00:28:27:C6:98:81:21:DF:11

    Default Owner:  SP A

    Auto-assign:  No

    Expansion Rate:  HIGH

    Bind Offset:  0

    Can metaLUN Be Expanded:  Yes

    Current State:  ENABLED

    Current Owner:  SP A

    Percent Expanded:  100

    Total User Capacity (Blocks/Megabytes):  2516582400/1228800

    Actual User Capacity (Blocks/Megabytes):  2516582400/1228800

    Auto-trespass:  No

    Is Redundant:  Yes

    Drive Type:  Fibre Channel

    Element Size Multiplier:  4

    Read Histogram[0]:  91223

    Read Histogram[1]:  73962

    Read Histogram[2]:  111094

    Read Histogram[3]:  18612802

    Read Histogram[4]:  932862205

    Read Histogram[5]:  1445789299

    Read Histogram[6]:  1004868064

    Read Histogram[7]:  2890156830

    Read Histogram[8]:  567258760

    Read Histogram[9]:  191968793

    Read Histogram Overflows:  296057933

    Write Histogram[0]:  87878

    Write Histogram[1]:  190505

    Write Histogram[2]:  71556

    Write Histogram[3]:  2043653

    Write Histogram[4]:  3325979823

    Write Histogram[5]:  672102050

    Write Histogram[6]:  115533215

    Write Histogram[7]:  112757266

    Write Histogram[8]:  36531975

    Write Histogram[9]:  97992649

    Write Histogram Overflows:  2022638

    Read Requests:  479492110

    Write Requests:  325923476

    Blocks Read:  4043805411

    Blocks Written:  3651257940

    Components: 

    Number of LUNs:  4

    LUNs: 

    LUN Number:  5965

    LUN Name:  LUN 609

    LUN WWN:  60:06:01:60:04:61:21:00:FA:B1:B5:C9:31:4E:DF:11

    RAID Type:  RAID5

    LUN Number:  5964

    LUN Name:  LUN 606

    LUN WWN:  60:06:01:60:04:61:21:00:90:21:9B:18:34:4E:DF:11

    RAID Type:  RAID5

    LUN Number:  5966

    LUN Name:  LUN 608

    LUN WWN:  60:06:01:60:04:61:21:00:F2:8F:91:A4:31:4E:DF:11

    RAID Type:  RAID5

    LUN Number:  5967

    LUN Name:  LUN 607

    LUN WWN:  60:06:01:60:04:61:21:00:56:65:27:80:31:4E:DF:11

    RAID Type:  RAID5

  • Storagesavvy

    474 Posts

    418

    1

    Posted December 16th, 2011 09:00

    The 6xx numbers you see are actually the text LUN names assigned to the LUNs before they were added to the Meta. You want to look at the LUN Numbers which are in the 5xxx range. If I recall correctly, the lowest number is the base LUN.

    Richard J Anderson

  • kelleg

    6 Operator

    4537 Posts

    418

    0

    Posted December 16th, 2011 13:00

    I'm betting that at one time, the original LUN Number 166 was actually renamed to LUN Name "LUN 606" before it was used in the metaLUN. You can't change the LUN Number, but you can change the LUN Number.

    glen

  • 418

    0

    Posted December 16th, 2011 13:00

    alrighty, that sounds good.... thanks for all the info.