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).
When an OceanStor V3 Is Heterogeneously Taken Over by Another OceanStor V3, What Are the Device SN and Device Model of the Remote LUNs Displayed on the Second One?

When an OceanStor V3 Is Heterogeneously Taken Over by Another OceanStor V3, What Are the Device SN and Device Model of the Remote LUNs Displayed on the Second One?

Question

When an OceanStor V3 is heterogeneously taken over by another OceanStor V3, what are the Device SN and Device Model of the remote LUNs displayed on the second one?

Answer

For example, there are three storage systems on the live network, namely, Storage1 (a storage system with an version earlier than V300R005), Storage2 (an OceanStor V3 storage system in version V300R005), and Storage3 (an OceanStor V3 storage system in version V300R005). After an eDevLUN is created for Storage2 to take over data from Storage1, the eDevLUN created in Storage2 is then mapped to Storage3. This scenario is a typical example of an OceanStor V3 heterogeneously taken over by another OceanStor V3. Figure 8-1 shows the whole takeover process.
Figure 8-1  Diagram of an OceanStor V3 heterogeneously taken over by another OceanStor V3

The following lists different scenarios in which Storage3 heterogeneously takes over Storage2. Table 8-1 shows the information displayed in DeviceManager on Storage3 after Storage2 LUNs are mapped to Storage3.
Table 8-1  Description of the pages displayed on Storage 3 in different mapping relationships

Scenario Number

Situation in Which Storage3 Heterogeneously Takes Over Storage2

Follow-up Mapping Relationship Between Storage2 and Storage3

Description of the DeviceManager Page on Storage3

Scenario 1

  1. Storage1 -> Storage2

    Storage 2 takes over the LUNs on Storage 1 on line by creating eDevLUNs that are masqueraded. Set eDevLUNs' host LUN ID to 0.

  2. Storage2 -> Storage3

    Map the eDevLUNs created on Storage 2 to Storage 3.

Map the LUNs (including local LUNs and eDevLUNs) that are not masqueraded on Storage 2 to Storage 3.

The Device SN of the remote LUNs is the SN of Storage 2, but the Device Model is the device model of Storage 1.

Map the LUNs (including local LUNs and eDevLUNs) that are masqueraded on Storage 2 to Storage 3.

The Device SN and Device Model of the remote LUNs are those of Storage 1.

Scenario 2

  1. Storage1 -> Storage2
    • Storage 2 takes over the LUNs on Storage 1 on line by creating eDevLUNs that are masqueraded. Do not set eDevLUNs' host LUN ID to 0.
    • Storage 2 takes over the LUNs on Storage 1 by creating eDevLUNs that are not masqueraded.
  2. Storage2 -> Storage3

    Map the eDevLUNs created on Storage 2 to Storage 3.

Map the LUNs (including local LUNs and eDevLUNs) that are not masqueraded on Storage 2 to Storage 3.

The Device SN and Device Model of the remote LUNs are those of Storage 2.

Map the LUNs (including local LUNs and eDevLUNs) that are masqueraded on Storage 2 to Storage 3.

The Device SN of the remote LUNs is the SN of Storage 2, but the Device Model is device model of Storage 1.

Translation
Download
Updated: 2018-12-29

Document ID: EDOC1000106155

Views: 56524

Downloads: 143

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