The proper order of steps to configure ESRS on a v8.1+ cluster: 1.Install and configure the SecureConnect-GW V5.1 at the correct customer site. If the SCG is up and running, proceed to Step 2 below.2.OneFS license serial needs to be created in the DELL EMC install base against the correct Site ID by doing ONE of the following steps: The customer could do this by downloading a Licensing file from the cluster and uploading to the eLicensing. If PS has done this for the customer, make sure the customer obtains a copy of the Email from the SLC. If the customer or PS does this AFTER setting up the SCG, the license should be automatically linked in the IB. If the customer licensing was done BEFORE the SCG was set up, then the SWID might not be fully linked. If this is the case, open a ticket with IBGroup to have the OneFS serial created manually against the correct site ID. The OneFS "serial" (or license aka SWID) can be found with the following CLI command: mycluster-1# isi license listOneFS License ID: ELMISL091xxxC3Valid Signature: Yes 3. Execute the cli # isi esrs modify --enabled=true --username="registered for site-id: name[NAME]-domain) --password=xyz Note: the command comes back without any message. 4. Go to the SCG GUI and check for the isilon devices. In my case they didn't show until a restart of the SCG itself  
Isilon OneFS 9.2.1.8 OneFS License ID:   srvisirz-1# isi esrs modify --enabled=true --username=dell-partner[NAME].net --password=(xyz)Internal error: ESRSError: ESRS Add Device failed. Response JSON was: { {'http_response_code': 201, u'responseCode': 400, u'serialNumber': u'ELMISL1121PNMV', u'gatewaySerialNumber': u'ELMAPL05222BLZ', u'veType': u'Connected', u'message': u'Device match not found for input device with Serial Number ELMISL1121PNMV and ISILON-GW', u'model': u'ISILON-GW', 'curl_trace': "* Trying 172.30.11.93:9443...\n* Name '172.30.253.24' family 2 resolved to '172.30.253.24' family 2\n* Local port: 0\n* Connected to 172.30.11.93 (172.30.11.93) port 9443 (#0)\n* ALPN, offering http/1.1\n* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:[NAME]\n* successfully set certificate verify locations:\n* CAfile: none\n* CApath: /etc/ssl/certs/\n* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384\n* ALPN, server accepted to use http/1.1\n* Server certificate:\n* subject: C=US; ST=MA; L=SO; O=EMC; OU=ESRS; CN=srvscg01\n* start date: May 4 11:26:40 2022 GMT\n* expire date: May 4 11:26:40 2042 GMT\n* issuer: C=US; ST=MA; L=SO; O=EMC; OU=ESRS; CN=srvscg01\n* SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.\n> POST /esrs/v1/devices/ISILON-GW/ELMISL1121PNMV HTTP/1.1\r\nHost: 172.30.11.93:9443\r\nUser-Agent: PycURL/7.43.0 libcurl/7.79.1 OpenSSL/1.0.2z-fips zlib/1.2.11\r\nAccept: */*\r\nContent-Type: application/json\r\nAccept-Type: application/json\r\nAuthorization:dell-partner[NAME].net:XjtjqJEaK1hyaI18uvVM\r\nContent-Length: 30\r\n\r\n* Mark bundle as not supporting multiuse\n< HTTP/1.1 201 \r\n< Date: Tue, 10 May 2022 13:25:09 GMT\r\n< Server: Apache\r\n< Strict-Transport-Security: max-age=31536000; includeSubDomains;\r\n< Content-Type: application/json\r\n< Content-Security-Policy: frame-ancestors 'self'\r\n< Transfer-Encoding: chunked\r\n< \r\n* Connection #0 to host 172.30.11.93 left intact\n"}}.   Question: Is it possible that the Customers installbase is missing the isilon's ELM?   The SCG has been setup after the isilon implementation with licensed fatures.    Any ideas out here? 
Adding isilon / powerscale to SCG failed: internal error http_response_code: 
201 u'responseCode: 400