Disconnected Concurrent Manager

Due to a network issue the other night, I got to see interesting error messages, starting with from the Oracle Alert product:

APP-FND-01564: ORACLE error 12203 in AFPCOA
Cause:  AFPCOA failed due to ORA-12203: TNS:unable to connect to destination
.
The SQL statement being executed at the time of the error was:  and was executed from the file .
/s_u01/<directories>/applmgr/<servername>/appl/alr/11.5.0/bin/ALECDC
Program exited with status 1

So what really was unable to get to the destination?  Well on several concurrent manager nodes we were receiving these error messages:

Invalid option.
Usage: CONNECT <username> [AS SYSDBA|SYSOPER]
Invalid option.
Usage: CONNECT <username> [AS SYSDBA|SYSOPER]
unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus

Failed to get arguments
ORACLE error 1012 in FDPCLS
Cause:  FDPCLS failed due to ORA-01012: not logged on
The main COMPLETION_TEXT being returned was "Concurrent program returned no reason for failure." or "Program exited with status 1" or "Concurrent Manager encountered an error while running SQL*Plus for your concurrent request <ID>.
Review your concurrent request log and/or report output file for more detailed information."

Additionally, our Workflow Mailer went down with this error:

[Sep 24, 2013 7:12:24 PM MST]:1380075144128:Thread[outboundThreadGroup1,5,outboundThreadGroup]:0:-1:<CM node 1>:<IP>:-1:-1:UNEXPECTED:[SVC-GSM-WFMLRSVC-1893136-10006 : oracle.apps.fnd.wf.mailer.SMTPOutboundProcessor.open()]:Unable to connect to tranport
ERROR:
ORA-12203: TNS:unable to connect to destination

On a whole, most anything that needed to have a stable network connection from one point to another was disrupted so this aftermath made us take down the Concurrent Manager on both nodes and restart them to make sure everything was clean.