Exadata Promiscuous Mode messages

어느순간 주기적으로 /var/og/messages 파일에 해당 로그가 10~20분 간격으로 발생. 

 

DB서버의 DB나 다른 어플리케이션단에서 사용하는건 없는데 트래픽이 튐.

 

CPU/Memory 사용율을 안높음.

Nov 1 11:37:51 semdb01t kernel: [47590251.017796] device bondeth0 entered promiscuous mode
Nov 1 11:37:51 semdb01t kernel: [47590251.017802] device eth2 entered promiscuous mode
Nov 1 11:37:51 semdb01t kernel: [47590251.019891] device ib0 entered promiscuous mode
Nov 1 11:37:51 semdb01t kernel: [47590251.050757] device ib1 entered promiscuous mode
Nov 1 11:37:54 semdb01t kernel: [47590253.682727] device bondeth0 left promiscuous mode
Nov 1 11:37:54 semdb01t kernel: [47590253.682730] device eth2 left promiscuous mode

 

Oracle Home : /u01/app/oracle/product/12.1.0.2/dbhome_1
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/12.1.0.2/dbhome_1/oraInst.loc
OPatch version : 12.2.0.1.19
OUI version : 12.1.0.2.0

 

해당 이슈는 버그로 OCW패치를 적용해줘야한다. 

Bug 25397620 - Public and Private interfaces entered/left Promiscuous Mode messages in OS log ( Doc ID 25397620.8 )

 

패치명 : p25397620_12102190716forOCW_Linux-x86-64.zip

 

Bug 25397620  Public and Private interfaces entered/left Promiscuous Mode messages in OS log

This note gives a brief overview of bug 25397620.
 The content was last updated on: 11-MAR-2020
 Click here for details of each of the sections below.

Affects:

 

Product (Component)	Oracle Server (PCW)
Range of versions believed to be affected	Versions >= 12.1 but BELOW 18.1
Versions confirmed as being affected	12.2.0.1 (Base Release) 12.1.0.2 (Server Patch Set)
Platforms affected	Generic (all / most platforms affected)

Fixed:

The fix for 25397620 is first included in

18.1.0 OCW RELEASE UPDATE 12.2.0.1.180116 12.1.0.2.191015 (Oct 2019) Grid Infrastructure Patch Set Update (GI PSU)

Interim patches may be available for earlier versions - click here to check.

Symptoms:	Related To:
(None Specified)	Cluster Ready Services / Parallel Server Management

Description

This bug is only relevant when using Real Application Clusters (RAC)
diagsnap.pl is turning private and public interfaces into promiscuous mode and it is reported in the OS logs continuously 
  
 
Rediscovery Notes
 You will see the following messages in the OS messages/syslog file due to diagsnap.pl

 

[root@rrac1 bin]# ./oifcfg getif 
eth0  10.208.xxx.0  global  public 
eth1  10.208.xxx.0  global  cluster_interconnect,asm 
eth2  10.208.xxx.0  global  cluster_interconnect,asm 
eth3  10.208.xxx.0  global  cluster_interconnect 
 
2). [root@rac1 bin]# vi /var/log/messages 
Jan 16 07:30:08 rac1 kernel: device eth3 left promiscuous mode 
Jan 16 07:30:08 rac1 kernel: device eth1 left promiscuous mode 
Jan 16 07:30:08 rac1 kernel: device eth2 left promiscuous mode 
Jan 16 07:30:11 rac1 kernel: device eth0 left promiscuous mode 
Jan 16 07:38:35 rac1 puppet-apply[12588]: (/Stage[main]/Sysadmin::Common::Pulse_audio_config/Exec[/var/tmp/update_csh.cshrc.sh]/returns) executed successfully 
Jan 16 07:38:35 rac1 puppet-apply[12588]: 
(/Stage[main]/Sysadmin::Common::Move_history_file_to_tmp/Exec[/var/tmp/move_history_file_to_tmp.sh]/returns) executed successfully 
Jan 16 07:38:35 rac1 puppet-apply[12588]: Finished catalog run in 1.17 seconds 
Jan 16 07:45:12 rac1 kernel: device eth1 entered promiscuous mode 
Jan 16 07:45:12 rac1 kernel: device eth0 entered promiscuous mode 
Jan 16 07:45:12 rac1 kernel: device eth2 entered promiscuous mode 
Jan 16 07:45:12 rac1 kernel: device eth3 entered promiscuous mode 
Jan 16 07:45:15 rac1 kernel: device eth1 left promiscuous mode 
Jan 16 07:45:15 rac1 kernel: device eth2 left promiscuous mode 
Jan 16 07:45:15 rac1 kernel: device eth0 left promiscuous mode 
Jan 16 07:45:19 rac1 kernel: device eth3 left promiscuous mode

 

 

Workaround
 Disable diagsnap

 $ oclumon manage -disable diagsnap