|
DHCP and BooTP Guideline
|
|
 Contents: - Overview - Configuration using DHCP/BootP - Configuring a BootP Server on Linux - Configuring a DHCP/BootP Server on Microsoft Windows NT4 - Configuring EtherPAD using SNMP Manager - Configuration using TFTP - Configuring a TFTP Server (Linux) - Configuring a TFTP Server (Ms Windows) - An Example of a TFTP File Format |
|
|
|
|
Overview
The SAN People EtherPAD may be configured to use DHCP or BOOTP to automatically configure the following settings when the EtherPAD is powered up or reboots: - Local IP Address - Local Subnet Mask - Optional Gateway Address - Optional DNS Servers - Optional Domain Name - Optional SMTP server A dedicated DHCP/BootP Server controls this process. The DHCP/BootP server may also specify a configuration file the EtherPAD should retrieve from a TFTP configuration server. MAC addresses When the EtherPAD leaves the factory, the only address associated with it will be its universally unique Ethernet address. This is also referred to as the MAC (Media Access Control) address. The MAC address is programmed at the factory and cannot be modified. It is a 12-digit hexadecimal number and is printed on a bar-coded label on the side of the unit EtherPAD MAC addresses currently begin with 0020B7. If the EtherPAD has no MAC address programmed, the unit must be returned to SAN People for re-configuration. 
|
|
|
|
|
|
Configuration using DHCP/BootP
BootP Request When an EtherPAD, with an IP address of 0.0.0.0 is powered up, it will broadcast a BootP request every 5 seconds. This request will only be broadcast on the local LAN unless there is a special gateway/router that can recognize BootP requests and forward them to a BootP server on a remote network. The BootP Request advertises the EtherPAD's MAC address to any listening BootP servers. When a BootP server receives the EtherPAD's BootP Request, it will search its BootP table for an entry that matches the EtherPAD's MAC address. BootP Reply If it finds such an entry, it will transmit a BootP Reply to the EtherPAD. The response will contain the IP address assigned to the EtherPAD as well as its network mask (as defined in the BootP table). The BootP server can also be set up to include other Network settings in the BootP reply. If you wish to change the EtherPAD's default settings (Custom Configuration) you can configure the BootP server to supply the name of the file containing the EtherPAD's configuration. The EtherPAD will then retrieve this configuration file using TFTP from the server specified.
|
|
|
|
|
|
Configuring a BootP Server on Linux
Under Linux the BootP server is typically named bootpd. Under Linux this program can usually be found in the directory /usr/sbin. Under NCR SVR4.0 it can be found in /usr/etc. The BootP table resides in a text file named bootptab. On Linux the bootptab file should be created in the directory /etc. An example of a Linux bootptab file: EtherPAD1:\ ht=ethernet:\ ha=0x0020b7000001:\ ip=192.168.111.64:\ sm=255.255.255.0:\ bf=/padcfg/test.cfg:\ gw=192.168.111.2:\ vm=rfc1048 EtherPAD2:\ ht=ethernet:\ ha=0x0020b7000002:\ ip=192.168.111.65:\ sm=255.255.255.0:\ bf=/padcfg/tcppad.cfg:\ gw=192.168.111.1:\ vm=rfc1048 .ip: IP Address .sm: Network Mask .gw: Default Gateway IP Address .ha: MAC address .bf: TFTP configuration file .vm: use RFC1048 compatible BootP replies. .ht: hardware type 'Ethernet'
|
|
|
|
|
|
|
|
|
|
|
|
Configuration using TFTP
When you configure the EtherPAD using DHCP/BootP, the filename of a text configuration file may also accompany the DHCP/BootP reply. If provided, the EtherPAD will retrieve this file, which contains more configuration options. Alternatively, these parameters may be entered using the Web Browser (recommended), Telnet, SNMP or via the Serial configuration interface. All configuration options, except those that are set via DHCP/BootP, can be configured with TFTP. An example of a TFTP file is included below and can also be found in the TFTP File Format directory on the SAN People Configuration and Utilities CD. Unlike the DHCP/BootP parameters, the TFTP parameters are added to the configuration. This means that the settings are visible when the EtherPAD configuration is accessed using one of the other configuration methods. The TFTP configuration file has the same format as used for the Command-Line Configuration with the following differences: - Comments are allowed. - Need to specify VERSION, LOGIN and PASSWORD at the top of the file. The TFTP configuration file can also be generated by configuring the EtherPAD and then selecting the View Configuration File option. Save the displayed file and reset the EtherPAD back to factory defaults.
|
|
|
|
|
|
Configuring a TFTP Server (Linux)
Under Linux, the TFTP server is typically named tftpd. This program can usually be found in the directory /usr/sbin and can be enabled by removing the comment on the line starting with TFTP in the file /etc/inetd.conf. Configuration files are usually stored in the directory /tftpboot.
|
|
|
|
|
|
Configuring a TFTP Server (Ms Windows)
Microsoft Windows does not ship with a TFTP server (only a TFTP client) and none is available from Microsoft. You can find a Freeware TFTP server on the SAN People Products CD under the Additional Software/TFTP directory. Alternatively a number of 3rd party vendors supply such a TFTP server for Windows at a nominal cost. Note: Should the EtherPAD fail to operate correctly after being moved to another domain or network, or not be able to use BootP after having been configured with and IP address, resetting the EtherPAD to factory defaults and then reconfiguring the required options will usually solve the problem.
|
|
|
|
|
|
An Example of a TFTP File Format
Note: Anything text that appears after a hash Character (#) is a comment and is not part of the configuration commands. For example: # this is a comment. Comments can be used in a TFTP file, but not in the command line configuration. ######################################## ########## TFTP FILE FORMAT ############ VERSION = "3" LOGIN = "root" PASSWORD = "xxx" RootPassword = "xxx" ConfirmRootPassword = "xxx" UserPassword = "user" ConfirmUserPassword = "user" DebugAll = "yes" DebugIP = "yes" DebugTCP = "yes" DebugPPP = "no" DebugModbus = "no" DebugFileSystem = "yes" INDEX = "eth0" IPAddress = "192.168.2.163" NetworkMask = "255.255.248.0" INDEX = "192.168.0.0" ADDROW RoutingTable 192.168.0.0 RouteGeneratingMask = "0.0.0.0" RouteGatewayIPAddress = "192.168.0.10" RouteInterfaceName = "eth0" RIP = "disabled" IpForwarding = "disabled" DnsServer1 = "0.0.0.0" DnsServer2 = "0.0.0.0" DnsServer3 = "0.0.0.0" DnsDomainName1 = "" DnsDomainName2 = "" DnsDomainName3 = "" DnsStaticHost1 = "" DnsStaticAddress1 = "0.0.0.0" DnsStaticHost2 = "" DnsStaticAddress2 = "0.0.0.0" DnsStaticHost3 = "" DnsStaticAddress3 = "0.0.0.0" DnsStaticHost4 = "" DnsStaticAddress4 = "0.0.0.0" DnsStaticHost5 = "" DnsStaticAddress5 = "0.0.0.0" SnmpManager = "255.255.255.255" SnmpTrapDest = "0.0.0.0" SMTPServer = "" Hostname = "" INDEX = "com1" ADDROW PppTable com1 PppInterfaceType = "asyncSerial" PppMRU = "1500" PppReceiveACCMap = "FFFFFFFFH" PppUseMagicNr = "yes" PppUseProtocolCompression = "yes" PppUseACFCompression = "yes" PppLocalPAPId = "" PppLocalPAPPassword = "" PppRemotePAPId = "" PppRemotePAPPassword = ""v PppInitialLocalIP = "0.0.0.0" PppInitialRemoteIP = "0.0.0.0" PppDefaultRoute = "yes" PppSilent = "no" PppPassive = "no" PppIdleTimeout = "0" INDEX = "com1" SerialDataBits = "8" SerialStopBits = "1" SerialParity = "none" SerialSpeed = "19200" SerialFlowControl = "none" SerialType = "rs232" SerialProtocol = "ppp" SerialMaxMessageLen = "64" SerialMessageTimeout = "100" SerialUseMessageTerminator = "no" SerialMessageTerminator = "13" SerialModemAccess = "dial-in" SerialModemInit = "" SerialModemReset = "" SerialModemDialType = "tone" SerialTelephoneNumber = "" SerialTC500Address = "01" mbmIdleTimeout = "2000" mbsNetworkTimeout = "0" INDEX = "com1" sysContact = "techsupport@sanpeople.com" sysName = "EtherPAD West" sysLocation = "Jupiter" ######################################## ########################################
|
|