|Article Number: 503237||Article Version: 3||Article Type: Break Fix|
ViPR Family,ViPR Controller Controller 3.6 SP1,ViPR Controller
The user/system is unable to add volumes to an existing cluster after upgrading to ViPR Controller 188.8.131.52.x. The error message is shown below:
vipr3 xxxxx.xxx.xxx.org controllersvc 2017-08-09 19:05:23,125 [5182|zoneExportAddVolumes|a35640a9-ce7b-4001-9c41-6ed8747880bae2693f19-1667-4704-a323-3e776aff57d1] INFO WorkflowService.java (line 652) Updating workflow step: a35640a9-ce7b-4001-9c41-6ed8747880bae2693f19-1667-4704-a323-3e776aff57d1 state ERROR : Failed to create zones for export group because of: Encountered an error while adding zones: An active zone with the same name but different members exists. Zone <user zone name> must have been either manually created or modified. Please undo any manual changes.
ViPR Controller 184.108.40.206.x has a code issue that prevents zone exports since it does not process Cisco device-aliases properly.
The issue was caused as a side effect of a bug fix that involved setting the alias type for a zone member to enable listing the zone member alias names. This impacted logic that gets executed during provisioning and zoning, which looks in to the zone members and alias types to determine the equivalence between the zones.
The Release Notes for version 220.127.116.11 further describes the issue as follows:
SAN-Cisco Original issue:
Export group updates fail for alias-based zones. When you perform an export to a host and then try to perform path adjustment or export more volumes to the same host, the updates/export fail with:
Encountered an error while adding zones: An active zone with the same name but different members exists.
This issue has been resolved in 18.104.22.168
The Release Notes for 22.214.171.124 are available at the following URL:
Upgraded to ViPR Controller version 126.96.36.199.x
A fix for the issue is available in ViPR Controller version 188.8.131.52.197 or higher.
Prior to 184.108.40.206.197, one workaround is to remove all Cicso pwwn device-aliases from the Cisco networks/switches used in ViPR Controller. This workaround must be discussed with the customer's network team prior to application.
Another workaround, only for environments that DO NOT have VPLEX in the ViPR Controller data path, is to set the following variable in the ViPR Controller GUI:
Physical > Controller Config > SAN Zoning > Enable Zoning On Export Add Volume (dropdown menu) > Scope Type > Global > Scope Value > Default > Value > False