NAME

fddiinit − initialize FDDI network interface; connect to FDDI network

SYNOPSIS

/etc/fddiinit [-l download_file] [-s] device_file

DESCRIPTION

fddiinit:

• Downloads firmware to the FDDI network interface and connects the interface to the FDDI network. 

• Must be executed for each interface present on a machine. 

• Can also be executed from within the /etc/netlinkrc script during network initialization. 

• Is also used to reinitialize and reconnect the interface after the interface has been reset.  Use the fddidstop command to reset the interface (see fddidstop(1M)).

Options and Command-Line Arguments

fddiinit recognizes the following options and command-line arguments:

-l download_file Specifies the firmware download file.  See DEPENDENCIES for machine-dependent details. 

-s (silent) Suppress the progress message.  While fddiinit is running, it periodically prints a series of dots on the terminal screen to indicate that the firmware download is in progress. 

device_file Specifies the device special file associated with the FDDI interface.  By convention, device special files are kept in the /dev directory.  Each device file has a name and a device number to uniquely identify the interface.  See DEPENDENCIES for a description of how to create device files. 

RETURN VALUE

Upon successful completion, fddiinit returns 0; otherwise, it returns 1. 

ERROR MESSAGES

fddiinit fails and the firmware is not downloaded if any of the following conditions are encountered:

• Command used incorrectly − usage message is returned. 

• Invalid device file − returns message Can’t open device file.  Check the device file.  See DEPENDENCIES for description of how to create device files. 

• Invalid download file − returns Can’t open download file or Invalid file format.  Contact your HP Customer Support representative. 

• Hardware or driver error − download was unsuccessful because of a hardware or firmware problem.  Check to ensure that hardware is correctly connected.  If the download is still unsuccessful, replace the card with a known-good unit if one is available, and retry the command.  Otherwise, contact your HP customer support representative. 

DEPENDENCIES

Series 700 EISA FDDI:

Each device file has a name and a device number to uniquely identify the interface.  To create the EISA FDDI device file manually (instead of through SAM ), specify the applicable major and minor numbers in the HP-UX /etc/mknod command.  EISA FDDI device files have the following major and minor numbers:

The following example uses /etc/mknod to create the EISA FDDI device special file /dev/lan1 on the first EISA slot:

/etc/mknod /dev/lan1 c 49 0x410000

If the FDDI interface card is configured using sam (see sam(1M)), sam creates the device file automatically and the name corresponds to the network interface name and unit.  For example, device files /dev/lan1 and /dev/lan2 are for network interfaces lan1 and lan2 respectively.  You can also use the /etc/lanscan command to display information about the network interfaces on the system. 

fddiinit requires a download file only for the EISA FDDI card.  The default download file is /etc/fddi/fddi_dnld. 

Series 700 Built-In/Integrated FDDI on 735/755:

For Integrated FDDI, the -l option does not apply. Integrated FDDI device files have a major number of 111 and a minor number of 0x209000. 

Series 800:

Device files for HPPB FDDI are created automatically by /etc/insf (see insf(1M)) when the system is rebooted after installing the HPPB FDDI driver and adapter card.  The device file name is of the form /dev/lanX where X >= 0. 

The major number for HPPB FDDI device files is 49.  The minor number containing the logical unit (lu number) is assigned based on the position of the HPPB FDDI card in the HPPB backplane relative to other LAN cards.  Each LAN card has a unique minor device number. 

To determine the device special file corresponding to a particular FDDI adapter, first use the /etc/lanscan command (see lanscan(1M)) to obtain the lu number that matches the hardware path of that adapter. Then use the /etc/lssf command (see lssf(1M)) on those files in the /dev directory that have a major number of 49 to find a file that has a matching lu number. 

mksf (see mksf(1M)) can be used to manually create a device file for the HPPB FDDI interface. 

The default download file is /etc/fddi/fddi_dnld.  This download file is used for the HPPB FDDI card. 

AUTHOR

fddiinit was developed by HP. 

FILES

/etc/fddi/fddi_dnld default FDDI download file. 

SEE ALSO

fddistop(1M), fddistat(1M), fddinet(1M), mknod(1M), lanscan(1M). 
 

Hewlett-Packard Company  —  HP-UX Release 9.03: April 1994