HP - LAN Administration

HP-UX LAN Administrators Guide
HP-UX 11i v2
Manufacturing Part Number : B2355-90796
E0903
Uni ted States
Copyri ght 2003 Hewl ett-Packard Devel opment Company L.P. Al l ri ghts reserved.
ii
Legal Notices
The i nformati on i n thi s document i s subject to change wi thout noti ce.
Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but
not limited to, the implied warranties of merchantability and tness for a particular purpose.
Hewl ett-Packard shal l not be hel d l i abl e for errors contai ned herei n or di rect, i ndi rect,
speci al , i nci dental or consequenti al damages i n connecti on wi th the furni shi ng, performance,
or use of thi s materi al .
Warranty
A copy of the speci c warranty terms appl i cabl e to your Hewl ett- Packard product and
repl acement parts can be obtai ned from your l ocal Sal es and Servi ce Ofce.
U.S. Government License
Propri etary computer software. Val i d l i cense from HP requi red for possessi on, use or copyi ng.
Consi stent wi th FAR 12.211 and 12.212, Commerci al Computer Software, Computer Software
Documentati on, and Techni cal Data for Commerci al I tems are l i censed to the U.S.
Government under vendor's standard commerci al l i cense.
Copyright Notice
Copyri ght 1997-2003 Hewl ett-Packard Devel opment Company L.P. Al l ri ghts reserved.
Reproducti on, adaptati on, or transl ati on of thi s document wi thout pri or wri tten permi ssi on i s
prohi bi ted, except as al l owed under the copyri ght l aws.
Trademark Notices
UNI X i s a regi stered trademark i n the Uni ted States and other countri es, l i censed
excl usi vel y through The Open Group.
I ntel and I tani um are regi stered trademarks of I ntel Corporati on.
Contents
iii
About This Document
New for the HP-UX 11i v2 Release
1. Installing HP-UX LAN
Overvi ew. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Checki ng LAN I nstal l ati on Prerequi si tes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Loadi ng LAN Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
I nstal l i ng LAN Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Conguring HP-UX LAN Using SAM
Overvi ew of Congurati on Usi ng SAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Conguri ng the Network I nterface Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Conguri ng Network Connecti vi ty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Veri fyi ng the I nstal l ati on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Reconguri ng I P Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3. Manually Installing and Conguring HP-UX LAN
Creati ng a New Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Veri fyi ng LAN Devi ce Fi l es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Edi ti ng Dri ver Congurati on Fi l es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Edi ti ng LAN Congurati on Fi l es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Modi fyi ng the Hewl ett-Packard Stati on Address (opti onal ). . . . . . . . . . . . . . . . . . . . 24
Edi ti ng /etc/rc.cong.d/netconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Executi ng the Network Congurati on Scri pt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Creati ng the /etc/hosts Fi l e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Network and System Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Acti vati ng Opti onal Network Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Modi fyi ng the /etc/servi ces Fi l e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Creati ng the /etc/networks Fi l e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Modi fyi ng the /etc/protocol s Fi l e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4. Troubleshooting HP-UX LAN
Troubl eshooti ng Overvi ew. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Troubl eshooti ng Q & A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
LAN I nterface Card Stati sti cs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
RFC 1213 MI B I I STATI STI CS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
RFC 1284 Ethernet-Li ke I nterface Stati sti cs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Contents
iv
100Base-T Checkl i st . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Di agnosti c Fl owcharts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Fl owchart 1: Congurati on Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Fl owchart 2: Congurati on Test conti nued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Fl owchart 3: Congurati on Test conti nued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Fl owchart 4: Network Level Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Fl owchart 5: Network Level Loopback Test conti nued. . . . . . . . . . . . . . . . . . . . . . . . 67
Fl owchart 6: Transport Level Loopback Test (usi ng I nternet Servi ces) . . . . . . . . . . 69
Fl owchart 7: Li nk Level Loopback Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Fl owchart 8: LAN Connecti ons Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Fl owchart 9: Gateway Remote Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Fl owchart 10: Gateway Remote Loopback Test conti nued . . . . . . . . . . . . . . . . . . . . . 78
Fl owchart 11: Subnet Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
5. LAN Resources
HP-UX Man Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Loggi ng and Traci ng Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Contacti ng Your HP Representati ve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
6. Network Addressing
Overvi ew of Network Addressi ng Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Networki ng Termi nol ogy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Routes and Protocol s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Network I nterface Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Routi ng Tabl e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
ARP Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Network Addresses and Node Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
I nternet Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
I nternet Address Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Assi gni ng an I nternet Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Subnet Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Sel ecti ng a Subnet Addressi ng Scheme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Fi xed-Length Subnet Addressi ng . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Conguri ng Gateways on Fi xed-Length Subnets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Contents
v
Expl i ci t Routi ng . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Dynami c Routi ng . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Proxy ARP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Vari abl e-Length Subnet Addressi ng . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Assi gni ng Vari abl e-Length Subnet Masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Conguri ng Gateways on Vari abl e-Length Subnets . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Expl i ci t Routi ng . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Dynami c Routi ng . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Proxy ARP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Conguri ng Gateways on Supernets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
I P Mul ti cast Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
I P Mul ti cast Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Ethernet Mul ti cast Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Mul ti cast Routi ng . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Vi rtual I P (VI P) Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
CI DR - Cl assl ess I nter-Domai n Routi ng. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
7. LAN Device and Interface Terminology
I nterfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
RARP Congurati on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Setti ng Up a RARP Cl i ent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Setti ng Up a RARP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Contents
vi
vii
About This Document
Thi s document descri bes how to i nstal l , congure, and troubl eshoot HP-UX 11i v2 LAN
transport software.
The document pri nti ng date and part number i ndi cate the documents current edi ti on. The
pri nti ng date wi l l change when a new edi ti on i s pri nted. Mi nor changes may be made at
repri nt wi thout changi ng the pri nti ng date. The document part number wi l l change when
extensi ve changes are made.
Document updates may be i ssued between edi ti ons to correct errors or document product
changes. To ensure that you recei ve the updated or new edi ti ons, you shoul d subscri be to the
appropri ate product support servi ce. See your HP sal es representati ve for detai l s.
The l atest versi on of thi s document can be found onl i ne at docs.hp.com, under the
Networki ng and Communi cati ons topi c, under HP-UX LAN. Speci cal l y, thi s i s at:
docs.hp.com/hpux/netcom/index.html#HP-UX%20LAN.
Intended Audience
Thi s document i s i ntended for system and network admi ni strators responsi bl e for i nstal l i ng,
conguri ng, and managi ng HP-UX 11i v2 LAN transport software. Admi ni strators are
expected to have knowl edge of Transmi ssi on Control Protocol /I nternet Protocol (TCP/I P)
networki ng concepts and network congurati on. As wel l , i t i s hel pful to have a worki ng
knowl edge of operati ng system concepts, commands, and congurati on.
Thi s document i s not a tutori al .
New and Changed Documentation in This Edition
Thi s gui de i s for the HP-UX 11i v2 rel ease onl y. I t has been updated from I nstalling and
Administering LAN/ 9000 Software (Edition 10). Overal l , thi s document has onl y had mi nor
modi cati ons to reect changes speci c to HP-UX 11i v2.
viii
Publishing History
Whats in This Document
Thi s manual provi des i nformati on for i nstal l i ng and admi ni steri ng the HP-UX LAN product.
The HP-UX LAN product al l ows HP computers to connect to an I EEE 802.3 or Ethernet Local
Area Network. An HP-UX LAN network can be further extended vi a bri dges and routers i nto
a Wi de Area Network.
Thi s manual al so i ncl udes some i nformati on that may be useful for conguri ng other HP-UX
l i nk products, such as 10/100Base-T PCI . Speci cal l y, thi s i nformati on i ncl udes:
Manual congurati on of l i nks
Network addressi ng
LAN devi ce and i nterface termi nol ogy
The i nformati on i n thi s manual i s i ntended for network managers or operators who i nstal l
and admi ni ster HP-UX LAN on TCP/I P networks. I t i s assumed the reader i s experi enced
wi th HP-UX and i s fami l i ar wi th the basi cs of l ocal and wi de area networki ng.
The manual i s organi zed as fol l ows:
Chapter 1 Installing HP-UX LAN descri bes how to i nstal l HP-UX LAN software.
Chapter 2 Conguring HP-UX LAN Using SAM descri bes the steps to congure
HP-UX LAN software automati cal l y usi ng the System Admi ni strati on
Manager (SAM).
Chapter 3 Manually Installing and Conguring HP-UX LAN descri bes the steps
to bui l d the kernel , create devi ce l es, and manual l y congure HP-UX LAN
usi ng the vi edi tor.
Table1 Publishing History Details
Document
Manufacturing
Part Number
Operating
Systems
Supported
Publication
Date
B2355-90796 11i v2 Jul y 2003
B2355-90748 11i v1.6, 11i
v1, 11.0, 10.x
March 2002
ix
Chapter 4 Troubleshooting HP-UX LAN provi des owcharts to hel p di agnose
HP-UX LAN software and hardware probl ems. Thi s chapter al so descri bes
LAN card status val ues and stati sti cs returned by lanadmin.
Chapter 5 LAN Resources provi des references to other useful tool s for i nstal l i ng,
conguri ng, and mai ntai ni ng HP-UX LAN software.
Chapter 6 Network Addressing denes networki ng terms and expl ai ns network
i nterface names, network addresses, names and subnets. The i nformati on i n
thi s chapter i s appl i cabl e to conguri ng other HP-UX l i nk products on
TCP/I P networks.
Chapter 7 LAN Device and Interface Terminology denes terms used by the I /O
system to i denti fy LAN cards and devi ce l es.
IMPORTANT HP-UX 11i v2, by defaul t, supports I Pv6 transport. Thi s gui de does not i ncl ude
I Pv6 transport i nformati on. Refer to HP-UX I Pv6 Transport Administrators
Guide and HP-UX I Pv6 Porting Guide for I Pv6 transport i nformati on on
HP-UX 11i v2.
NOTE Thi s manual does not contai n the procedures for addi ng and repl aci ng PCI
cards usi ng OLA/R. OLA/R stands for On Li ne Addi ti on and Repl acement. Thi s
refers to the abi l i ty of a PCI I /O card to be repl aced (removed and/or added) to
an HP-UX computer system desi gned to support thi s feature wi thout the need
for compl etel y shutti ng down, then rebooti ng the system or affecti ng other
system components.
I f you want to uti l i ze the OLA/R feature that your system provi des, refer to the
I nterface Card OL* Support Guide.
HP-UX Release Name and Release Identier
Each HP-UX 11i rel ease has an associ ated rel ease name and rel ease i denti er. The uname(1)
command wi th the -r opti on returns the rel ease i denti er. Thi s tabl e shows the rel eases
avai l abl e for HP-UX 11i .
Table2 HP-UX 11i Releases
Release
Identier
Release Name
SupportedProcessor
Architecture
B.11.23 HP-UX 11i v2 I ntel I tani um
x
Related Documents
HP Documentation
Addi ti onal i nformati on about HP-UX LAN can be found wi thi n docs.hp.comi n the networking
and communications col l ecti on under HP-UX LAN at:
http://www.docs.hp.com/hpux/netcom/index.html#HP-UX%20LAN
Addi ti onal i nformati on about HP-UX I Pv6 transport software can be found wi thi n
docs.hp.com i n the networking and communications col l ecti on under I Pv6 at:
http://www.docs.hp.com/hpux/netcom/index.html#IPv6
Related RFCs
Thi s secti on provi des a l i st of the protocol s and standards on whi ch the HP-UX LAN products
are based. The I ETF (I nternet Engi neeri ng Task Force) RFCs l i sted bel ow can be l ocated at:
http://www.ietf.org/rfc.html.
B.11.22 HP-UX 11i v1.6 I ntel I tani um
B.11.20 HP-UX 11i v1.5 I ntel I tani um
B.11.11 HP-UX 11i v1 PA-RI SC
Table3 LAN Protocols and Standards
For Information
on:
Read:
Subnetti ng RFC 950, RFC 1122
Cl assl ess I nter-
Domai n Routi ng
RFC1519
Requi rements for I P
Versi on 4 Routers
RFC 1812
Table2 HP-UX 11i Releases (Continued)
Release
Identier
Release Name
SupportedProcessor
Architecture
xi
Vari abl e Length
Subnet Tabl e
RFC 1878
Protocol s: Address
Resol uti on Protocol
(ARP)
RFC 826
Domai n
Requi rements
RFC 920
Domai n Name
Server
RFC 1034, 1035, 1535
I nternet Control
Message Protocol
(I CMP)
RFC 792
I nternet Protocol
(I P)
MI L-STD 1777; RFC 791
Standard for the
Format of ARPA
I nternet Text
Messages
RFC 822
Transmi ssi on
Control Protocol
(TCP)
MI L-STD 1788; RFC 793, 813, 814, 816, 817,
179, 889, 896, 1122, 1323, 2018, 2414, 2581,
2582
I P Mul ti cast RFC 1112
Path MTU Di scovery RFC 1191
Wi ndow Scal i ng RFC 1323
Reverse Address
Resol uti on Protocol
(RARP)
RFC 903
Table3 LAN Protocols and Standards (Continued)
For Information
on:
Read:
xii
HP Welcomes Your Comments
HP wel comes your comments concerni ng thi s document. We are trul y commi tted to provi di ng
documentati on that meets your needs.
Pl ease send comments to: neti nfo_feedback@cup.hp.com
Pl ease i ncl ude document ti tl e, manufacturi ng part number, and any comment, error found, or
suggesti on for i mprovement you have concerni ng thi s document. Al so, pl ease tel l us what you
l i ke, so we can i ncorporate i t i nto other documents.
DRAFT COPY
xiii
New for the HP-UX 11i v2 Release
The HP-UX 11i v2 rel ease has the fol l owi ng transport (I P, TCP, and UDP) changes:
Transport support for I Pv6
I Pv6 i s the next generati on I nternet Protocol . I Pv6 requi res support from hosts and
routers. HP-UX 11i v2 I Pv6 transport software provi des host support for I Pv6.
Wi th onl y a few congurati on steps, an I Pv6 i nterface can be enabl ed, and you can use the
functi onal features of I Pv6 and I Pv6-enhanced components for HP-UX 11i v2.
NOTE The fol l owi ng software currentl y offers I Pv6 support: Transport, I nternet
Servi ces, DCE, DLPI , FDDI , SAM-NNC, Li bc, Commands, Desktop (CDE),
X11R6-based appl i cati ons, EMS, Onl i ne Di agnosti cs, SNMP, nettl , I PSec,
Kerberos Cl i ent, Servi ce Guard, Gl ance, HP-UX Secure Shel l , Apache and
JVM. Refer to product-speci c documentati on for more i nformati on.
I f you are not pl anni ng to use I Pv6 software, there i s no i mpact to you. Even though the
software i s i ncl uded, other than a few new l es and man pages, there are no acti ons
requi red to not use I Pv6.
To l earn more about I Pv6 transport on HP-UX 11i v2, refer to the fol l owi ng
documentati on, al l avai l abl e at:http://docs.hp.com/hpux/netcom/i ndex.html #I Pv6
HP-UX I Pv6 Transport Administrators Guide
HP-UX I Pv6 Porting Guide
I Pv6 Support secti on of HP-UX 11i Version 2 Release Notes
NOTE Thi s Gui de onl y covers I Pv4 rel ated transport i nformati on. I t does not cover
I Pv6 rel ated transport i nformati on.
Transport Support for HP-UX 11i v2 DLPI enhancements
An OOP (Opti ons negoti ati ons and Out-of-Packet) header has been added to the front of al l
I P packets for both i nbound packets from DLPI l ayer and outbound packets to DLPI l ayer.
Thi s change supports the HP-UX 11i v2 DLPI enhancements to the Streams I nterface to
provi de a ri cher feature set for network stack feature opti ons.
DRAFT COPY
xiv
Enhancements to CKO (Check-sum Ofoad) i nterfaces between transport and DLPI .
Thi s change makes the CKO i nterfaces more general wi th respect to the types of
checksum ofoad hardware that HP wi l l support, and adds sufci ent exi bi l i ty to the
i nterface that supports checksum ofoad for future transport protocol s. Thi s change
i ncorporates the DLPI OOP header to carry the type of checksum ofoad and the ofoaded
checksum i tsel f.
The transport i nternal kernel header l e, net/cko.h has been modi ed to support thi s
enhancement. Kernel I P Stream modul es that previ ousl y used opti ons for fastpath
negoti ati on features or l ooked i nto network data packets i n previ ous versi ons must make
changes and recompi l e for HP-UX 11i v2.
Chapter 1 1
1 Installing HP-UX LAN
Thi s chapter descri bes the manual procedures to l oad HP-UX LAN software and to i nstal l
LAN hardware onto your system.
Installing HP-UX LANDRAFT COPY
Overview
Chapter 1 2
Overview
Thi s chapter contai ns the fol l owi ng secti ons:
Step 1: Checki ng LAN I nstal l ati on Prerequi si tes
Step 2: Loadi ng LAN Software
Step 3: I nstal l i ng LAN Hardware
IMPORTANT I f you have a system wi th HP-UX LAN pre-i nstal l ed on i t, you may ski p thi s
chapter and go di rectl y to chapter 2. Execute the command lanscan to
determi ne i f the HP-UX LAN software and hardware have been pre-i nstal l ed.
I f, i n addi ti on, you have a precongured system, you may al so ski p chapter 2,
Conguri ng LAN Usi ng SAM.
I f you are unfami l i ar wi th HP-UX LAN products or networki ng concepts, HP recommends
that you read the NetworkingOverviewmanual , as wel l as Chapter 6, Network Addressi ng,
and Chapter 7, LAN Devi ce and I nterface Termi nol ogy, of thi s gui de before begi nni ng
HP-UX LAN i nstal l ati on.
DRAFT COPY Installing HP-UX LAN
Checking LAN Installation Prerequisites
Chapter 1 3
Checking LAN Installation Prerequisites
Pri or to l oadi ng the HP-UX LAN product onto your system, check that you have met the
fol l owi ng hardware and software prerequi si tes:
Check that /usr/bin, /usr/sbin, and /sbin are i n your PATH usi ng the command:
echo $PATH
The operati ng system shoul d have been upgraded to HP-UX 11i v2 software. To obtai n
thi s i nformati on, execute the command:
uname -a
Pri or to i nstal l i ng HP-UX LAN, HP recommends that you create a network map or update
the exi sti ng map of your network. Refer to chapter 6 for a sampl e LAN network map and
sampl e worksheet.
You have the appropri ate cabl i ng for your LAN card.
You have the i nstal l ati on and servi ce manual for your network card.
You have an I P address, subnet mask (opti onal ), and host name al i as for your new LAN
card.
You have superuser capabi l i ty.
Loading LAN Software
Chapter 1 4
Loading LAN Software
Fol l ow the steps bel ow to l oad the HP-UX LAN software usi ng the HP-UX swinstall
program.
1. Log i n as root.
2. Check that /usr/bin, /usr/sbin, and /sbin are i n your PATH.
3. I nsert the software medi a i nto the appropri ate dri ve.
4. Run the swinstall program usi ng the command:
swinstall
Thi s opens the Software Sel ecti on Wi ndow and Speci fy Source Wi ndow.
5. Change the Source Host Name i f necessary, enter the mount poi nt of the dri ve i n the
Source Depot Path el d, and acti vate the OK button to return to the Software Sel ecti on
Wi ndow. Acti vate the Hel p button for more i nformati on.
The Software Sel ecti on Wi ndow now contai ns a l i st of avai l abl e software to i nstal l .
6. Hi ghl i ght the Networki ng software.
7. Choose Mark for Install from the Acti ons menu to choose the product to be i nstal l ed.
8. Choose Install from the Acti ons menu to begi n product i nstal l ati on and open the
I nstal l Anal ysi s Wi ndow.
9. Acti vate the OK button i n the I nstal l Anal ysi s Wi ndow when the Status el d di spl ays a
Ready message.
10. Acti vate the Yes button at the Conrmati on Wi ndow to conrm that you want to i nstal l
the software.
Vi ew the I nstal l Wi ndow to read processi ng data whi l e the software i s bei ng i nstal l ed,
unti l the Status el d i ndi cates Ready and the Note Wi ndow opens.
swinstall l oads the l eset, runs the control scri pts for the l eset, and bui l ds the kernel .
11. Acti vate the OK button on the Note Wi ndow to reboot the system.
The user i nterface di sappears and the system reboots.
12. When the system reboots, check the swinstall l og l e i n /var/adm/sw to make sure that
the i nstal l ati on was successful .
For addi ti onal i nformati on on the HP-UX swinstall program, refer to HP-UX 11i Version 2
I nstallation and Update Guide.
DRAFT COPY Installing HP-UX LAN
Installing LAN Hardware
Chapter 1 5
Fol l ow the steps bel ow to prepare the system for i nstal l ati on of your network i nterface
hardware.
1. At the HP-UX prompt, execute the command:
shutdown -h
Wai t for the system to respond wi th a message i ndi cati ng that the system has been
hal ted.
2. Observe anti stati c precauti ons by fol l owi ng the gui del i nes as descri bed i n the i nstal l ati on
i nstructi ons i n the hardware manual or the Anti stati c Precauti ons Note.
3. I nstal l your network i nterface card by referri ng to your hardware i nstal l ati on and servi ce
manual .
CAUTION HP recommends not rearrangi ng any network i nterface cards i nstal l ed i n
your system. I f you move any exi sti ng network i nterface card i n the system,
you may need to recongure the I P address. See Reconguri ng I P
Addresses secti on i n the next chapter.
4. Power up the system to compl ete the process. The network i nterface card wi l l run a
sel f-test automati cal l y. Any error messages wi l l appear on the termi nal di spl ay or system
consol e.
5. Proceed to chapter 2, Conguri ng HP-UX LAN Usi ng SAM.
Chapter 1 6
Chapter 2 7
2 Conguring HP-UX LAN Using SAM
Thi s chapter descri bes how to congure LAN usi ng SAM, the System Admi ni strati on
Manager. I t contai ns the fol l owi ng secti ons:
Overvi ew of Congurati on Usi ng SAM
Conguring HP-UX LAN Using SAMDRAFT COPY
Chapter 2 8
Step 1: Conguri ng the Network I nterface Card
Step 2: Conguri ng Network Connecti vi ty
Step 3: Veri fyi ng the I nstal l ati on
Step 4: Reconguri ng I P Addresses
DRAFT COPY Conguring HP-UX LAN Using SAM
Overview of Conguration Using SAM
Chapter 2 9
Overview of Conguration Using SAM
Once you have i nstal l ed hardware and software, you can use SAM to automati cal l y congure
networki ng.
SAM stands for System Admi ni strati on Manager, a menu-dri ven uti l i ty for system
admi ni strati on tasks, i ncl udi ng congurati on of networki ng software. SAM has two user
i nterfaces, an X-Wi ndows system i nterface and a text termi nal i nterface. The pri mary
components and functi onal i ty of SAM are the same for both i nterfaces. The di fferences are the
screen appearance and the navi gati on methods.
You can access the SAM on-l i ne hel p system usi ng the fol l owi ng methods:
Choose an i tem from the Hel p menu (l ocated i n the menu bar) for i nformati on about the
current SAM screen, keyboard navi gati on wi thi n SAM, and the versi on of SAM on your
system.
Acti vate the HELP button from a di al og or message box for i nformati on about the
attri butes and tasks you can perform from the currentl y di spl ayed wi ndow.
Press the F1 key for context-sensi ti ve i nformati on for the object at the l ocati on of the
cursor.
Usi ng SAM to congure HP-UX LAN can be di vi ded i nto two procedures:
1. Conguri ng the Network I nterface Card.
2. Conguri ng Network Connecti vi ty.
Fol l ow Step 1 to add the I P address, any al i as names, and, i f the LAN card i s on a subnetwork,
enter the subnet mask for your card. Thi s procedure wi l l automati cal l y i ni ti al i ze the LAN l i nk
and attach your node to the l ocal area network (LAN). Fol l ow Step 2 to add remote system
names and remote system I P addresses for network connecti vi ty, and al so to speci fy defaul t
gateway i nformati on.
Conguring the Network Interface Card
Chapter 2 10
NOTE Make sure the LAN card and dri ver are i nstal l ed i n the system before you use
SAM to congure the software.
Log i n as root and do the fol l owi ng:
1. At the HP-UX prompt, type: sam
2. Sel ect the Networking and Communications i tem of the SAM mai n wi ndow.
3. Sel ect the Network Interface Cards i tem of the Networking and Communications
wi ndow.
4. Doubl e-cl i ck the LAN card that you want to congure from the object l i st.
5. Veri fy that the hardware path i s correct for your LAN card (by compari ng the hardware
path on the Congure LAN Card wi ndow wi th the hardware path from the output of the
commands ioscan -fdbtlan and lanscan -v).
6. I f you are conguri ng the rst l ogi cal i nterface for a card type (al so cal l ed the i ni ti al
i nterface), hi ghl i ght the card and choose Configure from the Acti ons menu to open the
Configure LAN Card wi ndow.
I f you are addi ng l ogi cal i nterfaces to a card type, choose Add IP Logical Interface
from the Acti ons menu to open the Configure LAN Card wi ndow.
a. Enter the i nformati on about the LAN card. To do so, press the Tab key to move
through the data entry el ds.
NOTE SAM di spl ays the Card Name, Hardware (H/W) Path, and Stati on
Address el ds wi th the appropri ate val ues. These el ds cannot be
modi ed.
b. Choose the Card Type of your LAN card. The defaul t i s Ethernet. SNAP802.3 can be
sel ected.
NOTE The Enabl e DHCP button speci es that the system i s a Dynami c Host
Congurati on Protocol (DHCP) cl i ent. I f you acti vate thi s button, the I P
parameters for thi s system wi l l be set usi ng DHCP.
Chapter 2 11
c. Enter the I nternet address for your LAN card.
Upon exi ti ng the I nternet Address el d, SAM checks to make sure that the I P address
you entered i s correctl y formatted and i s not currentl y i n use.
d. Speci fy whether your LAN card wi l l be on a subnetwork or supernet.
The Subnet Mask el d can contai n a xed-l ength subnet mask, a vari abl e-l ength
subnet mask, or a supernet mask. Enter the appropri ate type of mask for your
network addressi ng scheme.
Refer to the Network Addressi ng chapter for more i nformati on regardi ng network
addressi ng schemes.
e. Opti onal l y, enter comments about your LAN card.
f. Choose Add Host Name Aliases. You must compl ete thi s step i f you have more than
one LAN card i nstal l ed i n your system.
g. Add, modi fy, or remove al i as host names for your l ogi cal i nterface.
h. Acti vate the OK button to perform the task and return to the Configure LAN Card
wi ndow.
i . Opti onal l y acti vate the Advanced Options button. Thi s wi l l al l ow you to modi fy the
Stati on Address and congure an I nternet Broadcast Address. The Maxi mum
Transmi ssi on Uni t (MTU) el d i s di spl ay onl y.
7. Acti vate the OK button at the Configure LAN Card wi ndow to enabl e your LAN card.
I f the software i s correctl y congured, SAM di spl ays the Network I nterface Cards object
l i st wi th the status Enabl ed for your LAN card; otherwi se, SAM di spl ays an error
message.
8. Choose Exit from the Fi l e menu.
9. At the Networking and Communications wi ndow, choose Exit SAM from the Fi l e menu.
NOTE I f you have moved or removed any LAN cards from the system, HP
recommends that you veri fy the I P address of every card i n the backpl ane
before l eavi ng SAM.
10. I P accesses LAN devi ces through a si ngl e Data Li nk Provi der I nterface (DLPI ) devi ce l e
/dev/dlpi. The /dev/dlpi l e i s created automati cal l y duri ng i nstal l ati on. Veri fy that
the /dev/dlpi l e has been created correctl y by executi ng the HP-UX command:
ls -al /dev/dlpi
The output appears somethi ng l i ke the fol l owi ng:
Chapter 2 12
crw-rw-rw- 1 bin bin 72 0x000077 Dec 4 11:14 /dev/dlpi
The major number, shown i n the fth col umn, must be 72 (deci mal ) and the mi nor
number, shown i n the si xth col umn, must be 77 (hexadeci mal ). I f the major numbers or
mi nor numbers are not correct, del ete the devi ce l e and recreate i t wi th the correct
numbers usi ng the mknod command. For exampl e:
mknod /dev/dlpi c 72 0x77
Conti nue to the next secti on, Conguri ng Network Connecti vi ty i f you want to congure
your system for network connecti vi ty. Otherwi se, conti nue to Veri fyi ng the I nstal l ati on.
Conguring Network Connectivity
Chapter 2 13
Your system may not be abl e to communi cate wi th other systems (for exampl e, PCs,
workstati ons, servers, etc.) unti l you congure system-to-system connecti ons. You can use
SAM to do thi s automati cal l y by compl eti ng the fol l owi ng steps:
2. Doubl e-cl i ck on the Networking and Communications i tem of the SAM mai n wi ndow.
3. Doubl e-cl i ck on Hosts. Doubl e-cl i ck on the Local Hosts File i tem.
SAM di spl ays the remote system names and I P addresses that are al ready congured.
4. Choose Add from the Acti ons menu to open the Add Host to File wi ndow.
Use the SAM on-l i ne hel p system for i nformati on about addi ng remote host connecti ons.
a. Enter the I nternet Address for the remote system.
Upon exi ti ng the I nternet Address el d, SAM checks to make sure you have entered a
val i d I P address. SAM al so determi nes i f a gateway i s requi red for the connecti on (see
step 4f).
b. Enter the remote host name.
Upon exi ti ng the Remote Host Name el d, SAM checks to make sure that connecti vi ty
has not al ready been congured for thi s system. I f i t has, SAM di spl ays an error
message.
c. Opti onal l y, choose Configure Aliases to open the Configure Aliases wi ndow for
remote systems.
d. Add, modi fy, or remove al i as names for the remote system.
e. Acti vate the OK button to perform the task and return to the Add Host to File
wi ndow.
f. Proceed to step 5 i f a gateway i s not requi red for thi s remote connecti on.
SAM di spl ays el ds for enteri ng gateway i nformati on i f a gateway i s requi red for thi s
remote system connecti on. Use the SAM on-l i ne hel p system for i nformati on about
gateways.
5. Acti vate the OK button to enabl e your system to communi cate wi th thi s system and
return to the Internet Addresses wi ndow.
SAM updates the object l i st to i ncl ude the remote system you congured.
Chapter 2 14
NOTE You can modi fy or remove remote systems and modi fy defaul t gateways by
hi ghl i ghti ng the Remote System Name from the object l i st and choosi ng
Modi fy, Remove, or Modi fy Defaul t Gateway from the Acti ons menu.
6. Choose Exit from the Fi l e menu.
7. Then Exi t SAM from the Fi l e menu agai n.
8. Veri fy remote system congurati on.
a. Vi ew the l i st of remote systems you can communi cate wi th usi ng a symbol i c name by
typi ng the fol l owi ng command at the HP-UX prompt (note that thi s l e may be l arge):
more /etc/hosts
b. Vi ew the congured desti nati ons reached through gateways and the gateways used to
reach those desti nati ons by typi ng the fol l owi ng command at the HP-UX prompt:
netstat -r
To veri fy that you can communi cate wi th a remote system usi ng the HP-UX LAN product,
conti nue to Veri fyi ng the I nstal l ati on.
Verifying the Installation
Chapter 2 15
Verifying the Installation
Once your HP-UX LAN software i s i nstal l ed, ful l y congured and runni ng, you shoul d execute
the fol l owi ng commands to veri fy LAN hardware and software i nstal l ati on. See the man
pages for compl ete descri pti ons of the commands l i sted bel ow.
1. Check the state of al l LAN hardware. To do so execute the lanscan command and veri fy
that the Hardware State i s UP.
2. Check the state of the network i nterface. To do so execute ifconfig on the i nterface you
wi sh to veri fy. The exampl e bel ow wi l l provi de i nformati on about the lan0 i nterface.
ifconfig lan0
3. Veri fy l i nk l evel l oopback connecti vi ty usi ng the linkloop command wi th the PPA and
stati on address of the i nterface you want to test. You can obtai n the stati on address
(typi cal l y 0x080009######) and PPA from the lanscan command output. The exampl e
bel ow wi l l test the connecti vi ty of the LAN card wi th PPA 4 and stati on address
0x080009266C3F.
linkloop -i 4 0x080009266C3F
4. Veri fy that the /dev/lan and /dev/snap l es have been created and symbol i cal l y l i nked
to the /dev/dlpi l e.
ls -l /dev/lan
ls -l /dev/snap
5. To check that the your system can communi cate wi th other systems, enter the ping
command at the HP-UX prompt. I n thi s exampl e, 191.2.1.2 i s the I P address of the remote
system. Enter [Ctrl]-C to stop ping.
ping 191.2.1.2
HP-UX LAN i nstal l ati on i s veri ed i f the steps above are successful . For i nformati on on
troubl eshooti ng HP-UX LAN congurati on and operati on, refer to the secti onDi agnosti c
Fl owcharts i n Chapter 4, Troubl eshooti ng HP-UX LAN.
Reconguring IP Addresses
Chapter 2 16
Reconguring IP Addresses
I f you have rearranged any network i nterface cards i n the system you may need to recongure
the I P addresses. Fol l ow the steps bel ow:
2. At the mai n menu sel ect the Networking and Communications i tem.
3. Sel ect the Network Interface Cards i tem.
4. Veri fy the I P addresses of al l the adapters i n the system by revi ewi ng the Card Name,
Hardware Path, and I nternet Address di spl ayed i n the Network I nterface Cards wi ndow.
5. For adapters wi th i ncorrect I P addresses, fol l ow the steps bel ow:
a. Sel ect the adapter you wi sh to modi fy.
b. Sel ect Modify from the Acti ons menu.
c. Modi fy the I nternet Address and sel ect ok.
Chapter 3 17
3 Manually Installing and Conguring
HP-UX LAN
Thi s chapter provi des i nformati on on manual l y conguri ng HP-UX LAN software. Manual l y
conguri ng HP-UX LAN i nvol ves the fol l owi ng steps:
Manually Installing and Conguring HP-UX LANDRAFT COPY
Chapter 3 18
Creati ng a New Kernel
Veri fyi ng LAN Devi ce Fi l es
Edi ti ng Dri ver Congurati on Fi l es
Edi ti ng LAN Congurati on Fi l es
Creati ng the /etc/hosts Fi l e
Acti vati ng Opti onal Network Features
DRAFT COPY Manually Installing and Conguring HP-UX LAN
Creating a New Kernel
Chapter 3 19
Before attempti ng thi s procedure, fami l i ari ze yoursel f wi th the system recongurati on
i nformati on i n the mk_kernel(1M) man page and HP-UX system l i terature.
Refer to the System Admi ni strati on manual for your system for compl ete i nstructi ons on how
to create a kernel . The steps bel ow contai n a general outl i ne of kernel congurati on steps wi th
some i nformati on for the HP-UX LAN dri vers and parameter setti ngs contai ned wi thi n that
framework.
I f the kernel was not created wi th the LAN dri ver i n i t duri ng the swinstall procedure, you
can create i t manual l y. To determi ne whether the LAN dri ver i s i n the kernel , check the
/stand/system l e for the lanX keyword (where X=2 or 3). To determi ne whether the LAN
dri ver i s i nstal l ed, execute what /stand/vmunix and check for references to LAN i n the
output.
I f you used some other l e to create the kernel previ ousl y, copy that l e to /stand/system
before fol l owi ng the steps bel ow.
1. Ensure that you have superuser capabi l i ti es.
2. Change to the /stand di rectory.
3. Make a backup copy of your current congurati on descri pti on l e (whi ch i s commonl y
system or build/system).
4. Edi t the system l e to add dri vers and/or change system parameters. (Refer to your
speci c Ethernet LAN documentati on, as appropri ate for your congurati on, for compl ete
i nformati on.)
a. Veri fy or add the appropri ate keywords:
Some exampl es of keywords are:
btl an (PCI 10/100BT adapters)
gel an (Gi gabi t Ethernet add-on adapters)
i gel an (Next Generati on Core I O 10/100/1000 cards)
I f the keyword does not exi st i n the /stand/system l e, add the appropri ate l i nes to
the l e.
Chapter 3 20
b. Dependi ng on whi ch l esets you have l oaded, you may al so need to add the fol l owi ng
keywords to the system l e:
5. Make a copy of the exi sti ng kernel (defaul t name vmunix).
6. Regenerate the kernel wi th mk_kernel, usi ng the edi ted system l e as i nput. mk_kernel
creates the new hp-ux kernel (the defaul t i s /stand/build/vmunix_test).
mk_kernel
I n thi s exampl e a new kernel i s created i n the bui l d di rectory cal l ed vmunix_test.
mk_kernel -s /stand/system -o /stand/vmunix
Thi s second exampl e automati cal l y moves the kernel to the /stand di rectory and makes a
backup (/stand/vmunix_prev) i f the l e /stand/vmunix al ready exi sts.
7. I f you di d not use the -o opti on wi th the mk_kernel command, execute kmupdate and thi s
wi l l copy the new kernel to /stand/vmunix. (Or you can manual l y copy the new kernel to
/stand/vmunix.)
8. Reboot the new kernel . I f the new kernel fai l s to boot, boot the system from the backup
kernel and repeat the process of creati ng a new kernel . To do so, fol l ow the i nstructi ons i n
the Managing System and Workgroups: A Guide for HP-UX System Administrators
manual .
Table3-1 Keywords
Keyword Comments
hpstreams requi red for streams
dl pi requi red
ui pc requi red for TCP/I P
i net requi red for TCP/I P
nms requi red for TCP/I P
nfs_core
nfs_cl i ent
nfs_server
netdi ag1
tun requi red for PPP
Chapter 3 21
9. Proceed to the next secti on Veri fyi ng LAN Devi ce Fi l es, i n thi s chapter to conti nue
conguri ng HP-UX LAN manual l y. To congure your system wi th the SAM uti l i ty,
proceed to Chapter 2, Conguri ng HP-UX LAN Usi ng SAM.
Verifying LAN Device Files
Chapter 3 22
Verifying LAN Device Files
Al l I P access to LAN devi ces i s done through the l es /dev/lan and /dev/snap, whi ch are
symbol i cal l y l i nked to the Data Li nk Provi der I nterface (DLPI ) devi ce l e /dev/dlpi. The
/dev/dlpi l e i s automati cal l y created at i nstal l ati on ti me. Veri fy that the /dev/lan and
/dev/snap l es have been created and symbol i cal l y l i nked to /dev/dlpi by enteri ng:
ls -l /dev/snap output wi l l l ook somethi ng l i ke:
lrwxr-xr-x 1 root sys 9 Mar 15 11:59 /dev/snap -> /dev/dlpi
ls -l /dev/lan output wi l l l ook somethi ng l i ke:
crw-rw-rw- 1 root sys 72 0x000077 Mar 15 11:59 /dev/lan
ls -l /dev/dlpi output wi l l l ook somethi ng l i ke:
crw-rw-rw- 1 root sys 72 0x000077 Mar 15 11:59 /dev/dlpi
The major number, shown i n the fth col umn, must be 72 (deci mal ) and the mi nor number,
shown i n the si xth col umn, must be 77 (hexadeci mal ). I f the i nformati on di ffers si gni cantl y,
del ete the l e and recreate i t correctl y wi th the mknod command:
mknod /dev/dlpi c 72 0x77
or
insf -d dlpi
Editing Driver Conguration Files
Chapter 3 23
Editing Driver Conguration Files
I f needed, edi t appropri ate congurati on l es. Refer to your speci c Ethernet LAN
documentati on, as appropri ate for your congurati on, for compl ete i nformati on.
Bel ow are some exampl es of software dri ver names, congurati on l es, and i ni t scri pts for
Fast Ethernet and Gi gabi t Ethernet cards/adapters.
Table3-2 Fast Ethernet Examples
Fast Ethernet
driver
name
conguration
le
init script
Core PCI
10/100BT cards
btl an hpbtl anconf hpbtl an
Table3-3 Gigabit Ethernet Examples
Gigabit Ethernet
driver
name
conguration
le
init script
Add-On
10/100/1000
Adapters
(A4926A, A4929A)
gel an hpgel anconf hpgel an
Core 10/100/1000
Cards
i gel an hpi gel anconf hpi gel an
Add-On
10/100/1000
Cards
(A6847A, A6825A)
i gel an hpi gel anconf hpi gel an
Editing LAN Conguration Files
Chapter 3 24
To congure and i ni ti al i ze LAN manual l y, you must edi t the /etc/rc.config.d/netconf l e
and execute the HP-UX LAN i ni ti al i zati on scri pt. To do so, you must be l ogged on as root.
The scri pt reads the i nformati on i n the edi ted netconf l e when the system reboots and
performs the fol l owi ng:
Congures the network i nterface wi th an I P address and opti onal subnet mask.
Congures the network routi ng tabl e i f your node i s a gateway or on a LAN wi th a
gateway.
NOTE You must i ni ti al i ze HP-UX LAN to use HP-UX NFS or HP-UX I nternet
Servi ces. Refer to Executi ng the Network Congurati on Scri pt secti on bel ow
for opti ons avai l abl e to make congurati on changes acti ve.
You may al so want to modi fy the defaul t stati on address. To modi fy the stati on address, you
must edi t the (dri ver speci c) congurati on l e i n the di rectory /etc/rc.config.d. Refer to
Tabl e 3-2 and Tabl e 3-3 for some exampl es, and to your speci c Ethernet LAN documentati on,
as appropri ate for your congurati on, for compl ete i nformati on.
Modifying the Hewlett-Packard Station Address (optional)
Thi s step i s opti onal and most customers do not need to modi fy the stati on address of thei r
Hewl ett-Packard LAN cards.
Modi fyi ng the stati on address of an acti ve card wi l l probabl y destroy exi sti ng connecti ons and
trafc resul ti ng i n data l oss. Modi fyi ng the stati on address can al so cause temporary
confusi on i n the network because al l nodes that were communi cati ng wi th the l ocal node wi l l
detect an error when usi ng the exi sti ng stati on address. The confusi on i s temporary and al l
nodes may eventual l y recover from the si tuati on. Probl ems caused by modi fyi ng a stati on
address duri ng a communi cati on sessi on are di fcul t to troubl eshoot.
Editing the Driver Conguration File in /etc/rc.cong.d/
Edi ti ng the dri ver congurati on l e (refer to Tabl e 3-2 and Tabl e 3-3 for some exampl es, and
to your speci c Ethernet LAN documentati on, as appropri ate for your congurati on, for
compl ete i nformati on) wi l l modi fy the stati on address each ti me the system reboots. The
modi ed stati on address i s not permanent. Each system reboot causes the preset stati on
address to be overwri tten when a val ue i s suppl i ed to the congurati on parameters.
Chapter 3 25
CAUTION Each HP LAN card has a preset stati on address, for exampl e 080009xxxxxx.
Thi s address must be modi ed wi th cauti on. Modi fyi ng the stati on address of
an acti ve card wi l l probabl y destroy exi sti ng connecti ons and trafc resul ti ng i n
data l oss.
The stati on address congurati on parameters have an i ndex val ue, [x], that groups the
stati on address parameters together. The i ndex val ue must be di fferent for each addi ti onal
i nterface.
Fol l owi ng i s a sampl e hpbtlanconf entry:
HP_BTLAN_INTERFACE_NAME[0]=lan1
HP_BTLAN_STATION_ADDRESS[0]=0x022345678901
Editing /etc/rc.cong.d/netconf
Edi ti ng the netconf l e al l ows you to i denti fy the network i nterface name, I P address, and
subnet mask of your LAN card, and add entri es to the network routi ng tabl e. As the netconf
l e has read-onl y permi ssi on, you must have superuser capabi l i ty to make modi cati ons to
thi s l e.
The steps to add the hostname, l oopback address, i nternet congurati on i nformati on and
routi ng congurati on i nformati on to the netconf l e are l i sted bel ow.
NOTE The netconf l e and the scri pt that i s executed are shel l programs; therefore,
shel l programmi ng rul es appl y.
1. Veri fy that the hostname and l oopback address are set. Upper l ayer software often
requi res l oopback. Be sure that l oopback i s al so enabl ed i n the netconf l e.
HOSTNAME=nameofyoursystem
LOOPBACK_ADDRESS=127.0.0.1
2. Add i nternet congurati on i nformati on.
I n thi s step you wi l l assi gn an I P address and subnet mask, and congure network
i nterface parameters. The i nternet congurati on parameters have an i ndex val ue, [x],
that groups the congurati on parameters together. Fol l owi ng i s a sampl e of the i nternet
congurati on i nformati on of the netconf l e entry:
INTERFACE_NAME[0]=lan0
IP_ADDRESS[0]=192.6.1.1
SUBNET_MASK[0]=255.255.224.0
Chapter 3 26
BROADCAST_ADDRESS[0]=
INTERFACE_STATE[0]=
DHCP_ENABLE[0]=0
I f you have more than one i nterface to congure, you must have a compl ete set of i nternet
congurati on parameters for each i nterface. The i ndex val ue must be di fferent for each
addi ti onal i nterface. The network i nterface name i n lanscan corresponds to the
INTERFACE_NAME[x] i n the i nternet congurati on parameters.
You can congure mul ti pl e l ogi cal i nterfaces for a physi cal i nterface. You must congure
the i ni ti al i nterface for a card/encapsul ati on type before you can congure other l ogi cal
i nstances of the same card/encapsul ati on type. For exampl e, you must congure l an0:0 (or
l an0) before you congure l an0:1 and l an0:2. I n the netconf entry shown previ ousl y, l an0
i s equi val ent to l an0:0, the i ni ti al i nterface for l an0. The fol l owi ng i s a sampl e netconf
entry for a second l ogi cal i nterface on l an0:
INTERFACE_NAME[1]=lan0:1
IP_ADDRESS[1]=192.6.3.3
SUBNET_MASK[1]=255.255.224.0
BROADCAST_ADDRESS[1]=
INTERFACE_STATE[1]=
DHCP_ENABLE[1]=0
For more i nformati on about speci fyi ng i nterface names for mul ti pl e l ogi cal i nterfaces, see
chapter 6, Network Addressi ng.
3. Add routi ng congurati on i nformati on.
I f you i ntend to use your system as a gateway or to communi cate wi th gateways, add the
route desti nati on, gateway address, and hop count parameter i nformati on. The routi ng
congurati on parameters have an i ndex val ue, [x], that groups the routi ng parameters
together. Fol l owi ng i s a sampl e netconf entry:
ROUTE_DESTINATION[0]=default
ROUTE_GATEWAY[0]=192.6.1.2
ROUTE_COUNT[0]=1
ROUTE_MASK[0]=
ROUTE_ARGS[0]=
The i ndex val ue must be di fferent for each addi ti onal route.
Executing the Network Conguration Script
Once you have edi ted the netconf l e, you need to acti vate thi s congurati on. After addi ng
the LAN and routi ng congurati on i nformati on i nto the netconf l e, you can ei ther reboot
your system, execute the ifconfig, and route commands manual l y, or re-execute the
/sbin/init.d/net.init and /sbin/init.d/net scri pts. Thi s secti on di scusses each of these
opti ons.
Chapter 3 27
Option 1: Reboot your system. HP recommends that you reboot your system to acti vate any
changes you made i n your netconf l e. A reboot i s the cl eanest method for executi ng the
network scri pt because the reboot handl es any other network i ni ti al i zati on dependenci es.
Option 2: Execute the ifconfig and route commands at the HP-UX prompt. HP recogni zes
that system reboots are di srupti ve to end users. To del ay or schedul e the reboot, but sti l l make
your congurati on changes acti ve, you may execute the ifconfig and route commands wi th
the appropri ate val ues for your network. When you reboot, the val ues i n your netconf l e
wi l l be used. Refer to the lanscan(1M), ifconfig(1M), and route(1M) man pages for
i nformati on on command usage.
Option 3:
I f you made changes to the stati on address, execute the i ni t scri pt i n the di rectory /sbi n/i ni t.d/.
Refer to Tabl e 3-2 and Tabl e 3-3 for some exampl es, and to your speci c Ethernet LAN
documentati on, as appropri ate for your congurati on, for correct i ni t scri pt. For a 100BT PCI
card on an rx2600 system, heres an exampl e:
/sbin/init.d/btlan start
After executi ng the above command, execute the command:
/sbin/init.d/net start
These commands wi l l source the contents of the netconf and hpbtlanconf l es. Executi ng
these scri pts wi l l not necessari l y properl y re-i ni ti al i ze any other networki ng subsystems. For
exampl e, i f you are runni ng an I nternet Servi ce over the l i nk you have just congured
manual l y, the servi ce may not work wi th your new congurati on. The system boot sequence
i ni ti al i zes networki ng subsystems and products i n the correct order. I ni ti al i zi ng a speci c
subsystem al one may cause network probl ems.
Creating the /etc/hosts File
Chapter 3 28
You must edi t the /etc/hosts l e to add an I P address and hostname for the LAN card that
you are i nstal l i ng.
NOTE I f you are usi ng a nami ng servi ce (DNS or NI S), you wi l l need to modi fy the
/etc/hosts l e to add the I P address and host name to the appropri ate
databases on the name server system. Refer to I nternet Services
Administrators Guide and NFS Services Administrators Guide for more
i nformati on on nami ng servi ces.
The /etc/hosts l e associ ates I P host addresses wi th mnemoni c host names and al i as
names. I t contai ns the names of other nodes i n the network wi th whi ch your system can
communi cate. HP-UX LAN di agnosti cs netstat and ping use /etc/hosts. I f you i nstal l
HP-UX I nternet Servi ces or HP-UX NFS, those products al so use the /etc/hosts l e.
You can create an /etc/hosts l e three ways:
From scratch, enteri ng the known nodes i n the format shown bel ow.
By copyi ng the l e from another node.
By copyi ng the ofci al host database mai ntai ned at the Network I nformati on Control
Center (NI C) for ARPA I nternet networks, i f you are i nstal l i ng HP-UX I nternet Servi ces.
I f you copy an /etc/hosts l e from another host, you may need to update the l e by addi ng
unofci al al i ases or unknown hosts, i ncl udi ng your own host.
Network and System Names
A system i s known by several names, each wi th i ts own purpose:
System name: Used for cl uster congurati on and UUCP communi cati on.
Host nameand aliases: Used for most network communi cati on. Thi s mi ght be a ful l y qual i ed
domai n name i ncl udi ng the DNS domai n. For exampl e: turtle.bnio.nmt.edu
HP recommends that you try to keep these names as consi stent as possi bl e, wi thi n thei r
l i mi tati ons. Thi s wi l l hel p to mi ni mi ze confusi on.
The exampl es bel ow show how a system wi th the name, host3, mi ght be referenced i n the
/etc/hosts and other system and networki ng l es and commands:
System name i n I nstal l screen:
Chapter 3 29
host3
/etc/rc.config.d/netconf l e:
HOSTNAME=host3
/etc/hosts l e:
192.6.1.1 host3 host3.site2.region4
uname -S host3
hostname host3
NOTE When you rst i nstal l a system, the netconf HOSTNAME entry, the
/etc/hosts entry, the hostname, and uname -S are set for you automati cal l y.
/etc/hosts
Each node has a one l i ne entry i n the /etc/hosts l e. Each entry i n the l e takes the
fol l owi ng form:
Syntax
IP_address host_name [alias]...
Parameters
IP_address The I P address that uni quel y i denti es the node. IP_address must be i n
i nternet dot notati on. Refer to Chapter 6, Network Addressi ng, for more
i nformati on on I P addresses.
host_name Name of the node. Host names can contai n any pri ntabl e character except
spaces, newl i ne, or the comment character (#). Nami ng Conventi on: the rst
ni ne characters shoul d be uni que for each network host.
alias Common name or names for the node. An al i as i s a substi tute for
host_name. Al i as names are opti onal . Nami ng Conventi on: the rst ni ne
characters shoul d be uni que for each network host.
/etc/hosts Format
When creati ng the /etc/hosts l e, fol l ow these rul es:
Li nes cannot start wi th a bl ank or tab character.
Fi el ds can have any number of bl anks or tab characters separati ng them.
Chapter 3 30
Comments are al l owed and desi gnated by a pound si gn (#) precedi ng the comment text.
Trai l i ng bl ank and tab characters are al l owed.
Bl ank l i ne entri es are al l owed.
Onl y one host entry per l i ne i s al l owed.
/etc/hosts Permissions
HP recommends that the /etc/hosts l e be owned by user root and have 0x444
(-r--r--r--) access permi ssi on. For more i nformati on on /etc/hosts, refer to the hosts(4)
man page i n the HP-UX Reference Pages.
NOTE HP hi ghl y recommends that you l i mi t access to the /etc/hosts l e by setti ng
the permi ssi on to 0x444 (-r-r-r--) for read access onl y.
/etc/hosts Example
The fol l owi ng /etc/hosts entry contai ns an I P address, hostname, and al i as names
(host3.si te2.regi on4 and grace).
192.6.1.1 host3 host3.site2.region4 grace
Activating Optional Network Features
Chapter 3 31
To acti vate speci al network features, you may al so want to congure /etc/services,
/etc/networks, and /etc/protocols. Each of these steps i s opti onal .
NOTE I f you are usi ng NI S, modi cati ons to the /etc/services, /etc/networks and
/etc/protocols l es shoul d onl y be made on the NI S Master Server. Refer to
the NFS Services Administrators Guide for more i nformati on
Modifying the /etc/services File
The /etc/services l e associ ates port numbers wi th mnemoni c servi ce names and al i as
names. The /etc/services l e contai ns the names, protocol names, and port numbers of al l
servi ces known to your l ocal host. The netstat di agnosti c uses the /etc/services l e.
I f you i nstal l HP-UX I nternet Servi ces or HP-UX NFS, these products wi l l al so use the
/etc/services l e.
NOTE You can modi fy thi s l e i f you have speci al requi rements, but i t i s properl y
congured when you recei ve HP-UX LAN.
/etc/services
Each servi ce has a one l i ne entry i n the /etc/services l e. Each entry i n /etc/services l e
takes the fol l owi ng form:
Syntax
service_name port_num/protocol [alias]...
Parameters
service_name Name of the servi ce. Servi ce names can contai n any pri ntabl e character
except spaces, newl i ne, or the comment character (#).
port_num /protocol port_num i s the protocol port number assi gned to thi s servi ce. Al l
requests for thi s servi ce must use thi s port number. protocol i s the protocol
name, as l i sted i n /etc/protocols, that the servi ce uses.
Chapter 3 32
alias Common name or names for the servi ce. An al i as i s a substi tute for
service_name. Al i as names are opti onal .
/etc/services Format
Comments are al l owed and desi gnated by a pound si gn (#) character precedi ng the
comment text.
Onl y one entry per l i ne i s al l owed.
/etc/services Permissions
The /etc/services l e shoul d be owned by user bin, group bin, and i t shoul d have 0x444
(-r--r--r--) access permi ssi on.
Refer to the /etc/services l e for exampl es of actual format and contents. For more
i nformati on on /etc/services, refer to the services(4) man page i n the HP-UX Reference
Pages.
/etc/services Example
The fol l owi ng /etc/services entry contai ns the servi ce name, port number, protocol name,
and al i as name for the shell servi ce.
shell 514/tcp cmd #remote command, no passwd used
Creating the /etc/networks File
The /etc/networks l e associ ates network addresses wi th mnemoni c names and al i as
names. The /etc/networks l e contai ns the name and address of known i nternet networks
wi th whi ch your host can communi cate. The HP-UX LAN di agnosti c netstat and the route
command use the /etc/networks l e. You must congure thi s l e for your host i f you want
route or netstat to use symbol i c network names i nstead of addresses.
You can create an /etc/networks l e two ways:
From scratch, enteri ng the known nodes i n the format shown bel ow.
By copyi ng the l e from another node.
Chapter 3 33
I f you copy an /etc/networks l e from another host, you may need to update the l e by
addi ng unofci al al i ases or unknown networks, i ncl udi ng your own network.
/etc/networks
Each network has a one l i ne entry i n the /etc/networks l e. Each entry i n /etc/networks
l e takes the fol l owi ng form:
Syntax
network_name network_address [alias]...
Parameters
network_name Name of the i nternet network. Network names can contai n any pri ntabl e
character except spaces, newl i ne, or the comment character (#).
network_address Network address that uni quel y i denti es the network. Thi s address can be
a subnet or supernet address. I t may al so contai n the netmask transl ati on.
network_address must be i n dot notati on. See Chapter 6 for detai l s on
network addresses.
alias Common name or names for the network. An al i as i s a substi tute for
network_name. Al i as names are opti onal .
/etc/networks Format
comment text.
/etc/networks Permissions
The /etc/networks l e shoul d be owned by user bin, group bin, and i t shoul d have 0x444
(-r--r--r--)access permi ssi on.
For more i nformati on on /etc/networks, refer to the networks(4) man page i n the HP-UX
Reference Pages.
Chapter 3 34
/etc/networks Example
The fol l owi ng /etc/networks entry contai ns a network name, network address, and an al i as
name for the network neta.
neta 192.6.1 testlan
Modifying the /etc/protocols File
The /etc/protocols l e associ ates port numbers wi th mnemoni c names and al i as names.
The /etc/protocols l e contai ns the names and protocol numbers of al l protocol s known to
your l ocal host. The netstat di agnosti c uses the /etc/protocols l e. I f you i nstal l HP-UX
I nternet Servi ces or HP-UX NFS, those products wi l l al so use the /etc/protocols l e.
NOTE You can modi fy thi s l e i f you have speci al requi rements, but i t i s properl y
congured when you recei ve the HP-UX LAN software.
/etc/protocols
Each protocol has a one l i ne entry i n the /etc/protocols l e. Each entry i n /etc/protocols
l e takes the fol l owi ng form:
Syntax
protocol_name protocol_num [alias]...
Parameters
protocol_name Name of the protocol . Protocol names can contai n any pri ntabl e character
except spaces, newl i ne, or the comment character (#).
protocol_num Protocol number that i denti es thi s protocol .
alias Common name or names for the protocol . An al i as i s a substi tute for
protocol_name. Al i as names are opti onal .
/etc/protocols Format
comment text.
Chapter 3 35
/etc/protocols Permissions
The /etc/protocols l e shoul d be owned by user bin, group bin, and i t shoul d have 0x444
(-r--r--r--) access permi ssi on.
Refer to the /etc/protocols l e for exampl es of actual format and contents. For more
i nformati on on /etc/protocols, refer to the protocols(4) man page i n the HP-UX
Reference Pages.
/etc/protocols Example
The fol l owi ng /etc/protocols entry contai ns a protocol name, protocol number and an al i as
name.
tcp 6 TCP
Chapter 3 36
Chapter 4 37
4 Troubleshooting HP-UX LAN
Thi s chapter provi des gui del i nes for troubl eshooti ng H-UX LAN. I t contai ns the fol l owi ng
secti ons:
Troubl eshooti ng Overvi ew
Troubleshooting HP-UX LANDRAFT COPY
Chapter 4 38
Troubl eshooti ng Q and A
LAN I nterface Card Stati sti cs
100Base-T Checkl i st
Di agnosti c Fl owcharts
DRAFT COPY Troubleshooting HP-UX LAN
Troubleshooting Overview
Chapter 4 39
Troubleshooting Overview
Troubl eshooti ng LAN probl ems can be di fcul t because a vari ety of hardware and software
components may be i nvol ved and because the probl em i mpacti ng your system may ori gi nate
i n another part of the network.
The Troubl eshooti ng Q and A secti on i n thi s chapter provi de qui ck x sol uti ons to common
network probl ems by provi di ng answers to the most frequentl y asked troubl eshooti ng
questi ons. Look through the probl ems i denti ed to see i f your probl em ts i nto any of these
categori es. I f so, you may be abl e to qui ckl y i denti fy and recover from the probl em wi thout any
further i nvesti gati on.
I f, however, you are unabl e to i denti fy your probl em, proceed to the 100Base-T Checkl i st to
have a general vi ew of your system and i ts possi bl e probl ems. Then i f you are sti l l unabl e to
i denti fy your probl em, proceed to the troubl eshooti ng owcharts. The troubl eshooti ng
owcharts provi de a l ogi cal sequence of steps to fol l ow when troubl eshooti ng HP-UX LAN.
Usi ng the di agnosti c owcharts provi ded i n thi s chapter, i denti fy whether the probl em i s wi th
HP-UX LAN, any of the connectors, or i f i t i s i n some other part of the LAN network. Veri fy
your assumpti ons and, i t i f i s l i mi ted to HP-UX LAN software and hardware, correct the
probl em.
Troubleshooting Q & A
Chapter 4 40
New system disrupts LAN: I tri ed to attach a new system to our si te LAN. To make the
i nstal l ati on process faster, I copi ed over an /etc/rc.config.d/netconf l e from another
system on the si te LAN and used i t on the new system. When I booted up the system, the si te
LAN went down.
Answer: You probabl y di dn't assi gn a new I P address and host name pri or to rebooti ng the
system. I f any two systems on the LAN have the same I P address and host name, the LAN
wi l l go down. Check the I P address i n the /etc/rc.config.d/netconf l e agai nst the I P
address of your system and other systems on your network map to be sure that no dupl i cate
I P addresses exi st on the LAN.
Rel ated Documentati on: Refer to the ifconfig(1M) man page.
Determining interface name: How do I determi ne the name of the i nterface to be
congured?
Answer: Use the lanscan command to determi ne the hardware path of the i nterface card that
you want to congure. Then use the val ue di spl ayed for the Net-I nterface Name PPA el d as
the i nterface name.
MultipleLAN interfaces, intermittent failures: I have been havi ng probl ems getti ng the
two LAN i nterfaces on my system to operate at the same ti me. Occasi onal l y the ethernet
cards stop communi cati ng wi th remote systems. When thi s happens, the remote system al so
cannot communi cate wi th the l ocal system.
Answer: Check that the two i nterfaces on your system do not have the same network number
or, i f you are subnetti ng, the same subnet address. I f both LAN i nterfaces have the same val ue
i n the network (subnet) address porti ons of the I P address, the cards may not be enabl ed
si mul taneousl y (al though they may both run separatel y.)
Rel ated Documentati on: Refer to Chapter 6, Network Addressi ng.
Newsystem, cant reach somesubnets: I recentl y tri ed to add a new system onto a subnet
on our si te LAN, and I am not abl e to communi cate successful l y wi th al l LANs on the
network.
Answer: Check the routi ng tabl e to make sure the route for the LAN you are tryi ng to
communi cate wi th has been properl y congured. Execute netstat -rvn on both ends. Veri fy
the subnet address, netmask and gateway.
Rel ated Documentati on: Refer to Assi gni ng Subnet Addresses i n Chapter 6.
Conguring address 127.0.0.1: I tri ed to add the I P address, 127.0.0.1, and the system
won't accept i t.
Chapter 4 41
Answer: Addresses wi th the format 127.n.n.n are reserved as l oopback addresses. Sel ect
another I P address. You can obtai n Cl ass C addresses that are uni que wi thi n the ARPANET
by contacti ng Government Systems, I nc.
Rel ated Documentati on: Refer to Assi gni ng an I nternet Address i n Chapter 6.
Displaying station address: How do I l ocate the stati on address of my LAN card?
Answer: Use the lanscan command to di spl ay the stati on addresses of al l LAN cards i n the
system:
lanscan
Rel ated Documentati on: Refer to the lanscan(1M) man page.
Resetting LAN card: How do I reset the LAN card?
Answer: Run the lanadmin di agnosti c by enteri ng the fol l owi ng sequence of commands, where
x i s the Physi cal Poi nt of Attachment (PPA) of the i nterface you want to reset. (Use the
lanscan command to determi ne the PPA of the i nterface on the system.)
lanadmin
lan
ppa
x
reset
quit
Rel ated Documentati on: Refer to the lanadmin(1M) man page.
Tracing: What's the best way to obtai n and format traci ng i nformati on when I am usi ng the
nettl uti l i ty?
Answer: HP el d engi neers recommend the fol l owi ng commands:
To begi n LAN and l oopback traci ng, execute:
nettl -tn pduin pduout -e ns_ls_driver -f filename
To end LAN traci ng, execute:
nettl -tf -e all
To format your enti re LAN trace (no l teri ng), execute:
netfmt -Nnl -f filename.TRC1 > fmt1
netfmt -Nnl -f filename.TRC0 > fmt0
The l e, filename.TRC0 i s the most recent trace l e. I f thi s l e does not contai n the trace
i nformati on you are l ooki ng for, check the filename.TRC1 l e.
To format your LAN trace usi ng a l ter l e, execute:
netfmt -c filterfile -N -f filename.TRC0 > fmt0
Chapter 4 42
nettl appends TRC0 or TRC1 to the name you gi ve the raw trace l e.
Rel ated Documentati on: Refer to Chapter 5, LAN Resources.
Intermittent networking problems: I 'm experi enci ng i ntermi ttent networki ng probl ems
on my computer. What shoul d I check to ensure proper operati on of my networki ng software?
Answer: Upper l ayer software often requi res l oopback. Check /etc/rc.config.d/netconf to
be sure that the l oopback entry i s correct. The l i ne i n netconf l e shoul d read:
LOOPBACK_ADDRESS=127.0.0.1
Rel ated Documentati on: Refer to chapter 6, Network Addressi ng.
Performance: I 've noti ced a si gni cant drop i n system response ti me and performance. What
steps can I take to i mprove i t?
Answer: Performance may be affected by many di fferent factors. Someti mes removi ng pseudo
dri vers from the kernel for networki ng software that you may not be usi ng i mproves
performance. The probl ems may al so be i n the upper l ayer software (ftp or telnet).
Al so, i t i s possi bl e that too l i ttl e memory i s al l ocated to hol d fragmented messages i n the I P
l ayer. I P messages may be fragmented i nto smal l er parts when the message i s sent through
the system. The fragments must be hel d i n memory for some ti me so that the enti re message
can be reassembl ed because the fragments arri ve at the desti nati on at di fferent ti mes and
possi bl y out of order. Normal l y, fragmentati on reassembl y memory i s l i mi ted arbi trari l y so
that i ncompl ete messages do not consume al l of memory, whi ch coul d cri ppl e the system.
Duri ng stressful networki ng acti vi ty, some fragments mi ght never be del i vered because they
are typi cal l y dropped i n transi t, for exampl e, due to a col l i si on or resource l i mi tati ons on an
i ntermedi ate system. However, fragments mi ght al so not be del i vered (dropped) i f there i s
i nsufci ent fragmentati on reassembl y memory on the desti nati on system duri ng peri ods of
hi gh network acti vi ty. Thi s can degrade performance due to retransmi ssi ons of data. I f the
probl em i s due to a hi gh number of fragments dropped after ti me-out (see the output from the
command netstat -sp ip), you mi ght want to i ncrease the si ze of the fragmentati on
reassembl y memory by changi ng the ip_reass_mem_limit val ue usi ng the ndd command.
(The defaul t i s 2 MB for the system.) Enter the command /usr/bin/ndd -h to di spl ay ndd
parameters and thei r use.
Deferred transmissions/collisions: Why i s there a si gni cant i ncrease i n the number of
deferred transmi ssi ons and col l i si ons on my network?
Answer: On I EEE802.3/Ethernet networks, a col l i si on occurs when two or more stati ons try to
transmi t data si mul taneousl y. A deferred transmi ssi on occurs i f the network i s busy when a
stati on attempts to transmi t data. The number of col l i si ons and deferred transmi ssi ons on a
node i s di rectl y rel ated to the network l oad. As the network l oad i ncreases, the number of
col l i si ons and deferred transmi ssi ons al so i ncrease.
Chapter 4 43
When hi gh-performance systems are pl aced on a LAN wi th l ower-performance systems (HP or
non-HP systems), i t i s possi bl e for the hi gh-performance systems to use a hi gher percentage of
the LAN bandwi dth wi th network trafc i ntensi ve appl i cati ons. Hi gh-performance systems
generate network trafc at a 10Mbi ts/s l i nk rate, and l ower-performance systems cannot
match thi s rate. Heavi l y l oaded LAN networks can resul t i n l ower throughput performance on
l ower-performance systems.
I n general , the short term average l oad on an I EEE802.3/Ethernet LAN shoul d not exceed
more than 70% of the total bandwi dth of the LAN. When i t does exceed 70% of the total
bandwi dth, network performance begi ns to degrade due to an i ncrease i n col l i si ons and
deferred transmi ssi ons. When i t consi stentl y exceeds 70% of the total bandwi dth, you may
need to recongure the systems on your LAN. I f you noti ce throughput/performance
degradati on on your system, contact your l ocal HP Representati ve for addi ti onal assi stance
and consul tati on.
No such interface: After I booted my server, I found that networki ng fai l ed. I found the
fol l owi ng error i n the /var/adm/rc.log l e:
ifconfig lan0: no such interface
How do I resol ve thi s probl em?
Answer: Thi s probl em i s caused by the LAN dri ver software di sabl i ng the LAN card because i t
was not connected to the LAN, or the LAN was down. Use lanadmin to reset the LAN card
and run ifconfig to bri ng the card up.
No such interface: When I congure an i nterface, ifconfig returns the error no such
i nterface. What shoul d I do?
Answer: The numeri c porti on of the i nterface name i s i ncorrect. Run the lanscan command to
obtai n a l i st of i nterface names.
Plumbing error: When I congure an i nterface, ifconfig returns a Pl umbi ng error
message. What shoul d I l ook for?
Answer: The i nterface name speci ed i n the ifconfig run stri ng i s not dened i n the /dev
di rectory or i s not a streams dri ver. The network devi ce l es /dev/ip and /dev/tcp are not
dened.
Cant communicate outside local supernet: I recentl y tri ed to set up a supernet on my
LAN. The systems i n the supernet can communi cate wi th one another, but they cannot
communi cate wi th systems outsi de the supernet.
Answer: Check the routi ng tabl e on your system and the node you want to communi cate wi th.
I f the system you want to communi cate wi th does not support supernetti ng, you wi l l have to
congure a network route for each of the networks i n the supernet. I f the system you want to
communi cate wi th supports supernetti ng, you wi l l onl y need to add a network route for the
supernet.
LAN Interface Card Statistics
Chapter 4 44
Thi s secti on contai ns descri pti ons of the RFC 1213 MI B I I stati sti cs el ds for LAN i nterface
cards whi ch are di spl ayed on the screen wi th the display command i n lanadmin LAN
I nterface Test Mode. A descri pti on of each el d fol l ows the di spl ay.
LAN INTERFACE STATUS DISPLAY
Mon, May 19,2003 11:16:22
Network Management ID = 1
Description = lan0 HP PCI Core I/O 1000Base-T Release B.11.23.00.01
Type (value) = ethernet-csmacd (6)
MTU Size = 1500
Speed = 10000000
Station Address = 0x80009266c3f
Administration Status (value) = up(1)
Operation Status (value) = up(1)
Last Change = 5917
Inbound Octets = 1862255299
Inbound Unicast Packets = 18765
Inbound Non-Unicast Packets = 7644729
Inbound Discards = 48847
Inbound Errors = 0
Inbound Unknown Protocols = 3877238
Outbound Octets = 1304687
Outbound Unicast Packets = 18721
Outbound Non-Unicast Packets = 19
Outbound Discards = 0
Outbound Errors = 0
Outbound Queue Length = 0
Specific = 655367
Ethernet-like Statistics Group
Index = 0
Alignment Errors = 0
FCS Errors = 0
Single Collision Frames = 0
Multiple Collision Frames = 0
Deferred Transmissions = 0
Late Collisions = 0
Excessive Collisions = 0
Internal MAC Transmit Errors = 0
Carrier Sense Errors = 0
Frames Too Long = 0
Internal MAC Receive Errors = 0
Chapter 4 45
RFC 1213 MIB II STATISTICS
Descri pti on A textual stri ng contai ni ng i nformati on about the i nterface. Thi s stri ng
i ncl udes the name of the manufacturer, the product name and the versi on of
the hardware i nterface.
Type (val ue) The type of i nterface, di sti ngui shed accordi ng to the physi cal /l i nk protocol (s)
i mmedi atel y bel ow the network l ayer i n the protocol stack. I t wi l l have one
of the fol l owi ng val ues:
Table4-1 Type(value)/Comments
other (1) None of the fol l owi ng
regul ar1822 (2)
hdh1822(3)
ddn-x25(4)
rfc877-x25(5)
ethernet-csmacd(6)
i so88023-csmacd(7)
i so88024-tokenBus(8)
i so88025-tokenRi ng(9)
i so88026-man(10)
starLan(11)
proteon-10Mbi t(12)
proteon-80Mbi t(13)
hyperchannel (14)
fddi (15)
l apb(16)
sdl c(17)
ds1(18) T-1
el (19) European equi val ent of T-1
Chapter 4 46
MTU Si ze The si ze of the l argest datagram whi ch can be sent/recei ved on the i nterface
speci ed i n octets.
Speed An esti mate of the current bandwi dth of the i nterface i n bi ts per second. For
i nterfaces whi ch do not vary i n bandwi dth or for those where no accurate
esti mates can be made, thi s object contai ns the nomi nal bandwi dth.
Stati on Address The i nterface address at the protocol l ayer i mmedi atel y bel ow the network
l ayer i n the protocol stack. For i nterfaces whi ch do not have such an
address, such as seri al l i ne, thi s object contai ns an octet stri ng of zero
l ength.
Admi ni strati on Status The desi red state of the i nterface I t wi l l have one of the fol l owi ng
val ues:
basi cI SDN(20)
pri maryI SDN(21) Propri etary seri al
proPoi ntToPoi ntSeri al (
22)
ppp(23)
softwareLoopback(24)
eon(25) CLNP over I P [11]
ethernet-3Mbi t(26)
nsi p(27) XNS over I P
sl i p(28) generi c SLI P
ul ta(29) ULTRA technol ogi es
ds3(30) T-3
si p(31) SMDS
frame-rel ay(32)
Table4-2 Administration Status
up(1) Ready to pass packets
down(2) Not operati ve
Table4-1 Type(value)/Comments (Continued)
Chapter 4 47
Operati on Status The current operati onal state of the i nterface. I t wi l l have one of the
fol l owi ng val ues.
Last Change The val ue of SysUpTi me at the ti me the i nterface entered i ts current
operati onal state. I f the current state was entered pri or to the l ast
rei ni ti al i zati on of the l ocal network management subsystem, then thi s
object contai ns a zero val ue.
I nbound Octets The total number of octets recei ved on the i nterface, i ncl udi ng frami ng
characters.
I nbound Uni cast Packets The number of subnetwork-uni cast packets del i vered to a
hi gh-l ayer protocol .
I nbound Non-Uni cast Packets The number of non-uni cast (subnetwork-broadcast or
subnetwork-mul ti cast) packets del i vers to a hi gher-l ayer protocol .
I nbound Di scards The number of i nbound packets that were di scarded even though no errors
had been detected, to prevent thei r bei ng del i vered to a hi gher-l ayer
protocol . One possi bl e reason for di scardi ng such a packet coul d be to free up
buffer space.
I nbound Errors The number of i nbound packets that contai ned errors preventi ng them from
bei ng del i verabl e to a hi gher-l ayer protocol .
I nbound Unknown Protocol s The number of packets recei ved vi a the i nterface whi ch were
di scarded because of an unknown or unsupported protocol .
Outbound Octets The total number of octets transmi tted out of the i nterface, i ncl udi ng
frami ng characters.
Outbound Uni cast Packets The total number of packets that hi gher-l evel protocol s requested
be transmi tted to a subnetwork-uni cast address, i ncl udi ng those that were
di scarded or not sent.
testi ng(3) I n test mode
Table4-3 Operation Status
up(1) Ready to pass packets
down(2) Not operati ve
testi ng(3) I n test mode
Table4-2 Administration Status (Continued)
Chapter 4 48
Outbound Non-Uni cast Packets The total number of packets that hi gher-l evel protocol s
requested be transmi tted to a non-uni cast (a subnetwork-broadcast or
subnetwork-mul ti cast) address, i ncl udi ng those that were di scarded or not
sent.
Outbound Di scards The number of outbound packets that were di scarded even though no
errors had been detected to prevent thei r bei ng transmi tted. One possi bl e
reason for di scardi ng such a packet coul d be to free up buffer space.
Outbound Errors The number of outbound packets that coul d not be transmi tted because of
errors.
Outbound Queue Length The l ength of the output packet queue (i n packets)
RFC 1284 Ethernet-Like Interface Statistics
I ndex A val ue that uni quel y i denti es an i nterface to an Ethernet-l i ke medi um.
Al i gnment Errors A count of frames recei ved on a parti cul ar i nterface that are not an i ntegral
number of octets i n l ength and do not pass the FCS check.
FCS Errors A count of frames recei ved on a parti cul ar i nterface that are not an i ntegral
number of octets i n l ength and do not pass the FCS check.
Si ngl e Col l i si on Frames A count of successful l y transmi tted frames on a parti cul ar i nterface
for whi ch transmi ssi on i s i nhi bi ted by exactl y one col l i si on.
Mul ti pl e Col l i si on Frames A count of successful l y transmi tted frames on a parti cul ar
i nterface for whi ch transmi ssi on i s i nhi bi ted by more than one col l i si on.
Deferred Transmi ssi ons A count of frames for whi ch the rst transmi ssi on attempt on a
parti cul ar i nterface i s del ayed because the medi um i s busy. The count
represented by an i nstance of thi s object does not i ncl ude frames i nvol ved i n
col l i si ons.
Late Col l i si ons The number of ti mes that a col l i si on i s detected on a parti cul ar i nterface
l ater than 512 bi t-ti mes i nto the transmi ssi on of a packet.
Excessi ve Col l i si ons A coupl e of frames for whi ch transmi ssi on on a parti cul ar i nterface fai l s
due to excessi ve col l i si ons.
I nternal MAC Transmi t Errors A count of frames for whi ch transmi ssi on on a parti cul ar
i nterface fai l s due to an i nternal MAC subl ayer transmi t error.
Carri er Sense Errors The number of ti mes that the carri er sense condi ti on was l ost or never
asserted when attempti ng to transmi t a frame on a parti cul ar i nterface.
Frames Too Long Account of frames recei ved on a parti cul ar i nterface that exceed the
maxi mum permi tted frame si ze.
Chapter 4 49
I nternal MAC Recei ve Errors A count of frames for whi ch recepti on on a parti cul ar i nterface
fai l s due to an i nternal MAC subl ayer recei ve error
100Base-T Checklist
Chapter 4 50
100Base-T Checklist
I n case of troubl e wi th 100Base-T LAN l i nks, you can use the fol l owi ng procedures to
troubl eshoot your network probl ems:
Verify Cabling: make sure the connecti on i s secured, UTP Category 5 i s used, the card i s
wel l i nserted. Al so, assure the cabl e l ength i s not wi thi n 35 - 41 meters. Check the cabl e
runni ng from the HP adapter to the Swi tch, and the Swi tch port, i n case ei ther i s
defecti ve.
I f the cabl e l ength i s between 35 - 41 meters, (or 114 - 133 feet), then expand or reduce
the l ength so that the cabl e i s l ess than 35 meters or greater than 41 meters, keepi ng
wi thi n 100Base-T speci cati ons.
Have your si te techni ci an veri fy that the pai r assi gnments and col or codes of the RJ45
connector pi ns match the fol l owi ng recommended versi on:
Recei ve Si gnal : pi n 1 = Whi te and pi n 2 = Orange
Transmi t Si gnal : pi n 3 = Whi te and pi n 6 = Green
Doubl e-check your exi sti ng punch-down bl ocks i n your networki ng envi ronment.
Punch-down bl ocks may affect the characteri sti cs of the medi um and therefore the
probl em seen wi th the 35-41 meter l ength cabl e may vary i n l ength.
Some vi si bl e symptoms that mi ght occur when the cabl e l ength i s between 35 - 41
meters are:
Li nk Status i s Down: LED l i ght col or turns amber because card negoti ati ng wi th
swi tch defaul ts to 10Mb/s i nstead of 100Mb/s. Or the LED l i ghts are i ntermi ttent
between 10Mb/s and 100Mb/s. They bl i nk between 10Mb/s and 100Mb/s and keep
doi ng that.
There i s no trafc or there i s hi gh rate of packet l oss.
To veri fy i f the l i nk i s not yet establ i shed, format l og l e usi ng the fol l owi ng
command and syntax:
netfmt -LN -f /var/adm/nettt.LOG* > outfile
Once the nettl l og l e i s formatted, l ook for a stri ng such as ...10/100Base-T dri ver
detected bad cabl e connecti on between the adapter i n sl ot #and the hub or swi tch.
100Base-T Checklist
Chapter 4 51
Or use the command lanscan to get the name of the Net I nterface Name or ppa number
or nmi d number. Once you have the ppa number, for exampl e l an17, you can i ssue these
fol l owi ng commands one at a ti me:
lanadmin
lan
ppa
17
display
- Look for the val ue of Operation Status. I t shoul d say DOWN.
Ensure that the host system contai ns the correct patch l evel . To nd out whi ch versi on of
the dri ver i s currentl y i nstal l ed, execute the command:
what /stand/vmunix | grep btlan
Or use the command:
swlist -l product | grep 100
Thi s shoul d di spl ay an ASCI I stri ng that i ndi cates the Versi on and possi bl y Patch l evel of
the dri ver. Many probl ems have been resol ved wi th newer versi ons of the dri ver, whi ch
can be obtai ned from the l atest patches for the 100Base-Tcards al ong wi th any dependent
patches. Work wi th the HP Response Center to determi ne i f there i s a newer dri ver that
xes the symptoms of the probl em you are faci ng.
There are three types of patches that are recommended:
- Patches for software driver
- Patch(es) for lanadmin - current lanadmin provides the
lanadmin -x -X functionality.
- Patch(es) for SAM - all systems need an updated SAM patch because SAM can step on
the 100Base-T configuration file Duplex mode.
Di spl ay the cards current speed and dupl ex, i ssue the command:
lanadmin -x NMID/PPA (nmid/ppa comes from the lanscan command)
I f probl ems persi st, i f a swi tch i s used, manual l y set the swi tch port to the desi red speed
and dupl ex.
Manual l y set the card to the desi red speed:
- for 100Base-T hubs: 100 Half Duplex
- for 10Base-T hubs: 10 Half Duplex
Manual setti ng can be done temporarily wi th the command:
100Base-T Checklist
Chapter 4 52
lanadmin -X speed/duplex nmid/ppa
Manual setti ng can be permanently set by modi fyi ng the congurati on l e i n
/etc/rc.config.d or by usi ng SAM (recommended way).
I f probl ems persi st: connect the card to a swi tch or hub that i s known to be good.
I f thi s connecti on works, contact the HP Response Center wi th the Swi tch/Hub
i nformati on. Thi s may be an I OP (I nteroperabi l i ty) probl em.
I f thi s connecti on fai l s, the card may be bad and may need to be repl aced.
Diagnostic Flowcharts
Chapter 4 53
Bel ow i s a summary of the types of network tests i n the di agnosti c owcharts. To di agnose
your probl em, rst check the connecti ons and congurati on on your system (Fl owcharts 1
through 5). I f thi s does not sol ve your probl em, use owcharts 6 through 11 to test/veri fy
connecti vi ty wi th a remote system.
1, 2 & 3 Congurati on Test
4 & 5 Network Level Loopback Test
6 Transport Level Loopback Test (usi ng I nternet Servi ces)
7 Li nk Level Loopback Test
8 LAN Connecti ons Test
9 &10 Gateway Remote Loopback Test
11 Subnet Test
Conguration Test: Veri es the congurati on of the network i nterface on a host usi ng the
lanscan, and ifconfig commands.
Network Level Loopback Test: Checks roundtri p communi cati on between Network Layers on
the source and target host usi ng the ping di agnosti c.
Transport Level Loopback Test: Checks roundtri p communi cati on between Transport Layers
on the source and target host usi ng I nternet Servi ces telnet and ftp commands.
Link Level Loopback Test: Checks roundtri p communi cati on between Li nk Level s on the
source and target host usi ng the linkloop di agnosti c.
LAN Connections Test: Checks the connecti ons between the LAN medi a and any component
between the LAN medi a and i ndi vi dual LAN cards.
Gateway Remote Loopback Test: Checks general network connecti ons through a gateway.
Chapter 4 54
Subnet Test: Veri es the correct use of subnets.
Figure4-1 Loopback Tests
The l oopback tests shown i n Fi gure 4-1 are used to i sol ate a network communi cati on probl em
that may be software- or hardware-rel ated. I n any case, you shoul d rst have checked that the
probl em i s not due to a recent congurati on change.
The network l evel l oopback test, ping, commonl y i s tri ed rst. I t i s fast, efci ent, and i t does
not requi re superuser pri vi l eges. I f the connecti on passes thi s test, you know the probl em i s at
OSI Layer 4 or above. Go on to the transport l evel l oopback test.
The Transport Level Loopback Test can be i mpl emented usi ng I nternet Servi ces. I n thi s case,
you use telnet and ftp to systemati cal l y focus on a probl em.
I f the network l evel l oopback test fai l ed, the probl em i s i n OSI Layer 3 or bel ow. I n thi s case,
conti nue wi th the l i nk l evel l oopback test, usi ng linkloop, to i sol ate a probl em to OSI Layer 2
or bel ow.
UDP
IP
LAN Driver
Network Interface Card
ARP
TCP
BSD Sockets
Virtual NFS Services
DLPI
Terminal Internet Services
1
2
3
6 & 7
5
4
ping
linkloop
lanadmin
ICMP
MAU
XTI
OSI Layer
telnet showmount
(NFS)
Chapter 4 55
The netstat uti l i ty reports network and protocol stati sti cs regardi ng trafc and the l ocal
LAN i nterface. As shown i n Fi gure 4-2, there are many opti ons to netstat. The opti ons that
are most useful are those whi ch di spl ay i nformati on that i s not avai l abl e through other
commands such as ping and lanadmin, for exampl e, -a and -r opti ons. You can al so use the
lanadmin command to obtai n LAN dri ver stati sti cs. For more detai l ed i nformati on on these
di agnosti cs, refer to the netstat(1M) and lanadmin(1M) man pages.
Figure4-2 Networking Software Statistics
1
2
3
6 & 7
5
4
netstat -r
lanadmin
netstat -a
netstat -s
netstat -i
UDP
IP
LAN Driver
Network Interface Card
ARP
TCP
BSD Sockets
Virtual NFS Services
DLPI
Terminal Internet Services
ICMP
OSI Layer
XTI
MAU
Chapter 4 56
Flowchart 1: Conguration Test
Figure4-3 Flowchart 1
1
A
B
C
no
yes
1
D
E
F
no
yes
no
2
Execute:
lanscan
All
interfaces
configured
?
Execute:
ioscan
bind
errors?
Correct
driver in
system
file?
Add correct
driver and regen
Call HP
Chapter 4 57
Flowchart 1 Procedures
A. Execute: lanscan. Execute lanscan to di spl ay i nformati on about LAN cards
that are successful l y bound to the system. For exampl e, to check the cards
on /stand/vmunix, enter:
lanscan
B. All interfaces congured? lanscan i s successful i f the output shows
i nformati on about every card i n the hardware backpl ane.
C. Execute ioscan. Execute the ioscan command to check for bi nd errors.
D. bind errors? I f a bi nd error exi sts, check that the hardware has been
properl y i nstal l ed.
E. Correct driver in / stand/ system le? Refer to Creati ng a New Kernel for
HP-UX Systems i n Chapter 3 for a l i st of LAN dri vers.
F. Add correct driver and regen. Edi t the /stand/system l e to contai n the
correct dri ver for your system type.
Chapter 4 58
Flowchart 2: Conguration Test continued
E
2
A
B C
yes
2
E
D
H I
no no
yes
no
yes
J
F
no
G
yes
no
yes
3
4
Execute
ifconfig <interface>
ifconfig
successful
?
Any
error message
returned?
Correct ifconfig
flag settings
Execute:
netstat -in
Interface
name
correct?
Correct
encapsulation
using ifconfig
Suspect
LAN card I/O
problem
?
Execute:
lanadmin
Problem
resolved
?
Call HP
Stop
Chapter 4 59
A. Execute: ifcong<interface>. Execute ifconfig on the i nterface you want to
test. For exampl e, to check LAN i nterface lan0, enter:
ifconfig lan0
B. ifcong successful? ifconfig i s successful i f the output shows the correct
I nternet address and the ags, typi cal l y: UP,BROADCAST,RUNNI NG.
C. Any error message returned? I f ifconfig i s not successful , and an error
message appears, go to Fl owchart 3. Fl owchart 3 shows common error
messages and what to do for each.
D. Correct ifcong ag settings. I f ifconfig returns an i ncorrect ag setti ng,
re-execute the command wi th the proper setti ng. For more i nformati on,
refer to the ifconfig(1M) man page. Start agai n wi th Fl owchart 2, as
necessary.
E. Execute: netstat -i. I f ifconfig i s successful , you know the network i nterface
has been congured correctl y. Usi ng netstat, you can return stati sti cs
whi ch show the i nterface i s operati onal . Enter:
netstat -in
netstat stati sti cs gi ve a qui ck check of key operati ng parameters. For
i nstance, i f the Opkts val ue does not change after attempti ng the l e
transfer, packets are not bei ng transmi tted. Si mi l arl y, i f the Ipkts val ue
does not change, packets are ei ther not bei ng recei ved by the l ocal node or
are not bei ng sent by the remote node, whi ch may not be recei vi ng your
transmi ssi ons.
F. I nterface name correct? Veri fy that the name for your i nterface i s what you
expect. See the ifconfig(1M) man page.
G. Correct encapsulation using ifcong. Use the ifconfig command to correct
the encapsul ati on method of your i nterface. For more i nformati on, refer to
the ifconfig(1M) man page. Go to E.
H. Suspect LAN card I / Oproblems?I f the stati sti cs i ndi cate possi bl e LAN card
probl ems, go to I , otherwi se go to Fl owchart 4.
I . Execute: lanadmin. Use lanadmin to ensure the LAN card i s operati onal . I f
the val ues of the Ierrs and Oerrs el ds i ncrease substanti al l y duri ng a l e
transfer attempt, thi s can i ndi cate transmi ssi on or recepti on probl ems.
Refer to LAN I nterface Card Stati sti cs i n thi s chapter for more
i nformati on.
Chapter 4 60
J. Problem resolved? I f you have found and corrected the LAN card probl em,
stop. I f not, cal l your HP representati ve for hel p. Be prepared to di scuss the
probl em as descri bed i n Contacti ng your HP Representati ve at the end of
thi s chapter.
Chapter 4 61
Flowchart 3: Conguration Test continued
3
I
J
D
N E
C
A
B
yes
no
G
H
F
K
L
M
yes
no
2
1
2
2
ifconfig
not found
Bad system
call
No such
interface
Check for
plumbing error
Any other
error message
Restore ifconfig
from media
Reconfigure
HP-UX kernel
to include
HP-UX LAN
Execute:
lanscan
Execute:
/sbin/init.d/net
.init start
Call HP
Find correct
interface
name
Execute:
netstat -in
Call HP Is Hardware
State UP?
Ping
127.0.0.1?
Call HP
Execute:
lanadmin
Chapter 4 62
A. ifcongnot found. The command has been rel ocated on the system, del eted,
or /usr/sbin i s not i n your PATH.
B. Restore / etc/ ifcong from media. You can restore ifconfig from the l ast
good backup tape or your i nstal l /update tape. Go to Fl owchart 2.
C. Bad system call. Networki ng i s not congured i nto the HP-UX kernel .
D. Recongure HP-UX kernel to include HP-UX LAN software. Edi t the
/stand/system l e to i ncl ude HP-UX LAN software. Refer to chapter 3 for a
l i st of LAN dri vers.
E. No such interface name. The i nterface name passed to ifconfig does not
exi st on the system. Check spel l i ng and names of i nterfaces on the system
usi ng lanscan.
I f you have more than one LAN card, make sure the number of LAN cards
has been congured i nto the kernel and that an ifconfig command has
been executed for each.
F. Execute lanscan. Execute lanscan to di spl ay i nformati on about the LAN
cards i n your system.
G. Find correct interface name. Usi ng the correct i nterface name, start agai n
wi th Fl owchart 1.
H. I s Hardware State UP? Veri fy the state of the hardware wi th the output
from the lanscan command. I f the Hardware State i s up cal l your HP
representati ve for hel p. Otherwi se go to I .
I . Executelanadmin. Use the lanadmin command to reset the LAN card. Go to
Fl owchart 2.
J. Check for the plumbing error: Bad le number. I f you see thi s error, the
TCP/I P stack has not yet been i ni ti al i zed.
K. I nitialize the TCP/ I P stack. Execute the command
/sbin/init.d/net.init start.
L. Check thestatus of thenetwork. Use the command netstat -in. Make sure
that the l oopback i nterface lo0 appears i n the di spl ay.
M. Check the loopback interface. Use the command ping 127.0.0.1. I f you
cannot pi ng the l oopback i nterface, cal l HP. I f the pi ng i s successful , go to
Fl owchart 2.
Chapter 4 63
N. Any other error message. I f you recei ved an error message not l i sted on thi s
owchart, i nterpret the message and take the appropri ate acti on. I f you
need assi stance, cal l your HP representati ve. Be prepared to di scuss the
probl em as descri bed i n Contacti ng Your HP Representati ve i n Chapter 5,
LAN Resources.
Chapter 4 64
Flowchart 4: Network Level Loopback Test
E
F
B C
G
I
A
D
H
J
4
yes
no
yes
yes
yes
yes
yes
no
no
no
no
no
4
4
4
5
Execute: ping
to remote host
ping
successful?
Network
unreachable
?
Local LAN
interface up
?
Call HP
Stop
Command
hangs?
Configure
interface up
Unknown
host?
Correct BIND, NIS,
or /etc/hosts
configuration
No route
to host?
Add route
table entry
Call HP
Chapter 4 65
A. Execute: pingtoremotehost. Usi ng ping, send a message to the remote host
wi th whi ch you are havi ng probl ems connecti ng. For exampl e, suppose the
remote host i s known as 192.6.20.2. Enter:
ping 192.6.20.2
NOTE HP recommends usi ng the I P address, rather than the hostname, as part of the
probl em may be an error i n the /etc/hosts l e or connecti vi ty wi th a name
server.
B. ping successful? A message i s pri nted on stdout for each ping packet
returned by the remote host. I f packets are bei ng returned, your system has
network l evel connecti vi ty to the remote host.
You may nd i t useful to note what percentage of the total packets are l ost,
i f any. Losi ng ten percent or more may i ndi cate the network or remote host
i s extremel y busy. I f, over a one-day peri od, ping reports a packet l oss that
you feel i s unacceptabl e, yet connecti vi ty remai ns, report thi s to your HP
representati ve.
You may al so nd i t useful to note the round-tri p transmi ssi on ti mes.
Peri odi cal l y hi gh transmi ssi on ti mes may i ndi cate that the network or
remote host i s extremel y busy. Consi stentl y hi gh transmi ssi on ti mes may
i ndi cate the l ocal host i s extremel y busy. Make sure that the network event
l oggi ng masks are not set to val ues whi ch can i mpai r system performance
(such as DEWRP).
C. Network unreachable? I f so, check the status of the l ocal LAN i nterface rst.
D. Local LAN interface up? Execute ifconfig on the l ocal i nterface to be sure
i t i s congured up.
E. Congure interface up. I f you nd the l ocal i nterface i s not up, execute
ifconfig wi th the appropri ate ags set. Start agai n wi th Fl owchart 4.
F. Command hangs? I f a message i s not returned after executi ng ping, go to
Fl owchart 5.
G. Unknown host? (Error= Unknown host hostname?) There i s a probl em wi th
the congurati on for the host i n the /etc/hosts l e or on the name server.
H. Correct BI ND, NI S or / etc/ hosts conguration. Add the mi ssi ng host name
and start agai n wi th Fl owchart 4.
Chapter 4 66
I . No route to host? (Error= Sendto: No route to host?) Use netstat -rn to
check the routi ng tabl e. I f there i s no route tabl e entry for the host, go to J.
Otherwi se, cal l your HP representati ve for hel p. Be prepared to di scuss the
probl em as descri bed i n Contacti ng Your HP Representati ve i n Chapter 5,
LAN Resources.
J. Add route table entry. Usi ng route, add a route tabl e entry for that host.
Chapter 4 67
Flowchart 5: Network Level Loopback Test continued
F
D
no
5
A B C
I
H
E
G
yes
yes
yes
yes yes
no
no
no
no
4
4
4
Host entry
in ARP cache
?
Remote
host up?
LAN card
OK?
Call HP
Bring up
remote host
Replace or
reset LAN card
Entry
complete?
Use arp to
complete entry
ping local host
ping
successful?
Call HP
Note: This time ping from
remote host to local host
Chapter 4 68
A. Host entry in ARP cache? Usi ng arp, check that an entry exi sts for the
remote host i n your system's ARP cache. For exampl e, suppose the remote
host i s known as 192.6.20.2. Enter:
arp 192.6.20.2
B. Remote host up? I f there i s no ARP cache entry for the remote host, rst
check that the remote host i s up. I f not, the remote host has not broadcast
an ARP message, and that l i kel y i s why there i s no entry i n the ARP cache.
C. LAN card O.K.? Use lanadmin to ensure the remote LAN card i s
operati onal .
D. Replaceor reset LAN card. When the LAN card i s operati onal , use lanadmin
to reset. Refer to the lanadmin command descri pti on or sampl e output i n
thi s chapter.
E. Bring-up remotehost. Have the node manager of the remote host bri ng that
system up.
F. Entry complete? Perhaps there i s an ARP cache entry, but i t i s wrong or not
compl ete.
G. Use arp to complete entry. Usi ng arp, enter the correct Stati on Address. For
more i nformati on, refer to the arp(1M) man page.
H. pinglocal host. Usi ng ping, do an i nternal l oopback on your own system. I n
other words, ping your own I P address. Thi s wi l l determi ne i f the probl em i s
on your end.
I . ping successful? I f the i nternal l oopback i s successful , your system i s
operati ng properl y to the Network Layer (OSI Layer 3). I n addi ti on, you
know an ARP cache entry for the remote host exi sts on your system. I f thi s
i s true, the network i nterface or software on the remote host i s suspect.
Start agai n wi th Fl owchart 4, but thi s ti me ping from the remote host to
your system.
I f the ping was not successful , cal l your HP representati ve for hel p.
Chapter 4 69
Flowchart 6: Transport Level Loopback Test (usingInternet Services)
6
B
A
yes
C
F
D
E
G
6
no
no
no
yes
yes
Execute: telnet
to remote host
Successful?
Stop
Execute: ftp
to remote host
Successful?
Call HP
Check for
network congestion
Call HP
TCP
configured on
local or remote
host?
Configure TCP
Chapter 4 70
A. Execute: telnet to remote host. Try to establ i sh a telnet connecti on to the
remote host.
B. Successful? I f your telnet attempt was successful , stop. The connecti on i s
okay through the Transport Layer (OSI Layer 4).
C. Execute: ftp to remote host. Unl i ke telnet, ftp does not go through a
pseudo-termi nal dri ver (pty) on your system. Thi s step tests to see i f the pty
i s why telnet fai l ed.
D. Successful?I f ftp i s successful , you l i kel y have a probl em wi th a pty on your
system. Contact your HP representati ve.
E. TCP congured on local or remote host? Nei ther telnet or ftp wi l l work i f
TCP i s not congured on ei ther si de of the connecti on. Check the
/etc/protocols l e on both hosts to be sure TCP i s i nstal l ed and
congured.
F. Congure TCP. I f necessary, i nstal l TCP on ei ther or both hosts.
G. Network congested? I f TCP i s i nstal l ed on both hosts, do a l e transfer to
another remote host on the network. Use netstat to check for l ost packets.
I f 10 percent or more packets are l ost, the network i s extremel y busy. I f you
cannot determi ne the cause, contact your HP representati ve for hel p.
I f both ftp and telnet fai l , the /etc/inetd.conf l e may be congured
i ncorrectl y or the inetd daemon may not be runni ng on the remote system.
I f the probl em i s not resol ved, more detai l ed di agnosti cs are requi red.
Agai n, contact your HP representati ve.
Chapter 4 71
Flowchart 7: Link Level Loopback Test
7
B
A
no
yes
D
J
7
C
E
F G
H
I
K
yes yes
no
no
8
Execute: linkloop
on local interface
Successful?
Execute: linkloop
to remote host
linkloop
successful?
Stop
Loopback FAILED:
Address has bad
format
Loopback FAILED:
Not an individual
address
Loopback FAILED
Correct the link
address parameter
Choose a different
remote IEEE 802.3
host; re-execute
linkloop
Check remote host
connectivity to LAN
linkloop
successful?
Stop
Chapter 4 72
A. Execute: linkloop on local interface. Execute the linkloop command wi th
the stati on address of the l ocal i nterface. Execute lanscan to nd the l i nk
l evel address (stati on address) on the remote host or obtai n i t from your
network map. For more i nformati on, refer to the linkloop(1M) man page.
B. linkloop successful? I f not, your LAN card may not be operati onal . Go to
Fl owchart 8.
C. Execute: linkloop to remote host. Enter the l i nk l evel address (stati on
address) of the remote host.
D. linkloop successful? I f the test was successful , stop. Network connecti vi ty i s
okay through the Li nk Layer (OSI Layer 2). I f not successful , note whi ch
error was returned and conti nue wi th thi s owchart.
E. Loopback failed; Address has bad format. The l i nk l evel address i s not
correct. Go to H.
F. Loopback failed; Not an individual address. The l i nk l evel address i s not
correct. The second hexadeci mal di gi t i s odd. Thi s means i t i s a mul ti cast or
broadcast address, whi ch i s not al l owed. The address must be uni que to one
remote host. Go to H.
G. Loopback failed. The remote host di d not respond. Go to I .
H. Correct the link address parameter. Change the l i nk l evel address to an
al l owed val ue and go to C.
I . Choose a different I EEE 802.3 host; re-execute linkloop. Restart thi s
owchart usi ng a di fferent remote host. NOTE: Make sure the remote host
i s an HP Server and try agai n.
J. linkloop successful? I f the test was successful , stop. Network connecti vi ty i s
okay through the Li nk Layer (OSI Layer 2). I f not successful , go to K.
K. Check remote host's connectivity to LAN. Contact the node manager of the
remote host. Check that the host i s congured correctl y and that i ts network
i nterface i s up. I f necessary, use Fl owcharts 1 and 12 to veri fy congurati on
and connecti vi ty of the remote host.
Chapter 4 73
Flowchart 8: LAN Connections Test
8
A
B
yes
no
G
C
D
E
H
I
F
J
K
ThinLAN
Thick Coax
Check: AUI
solidly connected to
LAN card
Thick or
thin cabling
?
Check: AUI
solidly connected to
MAU and LAN card
Check: ThinLAN
cable terminated
at both ends
Check: Backbone
cable terminated
at both ends
Check: BNC
T-connectors secure
Check: MAU tapped
securely into cable
Check: Splices
and taps
Check: Backbone
cable grounded
in only one place
Check: ThinLAN
cable grounded
in only one place
Problem
solved?
Stop
Call HP
RJ45
LED = ON
No
A1
A2
?
Card seated
securedly
RJ45:
Chapter 4 74
A. Thick or thin cabling? I f your network cabl i ng i s the thi cker coaxi al cabl i ng,
conti nue i n the di recti on marked Thi ck Coax. I f your network cabl i ng i s
the Thi nLAN cabl i ng, conti nue i n the di recti on marked Thi nLAN.
A1. RJ 45 Adapter? Veri fy LEDs. Network Acti vi ty and Li nk Status LED
di spl ays: Li nk Status LED i s l i t GREEN for a val i d l i nk. Network Acti vi ty
LED i s l i t AMBER col or for both 10 Mbps and 100Mbps. Someti me Li nk
Status LED i s not l i t up at 10 Mbps mode.
A2. Card seated securely? Check adapter i nstal l ati on, reset and reseat adapter.
Check for i ncorrect or faul ty network cabl e or connector. Ensure setti ngs for
swi tch and adapter are the same.
B. Check: AUI solidly connected to LAN card. Make sure the AUI cabl e i s
sol i dl y connected to the LAN card. I f the AUI cabl e i s not connected, turn off
the power to the computer before you connect i t.
C. Check: ThinLAN cable terminated at both ends. Make sure the backbone
cabl e i s termi nated at both ends.
D. Check: BNC T-connectors secure. Make sure each BNC T-connector i s
securel y attached to a BNC connector on the Thi nLAN cabl e and that no
i nterveni ng cabl e i s between the MAU and the T-connector.
E. Check: ThinLAN cable grounded in only one place. Make sure the Thi nLAN
cabl e i s grounded i n onl y one pl ace.
F. Problemsolved?I f so, stop. I f you sti l l have a probl em after worki ng through
thi s owchart, you may have a fai l ed LAN card, an i ncorrect jumper setti ng
on the LAN card, or a probl em wi th the transmi t or recei ve functi on of the
MAU. Contact your HP representati ve for hel p. Be prepared to di scuss the
probl em as descri bed i n Contacti ng Your HP Representati ve at the end of
thi s chapter.
G. Check: AUI solidly connected to MAU and LAN card. Make sure the AUI
cabl e i s sol i dl y connected to the MAU and the LAN card. I f the AUI cabl e i s
not connected, turn off the power to the computer before you connect i t.
H. Check: Backbone cable terminated at both ends. Make sure the backbone
cabl e i s termi nated at both ends.
I . Check: MAU tapped securely into cable. Make sure the MAU i s tapped
securel y i nto the backbone cabl e.
J. Check: Splices and Taps. Make sure al l spl i ces and taps are secure.
Chapter 4 75
K. Check: Backbone cable grounded in only one place. Make sure the backbone
cabl e i s grounded i n onl y one pl ace.
Chapter 4 76
Flowchart 9: Gateway Remote Loopback Test
9
A
yes
no
B
C
E
G
D
F
yes
yes
no
no
10 4
10
Execute: ping from
known good host
through gateway to
known good remote host
ping
successful
?
Stop
Execute:
netstat -rn
Add route entry
on local system
Direct
route to remote
or default route
to gateway?
Routing
table on remote
OK?
Correct
routing table
Chapter 4 77
A. Execute: pingfromknown good host through gatewaytoknown good host on
remote network. Thi s wi l l test gateway connecti vi ty to the remote network.
For more i nformati on on ping, refer to chapter 6.
B. pingsuccessful? I f the executi ng ping returned does not return successful l y,
the probl em may exi st i n the routi ng tabl e for the probl em host. Go to C.
C. Execute netstat -rn. To di spl ay gateway routi ng i nformati on i n numeri cal
form, execute:
netstat -rn
D. Direct routetoremoteor default routetogateway? I f the route exi sts, go to F.
I f not, go to E to add a new route.
E. Add route entry on local system. Use the route command to add a route
entry to the route tabl e on the l ocal system. Refer to the route(1M) man
page for a compl ete descri pti on of the command.
F. Routing table on remote OK? Check that the routi ng i nformati on on the
remote system i s OK.
G. Correct routingtable. I f the routi ng i nformati on i s i ncorrect, correct i t usi ng
the route command.
Chapter 4 78
Flowchart 10: Gateway Remote Loopback Test continued
10
F G
yes
no
E
D
A
C
B
no
1 4
Examine
gateway
Other HP;
other vendors
HP-UX
Refer to networking
documentation
Execute: ifconfig
on gateway host
Network
interface up?
Configure
interface up
Chapter 4 79
A. Examinegateway. I f the gateway i s an HP-UX Server, go to D. I f i t i s not, go
to B.
B. Other HP; other vendors. Go to C.
C. Refer to networking documentation. Refer to the documentati on that came
wi th the gateway for addi ti onal di agnosti cs.
D. HP-UX. Go to E.
E. Execute: ifcong on gateway host. Execute ifconfig for al l network
i nterfaces on the gateway.
NOTE Running i s al ways di spl ayed by i fcong output. I t i ndi cates onl y that there i s
OS support for the i nterface.
F. Network interface up? I f the output from ifconfig does not i ncl ude the UP
parameter, the network i nterface i s down. Execute netstat -in to check
the status of the network i nterfaces. An asteri sk (*) next to the i nterface
i ndi cates that the i nterface i s down.
I f the network i nterface i s down, go to Fl owchart 2. I f the network i nterfaces
are UP, start agai n wi th Fl owchart 1. Usi ng Fl owchart 1, test al l network
i nterfaces on the gateway.
Use netstat -in to make sure that the congured encapsul ati on i s correct.
G. Congure interface up. Execute ifconfig on each i nterface to bri ng i t up.
Start agai n wi th Fl owchart 1. Usi ng Fl owchart 1, test al l network i nterfaces
on the gateway.
Chapter 4 80
Flowchart 11: Subnet Test
A
I
11
D
H
G
E
J
K
no
no
no
yes
yes
yes
yes
F
11
11a
11a
11a
Host
portion all 0s
or all 1s?
Subnet mask
set to what you
expect?
Correct IP
address
All
hosts on
subnet using
same subnet
mask?
Correct
subnet mask
All
hosts on
network have
subnet mask
set?
Correct
subnet mask
Check route table on
source, destination
Stop
Correct
route tables
no
B
Correct IP
address
Chapter 4 81
A. Host Portion all 0's or all 1's? Execute ifconfig. I s the host porti on of the
I P address al l 0's or al l 1's? These val ues are reserved. Refer to chapter 6 for
detai l s on subnets. I f the host porti on of the I P address i s al l 0's or al l 1's, go
to B to correct the I P address. Otherwi se, go to C to exami ne the subnetwork
number.
B. Correct I P address. Correct the I P address and start agai n wi th Fl owchart
11.
D. Subnet mask set to what you expect? Check your network map and execute
ifconfig to determi ne the subnet mask for your node. Refer to Chapter 6
for detai l s on subnets. I f the subnet mask i s not what you expect, go to I .
Otherwi se, go to E.
E. All hosts on subnet using same subnet mask? Execute ifconfig for every
network i nterface on each node on the enti re network. I f al l nodes are usi ng
the same subnet mask, go to F. Otherwi se, go to J to correct the subnet
masks.
F. All hosts on network have subnet mask set? Execute ifconfig for every
network i nterface on each node on the enti re network. I f al l nodes have the
same subnet mask set, go to G. Otherwi se, go to K to set the correct subnet
masks.
G. Check route table on source, destination. Execute netstat -rv on the two
hosts. Go to H.
H. Correct the route tables (if necessary). I n general , speci fy a network, not a
host when addi ng to the route tabl e. Speci fyi ng a network as the desti nati on
enabl es you to add nodes to the remote desti nati on subnetwork wi thout
updati ng the route tabl es on the l ocal subnetwork every ti me you add a node
to the remote subnetwork.
I . Correct I P address. Set the subnet mask to the proper val ue. Go to D.
J. Correct subnet mask. To do so, execute ifconfig wi th the proper subnet
mask. Go to D.
K. Correct subnet mask. To do so, execute ifconfig wi th the proper subnet
mask. Go to D.
Chapter 4 82
Chapter 5 83
5 LAN Resources
I n addi ti on to thi s manual , use the fol l owi ng resources to mai ntai n and admi ni ster HP
HP-UX LAN software.
LAN ResourcesDRAFT COPY
HP-UX Man Pages
Chapter 5 84
HP-UX Man Pages
Whi l e i nstal l i ng, conguri ng, or troubl eshooti ng HP-UX LAN, you may need to refer to any of
the fol l owi ng onl i ne man pages (manual reference pages) for useful HP-UX operati ng system
or HP-UX LAN commands. To di spl ay a man page, type the fol l owi ng at the system prompt:
man <command name>
arp(1M) di spl ays and modi es the I nternet-to-Ethernet and I nternet-to-Fi bre Channel
address transl ati on tabl es used by the Address Resol uti on Protocol .
hosts(4) contai ns database that contai ns a si ngl e l i ne entry for each host name entry.
ifalias(1M) congures network i nterface to support mul ti pl e I P addresses at Network
Layer.
ifconfig(1M) assi gns an address to a network i nterface and congures parameters, such
as the netmask, broadcast address, and trai l er support.
ioscan(1M) scans system hardware, usabl e I /O system devi ces, or kernel I /O system data
structures as appropri ate, and l i sts the resul ts.
lanadmin(1M) resets or reports status of the LAN card.
lanconfig(1M) congures network i nterface parameters at Data-Li nk Layer.
lanscan(1M) di spl ays i nformati on about LAN adapters that are successful l y bound to the
system.
linkloop(1M) veri es network connecti vi ty through the Data Li nk Layer.
ndd(1M) di spl ays and modi es network dri ver parameters.
netfmt(1M) formats the nettl traci ng and l oggi ng bi nary l es.
netstat(1M) provi des network stati sti cs and i nformati on about network connecti ons.
nettladm(1M) captures and control s network traci ng and l oggi ng i nformati on.
nettl(1M) control s network traci ng and l oggi ng.
ping (1M) veri es network connecti vi ty through the Network Layer and reports
round-tri p ti me of communi cati ons between the l ocal and remote hosts.
route(1M) adds and del etes entri es to the network routi ng tabl e, al l owi ng your system to
communi cate through a gateway.
swinstall(1M) l oads software l esets onto 10.0 systems.
traceroute(1M) traces the network path between two poi nts at Network Layer.
DRAFT COPY LAN Resources
Logging and Tracing Messages
Chapter 5 85
Logging and Tracing Messages
HP-UX LAN comes wi th an onl i ne message catal og that reports LAN probl ems, probabl e
causes, and acti ons for you to take to correct the probl ems. Messages are sent ei ther to the
system consol e or l og l es based on the l oggi ng and traci ng congurati on. To vi ew the
probabl e cause and acti on text of the message, use the netfmt command wi th the -v opti on.
Bel ow i s an exampl e.
# netfmt -v -f /var/adm/nettl.LOG00
**********************LAN/9000 NETWORKING*********************
Timestamp : Tue Apr 04 PDT 1995 10:15:13.290279
Process ID : [ICS] Subsystem : NS_LS_DRIVER
User ID ( UID ) : -1 Log Class : ERROR
Device ID : 0 Path ID : 0
Connection ID : 0 Log Instance: 0
Location : 02004
Network NS_LS_DRIVER Error 2004, pid [ICS]

82596 External loopback test failed.
The loopback test through the external MAU Failed
Check the LAN cable to make sure its properly connected to the
LAN card.Use the lanscan (1M) command to find the NMID of the
LAN card and reset this card. If the reset does not solve the
problem, reboot.
If rebooting is ineffective, notify your HP representative.
HP-UX LAN uses the nettl l oggi ng and traci ng faci l i ty suppl i ed wi th HP-UX to capture,
control , and format messages produced by LAN. See the nettl(1M) man page for i nformati on
on usi ng the graphi cal user i nterface or command l i ne i nterface. The graphi cal i nterface,
whi ch i s accessed by runni ng the nettladm command, i ncl udes the fol l owi ng features:
screens whi ch take you through any l oggi ng or traci ng task desi red
screens whi ch al l ow you to create and format reports
the capabi l i ty of l oggi ng and traci ng subsystem-speci c i nformati on
mai n screens whi ch are updated i nstantaneousl y wi th current l oggi ng and traci ng
i nformati on by subsystem
context-sensi ti ve on-l i ne hel p
Contacting Your HP Representative
Chapter 5 86
I f you do not have a servi ce contract wi th HP, you may fol l ow the procedure descri bed bel ow,
but you wi l l be bi l l ed accordi ngl y for ti me and materi al s.
I f you have a servi ce contract wi th HP, document the probl em as a Servi ce Request (SR) and
forward i t to your HP representati ve. I ncl ude the fol l owi ng i nformati on where appl i cabl e:
A characteri zati on of the probl em. Descri be the events and symptoms l eadi ng up to the
probl em. Attempt to descri be the source of the probl em.
Your characteri zati on shoul d i ncl ude: HP-UX commands; communi cati on subsystem
commands; functi onal i ty of user programs; resul t codes and messages; and data that can
reproduce the probl em.
Obtai n the versi on, update, and x i nformati on for al l software. To check your I nternet
Servi ces or HP-UX LAN versi on, execute the command:
what /stand/vmunix
To check the versi on of your kernel , execute the command:
uname -a
Thi s al l ows HP to determi ne i f the probl em i s al ready known, and i f the correct software
i s i nstal l ed at your si te.
I l l ustrate as cl earl y as possi bl e the context of any message(s). Record al l error messages
and numbers that appear at the user termi nal and the system consol e.
Prepare a l i sti ng of the HP-UX I /O congurati on you are usi ng for your HP representati ve
to further anal yze.
Try to determi ne the general area wi thi n the software where you thi nk the probl em
exi sts. Refer to the appropri ate reference manual and fol l ow the gui del i nes on gatheri ng
i nformati on for that product.
Document your i nteri m, or workaround, sol uti on. The cause of the probl em can
someti mes be found by compari ng the ci rcumstances i n whi ch i t occurs wi th the
ci rcumstances i n whi ch i t does not occur.
Create copi es of any I nternet Servi ces or HP-UX LAN l i nk trace l es that were acti ve
when the probl em occurred for your HP representati ve to further anal yze.
DRAFT COPY LAN Resources
Chapter 5 87
I n the even of a system fai l ure, obtai n a ful l memory dump. I f the di rectory
/var/adm/crash exi sts, the HP-UX uti l i ty /usr/sbin/savecore automati cal l y executes
duri ng reboot to save the memory dump. Hewl ett-Packard recommends that you create
the /var/adm/crash di rectory after successful l y i nstal l i ng thi s product. Send the output
of your system fai l ure memory dump to your HP representati ve.
Prepare copi es of the /etc/hosts and /etc/rc.config.d/netconf l es as wel l as any
dri ver speci c congurati on l es that appl y.
Run the veri cati on command, /usr/sbin/swverify, and record the output.
Execute the display command of the lanadmin di agnosti c on the LAN i nterface and
record the output.
Record the troubl eshooti ng owchart number and step number where you are unabl e to
resol ve the probl em.
Save al l network l og l es. Make sure that ERROR and DI SASTER l og cl asses are enabl ed
when l og l es are col l ected.
Execute the fol l owi ng commands and record the output:
netstat -s >> /tmp/filename
netstat -in >>/tmp/filename
netstat -rvn >>/tmp/filename
ndd -get /dev/tcp tcp_status >>/tmp/filename
ndd -get /dev/ip ip_ill_status >>/tmp/filename
ndd -get /dev/ip ip_ipif_status >>/tmp/filename
ndd -get /dev/ip ip_ire_status >>/tmp/filename
ndd -get /dev/ip ip_ill_config_status >> /tmp/filename
ndd -get /dev/arp arp_cache_report >> /tmp/filename
arp -an >>/tmp/filename
lanscan >>/tmp/filename
what /stand/vmunix >>/tmp/filename
uname -a >>/tmp/filename
Prepare the formatted output and a copy of the l og l e for your HP representati ve to further
anal yze.
Chapter 5 88
Chapter 6 89
6 Network Addressing
Thi s chapter i ntroduces network addressi ng concepts. I t contai ns the fol l owi ng secti ons:
Overvi ew of Network Addressi ng Schemes
Network AddressingDRAFT COPY
Chapter 6 90
Networki ng Termi nol ogy
Network Addresses and Node Names
I nternet Addresses
Subnet Addresses
Conguri ng Gateways on Fi xed-Length Subnets
Vari abl e-Length Subnet Addressi ng
Conguri ng Gateways on Vari abl e-Length Subnets
Conguri ng Gateways on Supernets
I P Mul ti cast Addresses
Vi rtual I P (VI P) Addresses
CI DR - Cl assl ess I nter-Domai n Routi ng
DRAFT COPY Network Addressing
Overview of Network Addressing Schemes
Chapter 6 91
On the HP-UX 11i v2 Rel ease, Hewl ett-Packard offers several types of addressi ng schemes.
Tabl e 6-1 bel ow shows the advantages and di sadvantages of each type of scheme.
Table6-1 Comparison of Subnet and Supernet Addressing Schemes
Address Type Advantages Disadvantages
Fi xed-Length
Subnet
Addressi ng
Si mpl i ci ty
- same netmask across network
- same si ze subnets across the
network
I nefci ency & I nexi bi l i ty
- waste of address space
- same si ze subnets across
the network
- cannot grow subnet beyond
the xed si ze
Vari abl e-Length
Subnet
Addressi ng
Efci ency & Fl exi bi l i ty
- address space al l ocated
accordi ng to projected si ze of
subnets
- vari abi l i ty i n subnet si ze
- expandabi l i ty i n subnet si ze
- grow subnet by changi ng
subnet mask onl y
Compl exi ty
- keepi ng track of subnet
ranges
- keepi ng track of netmasks
Supernet
Addressi ng
Si mpl i ci ty
- same netmask across subnets
- no gateway congurati on for
networks
Network I mpact
- performance. Network
bandwi dth i s shared by al l
nodes i n the supernet.
- requi res bri dges i f the
supernet i s spread across
mul ti pl e physi cal networks
Chapter 6 92
NOTE I f you are al ready usi ng the xed-l ength addressi ng scheme and do not need
extra addressi ng space, then i t i s recommended that you not convert your
network to one of the new addressi ng schemes.
Refer to the Subnet Addresses subsecti on for i nformati on on xed-l ength and
vari abl e-l ength addressi ng.
Networking Terminology
Chapter 6 93
Fol l owi ng are descri pti ons of i mportant networki ng terms.
Nodes
A node i s a computer on the network. Local node (or host) refers to the computer or host to
whi ch your termi nal i s physi cal l y attached. A remote node i s a computer on the network
wi th whi ch your l ocal node can communi cate. A remote node does not have to be di rectl y
attached to your termi nal .
Routes and Protocols
A route i s the sequence of network nodes through whi ch messages travel when sent from a
source node to a desti nati on node.
A protocol i s a set of rul es for a parti cul ar communi cati on task. A protocol handl er or
protocol modul e i s a pi ece of software that i mpl ements a parti cul ar protocol .
Network Interface Name
A network interface i s a communi cati on path through whi ch messages can be sent and
recei ved. A hardware network i nterface has a hardware devi ce associ ated wi th i t, such as an
Ethernet, Fi bre Channel , ATM, Token Ri ng, or FDDI card. A software network i nterface does
not i ncl ude a hardware devi ce, (for exampl e, the loopback i nterface). An I P address i s
associ ated wi th an i nterface name. The i nterface name(s) for a hardware network i nterface
can be found by runni ng the lanscan command and l ooki ng at the Net-I nterface Name PPA
el d.
For Ethernet cards, you can choose ei ther Ethernet encapsul ati on by speci fyi ng lan when
conguri ng the i nterface, or I EEE 802.3 encapsul ati on by speci fyi ng snap when conguri ng
the i nterface.
The i nterface name may i ncl ude a col on (:), fol l owed by a number that denotes the l ogi cal
i nterface number. The number 0 i s the rst l ogi cal i nterface number for a card/encapsul ati on
type and i s known as the i ni ti al i nterface. The i nterface name l an0 i s equi val ent to l an0:0,
l an1 i s equi val ent to l an1:0, and so on.
You must congure the i ni ti al i nterface for a card/encapsul ati on type before you can congure
subsequent i nterfaces for the same card/encapsul ati on type. For exampl e, you must congure
l an0:0 (or l an0) before you congure l an0:1 and l an0:2. Once you have congured the i ni ti al
i nterface, you can congure the subsequent i nterfaces i n any order. Note that the I P
Chapter 6 94
addresses assi gned to a card may be on the same subnet or on di fferent subnets. See the
secti on I nterfaces, i n Chapter 7 for more i nformati on about l ogi cal i nterfaces and i nterface
names.
An i ni ti al i nterface cannot be removed from the system unti l al l subsequent l ogi cal i nterfaces
are removed. You can remove subsequent i nterfaces from the system wi th the ifconfig
command, as i n the fol l owi ng exampl e:
ifconfig lan1:1 inet 0.0.0.0
The i ni ti al i nterface (for exampl e, l an1) can then be removed from the system wi th the
ifconfig command, as i n the fol l owi ng exampl e:
ifconfig lan1 unplumb
A l oopback i nterface does not have a hardware devi ce associ ated wi th i t. The name of thi s
type of i nterface i s lo0, denoti ng the l oopback i nterface. A l oopback i nterface i s automati cal l y
created by the TCP/I P stack even i f the system i s not connected to a network.
Gateway
A gateway i s a devi ce used to connect two or more networks. The gateway serves to route
i nformati on among the networks. An HP-UX Server wi th two or more LAN cards i nstal l ed
may act as a LAN-to-LAN gateway. Such a node may al so be referred to as a LAN-to-LAN
router or I P router. I f a node i s a gateway, i t affects how you congure and mai ntai n LAN
software. Refer to node D i n the network maps i n Fi gure 6-7 and Fi gure 6-13 for exampl es of
gateways. A gateway system has to have at l east two network i nterfaces congured, one for
each network to whi ch i t bel ongs. A gateway can be ei ther a router or a system.
Routing Table
Each node on the LAN has a routi ng tabl e. A routing table contai ns i nformati on about the
route to nodes on other LANs. The connecti ons to other LANs are made through gateways.
ARP Cache
Each i nterface card on a system i s i denti ed by an I P address and a stati on address. The ARP
cache contai ns the I P address of a remote i nterface and the stati on address whi ch i s used to
send packets to that I P address. I f the remote system i s not on the same physi cal network, the
stati on address i n the ARP cache i s for an i nterface on a gateway.
Usual l y, an ARP cache entry i s automati cal l y created when the system needs to send the rst
packet to a remote I P address. ARP cache entri es are usual l y del eted automati cal l y when they
have not been used for a peri od of ti me.
Chapter 6 95
Several types of names and addresses are used i n networki ng software. Thi s can be confusi ng
to rst-ti me users. Tabl e 6-2 i l l ustrates whi ch address type i s used by each l ayer of the OSI
model . A descri pti on of each address type and how i t i s used by LAN and the servi ces whi ch
run on i t fol l ows i nTabl e 6-3. Refer to Network and System Names on page 28 for addi ti onal
i nformati on on how these names are assi gned.
Table6-2 Network Addresses and the OSI Model
OSI Layer
Name
OSI Layer
Function
Address Type
Used
7 Appl i cati on network programs hostname
6 Presentati on data
i nterpretati on
hostname
5 Sessi on connecti on control socket address
4 Transport end-to-end
transfer
port address
3 Network routi ng and
swi tchi ng
I nternet (I P)
address
2 Data Li nk data packagi ng
and error
detecti on
l i nk l evel address
1 Physi cal physi cal
connecti on
l i nk l evel address
Chapter 6 96
Table6-3 Network Address Types, Descriptions, and Examples
Address
Type
Description Recorded In Used By
l i nk l evel
address
Al so referred to as MAC address
or station address.
A l i nk l evel address i s the uni que
address of the LAN i nterface card.
Thi s val ue can be congured i n
SAM and lanadmin.
An exampl e of a l i nk l evel address
i n hexadeci mal : 0800090012AB.
I nterface card; can
be changed i n
/etc/rc.config.d
/hpbtlanconf l e.
Refer toTabl e 3-2
for sampl e
l enames.
linkloop
di agnosti c;
i nternal s of
networki ng
software to
uni quel y
i denti fy nodes
on the LAN;
di spl ayed by
lanadmin and
lanscan
di agnosti cs.
i nternet (I P)
address
Al so referred to as IP address.
An i nternet address i s the
network address of a computer
node. Thi s address i denti es
whi ch network the host i s on (see
network address descri pti on
bel ow) and whi ch host i t i s (see
host address descri pti on bel ow).
An exampl e of an i nternet
address: 192.6.23.3
/etc/hosts;
/etc/rc.config.d
/netconf.
Typi cal l y used
i n combi nati on
wi th the
network
address to form
an i nternet
address.
HP-UX
ifconfig
command.
Chapter 6 97
network
address
Al so, network number.
The network address i s the
network porti on of an i nternet
address that represents the l ocal
network on whi ch a host exi sts.
The network address i s the same
for al l nodes on that network.
Refer to I nternet Addresses i n
thi s chapter for a deni ti on of
I nternet address cl asses.
I f the I P address i s 192.6.23.3
(Cl ass C), and the subnet address
i s 255.255.255.0, then the
network address porti on i s
192.6.23.
/etc/networks.
Combi ned wi th
host address i n
/etc/hosts.
Routi ng faci l i ty.
Di spl ayed by:
netstat -in,
netstat -rn,
and netstat
-rnv.
HP-UX
ifconfig
command.
host address Al so, host number.
The host address i s that porti on of
the i nternet address that i s
uni que to the network. The host
address i denti es a parti cul ar
node on the network. Refer to
I nternet Addresses i n thi s
chapter for a deni ti on of I nternet
address cl asses.
I f the I P address i s 192.6.23.3
(Cl ass C), and subnet address i s
255.255.255.0, then the host
address porti on i s 3.
Combi ned wi th
network address i n
/etc/hosts.
Typi cal l y used
i n combi nati on
wi th the
network
address to form
an i nternet
address.
HP-UX
ifconfig
command.
Table6-3 (Continued) (Continued)Network Address Types, Descriptions,
Address
Type
Chapter 6 98
port address Al so referred to as TCP port
number, UDP port number, or
si mpl y port.
A port address i s an address
wi thi n a host that i s used to
di fferenti ate between mul ti pl e
communi cati on endpoi nts wi th
the same i nternet address and
protocol . A port address i s
associ ated wi th a parti cul ar
servi ce. Wel l known port numbers
are dened by RFC 923, Assi gned
Numbers.
For exampl e, i f your l ocal address
i s l i sted as 192.6.23.3.1023, then
.1023 i s the port address.
/etc/services. Servi ce
requests.
Di spl ayed by
netstat -an.
socket
address
A socket address i s decl ared i n
processes dened by the
i nterprocess communi cati on
software. Refer to Using I nternet
Services for more i nformati on on
i nterprocess communi cati on.
Refer to the sockaddr struct i n
the BSD Sockets I nterface
Programmer's Guide for
exampl es.
Socket address
vari abl es.
I nterprocess
communi cati on.
Address
Type
Chapter 6 99
system
name
Al so referred to as the system
host name and system node
name.
Thi s i s the name your HP-UX
system i s known by and i s
assi gned usi ng the HP-UX uname
command.
An exampl e of a system name i s:
host3. Assi gned automati cal l y by
the system.
/etc/rc.config.d
/netconf (as
HOSTNAME
vari abl e).
uucp faci l i ti es.
host name
node name
Al so known as the Internet host
name and NFS host name.
A symbol i c name associ ated wi th
an i nternet address by whi ch a
node can be uni quel y i denti ed.
An exampl e of a host name i s:
host3. Assi gned by usi ng the
hostname command.
/etc/hosts ;
/etc/hosts.equiv
(opti onal );
$HOME/.rhosts
(opti onal ) ;
$HOME/.netrc
(opti onal ) ;
/usr/adm/inetd.s
ec (opti onal ) .
Al l I nternet
Servi ces.
Address
Type
Internet Addresses
Chapter 6 100
Internet Addresses
I nternet addresses are used extensi vel y by LAN and WAN products as wel l as I nternet
Servi ces.
An i nternet address (often referred to as the I P address) consi sts of two parts:
Network address.
Host address.
The network address i denti es the network. The host address i denti es a node wi thi n the
network. A network address i s concatenated wi th a host address to form the i nternet address
and to uni quel y i denti fy a node wi thi n a network.
Internet Addresses
Chapter 6 101
Internet Address Formats
There are four i nternet address cl asses, each accommodati ng a di fferent number of network
and host addresses. The address cl asses are dened by the most si gni cant bi ts of the bi nary
form of the address as shown i n Fi gure 6-1. Thi s secti on di scusses three of the cl asses (Cl ass
A, Cl ass B, Cl ass C). The fourth cl ass (Cl ass D) i s di scussed i n the secti on I P Mul ti cast
Addresses.
Figure6-1 Internet Address Classes
The address cl asses can al so be broken down by address ranges. I nternet addresses are
typi cal l y represented by converti ng the bi ts to deci mal val ues an octet (8 bi ts) at a ti me, and
separati ng each octet's deci mal val ue by a peri od ( . ). Therefore, i nternet addresses are
typi cal l y of the fol l owi ng form:
n.n.n.n
31 23 0
31 30 0
31 29 0 7
15
0
1 0
1 1 0
Class A
Network Address Host Address
Class B
Class C
Internet Addresses
Chapter 6 102
where n i s a number from 0 to 255, i ncl usi ve. Thi s form i s referred to as deci mal dot notati on
or dot notati on.
Tabl e 6-4 l i sts the number of networks and nodes and the address ranges for Cl ass A, Cl ass B,
and Cl ass C networks. Cl ass D networks are descri bed l ater i n thi s chapter i n I P Mul ti cast
Addresses.
To determi ne a network address and host address from an i nternet address, you must
separate the network and host address el ds. For exampl e, the bi t representati on of i nternet
address 192.6.1.1 i s separated as fol l ows:
Figure6-2 Bit Representation of Internet Address
Assigning an Internet Address
Each node on the network has at l east one i nternet address. When assi gni ng i nternet
addresses, you must determi ne network addresses and host addresses as descri bed i n thi s
secti on.
Table6-4 Internet Address Classes
Class Networks
Nodes
per
Network
Address Range
A 127 16777215 1.0.0.1 126.255.255.254
B 16383 65535 128.1.0.1 191.255.255.254
C 2097151 255 192.0.1.1 223.255.255.254
Reserved - - 224.0.0.0 255.255.255.255
indicates
Class C
11000000.00000110.00000001.00000001
Network Address = 192.6.1 Host Address = 1
Internet Addresses
Chapter 6 103
NOTE When speci fyi ng i nternet addresses, do not use l eadi ng zeroes wi thi n address
el ds. For exampl e: 192.006.012.023 i s i ncorrect; 192.6.12.23 i s correct.
Assigning Network Addresses
To assi gn network addresses, fol l ow these rul es:
You must have a network address for each l ogi cal network.
I f your system i s attached to more than one physi cal network vi a a gateway, the network
addresses of these i nterfaces may not be the same. Refer to Tabl e 6-3 bel ow for a gateway
exampl e.
Al l nodes i n the same network, however, must have the same network address.
Do not assi gn the network addresses 0 or 255 (Cl ass A), 0.0 or 255.255 (Cl ass B), or 0.0.0
or 255.255.255 (Cl ass C) to any network. Those addresses are reserved.
Do not assi gn Cl ass A network address 127. Thi s address i s reserved for the l oopback
i nterface.
Figure6-3 Assigning Network Addresses
A
D
B
C
Gateway 192.6.12
192.6.20
Internet Addresses
Chapter 6 104
Assigning Host Addresses
Host addresses must be uni que wi thi n each network. You can assi gn host addresses accordi ng
to your own needs, but they must be wi thi n the range for the i nternet address cl ass that you
are usi ng.
NOTE Do not assi gn the host addresses 0.0.0 or 255.255.255 (Cl ass A), 0.0 or 255.255
(Cl ass B), or 0 or 255 (Cl ass C) to any nodes; these addresses are reserved.
IP Address for Loopback Interface (lo0)
The l oopback i nterface (lo0) i s automati cal l y congured when the system boots wi th the
TCP/I P software. The l oopback i nterface i s real l y a pseudo-devi ce, si nce there i s no
hardware card associ ated wi th i t. Thi s i nterface i s created sol el y to faci l i tate sendi ng I P
datagrams to the I P l oopback address 127.0.0.1.
The defaul t I P address and netmask of the l oopback i nterface are 127.0.0.1 and 255.0.0.0,
respecti vel y. By defaul t, the l oopback i nterface sets up routi ng entri es so that packets for any
127.*.*.* address wi l l l oop back to the l ocal host. Any attempt to change the address of the
i ni ti al l oopback i nterface (l o0:0) wi l l fai l .
Subnet Addresses
Chapter 6 105
Subnet Addresses
Subnetti ng i s an opti onal addressi ng scheme that al l ows you to parti ti on the host address
porti on of an i nternet address i nto di screte subnetworks. Thi s al l ows you to have mul ti pl e
physi cal networks wi thout requi ri ng you to obtai n mul ti pl e network addresses. The physi cal
networks are connected vi a gateways.
For exampl e, i f you have a l arge i nstal l ati on wi th many i nterconnected nodes, you coul d run
i nto hardware congurati on restri cti ons or performance degradati on i f you tri ed to pl ace al l
nodes on the same physi cal network. Wi th subnetti ng you can i nstal l several smal l er physi cal
networks but have them al l share the same network address. When messages wi th subnet
addresses are routed across the network, the i nternet address i s ANDed wi th the subnet
mask to determi ne the subnetwork address. (0 val ues i n the subnet mask convert
correspondi ng bi ts i n the I P address to 0.)
Subnet Addresses
Chapter 6 106
Fi gure 6-4 shows how a Cl ass C I nternet address and a subnet mask combi ne to form a
subnet address.
Figure6-4 Internet Address 192.6.12.33 ANDed with Subnet Mask
255.255.255.224
When the i nternet address i s ANDed wi th the subnet mask, the zero val ues i n the host
porti on of the subnet mask wi l l overwri te the correspondi ng bi ts of the host porti on of the
i nternet address and the resul tant subnet address wi l l be 192.6.12.32 as shown i n Fi gure 6-4
above. Non-zero val ues i n the subnet mask i ndi cate that the correspondi ng bi ts i n the
i nternet address do not change. The subnet mask may be xed-l ength or vari abl e-l ength.
IP Subnet Mask
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 1 1 1 1 1 0 0 0
1 1 0 0 0 0 0 0 1 1 0 0 0 0 0 1 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1
1 1 0 0 0 0 0 0 1 1 0 0 0 0 0 1 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0
255 . 255 . 255 . 224
Subnet
Mask
AND
0 values in mask (00000)
192 . 6 . 12 . 33
Internet
Address
Convert
to
Subnet
Address
overwrite value of 1 (00001)
in IP address
Bit values unchanged
Bit values
converted to
zero
resulting in new value
(00100000) in host address
(or 32 in dot notation)
192 . 6 . 12 . 32
Subnet Addresses
Chapter 6 107
The subnet el d (the porti on of an I P address that i denti es the subnet beyond the network
porti on of the address) can be al l 0s or al l 1s, as descri bed i n RFC 1878.To di sal l ow subnet
el ds wi th al l ones or al l zeroes (conform to RFC 1122 behavi or), set the ndd parameter
ip_check_subnet_addr to 1 i n the nddconf l e (/etc/rc.config.d/nddconf).
Selecting a Subnet Addressing Scheme
I n addi ti on to xed-l ength subnet addressi ng, HP-UX11i v2 systems support vari abl e-l ength
subnet addressi ng. The advantages of usi ng vari abl e-l ength subnet addressi ng over
xed-l ength subnet addressi ng i ncl ude the fol l owi ng:
Al l ows the l ocal admi ni strator to easi l y i ncrease/decrease the si ze of i ndi vi dual subnets
when vari abl e-l ength subnet addressi ng i s used i n conjuncti on wi th a non-conti guous
numberi ng system (and/or ranges of numbers for each subnet that are non-conti guous).
The mi rror-i mage counti ng feature, whi ch wi l l be di scussed i n the fol l owi ng secti on, al so
al l ows for more possi bi l i ti es i n the numbers that can be assi gned to i ndi vi dual subnets.
Reduces the amount of rework that network pl anners wi l l have to do on network desi gn
after the i ni ti al pl an has been compl eted.
Fi xed-l ength subnets were easy to i mpl ement, but growth restri cti ons often meant that i t
was necessary to i nvest more ti me whenever a change was made to a subnet after i t had
been ori gi nal l y desi gned.
Thi s new feature al so makes i t possi bl e to have more than one subnet mask on a network.
As descri bed previ ousl y, an i nternet address can be represented as four el ds separated by a
peri od, each of whi ch represents 8 bi ts of the overal l address.
The subnet address i s based on the host address porti on of the i nternet address. The host
address porti on subdi vi des i nto subnet number and host number el ds to accommodate a
gi ven number of subnetworks and a gi ven number of nodes per subnetwork. The si ze of the
subnet number el d i s determi ned by the subnet mask, whi ch i s expl ai ned l ater i n thi s
secti on. The subnet number el d must contai n a mi ni mum of one bi t.
I n the exampl e bel ow, the I P address, 192.6.12.33, has a subnet number of 1.
Subnet Addresses
Chapter 6 108
Refer to Fi gure 6-5 earl i er i n thi s chapter for an i l l ustrati on of how the subnet mask i s ANDed
wi th the I P address to form the subnet number.
Figure6-5 Subnet Address and Subnet Number of Class C Internet Address
192.6.12.33
The fol l owi ng rul es appl y when choosi ng a subnet addressi ng scheme and an i nternet
address:
Al l subnets on the same network must have the same network address.
I f your system i s attached to more than one physi cal network, the subnet addresses of the
i nterfaces on your system cannot be the same.
Do not assi gn a host address where al l the bi ts of the host number are 0 or al l the bi ts are
1.
You may choose a xed-l ength subnet addressi ng scheme i n whi ch one subnet mask wi l l be
used i n al l subnets i n your network. You may al so choose a vari abl e-l ength subnet addressi ng
scheme i n whi ch the subnet masks may be vari ed dependi ng on the si ze of the subnets you
want.
I f you wi sh to i mpl ement vari abl e-l ength subnetti ng, rst read the conceptual i nformati on,
Assi gni ng Vari abl e-Length Subnet Addresses l ater i n thi s chapter. Then refer to the speci c
task-ori ented i nstructi ons i n the Manual l y I nstal l i ng and Conguri ng HP-UX LAN chapter
earl i er i n thi s manual . For addi ti onal i nformati on, refer to the fol l owi ng onl i ne man pages:
ifconfig(1M), netstat(1), ppl.remotes(4), routing(7), and route(1M). Detai l ed
descri pti ons of xed-l ength and vari abl e-l ength subnet addressi ng fol l ow.
1 1 0 0 0 0 0 0 1 1 0 0 0 0 0 1 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1
192 . 6 . 12 . 33
Class C
IP Address:
network address = 192.6.12 subnet number = 1
host address = 33
subnet address = 192.6.12.32
Subnet Addresses
Chapter 6 109
Fixed-Length Subnet Addressing
Thi s secti on shows you how to appl y a xed-l ength subnet addressi ng scheme on a cl ass C
network. The same steps may be appl i ed on a Cl ass A or Cl ass B network.
Assigning a Fixed-Length Subnet Mask
Subnet addressi ng i s i mpl emented by speci fyi ng a 32-bi t subnet mask i n the ifconfig
command or the netconf l e when a LAN i nterface card i s assi gned an i nternet address. Al l
nodes on a subnet must have the same subnet mask. Under the xed-l ength subnet address
scheme, al l subnets on a network, must have the same subnet mask.
The subnet mask i s ANDed wi th the address attached to a message comi ng across the
network to determi ne i f that message shoul d be routed to a node on the l ocal network or
i gnored.
Before a subnet mask i s appl i ed, the rst three octets of a Cl ass C I P address represent the
network address. I f the subnet mask 255.255.255.224 i s appl i ed, the rst three octets of the
address and the rst three bi ts of the l ast octet i ndi cate the subnet address whi l e the l ast ve
bi ts of the l ast octet i ndi cate the host address. Thi s i s shown i n the fol l owi ng gure.
Figure6-6 Fixed-Length Subnet Mask Example
Wi th thi s subnet mask, up to 8 subnets wi th 30 nodes per subnet are possi bl e. Tabl e 6-5 bel ow
l i sts the val i d i nternet address ranges for nodes i n a network wi th the subnet mask
255.255.255.224.
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 1 1 1 1 1 0 0 0
Class C Subnet Mask:
255 . 255 . 255 . 224
network address subnet portion of
host address
host portion of
host address
Subnet Addresses
Chapter 6 110
Table6-5 Fixed-Length Subnet Addressing (Subnet Mask
255.255.255.224)
Subnet
Address
(dot notation)
Internet Address Range
(dot notation)
Subnet
Broadcast
Address
n.n.n.0 n.n.n.1 - n.n.n.30 n.n.n.31
n.n.n.32 n.n.n.33 - n.n.n.62 n.n.n.63
n.n.n.64 n.n.n.65 - n.n.n.94 n.n.n.95
n.n.n.96 n.n.n.97 - n.n.n.126 n.n.n.127
n.n.n.128 n.n.n.129 - n.n.n.158 n.n.n.159
n.n.n.160 n.n.n.161 - n.n.n.190 n.n.n.191
n.n.n.192 n.n.n.193 - n.n.n.222 n.n.n.223
n.n.n.224 n.n.n.225 - n.n.n.254 n.n.n.255
Subnet Addresses
Chapter 6 111
Example of Subnets with a Fixed-Length Subnet Mask
The fol l owi ng exampl e shows four subnetworks wi thi n the 192.6.12 network al ong wi th the
netconf entri es necessary to congure these subnetworks. The compl ete network map i s
shown i n Fi gure 6-8.
Figure6-7 Network Map for Subnetting
Summary network i nformati on:
Company division network = 192.6.12
Subnet mask: 255.255.255.224
Facility LAN subnet number = 1
Host address range: 22 to 62
Host A internet address: 192.6.12.33 for network interface lan0
Host B internet address: 192.6.12.36 for network interface lan0
Host C internet address: 192.6.12.34 for network interface lan0
Host D internet address: 192.6.12.35 for network interface lan0
Marketing Department subnet number = 2
R & D Department subnet number = 3
Host A internet address: 192.6.12.97 for network interface lan1:0
Host B internet address: 192.6.12.98 for network interface lan1:1
A
C
B D
Marketing Dept.
(Subnet 2)
lan1
Corporate Offices
lan0
Facility LAN
(Subnet 1)
lan0
lan1
Manufacturing Dept.
(Subnet 4)
R & D Dept.
(Subnet 3)
lan 1:0
192.6.12.97
lan 1:1
192.6.12.98
lan0:0
192.6.12.34
lan0:1
192.6.12.37
lan0
192.6.12.35
(Gateway)
lan1
192.6.20.1
(network 192.6.20)
192.6.12.65
192.6.12.33
192.6.12.36
192.6.12.130
Subnet Addresses
Chapter 6 112
Manufacturing Department subnet number = 4
Conguring Hosts on Fixed-Length Subnets Using the netconf le
There are two ways to congure a subnet mask:
Use SAM to congure the subnet mask.
Use the ifconfig command. These changes wi l l di sappear, however, when the system
reboots.
To set a subnet mask, you may ei ther i ncl ude i t i n the SUBNET_MASK vari abl e i n the
netconf l e or the ifconfig command. The netconf l e contai ns i nformati on you entered i n
SAM and thi s i nformati on i s used to start networki ng when the system reboots. I f you
congure your network i nterfaces usi ng SAM, SAM wi l l enter the proper i nformati on i n the
netconf l e for you. The exampl es bel ow are netconf exampl es for the hosts i n the exampl e
above after you have congured them i n SAM:
Host A:
IP_ADDRESS[0]=192.6.12.33
SUBNET_MASK[0]=255.255.255.224
IP_ADDRESS[1]=192.6.12.65
SUBNET_MASK[1]=255.255.255.224
Host B:
IP_ADDRESS[0]=192.6.12.36
SUBNET_MASK[0]=255.255.255.224
IP_ADDRESS[1]=192.6.12.130
SUBNET_MASK[1]=255.255.255.224
Host C:
IP_ADDRESS[0]=192.6.12.34
SUBNET_MASK[0]=255.255.255.224
IP_ADDRESS[1]=192.6.12.37
SUBNET_MASK[1]=255.255.255.224
IP_ADDRESS[2]=192.6.12.97
SUBNET_MASK[2]=255.255.255.224
Subnet Addresses
Chapter 6 113
IP_ADDRESS[3]=192.6.12.98
SUBNET_MASK[3]=255.255.255.224
Host D:
IP_ADDRESS[0]=192.6.12.35
SUBNET_MASK[0]=255.255.255.224
IP_ADDRESS[1]=192.6.20.1
SUBNET_MASK[1]= 255.255.255.0
I n addi ti on, every other host on each subnetwork woul d requi re the subnet mask
255.255.255.224 i n thei r netconf l e entri es.
Subnet Addresses
Chapter 6 114
Example of Network Map with Fixed-Length Subnets
Thi s sampl e network combi nes networks, subnets wi th a xed-l ength mask, and cl usters
previ ousl y descri bed and i l l ustrated i n thi s chapter al ong wi th a sampl e worksheet that
provi des congurati on i nformati on necessary to attach these systems to the networks.
Figure6-8 Network Map I
A1 A2
A
D B
B2 B1
C
C2 C1
Div2
E
Div3
Marketing Dept.
(Subnet 2)
R & D Dept.
Corporate Offices
Gateway
Modem
Modem
RS232
RS232
192.6.12.67 192.6.12.66
lan1
192.6.12.65
lan0
192.6.12.33
Facility LAN
(Subnet 1)
lan0
192.6.12.36
lan1
192.6.12.130
192.6.12.131
192.6.12.132
192.1.1.2
(Subnet 4)
Manufacturing Dept.
SLIP
192.1.1.1
Remote access to
network using
Serial Line IP Protocols
192.6.12.99 192.6.12.98
lan1:0
192.6.12.97
lan1:1
192.6.12.98
lan0:0
192.6.12.34
lan0:1
192.6.12.37
lan0
192.6.12.35
lan1
192.6.20.1
(network 192.6.20)
lan1
192.6.20.3
lan0
192.6.13.130
lan1
192.6.20.2
lan0
192.6.14.129
Subnet Addresses
Chapter 6 115
Subnet mask = 255.255.255.224
Table6-6 Network Map I Worksheet
Host
Inter-
face
Alias
Internet
Address
Station
Address
Cnode
Type
A mkt_32
mkt_64
192.6.12.33
192.6.12.65
08000909030D
080009080102
Server
A1 mkt_a1 192.6.12.67 080009005201 Cl i ent 1
A2 mkt_a2 192.6.12.66 080009003001 Cl i ent 2
B mfg_32
mfg_128
192.6.12.36
192.6.12.130
080009005201
080009000C24
N/A
B1 mfg__b1
b1_sl i p
192.6.12.131
192.1.1.2
080009001001
N/A
N/A
B2 mfg_b2 192.6.12.132 080009002125 N/A
C rd_32
rd_36
rd_96
rd_99
192.6.12.34
192.6.12.37
192.6.12.97
192.6.12.98
080009267C14
080009267C14
080009260C85
080009260C85
Server
C1 rd_c1 192.6.12.99 08000900079C Cl i ent 1
C2 rd_c2 192.6.12.98 08000900601A Cl i ent 2
D di v1_32
di v_gw
192.6.12.35
192.6.20.1
080009000740
080009000B30
N/A
Di v2 di v2_128
di v2_gw
192.6.14.129
192.6.20.2
080009006041
080009007104
N/A
Di v3 di v3_128
di v3_gw
192.6.13.130
192.6.20.3
080009004020
080009010312
N/A
E
(SLI P)
e_sl i p 192.1.1.1 N/A N/A
Conguring Gateways on Fixed-Length Subnets
Chapter 6 116
Besi des usi ng the appropri ate subnet masks, each gateway needs to be congured so that i t
can properl y route messages among the several subnetworks. Fol l owi ng are descri pti ons of
two types of routi ng: expl i ci t routi ng and dynami c routi ng. When usi ng expl i ci t routi ng, you
must speci fy the I P address of each gateway to whi ch you are di rectl y connected. When usi ng
dynami c routi ng, you need to speci fy onl y the I P address of one gateway, and the system
l earns the I P address of other gateways from the speci ed gateway.
Explicit Routing
There are many ways to set up routi ng. For exampl e, you mi ght use the route command or you
may add the fol l owi ng entri es to the netconf l e on Host A i n Fi gure 6-8:
ROUTE_DESTINATION[0]=net 192.6.12.128
ROUTE_COUNT[0]=1
ROUTE_COUNT[1]=1
ROUTE_DESTINATION[2]=net default
ROUTE_COUNT[2]=1
The 1 i n each ROUTE_COUNT entry speci es an i ndi rect route. For exampl e, messages for
the system on the 192.6.12.128 subnetwork wi l l rst be sent to Host B (192.6.12.36), and from
there they wi l l be forwarded to the desti nati on system.
Dynamic Routing
Al ternati vel y, and perhaps the easi est way to manage growth on the 192.6.12 network, you
mi ght add the fol l owi ng entri es to each netconf l e.
Hosts A, B and C:
ROUTE_COUNT[0]=1
Host D (Site gateway):
ROUTE_COUNT[0]=1
Chapter 6 117
ROUTE_COUNT[1]=1
ROUTE_COUNT[2]=1
ROUTE_COUNT[3]=0
I f you add a new subnetwork to the Faci l i ty LAN at a l ater ti me, you wi l l need to add onl y an
appropri ate routi ng entry on Host D. I t wi l l not be necessary to congure the other subnet
gateways A, B, and C.
Wi th thi s congurati on, each subnet gateway (Hosts A, B, and C) wi l l i ni ti al l y route messages
for a system outsi de i ts subnet to Host D. The subnet gateway, however, wi l l l earn of the more
di rect routes automati cal l y when Host D redi rects the messages to one of the other subnet
gateways. Subsequent messages for the desti nati on system wi l l be routed di rectl y to the
appropri ate subnet gateway.
For exampl e, referri ng to Fi gure 6-8, suppose messages are sent from system A1 (192.6.12.67)
to system B1 (192.6.12.131). The rst message wi l l actual l y be routed to Host D (through Host
A). Host D then wi l l redi rect the message through Host B. At the same ti me, Host D wi l l
noti fy Host A that Host B i s a more di rect route for messages to system B1. Subsequent
messages to system B1 wi l l be routed di rectl y from Host A to Host B.
Redi rected routes are cal l ed dynami c routes. You can see these dynami c routes by executi ng
the command netstat -r on Host A. Dynami c routes are i ndi cated i n the di spl ay by a D ag.
Proxy ARP Server
The defaul t di rect route entry on Host D assumes that there i s a proxy ARP server on the
192.6.20 network. I f one does not exi st, addi ti onal i ndi rect route entri es can be congured for
each gateway that i s di rectl y connected to the 192.6.20 network.
For exampl e, referri ng to Fi gure 6-8, you mi ght add the fol l owi ng i ndi rect routes on Host D to
send messages to Di vi si on 2 and Di vi si on 3.
ROUTE_DESTINATION[4]=net 192.6.14
ROUTE_COUNT[4]=1
ROUTE_COUNT[5]=1
Variable-Length Subnet Addressing
Chapter 6 118
For the most efci ent use of address space and maxi mum exi bi l i ty i n i ncreasi ng/decreasi ng
the si ze of your subnets, Hewl ett-Packard recommends vari abl e-l ength subnet addressi ng. To
maxi mi ze the possi bi l i ti es offered wi th thi s new approach, you shoul d uti l i ze mi rror i mage
counti ng, as descri bed i n thi s secti on, to sel ect subnet numbers.
I n the past, a network admi ni strator typi cal l y assi gned val ues to the subnet number and host
address el ds i n numeri cal order. For exampl e, wi thi n a gi ven subnet, hosts were numbers 1,
2, 3, etc. and wi thi n a gi ven network, the subnets were numbered 1, 2, 3, etc. The resul t was
that some bi ts on the ri ght si de of the subnet el d and host el d were ones and zeros and
some bi ts on the l eft si de of the subnet and host el ds were al l zeros for al l subnets and
hosts. As shown bel ow, the al l zeros bi ts represented room for growth, and the ones and
zeros bi ts represented bi ts al ready consumed by growth.
Figure6-9 Traditional Subnet and Host Field Allocation
0s 1s & 0s
0s 1s & 0s
subnet field host field
subnets can
grow here
hosts can
grow here
Chapter 6 119
I n the next exampl e. the enti re host el d has been al l ocated. As a resul t, onl y the subnet el d
can grow.
Figure6-10 Entire Host Field Allocated
To al l evi ate thi s restri cti ve si tuati on, when you use the vari abl e-l ength subnetti ng approach,
you can, al ternati vel y, assi gn subnet numbers from the l eft of the subnet el d and work ri ght.
Thi s i s i mpl emented usi ng mi rror-i mage counti ng. I n the mi rror i mage approach, the bi ts for
subnet numbers are assi gned l eft to ri ght i nstead of ri ght to l eft (normal si tuati on). Thi s
woul d resul t i n the fol l owi ng format:
Table6-7 Mirror Image Counting
Traditional
Approach
Mirror
Image
Approach
01 10
10 01
011 110
100 001
101 101
0s 1s & 0s 1s & 0s
subnets can
grow here
Chapter 6 120
Thi s wi l l al l ow for more growth bi ts between the subnet el d and the host el ds as shown
bel ow.
Figure6-11 Mirror Image Subnet and Host Field Allocation
I n thi s case, both the host el d and subnet el d have consi derabl y more growi ng space than
before, al though the combi ned growi ng space i s the same. As i t i s di fcul t to predi ct how many
hosts mi ght end up i n a subnet, or how many subnets there mi ght eventual l y be, thi s
arrangement al l ows for maxi mum exi bi l i ty i n growth.
Assigning Variable-Length Subnet Masks
I n Fi gure 6-11, the boundary between the host and subnet el ds i s shown i n the mi ddl e of the
growth area. The boundary, however, coul d exi st anywhere wi thi n the growth area. The
subnet mask determi nes where the boundary i s l ocated. Ones i n the subnet mask i ndi cate
subnet bi ts, and zeros i ndi cate host bi ts. To mi ni mi ze the amount of rework after the i ni ti al
pl anni ng of your network, you shoul d choose a subnet mask for a gi ven subnet based on the
projected growth of that subnet. As shown i n Fi gure 6-12, the subnet i s projected to have a
maxi mum si ze of 14 hosts. Therefore, the subnet mask shoul d be 255.255.255.240. There are
two remai ni ng growth bi ts for thi s subnet. I f the subnet grows beyond 14 hosts, you may
choose to change one of the two remai ni ng growth bi ts to a host bi t. The new subnet mask wi l l
be 255.255.255.224.
0s 1s & 0s 1s & 0s
Both hosts and subnets
can grow here.
Chapter 6 121
Vari abl e-l ength subnet masks are assi gned usi ng the netmask parameter of the ifconfig
command, SUBNET_MASK i n netconf wi th a 32-bi t subnet mask i ndi cated i n dot notati on,
or SAM. I n the exampl e bel ow wi th a Cl ass C I P address, the host porti on has three types of
assi gned bi ts: subnet number bi ts, growth bi ts, and host bi ts, wi th a chosen subnet mask that
al l ows for growth i n both the host el d and subnet el d wi thout a mask change.
Figure6-12 Example of Variable-Length Subnet Mask
The exampl e bel ow shows how the bi ts mi ght l ook i n the host address porti on of a Cl ass C
address i n a network wi th four subnets usi ng vari abl e-l ength subnetti ng. I n thi s exampl e g
stands for growth bi ts and h stands for host bi ts. The 0s and 1s i n the host address are
assi gned subnet numbers.
Table6-8 Subnets with Variable-Length Subnet Mask
Subnet
Host Address
(Bits)
Subnet Mask
(Bits)
A 10gg gghh 1111 1100
B 01gg ghhh 1111 1000
C 110g ghhh 1111 1000
D 001g ghhh 1111 1000
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 0 0 0
subnet portion of host address
growth portion of host address
host portion of host address
Predetermined
boundary
Class C Subnet Mask:
network address
255 . 255 . 255 . 240
Chapter 6 122
I f hosts are added to subnet B above, so that al l of i ts remai ni ng g bi ts become h bi ts, the
mask i n subnet B al so must change. Tabl e 6-9 shows the resul ts of these changes. Al so, two
addi ti onal subnets have been added, subnet E and subnet F.
Noti ce that these addi ti ons caused A to change i ts l eftmost g-bi t i nto a subnet-bi t (s bi t).
Wi th the addi ti on of subnet address 101 for subnet E, the ol d subnet address 10 of subnet A
must be changed to 100 so that the proper number of bi ts are used to make the subnet
numbers uni que.
Tabl e 6-10 shows the resul ts of removi ng subnet E.
Noti ce that wi th thi s change, subnet A gai ns back one growth bi t (g bi t) as i ts ol d subnet
address of 10 i s now uni que agai n.
Table6-9 Subnets with Subnet Mask (B) Modied
Subnet
Host Address
(Bits)
Subnet Mask
(Bits)
A 100g gghh 1111 1000
B 01hh hhhh 1100 0000
C 110g ghhh 1111 1000
D 001g ghhh 1111 1000
E 101g ghhh 1111 1000
F 1110 ghhh 1111 1000
Table6-10 Subnets with Subnet E Removed
Subnet
Host Address
(Bits)
Subnet Mask
(Bits)
A 10gg gghh 1111 1100
B 01hh hhhh 1100 0000
C 110g ghhh 1111 1000
D 001g ghhh 1111 1000
F 1110 ghhh 1111 1000
Chapter 6 123
Example of Subnets with Variable-Length Subnet Masks
The fol l owi ng exampl e shows four subnetworks wi thi n the 192.6.12 network al ong wi th the
netconf entri es necessary to congure these subnetworks wi th vari abl e-l ength subnet masks.
Note that there are four di fferent subnet masks used i n thi s network. Al so note that the
subnet numbers i n the network map correspond to the mi rror i mage subnet numbers l i sted i n
Tabl e 6-7.
Figure6-13 Network Map with Variable-Length Subnets
The subnet numbers shown bel ow correspond to the subnets show i n the network map i n
Fi gure 6-13.
I n thi s exampl e of mi rror i mage counti ng, the rst subnet has 6 hosts (wi th space al l ocated for
a maxi mum of 6 hosts), the second subnet has 60 hosts (wi th space al l ocated for a maxi mum
of 62 hosts), the thi rd subnet has 30 hosts (wi th space al l ocated for a maxi mum of 30 hosts),
and the fourth subnet has 14 hosts (wi th space al l ocated for a maxi mum of 16 hosts). Noti ce
how the range of numbers (129-135, 65-127,193-223, and 33-47) i s spread out to al l ow room
for addi ti onal growth i n each case.
A
C
192.6.12.64,
255.255.255.192
B
192.6.12.192,
255.255.255.224
D
Corporate Offices
Marketing Dept.
(Subnet 1) R & D Dept.
(Subnet 6)
Facility LAN
(Subnet 16)
Manufacturing Dept.
(Subnet 2)
lan1
192.6.12.64,
255.255.255.192
lan0
192.6.12.129,
255.255.255.248
lan1
192.6.12.193,
255.255.255.224
lan0
192.6.12.130,
255.255.255.248
192.6.12.132
255.255.255.248
(Gateway)
lan1
192.6.20.1
(network 192.6.20)
lan0
192.6.12.131,
255.255.255.248
lan1
192.6.12.33,
255.255.255.240
192.6.12.128,
255.255.255.248
192.6.12.32,
255.255.255.240
E
Networking LAN
(Subnet 17)
lan2
192.6.12.1
192.6.12.2.
lan1
255.255.255.128
Chapter 6 124
NOTE I n a Cl ass C network, no two subnets can have more than 125 hosts.
Summary network i nformati on:
Company division network = 192.6.12
Facility LAN subnet
Subnet mask: 255.255.255.248
Subnet number: 16
Mirror image subnet number: 1
Subnet address: 192.6.12.128
Marketing Department Subnet
Subnet mask: 255.255.255.192
Subnet number: 1
Table6-11 Variable-Length Subnet Addressing in a Class C Network
Subnet
Mask
255.255.255
Subnet
Number
Mirror
Image
Subnet
Number
Subnet
Address
Internet Address
Range
248 16
(10000)
1
(00001)
n.n.n.128 n.n.n.129 - n.n.n.134
192 1
(01)
2
(10)
n.n.n.64 n.n.n.65-n.n.n.126
128 1
(01)
2
(10)
n.n.n.0 n.n.n.1-n.n.n.126
n.n.n.129-n.n.n.254
224 6
(110)
3
(011)
n.n.n.192 n.n.n.193-n.n.n.222
240 2
(0010)
4
(0100)
n.n.n.32 n.n.n.33-n.n.n.46
Chapter 6 125
Networking LAN subnet
Subnet mask: 255.255.255.128
Subnet number: 17
Host address range: 1 to 126 and 129 to 254
R & D Department Subnet
Subnet mask: 255.255.255.224
Subnet number: 6
Manufacturing Department Subnet
Subnet mask: 255.255.255.240
Subnet number: 2
Chapter 6 126
Example of Network Map with Variable-Length Subnets
Thi s sampl e network combi nes networks, subnets wi th vari abl e-l ength subnet masks, and
cl usters previ ousl y descri bed and i l l ustrated i n thi s chapter. Note that the subnet masks for
each I P address are shown on the accompanyi ng worksheet.
Chapter 6 127
Figure6-14 Network Map II
Table6-12 Network Map II Worksheet
Host
Interface
Alias
Internet
Address
Subnet Mask
Cnode
Type
A mkt_32
mkt_64
192.6.12.129
192.6.12.65
255.255.255.248
255.255.255.192
Server
A1 mkt_a1 192.6.12.67 255.255.255.192 Cl i ent 1
A1 A2
A
D B
B2 B1
C
C2 C1
Div2
E
Div3
lan1
192.6.12.65
255.255.255.192
Marketing Dept.
(Subnet 1)
R & D Dept.
(Subnet 6)
192.6.12.67
255.255.255.192
192.6.12.66
255.255.255.192
Corporate Offices
Manufacturing Dept.
(Subnet 2)
Facility LAN
(Subnet 16)
lan0
192.6.12.129,
255.255.255.248
lan0
192.6.12.131
255.255.255.248
lan1
192.6.12.33
255.255.255.240
192.6.12.34
255.255.255.240
RS232
Modem
Modem
RS232
192.1.1.2
192.1.1.1
Remote access to network using
Serial Line IP Protocols
192.6.12.35
255.255.255.240
192.6.12.195
255.255.255.224
192.6.12.194
255.255.255.224
lan1 192.6.12.193
255.255.255.224
lan0
192.6.12.130
255.255.255.248
lan0 192.6.12.132
255.255.255.248
lan1
192.6.20.1
255.255.255.0
(network 192.6.20)
lan1 lan0
192.6.20.3
255.255.255.0
192.6.13.130
255.255.255.0
lan1
lan0
192.6.20.2
255.255.255.0
192.6.14.129
255.255.255.0
Chapter 6 128
A2 mkt_a2 192.6.12.66 255.255.255.192 Cl i ent 2
B mfg_32
mfg_128
192.6.12.131
192.6.12.33
255.255.255.248
255.255.255.240
N/A
B1 mfg__b1
b1_shi p
192.6.12.34
192.1.1.2
255.255.255.240
N/A
N/A
B2 mfg_b2 192.6.12.35 255.255.255.240 N/A
C rd_32
rd_96
192.6.12.130
192.6.12.193
255.255.255.248
255.255.255.224
Server
C1 rd_c1 192.6.12.195 255.255.255.224 Cl i ent 1
C2 rd_c2 192.6.12.194 255.255.255.224 Cl i ent 2
D di v1_32
di v_gw
192.6.12.132
192.6.20.1
255.255.255.248
255.255.255.0
N/A
Di v2 di v2_128
di v2_gw
192.6.14.129
192.6.20.2
255.255.255.0
255.255.255.0
N/A
Di v3 di v3_128
di v3_gw
192.6.13.130
192.6.20.3
255.255.255.0
255.255.255.0
N/A
E
(SLI
P)
e_sl i p 192.1.1.1 N/A N/A
Table6-12 Network Map II Worksheet (Continued)
Host
Interface
Alias
Internet
Address
Subnet Mask
Cnode
Type
Conguring Gateways on Variable-Length Subnets
Chapter 6 129
Besi des usi ng the appropri ate subnet masks, each gateway needs to be congured so that i t
can properl y route messages among the several subnet works. Fol l owi ng are descri pti ons of
two types of routi ng: expl i ci t routi ng and dynami c routi ng. When usi ng expl i ci t routi ng, you
must speci fy the I P address of each gateway to whi ch you are di rectl y connected. When usi ng
dynami c routi ng, you need to speci fy onl y the I P address of one gateway, and the system
l earns the I P address of other gateways from the speci ed gateway.
Explicit Routing
There are many ways to set up routi ng. For exampl e, you mi ght add the fol l owi ng entri es to
the netconf l e on Host A i n Fi gure 6-14:
ROUTE_MASK[0]=255.255.255.224
ROUTE_COUNT[0]=1
ROUTE_MASK[1]=255.255.255.240
ROUTE_COUNT[1]=1
ROUTE_DESTINATION[2]=net default
ROUTE_MASK[2]=
ROUTE_COUNT[2]=1
The 1 i n each ROUTE_COUNT entry speci es an i ndi rect route. For exampl e, messages for
the system on the 192.6.12.32 subnetwork wi l l rst be sent to Host B (192.6.12.131), and from
there they wi l l be forwarded to the desti nati on system.
Dynamic Routing
Al ternati vel y, and perhaps the easi est way to manage growth on the 192.6.12 network, you
mi ght add the fol l owi ng entri es to each netconf l e.
Hosts A, B and C:
ROUTE_COUNT[0]=1
Host D (Site gateway):
Chapter 6 130
ROUTE_MASK[0]=255.255.255.192
ROUTE_COUNT[0]=1
ROUTE_MASK[1]=255.255.255.224
ROUTE_COUNT[1]=1
ROUTE_MASK[2]=255.255.255.240
ROUTE_COUNT[2]=1
ROUTE_COUNT[3]=0
I f you add a new subnetwork to the Faci l i ty LAN at a l ater ti me, you wi l l need to add onl y an
appropri ate routi ng entry on Host D. I t wi l l not be necessary to congure the other subnet
gateways A, B, and C.
Wi th thi s congurati on, each subnet gateway (Hosts A, B, and C) wi l l i ni ti al l y route messages
for a system outsi de i ts subnet to Host D. The subnet gateway, however, wi l l l earn of the more
di rect routes automati cal l y when Host D redi rects the messages to one of the other subnet
gateways. Subsequent messages for the desti nati on system wi l l be routed di rectl y to the
appropri ate subnet gateway.
For exampl e, referri ng to Fi gure 6-14, suppose messages are sent from system A1
(192.6.12.67) to system B1 (192.6.12.34). The rst message wi l l actual l y be routed to Host D
(through Host A). Host D then wi l l redi rect the message through Host B. At the same ti me,
Host D wi l l noti fy Host A that Host B i s a more di rect route for messages to system B1.
Subsequent messages to system B1 wi l l be routed di rectl y from Host A to Host B.
Redi rected routes are cal l ed dynami c routes. You can see these dynami c routes by executi ng
the command netstat -rv on Host A. Dynami c routes are i ndi cated i n the di spl ay by a D
ag.
Proxy ARP Server
The defaul t di rect route entry on Host D assumes that there i s a proxy ARP server on the
192.6.20 network. I f there i s none, addi ti onal i ndi rect route entri es can be congured for each
gateway that i s di rectl y connected to the 192.6.20 network.
For exampl e, referri ng to Fi gure 6-14, you mi ght add the fol l owi ng i ndi rect routes to send
messages to Di vi si on 2 and Di vi si on 3.
Chapter 6 131
ROUTE_MASK[4]=255.255.255.0
ROUTE_COUNT[4]=1
ROUTE_MASK[5]=255.255.255.0
ROUTE_COUNT[5]=1
Conguring Gateways on Supernets
Chapter 6 132
Conguring Gateways on Supernets
I f al l the hosts and gateways i n your networks support vari abl e-l ength subnet masks, then
the gateway congurati on of the supernet wi l l be the same as i n gateway congurati on for
vari abl e-l ength subnets.
I n Fi gure 6-18, i f you use expl i ci t routi ng, you may congure the fol l owi ng supernet route on
Host A to enabl e Host A to communi cate wi th any host on supernet 192.6.12
ROUTE_MASK[0]=255.255.254.0
ROUTE_COUNT[0]=1
I f you use dynami c routi ng, then the defaul t gateway, Gd, on network 192.6.14 must have the
above supernet route congured.
I f some of the hosts and gateways i n your networks do not support vari abl e-l ength subnet
masks, then you must congure a separate network route for each of the networks i n the
supernet.
I f you use expl i ci t routi ng and Host A does not support supernetti ng, then you must congure
the fol l owi ng two net routes on Host A.
ROUTE_MASK[0]=255.255.255.0
ROUTE_COUNT[0]=1
ROUTE_MASK[1]=255.255.255.0
ROUTE_COUNT[1]=1
I f you use dynami c routi ng, then the defaul t gateway, Gd, on network 192.6.14 must have the
above net routes congured.
IP Multicast Addresses
Chapter 6 133
I P mul ti casti ng provi des a mechani sm for sendi ng a si ngl e datagram to a group of systems.
General l y, onl y systems that have joi ned the mul ti cast group process the datagrams.
Mul ti cast datagrams are transmi tted and del i vered wi th the same best effort rel i abi l i ty as
regul ar uni cast I P datagrams. The datagrams are not guaranteed to arri ve i ntact at al l
members of the desti nati on group or i n the same order as the datagrams were sent.
Membershi p i n a mul ti cast group i s dynami c. Systems can joi n or l eave groups at any ti me
based upon the appl i cati ons behavi or. A system remai ns a member of a mul ti cast group unti l
the l ast socket that joi ned the group i s cl osed or drops membershi p i n the group. A system can
be a member of more than one group at a ti me. A system that has mul ti pl e i nterfaces mi ght be
a member of the same group on each i nterface.
At the I P l ayer, a mul ti cast address i s a Cl ass D I nternet address wi th the fol l owi ng format:
Figure6-15 Multicast Address Format
User I P mul ti cast addresses can be i n the range 224.0.1.0 through 239.255.255.255. The
addresses 224.0.0.0 through 224.0.0.255 are reserved. The addresses of other wel l -known
permanent mul ti cast groups are publ i shed i n the Assigned Numbers RFC (RFC-1060,
March 1990).
Ethernet Multicast Addresses
The Ethernet data-l i nk address, al so cal l ed the l i nk l evel or stati on address, i s deri ved from
the I P mul ti cast address. The l ower 23 bi ts of the I P mul ti cast address are pl aced i nto the
l ower 23 bi ts of the Ethernet mul ti cast address 01-00-5E-00-00-00 (hex). Ethernet mul ti cast
addresses can be i n the range 01-00-5E-00-00-01 through 01-00-5E-7F-FF-FF.
1 1 1 0
0 31 30 29 28 27
MULTICAST GROUP ADDRESS
Chapter 6 134
NOTE Several I P mul ti cast addresses may share the same Ethernet mul ti cast address
because the I P mul ti cast address has 28 si gni cant bi ts.
Multicast Routing
Mul ti cast datagrams are sent through the i nterface associ ated wi th the defaul t route. I f that
i nterface does not support mul ti cast, attempts to send mul ti cast datagrams wi l l resul t i n the
ENETUNREACH error.
A defaul t mul ti cast route can be congured by speci fyi ng a network route for 224.0.0.0. The
exampl e bel ow provi des both the command l i ne and netconf l e entri es.
route add 224.0.0.0 192.1.2.3 0 #192.1.2.3 is a local interface
ROUTE_DESTINATION[1]=224.0.0.0
ROUTE_COUNT[1]=0
Addi ti onal l y, routes for speci c mul ti cast addresses can be congured just l i ke any other host
route. The exampl e bel ow provi des both the command l i ne and netconf l e entri es.
route add 224.1.2.3 192.5.6.7 0 #192.5.6.7 is a local interface
ROUTE_DESTINATION[2]=224.1.2.3
ROUTE_COUNT[2]=0
Virtual IP (VIP) Addresses
Chapter 6 135
Systems can have Vi rtual I P (VI P) addresses that are not permanentl y assi gned to a si ngl e,
speci c physi cal i nterface. The system wi l l accept to a packet addressed to i ts VI P (or VI Ps)
regardl ess of the physi cal i nterface on whi ch i t was recei ved. Thi s al l ows a system to have a
"system I P" address that i s avai l abl e as l ong as one i nterface stays usabl e.
To congure VI Ps, associ ate the VI P address wi th a secondary l oopback i nterface (l o0:n,
where n i s 1 or greater, such as l o0:1). The VI P address does not have to be i n the same subnet
(or network) of the addresses used for the physi cal i nterfaces.
I n the exampl e bel ow, the system has two LAN i nterfaces. One i s attached to the 15.n.n.n
network and has the address 15.1.1.1. The second LAN i s attached to the 16.n.n.n network
and has the address 16.1.1.1. The VI P address i s 17.1.1.1.
Figure6-16
Note that the i nfrastructure of the network (routers, swi tches) must al l ow I P packets wi th the
address 17.1.1.1 to be properl y routed to thi s system's i nterfaces on the 15.n.n.n and 16.n.n.n
networks for thi s congurati on to be useful .
/etc/rc.cong.d/netconf l e statements for the above VI P:
INTERFACE_NAME[2]=lo0:1
IP_ADDRESS[2]=15.1.1.1
:
:
15.1.1.1
lan0:0
VIP
(no physical interface)
15.n.n.n net
16.n.n.n net
16.1.1.1 17.1.1.1
lan1:0 1o0:1
Chapter 6 136
i fcong command for the above VI P:
ifconfig lo0:1 inet 15.1.1.1
Note that you cannot assi gn VI Ps to the pri mary l oopback i nterface, l o0:0, or l o0.
CIDR - Classless Inter-Domain Routing
Chapter 6 137
As the I nternet has evol ved and grown i n recent years, i t has become cl ear that i t i s faci ng
several seri ous probl ems. These i ncl ude:
Exhausti on of the Cl ass B network address space. One fundamental cause of the probl em
i s the l ack of a network cl ass of a si ze that i s appropri ate for a mi d-si zed organi zati on.
Cl ass-C, wi th a maxi mum of 254 host addresses, i s too smal l , whi l e Cl ass-B, whi ch al l ows
up to 65534 addresses, i s too l arge to be densel y popul ated. The resul t i s i nefci ent
uti l i zati on of Cl ass-B network numbers.
Routi ng I nformati on overl oad. The si ze and rate of growth of the routi ng tabl es i n
I nternet routers i s beyond the abi l i ty of current software (and peopl e) to effecti vel y
manage.
Cl assl ess I nter-Domai n Routi ng (CI DR) attempts to deal wi th these probl ems by deni ng a
mechani sm to sl ow the growth of routi ng tabl es and reduce the need to al l ocate new I P
network numbers.
Chapter 6 138
The basi c i dea of the CI DR pl an i s to al l ocate one or more bl ocks of Cl ass-C network numbers
to each network servi ce provi der. Organi zati ons usi ng the network servi ce provi der for
I nternet connecti vi ty are al l ocated bi tmask-ori ented subnets of the provi ders address space
as requi red.
Figure6-17 Internet Address 192.6.13.2 ANDed with Supernet Mask
255.255.254.0
To i mpl ement thi s feature, you must appl y the supernet netmask to al l i nterfaces connected
to the supernet usi ng the ifconfig command. Thi s feature wi l l al l ow al l hosts on the
supernet to communi cate wi th al l other hosts on the supernet wi thout standard routi ng.
I n the exampl e bel ow, the hosts i n two Cl ass C networks, 192.6.12 and 192.6.13, are i ncl uded
i n a l arger supernet usi ng the netmask opti on.
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 1 1 1 1 1 0 0 0
1 1 0 0 0 0 0 0 1 1 0 0 0 0 0 1 1 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0
1 1 0 0 0 0 0 0 1 1 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
overwrite value 1 in
network address
resulting in a supernet
address of 192.6.12.
Net
Mask
255 . 255 . 254 . 0
0 values in mask
AND
192 . 6 . 13 . 2
Internet
Address
Bit values
converted to
zero
Bit values unchanged
Convert
to
Super-
net
Address
192 . 6 . 12 . 2
Chapter 6 139
NOTE Si nce the gateway i s i tsel f a host on the supernet, i t must support CI DR.
Figure6-18 Network Map for Supernetting
A
G
C
B
192.6.14.1
192.6.14.2
192.6.12.1
255.255.254.0
192.6.12.2
255.255.254.0
192.6.13.2
255.255.254.0
Supernet
Network
G
d
s
192.6.14.3
(Gateway)
Chapter 6 140
Chapter 7 141
7 LAN Device and Interface
Terminology
Fol l owi ng i s a descri pti on of terms used by the I /O subsystem to i denti fy LAN cards and
devi ce l es associ ated wi th LAN cards.
LAN Device and Interface TerminologyDRAFT COPY
Interfaces
Chapter 7 142
Interfaces
HP-UX 11i v2 al l ows you to congure mul ti pl e I P addresses for a si ngl e physi cal i nterface.
Thi s al l ows a si ngl e system to be seen as mul ti pl e systems, wi th mul ti pl e I P addresses and
host names, even i f the system has onl y one physi cal i nterface card. The I P addresses
assi gned to a card can general l y be on the same subnet or on di fferent subnets.
Logi cal i nterfaces are al so used when an i nterface card i s used for both I P/Ethernet and
I P/I EEE802.3 packets. (I n HP-UX 11i v2, al l I P packets sent over I EEE802.3 must use
Sub-Network Access Protocol (SNAP) encapsul ati on.) Sendi ng I P packets usi ng Ethernet and
sendi ng I P packets usi ng I EEE 802.3 over the same card requi res two separate l ogi cal
i nterfaces. To send I P packets usi ng Ethernet and I EEE 802.3, you must congure two l ogi cal
i nterfaces, wi th two di fferent I P addresses. I n addi ti on, the I P addresses must be i n two
di fferent subnets. For l ogi cal i nterfaces wi th the same encapsul ati on, the I P addresses can be
on the same or on di fferent subnets.
I n HP-UX 11i v2, the i nterface names used for ifconfig and /etc/rc.config.d/netconf
statements can have a l ogi cal i nterface number appended to the card name. The syntax i s:
nameX[:logical_interface_number]
name i s the cl ass of the i nterface. Val i d names i ncl ude l an (Ethernet LAN, Token Ri ng, FDDI ,
or Fi bre Channel l i nks), snap (I EEE802.3 wi th SNAP encapsul ati on), atm (ATM), du
(Di al -up), i xe (X.25), or mfe (Frame Rel ay).
X i s the Physi cal Poi nt of Attachment (PPA). Thi s i s a numeri cal i ndex for the physi cal card i n
i ts cl ass. For LAN devi ces, the lanscan command di spl ays the concatenated name and PPA
number i n the Net-I nterface NamePPA el d.
logical_interface_number i s an i ndex that corresponds to the l ogi cal i nterface for the
speci ed card. The defaul t i s 0. The i nterface name l an0 i s equi val ent to l an0:0, l an1 i s
equi val ent to l an1:0, and so on.
The rst l ogi cal i nterface for a card type and i nterface i s known as the initial interface. You
must congure the i ni ti al i nterface for a card/encapsul ati on type before you can congure
subsequent i nterfaces for the same card/encapsul ati on type. For exampl e, you must congure
l an2:0 (or l an2) before conguri ng l an2:1. Once you have congured the i ni ti al i nterface, you
can congure subsequent i nterfaces i n any order.
DRAFT COPY LAN Device and Interface Terminology
RARP Conguration
Chapter 7 143
RARP Conguration
RARP (Reverse Address Resol uti on Protocol , RFC 903) congurati on i s an opti onal
addressi ng scheme i n whi ch a freshl y booted system queri es a network server for the I P
address of i ts own networki ng i nterface.
For exampl e, i f you have a l arge i nstal l ati on wi th many nodes, you can central i ze the I P
address database onto a system that serves as a RARP server. When each cl i ent system wants
to congure i ts network i nterface, i t queri es the RARP server to provi de the i nformati on l i sted
i n i ts database. I n thi s way, each cl i ent system does not need to have i ts own customi zed
versi on of the netconf l e to contai n i ts I P address.
When an i nterface needs to be congured wi th an I P address speci ed by a RARP server, the
/usr/sbin/rarpc program i s used to broadcast a RARP request over the network connected
to the i nterface for whi ch the i nformati on i s bei ng requested. I f there i s a RARP server on that
network, and i f the hardware address for the cl i ent i nterface i s i n the servers database, then
the server wi l l send a response to the cl i ent contai ni ng the I P address of that i nterface. The I P
address i s then passed to the congurati on scri pt, whi ch uses i t to congure the i nterface.
Setting Up a RARP Client
An i nterface i s congured to use RARP congurati on when the IP_ADDRESS vari abl e i n the
/etc/rc.config.d/netconf l e i s assi gned the val ue of RARP. The I P address vari abl e i s an
array, each el ement of whi ch corresponds to a parti cul ar i nterface number. Usual l y, thi s
vari abl e contai ns an expl i ci t I P address, whi ch i s used to congure the i nterface speci ed by
the INTERFACE_NAME vari abl e.
To congure an i nterface to use RARP, the /etc/rc.config.d/netconf l e must be modi ed
so the IP_ADDRESS vari abl e i s set to RARP. Thi s can be done wi th a text edi tor such as vi, and
i t can be done for i nterface entri es other than 0. For exampl e, for i nterface entry 1 to use
RARP, the IP_ADDRESS l i ne shoul d be modi ed to IP_ADDRESS[1]=RARP. I f the i nterface name
for entry 1 i s speci ed as INTERFACE_NAME[1]=lan1, then i nterface lan1 wi l l be congured
wi th RARP i nformati on when the system i s next booted.
When maki ng thi s modi cati on, the I P address shoul d be recorded so the appropri ate entry
can be added to the server database.
Setting Up a RARP Server
A system i s set up to be a RARP server when the RARPD vari abl e i n
/etc/rc.config.d/netconf i s set to 1. Usual l y, thi s vari abl e i s set to 0 so that a RARP
server i s not started.
LAN Device and Interface TerminologyDRAFT COPY
RARP Conguration
Chapter 7 144
Thi s can be done wi th a text edi tor such as vi. Thi s wi l l cause /usr/sbin/rarpd to be started
at boot ti me.
Another l e whi ch must be modi ed i s /etc/rarpd.conf. Thi s i s the RARP server database
l e. I t contai ns a l i st of entri es that map hardware address to I P address for each cl i ent
i nterface.
The /etc/rarpd.conf l e has the fol l owi ng format:
A comment l i ne i s i ndi cated by a pound si gn (#) i n the rst col umn.
Other than comment l i nes and bl ank l i nes, al l l i nes are consi dered cl i ent entri es. A cl i ent
entry i s of the form:
<hardware_address> <i p_address>
where <hardware_address> consi sts of col on-separated (:) hexadeci mal bytes, and
<i p_address> consi sts of dot-separated (.) deci mal bytes.
Exampl e:
08:00:09:22:e4:a9 15.13.106.69
There must be exactl y 6 hardware address bytes.
There must be exactl y 4 protocol address bytes.
Once the rarpd server i s started, i t wi l l recei ve RARP requests over al l congured network
i nterfaces, and i t wi l l respond to cl i ents that have entri es i n the RARP database.
I f the /etc/rarpd.conf l e i s modi ed whi l e a rarpd i s al ready runni ng, the changes wi l l not
be reected i n the rarpd appl i cati on unti l i t i s restarted or i s sent the SI GHUP si gnal . To see
what i nformati on i s i n the currentl y runni ng rarpd, sendi ng i t a SIGINT si gnal causes i t to
dump i ts database i nto /var/tmp/rarpd.db.
See the rarpd(1M) and rarpc(1M) man pages for more i nformati on.
145
Index
Symbols
$HOME/.netrc, 99
$HOME/.rhosts, 99
/etc/hosts, 29, 96, 97, 99
creati ng, 28
edi ti ng manual l y, 28
edi ti ng wi th SAM, 13
permi ssi ons, 30
purpose of, 28
sampl e entry, 30
/etc/hosts.equi v, 99
/etc/networks, 97
permi ssi ons, 33
purpose of, 32
sampl e entry, 34
syntax, 33
/etc/protocol s
permi ssi ons, 35
purpose of, 34
syntax, 34
/etc/rc.cong.d/netconf, 29, 96, 99
edi ti ng wi th SAM, 13
purpose of, 24
/etc/route
and SAM, 13
/etc/servi ces, 31, 98
edi ti ng, 31
permi ssi ons, 32
purpose of, 31
sampl e entry, 32
syntax, 31
/sbi n/i ni t.d/net, executi ng, 26
/stand/system, creati ng kernel , 19
/usr/adm/i netd.sec, 99
Numerics
127.n.n.n, 25
A
Address, Descri pti ons, 95
Al i as, 29
and /etc/networks, 32
and /etc/protocol s, 34
and /etc/servi ces, 31
ARP cache, 94
ARPA host name, 99
Assi gni ng
I P address, 25
network i nterface name, 25
C
Card
conguri ng, 10
i nstal l i ng, 5
movi ng, 11, 16
Conguri ng
gateways, 13, 113
kernel manual l y, 19
LAN cards, 10
manual l y, 19
network connecti vi ty, 13
Contacti ng HP, 50, 86
D
Di agnosti cs, pi ng(1M), 15
Documenti ng probl ems, 50, 86
Dynami c routi ng, 116, 129
E
Edi ti ng l es
/etc/hosts, 28
/etc/networks, 32
/etc/protocol s, 34
/etc/rc.cong.d/netconf, 24
/etc/servi ces, 31
Encapsul ati on method, 10
Error messages, 85
Expl i ci t routi ng, 116, 129
G
Gateway
conguri ng, 13
deni ti on, 94
H
Hardware
path, 10
sl ot numbers, 10
Host
address, 97, 104
and /etc/hosts, 29
name, 99
hostname(1M), 29
Index
146
I
i fcong(1M), 97
enabl i ng l oopback, 25
exampl e, 111, 123
manpage, 84
subnet addressi ng, 109
I nstal l i ng
hardware, 5
LAN/9000 software, 1
prerequi si tes, 3
I nterface card
stati sti cs, 44
status val ues, 45
I nternet address, 96
address ranges, 102
and /etc/hosts, 29
assi gni ng, 102
cl asses, 102
conguri ng manual l y, 25
conguri ng wi th SAM, 9
di sti ngui shed from network address, 102
formats, 101
I P address, 96
l ogi cal i nstances, 142
mul ti cast addresses, 133
network address, 100
reconguri ng, 16
subnetti ng, 105
I nterprocess communi cati on, 98
I P address
See I nternet address, 9
I Pv6, xi i i
K
Kernel
and /stand/system l e, 19
creati ng, 19
kmupdate, 20
L
LAN card
conguri ng, 10
i ni ti al i zi ng, 10
LAN network i nterface, power-up, 11
LAN/9000
devi ce termi nol ogy, 141
prei nstal l ed, 2
l anadmi n(1M)
i nterface card stati sti cs, 44
NMI D, 44
status di spl ay, 44
status val ue deni ti ons, 45
l anscan(1M), 2
manpage, 84
NMI D, 15
l i nkl oop(1M), 84
NMI D, 15
Loadi ng software, 4
Loggi ng
messages, 85
Logi cal i nterfaces, 142
l s(1M), 11
M
MAC address, 96
manpage
arp, 84
i fcong, 84
l anadmi n, 84
l anscan, 84
l i nkl oop, 84
ndd, 84
netfmt(1M), 84
netstat(1M), 84
nettl , 84
pi ng, 84
route(1M), 84
Manual reference page, see manpage, 84
Messages, 85
l oggi ng and traci ng, 85
more(1M), 14
N
ndd
manpage, 84
netfmt(1M)
manpage, 84
netstat(1M)
manpage, 84
veri fyi ng remote systems, 14
nettl , 85
manpage, 84
Network
i nterface, 10, 25
number, 97
termi nol ogy, 93
Network addresses, 97
ARPA host name, 99
assi gnment rul es, 103
Index
147
deni ti ons, 95
di sti ngui shed from i nternet address, 102
host address, 97
host name, 99
HP-UX host name, 99
I nternet address, 96
l i nk l evel address, 96
l ogi cal i nstances, 142
MAC address, 96
NFS host name, 99
port address, 98
reserved, 103
stati on address, 96
subnetti ng, 105
system host name, 99
system node name, 99
TCP port number, 98
troubl eshooti ng, 103, 112
UDP port number, 98
Network I nterface Name and Uni t deni ti on,
93
NFS host name, 99
O
OLA/R, i x
Onl i ne hel p system
SAM, 9
P
pi ng(1M), 15
manpage, 84
Port, 98
address, 98
number and /etc/servi ces, 31
R
Reserved addresses, 103
route(1M), 111, 116, 123, 129
manpage, 84
Routes and Protocol s
deni ti on, 93
Routi ng
dynami c, 116, 129
expl i ci t, 116, 129
mul ti cast, 134
Routi ng tabl e
addi ng entri es, 26
deni ti on, 94
S
SAM
See System Admi ni strati on Manager, 9
shutdown(2M), 5
Software
conguri ng wi th SAM, 10
l oadi ng wi th swi nstal l , 4
Stati on address, 96
Subnet
addressi ng, 105, 107
conguri ng gateways, 113, 116, 129
exampl e, 111, 123
xed-l ength addressi ng, 91, 109
vari abl e-l ength addressi ng, 91, 118
Supernet
addressi ng, 91, 137
conguri ng gateways, 132
swi nstal l (1M), 4
System Admi ni strati on Manager
conguri ng LAN cards, 10
conguri ng network connecti vi ty, 13
descri pti on of, 9
i ni ti al i zi ng LAN cards, 10
onl i ne hel p system, 9
System nami ng
host name, 28, 99
node name, 99
system name, 28
T
TCP port number, 98
Termi nol ogy
LAN devi ce, 141
network, 93
Traci ng
messages, 85
Troubl eshooti ng
contacti ng HP representati ve, 50, 86
network addresses, 103, 112
U
UDP port number, 98
uname(1M), 3, 86, 87
V
Veri fyi ng
LAN i nstal l ati on, 15
network connecti vi ty, 14
Vi rtual I P (VI P) Address, 135

HP - LAN Administration

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HP - LAN Administration

Uploaded by

Copyright:

Available Formats

HP-UX LAN Administrators Guide

Network NS_LS_DRIVER Error 2004, pid [ICS]

You might also like