Commit | Line | Data |
---|---|---|
5ebe7d4b KB |
1 | .\" Copyright (c) 1983, 1991, 1993 |
2 | .\" The Regents of the University of California. All rights reserved. | |
954133cd | 3 | .\" |
91cff1e1 | 4 | .\" %sccs.include.redist.man% |
954133cd | 5 | .\" |
5ebe7d4b | 6 | .\" @(#)ddn.4 8.1 (Berkeley) %G% |
da29eb96 | 7 | .\" |
9903e566 CL |
8 | .Dd |
9 | .Dt DDN 4 vax | |
10 | .Os BSD 4.3 | |
11 | .Sh NAME | |
12 | .Nm ddn | |
13 | .Nd | |
14 | .Tn DDN | |
15 | Standard Mode | |
16 | .Tn X.25 | |
17 | .Tn IMP | |
18 | interface | |
19 | .Sh SYNOPSIS | |
20 | .Cd "device ddn0 at uba0 csr 166740 vector ddnintr" | |
21 | .Sh DESCRIPTION | |
da29eb96 | 22 | The |
9903e566 CL |
23 | .Nm ddn |
24 | device provides a | |
25 | .Tn DDN | |
26 | Standard Mode | |
27 | .Tn X.25 | |
28 | interface to an | |
29 | .Tn IMP | |
30 | using | |
31 | the | |
32 | .Tn ACC ACP625 | |
33 | .Tn X.25 | |
34 | board. It is normally used for connecting to | |
35 | the Defense Data Network | |
36 | .Pq Tn DDN . | |
37 | The controller itself is not accessible | |
da29eb96 KM |
38 | to users, but instead provides a network interface for the |
39 | Internet Protocol described in | |
9903e566 CL |
40 | .Xr ip 4 . |
41 | .Sh DIAGNOSTICS | |
42 | .Bl -diag | |
43 | .It ddn%d: not alive. | |
da29eb96 KM |
44 | The initialization routine was entered even though the device |
45 | did not autoconfigure. This indicates a system problem. | |
9903e566 CL |
46 | .Pp |
47 | .It ddn%d: failed getting UBA resources for lcn %d." | |
48 | Insufficient | |
49 | .Tn UNIBUS | |
50 | resources existed to initialize the device. | |
51 | This is likely to be a shortage of | |
52 | .Tn UNIBUS | |
53 | mapping registers. | |
54 | .Pp | |
55 | .It ddn%d: couldn't get X25 init buffer. | |
da29eb96 | 56 | This indicates that an |
9903e566 | 57 | .Em mbuf |
da29eb96 | 58 | could not be allocated for sending the initialization message to the |
9903e566 CL |
59 | .Tn ACP Ns 625. |
60 | .Pp | |
61 | .It DDN: illegal X25 address length! | |
62 | .It DDN: illegal X25 address format! | |
63 | These errors indicate a problem with the called | |
64 | .Tn X.25 | |
65 | address received | |
66 | from the | |
67 | .Tn IMP | |
68 | on an incoming call. | |
69 | .Pp | |
70 | .It X25 RESET on lcn = %d. | |
71 | This indicates that an unexpected | |
72 | .Tn X.25 | |
73 | .Tn RESET | |
74 | was received on the | |
75 | indicated | |
76 | .Tn LCN . | |
77 | .Pp | |
78 | .It X25 INTERRUPT on lcn = %d, code = %d. | |
79 | This indicates that an unexpected | |
80 | .Tn X.25 | |
81 | .Tn INTERRUPT | |
82 | Packet was received on the | |
83 | indicated | |
84 | .Tn LCN . | |
85 | .Pp | |
86 | .It ddn%d: failed to get supr msg bfr! | |
da29eb96 | 87 | This indicates that an |
9903e566 | 88 | .Em mbuf |
da29eb96 | 89 | could not be allocated for sending a supervisor message to the |
9903e566 CL |
90 | .Tn ACP625 . |
91 | .El | |
92 | .Pp | |
93 | Any other error message from | |
94 | .Ql ddn%d: | |
95 | indicates a serious error | |
96 | detected by either the driver or the | |
97 | .Tn ACP Ns 625 | |
98 | firmware. | |
99 | .Sh SEE ALSO | |
100 | .Xr netintro 4 , | |
101 | .Xr ip 4 | |
102 | .Sh HISTORY | |
103 | The | |
104 | .Nm | |
105 | interface appeared in | |
106 | .Bx 4.3 . |