Commit | Line | Data |
---|---|---|
95f51977 | 1 | .\" @(#)ddn.4 6.2 (Berkeley) 5/16/86 |
da29eb96 | 2 | .\" |
95f51977 | 3 | .TH DDN 4 "May 16, 1986" |
da29eb96 KM |
4 | .UC 6 |
5 | .SH NAME | |
6 | ddn \- DDN Standard Mode X.25 IMP interface | |
7 | .SH SYNOPSIS | |
8 | .B "device ddn0 at uba0 csr 166740 vector ddnintr" | |
9 | .SH DESCRIPTION | |
10 | The | |
11 | .I ddn | |
12 | device provides a DDN Standard Mode X.25 interface to an IMP using | |
13 | the ACC ACP625 X.25 board. It is normally used for connecting to | |
14 | the Defense Data Network (DDN). The controller itself is not accessible | |
15 | to users, but instead provides a network interface for the | |
16 | Internet Protocol described in | |
71d64def MK |
17 | .IR ip (4P). |
18 | .SH SEE ALSO | |
19 | intro(4N), ip(4P) | |
da29eb96 KM |
20 | .SH DIAGNOSTICS |
21 | .BR "ddn%d: not alive" . | |
22 | The initialization routine was entered even though the device | |
23 | did not autoconfigure. This indicates a system problem. | |
24 | .PP | |
25 | .BR "ddn%d: failed getting UBA resources for lcn %d" . | |
26 | Insufficient UNIBUS resources existed to initialize the device. | |
27 | This is likely to be a shortage of UNIBUS mapping registers. | |
28 | .PP | |
29 | .BR "ddn%d: couldn't get X25 init buffer" . | |
30 | This indicates that an | |
31 | .I mbuf | |
32 | could not be allocated for sending the initialization message to the | |
33 | ACP625. | |
34 | .PP | |
35 | .BR "DDN: illegal X25 address length!" | |
36 | .br | |
37 | .BR "DDN: illegal X25 address format!" | |
38 | .br | |
39 | These errors indicate a problem with the called X.25 address received | |
40 | from the IMP on an incoming call. | |
41 | .PP | |
42 | .BR "X25 RESET on lcn = %d" . | |
43 | This indicates that an unexpected X.25 RESET was received on the | |
44 | indicated LCN. | |
45 | .PP | |
46 | .BR "X25 INTERRUPT on lcn = %d, code = %d" . | |
47 | This indicates that an unexpected X.25 INTERRUPT Packet was received on the | |
48 | indicated LCN. | |
49 | .PP | |
50 | .BR "ddn%d: failed to get supr msg bfr!" . | |
51 | This indicates that an | |
52 | .I mbuf | |
53 | could not be allocated for sending a supervisor message to the | |
54 | ACP625. | |
55 | .PP | |
56 | Any other error message from ddn%d: indicates a serious error | |
57 | detected by either the driver or the ACP625 firmware. |