Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #851
Difficulty: Medium
Angular is a TypeScript-based open-source web application framework.
True or False?
Linux & Unix Commands - Search Man Pages

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

mfa(7)							 Miscellaneous Information Manual						    mfa(7)

NAME
mfa - DEMFA FDDI Network Interface SYNOPSIS
config_driver mfa DESCRIPTION
The mfa interface is a high speed XMI adapter to a 100 Mbit/second Fiber Distributed Data Interface (FDDI) timed token ring network adapter. The mfa 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 mfa interface employs the address resolution protocol described in arp(7) to map dynamically between Internet and FDDI addresses on the local network. The maximum frame size for the mfa interface is 4500 bytes, which is substantially larger that the 1500 bytes maximum packet size of the Ethernet interfaces. The mfa 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 DEMFA adapter. The physical address of the DEMFA adapter can be changed by use of the SIOCSPHYSADDR ioctl. The SIOCADDMULTI and SIOCDELMULTI ioctls can be used to add or delete multicast addresses. The DEMFA supports up to 15 multicast addresses. The SIOCRDCTRS ioctl can be used to read the FDDI driver counters. The DEMFA adapter status and characteristics can also be read through this ioctl by providing a FDDISTATUS flag . The argument to this ioctl is a pointer to a counter or status structure, ctrreq, found in <net/if.h>. The SIOCENABLBACK and SIOCDISABLBACK ioctls can be used to enable and disable the interface loopback mode, respectively. The SIOCIFRESET ioctl can be used to reset the adapter. 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,"mfa0"); 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 reset the adapter, use the SIOCIFRESET 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,"mfa0"); if (ioctl(s,SIOCIFRESET,&data) < 0) { perror("SIOCIFRESET:"); exit(1); } close(s); } ERRORS
Diagnostic error messages contain information provided by the mfa driver. For example: The DEMFA adapter did not pass the power-up selftest during autoconfiguration. The DEMFA is unable to allocate system memory or cluster mbufs for device initialization. The DEMFA cannot transition to the initialized state. An interrupt has been received with no packets found. An internal command to the device has failed to complete on time. An internal command to the device has returned an error. The DEMFA has received an unknown type of unsolicited interrupt about the FDDI ring state. The DEMFA has received an unsolicited interrupt, the FDDI ring state has been changed. The DEMFA was unable to change FDDI characteristics and restart. An attempt was made to add more than 15 multicast addresses to the device. The DEMFA has failed internal self test during a reset operation. The DEMFA has failed to re-initialize after a reset operation. The DEMFA has encountered a hard error which should cause the device to reset. RELATED INFORMATION
netstat(1), arp(7), inet(7), intro(7), fddi_config(8) delim off mfa(7)

Featured Tech Videos