Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

hy(4) [bsd man page]

HY(4)							     Kernel Interfaces Manual							     HY(4)

hy - Network Systems Hyperchannel interface SYNOPSIS
/sys/conf/SYSTEM: NHY hy_controllers # Hyperchannel DESCRIPTION
The hy interface provides access to a Network Systems Corporation Hyperchannel Adapter. The network to which the interface is attached is specified at boot time with an SIOCSIFADDR ioctl. The host's address is discovered by reading the adapter status register. The interface will not transmit or receive packets until the network number is known. DIAGNOSTICS
hy%d: unit number 0x%x port %d type %x microcode level 0x%x. Identifies the device during autoconfiguration. hy%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was dropped. hy%d: can't initialize. The interface was unable to allocate UNIBUS resources. This is usually due to having too many network devices on an 11/750 where there are only 3 buffered data paths. hy%d: NEX - Non Existent Memory. Non existent memory error returned from hardware. hy%d: BAR overflow. Bus address register overflow error returned from hardware. hy%d: Power Off bit set, trying to reset. Adapter has lost power, driver will reset the bit and see if power is still out in the adapter. hy%d: Power Off Error, network shutdown. Power was really off in the adapter, network connections are dropped. Software does not shut down the network unless power has been off for a while. hy%d: RECVD MP > MPSIZE (%d). A message proper was received that is too big. Probable a driver bug. Shouldn't happen. hy%d: xmit error - len > hy_olen [%d > %d]. Probable driver error. Shouldn't happen. hy%d: DRIVER BUG - INVALID STATE %d. The driver state machine reached a non-existent state. Definite driver bug. hy%d: watchdog timer expired. A command in the adapter has taken too long to complete. Driver will abort and retry the command. hy%d: adapter power restored. Software was able to reset the power off bit, indicating that the power has been restored. SEE ALSO
intro(4N), inet(4F) BUGS
If the adapter does not respond to the status command issued during autoconfigure, the adapter is assumed down. A reboot is required to recognize it. The adapter power fail interrupt seems to occur sporadically when power has, in fact, not failed. The driver will believe that power has failed only if it can not reset the power fail latch after a ``reasonable'' time interval. These seem to appear about 2-4 times a day on some machines. There seems to be no correlation with adapter rev level, number of ports used etc. and whether a machine will get these ``bogus powerfails''. They don't seem to cause any real problems so they have been ignored. 3rd Berkeley Distribution August 20, 1987 HY(4)

Check Out this Related Man Page

fza(4)							     Kernel Interfaces Manual							    fza(4)

       fza - DEFZA FDDI Network Interface

       device fza0 at ibus? vector fzaintr

       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

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

       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.

       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)

Man Page

Featured Tech Videos