Doc : Dom0 Upgrade Execution Process Version: 1.54-------------------------------------------------------------------------------------------------------------------------- Objective :-This Document describes the steps to be followed to perform the OVMS upgrade or Dom0 upgrade. Pre check to be performed 1 hr before the schedule of Execution 1.Ensure : DBA has taken the HC for the Affected Dom0 ping channel ovms-up-project /mig-os - script will auto mount 3.Mig-os mount source details :-mkdir /mig-os ; mount -o noacl rm02stor29-nas:/export/roh_29a_hwmig/rmdc_dom0 /mig-osmkdir /mig-os ; mount -o noacl adc08ntap17-bkp:/vol/aoh_17a_hwmig/adc_dom0 /mig-os mkdir /mig-os ; mount -o noacl sl05stor02-nas:/export/sloh_02a_hwmig/sldc_dom0 /mig-osmkdir /mig-os ; mount -o noacl tvp01stor05-nas:/export/tvpoh_05a_hwmig/tvpdc_dom0 /mig-osmkdir /mig-os ; mount -o noacl epc002oodstor02-nas:/export/epcoh_02a_hwmig/epdc_dom0 /mig-osmkdir /mig-os ; mount -o noacl syc002oodstor01-nas:/export/sycoh_01a_hwmig/sydc_dom0 /mig-osmkdir /mig-os ; mount -o noacl llg02stor02-bkp:/export/llgoh_07a_hwmig/llg_dom0 /mig-os

4.Validate Prep Data and Current Environment ============== TEMPLATE ==============SR#:Source Dom0:Target Dom0:Source Dom0 VM list :Nos of VMs from PREP : Nos of VMs from Portal: Are the VM names Listed in Prep the same as current VM List [Y/N] : ============== TEMPLATE ==============Use This as reference through out activity5.To Take: Source Dom0 Pre Health checks and paste the output in the SRCheck the OS version of each VM It should not be OEL 6.X

If VMs OEL version Ok then proceed next stepsRun: a) /ptsadmin/os_migration/OEL/Dom0_Upgrade_sysinfo_pre_upg_post_checks.sh -o source -o pre -rfc 3-TESTIIAbove script covers:HW_model of the Dom0BIOS version ,ILOM versionunamecat /etc/enterprise-releasemig-os is mountedreset ilom passwordShows Total vcpus of all running VMs ,Shows Total Memory of all running VMsChecking the vm.cfg for vcpu_max parameterCheck if vms are on localdiskIdentify the container to snapEM agent status ,Ovs-agent statusLdap statusIfconfig,bond,MTU,route details c). Ensure you are able to access the ilom console of the Dom0d). Ensure that /etc/ovms-provision.conf exists. If it does not, perform the following step:cat > /etc/ovms-provision.conf show serverPool name=rmc002oodpool001OVM> show serverPool name=rmc002oodpool001

update the vlan tagging page

3.IF we find more than Two Bridges for a VM check it has rac interfaceIn that case we need to take ./getnet for rac also and get it tagged

Run for : -rac-vip-FrontendLogin : hqsun1 - take the vlan id details of the VMs

EX:bash-2.03$ /home/vvarughe/getnet vmohsadvg501

Request: vmohsadvg501

FQDN: vmohsadvg501.oracleoutsourcing.comIP: 148.87.205.163Netmask: 255.255.255.240

vlan id: rmdc-z2-advg-v160vlan note: NAIR-DB-Advantage-Sales-and-Marketing-(sr3-5756856194)

Network: 148.87.205.160/28First IP: 148.87.205.161Last IP: 148.87.205.174Broadcast IP: 148.87.205.175

To Get the Switch port details and : PFE and SFE Use portal : http://pnvcapp01.oracle.com/cgi-bin/switches.cgi

Sample VLAN tagging SR Template

Subject: OVMS Project:auc055oodhost044:VLAN tagging request

Suggested SR request

This SR is part of the OVMS project for tagging all servers which belongs to rmc002oodpool006

Please VLAN Tag the following Dom0HOSTNAME: rmc002oodhost052Mac address : 00:10:E0:57:C9:4F

SW1: cosprings1z2-swi-107.oracle.comSW2: cosprings1z2-swi-108.oracle.comPORT: 12

VLAN:rmdc-z2-isuv-v219 10.222.66.192/28 NANR-RAC-Illinois-State-University-(sr3-9100325470)

Rasie SR to : Network TeamSample SR#3-11199598771Follow up till completion of the VLAN tagging SRValidate all VLANS from the list given are tagged.

4. During Prep stage for : cit-em-agent-12-R4 copy the : /mig-os/pchandru/cit-em-agent-12-R4.remove file as : /usr/local/git/etc/software/cit-em-agent-12-R4.remove

5. Run : /usr/local/git/bin/host-group -f all make sure service_code = noneIf it is showing : ebso pod etc update ITASgo to ITAS -- > Asset Details -- > change service_code to Noneit will take 15 min to pushup APS

6. Check the Business_area of the host must be : commercial any other inform LeadEX: [root@rmc002oodhost438 ~]# /usr/local/git/bin/host-group -f all | grep -i business_areabusiness_area: commercial 7. check ILOM DNS is resolving fine with correct format Refer below:-ILOM_NAME="${DATACENTER}-mgmt-${SERIAL}.${DOMAIN_NAME}" # ADC Zone 7 # ADC Zone 8 # ADC Zone 9 # ADC Zone 15 # ADC Zone 26 # ADC Zone 31 # ADC Zone 32 # ADC Zone 33 # ADC Zone 34 # ADC Zone 36 # ADC Zone 38 # ADC Zone 39 # ADC Zone 40 # RMDC Zone 2 # RMDC Zone 5 # RMDC Zone 6 # LLG Zone 1 # LLG Zone 2 # LLG Zone 6 # LLG Zone 7 # LLG Zone 3 # TVP Zone 1 # TVP Zone 2 # SLDC Zone 4 # SLDC Zone 5

ILOM_NAME="${HOSTNAME}-ilom.${DOMAIN_NAME}" # ADC Zone 42 # ADC Zone 43 # ADC Zone 44 # ADC Zone 45 # ADC Zone 46 # ADC Zone 47 # ADC Zone 48 # ADC Zone 49 # ADC Zone 50 # ADC Zone 51 # ADC Zone 52 # ADC Zone 53 # ADC Zone 54 # ADC Zone 55 # ADC Zone 56 # ADC Zone 57 # ADC Zone 58 # ADC Zone 59 # ADC Zone 60 # ADC Zone 70 # LLG Zone 10 # LLG Zone 11 # SLDC Zone 6 # SLDC Zone 7 # SLDC Zone 8 # SLDC Zone 9 # SLDC Zone 10 # SLDC Zone 11 # SLDC Zone 12 # SLDC Zone 13 # SLDC Zone 14 # SLDC Zone 40 # SYDC Zone 1 & 2 # SYDC Zone 3 # EPDC Zone 2 # TRDC Zone 1 # TRDC Zone 2

Login to the OVMM server:-

Take login details from Leads

Once logged in > click on Severs and VMs > click on the zoom glass icon

Put in your Dom0 name

Click ok

Yo should see a :Green Pointing for your dom0, confirms Dom0 is discovere.We are good.

Otherwise right click on the server and click on ReDiscover