Start a Conversation

Unsolved

This post is more than 5 years old

A

5 Practitioner

 • 

274.2K Posts

1783

February 26th, 2018 08:00

Error in REST request after VPLEX upgrade

Hi,

last week we upgraded one of our VPLEX's GeoSynchrony from version 5.4.1.03.00.04 to version 6.0.1.06.00.03.

after the upgrade one of our monitoring scripts doesn't work anymore with the upgraded VPLEX, but it works fine with the non-upgraded one.

the script issues a REST POST request using curl to get details from the machine.

this is the curl command:

curl -K /root/.curl.cfg -g -d '{"args":"-l /engines/engine-1-1/directors/director-1-1-A/hardware/sfps"}' -X POST https:// /vplex/ls

for some reason, this is the output i receive:

Exception:

  Invalid URI in POST request. Not one among context,command or attribute.

if i run the same command in the non-upgraded VPLEX, i get the desired output:

/engines/engine-1-1/directors/director-1-1-A/hardware/sfps:

Name     Manufacturer  PartNumber        S/N              RxPower[uW]  TxPower[uW]  Temp

-------  ------------  ----------------  ---------------  -----------  -----------  -------

A0-FC00  FINISAR       FTLF8528P2BNV-E5  PNH0S6J          420          474          37

         CORP.

A0-FC01  FINISAR       FTLF8528P2BNV-E5  PNH0E43          589          456          38

         CORP.

A0-FC02  FINISAR       FTLF8528P2BNV-E5  PNG6T9J          463          471          37

         CORP.

A0-FC03  FINISAR       FTLF8528P2BNV-E5  PNH0RD6          464          470          37

         CORP.

A1-FC00  FINISAR       FTLF8528P2BNV-E5  PNH20VD          443          473          32

         CORP.

A1-FC01  FINISAR       FTLF8528P2BNV-E5  PNG6TRF          488          465          34

         CORP.

A1-FC02  FINISAR       FTLF8528P2BNV-E5  PNG6TYQ          555          461          35

         CORP.

A1-FC03  FINISAR       FTLF8528P2BNV-E5  PNH0J2X          604          460          32

         CORP.

A3-FC00  AVAGO         AFBR-57D7APZ-E2   AGL1235A3270807  619          569          35

A3-FC01  AVAGO         AFBR-57D7APZ-E2   AGL1240A3295023  644          563          34

i tried to make some adjustments from another topic - Correct CURL/REST payload data to invalidate cache for a consistency group but to no avail

so now i wanted to ask the help from the masses, 2 (billion) brains are better than 1

any suggestions?

5 Practitioner

 • 

274.2K Posts

February 27th, 2018 02:00

Update 27Feb:

as of GeoSynchrony 6.X there are some deprecated commands.

one of them is "ls", that is why the REST request no longer works on our upgraded VPLEX.

2 Posts

June 19th, 2018 12:00

Not according to the manual. It's not listed in the list of deprecated commands and is listed on page 362 of the CLI Reference Guide for Version 6.

5 Practitioner

 • 

274.2K Posts

June 28th, 2018 19:00

Have got a ask from Customer for the same symptom, "ls" does not work after have upgraded to version 6.0.x;

Found 5.5 release notes with following information:

https://support.emc.com/docu61211_VPLEX-with-GeoSynchrony-5.5-and-Patches-Release-Notes.pdf?language=en_US

===============================================

Deprecation of the "ls" command through the VPLEX REST API

Support for executing the "ls" command through the VPLEX REST API has been deprecated.

The equivalent functionality for retrieving context contents and attributes has been provided through the VPLEX GET context URI method, which returns the data

in a structured format that is more efficiently parsed by clients of the REST API.

Ensure that you convert any existing usage of the "ls" command through the RESTful API to use

the VPLEX GET context URI method to avoid incompatibility.

===============================================

2 Posts

June 29th, 2018 10:00

While I didn't find it in the documentation, I definitely agree the "ls" command is gone in version 6. Came to the same conclusion that REST API GET does the same thing, so have already converted all my code.

The other manuals have examples of using "ls" everywhere, which should probably be removed or changed/updated.

Thanks for finding the documentation that notes the deprecation.

No Events found!

Top