![]() | ![]() |
[53]Although not directly related to network topology, one of the best things you can do for your diskless clients is to load them with an adequate amount of memory so that they can perform aggressive caching and reduce the number of round trips to the server.Booting a client through a router is less than ideal, since the diskless client's root and swap partition traffic unnecessarily load the packet forwarding bandwidth of the router. However, if necessary, a diskless client can be booted through a router as follows:
In Solaris, in.rarpd takes the network device name and the instance number as arguments. In this example we start in.rarpd on /dev/hme0, the network interface attached to the diskless client's network. in.rarpd uses the ethers, hosts, and ipnodes databases[54] to map the requested Ethernet address into the corresponding IP address. The IP address is then returned to the diskless client in a RARP reply message. The diskless client must be listed in both databases for in.rarpd to locate its IP address.in.rarpd hme 0
[54]The ethers database is stored in the local file /etc/ethers or the corresponding NIS map. The hosts and ipnodes database is located in the local files /etc/inet/hosts and /etc/inet/ipnodes, or DNS and NIS maps. The search order depends on the contents of the name switch configuration file /etc/nsswitch.conf.
![]() | ![]() | ![]() |
17.3. Network infrastructure | ![]() | 17.5. Protocol filtering |
Copyright © 2002 O'Reilly & Associates. All rights reserved.