EXACS - nodes reboot and cluster won't start after reduced cpu using dynamic scaling (Doc ID 2893028.1)

Last updated on NOVEMBER 16, 2022

Applies to:

Symptoms

Cluster won't start after an nodes abrupt reboot command by the clusterware

CRS, asm and other services won't start

The log files say no has network interfaces on computer nodes



ip addr sh not showing all private interfaces and not able to start the missing interfaces manually

e.g.

[root@nagu-2hdrr1 ~]# ifup clre1
ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device clre1 does not seem to be present, delaying initialization.

[root@nagu-2hdrr2 ~]# ifup clre1
ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device clre1 does not seem to be present, delaying initialization.

Changes

used a dynamic scaling CPU resource reshape per api with oci to reduce cpus to 6 on each node

[root@node1 tmp]# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 6
On-line CPU(s) list: 0-5
Thread(s) per core: 2
Core(s) per socket: 1
Socket(s): 2
NUMA node(s): 2
Vendor ID: AuthenticAMD
CPU family: 25
Model: 1
Model name: AMD EPYC 7J13 64-Core Processor
Stepping: 1
CPU MHz: 2445.402
BogoMIPS: 4890.80
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 64K
L1i cache: 64K
L2 cache: 512K
L3 cache: 16384K
NUMA node0 CPU(s): 0-3
NUMA node1 CPU(s): 4,5

[oracle@node2 ~]$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 6
On-line CPU(s) list: 0-5
Thread(s) per core: 2
Core(s) per socket: 1
Socket(s): 2
NUMA node(s): 2
Vendor ID: AuthenticAMD
CPU family: 25
Model: 1
Model name: AMD EPYC 7J13 64-Core Processor
Stepping: 1
CPU MHz: 2445.404
BogoMIPS: 4890.80
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 64K
L1i cache: 64K
L2 cache: 512K
L3 cache: 16384K
NUMA node0 CPU(s): 0-3
NUMA node1 CPU(s): 4,5

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.