We're trying to find a method to update an appliance to a specific version and not the one which is available through yum or GUI.
Accordingly to the KB the only they are the only two methods.
But this is a problem for us, as we're qualifiying one specific version, them deploy this version in production.
The problems are :
- if a new version goes out between our qualification tests (which can take up to a month or two) we can't update the production with the version we qualified
- the appliance needs to have a direct access to Internet to be able to update (some of our appliance does not have a direct access...).
Is there a place where we can find the binary files (like .rpm packages) ?
If not, how can we grab them using yum and then deploy them on another appliance ?
ThanksCe message a été modifié par: jtyt on 20/08/12 05:04:12 CDT
I can comment on Supports view point of this, but it does work.
If you look in
on your appliance you can finde the addresses that the RPM's are fetched from. There are tools avalible to download the contents of repos (or you can write your own fairly easily) and you would then just need to change the mlos.repo (or idealy disable that and make your own repo file) and update from a local server that way.
With regard to servers not ahving direct internet access, you can make them update through a proxy server.
This is what I've found :
- yum --showduplicates list mwg-release : show all the releases for a specific package
[root@DI-444440-AVMC-1-PV4-2 yum.repos.d]# yum --showduplicateslist mwg-release
Loaded plugins: changelog, fastestmirror
Loading mirror speeds from cached hostfile
* mlos-Ti-base: appliance2.webwasher.com
* mlos-Ti-mwg: appliance2.webwasher.com
* mlos-Ti-updates: appliance2.webwasher.com
* mlos-current-base: appliance2.webwasher.com
* mlos-current-mwg: appliance2.webwasher.com
* mlos-current-updates: appliance2.webwasher.com
mwg-release.noarch 18.104.22.168.0-13253 installed
mwg-release.noarch 7.2.0-13081 mlos-Ti-mwg
mwg-release.noarch 7.2.0-13081 mlos-current-mwg
mwg-release.noarch 22.214.171.124.0-13253 mlos-Ti-mwg
mwg-release.noarch 126.96.36.199.0-13253 mlos-current-mwg
mwg-release.noarch 188.8.131.52.0-13603 mlos-Ti-mwg
mwg-release.noarch 184.108.40.206.0-13603 mlos-current-mwg
- yum install mwg-release-[version].noarch : to install a specific version of a package where version is found if the previous list (ex: 220.127.116.11.0-13253)
This should be done for (at least) every package beginning by "mwg-" (ie : mwg.x86_64, mwg-config.x86_64, mwg-release.noarch, mwg-ui.noarch).
The packages can be manually downloaded from http://appliance.webwasher.com/mwg/current/mwg/x86_64/
You can donwnload the iso images from the Webwasher Extranet (https://contentsecurity.mcafee.com/software_mwg7_download)
I have some WebGateways with no internet access too.
My installation guide is this:
2) export http_proxy
3) yum install yumconf-7.2.0-mwg
4) yum upgrade yum yumconf\*
5) yum upgrade
To check the version on command line:
I was trying to upgrade via YUM over a proxy, but it doesn't work because our MWGs are using internal nameservers that do not resolve publich domain names. Is there anything else we can do?
before making things complicated I recommend to add appliance.webwasher.com and appliance2.webwasher.com to /etc/hosts, run the update and remove the entries afterwards.
How to upgrade to 18.104.22.168
Florian Hallasthank you!
But i used other sintax and other steps
2) export http_proxy
4) yum upgrade
As per notes on Best practices to upgrade
Upgrading with this repository will always take you to the latest release in the Main Branch. Make sure you know the most current release within the Main repository before upgrading.
It's not clear in the URL above how to upgrade to a specific version