brian@ucsd.EDU (Brian Kantor) (01/13/89)
Environment: Vax780, ACC6250 interface, X.25 connection to PSN 26.5.0.3 "dda0: Call Cleared LCN x cause code 9 diag code 88" Ever since the new PSN software was installed on our Milnet IMP, we've been getting thousands of these messages, often several a minute. From what I can see, they are not an error, but instead represent a change in the PSN software that now advises me that a host is down by blowing the X.25 connection out of the water instead of just letting it time out. The difficulty is that each and every one of these cleared calls causes a message to get printed on the console, and we're wasting trees. I've ADB-hotpatched a null into the beginning of the print string in the system kernel to stop the messages, and perhaps at some later time I'll take the printf out or modify the conditions under which it squirts out. Any insight or advice on this? Am I doing the right thing by ignoring and suppressing these messages, or is there really something wrong? Brian Kantor UCSD Office of Academic Computing Academic Network Operations Group UCSD B-028, La Jolla, CA 92093 USA brian@ucsd.edu ucsd!brian BRIAN@UCSD
oleary@GODOT.PSC.EDU (dave o'leary) (01/14/89)
Brian, we get the dda0: Call cleared msgs all the time on our ACC 5250 machine on the Arpanet. Somebody at ACC told me that it was nothing to woohrry about, I think it may even be the normal open and close of X.25 circuits. I haven't dealt with any problems on that for a while (since Arpa went to 7.0 actually) so the stuff isn't too clear in my memory. We are still getting the msgs after many months. dave
stjohns@BEAST.DDN.MIL (Mike St. Johns) (01/14/89)
A quick look at the driver code reveals that it prints the message anytime a connection is cleared without completing. I.e. what would usually be considered "abnormal" aborts. I think if I were getting as many messages as were mentioned, I'd probably either comment the lines out, or do some filtering to select only *real* aborts. Mike