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
Configuring Gateways on Fixed-Length Subnets
Chapter 7116
Configuring Gateways on Fixed-Length Subnets
Besides using the appropriate subnet masks, each gateway needs to be configured so that it
can properly route messages among the several subnetworks. Following are descriptions of
two types of routing: explicit routing and dynamic routing. When using explicit routing, you
must specify the IP address of each gateway to which you are directly connected. When using
dynamic routing, you need to specify only the IP address of one gateway, and the system
learns the IP address of other gateways from the specified gateway.
Explicit Routing
There are many ways to set up routing. For example, you might use the route command or you
may add the following entries to the netconf file on Host A in Figure 7-8:
ROUTE_DESTINATION[0]=”net 192.6.12.128”
ROUTE_GATEWAY[0]=”192.6.12.36”
ROUTE_COUNT[0]=”1”
ROUTE_DESTINATION[1]=”net 192.6.12.96”
ROUTE_GATEWAY[1]=”192.6.12.34”
ROUTE_COUNT[1]=”1”
ROUTE_DESTINATION[2]=”net default”
ROUTE_GATEWAY[2]=”192.6.12.35”
ROUTE_COUNT[2]=”1”
The 1 in each ROUTE_COUNT entry specifies an indirect route. For example, messages for
the system on the 192.6.12.128 subnetwork will first be sent to Host B (192.6.12.36), and from
there they will be forwarded to the destination system.
Dynamic Routing
Alternatively, and perhaps the easiest way to manage growth on the 192.6.12 network, you
might add the following entries to each netconf file.
Hosts A, B and C:
ROUTE_DESTINATION[0]=”default”
ROUTE_GATEWAY[0]=”192.6.12.35”
ROUTE_COUNT[0]=”1”
Host D (Site gateway):
ROUTE_DESTINATION[0]=”net 192.6.12.64”
ROUTE_GATEWAY[0]=”192.6.12.33”
ROUTE_COUNT[0]=”1”