Use at the server console to link a communication protocol to a network board and its LAN driver. Unless you link the protocol to the board, the board can't process packets.
You can also use INETCFG to link the network boards and their LAN drivers to the communication protocols.
NOTE:Before you bind a protocol to a network board and LAN driver, you must install the network board and load the LAN driver.
BIND protocol [TO] lan driver | board name [driver parameter...] [protocol parameter...]
Parameter |
Use to |
---|---|
protocol |
Specify the communication protocol. |
lan driver | board name |
Specify either the LAN driver name or the network board name. |
driver parameter |
Identify a particular network board. If you specified a network board name, you do not need to specify driver parameters. If you specified a LAN driver and your server has more than one instance of the LAN driver loaded, use a driver parameter to specify the particular board the driver is running. For a list of valid driver parameters, see Driver Parameters. |
protocol parameter |
Specify the protocol parameters required for the protocol you are binding. See Protocol Parameters. |
Depending on your system, one or more of the following parameters can be used to identify a particular board.
You may not need to use the BIND command unless you want to add new LAN drivers after the initial server installation.
You can also use INETCFG to load and bind LAN drivers. INETCFG places the BIND statements in the initsys.cfg file.
If you use only the IPX/SPX™ protocol, you can add the BIND statement to the autoexec.ncf file.