Symptom
When one of the following zoning configuration commands fail, it is logged in the accounting log as successful.
zone rename
zoneset rename
zone clone
zoneset clone
zone convert
For Example:
MDS(config)# zone rename nonexist new vsan 200
Rename requested for a non existing zone
MDS(config)# show accounting log
Sun Apr 30 12:42:19 2017:type=update:id=slot-5@pts/0:user=admin:cmd=configure terminal ; zone rename nonexist new vsan 200 (SUCCESS)
Conditions
Applies to all MDS platforms and all releases.
The current zone or zoneset that is being cloned, renamed or converted does not exist or there may be a zone lock in place.
Workaround
Verify the commands succeeded using show zone or show zoneset commands.
there is an additional info logged by zone in accounting log. i.e. something like "zone is cloned". if that message is present, that means zone clone is successful", else it is failure.
Further Problem Description
Problem is with both basic and enhanced zoning.
Resolution Summary
The proper return result is logged in the accounting log.
For Example:
(config)# zoneset rename shdfsfs sdjdsfs vsan 1
Rename requested for a non existing zoneset
(config)# show accounting log | tail
Mon May 15 20:01:11 2017:type=update:id=console0:user=root:cmd=configure (SUCCESS)
Mon May 15 20:01:19 2017:type=update:id=console0:user=root:cmd=configure terminal ; zoneset rename shdfsfs sdjdsfs vsan 1 (FAILURE)
