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

Network AddressingDRAFT COPY
Subnet Addresses
Chapter 7112
Manufacturing Department subnet number = 4
Host address range: 129 to 158
Host B internet address: 192.6.12.130 for network interface lan1
Configuring Hosts on Fixed-Length Subnets Using the netconf file
There are two ways to configure a subnet mask:
• Use SAM to configure the subnet mask.
•Use the ifconfig command. These changes will disappear, however, when the system
reboots.
To set a subnet mask, you may either include it in the SUBNET_MASK variable in the
netconf file or the ifconfig command. The netconf file contains information you entered in
SAM and this information is used to start networking when the system reboots. If you
configure your network interfaces using SAM, SAM will enter the proper information in the
netconf file for you. The examples below are netconf examples for the hosts in the example
above after you have configured them in SAM:
Host A:
INTERFACE_NAME[0]=”lan0”
IP_ADDRESS[0]=”192.6.12.33”
SUBNET_MASK[0]=”255.255.255.224”
INTERFACE_NAME[1]=”lan1”
IP_ADDRESS[1]=”192.6.12.65”
SUBNET_MASK[1]=”255.255.255.224”
Host B:
INTERFACE_NAME[0]=”lan0”
IP_ADDRESS[0]=”192.6.12.36”
SUBNET_MASK[0]=”255.255.255.224”
INTERFACE_NAME[1]=”lan1”
IP_ADDRESS[1]=”192.6.12.130”
SUBNET_MASK[1]=”255.255.255.224”
Host C:
INTERFACE_NAME[0]=”lan0”
IP_ADDRESS[0]=”192.6.12.34”
SUBNET_MASK[0]=”255.255.255.224”
INTERFACE_NAME[1]=”lan0:1”
IP_ADDRESS[1]=”192.6.12.37”
SUBNET_MASK[1]=”255.255.255.224”
INTERFACE_NAME[2]=”lan1”
IP_ADDRESS[2]=”192.6.12.97”
SUBNET_MASK[2]=”255.255.255.224”