pefn(7)                        DG/UX 5.4R3.00                        pefn(7)


NAME
       pefn - Peregrine FDDI network interface

SYNOPSIS
       pefn([vmebus,][def]) or
       pefn@devicecode([vmebus,]VMEA16addr)

DESCRIPTION
       The pefn device driver allows an AViiON system that includes a V/FDDI
       controller to access a Fiber Distributed Data Interface (FDDI)
       network. To set up this interface, you include one or more pefn
       entries in the DG/UX system configuration file.

       The pefn entry has two formats (shown above and illustrated below).
       The first format accepts all defaults for a specified controller
       board.  The second format specifies all values:

       vmebus        The device name of the parent VME bus to which the
                      pefn controller is attached, such as vme(0) or vme(1).
                      If this parameter is omitted, a parent bus of vme(0)
                      is assumed, and all subsequent parameters move up one
                      position.  Thus, pefn(3) is equivalent to
                      pefn(vme(0),3).

       def            A number from 0 to 7, or null for 0, identifying the
                      controller board defaults to use

       @devicecode   The network controller device code, preceded by the @
                      character

       VMEA16addr   The VME A16 (short I/O) address of the controller

       The pefn device is implemented as a clonable Streams driver.  This
       means that you can open a single node, such as /dev/pefn0, to access
       any unused minor device.  Each subsequent access of the node via the
       open(2) system call allocates a separate Stream (minor number) to the
       device driver.

DIAGNOSTICS
       Use the -i option with netstat(1C).

EXAMPLES
       The following entries in a DG/UX configuration file configure two
       FDDI controllers with default values, at nodes /dev/pefn0 and
       /dev/pefn1:

            pefn(0)
            pefn(4)

       Note that either pefn() or pefn(0) will create the initial node.
       Note also that the /dev/pefn* device nodes are created on a first-
       come, first-served basis:  the first pefn entry in the system file is
       the first pefn device configured, so it gets the node named
       /dev/pefn0; the second entry gets the node named /dev/pefn1, and so



Licensed material--property of copyright holder(s)                         1

pefn(7)                        DG/UX 5.4R3.00                        pefn(7)


       on.

       The following entry configures an FDDI controller with device code 7B
       and VME A16 address ffff2400:

            pefn@7B(ffff2400)

       For more information about DG/UX device configuration, refer to
       "Writing a Device Driver" in Programming in the DG/UX Kernel
       Environment.

       For a full discussion of device naming conventions and a list of
       board defaults, see Customizing the DG/UX System.

SEE ALSO
       ifconfig(1M), netinit(1M), system(4), arp(6P), vme(7), intro(7),
       inet(6F).








































Licensed material--property of copyright holder(s)                         2