I have never heard of any such reports. Netconfig should not be doing much differently that what would happen if you logged in manually, and performed the same commands. what is does do differently is setup the session for less interactivity (i.e. disables the pager, turns off some session messages, etc.).
If you happened to have ConfigJob debugging enabled when you ran this job, the job directory would be helpful in determining when the switch lost connectivity with RME (i.e. when it reloaded).
If not, the best way to troubleshoot this would be to schedule a maintenance window, and repeat the same job with ConfigJob debugging enabled as well as while running a sniffer trace. When the switch reloads, there will be a good paper trail showing what led up to that. Opening a TAC service request with that information will get you to the right team that can troubleshoot why CatOS is crashing.
It may also be good to open up a TAC service request before doing the job to see if there are additional things that should be set up on the switch side for making the most out of the crash.
All that said, if your job is to do a show banner, you should consider using Netshow instead of Netconfig. Netconfig is geared to doing configuration changes rather than executing commands for purposes of capturing output.
