It is recommended to keep both Oracle VM Manager and VM Server on same version. So here I’m going to upgrade Oracle VM Server to 3.3.5 from 3.3.3 version in command line interface.
Step 1: Create the Yum Repositories using installation media
[root@mgmtsrv ~]# cd /var/www/html/
[root@mgmtsrv html]# mount -t iso9660 /dev/sr0 /mnt/
mount: block device /dev/sr0 is write-protected, mounting read-only
[root@mgmtsrv html]# cp -rp /mnt/* ovs3.3.5/
Step 2: Login in to Oracle VM Manager as admin user
[root@mgmtsrv ~]# ssh -l admin ovm.lab.local -p 10000
admin@ovm.lab.local's password:
OVM>
Step 3: Create VM Manager Server Update Repository
OVM> create ServerUpdateRepository repositoryName=NewRepository3.3.5 url=http://mgmtsrv.lab.local/ovs3.3.5 enabled=Yes pkgSignatureType=GPG pkgSignatureKey=http://mgmtsrv.lab.local/ovs3.3.5/RPM-GPG-KEY name=MyOVSRepo on ServerUpdateGroup id=GlobalX86ServerUpdateConfiguration
Command: create ServerUpdateRepository repositoryName=NewRepository3.3.5 url=http://mgmtsrv.lab.local/ovs3.3.5 enabled=Yes pkgSignatureType=GPG pkgSignatureKey=http://mgmtsrv.lab.local/ovs3.3.5/RPM-GPG-KEY name=MyOVSRepo on ServerUpdateGroup id=GlobalX86ServerUpdateConfiguration
Status: Success
Time: 2017-12-19 06:30:05,854 EST
JobId: 1513682997560
Data:
id:0004fb000031000014f76b016ce471a4 name:MyOVSRepo
OVM> list ServerUpdateRepository
Command: list ServerUpdateRepository
Status: Success
Time: 2017-12-19 06:31:55,639 EST
Data:
id:0004fb000031000014f76b016ce471a4 name:MyOVSRepo
OVM> show ServerUpdateRepository name=MyOVSRepo
Command: show ServerUpdateRepository name=MyOVSRepo
Status: Success
Time: 2017-12-19 06:33:06,074 EST
Data:
Server Update Group = GlobalX86ServerUpdateConfiguration [GlobalX86ServerUpdateConfiguration]
Repository Name = NewRepository3.3.5
Url = http://mgmtsrv.lab.local/ovs3.3.5
Enabled = Yes
Package Signature Type = GPG
Package Signature Key = http://mgmtsrv.lab.local/ovs3.3.5/RPM-GPG-KEY
Id = 0004fb000031000014f76b016ce471a4 [MyOVSRepo]
Name = MyOVSRepo
Locked = false
Step 4: Put Oracle VM Server in to Maintenance Mode
This is step is not needed because when you execute the Step 5 command will place your Oracle VM Server into maintenance mode, checks for any updates in the server update repository, installs any updates, restarts the Oracle VM Server, then takes it out of maintenance mode and returns it to the server pool as a fully functioning member of the pool. But however it is a good practice if we manually put the server in maintenance mode before doing any server related activity.
OVM> setMaintenanceMode Server name=ovs01.lab.local mode=on
Command: setMaintenanceMode Server name=ovs01.lab.local mode=on
Status: Success
Time: 2017-12-19 06:34:22,205 EST
JobId: 1513683001804
Step 5: Upgrade Oracle VM Server
OVM> upgrade Server name=ovs01.lab.local
Command: upgrade Server name=ovs01.lab.local
Status: Success
Time: 2017-12-19 06:46:24,619 EST
JobId: 1513683310258
Step 6: Take out the server from Maintenance Mode
We need to take out the server from maintenance mode, Since we did manually in Step 4.
OVM> setMaintenanceMode Server name=ovs01.lab.local mode=off
Command: setMaintenanceMode Server name=ovs01.lab.local mode=off
Status: Success
Time: 2017-12-19 06:51:54,977 EST
JobId: 1513684314777
Step 7: Delete Server Update Repository
OVM> delete ServerUpdateRepository name=MyOVSRepo
Command: delete ServerUpdateRepository name=MyOVSRepo
Status: Success
Time: 2017-12-19 06:56:19,409 EST
JobId: 1513684574493
OVM> list ServerUpdateRepository
Command: list ServerUpdateRepository
Status: Success
Time: 2017-12-19 06:57:21,744 EST
Data:
None
That’s it. Now login to Oracle VM Server and the check the version.
Linux System Administrator's Blog 