Patching an Exadata or ZDLRA Node with an Image that Includes a Broadcom Upgrade can Result in a Down Link
(Doc ID 2933783.1)
Last updated on JUNE 27, 2023
Applies to:
Cisco Nexus Switch - Version All Versions to All Versions [Release All Releases]Exadata Database Machine X8-2/X8M-2 Hardware - Version All Versions to All Versions [Release All Releases]
Zero Data Loss Recovery Appliance X8/X8M Hardware - Version All Versions to All Versions [Release All Releases]
Exadata Database Machine X9M-2 Hardware - Version All Versions to All Versions [Release All Releases]
Zero Data Loss Recovery Appliance X9M Hardware - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Symptoms
Symptom 1)Patch Precheck Script Fails with the following:
[FAIL] dbadm01: Force auto-negotiation are configured in ifcfg-eth1. Please check DocID 2933783.1.
[FAIL] dbadm01: Force auto-negotiation are configured in ifcfg-eth2. Please check DocID 2933783.1.
[FAIL] dbadm01: Force auto-negotiation are configured in ifcfg-eth3. Please check DocID 2933783.1.
[FAIL] dbadm01: Force auto-negotiation are configured in ifcfg-eth4. Please check DocID 2933783.1.
See Solution 1 below to remove the forced speed settings from the ifcfg-extX file
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Symptom 2) After upgrading from an Exadata image that includes Broadcom 214.2.271.9 to a new image that includes 222.1.86.0 a DOWN link can occur if speed and duplex are forced in the ifcfg-ethX files
Example:
See Solution 2 below for steps to enable auto-negotiation on ethX for Systems that have a sudden link down after upgrading
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |