Get error code 497 when attempting to upload

Thanks for your response.

The MD5 checksum verifies as correct.

That's the message I get.

I've tried uploading several times - with the same results. I've also downloaded the upgrade file to different PCs and then uploading from there - the results are always the same. What I haven't tried yet (and am in the process of trying) is downloading to a Linux box and then uploading from there. I doubt that it will make a difference, but stranger things have happened.

Error code 497 should have presented the following error string in the UI:

• The system was unable to process the update candidate. The candidate may be corrupted; download a new update candidate. Be sure that the peer Storage Processor is operating properly and not in Service Mode, then upload the update candidate again. If this does not resolve the problem, record the error code and refer to the Product Support Page for support options. (Error Code: 497)

Since the MD5 checksum is correct on the client system where you are uploading to the VNXe from and running Unisphere that suggests the upgrade file is getting corrupted during upload. Have you tried to re-upload the file? Do you get error code 497 every time?

Thanks,
Andrew

I checked with EMC Technical Support and understand they have been in contact with you and the download and upgrade has now successfully taken place.

I just wanted to confirm.

Thanks,

Andrew

Hi all,

has this issue been resolved?!? If so how?

We have the very same problem, with the only difference that we've successfully managed to patch the VNXe 3100 with sp 2.2.0.17142 few months ago.

Now we're experiencing problems (Error Code 497) with latest patch: MR2 SP0.1 - 2.2.0.17384

[We need it in order to get support for Microsoft Win 2k8R2 Server clustering, SCSI-3 & Persistent Reservation related commands.]

Thanks,

Amadeo

I have the same problem.  downloaded it several times and tried uploading several times.  Still the same error 497.

After restarting both Storage Processors, we finally managed to bypass this error, by powering off whole system... yes this means some downtime is required...

Well that stinks!  I'm waiting for next major update.  It seems that I never have a smooth firmware update.

I have to deal with this issue today.I checked the back end and the main partition was mostly full. The root filesystem must have 32% free space and /nbsnas filesystem must have 40%.

you can run this command df -h on the VNXe Command line and if you see the main partition is over 69% you might probably have to reimage the processor or sometimes both processors. This below is an example where you might not have enough space.

service@spa spa:~> df -h

Filesystem            Size  Used Avail Use% Mounted on

/dev/sda2             5.0G  3.4G  1.4G  73% /

tmpfs                 917M  2.9M  914M   1% /dev/shm

udev                  469M  904K  468M   1% /dev

/dev/sda4             4.1G  539M  3.4G  14% /cores

/dev/tmpfs             32M   13M   20M  40% /tmp

/dev/mirrora4          17G  1.1G   15G   7% /EMC/backend/service

/dev/c4nasdba2       1019M   32M  937M   4% /EMC/backend/CEM

/dev/c4nasdba1       1015M   39M  926M   5% /nbsnas

/dev/c4loga2          653M   28M  592M   5% /EMC/backend/perf_stats

/dev/c4loga1          3.4G  195M  3.0G   6% /EMC/backend/log_shared

These options are available from Unisphere under VNXe>Settings>Service System

If a Reimage is needed, you need to select the processors you are Reimaging from Unisphere, set the SP in service mode> so it needs to reboot and be placed in service mode, once in service mode you can reimage, the process to complete can take up to 20 minutes.Reimagewillclear up any space issues and errors  or logs no needed.

Note: To see the Reimage option you need to select the Storage Processor, be sure not to get confused with Reinitialize which will set the system to factory default.