AppSync 1.6.0 no longer sees VNX5500 after OE upgrade to .215.

Hi Folks,

Can anyone shed any light on this?

I started with a working environment - VNX5500 running 5.32.000.5.201 and AppSync 1.6.0.0.  Protecting a SQL data volume on a VNX LUN using VNX Snaps.  The Service Plan has been executing fine for a while.  After upgrading the VNX to 5.32.000.5.215, the Service Plan now fails, saying it "failed to set active path" on the VNX, and complaining of invalid credentials, and calling out the IP address of SP-B.  However, I can point a browser at that SP IP and log in to Unisphere successfully with the AppSync credentials.  I can also ping the SP IP successfully from the AppSync VM.

In AppSync, I tried to rediscover the VNX - it failed with invalid credentials.  I re-entered the proper credentials and it still failed.  I then tried to remove and re-add the VNX.  Removal fails due to existing VNX Snaps.  I expired the Snaps from AppSync, but they still remained in Unisphere.  I then deleted them from Unisphere.  Trying to remove the VNX from AppSync still fails due to the presence of existing Snaps, which of course no longer exist.

BTW, AppSync is still connected to the RPAs, and executes RP Service Plans successfully on the same SQL server. (Different volume, but same AppSync plug-in instance.)  Also, the VNX is otherwise fully connected and functional post-upgrade with 2 RPAs, an ESX cluster, and 2 Windows servers.

So two things seem to be amiss on the AppSync side of things: 1) Connection failure with the VNX, and 2) Deleted Snaps that AppSync still believes are present.  Again, the only change between the working and non-working states was the VNX code upgrade.

Any ideas?

Thanks!

Gordon