Logical unit settings for the Hitachi TagmaStore AMS 2000 family of systems

Logical unit (LU) settings apply to individual LUs that are configured in the Hitachi TagmaStore AMS 2000 family of systems.

You must configure the systems LUs as described in Table 1 if the logical unit number (LUN) is associated with ports in a switch zone that is accessible to the Lenovo Storage V7000clustered system.

Table 1. Hitachi TagmaStore AMS 2000 family of systems LU settings for the Lenovo Storage V7000
Option	Default setting	Lenovo Storage V7000 required setting
LUN management information
Security	Off	Off Note: LUN Security enables LUN masking by the worldwide node name (WWNN) of the initiator port. This function is not supported for logical units (LUs) that are used by Lenovo Storage V7000 systems.
LU mapping	One-to-one	One-to-one
LAN management options
Maintenance port IP address automatic change mode	Off	Off
IPv4 DHCP	Off	Off
IPv6 address setting mode	Auto	Auto
Negotiation	Auto	Auto

Note: These settings only apply to LUs that are accessible by the Lenovo Storage V7000 system.

Data corruption scenarios to avoid

Scenario 1: The configuration application enables you to change the serial number for an LU. Changing the serial number also changes the unique user identifier (UID) for the LU. Because the serial number is also used to determine the WWPN of the controller ports, two LUNs cannot have the same unique ID on the same SAN because two controllers cannot have the same WWPN on the same SAN.

Scenario 2: The serial number is also used to determine the WWPN of the controller ports. Therefore, two LUNs must not have the same ID on the same SAN because this results in two controllers having the same WWPN on the same SAN. This is not a valid configuration.

Attention: Do not change the serial number for an LU that is managed by a Lenovo Storage V7000 system because this can result in data loss or undetected data corruption.

Scenario 3: The configuration application enables you to create LUN A, delete LUN A, and create LUN B with the same unique ID as LUN A. If the LUN is managed by a Lenovo Storage V7000 system, this scenario can cause data corruption because the system might not recognize that LUN B is different than LUN A.