Upgrading ESA C100V appliance

[cisco]

Hi,

We are trying to uprade our ESA to build 106.

And we still get the following error:

The following errors occurred during upgrade:

Download error: http://updates.ironport.com/asyncos/phoebe-8-5-6-106/hints/default/1

Upgrade exited without success.

Please attempt the upgrade again after clearing the error.

I have cleared the error for several times, but it still exists.

In the log directory i saw the following error:

DownloadError url=http://updates.ironport.com/asyncos/phoebe-8-5-6-106/hints/default/1 reason=>

But there was no reason mentioned.

I checked the DNS and everything seems to be allright.

How can i solve this issue?

Regards,

Ronald Pastoor

[Robert Sherwin]

Do you have a proxy in place?  Is appliance in cluster with hardware appliances?

Also - can you assure that you are pointing to update-manifest.sco.cisco.com:443 for your updateconfig settings?

http://www.cisco.com/c/en/us/support/docs/security/email-security-appliance/118065-maintainandoperate-esa-00.html

-Robert

[Marijo Bartakovic]

Hi Robert,

we have the same issue with our C100V. We pointed the appliance already to the manifest mentiones above.

Could you please add our VLNESA too?

VLN: VLNESA113066

Thanks,

Marijo

[Robert Sherwin]

I'll add in on provisioning.  Typically - we would like to have a support case opened and the provisioning request submitted formally.  I will have this done, and you should see here in about 1 hour to the manifest.

-Robert

[neb-ITOps]

My C100V is still on 8.5.6-092 - when I try to check for upgrades it says 'no available upgrades'.

updateconfig/dynamichost config is correct on my virtual... maybe the update is still rolling out to appliances?

[Robert Sherwin]

What is your VLNESA.  Can check backend to make sure provisioning is correct.

-Robert

[neb-ITOps]

Hi Robert - thanks for your help.

VLNESA is: VLNESA33022106

Tried to raise a support ticket today from the vESA but the serial number couldn't be found in the system so the support agent had to raise a ticket manually - unsure why as we have valid licenses and support contract on our physical.

[Robert Sherwin]

Went through and manually provisioned.  Should hopefully see this to the manifests within about 1 hour.

-Robert

[neb-ITOps]

Nice one! Do I still need to get customer service to link the vESA with the physical contract ID (so I can raise tickets from the virtual appliance)?

[Robert Sherwin]

Sadly, that is still an issue we are battling with, and are hopefully getting close to solving.  

For those - we ask that you request to bypass entitlement and have the case sent straight into TAC with your listed VLNESA #, or, open with a hardware SN.

Once we have this issue resolved for opening support cases tied to the virtual (VLNESA, VLNWSA, VLNSMA), I will have it advertised on forums.  We do apologize for this inconvenience.

[neb-ITOps]

Thank you Robert - I thought it was something I was doing wrong.

Last question for you - I upgraded our IronPort to 9.0 (thanks to you provisioning it) but cannot see an upgrade to 9.1 even though the upgrade path says we should be able to.

How can I upgrade from 9.0 to 9.1?

[Robert Sherwin]

Added that just now as well - you should see on the appliance shortly.

-Robert

[neb-ITOps]

Thanks Rob - on 9.1 now and it's running great.