Hi Steve,
Thanks for sharing the import. For the future, if planning/execution points are involved it might be better to attach a backup, which would include the cache and allow mimicking your environment
and trying to plan the flow.
Also, it would be most helpful if you can share what you tried changing from previous iteration so we could know what worked and what didn't.
Now, for what I saw at "Clone environment 3/7" (Hopefully that's the one you are working on:
1) Name of variables - These should be alphanumeric only. Consider these as variable names as container with multiple attribute that would be fed to a command.
Looking at the name for the lunmap object - It should note include "/" of any kind.
2) In the "other parameters" tab of the same command you are expected to plug in an igroup name. I see there "devtest_igroup" which looks like a variable for igroup.
This variable is not defined and has no value. You need to get that value from somewhere, either by searching or defining it. For that you can use a No-Op command:
This command does nothing but defines a variable based on specific info (If you know which igroup) or based on using a finder.
Here's an example:
I am defining an array object, based on your constant string
and then, in the same command defining "devtest_igroup"
Obviously, the Map Lun command requires "devtest_igroup.name"
Alternatively, if you know exactly what's the name you need you can plug it there directly.
An alternate route would have been not to define array1, but to use that object from "ParentVolume1.aggregate.array"
Let me know if that helps.
Best,
Yaron Haimsohn
