projects / unix-history / blame
| Commit | Line | Data |
|---|---|---|
| da29eb96 KM |
1 | .\" @(#)ddn.4 6.1 (Berkeley) %G% |
| 2 | .\" | |
| 3 | .TH DDN 4 "" | |
| 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 | |
| 17 | .IR ip (4). | |
| 18 | .SH DIAGNOSTICS | |
| 19 | .BR "ddn%d: not alive" . | |
| 20 | The initialization routine was entered even though the device | |
| 21 | did not autoconfigure. This indicates a system problem. | |
| 22 | .PP | |
| 23 | .BR "ddn%d: failed getting UBA resources for lcn %d" . | |
| 24 | Insufficient UNIBUS resources existed to initialize the device. | |
| 25 | This is likely to be a shortage of UNIBUS mapping registers. | |
| 26 | .PP | |
| 27 | .BR "ddn%d: couldn't get X25 init buffer" . | |
| 28 | This indicates that an | |
| 29 | .I mbuf | |
| 30 | could not be allocated for sending the initialization message to the | |
| 31 | ACP625. | |
| 32 | .PP | |
| 33 | .BR "DDN: illegal X25 address length!" | |
| 34 | .br | |
| 35 | .BR "DDN: illegal X25 address format!" | |
| 36 | .br | |
| 37 | These errors indicate a problem with the called X.25 address received | |
| 38 | from the IMP on an incoming call. | |
| 39 | .PP | |
| 40 | .BR "X25 RESET on lcn = %d" . | |
| 41 | This indicates that an unexpected X.25 RESET was received on the | |
| 42 | indicated LCN. | |
| 43 | .PP | |
| 44 | .BR "X25 INTERRUPT on lcn = %d, code = %d" . | |
| 45 | This indicates that an unexpected X.25 INTERRUPT Packet was received on the | |
| 46 | indicated LCN. | |
| 47 | .PP | |
| 48 | .BR "ddn%d: failed to get supr msg bfr!" . | |
| 49 | This indicates that an | |
| 50 | .I mbuf | |
| 51 | could not be allocated for sending a supervisor message to the | |
| 52 | ACP625. | |
| 53 | .PP | |
| 54 | Any other error message from ddn%d: indicates a serious error | |
| 55 | detected by either the driver or the ACP625 firmware. |