Exalogic: EMOC Jobs To Fail Due To FabricCRUDTasks timing out when spsh process experiences slow startup on NM2-GW switches
(Doc ID 1667237.1)
Last updated on FEBRUARY 22, 2019
Applies to:Oracle Exalogic Elastic Cloud Software - Version 18.104.22.168.2 and later
Information in this document applies to any platform.
You have an Exalogic system running Exalogic Elastic Cloud Software (EECS) deployed in a virtual configuration and are experiencing unexpected failures from jobs initiated through the Enterprise Manager OpsCenter browser based user interface that drive additional configuration against NM2-GW switches, for example vDC-Create-vServer, Define Network etc. When you encounter such failures the audit trail for the failed EMOC job and the cacao.0 log (/var/opt/sun/cacao2/instances/scn-proxy/logs/cacao.0) for the Proxy Controller that initiated the failed FabricCRUD Task show an error similar to the following:
Make a note of the elapsed time for the execution - if the issue is not present and you enter the ilom-admin password and "exit" promptly then the expected time should be between 3 and 6 seconds.
- If the average time for completion is 3-6 seconds then the issue is not occurring on the given switch at that time
- If the elapsed time for any one test is greater than 20 seconds or the average time for completion is greater than 12 seconds then you have likely encountered this issue
It is possible that you have introduced a security tool, such as QualysGaurd or similar, that probes network ports to identify which ones are open for requests.
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