hy(4) [bsd man page]
HY(4) Kernel Interfaces Manual HY(4) NAME
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
xna(7) Miscellaneous Information Manual xna(7) NAME
xna - The DEMNA Ethernet interfaces SYNOPSIS
config_driver xna DESCRIPTION
The xna driver provides access to a 10-MB Ethernet network through the DEMNA adapter. The DEMNA is an Ethernet-to-XMI adapter. The host's Internet address is specified at boot time with an SIOCSIFADDR ioctl. The xna driver employs the Address Resolution Protocol, as described in arp(7), to map dynamically between Internet and Ethernet addresses on the local network. 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 xna driver supports a maximum of 12 multi- cast addresses. The argument to the latter ioctls is a pointer to an ``ifreq'' structure found in <net/if.h>. 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 <net/if.h>. The ioctls SIOCENABLBACK and SIOCDISABLBACK can be used to enable and disable the interface loopback mode. RESTRICTIONS
The PUP protocol family is not supported. EXAMPLES
To obtain the physical address of the adapter, use the SIOCRPHYSADDR ioctl as in the following program example: #include <stdio.h> /* standard I/O */ #include <errno.h> /* error numbers */ #include <sys/socket.h> /* socket definitions */ #include <sys/ioctl.h> /* ioctls */ #include <net/if.h> /* generic interface structures */ main() { int s,i; static struct ifdevea devea; /* Get a socket */ s = socket(AF_INET,SOCK_DGRAM,0); if (s < 0) { perror("socket"); exit(1); } strcpy(devea.ifr_name,"xna0"); if (ioctl(s,SIOCRPHYSADDR,&devea) < 0) { perror(&devea.ifr_name[0]); exit(1); } printf("Address is "); for (i = 0; i < 6; i++) printf("%X ", devea.default_pa[i] & 0xff); printf(" "); close(s); } To enable external loopback, use the SIOCENABLEBACK ioctl as in the following program example: #include <stdio.h> /* standard I/O */ #include <errno.h> /* error numbers */ #include <sys/socket.h> /* socket definitions */ #include <sys/ioctl.h> /* ioctls */ #include <net/if.h> /* generic interface structures */ main() { int s; struct ifreq data; /* Get a socket */ s = socket(AF_INET,SOCK_DGRAM,0); if (s < 0) { perror("socket"); exit(1); } strcpy(data.ifr_name,"xna0"); if (ioctl(s,SIOCENABLEBACK,&data) < 0) { perror("SIOCENABLEBACK:"); exit(1); } close(s); } ERRORS
The DEMNA errors are coded as follows: Adapter did not pass the power-up self-test during autoconfiguration time. The port attachment fails. The xna driver was unable to allocate memory for adapter data structures. The port attachment fails. The xna driver was unable to map memory for adapter data structures. The port attachment fails. The xna driver was unable to bring the adapter into the initialized state. The port attachment fails. The xna driver failed to prepare the adapter for run-time use. The xna driver was unable to bring the adapter into the initialized state during a port reset. The adapter port command failed. The error code gives reason for failure. Too many multicast requests have been made. RELATED INFORMATION
Files: arp(7), inet(7), intro(4), netstat(1) delim off xna(7)