Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

xna(4) [ultrix man page]

xna(4)							     Kernel Interfaces Manual							    xna(4)

Name
       xna - DEBNI and DEMNA Ethernet interfaces

Syntax
       device xna0 at vaxbi? node? vector xnaintr (DEBNI)
       device xna0 at xmi? node? vector xnaintr (DEMNA)

Description
       The  driver provides access to a 10 Mbytes Ethernet network through the DEBNI and DEMNA adapters.  The DEBNI is an Ethernet to BI bus.  The
       DEMNA is an Ethernet to XMI adapter.

       The host's Internet address is specified at boot time with an SIOCSIFADDR ioctl.  The driver employs the Address  Resolution  Protocol,	as
       described in to map dynamically between Internet and Ethernet addresses on the local network.

       The  driver normally tries to use a trailer encapsulation to minimize copying data on input and output.	This can be disabled for an inter-
       face by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl.  Trailers are used only for packets destined for Internet hosts.

       The SIOCSPHYSADDR ioctl can be used to change the physical address of the adapter and SIOCRPHYSADDR  can  be  used  to  read  its  physical
       address.   SIOCADDMULTI	and  SIOCDELMULTI can be used to add or delete multicast addresses.  The driver supports a maximum of 12 multicast
       addresses. The argument to the latter ioctls is a pointer to an ``ifreq'' structure found in

       SIOCRDCTRS and SIOCRDZCTRS ioctls can be used to read or read and clear network counters. The argument  to  the	latter	two  ioctls  is  a
       pointer to a counter structure ``ctrreq'' found in

       The ioctls SIOCENABLBACK and SIOCDISABLBACK can be used to enable and disable the interface loopback mode.

Restrictions
       The PUP protocol family is not supported.

Diagnostics
       xna%d: port self-test failed:<register list>
       Adapter did not pass the power-up self-test during autoconfiguration time. The port attachment fails.

       xna%d: couldn't allocate...
       The driver was unable to allocate memory for adapter data structures.  The port attachment fails.

       xna%d: port probe failed:<register list>
       The driver was unable to bring the adapter into the initialized state.  The port attachment fails.

       xna%d: port init failed:<register list>
       The driver failed to prepare the adapter for runtime use.

       xna%d: port state changed, resetting:<register list>
       The adapter issued a port state change interrupt. The port state is reset.

       xna%d: port reset failed
       The driver was unable to bring the adapter into the initialized state during a port reset.

       xna%d: command failed, error code:<error code>
       The adapter port command failed. The error code gives reason for failure.

       xna%d: couldn't handle af%d
       A packet with an undefined protocol type has been sent to the adapter.

       xna%d: addmulti failed, multicast list full
       Too many multicast requests have been made.

See Also
       arp(4p), inet(4f), intro(4n)

																	    xna(4)

Check Out this Related Man Page

fza(4)							     Kernel Interfaces Manual							    fza(4)

Name
       fza - DEFZA FDDI Network Interface

Syntax
       device fza0 at ibus? vector fzaintr

Description
       The  interface  is  a  high  speed  TURBOchannel  bus to a 100 Mbit/second Fiber Distributed Data Interface (FDDI) timed token ring network
       adapter.  The interface allows the host system to be an FDDI single attachment station.

       The host's Internet address is specified at boot time with an SIOCSIFADDR ioctl.  The interface employs	the  address  resolution  protocol
       described in to map dynamically between Internet and FDDI addresses on the local network.

       The maximum frame size for the interface is 4500 bytes, which is substantially larger that the 1500 bytes maximum packet size of the Ether-
       net interfaces. The interface does not support the BSD trailer encapsulation, which is specific to the VAX architecture.

       The SIOCRPHYSADDR ioctl can be used to read the physical address of the DEFZA adapter. The physical address of the DEFZA adapter can not be
       changed.

       The  SIOCADDMULTI  and  SIOCDELMULTI  ioctls  can  be  used  to	add  or delete multicast addresses.  The DEFZA supports up to 64 multicast
       addresses.

       The SIOCRDCTRS ioctl can be used to read the FDDI driver counters.  The DEFZA adapter status and characteristics can also be  read  through
       this ioctl by providing a FDDI_STATUS flag . The argument to this ioctl is a pointer to a counter or status structure, found in <net/if.h>.

       The SIOCENABLBACK and SIOCDISABLBACK ioctls can be used to enable and disable the interface loopback mode, respectively.

       The SIOCEEUPDATE ioctl can be used to update the adapter's firmware.

       The SIOCIFRESET ioctl can be used to reset the adapter.

Diagnostics
       Diagnostic error messages contain information provided by the driver. For example:

       fza%d: fzaprobe selftest failed
       The DEFZA adapter did not pass the power-up selftest during autoconfiguration.
       fza%d: port init failed
       The DEFZA adapter cannot be initialized.
       fza%d: port in the Halt State -> CNS hardware fault
       The DEFZA adapter went to the Halt state because of an adapter firmware fault.
       fza%d: LINK unavailable
       The network link went down which means that the station is not on the FDDI ring.
       fza%d: Ring Init Received
       A Ring Initialization unsolicited event has been received from the fza%d interface.

See Also
       arp(4p), inet(4f), intro(4n)

																	    fza(4)
Man Page