Cisco has multiple alias types. There is a friendly name in the DCNM gui, that is not on the switches, there is a fcalias that is tied to the VSAN, and there can also be a device-alias that spans VSANs. Admins who use DCNM can achieve human readable zoning via the GUI but the config on the switch still be wwn based zoning.
Cisco does have an Smart Zone method, but that is not what was documented above. It is similar to Brocades it's similar to Brocade's Target driven peer zoning, in a sense that the zone has ports marked as targets, and ports marked as initiators, and the switch auto-resolves this to apply a single target-single initiator relationship, not allowing initiators to see other.
PaulC - I recommend getting some professional services to help you sort this out, and get you on track. HPE, and most VARs, have consultants that can help with both the 3PAR and the switches. Fibre Channel switching is robust and low latency, but it's also complex. Mistakes can easily lead to outages when you don't 2 redundant fabrics as a starting point, and not following best practices.
I believe your fabric needs some redesign too, top of mind is that you are using VSAN2 on both switches. This puts you at high risk of an accidental zone-merge if anyone accidentally runs a cable from switch 1 to switch 2, and will cause some headaches cleaning that up.
https://www.cisco.com/c/en/us/support/d ... tches.html