3PAR: Volume Attachment Failed with FC

[Vivek Soni]

3PAR: Volume Attachment Failed with FC

with the port persistent feature enabled on 3par, the volume attachment failed with below error:

 _http_log_resp /usr/lib/python2.7/site-packages/hpe3parclient/http.py:181
2018-02-06 12:09:37.251 963999 DEBUG cinder.volume.drivers.hpe.hpe_3par_fc [req-31eab641-baec-4760-b8be-0bc23c64e9d9 07330a460401434bb02fed5acb0e3d3c 1b6c62dd0a6a4f7c8917304292298cb0 - default default] <== decorator: exception (3731ms) KeyError('remoteName',) trace_logging_wrapper /usr/lib/python2.7/site-packages/cinder/utils.py:901
2018-02-06 12:09:37.252 963999 ERROR cinder.volume.manager [req-31eab641-baec-4760-b8be-0bc23c64e9d9 07330a460401434bb02fed5acb0e3d3c 1b6c62dd0a6a4f7c8917304292298cb0 - default default] Driver initialize connection failed (error: 'remoteName').
2018-02-06 12:09:37.252 963999 ERROR cinder.volume.manager Traceback (most recent call last):
2018-02-06 12:09:37.252 963999 ERROR cinder.volume.manager File "/usr/lib/python2.7/site-packages/cinder/volume/manager.py", line 1429, in initialize_connection
2018-02-06 12:09:37.252 963999 ERROR cinder.volume.manager conn_info = self.driver.initialize_connection(volume, connector)
2018-02-06 12:09:37.252 963999 ERROR cinder.volume.manager File "/usr/lib/python2.7/site-packages/cinder/utils.py", line 895, in trace_logging_wrapper
2018-02-06 12:09:37.252 963999 ERROR cinder.volume.manager result = f(*args, **kwargs)
2018-02-06 12:09:37.252 963999 ERROR cinder.volume.manager File "/usr/lib/python2.7/site-packages/cinder/zonemanager/utils.py", line 81, in decorator
2018-02-06 12:09:37.252 963999 ERROR cinder.volume.manager conn_info = initialize_connection(self, *args, **kwargs)
2018-02-06 12:09:37.252 963999 ERROR cinder.volume.manager File "/usr/lib/python2.7/site-packages/cinder/volume/drivers/hpe/hpe_3par_fc.py", line 340, in initialize_connection
2018-02-06 12:09:37.252 963999 ERROR cinder.volume.manager if vlun['remoteName'] in init_targ_map:
2018-02-06 12:09:37.252 963999 ERROR cinder.volume.manager KeyError: 'remoteName'
2018-02-06 12:09:37.252 963999 ERROR cinder.volume.manager
2018-02-06 12:09:37.254 963999 ERROR oslo_messaging.rpc.server [req-31eab641-baec-4760-b8be-0bc23c64e9d9 07330a460401434bb02fed5acb0e3d3c 1b6c62dd0a6a4f7c8917304292298cb0 - default default] Exception during message handling

Analysis:
-----------------
After doing some analysis on it, we pointed out "21:41:00:02:AC:01:E1:66" entry was missing.

[Vivek Soni (viveksoni)]

Hi Nitin/Sushant,

After adding this wwn entry in zone, to check whether the issue still occur or not, i request you to perform the same steps again and provide us with c-vol log to check whether the issue still occurs or not

[Vivek Soni (viveksoni)]

Hi Nitin/Sushant,

Please verify and ensure whether the setup is having below mentioned rules set for Port Persistence

The following configuration requirements and limitations apply when using persistent ports for port-level failover:
1) The host port must be connected and zoned through fabric topology to an HPE 3PAR StoreServ Storage system physical port.
2) The automatically designated partner port must be connected to the same fabric as its partner port on the same switch.
3) The partner port does not have to be zoned to the host port.
4) Under normal conditions, a host port has a single I/O path to the storage array available.
5) If a partner port is zoned to the same host port as the primary port, the host port has two I/O paths to the storage array available.
6) Host-facing adapters on 3PAR storage systems used in the configuration must support NPIV.
7) FC adapters on hosts used in this configuration do not require NPIV support.
8) Port failover is only supported on target mode point-to-point port configurations.

Persistent port failover is only supported on the following NPIV-compliant HBAs:
1) HPE 3PAR two-port 4G FC
2) Emulex two-port 4G
3) Emulex four-port 8G FC

[Vivek Soni (viveksoni)]

As per the latest updates, after adding the missing 'wwn' in the zone, the attachment was successful