Consequences of System Board replacement for ODA

      190 Comments on Consequences of System Board replacement for ODA

Hi there,
If one day, you have the experience like me to manage the replacement of a motherboard into an ODA, think about the following:
No more private interconnect between dom_base0 and dom_base1
NIC priv1 is down on dom0
eth0 is not working on dom_base
From dom0
[code language=”sql”]
[root@hostdom01 ~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default xxx.16.10.5 0.0.0.0 UG 0 0 0 net1
169.254.0.0 * 255.255.0.0 U 0 0 0 priv1
xxxx.16.10.0 * 255.255.255.0 U 0 0 0 net1
missing: 192.168.16.0 * 255.255.255.0 U 0 0 0 priv1
[/code]
All of us is expecting from the field engineer to do the full job but in fact they are not doing that!
Got to this page: https://docs.oracle.com/cd/E22693_01/doc.12/e55580/oakcli.htm
Table 5-7 oakcli configure network Command Parameters
Parameter Description
-changeNetCard Configures the network card after it has been replaced. You must run the oakcli configure network -changeNetCard command on each node if the network card has been replaced on each node. This parameter is supported on all Oracle Database Appliance hardware models.
This command must be executed from dom0 on virtualized platforms
Once this is done, when you run service network restart on dom0, the priv1 NIC report invalid MAC address!
Then we have to change the HWADDR into the ifcfg-priv on both nodes and done!
[code language=”sql”]
[root@hostdom01 ~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default xxx.16.10.5 0.0.0.0 UG 0 0 0 net1
169.254.0.0 * 255.255.0.0 U 0 0 0 priv1
xxxx.16.10.0 * 255.255.255.0 U 0 0 0 net1
192.168.16.0 * 255.255.255.0 U 0 0 0 priv1
[/code]
Hope this will help in case you get the same situation.
Cheers
jko


     

Leave a Reply

Your email address will not be published. Required fields are marked *