NE(4) — DEVICES AND NETWORK INTERFACES

NAME

ne − Interphase Network Coprocessor driver

AVAILABILITY

The ne driver is available from the Interphase Network Coprocessor (NC) software distribution. This driver is specific to this product. For information about installing the NC software distribution, refer to the Network Coprocessor Installation Manual.

CONFIG

options         OMNINET
device          ne0 at vme16d32 ? csr 0x6000 flags 0xa00000 priority 3
                        vector neintr 0xd4
device          ne1 at vme16d32 ? csr 0x6800 flags 0xa80000 priority 3
                        vector neintr 0xd5
device          ne2 at vme16d32 ? csr 0x5000 flags 0xb00000 priority 3
                        vector neintr 0xd6
device          ne3 at vme16d32 ? csr 0x5800 flags 0xb80000 priority 3
                        vector neintr 0xd7
device          ne4 at vme16d32 ? csr 0x4000 flags 0x800000 priority 3
                        vector neintr 0xd8
device          ne5 at vme16d32 ? csr 0x4800 flags 0x880000 priority 3
                        vector neintr 0xd9
device          ne6 at vme16d32 ? csr 0x3000 flags 0x900000 priority 3
                        vector neintr 0xda
device          ne7 at vme16d32 ? csr 0x3800 flags 0x980000 priority 3
                        vector neintr 0xdb

Up to eight Network Coprocessor interfaces may be installed depending on the configuration of the system. Device names range from ne0 to ne7. For information on how many Network Coprocessors are supported on a given machine type and configuration, refer to the Network Coprocessor READ_ME_FIRST or RMF document packaged with your product.

DESCRIPTION

ne is the device driver software that controls the Network Coprocessor board. The ne driver interfaces to the omni_nfsd(8) NFS daemons on the one hand, and to the Network Coprocessor software on the other. The Network Coprocessor software handles all of the network-related processing involved in the NFS file server function. In addition, it handles data link level processing for the remaining networking activities the server may be involved in (such as rlogin, rsh, RPC based programs other than NFS, etc.). With respect to the latter function, the ne driver interfaces to SunOS protocol stacks via the if(4N) general network interface mechanism.

On a kernel configured with the ne driver, the data link layer functionality provided by ne is available as soon as the Network Coprocessor is booted using the neload(8) utility. The NFS server functionality offered by ne does not become available until the omni_nfsd(8) daemons are started.

FILES

/dev/ne[0-7] Network Coprocessor interfaces

/usr/etc/neload downloads the Network Coprocessor software.

/etc/OMNI/ne.dwnld
binary file to be downloaded

Museum