Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

acc(4) [bsd man page]

ACC(4)							     Kernel Interfaces Manual							    ACC(4)

acc - ACC LH/DH IMP interface SYNOPSIS
/sys/conf/SYSTEM: NACC 0 # ACC LH/DH ARPAnet IMP interface PLI YES # LH/DH is connected to a PLI DESCRIPTION
The acc device provides a Local Host/Distant Host interface to an IMP. It is normally used when participating in the DARPA Internet. The controller itself is not accessible to users, but instead provides the hardware support to the IMP interface described in imp(4). When configuring, the imp(NIMP) pseudo-device must also be included. DIAGNOSTICS
acc%d: not alive. The initialization routine was entered even though the device did not autoconfigure. This indicates a system problem. acc%d: can't initialize. Insufficient UNIBUS resources existed to initialize the device. This is likely to occur when the device is run on a buffered data path on an 11/750 and other network interfaces are also configured to use buffered data paths, or when it is configured to use buffered data paths on an 11/730 (which has none). acc%d: imp doesn't respond, icsr=%b. The driver attempted to initialize the device, but the IMP failed to respond after 500 tries. Check the cabling. acc%d: stray xmit interrupt, csr=%b. An interrupt occurred when no output had previously been started. acc%d: output error, ocsr=%b, icsr=%b. The device indicated a problem sending data on output. acc%d: input error, csr=%b. The device indicated a problem receiving data on input. acc%d: bad length=%d. An input operation resulted in a data transfer of less than 0 or more than 1008 bytes of data into memory (according to the word count register). This should never happen as the maximum size of a host-IMP message is 1008 bytes. 3rd Berkeley Distribution July 26, 1987 ACC(4)

Check Out this Related Man Page

IMP(4)							     Kernel Interfaces Manual							    IMP(4)

imp - 1822 network interface SYNOPSIS
/sys/conf/SYSTEM: NIMP count # ARPAnet IMP 1822 interface DESCRIPTION
The imp interface, as described in BBN Report 1822, provides access to an intelligent message processor normally used when participating in the Department of Defense ARPA network. The network interface communicates through a device controller, usually an ACC LH/DH or HDH or a DEC IMP-11A, with the IMP. The interface is "reliable" and "flow-controlled" by the host-IMP protocol. To configure IMP support, at least one of acc(4), css(4) or hdh(4) must be included. The count specifies the total number of IMP connec- tions. The network number on which the interface resides is specified at boot time using the SIOCSIFADDR ioctl. The host number is dis- covered through receipt of NOOP messages from the IMP. The network interface is always in one of four states: up, down, initializing, or going down. When the system is booted, the interface is marked down. If the hardware controller is successfully probed, the interface enters the initializing state and transmits three NOOP mes- sages to the IMP. It then waits for the IMP to respond with two or more NOOP messages in reply. When it receives these messages it enters the up state. The ``going down'' state is entered only when notified by the IMP of an impending shutdown. Packets may be sent through the interface only while it is in the up state. Outgoing packets are dropped with the error ENETDOWN returned to the caller if the interface is in any other state. DIAGNOSTICS
imp%d: not configured. A hardware interface could not be attached during autoconfiguration because too few IMP pseudo-devices were config- ured. imp%d: leader error. The IMP reported an error in a leader (1822 message header). This causes the interface to be reset and any packets queued up for transmission to be purged. imp%d: going down in 30 seconds. imp%d: going down for hardware PM. imp%d: going down for reload software. imp%d: going down for emergency reset. The Network Control Center (NCC) is manipulating the IMP. By convention these messages are reported to all hosts on an IMP. imp?: host %x, lost %d rfnms. The IMP had messages outstanding to the host listed, but no RFNM (Request for Next Message) messages were received from the IMP in 127 seconds. The software state for that host is reinitialized. imp%d: interface reset. The host has received an interface reset message from the IMP. imp%d: address reset to x%x (%d/%d). The host has received a NOOP message which caused it to reset its notion of its current address. The Internet address is printed in hexadecimal, with the host and IMP numbers following. This indicates that the address originally set by ifconfig(8) was incorrect, that the IMP has undergone an identity crisis, or that communication between the IMP and the host is being gar- bled. imp%d: data error. The IMP noted an error in data transmitted. The host-IMP interface is reset and the host enters the init state (await- ing NOOP messages). imp%d: interface reset. The reset process has been completed. imp%d: marked down. After receiving a "going down in 30 seconds" message, and waiting 30 seconds, the host has marked the IMP unavailable. Before packets may be sent to the IMP again, the IMP must notify the host, through a series of NOOP messages, that it is back up. imp%d: can't handle af%d. The interface was handed a message with addresses formatting in an unsuitable address family; the packet was dropped. SEE ALSO
intro(4N), inet(4F), acc(4), css(4), hdh(4), implog(8), implogd(8) 3rd Berkeley Distribution August 2, 1987 IMP(4)
Man Page