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

OceanStor 2200 V3 and 2600 V3 Storage System V300R005 SmartVirtualization Feature Guide 07

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).
General Restrictions

General Restrictions

This section describes the restrictions that must be observed when the OceanStor 2200 V3/2600 V3 hosts LUNs created on a heterogeneous storage system.

  • Generally, external LUNs that have been mapped to a local storage system cannot be mapped to any hosts or storage systems any more.
    Perform the following operations to map the external LUNs that have been mapped to a local storage system to a host:
    1. Stop services on the eDevLUN that corresponds to the external LUNs.
    2. Wait until all service data on the eDevLUN are sent to a heterogeneous storage system.

      Run the show lun_cache general command to view cache data on the eDevLUN. If the values in Dirty Page and Fault Page are No, all service data on the eDevLUN has been sent to the heterogeneous storage system.

    3. Delete the eDevLUN and cancel the mapping relationship between the external LUNs and the local storage system in the heterogeneous storage system.
    4. Map the external LUNs to a host and restart services on the external LUNs.
  • Before deleting the external LUN from the heterogeneous storage system, delete its corresponding eDevLUN from the local storage system.
  • Do not map read-only LUNs (such as snapshot LUNs in some heterogeneous storage systems and LUNs for which write protection is configured) to the local storage system.
  • Do not map external LUNs whose sector size is 4 KB to a local storage system.
    NOTE:

    For details about how to view sector size, see operation guides for heterogeneous storage systems.

  • To ensure data on the heterogeneous storage system is consistent with that on the local storage system, do not change Host LUN ID of external LUNs on the heterogeneous storage system if external LUNs have been connected to the local storage system and there are services on the external LUNs.
  • After HyperMetro is configured for a LUN (including local or remote LUN of HyperMetro) on a Huawei OceanStor V3 storage system, the LUN cannot be mapped to the local storage system for a heterogeneous takeover.
  • After the thin LUNs of the heterogeneous storage systems are mapped to the local storage system and eDevLUNs are created, you are advised to set the write policy of the eDevLUNs to write through.
    NOTE:

    If you need to configure value-added features for the eDevLUNs, see the principles of how to modify write policies for eDevLUNs described in Follow-up Procedure in "Creating an eDevLUN Without Masquerading Properties" or "Creating an eDevLUN With Masquerading Properties".

  • The number of heterogeneous storage systems connected to a local storage system cannot exceed the upper limit.
    If the number of heterogeneous storage systems reaches or exceeds the upper limit, take recommended actions in Table 10-1.
    NOTE:

    For details about the specifications, refer to the OceanStor 2200 V3&2600 V3 Storage System V300R005 Product Description.

    Table 10-1  Recommended actions when the number of heterogeneous storage systems reaches or exceeds the upper limit

    Configuration Scenario

    Symptom

    Recommended Action

    The number of heterogeneous storage systems reaches the upper limit.

    New heterogeneous storage systems cannot be connected.

    1. Remove one or more heterogeneous storage systems on the DeviceManager.
    2. Disconnect the local storage system from the existing heterogeneous storage systems.
    3. Connect the local storage system to new heterogeneous storage systems.
    4. Optional: If an iSCSI network is set up between the local storage system and the heterogeneous storage system, add the new heterogeneous storage systems on the DeviceManager.
    NOTE:

    After removing a cable, wait at least 30 seconds before reinserting it.

    The number of heterogeneous storage systems exceeds the upper limit.

    Connected heterogeneous storage systems cannot be correctly identified.

    1. Remove one or more heterogeneous storage systems on the DeviceManager.
    2. Disconnect the local storage system from the storage systems that cannot be identified.
    3. Connect the local storage system to the storage systems that cannot be identified.
    4. Optional: If an iSCSI network is set up between the local storage system and the heterogeneous storage system, add the unidentified heterogeneous storage system on the DeviceManager.
    NOTE:

    After removing a cable, wait at least 30 seconds before reinserting it.

  • The number of links between a local storage system and heterogeneous storage systems cannot exceed the upper limit.
    If the number of links reaches or exceeds the upper limit, take recommended actions in Table 10-2.
    NOTE:

    For details about the specifications, refer to the OceanStor 2200 V3&2600 V3 Storage System V300R005 Product Description.

    Table 10-2  Recommended actions when the number of links reaches or exceeds the upper limit

    Configuration Scenario

    Symptom

    Recommended Action

    The number of links between a local storage system and heterogeneous storage systems reaches the upper limit.

    New links cannot be added to the storage systems.

    1. Remove one or more links between the local storage system and heterogeneous storage systems.
    2. Re-connect the new links.
    NOTE:

    After removing a cable, wait at least 30 seconds before reinserting it.

    The number of links between a local storage system and heterogeneous storage systems exceeds the upper limit.

    Connected links cannot be identified by the local storage system.

    1. Remove one or more links between the local storage system and heterogeneous storage systems.
    2. Re-connect the links that cannot be identified.
    NOTE:

    After removing a cable, wait at least 30 seconds before reinserting it.

  • When external LUNs are mapped to the local storage system, the number of LUNs mapped from the same heterogeneous storage system to the local storage system cannot exceed the upper limit, and host LUN IDs must range from 0 to 510. and host LUN IDs must range from 0 to 8191.
    If the number of mapped LUNs reaches or exceeds the upper limit, take recommended actions in Table 10-3.
    Table 10-3  Recommended actions when the number of LUN mappings reaches the upper limit

    Configuration Scenario

    Symptom

    Recommended Action

    The number of LUNs mapped to a local storage system reaches the upper limit.

    New mapped LUNs cannot be identified by the local storage system any more.

    1. Perform the following operations on the heterogeneous storage system:
      1. Remove at least one LUN mapping.
      2. Add a new LUN mapping.
    2. Perform the following operation on the local storage system:
      1. Scan for LUNs.

    The number of LUNs mapped to a local storage system exceeds the upper limit.

    • Existing mapped LUNs cannot be identified by the local storage system.
    • The number of remote LUNs in the local link is different from the number of remote LUNs actually mapped to the local storage system.
    NOTE:

    Existing mapped LUNs cannot be identified by the local storage system after it is powered off and re-powered on.

    1. Remove one or more LUN mappings and LUN mappings that cannot be identified on the heterogeneous storage systems.
    2. Scan for LUNs on the local storage system.
    3. Add LUN mappings for LUNs that cannot be identified on the heterogeneous storage systems.
    4. Scan for LUNs on the local storage system.

    The number of LUNs mapped to the local storage system through a controller reaches the upper limit.

    After the new heterogeneous storage system is connected to a controller, the local storage system fails to identify the heterogeneous storage system.

    1. Perform the following operation on the heterogeneous storage system:
      1. Cancel the mapping of one or multiple LUNs that are not in use.
    2. Perform the following operation on the local storage system:
      1. Scan for LUNs.
Translation
Download
Updated: 2018-12-29

Document ID: EDOC1000106155

Views: 55524

Downloads: 143

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