Create Link in Pmax 8500 - version 10.3.0.0- get error 502

[johndanielk]

I need some help, please.

I have a script that has been running fine for many months.

However, after we upgraded Pmax from version 10.2 to 10.3, my script is failing.

Despite the script failing, the link is being created successfully on the Pmax (I can confirm this in the Pmax GUI).

I have already checked the REST API documentation and confirmed that nothing has changed in the API endpoints or structure relevant to the script.

Could you please review my script to help me determine if something is wrong with it, as the link creation seems successful, but the script is reporting a failure?

I am attaching the script for your review.

var srcStorageGrpId = refreshSourceSG;
var tgtStorageGrpId = refreshTargetSG;
var snapId = srcSnapIdRefresh;
var url = "/univmax/restapi/" + apiVer + "/replication/symmetrix/" + encodeURIComponent(symmetrixId) +
          "/storagegroup/" + encodeURIComponent(refreshSourceSG) +
          "/snapshot/" + encodeURIComponent(srcSnapRefresh) +
          "/snapid/" + encodeURIComponent(srcSnapIdRefresh);
System.log("Link URL: " + url);
System.sleep(1000);
var body = {
    "action": "Link",
    "link": {
        "storage_group_name": tgtStorageGrpId
    }
};
var req = pmaxHost.createRequest("PUT", url, JSON.stringify(body));
req.setHeader("Authorization", "Basic " + basicAuth);
req.setHeader("Accept", "application/json");
req.setHeader("Content-Type", "application/json");
var res = req.execute();
var statusCode = res.statusCode;
System.log("Response Status Code: " + statusCode);
if (statusCode == 200) {
    System.log("Snapshot was successfully linked.");
    var responseJson = JSON.parse(res.contentAsString);
    System.log("Link Response to Existing sg: " + JSON.stringify(responseJson, null, 2));
} else {
    var errorException = "Failed to Create link snapshot. Error code: " + statusCode + ". Response: " + res.contentAsString;
    System.log("~~~~ Error: " + errorException + " ~~~");
    throw errorException;
}

this is error I get code 502

storageGroup source: sg_myVMxxx10_REFRESH

storageGroup Target: sg_myVMxxx26_REFRESH

infosrcSnapIdRefresh: 95737447424

infosrcSnapRefresh: snapRef_myVMxxx10_04-12_0712

infoLink URL: /univmax/restapi/103/replication/symmetrix/12345678/storagegroup/sg_myVMxxx10_REFRESH/snapshot/snapRef_myVMxxx10_04-12_0712/snapid/95737447424

Response Status Code: 502

Error: Failed to create link snapshot.

Error code: 502. Response: {"message":"cvc-complex-type.2.4.a:
Invalid content was found starting with element '{[http://www.emc.com/em/2012/07/univmax/restapi/103/replication\](http://www.emc.com/em/2012/07/univmax/restapi/103/replication/):linked_volume_name}'.
One of '{[http://www.emc.com/em/2012/07/univmax/restapi/103/replication\](http://www.emc.com/em/2012/07/univmax/restapi/103/replication/):source_volume_name}' is expected."} ~~~

[rawstorage]

Have you tried the script with another storage group? the errror suggests that there is no source_volume_name being picked up so I suspect your source storage group is empty, if this is still failing you should open an SR to have a look with customer support, I have tested these endoints with PyU4V and REST Client

https://Unisphere:8443/univmax/restapi/103/replication/symmetrix/000120001366/storagegroup/veritas/snapshot/test/snapid/95743511809

{
"action": "Link",
"link": {
"storage_group_name": "vertias_lnk"
}
}

Response Code:
200
Time:
2s 112ms
Response Size:
722.00 Bytes

{
"name": "test",
"snapid": 95743511809,
"timestamp": "09:16:51 Thu, 04 Dec 2025 +0000",
"timestamp_utc": 1764839811000,
"state": [
"Established"
],
"num_source_volumes": 1,
"source_volume": [
{
"name": "00151",
"capacity": 546,
"capacity_gb": 0.99975586
}
],
"num_storage_group_volumes": 1,
"tracks": 0,
"non_shared_tracks": 0,
"time_to_live_expiry_date": "10:16:52 Thu, 04 Dec 2025 +0000",
"expired": false,
"linked": true,
"restored": false,
"linked_storage_group_names": [
"vertias_lnk"
],
"linked_storage_group": [
{
"name": "vertias_lnk",
"source_volume_name": "00151",
"linked_volume_name": "0018A",
"tracks": 0,
"trackSize": 131072,
"percentageCopied": 100,
"linkedCreationTimestamp": "09:17:32 Thu, 04 Dec 2025 +0000",
"defined": true,
"background_define_in_progress": false
}
]
}

[johndanielk]

Hi,
yes , I checked and its works with ohter Storage Group.

That's very strange... The source storage group is not empty (or: are still present). In any case, thank you. I have opened an SR .
If you are interested—once I have a solution, I can post it here.
Thanks

[rawstorage]

Does the source storage group have a link to it or is it in a restored state or anything like that?, the following API call is very useful for identifying all the relationships

https://Unisphere:8443/univmax/restapi/103/replication/symmetrix/000120001366/storagegroup/srcsgname

[johndanielk]

I am in the process of creating the LINK
The link is being made.. but there is a 502 error

Then
I do the same rest api test instead of a put command I put a get command
And I get the same 502 error message

In my opinion, as you said - this is a specific problem with this SG
Although nothing has changed - only the PMAX upgrade
source storage group name "sg_myVMxxx10_REFRESH" is link to the "sg_myVMxxx26_REFRESH" (target)
so , its replace the all data in on the volumes

the storage group name build like this
main Storage Group name - like "sg_xxx01"
and under this main SG have the "sg_myVMxxx10_REFRESH"

the same build on target Storage Group

about this command
https://unisphere:8443/univmax/restapi/103/replication/symmetrix/000120001366/storagegroup/srcsgname
I will check and compare it

[johndanielk]

hi
updates...
this is the report I get on both SG

from SG - "sg_myVMxxx26_REFRESH"

{
  "name": "sg_myVMxxx26_REFRESH",
  "symmetrixId": "1111111111",
  "parentName": "sg_Gold01_DC_myVMxxx26",
  "numDevicesNonGk": 12,
  "capacityGB": 121857,
  "numSnapVXSnapshots": 1,
  "snapVXSnapshots": [
    "Snap_myVMxxx26_07-12_0703"
  ],
  "rdf": false,
  "isLinkTarget": false
}

from SG - "sg_myVMxxx10_REFRESH"

 {
  "name": "sg_myVMxxx10_REFRESH",
  "symmetrixId": "1111111111",
  "parentName": "sg_Silver_BI",
  "numDevicesNonGk": 12,
  "capacityGB": 121857,
  "numSnapVXSnapshots": 5,
  "snapVXSnapshots": [
    "1-Daily004",
    "onePerHour",
    "snapRef_myVMxxx10_07-12_0703"
  ],
  "rdf": true,
  "isLinkTarget": false,
  "snapshot_policies": [
    "1-Daily004",
    "onePerHour"
  ],
  "rdf_groups": [
    16
  ],
  "snapshot_policies_associations": [
    {
      "policy_name": "1-Daily004",
      "directly_associated": false,
      "sg_suspended": false,
      "policy_suspended": false
    },
    {
      "policy_name": "onePerHour",
      "directly_associated": false,
      "sg_suspended": false,
      "policy_suspended": false
    }
  ]
}

Thanks

[johndanielk]

update ....
(Currently checking with support.)
We managed to recreate the issue and it seems that it's related to having more than one child storage group.
So, since the upgrade from 10.2 to 10.3, having more than one child storage group under a parent is causing Error 502 when running a put/get/etc. command
If there's only one child SG under a parent, the command works successfully.

Thanks

[johndanielk]

Another update from support
They did a lab test, and it turned out to be correct - and saw the problem as I described

In short, they are working on fixing the problem
I will continue to update

Thanks