HP-UX LAN Administrator's Guide (Feburary 2007)
Table Of Contents
- About This Document
- 1 New for the HP-UX 11i v3 Release
- 2 Installing HP-UX LAN
- 3 Configuring HP-UX LAN Using SAM
- 4 Manually Installing and Configuring HP-UX LAN
- 5 Troubleshooting HP-UX LAN
- Troubleshooting Overview
- Troubleshooting Q & A
- LAN Interface Card Statistics
- 100Base-T Checklist
- Diagnostic Flowcharts
- Flowchart 1: Configuration Test
- Flowchart 2: Configuration Test continued
- Flowchart 3: Configuration Test continued
- Flowchart 4: Network Level Loopback Test
- Flowchart 5: Network Level Loopback Test continued
- Flowchart 6: Transport Level Loopback Test (using Internet Services)
- Flowchart 7: Link Level Loopback Test
- Flowchart 8: LAN Connections Test
- Flowchart 9: Gateway Remote Loopback Test
- Flowchart 10: Gateway Remote Loopback Test continued
- Flowchart 11: Subnet Test
- 6 LAN Resources
- 7 Network Addressing
- Overview of Network Addressing Schemes
- Networking Terminology
- Network Addresses and Node Names
- Internet Addresses
- Subnet Addresses
- Configuring Gateways on Fixed-Length Subnets
- Variable-Length Subnet Addressing
- Configuring Gateways on Variable-Length Subnets
- Configuring Gateways on Supernets
- IP Multicast Addresses
- Virtual IP (VIP) Addresses
- CIDR - Classless Inter-Domain Routing
- 8 LAN Device and Interface Terminology

LAN Device and Interface TerminologyDRAFT COPY
RARP Configuration
Chapter 8144
This can be done with a text editor such as vi. This will cause /usr/sbin/rarpd to be started
at boot time.
Another file which must be modified is /etc/rarpd.conf. This is the RARP server database
file. It contains a list of entries that map hardware address to IP address for each client
interface.
The /etc/rarpd.conf file has the following format:
• A comment line is indicated by a pound sign (#) in the first column.
Other than comment lines and blank lines, all lines are considered client entries. A client
entry is of the form:
— <hardware_address> <ip_address>
where <hardware_address> consists of colon-separated (:) hexadecimal bytes, and
<ip_address> consists of dot-separated (.) decimal bytes.
Example:
— 08:00:09:22:e4:a9 15.13.106.69
There must be exactly 6 hardware address bytes.
There must be exactly 4 protocol address bytes.
Once the rarpd server is started, it will receive RARP requests over all configured network
interfaces, and it will respond to clients that have entries in the RARP database.
If the /etc/rarpd.conf file is modified while a rarpd is already running, the changes will not
be reflected in the rarpd application until it is restarted or is sent the SIGHUP signal. To see
what information is in the currently running rarpd, sending it a SIGINT signal causes it to
dump its database into /var/tmp/rarpd.db.
See the rarpd(1M) and rarpc(1M) man pages for more information.