How to configure SmartSAN/TDPZ and Persistent Ports

[jwe]

Hi,

I'm trying to move a 3PAR 8200 to SmartSAN.
According to the "HPE Smart SAN for 3PAR 2.0 User Guide, page 57" the createhost-command is used to create TDPZ zones for each persistent port pair.
This is required to make persistent port work as expected when only TDPZ is used.

After creating this host with one persistent port pair, this host is not connected to any port according to "showhost":
showhost PP_x02
Id Name Persona -WWN/iSCSI_Name- Port
4 PP_x02 Generic-ALUA 20020002AC01FF98 ---
                      21020002AC01FF98 ---
--------------------------------------------
2 total

As a result this host shows up as "degraded" in the SSMC:
State: Degraded
State description: Path is not connected to a port

The two TDPZ zones have been created as expected:
showportdev tzone 0:0:2

Zone Name: tdz3par_20020002ac01ff98_00
Zone Entry Count: 1
Zone State: up_to_date
Principal Member: 20020002AC01FF98
Number ----Port_WWN---- -Alias_Name-
1        21020002AC01FF98

showportdev tzone 1:0:2

Zone Name: tdz3par_21020002ac01ff98_00
Zone Entry Count: 1
Zone State: up_to_date
Principal Member: 21020002AC01FF98
Number ----Port_WWN---- -Alias_Name-
1        20020002AC01FF98

How do I get rid of the degraded state of the configured host?
What is the recommended way to configure zoning for these persistent port pairs in a Smart SAN environment?

regards
Joerg

[support_s]

System recommended content:

1. HPE SAN Design Reference Guide | Zoning with 3PAR persistent ports

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[sbhat09]

Hello @jwe,

The procedure says 'the Native and Guest ports should be in the same zone'. But in this command output, if my observation is right, the ports 0:0:2 and 1:0:2 look like in the different zones ( Zone names '2002... and 2102...)

Can you please confirm that and share the representative diagram of your implementation plan?

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of the company.

[jwe]

Hi @sbhat09 ,

the tdpz zones where created with the command "createhost -port 0:0:2,1:0:2 PP_x02 20020002AC01FF98 21020002AC01FF98".

Quote from SmartSAN UG: "This command results in two Smart SAN TDPZ zones. In one zone, one of the ports is considered to be the principal port
and the partner port a peer member of the TDPZ zone; in the other zone, those port roles are reversed."

If I read the output of "showportdev tzone" correctly, two zones have been created:
First zone "tdz3par_2002..." with port 0:0:2 as the principal member and port 1:0:2 as a partner member.
In the second zone "tdz3par_2102..." the port roles are reversed.

showportdev tzone 0:0:2

Zone Name: tdz3par_20020002ac01ff98_00
Zone Entry Count: 1
Zone State: up_to_date
Principal Member: 20020002AC01FF98
Number ----Port_WWN---- -Alias_Name-
1 21020002AC01FF98

showportdev tzone 1:0:2

Zone Name: tdz3par_21020002ac01ff98_00
Zone Entry Count: 1
Zone State: up_to_date
Principal Member: 21020002AC01FF98
Number ----Port_WWN---- -Alias_Name-
1 20020002AC01FF98

The even ports of the 3PAR are connected to FabricA and the odd ports to FabricB. So the above ports 0:0:2 and 1:0:2 are connected to the same FC-switch.

So both ports should be connected via TDPZ zone. But is 3PAR port zoned like this considered as a "host port" by the system? 

regards
Joerg

[sbhat09 · Accepted solution]

Hello @jwe,

Are you sure there was no 'degraded' error before creating tdpz zones?

If that is not the suspect, it requires detailed log analysis to find the cause or it may be a bug as well. Involving HPE support will be more appropriate. Please initiate insplore logs immediately.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of the company.

[jwe]

Will contact HPE Support to fix this issue.
Regards