Black Box 16 port User Manual
3.11 Mb

How to setup BOOTP

Your nominated BOOTP server should be on the same network as the unit(s). The BOOTP server can also be on a different segment of the same network, provided that segment is connected by a bridge.

You can locate your BOOTP server on another network to the unit; this means that the bootp request and replies have to pass through a router or gateway. You must configure your router or gateway:

to pass through BOOTP requests and replies

for RIP

Note that if you have an existing unit, you do not have to enter the details of the gateway or router into the unit before using bootp. Details of gateways or routerspre-configuredin the unit will be ignored during the bootp process.

The bootptab file entry

bootptab file entry for a single unit

Find the bootptab file on the host; on UNIX systems the bootptab file is usually file /etc/ bootptab. Make an entry for the unit; an example for a single unit is shown at bootptab file entry for a single unit on page 231 on page 231. An example for multiple units is shown atbootptab file entry for multiple units on page 238.










This entry should include the ethernet address of the unit. Other standard BOOTP tags which the unit supports are listed below, together with the unit’s interpretation:

Black Box Console Server user guide



ht (hardware type) set to 1 (=10Mb ethernet).


ha (hardware address) the ethernet address of the unit.


ip (internet address) enter the ip address to assign to the unit.


sm (subnet mask) enter the subnet mask of the unit.


hn (host name) enter as :hn:\ which causes the name at the start of the


file (Console Server_blue) to be allocated to this unit.


bf (bootfile name) enter the name of the file containing specific


configuration information; see An example bootfile on page 234.


ds (domain servers)enter the ip address of up to two nameservers.


gw (gateway)enter the ip address of a single passive gateway




use the ‘gw’ flag only in very specific circumstances; see Note 5. below.



Notes on the above BOOTP tags:

1.Specify the fields that you wish; you do not have to specify all of them. E.g. if you wish to download only the internet address to the unit, specify the ip field (you must specify - as a minimum - theha andht fields).

2.If the subnet mask (sm) has not been explicitly specified by a BOOTPREPLY packet, it will be derived from the class of internet address.

3.If domain name servers are specified their port number will always be set to the default for a name server (53).

4.If you require a bootfile (bf) it must be on the same host as the bootptab file entry.

5.include the gw (gateway) flag only if your BOOTP server is on a different network and your gateway (or router) isnot configured to support RIP.

The effect of using the ‘gw’ field is:

-to make only this gateway available in the unit; it will be a passive gateway. You can view the details of the gateway only in the cli, using the ‘show routes’ command.

-to turn off RIP in the unit; i.e. the unit will ignore RIP messages broadcast on the network

-the unit will ignore gateways pre-configuredin the unit or added afterboot-up.It will respond only to the single gateway.

-you delete the gateway as follows: omit the ‘gw’ field in the bootptab file entry andre-bootthe unit. You can now add/configure active and passive gateways into the unit.

Black Box Console Server user guide


Gateways are detailed in Section Chapter 2 Installation.

Black Box Console Server user guide


The bootfile

If you wish to download basic configuration information to the unit you must create a bootfile. This file is a text file formatted in a particular style; an example is shown at An example bootfile on page 234.

Note The bootfile must be located on the same host as the bootptab file An example


# cat xxxxxxp.bfc













Notes on the above example:

1.The bootfile can have line entries for other files, e.g. a software or configuration file. The unit will download these files only if the filename has changed (excludes the pathname).

2.The format of each line entry in the file is:

PARAMETER_NAME <white space> parameter value <carriage return/line feed>

3.The parameter name must be in UPPER CASE and match exactly the strings shown in An example bootfile on page 234; e.g. AUTH_TYPE.

4.An explanation of these parameters is shown in Bootfile parameters on page 235.

5.Include only those parameters which you want to configure. For example you may not wish to download a configuration file, so omit the line beginning CONFIG_FILE (or precede the line with a hash # character).

Black Box Console Server user guide


6.If a domain name and nameserver are configured, either in the bootptab entry or in the unit’s memory, you can replace ip addresses with hostnames in lines specifying additional files; e.g.


Table 1Bootfile parameters



Brief Meaning

Fuller explanation






a filename and a full

a version of software

Appendix D Upgrading




your firmware


- all pre-fixedby




hostname/ip address




a filename and full

a set of saved

configuration parameters




which are not listed in the


- all pre-fixedby

parameters from an

BOOTPTAB file entry or


hostname/ip address

existing unit. Note:

in the bootfile. The



these parameters

parameters will not



include user

overwrite network




configuration parameters




specified in your bootfile.


on, off

access to the unit

Chapter 2 Installation



from a web browser



both, local or radius

authentication method

Chapter 2 Installation



employed by the unit




for all users



ip address in dot

default ip host for a



decimal notation

user when user




service is set to




‘telnet’ ‘rlogin’ or




‘tcp clear’



on, off

‘reverse’ line types,




‘printer’ line type and




remote configuration -




all restricted to




devices listed in the




the unit’s host table


Black Box Console Server user guide