Exalogic : "Bad Q_Key" messages reporting on opensm.log from exalogic compute nodes
(Doc ID 2280208.1)
Last updated on MAY 10, 2021
Applies to:Oracle Exalogic Elastic Cloud Software - Version 18.104.22.168.161018 to 22.214.171.124.170117
Exalogic Elastic Cloud X4-2 Hardware - Version X4 to X4 [Release X4]
Exalogic Elastic Cloud X5-2 Hardware - Version X5 to X5 [Release X5]
Oracle Virtual Sever (64-bit)
In X5-2 Exalogic environment, we can see /var/log in two NM2-GW switches are quickly exhausted.
Due to this issue:
- GW switch function compromised by dysfunctional opensmd and whereismasterd service.
- No master SM in IB fabric network.
- Dysfunctional jobs like creating guest vServers, restart Control stack and etc in Exalogic.
- Outage in Exadata like missing default IPoIB netowrk in compute and cell node
Upgrading to Oct 2016 PSU or Jan 2017 PSU.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document