No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Command Reference

OceanStor 18000 and 18000F V5 Series V500R007

This document is applicable to OceanStor 18500 V5, 18800 V5, 18500F V5, and 18800F V5. Based on the CLI provided by DeviceManager, this document describes how to use various commands classified by functions and how to set the CLI and manage the storage system through these commands. The document that you browse online matches the latest C version of the product. Click Download to download documents of other C versions.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
change lun

change lun

Function

The change lun command is used to modify the settings of a logical unit number (LUN) including the name, capacity, and type.

Format

change lun lun_id=? { name=? | relocation_policy=? | write_policy=? | owner_controller=? | prefetch_policy=? [ prefetch_multiple=? ] [ prefetch_value=? ] | io_priority=? | read_cache_policy=? | write_cache_policy=? | dif_switch=? | thresholds_switch=? | thresholds_percent=? } * [ description=? | clear_description=? ]

change lun lun_id=? { name=? | relocation_policy=? | write_policy=? | owner_controller=? | prefetch_policy=? [ prefetch_multiple=? ] [ prefetch_value=? ] | io_priority=? | read_cache_policy=? | write_cache_policy=? | dif_switch=? | thresholds_switch=? | thresholds_percent=? | mirror_policy=? | zero_data_enabled=? | work_controller=? } * [ description=? | clear_description=? ]

change lun lun_id=? { compression_enabled=? | compression_method=? | dedup_enabled=? | intelligent_dedup_enabled=? | bytecomparison_enabled=? | dedup_metadata_sample_ratio=? } * [ description=? | clear_description=? ]

change lun { lun_id=? | lun_id_list=? } capacity=? [ description=? | clear_description=? ]

change lun lun_id_list=? { relocation_policy=? | write_policy=? | owner_controller=? | prefetch_policy=? [ prefetch_multiple=? ] [ prefetch_value=? ] | io_priority=? | read_cache_policy=? | write_cache_policy=? | dif_switch=? | thresholds_switch=? | thresholds_percent=? } * [ description=? | clear_description=? ]

change lun lun_id_list=? { relocation_policy=? | write_policy=? | owner_controller=? | prefetch_policy=? [ prefetch_multiple=? ] [ prefetch_value=? ] | io_priority=? | read_cache_policy=? | write_cache_policy=? | dif_switch=? | thresholds_switch=? | thresholds_percent=? | mirror_policy=? | zero_data_enabled=? | work_controller=? } * [ description=? | clear_description=? ]

change lun { lun_id=? | lun_id_list=? } replication_enabled=? [ description=? | clear_description=? ]

change lun { lun_id=? | lun_id_list=? } dedup_checksum_enabled=? [ description=? | clear_description=? ]

change lun { lun_id=? | lun_id_list=? } { silence_check_period=? | silence_check_count=? | silence_keep_time=? } [ description=? | clear_description=? ]

change lun { lun_id=? | lun_id_list=? } { seqflow_bitmap=? | seqflow_counter=? | seqflow_disable_time=? | seqflow_distance=? | seqflow_algorithm_switch=? | seqflow_min_prefetch_threshold=? | seqflow_interval_multiple=? | seqflow_max_prefetch_len=? | seqflow_min_prefetch_len=? } * [ description=? | clear_description=? ]

change lun { lun_id=? | lun_id_list=? } { vstore_id=? } [ force=? ]

change lun lun_name=? { name=? | relocation_policy=? | write_policy=? | owner_controller=? | prefetch_policy=? [ prefetch_multiple=? ] [ prefetch_value=? ] | io_priority=? | read_cache_policy=? | write_cache_policy=? | dif_switch=? | thresholds_switch=? | thresholds_percent=? | mirror_policy=? | zero_data_enabled=? | work_controller=? } * [ description=? | clear_description=? ]

change lun lun_name_list=? { relocation_policy=? | write_policy=? | owner_controller=? | prefetch_policy=? [ prefetch_multiple=? ] [ prefetch_value=? ] | io_priority=? | read_cache_policy=? | write_cache_policy=? | dif_switch=? | thresholds_switch=? | thresholds_percent=? | mirror_policy=? | zero_data_enabled=? | work_controller=? } * [ description=? | clear_description=? ]

change lun { lun_id=? | lun_name=? } isolation_switch=?

change lun { lun_id=? | lun_name=? } capacity_alarm_threshold=?

Parameters

Parameter

Description

Value

lun_id=?

ID of a LUN whose settings you want to modify.

To obtain the value, run "show lun general".

lun_id_list=?

ID list of LUNs whose settings you want to modify.

To obtain the value, run "show lun general". Multiple IDs are separated by commas (,), and the LUN ID range is expressed with hyphens (-).

lun_name_list=?

Name list of LUNs whose settings you want to modify.

To obtain the value, run "show lun general". Multiple IDs are separated by commas (,).

name=?

Updated name of a LUN.

The value contains 1 to 31 ASCII characters, including digits, letters, underscores (_), hyphens (-), and periods (.).

lun_name=?

Name of the LUN before modification.

The value contains 1 to 31 ASCII characters, including digits, letters, underscores (_), hyphens (-), and periods (.).

capacity=?

Updated capacity of a LUN.

The value is in the format of capacity+unit, where the unit can be KB, MB, GB, TB, Blocks, or all.

  • The value ranges from 512 KB to 256 TB.
  • One block equals 512 bytes.
  • When the unit is GB or TB, a decimal number can be used.
  • "all" is used to expand the capacity of an eDevLUN.

relocation_policy=?

SmartTier policy.

The value can be "none", "automatic", "lowest_available", or "highest_available", where:

  • "none": Data migration is not performed.
  • "automatic": The system automatically determines the data migration direction.
  • "lowest_available": Data is migrated to a lower-performance storage tier. For example, data is migrated from the high-performance tier to the performance tier.
  • "highest_available": Data is migrated to a higher-performance tier. For example, data is migrated from the performance tier to the high-performance tier.

The default value is "automatic".

write_policy=?

Cache write policy.

The value can be "write_through" or "write_back", where:

  • "write_through": write-through. The system considers that a data write is successful only after data is written to hard disks. Hard disks are accessed in each data write.
  • "write_back": write-back. After data is written to the cache of the local controller, the system considers that a data write is successful. In addition, the data will be written to the cache of the peer controller as a mirror. When certain conditions are met, the caches write data to disks.

The default value is "write_back".

prefetch_policy=?

Cache prefetch policy.

The value can be "none", "constant", "variable", or "intelligent", where:

  • "none": non-prefetch.
  • "constant": constant prefetch.
  • "variable": variable prefetch.
  • "intelligent": intelligent prefetch.

The default value is "intelligent".

prefetch_multiple=?

Cache prefetch multiple. This parameter is required when "prefetch_policy=?" is set to "variable".

The value ranges from 0 to 1024.

prefetch_value=?

Cache prefetch value. When the value of "prefetch_policy=?" is "constant", this parameter is mandatory. When the value is "intelligent", this parameter is optional.

When the value of "prefetch_policy=?" is "constant", this parameter ranges from 0 to 1024 and is expressed in KB. When the value is "intelligent", this parameter ranges from 1024 to 8192 and is expressed in KB.

owner_controller=?

Owning controller of a LUN.

The value is in the format of "XA", "XB", "XC", or "XD", where the "X" is an integer ranging from 0 to 3.

io_priority=?

I/O priority of a LUN.

The value can be "Low", "Middle", or "High", where:

  • "Low": low priority.
  • "Middle": medium priority.
  • "High": high priority.

read_cache_policy=?

Cache read policy of a LUN.

The value can be "Resident", "Default", or "Recycle". The default value is "Default".

write_cache_policy=?

Cache write policy of a LUN.

The value can be "Resident", "Default", or "Recycle". The default value is "Default".

thresholds_switch=?

Threshold alarm switch of a thin LUN.

The value can be "off" or "on", where:

  • "off": The alarm function will not be enabled.
  • "on": The alarm function will be enabled.

The default value is "off".

thresholds_percent=?

Alarm threshold of a thin LUN.

The value ranges from 50 to 99, expressed in %. The default value is 90.

dif_switch=?

Whether to enable the DIF function.

The value can be "yes" or "no", where:

  • "yes": The DIF function will be enabled.
  • "no": The DIF function will not be enabled.

zero_data_enabled=?

Zero page check switch. This parameter is valid only in developer mode. For details about how to go to the developer mode, see the Advanced O&M Command Reference.

The value can be "yes" or "no", where:

  • "yes": The zero page check switch will be turned on.
  • "no": The zero page check switch will be turned off.

compression_enabled=?

Whether the compression function is enabled.

The value can be "yes" or "no", where:

  • "yes": The compression function will be enabled.
  • "no": The compression function will not be enabled.

The default value is "no".

compression_method=?

Sets the LUN compression algorithm.

The value can be "fast" or "deep", where:

  • "fast": The speed is the priority.
  • "deep": The compression rate is the priority.

The default value is "fast".

dedup_enabled=?

Whether the deduplication function is enabled.

The value can be "yes" or "no", where:

  • "yes": The deduplication function will be enabled.
  • "no": The deduplication function will not be enabled. The default value is "no".

bytecomparison_enabled=?

Whether the byte-by-byte comparison function is enabled.

The value can be "yes" or "no", where:

  • "yes": The byte-by-byte comparison function will be enabled.
  • "no": The byte-by-byte comparison function will not be enabled. The default value is "no".

intelligent_dedup_enabled=?

Whether the intelligent deduplication function is enabled.

The value can be "yes" or "no", where:

  • "yes": The intelligent deduplication function will be enabled.
  • "no": The intelligent deduplication function will not be enabled. The default value is "yes".

dedup_metadata_sample_ratio=?

Deduplication metadata sampling ratio.

The value can be "1", "2", "4", "8", "16", or "32". A larger sample ratio means smaller impact on performance. However, the ratio of space saved by deduplication may be affected.

description=?

LUN description.

The value contains 1 to 255 characters.

clear_description=?

Clears the description.

The value can be:

"Enable": clears the description.

isolation_switch=?

Isolation switch of the LUN.

The value can be "on" or "off", and the default value is "off".

capacity_alarm_threshold

Capacity alarm threshold.

The value is an integer between 1 and 95.

Level

Administrator

Usage Guidelines

  • Before running this command, ensure that the selected LUN is exactly the one whose settings you want to modify.
  • Before running this command, clean up the cache of the application server that has mappings to the selected LUN.

Example

  • Change the capacity of LUN "1" to 300 MB.
    admin:/>change lun lun_id=1 capacity=300MB 
    CAUTION: You are about to expand LUN. This operation will expand the capacity of the LUN. 
    Suggestion: Rescan for the LUN on the server after the capacity expansion. 
    Do you wish to continue?(y/n)y 
    Command executed successfully.
  • Change the cache prefetch policy and I/O priority of LUN "1" to "none" and "Middle" respectively.
    admin:/>change lun prefetch_policy=none io_priority=Middle lun_id=1     
    WARNING: You are about to change the cache prefetch policy of LUN or change the priority of LUN. This operation may affect the LUN performance. 
    Suggestion: Before performing this operation, ensure that the preceding risk is acceptable and the correct LUN is selected. 
    Have you read warning message carefully?(y/n)y 
    Are you sure you really want to perform the operation?(y/n)y 
    Command executed successfully.
  • Change the cache prefetch policy and I/O priority of LUNs "1", "2", and "3" to "none" and "Middle" respectively.
    admin:/>change lun prefetch_policy=none io_priority=Middle lun_id_list=1,2,3     
    WARNING: You are about to change the cache prefetch policy of LUN or change the priority of LUN. This operation may affect the LUN performance. 
    Suggestion: Before performing this operation, ensure that the preceding risk is acceptable and the correct LUN is selected. 
    Have you read warning message carefully?(y/n)y 
    Are you sure you really want to perform the operation?(y/n)y 
    Change LUN 1 successfully. 
    Change LUN 2 successfully. 
    Change LUN 3 successfully.
  • Change the cache prefetch policy of LUNs "1", "2", and "3" to "none".
    admin:/>change lun prefetch_policy=none lun_id_list=1,2,3 
    WARNING: You are about to change the cache prefetch policy of LUN. This operation may affect the LUN performance. 
    Suggestion: Before performing this operation, ensure that the preceding risk is acceptable and the correct LUN is selected. 
    Have you read warning message carefully?(y/n)y 
    Are you sure you really want to perform the operation?(y/n)y 
    Change LUN 1 successfully. 
    Change LUN 2 successfully. 
    Change LUN 3 successfully
  • Change the I/O priority of LUNs "1", "2", and "3" to "Middle".
    admin:/>change lun io_priority=Middle lun_id_list=1,2,3 
    WARNING: You are about to change the priority of LUN. This operation may affect the LUN performance. 
    Suggestion: Before performing this operation, ensure that the preceding risk is acceptable and the correct LUN is selected. 
    Have you read warning message carefully?(y/n)y 
    Are you sure you really want to perform the operation?(y/n)y 
    Change LUN 1 successfully. 
    Change LUN 2 successfully. 
    Change LUN 3 successfully.
  • Change the sequence flow bitmap of LUN "1" to 12.
    developer:/>change lun lun_id =1 seqflow_bitmap=12 
    WARNING: You are about to change the parameters related to the cache sequential flow of the LUN. This operation may affect the LUN performance. 
    Suggestion: Before performing this operation, ensure that the preceding risk can be accepted and the selected LUN is correct. 
    Have you read warning message carefully?(y/n)y 
    Are you sure you really want to perform the operation?(y/n)y 
    Change LUN 1 successfully.
  • Change the sequence flow disabling time of LUNs "1", "2", and "3" to 3600.
    developer:/>change lun lun_id_list=1,2,3 seqflow_disable_time=3600 
    WARNING: You are about to change the parameters related to the cache sequential flow of the LUN. This operation may affect the LUN performance. 
    Suggestion: Before performing this operation, ensure that the preceding risk can be accepted and the selected LUN is correct. 
    Have you read warning message carefully?(y/n)y 
    Are you sure you really want to perform the operation?(y/n)y 
    Change LUN 1 successfully. 
    Change LUN 2 successfully. 
    Change LUN 3 successfully.
  • Change the vStore ID of LUN "1" to 2.
    developer:/>change lun lun_id=1 vstore_id=2 
    CAUTION: You are about to change the ID of the vStore to which the LUN belongs. This operation will change the vStore to which the LUN belongs.  
    Suggestion: Before you perform this operation, ensure that the preceding risks are acceptable and that the selected LUN is correct. 
    Do you wish to continue?(y/n)y 
    Command executed successfully.
  • Change the vStore ID of LUNs "1", "2", and "3" to "2".
    developer:/>change lun lun_id_list=1,2,3 vstore_id=2 
    CAUTION: You are about to change the ID of the vStore to which the LUN belongs. This operation will change the vStore to which the LUN belongs.  
    Suggestion: Before you perform this operation, ensure that the preceding risks are acceptable and that the selected LUN is correct. 
    Do you wish to continue?(y/n)y 
    Change LUN 1 successfully. 
    Change LUN 2 successfully. 
    Change LUN 3 successfully.
  • Change the vStore ID of LUNs "1", "2", and "3" to "2" forcibly.
    developer:/>change lun lun_id_list=1,2,3 vstore_id=2 force=yes 
    WARNING: You are about to forcibly change the ID of the vStore to which the LUN belongs. This operation will forcibly change the vStore ID of the LUN and LUN's snapshot. As a result, value-added services of the LUN may be unavailable.  
    Suggestion: Before performing this operation, ensure that the preceding risks are acceptable and the selected LUN is correct. 
    Have you read warning message carefully?(y/n)y 
    Are you sure you really want to perform the operation?(y/n)y 
    Change LUN 1 successfully. 
    Change LUN 2 successfully. 
    Change LUN 3 successfully.
  • Change the cache prefetch policy and I/O priority of LUNs "LUN001", "LUN002", and "LUN003" to "none" and "Middle" respectively.
    admin:/>change lun prefetch_policy=none io_priority=Middle lun_name_list=LUN001,LUN002,LUN003 
    WARNING: You are about to change the cache prefetch policy of LUN or change the priority of LUN. This operation may affect the LUN performance. 
    Suggestion: Before performing this operation, ensure that the preceding risk is acceptable and the correct LUN is selected. 
    Have you read warning message carefully?(y/n)y 
    Are you sure you really want to perform the operation?(y/n)y 
    Change LUN 1 successfully. 
    Change LUN 2 successfully. 
    Change LUN 3 successfully.
  • Change the name of LUN "LUN001" to "LUN002".
    admin:/>change lun lun_name=LUN001 name=LUN002 
    WARNING: You are about to change the cache prefetch policy of LUN or change the priority of LUN. This operation may affect the LUN performance. 
    Suggestion: Before performing this operation, ensure that the preceding risk is acceptable and the correct LUN is selected. 
    Have you read warning message carefully?(y/n)y 
    Are you sure you really want to perform the operation?(y/n)y 
    Command executed successfully.
  • Change the isolation switch of LUN "1" to on.
    developer:/>change lun lun_id=1 isolation_switch=on 
    DANGER: You are about to isolate the LUN. After the operation, the status of the LUN becomes offline, and all services related to the LUN are interrupted. 
    Suggestion: Before performing this operation, ensure that all services of the LUN are allowed to be interrupted. 
    Have you read danger alert message carefully?(y/n)y 
    Are you sure you really want to perform the operation?(y/n)y 
    Command executed successfully.
  • Change the isolation switch of LUN "LUN001" to off.
    developer:/>change lun lun_name=LUN001 isolation_switch=off 
    Command executed successfully.
  • Change the capacity alarm threshold of LUN "1" to 80%.
    admin:/>change lun lun_id=1 capacity_alarm_threshold=80 
    Command executed successfully.
  • Change the capacity alarm threshold of LUN "LUN001" to 80%.
    admin:/>change lun lun_name=LUN001 capacity_alarm_threshold=80 
    Command executed successfully.
  • Change the SmartTIer policy of LUNs "1", "2", and "3" to "automatic".
    admin:/>change lun lun_id_list=1,2,3 relocation_policy=automatic 
    WARNING: The current SmartTier policy is automatic relocation. The policy takes effect only after the I/O monitoring function is enabled. 
    Suggestion: Check whether the I/O monitoring function is enabled. 
    Have you read warning message carefully?(y/n)y 
    Are you sure you really want to perform the operation?(y/n)y 
    Change LUN 1 successfully. 
    Change LUN 2 successfully. 
    Change LUN 3 successfully.
  • Change the SmartTIer policy of LUNs "1", "2", and "3" to "lowest_available".
    admin:/>change lun lun_id_list=1,2,3 relocation_policy=lowest_available 
    WARNING: The current SmartTier policy is relocation to the low-performance tier. If the amount of data to be relocated is too large, the low-performance tier may be used up. As a result, data cannot be relocated to the low-performance tier. 
    Suggestion:  Ensure that the capacity configured for the low-performance tier can meet subsequent requirements. 
    Have you read warning message carefully?(y/n)y 
    Are you sure you really want to perform the operation?(y/n)y 
    Change LUN 1 successfully. 
    Change LUN 2 successfully. 
    Change LUN 3 successfully.
  • Change the SmartTIer policy of LUNs "1", "2", and "3" to "highest_available".
    admin:/>change lun lun_id_list=1,2,3 relocation_policy=highest_available 
    WARNING: The current SmartTier policy is relocation to the high-performance tier. If the amount of data to be relocated is too large, the high-performance tier may be used up. As a result, data cannot be relocated to the high-performance tier. 
    Suggestion:  Ensure that the capacity configured for the high-performance tier can meet subsequent requirements. 
    Have you read warning message carefully?(y/n)y 
    Are you sure you really want to perform the operation?(y/n)y 
    Change LUN 1 successfully. 
    Change LUN 2 successfully. 
    Change LUN 3 successfully.

System Response

None

Translation
Download
Updated: 2019-09-02

Document ID: EDOC1000181601

Views: 322240

Downloads: 41

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next