We have a DNCS 5.0 system in our lab, and recently all the in-=band traffic to our BFS stopped. I couldn't see anything obviously wrong, and the BFSServer could be restarted from dncsControl without a problem. But, none of our boxes were able to load anything off the BFS and in-band traffic was zero. So, I decided to try and restart the sessions. Now, all the BFS sessions for all BFS sources will not start, right down to the native sources (in band, bootloader, etc). When I try to start a session for any, from the Source Definition, for any BFS Source, it just kicks back to the start session screen. I the BFS log I see a lot of errors with response code 18. 12/03/2018 14:22:11.538|14406/1|WARN|bfsServer:BfsData.C(684)|BfsData::_monitorDataCarousels() not all sessions up, retrying in 30 seconds 12/03/2018 14:22:11.595|14406/1|ERROR|bfsServer:BfsSerSession.C(199)|BfsSerSession::initiateComplete() session: 00:00:00:00:00:00/2 FAILED with rspCode: 18 12/03/2018 14:22:11.596|14406/1|ERROR|libdsmcc:serverStates.C(1585)|WFSSesCnf::handle(ServerCFSCnf):ERROR: Resonse code in ServerCFSCnf message is NOT rspOK for ServerCFSCnf message. For sessionId[00:00:00:00:00:00/2]. Response Code[18]. 12/03/2018 14:22:11.596|14406/1|WARN|bfsServer:BfsNetMgr.C(284)|Unable to make a DsmccMsg because there are not enough bytes. (MessageUnderflow.) What does "Response Code [18]" mean? Any ideas, suggestions, or questions? Thanks!
... View more
