i was wondering how i could get the next free lun id (or free lun id list) from a command line, i did not found the option within navicli
Anyone know how to do it ?
There is no CLI command that will give you the next available LUN. This info is available in the UI when using the expand wizard, but the available LUN list is compiled with some filtering by Navi Mgr.
When planning metaLUNs, most users design a LUN numbering scheme that will give them and idea of the physical placement within the array. It looks like you are planning several striped metaLUNs. First, the array requires that the LUNs in a striped expansion be the exact same size. You may have handled this by standardizing on a particular LUN size.
For the physical placement, you can employ a LUN numbering scheme that includes the RG number. In your example, you are creating a meta with LUNs residing on RGs 3 and 10. For example, let's assume you are binding 10 LUNs per RG. You would bind LUN numbers 300 - 309 (or 301 - 310) on RG 3 and LUNs 1000 - 1009 on RG 10.
When you build your script, you can key off of the LUN position in the RG to build your metaLUN. So LUNs 301 and 1001 would be used to create a stripe, etc. If you wanted to expand the capacity of the group later, you could add a striped component with LUNs 302 and 1002, etc.
The topic of metaLUN expansion strategies is covered in the document CLARiiON Best Practices for Fibre Channel Devices on PowerLink. Although it doesn't go into detail about LUN numbering specifically, I think it describes the recommended approach pretty well.
fpatraul, Can you provide a bit of context behind the question? In case this may be related to bind operations - when issuing a bind request, if a specific LUN number is not specified, the lowest available number will be automatically assigned.
i would like to create a script which could create metalun with specifying only few options, ie. number of luns, raidgroup and hostname (i omit description, keeping it by default)
the problem i see is that expanding need to specify the lunid used for the bind command, how should i guess which one is used for previous bind operation (lowest)
I know exactly what you are trying to do here. Unfortunately you would have to create some sort of DB to keep track of all the currently used LUN ID's (Which is just way to much work for what you are trying to do). If you don't care what the ID's are then just leave them blank and it will assign them. Unfortunately the people that make the GUI do not think of us CLI users
BAP2
12 Posts
623
0
Posted November 29th, 2006 11:00
There is no CLI command that will give you the next available LUN. This info is available in the UI when using the expand wizard, but the available LUN list is compiled with some filtering by Navi Mgr.
When planning metaLUNs, most users design a LUN numbering scheme that will give them and idea of the physical placement within the array. It looks like you are planning several striped metaLUNs. First, the array requires that the LUNs in a striped expansion be the exact same size. You may have handled this by standardizing on a particular LUN size.
For the physical placement, you can employ a LUN numbering scheme that includes the RG number. In your example, you are creating a meta with LUNs residing on RGs 3 and 10. For example, let's assume you are binding 10 LUNs per RG. You would bind LUN numbers 300 - 309 (or 301 - 310) on RG 3 and LUNs 1000 - 1009 on RG 10.
When you build your script, you can key off of the LUN position in the RG to build your metaLUN. So LUNs 301 and 1001 would be used to create a stripe, etc. If you wanted to expand the capacity of the group later, you could add a striped component with LUNs 302 and 1002, etc.
The topic of metaLUN expansion strategies is covered in the document CLARiiON Best Practices for Fibre Channel Devices on PowerLink. Although it doesn't go into detail about LUN numbering specifically, I think it describes the recommended approach pretty well.
Regards,
Bruce
The Best Practices paper is posted to PowerLink:
http://powerlink.emc.com/km/live1/en_US/Offering_Technical/White_Paper/H2358_clariion_best_prac_fibre_chnl_wp_ldv.pdf?mtcs=ZXZlbnRUeXBlPUttQ2xpY2tTZWFyY2hSZXN1bHRzRXZlbnQsZG9jdW1lbnRJZD0wOTAxNDA2NjgwMWI1NzZlLGRhdGFTb3VyY2U9RENUTV9lbl9VU18w