Uncategorized
ODA : Update Firmware On ODA Post Reimage
Introduction
In my previous article we have learned how to Reimage an Oracle Database Appliance to 12.1.2.10. It is important to note that the Reimage process doesn’t update the firmware (BIOS, ILOM, Local and Shared HDD) on ODA nodes. The below screen shot show the output post Re-imaging an ODA X4-2. There is nothing wrong with reimage process and it is completely expected as the reimage process doesn’t update the firmware.
We can see that the ILOM, BIOS, HDD _Local and HDD_Shared are not up-to-date.
In this article I will demonstrate how to update the firmware post ODA re-imaging.
Prerequisites
- Root user access to ODA ILOM
- Download the ODA Bundle Patch using patch 25499210
The following steps should be followed to update the firmware on ODA post reimaging.
- Configure initial network
- Copy ODA software
- Update firmware
Configure initial network
The “oakcli configure firstnet” command is used to configure an initial network on Oracle Database Appliance (ODA) that enables you to copy ODA End User Bundle software to ODA server. oakcli configure firstnet allows you to establish the network interfaces for the Oracle Database Appliance upon first usage. Once you have completed the reimaging of ODA servers, you should log onto the one of the node ILOM console and do the initial configuration of the Oracle Database Appliance network using the command firstnet. The bond0 interface is configured when execute the firstnet utility. Before running firstnet, ensure that you allocated IP addresses and verify that their entries in the DNS have been completed.
Steps to Execute firstnet utility
Connect to the ILOM console using browser or putty to configure the initial IP address for the node you are connected to.
Once you execute the firstnet utility it will ask you for the IP address, Netmask and Gateway IPs.
Once the network interfaces have been configured, you need to test them by using the ping command on the node. Additionally, you can test the network by pinging the configured node from your remote client.
[root@oak1 ~]# ping 10.10.17.11
PING 172.16.202.71 (10.10.17.11) 56(84) bytes of data.
64 bytes from 10.10.17.11: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from 10.10.17.11: icmp_seq=2 ttl=64 time=0.008 ms
64 bytes from 10.10.17.11: icmp_seq=3 ttl=64 time=0.008 ms
64 bytes from 10.10.17.11: icmp_seq=4 ttl=64 time=0.006 ms
64 bytes from 10.10.17.11: icmp_seq=5 ttl=64 time=0.005 ms
— 172.16.202.71 ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4544ms
rtt min/avg/max/mdev = 0.005/0.010/0.027/0.009 ms
[root@oak1 ~]# ifconfig
bond0 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2
inet addr:10.10.17.11 Bcast:10.10.17.255 Mask:255.255.255.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:762 (762.0 b) TX bytes:546 (546.0 b)
bond1 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4
UP BROADCAST MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth0 Link encap:Ethernet HWaddr 90:E2:BA:81:2B:B4
inet addr:192.168.16.24 Bcast:192.168.16.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:138257 errors:0 dropped:0 overruns:0 frame:0
TX packets:138436 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11200490 (10.6 MiB) TX bytes:11134648 (10.6 MiB)
eth1 Link encap:Ethernet HWaddr 90:E2:BA:81:2B:B5
inet addr:192.168.17.24 Bcast:192.168.17.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:138217 errors:0 dropped:0 overruns:0 frame:0
TX packets:138434 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11197894 (10.6 MiB) TX bytes:11134800 (10.6 MiB)
eth2 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:762 (762.0 b) TX bytes:546 (546.0 b)
eth3 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth4 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth5 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:512371 errors:0 dropped:0 overruns:0 frame:0
TX packets:512371 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:38908072 (37.1 MiB) TX bytes:38908072 (37.1 MiB)
Repeat the steps on ODA node 2.
Copy Patches to ODA
Once the initial network is configured you can now copy the ODA patch to ODA node 1 under /tmp.
Update firmware
The Reimage process doesn’t update the firmware (BIOS, ILOM, Local and Shared HDD). The below screen shows that the firware is not updated on both the nodes.
Let’s update the firmware on ODA nodes.
- Copy the patches from node 1 to node 2.
- Unpack the patches using oakcli command as shown on both the nodes
- Update the firmware on node 1. At the end of the firmware update the node is rebooted.
- Once the node 1 comes back, verify the firmware is updated.
- Update the firmware on node 2. At the end of the firmware update the node is rebooted.
- Once the node 2 comes back, verify the firmware is updated.
- Update the firmware on Shared Storage. Both the ODA nodes rebooted at the end of storage update.
- Now verify the firmware on both the nodes.
We can now see that the firware is update on both the nodes.
Conclusion
Reimaging an Oracle Database Appliance doesn’t update the firmware (BIOS, ILOM, Local and Shared HDD). So we have to download the ODA patches and update the firmware post reimage manually. You must run the update command on both the ODA nodes and once for storage from node 1. It is fairly straight forward to update the firmware.