Installing and Administering LAN/9000 Software Edition 9 Manufacturing Part Number: B2355-90748 E0302 United States © Copyright 2002 Hewlett-Packard Company
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty.
©copyright 1980, 1984, 1986 Novell, Inc. ©copyright 1986-1992 Sun Microsystems, Inc. ©copyright 1985-86, 1988 Massachusetts Institute of Technology. ©copyright 1989-93 The Open Software Foundation, Inc. ©copyright 1986 Digital Equipment Corporation. ©copyright 1990 Motorola, Inc.
Contents Printing History Preface Related Information New for the HP-UX 11i Release 1. Installing LAN/9000 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 Step 1: Checking LAN Installation Prerequisites . . . . . . . . . . . . . . . . . .27 Step 2: Loading LAN Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Step 3: Installing The Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 2.
Contents Editing the LAN Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the Hewlett-Packard Station Address (optional). . . . . . . . Editing /etc/rc.config.d/netconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Executing the Network Configuration Script . . . . . . . . . . . . . . . . . . . 49 49 50 52 Creating the /etc/hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Network and System Names . . . . . . . . . . . .
Contents Flowchart 10: Gateway Remote Loopback Test continued. . . . . . . . .106 Flowchart 11: Subnet Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 5. LAN Resources 6. Network Addressing Overview of Network Addressing Schemes . . . . . . . . . . . . . . . . . . . . . .123 Networking Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125 Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Variable-Length Subnet Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Assigning Variable-Length Subnet Masks . . . . . . . . . . . . . . . . . . . . 156 Configuring Gateways on Variable-Length Subnets . . . . . . . . . . . . . . Explicit Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Proxy ARP Server . . . . . . . . . . . . . . . . . . . .
Printing History The manual printing date and part number indicate its current edition. The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. the manual part number will change when extensive changes are made. Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, you should subscribe to the appropriate product support service.
Preface This manual provides information for installing and administering the LAN/ 9000 product. The LAN/9000 product allows HP 9000 computers to connect to an IEEE 802.3 or Ethernet Local Area Network. A LAN/9000 network can be further extended via bridges and routers into a Wide Area Network. This manual also includes the information that may be useful for configuring other HP-UX link products, such as Token Ring/9000, FDDI/ 9000, 100Base-T HSC/9000 and 100Base-T PCI/9000.
9000 software. Chapter 6 Network Addressing defines networking terms and explains network interface names, network addresses, names and subnets. The information in this chapter is applicable to configuring other HP-UX link products on TCP/IP networks. Chapter 7 LAN Device and Interface Terminology defines terms used by the I/O system to identify LAN cards and device files. The information in this chapter is applicable to configuring other HP-UX link products on TCP/IP networks.
Related Information This section provides lists of related networking and system documentation along with lists of the protocols and standards on which the LAN and Internet Services products are based.
Table 1 List of Networking Manuals For Information on: Table 2 Read: Gigabit Ethernet Cards HSC and PCI 1000Base-SX/9000 Quick Install EISA Configuration Utility Installing Peripherals Installing Token Ring/ 9000 Software Installing and Administering Token Ring/9000 Software Installing FDDI/9000 Software Installing and Administering FDDI/9000 Software Installing Fibre Channel Software Installing and Administering Fibre Channel/9000 Using Point-to-Point or Serial Line IP Protocols with HP 9000
Table 3 List of Networking Protocols and Standards For Information on: Internetwork Mail Routing Read: Installing and Administering Internet Services Sendmail by Brian Costales with Eric Allman & Neil Rickert, published by O’Reilly and Associates, Inc. Sendmail–An Internetwork Mail Router (Document reference number: UNX11.2.
Table 3 List of Networking Protocols and Standards For Information on: Read: Standard for the Format of ARPA Internet Text Messages RFC 822 Telnet MIL-STD 1782; RFC 854 Transmission Control Protocol (TCP) MIL-STD 1788; RFC 793, 813, 814, 816, 817, 179, 889, 896, 1122, 1323, 2018, 2414, 2581, 2582 IP Multicast RFC 1112 Path MTU Discovery RFC 1191 Window Scaling RFC 1323 Reverse Address Resolution Protocol (RARP) RFC 903 16
New for the HP-UX 11i Release The 11i HP-UX release has the following transport (IP, TCP, and UDP) changes: • IP address subnet identifiers can now be all 1s or all 0s (RFC 1812). • IP PMTU (Path Maximum Transmission Unit) discovery algorithm reverts back to 10.20 behavior. • Virtual IP (VIP) addresses can now be configured for a system. A system VIP address is not tied to a specific physical interface and can be used to send and receive IP packets on any physical interface of the system.
initiate the use of these enhancements. **A scaling factor of 1 (same as no scaling) is used unless the application has a receive buffer greater than 2**16. Refer to the "Scaled Windows" section below for more information. IP Subnet Mask The ifconfig subnet mask default now allows all 1s or all 0s in the masked part of the subnet field. This provides up to twice as many IP addresses as before.
The value 2 for the ndd parameter ip_pmtu_strategy is no longer supported. This was previously the default value for this parameter. The new default value for ip_pmtu_strategy is 1, which causes the system to use the HP-UX 10.20 IP PMTU behavior. If the nddconf file has the value 2 for this parameter, the new default value (1) will be used. A description of the IP PMTU strategy is provided in the ndd online help facility.
Note that the infrastructure of the network (routers, switches) must allow IP packets with the address 17.1.1.1 to be properly routed to this system's interfaces on the 15.n.n.n and 16.n.n.n networks for this configuration to be useful. /etc/rc.config.d/netconf file statements for the above VIP: INTERFACE_NAME[2]=lo0:1 IP_ADDRESS[2]=15.1.1.1 : : ifconfig command for the above VIP: ifconfig lo0:1 inet 15.1.1.1 Note that you cannot assign VIPs to the primary loopback interface, lo0:0, or lo0.
RFC 1323 (TCP Extensions for High Performance) specifies TCP extensions intended to benefit high-speed networks and networks with both large bandwidths and long delays, such as high capacity satellite networks or long-distance fiber-optic networks. Scaled windows and timestamps were available beginning in release 10.30, but these features were not documented, and the ndd parameters to disable them were not supported.
• Initial TCP Congestion Window RFC 2414 defines a formula for calculating the sender's initial congestion window that usually results in a larger window than in previous releases. The default initial congestion window is now calculated using the following formula: min((4 * MSS), max(2 * MSS, 4380)) where MSS is the maximum segment size for the underlying link. With the new congestion window formula, it is possible for TCP to send a large, initial block of data without waiting for acknowledgments.
• TCP Socket Structure Caching The ndd TCP parameter tcp_conn_strategy is used to enable socket caching. This value determines how many cached data structures for BSD TCP sockets the system keeps. This could cause the system to speed up considerably if there are many short-lived connections on the system. The default value of 0 (zero) disables the feature. A value between 1 and 512 will set a minimum of 512. Any number above 512 will set that value. This feature was available but undocumented in HP-UX 11.
receive buffers and UDP receive buffers. This can prevent situations where processes consume excessive amounts of memory by requesting large send or receive buffers filling these buffers by not reading data from the socket or by sending large amounts of data. This feature was added to 11.00 to solve a system hang problem.
1 Installing LAN/9000 This chapter describes the manual procedures to load LAN/9000 software and to install LAN hardware onto your system.
Installing LAN/9000 Overview Overview This chapter contains the following sections: • Step 1: Checking LAN Installation Prerequisites. • Step 2: Loading LAN Software. • Step 3: Installing LAN Hardware. NOTE If you have a system with LAN/9000 preinstalled on it, you may skip this chapter and go directly to chapter 2. Execute the command lanscan to determine if the LAN/9000 software and hardware have been pre-installed.
Installing LAN/9000 Step 1: Checking LAN Installation Prerequisites Step 1: Checking LAN Installation Prerequisites Prior to loading the LAN/9000 product onto your system, check that you have met the following hardware and software prerequisites: • Check that /usr/bin, /usr/sbin, and /sbin are in your PATH using the command: echo $PATH • The operating system should have been upgraded to HP-UX 11i software.
Installing LAN/9000 Step 2: Loading LAN Software Step 2: Loading LAN Software Follow the steps below to load the LAN/9000 software using the HP-UX swinstall program. 1. Log in as root. 2. Check that /usr/bin, /usr/sbin, and /sbin are in your PATH. 3. Insert the software media into the appropriate drive. 4. Run the swinstall program using the command: swinstall This opens the Software Selection Window and Specify Source Window. 5.
Installing LAN/9000 Step 2: Loading LAN Software The user interface disappears and the system reboots. 12. When the system reboots, check the swinstall log file in /var/adm/sw to make sure that the installation was successful. For additional information on the HP-UX swinstall program, refer to Installing HP-UX.
Installing LAN/9000 Step 3: Installing The Hardware Step 3: Installing The Hardware Follow the steps below to prepare the system for installation of your network interface hardware. 1. At the HP-UX prompt, execute the command: shutdown -h Wait for the system to respond with a message indicating that the system has been halted. 2. Observe antistatic precautions by following the guidelines as described in the installation instructions in the hardware manual or the Antistatic Precautions Note. 3.
2 Configuring LAN/9000 Using SAM This chapter describes how to configure LAN using SAM, the System Administration Manager.
Configuring LAN/9000 Using SAM • Overview of Configuration Using SAM • Step 1: Configuring the Network Interface Card • Step 2: Configuring Network Connectivity • Step 3: Verifying the Installation • Step 4: Reconfiguring IP Addresses 32 Chapter 2
Configuring LAN/9000 Using SAM Overview of Configuration Using SAM Overview of Configuration Using SAM Once you have installed hardware and software, you can use SAM to automatically configure networking. SAM stands for System Administration Manager, a menu-driven utility for system administration tasks, including configuration of networking software. SAM has two user interfaces, an X-Windows system interface and a text terminal interface.
Configuring LAN/9000 Using SAM Step 1: Configuring the Network Interface Card Step 1: Configuring the Network Interface Card NOTE Make sure the LAN card and driver are installed in the system before you use SAM to configure the software. Log in as root and do the following: 1. At the HP-UX prompt, type: sam 2. Select the Networking and Communications item of the SAM main window. 3. Select the Network Interface Cards item of the Networking and Communications window. 4.
Configuring LAN/9000 Using SAM Step 1: Configuring the Network Interface Card NOTE SAM displays the Card Name, Hardware (H/W) Path, and Station Address fields with the appropriate values. These fields cannot be modified. b. Choose the Card Type of your LAN card. The default is Ethernet. SNAP802.3 can be selected. NOTE The Enable DHCP button specifies that the system is a Dynamic Host Configuration Protocol (DHCP) client.
Configuring LAN/9000 Using SAM Step 1: Configuring the Network Interface Card your LAN card. If the software is correctly configured, SAM displays the Network Interface Cards object list with the status Enabled for your LAN card; otherwise, SAM displays an error message. 8. Choose Exit from the “File” menu. 9. At the Networking and Communications window, choose Exit SAM from the “File” menu.
Configuring LAN/9000 Using SAM Step 2: Configuring Network Connectivity Step 2: Configuring Network Connectivity Your system may not be able to communicate with other systems (for example, PCs, workstations, servers, etc.) until you configure system-to-system connections. You can use SAM to do this automatically by completing the following steps: 1. At the HP-UX prompt, type: sam 2. Double-click on the Networking and Communications item of the SAM main window. 3. Double-click on Hosts.
Configuring LAN/9000 Using SAM Step 2: Configuring Network Connectivity is required for this remote system connection. Use the SAM on-line help system for information about gateways. 5. Activate the OK button to enable your system to communicate with this system and return to the Internet Addresses window. SAM updates the object list to include the remote system you configured.
Configuring LAN/9000 Using SAM Step 3: Verifying the Installation Step 3: Verifying the Installation Once your LAN/9000 software is installed, fully configured and running, you should execute the following commands to verify LAN hardware and software installation. See the man pages for complete descriptions of the commands listed below. 1. Check the state of all LAN hardware. To do so execute the lanscan command and verify that the Hardware State is UP. 2. Check the state of the network interface.
Configuring LAN/9000 Using SAM Step 4: Reconfiguring IP Addresses Step 4: Reconfiguring IP Addresses If you have rearranged any network interface cards in the system you may need to reconfigure the IP addresses. Follow the steps below: 1. At the HP-UX prompt, type: sam 2. At the main menu select the Networking and Communications item. 3. Select the Network Interface Cards item. 4.
3 Manually Installing and Configuring LAN/9000 This chapter provides information on manually configuring LAN/9000 software.
Manually Installing and Configuring LAN/9000 • Creating a New Kernel for All HP 9000 Systems. • Verifying the LAN Device Files. • Release 11i drivers, configuration files, and init scripts. • Editing the LAN Configuration Files. • Creating the /etc/hosts File. • Activating Optional Network Features.
Manually Installing and Configuring LAN/9000 Creating a New Kernel for HP 9000 Systems Creating a New Kernel for HP 9000 Systems Before attempting this procedure, familiarize yourself with the system reconfiguration information in the mk_kernel(1M) manual reference page and HP-UX system literature. Refer to the System Administration manual for your system for complete instructions on how to create a kernel.
Manually Installing and Configuring LAN/9000 Creating a New Kernel for HP 9000 Systems Table 3-1 Driver Keyword Software driver names HP 9000 Systems btlan HSC and PCI 100BT adapters on SuperDome, A, L, N and rp54xx servers btlan0 EISA 100BT adapters on D-Class and Workstations (only supported on HP-UX 11i 32-bit, and not on 64-bit) btlan1 HP-PB 100BT adapters on K & T-Class systems lan2, lan3 Core Built-in 10/100BT card gelan Gigabit Ethernet add-on adapters on A, L, N, Superdome, Workstations,
Manually Installing and Configuring LAN/9000 Creating a New Kernel for HP 9000 Systems Table 3-2 Keyword Comments netdiag1 tun required for PPP 5. Make a copy of the existing kernel (default name vmunix). 6. Regenerate the kernel with mk_kernel, using the edited system file as input. mk_kernel creates the new hp-ux kernel (the default is /stand/build/vmunix_test). mk_kernel In this example a new kernel is created in the build directory called vmunix_test.
Manually Installing and Configuring LAN/9000 Verifying the LAN Device Files Verifying the LAN Device Files All IP access to LAN devices is done through the files /dev/lan and /dev/snap, which are symbolically linked to the Data Link Provider Interface (DLPI) device file /dev/dlpi. The /dev/dlpi file is automatically created at installation time.
Manually Installing and Configuring LAN/9000 HP-UX 11i Drivers, Configuration files and Init Scripts for Fast Ethernet HP-UX 11i Drivers, Configuration files and Init Scripts for Fast Ethernet With the HP-UX 11i Release, Hewlett-Packard offers the LAN Unified Driver btlan for all PCI and HSC 100Base-T cards. Table 3-3 below shows the different Software drivers, Configuration Files, and Init scripts for different platforms.
Manually Installing and Configuring LAN/9000 HP-UX 11i Drivers, Configuration files and Init Scripts for Gigabit Ethernet HP-UX 11i Drivers, Configuration files and Init Scripts for Gigabit Ethernet Hewlett-Packard offers Gigabit Ethernet products on several platforms, both with the add-on cards and the Core IO cards. Table 3-4 below shows the different Software drivers, Configuration Files, and Init scripts for different platforms.
Manually Installing and Configuring LAN/9000 Editing the LAN Configuration Files Editing the LAN Configuration Files To configure and initialize LAN manually, you must edit the /etc/rc.config.d/netconf file and execute the LAN/9000 initialization script. To do so, you must be logged on as super-user. The script reads the information in the edited netconf file when the system reboots and performs the following: • Configures the network interface with an IP address and optional subnet mask.
Manually Installing and Configuring LAN/9000 Editing the LAN Configuration Files configuration file) will modify the station address each time the system reboots. The modified station address is not permanent. Each system reboot causes the preset station address to be overwritten when a value is supplied to the configuration parameters. CAUTION Each HP LAN card has a preset station address, for example 080009xxxxxx. Modifying this address should be approached with caution.
Manually Installing and Configuring LAN/9000 Editing the LAN Configuration Files configure network interface parameters. The internet configuration parameters have an index value, [x], that groups the configuration parameters together. Following is a sample netconf file entry: INTERFACE_NAME[0]=”lan0” IP_ADDRESS[0]=”192.6.1.1” SUBNET_MASK[0]=”255.255.224.
Manually Installing and Configuring LAN/9000 Editing the LAN Configuration Files ROUTE_ARGS[0]=”” The index value must be different for each additional route. If you want to modify the preset station address of any HP interface card, proceed to the section, “Modifying the Hewlett-Packard Station Address”; otherwise go to the section, “Executing the Network Configuration Script.” Executing the Network Configuration Script Once you have edited the netconf file, you need to make your configuration active.
Manually Installing and Configuring LAN/9000 Editing the LAN Configuration Files re-initialize any other networking subsystems. For example, if you are running an Internet Service over the link you have just configured manually, the service may not work with your new configuration. The system boot sequence initializes networking subsystems and products in the correct order. Initializing a specific subsystem alone may cause network problems.
Manually Installing and Configuring LAN/9000 Creating the /etc/hosts File Creating the /etc/hosts File You must edit the /etc/hosts file to add an IP address and hostname for the LAN card that you are installing. NOTE If you are using a naming service (DNS or NIS), you will need to modify the /etc/hosts file to add the IP address and host name to the appropriate databases on the name server system.
Manually Installing and Configuring LAN/9000 Creating the /etc/hosts File might be a fully qualified domain name including the DNS domain. For example: turtle.bnio.nmt.edu HP recommends that you try to keep these names as consistent as possible, within their limitations. This will help to minimize confusion. The examples below show how a system with the name, host3, might be referenced in the /etc/hosts and other system and networking files and commands: System name in Install screen: host3 /etc/rc.config.
Manually Installing and Configuring LAN/9000 Creating the /etc/hosts File printable character except spaces, newline, or the comment character (#). Naming Convention: the first nine characters should be unique for each network host. alias Common name or names for the node. An alias is a substitute for host_name. Alias names are optional. Naming Convention: the first nine characters should be unique for each network host.
Manually Installing and Configuring LAN/9000 Activating Optional Network Features Activating Optional Network Features To activate special network features, you may also want to configure /etc/services, /etc/networks, and /etc/protocols. Each of these steps is optional. NOTE If you are using NIS, modifications to the /etc/services, /etc/networks, /etc/protocols files should only be made on the NIS Master Server. Refer to Installing and Administering NFS Services for more information.
Manually Installing and Configuring LAN/9000 Activating Optional Network Features comment character (#). port_num / protocol port_num is the protocol port number assigned to this service. All requests for this service must use this port number. protocol is the protocol name, as listed in /etc/protocols, that the service uses. alias Common name or names for the service. An alias is a substitute for service_name. Alias names are optional.
Manually Installing and Configuring LAN/9000 Activating Optional Network Features command use the /etc/networks file. You must configure this file for your host if you want route or netstat to use symbolic network names instead of addresses. You can create an /etc/networks file two ways: • From scratch, entering the known nodes in the format shown below. • By copying the file from another node.
Manually Installing and Configuring LAN/9000 Activating Optional Network Features • Trailing blank and tab characters are allowed. • Blank line entries are allowed. • Only one entry per line is allowed. /etc/networks Permissions The /etc/networks file should be owned by user bin, group bin, and it should have 0444 (-r—r—r—) access permission. For more information on /etc/networks, refer to the networks(4) man page in the HP-UX Reference Pages.
Manually Installing and Configuring LAN/9000 Activating Optional Network Features Parameters protocol_name Name of the protocol. Protocol names can contain any printable character except spaces, newline, or the comment character (#). protocol_num Protocol number that identifies this protocol. alias Common name or names for the protocol. An alias is a substitute for protocol_name. Alias names are optional. /etc/protocols Format • Lines cannot start with a blank or tab character.
Manually Installing and Configuring LAN/9000 Activating Optional Network Features 62 Chapter 3
4 Troubleshooting LAN/9000 This chapter provides guidelines for troubleshooting LAN/9000. It contains the following sections: • Troubleshooting Overview.
Troubleshooting LAN/9000 • Troubleshooting Q and A. • LAN Interface Card Statistics. • 100Base-T Checklist. • Diagnostic Flowcharts.
Troubleshooting LAN/9000 Troubleshooting Overview Troubleshooting Overview Troubleshooting LAN problems can be difficult because a variety of hardware and software components may be involved and because the problem impacting your system may originate in another part of the network. The first two sections in this chapter provide quick fix solutions to common network problems. “Addressing Do's and Don'ts” identifies common addressing errors made when new systems are added to the network.
Troubleshooting LAN/9000 Troubleshooting Q & A Troubleshooting Q & A New system disrupts LAN: I tried to attach a new system to our site LAN. To make the installation process faster, I copied over an /etc/rc.config.d/netconf file from another system on the site LAN and used it on the new system. When I booted up the system, the site LAN went down. Answer: You probably didn't assign a new IP address and host name prior to rebooting the system.
Troubleshooting LAN/9000 Troubleshooting Q & A gateway. Related Documentation: Refer to “Assigning Subnet Addresses” in chapter 6. Configuring address 127.0.0.1: I tried to add the IP address, 127.0.0.1, and the system won't accept it. Answer: Addresses with the format 127.n.n.n are reserved as loopback addresses. Select another IP address. You can obtain Class C addresses that are unique within the ARPANET by contacting Government Systems, Inc.
Troubleshooting LAN/9000 Troubleshooting Q & A quit Related Documentation: Refer to the lanadmin(1M) man page. Tracing: What's the best way to obtain and format tracing information when I am using the nettl(1M) utility? Answer: The HP field engineers recommend the following commands: To begin LAN and loopback tracing, execute: nettl -tn pduin pduout -e ns_ls_driver -f filename To end LAN tracing, execute: nettl -tf -e all To format your entire LAN trace (no filtering), execute: netfmt -Nnl -f filename.
Troubleshooting LAN/9000 Troubleshooting Q & A may also be in the upper layer software (ftp or telnet). Also, it is possible that too little memory is allocated to hold fragmented messages in the IP layer. IP messages may be fragmented into smaller parts when the message is sent through the system. The fragments must be held in memory for some time so that the entire message can be reassembled because the fragments arrive at the destination at different times and possibly out of order.
Troubleshooting LAN/9000 Troubleshooting Q & A In general, the short term average load on an IEEE802.3/Ethernet LAN should not exceed more than 70% of the total bandwidth of the LAN. When it does exceed 70% of the total bandwidth, network performance begins to degrade due to an increase in collisions and deferred transmissions. When it consistently exceeds 70% of the total bandwidth, you may need to reconfigure the systems on your LAN.
Troubleshooting LAN/9000 LAN Interface Card Statistics LAN Interface Card Statistics This section contains descriptions of the RFC 1213 MIB II statistics fields for LAN interface cards which are displayed on the screen with the display command in lanadmin LAN Interface Test Mode. A description of each field follows the display. LAN INTERFACE STATUS DISPLAY Thu, Nov 21,1991 11:16:22 Network Management ID = 1 Description = lan0 Hewlett-Packard LAN ..
Troubleshooting LAN/9000 LAN Interface Card Statistics Frames Too Long Internal MAC Receive Errors = 0 = 0 RFC 1213 MIB II STATISTICS Description A textual string containing information about the interface. This string includes the name of the manufacturer, the product name and the version of the hardware interface. Type (value) The type of interface, distinguished according to the physical/link protocol(s) immediately below the network layer in the protocol stack.
Troubleshooting LAN/9000 LAN Interface Card Statistics Table 4-1 (Continued) sdlc(17) ds1(18) T-1 el(19) European equivalent of T-1 basicISDN(20) primaryISDN(21) Proprietary serial proPointToPointSerial(22) ppp(23) softwareLoopback(24) eon(25) CLNP over IP [11] ethernet-3Mbit(26) nsip(27) XNS over IP slip(28) generic SLIP ulta(29) ULTRA technologies ds3(30) T-3 sip(31) SMDS frame-relay(32) MTU Size The size of the largest datagram which can be sent/received on the interface specified in
Troubleshooting LAN/9000 LAN Interface Card Statistics Administration Status The desired state of the interface It will have one of the following values: Table 4-2 up(1) Ready to pass packets down(2) Not operative testing(3) In test mode Operation Status The current operational state of the interface. It will have one of the following values.
Troubleshooting LAN/9000 LAN Interface Card Statistics Inbound Unknown Protocols The number of packets received via the interface which were discarded because of an unknown or unsupported protocol. Outbound Octets The total number of octets transmitted out of the interface, including framing characters. Outbound Unicast Packets The total number of packets that higher-level protocols requested be transmitted to a subnetwork-unicast address, including those that were discarded or not sent.
Troubleshooting LAN/9000 LAN Interface Card Statistics Multiple Collision Frames A count of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision. Deferred Transmissions A count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. The count represented by an instance of this object does not include frames involved in collisions.
Troubleshooting LAN/9000 100Base-T Checklist 100Base-T Checklist In case of trouble with 100Base-T LAN links, you can use the following procedures to troubleshoot your network problems: • Verify Cabling: make sure the connection is secured, UTP Category 5 is used, the card is well inserted. Also, assure the cable length is not within 35 - 41 meters. Check the cable running from the HP adapter to the Switch, and the Switch port, in case either is defective.
Troubleshooting LAN/9000 100Base-T Checklist “...10/100Base-T driver detected bad cable connection between the adapter in slot # and the hub or switch.” Or use the command lanscan to get the name of the Net Interface Name or ppa number or nmid number. Once you have the ppa number, for example lan17, you can issue these following commands one at a time: lanadmin lan ppa 17 display - Look for the value of Operation Status. It should say “DOWN”. • Ensure that the host system contains the correct patch level.
Troubleshooting LAN/9000 100Base-T Checklist • If the card is not an EISA 100Base-T card, set the card to Auto-Negotiation mode. This can be done temporarily with the command: lanadmin -X AUTO_ON nmid/ppa or permanently by removing any manual settings for this port in the /etc/rc.config.d/ eisa configuration files. Refer to Table 3-3 for correct configuration file. • If problems persist, if a switch is used, manually set the switch port to the desired speed and duplex.
Troubleshooting LAN/9000 Diagnostic Flowcharts Diagnostic Flowcharts Below is a summary of the types of network tests in the diagnostic flowcharts. To diagnose your problem, first check the connections and configuration on your system (Flowcharts 1 through 5). If this does not solve your problem, use flowcharts 6 through 11 to test/verify connectivity with a remote system.
Troubleshooting LAN/9000 Diagnostic Flowcharts Figure 4-1 Loopback Tests OSI Layer telnet showmount (NFS) 6&7 5 4 3 2 Virtual Terminal NFS Services Internet Services BSD Sockets XTI TCP UDP IP ICMP ping ARP LAN Driver DLPI lanadmin linkloop Network Interface Card 1 MAU The loopback tests shown in Figure 4-1 are used to isolate a network communication problem that may be software- or hardware-related.
Troubleshooting LAN/9000 Diagnostic Flowcharts netstat(1M) reports network and protocol statistics regarding traffic and the local LAN interface. As shown in Figure 4-2, there are many options to netstat(1M). The options that are most useful are those which display information that is not available through other commands such as ping and lanadmin, for example, -a and -r options. You can also use the lanadmin(1M) command to obtain LAN driver statistics.
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 1: Configuration Test Figure 4-3 Flowchart 1 1 A Execute: lanscan C B All interfaces configured ? no Execute: ioscan yes 2 D bind errors? no F E Correct driver in system file? no Add correct driver and regen yes Call HP Chapter 4 1 83
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 1 Procedures A. Execute: lanscan. Execute lanscan to display information about LAN cards that are successfully bound to the system. For example, to check the cards on /stand/vmunix, enter: lanscan B. All interfaces configured? lanscan is successful if the output shows information about every card in the hardware backplane. C. Execute ioscan. Execute the ioscan(1M) command to check for bind errors. D.
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 2: Configuration Test continued Figure 4-4 Flowchart 2 2 A Execute ifconfig B E D C ifconfig successful ? yes no no Any error message returned? Correct ifconfig flag settings 2 yes 3 Execute: netstat -in G F Interface name correct? no Correct encapsulation using ifconfig yes I H Suspect LAN card I/O problem ? J yes Execute: lanadmin Problem resolved ? no Call HP yes no Stop 4 E Chapter 4 85
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 2 Procedures A. Execute: ifconfig . Execute ifconfig on the interface you want to test. For example, to check LAN interface lan0, enter: ifconfig lan0 B. ifconfig successful? ifconfig is successful if the output shows the correct Internet address and the flags, typically: UP,BROADCAST,RUNNING. C. Any error message returned? If ifconfig is not successful, and an error message appears, go to Flowchart 3.
Troubleshooting LAN/9000 Diagnostic Flowcharts indicate possible LAN card problems, go to J, otherwise go to Flowchart 4. I. Execute: lanadmin. Use lanadmin to ensure the LAN card is operational. If the values of the Ierrs and Oerrs fields increase substantially during a file transfer attempt, this can indicate transmission or reception problems. Refer to “LAN Interface Card Statistics” in this chapter for more information. J. Problem resolved? If you have found and corrected the LAN card problem, stop.
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 3: Configuration Test continued Figure 4-5 Flowchart 3 3 A E C ifconfig not found No such interface Bad system call Restore ifconfig from media Execute: lanscan Reconfigure HP-UX kernel to include LAN/9000 G 1 yes Execute: /sbin/init.d/net .
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 3 Procedures A. ifconfig not found. The command has been relocated on the system, deleted, or /usr/sbin is not in your PATH. B. Restore /etc/ifconfig from media. You can restore ifconfig from the last good backup tape or your install/update tape. Go to Flowchart 2. C. Bad system call. Networking is not configured into the HP-UX kernel. D. Reconfigure HP-UX kernel to include LAN/9000 software.
Troubleshooting LAN/9000 Diagnostic Flowcharts M. Check the loopback interface. Use the command ping 127.0.0.1. If you cannot ping the loopback interface, call HP. If the ping is successful, go to Flowchart 2. N. Any other error message. If you received an error message not listed on this flowchart, interpret the message and take the appropriate action. If you need assistance, call your HP representative.
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 4: Network Level Loopback Test Figure 4-6 Flowchart 4 4 A Execute: ping to remote host B C ping successful? no Network unreachable ? yes Stop D yes yes Local LAN interface up ? no F no Call HP E yes Command hangs? Configure interface up 5 no G 4 H Unknown host? yes Correct BIND, NIS, or /etc/hosts configuration 4 no J I No route to host? yes Add route table entry 4 no Call HP Chapter 4 91
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 4 Procedures A. Execute: ping to remote host. Using ping(1M), send a message to the remote host with which you are having problems connecting. For example, suppose the remote host is known as 192.6.20.2. Enter: ping 192.6.20.2 NOTE HP recommends using the IP address, rather than the hostname, as part of the problem may be an error in the /etc/hosts file or connectivity with a name server. B.
Troubleshooting LAN/9000 Diagnostic Flowcharts F. Command hangs? If a message is not returned after executing ping, go to Flowchart 5. G. Unknown host? (Error= Unknown host hostname?) There is a problem with the configuration for the host in the /etc/hosts file or on the name server. H. Correct BIND, NIS or /etc/hosts configuration. Add the missing host name and start again with Flowchart 4. I. No route to host? (Error= Sendto: No route to host?) Use netstat -rn to check the routing table.
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 5: Network Level Loopback Test continued Figure 4-7 Flowchart 5 5 A B Host entry in ARP cache ? C yes yes no Remote host up? E yes LAN card OK? no no Bring up remote host Call HP D Replace or reset LAN card 4 G F Entry complete? no Use arp to complete entry 4 yes H ping local host I no ping successful? Call HP yes Note: This time ping from remote host to local host 4 94 Chapter 4
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 5 Procedures A. Host entry in ARP cache? Using arp, check that an entry exists for the remote host in your system's ARP cache. For example, suppose the remote host is known as 192.6.20.2. Enter: arp 192.6.20.2 B. Remote host up? If there is no ARP cache entry for the remote host, first check that the remote host is up. If not, the remote host has not broadcast an ARP message, and that likely is why there is no entry in the ARP cache. C.
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 6: Transport Level Loopback Test (using Internet Services) Figure 4-8 Flowchart 6 6 A Execute: telnet to remote host B yes Successful? C Stop no Execute: ftp to remote host D yes Successful? E G Check for network congestion Call HP 96 Call HP no TCP yes configured on local or remote host? F no Configure TCP 6 Chapter 4
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 6 Procedures A. Execute: telnet to remote host. Try to establish a telnet connection to the remote host. B. Successful? If your telnet attempt was successful, stop. The connection is okay through the Transport Layer (OSI Layer 4). C. Execute: ftp to remote host. Unlike telnet, ftp does not go through a pseudo-terminal driver (pty) on your system. This step tests to see if the pty is why telnet failed. D.
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 7: Link Level Loopback Test Figure 4-9 Flowchart 7 7 A Execute: linkloop on local interface C B yes Successful? D yes Execute: linkloop to remote host linkloop successful? no Stop no 8 G F E Loopback FAILED: Address has bad format Loopback FAILED: Not an individual address I H Correct the link address parameter K 7 Loopback FAILED Choose a different remote IEEE 802.
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 7 Procedures A. Execute: linkloop on local interface. Execute the linkloop command with the station address of the local interface. Execute lanscan (1M) to find the link level address (station address) on the remote host or obtain it from your network map. For more information on linkloop, refer to the man page. B. linkloop successful? If not, your LAN card may not be operational. Go to Flowchart 8. C. Execute: linkloop to remote host.
Troubleshooting LAN/9000 Diagnostic Flowcharts configuration and connectivity of the remote host.
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 8: LAN Connections Test Figure 4-10 Flowchart 8 8 A B Thick Coax ThinLAN Thick or thin cabling ? Check: AUI solidly connected to LAN card G Check: AUI solidly connected to MAU and LAN card No H A1 C Check: Backbone cable terminated at both ends RJ45 LED = ON ? Check: ThinLAN cable terminated at both ends I A2 RJ45: Card seated securedly D Check: BNC T-connectors secure Check: MAU tapped securely into cable K J Check: Backbone cab
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 8 Procedures A. Thick or thin cabling? If your network cabling is the thicker coaxial cabling, continue in the direction marked “Thick Coax.” If your network cabling is the ThinLAN cabling, continue in the direction marked “ThinLAN.” A1. RJ45 Adapter? Verify LEDs. Network Activity and Link Status LED displays: Link Status LED is lit GREEN for a valid link. Network Activity LED is lit AMBER color for both 10 Mbps and 100Mbps.
Troubleshooting LAN/9000 Diagnostic Flowcharts Make sure the AUI cable is solidly connected to the MAU and the LAN card. If the AUI cable is not connected, turn off the power to the computer before you connect it. H. Check: Backbone cable terminated at both ends. Make sure the backbone cable is terminated at both ends. I. Check: MAU tapped securely into cable. Make sure the MAU is tapped securely into the backbone cable. J. Check: Splices and Taps. Make sure all splices and taps are secure. K.
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 9: Gateway Remote Loopback Test Figure 4-11 Flowchart 9 9 A B Execute: ping from known good host through gateway to known good remote host ping successful ? yes Stop no C Execute: netstat -rn E D Add route entry on local system Direct route to remote or default route to gateway? no yes 10 F G Routing table on remote OK? no Correct routing table yes 10 104 4 Chapter 4
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 9 Procedures A. Execute: ping from known good host through gateway to known good host on remote network. This will test gateway connectivity to the remote network. For more information on ping(1M), refer to chapter 6. B. ping successful? If the executing ping returned successfully, the problem may exist in the routing table for the problem host. Go to C. C. Execute netstat -rn.
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 10: Gateway Remote Loopback Test continued Figure 4-12 Flowchart 10 10 no A Examine gateway B D Other HP; other vendors C HP 9000 E Refer to networking documentation Execute: ifconfig on gateway host G F Network interface up? no Configure interface up yes 1 106 4 Chapter 4
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 10 Procedures A. Examine gateway. If the gateway is an HP 9000, go to C. If it is not, go to B. B. Other HP; other vendors. Go to C. C. Refer to networking documentation. Refer to the documentation that came with the gateway for additional diagnostics. D. HP 9000. Go to E. E. Execute: ifconfig on gateway host. Execute ifconfig for all network interfaces on the gateway. F.
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 11: Subnet Test Figure 4-13 Flowchart 11 11 A I D Host portion all 0s or all 1s? no no Correct IP address Subnet mask set to what you expect? 11a yes yes B E Correct IP address J All hosts on subnet using same subnet mask? no Correct subnet mask 11a yes 11 F G K All hosts on network have subnet mask set? no Correct subnet mask yes Check route table on source, destination 11a H Stop 108 Correct route tables Chapter 4
Troubleshooting LAN/9000 Diagnostic Flowcharts Flowchart 11 Procedures A. Host Portion all 0's or all 1's? Execute ifconfig(1M). Is the host portion of the IP address all 0's or all 1's? These values are reserved. Refer to chapter 6 for details on subnets. If the host portion of the IP address is all 0's or all 1's, go to B to correct the IP address. Otherwise, go to C to examine the subnetwork number. B. Correct IP address. Correct the IP address and start again with Flowchart 11. D.
Troubleshooting LAN/9000 Diagnostic Flowcharts K. 110 Correct subnet mask. To do so, execute ifconfig with the proper subnet mask. Go to D.
5 LAN Resources In addition to this manual, use the following resources to maintain and administer HP LAN/9000 software.
LAN Resources HP-UX Manual Reference Pages HP-UX Manual Reference Pages While installing, configuring, or troubleshooting LAN, you may need to refer to any of the following online manual reference pages (man pages) for useful HP-UX operating system or LAN commands. To display a man page, type the following at the system prompt: man • arp(1M) displays and modifies the Internet-to-Ethernet and Internet-to-Fibre Channel address translation tables used by the Address Resolution Protocol.
LAN Resources HP-UX Manual Reference Pages • netstat(1M) provides network statistics and information about network connections. • nettladm(1M) captures and controls network tracing and logging information. • nettl(1M) controls network tracing and logging. • ping (1M) verifies network connectivity through the Network Layer and reports round-trip time of communications between the local and remote hosts.
LAN Resources Logging and Tracing Messages Logging and Tracing Messages HP LAN/9000 comes with an online message catalog that reports LAN problems, probable causes, and actions for you to take to correct the problems. Messages are sent either to the system console or log files based on the logging and tracing configuration. To view the probable cause and action text of the message, use the netfmt command with the -v option. Below is an example. # netfmt -v -f /var/adm/nettl.
LAN Resources Auto-Port Aggregation Auto-Port Aggregation HP APA (J4240AA) increases a user’s efficiency by grouping or aggregating up to four ports into a single link having a single IP address. The number of link aggregates allowed per computer is 50. The aggregated connections are IEEE 802.3-compliant (IEEE 802.3u, 802.3z, 802.3ab, and 802.3ad) and can be either HSC, HP-PB, or PCI 10 or 100 Mbits/s Ethernet or Gigabit Ethernet. This product offers full APA functionality on HP-UX Release 11.
LAN Resources VLAN or Virtual LAN VLAN or Virtual LAN VLANs are literally virtual LANs. A LAN can be defined as a network connecting devices inside a single building or inside the buildings close to each other. Typically, LANs are used to isolate broadcast domains for better performance and manageability. VLAN technology, on the other hand, allows us to separate the logical connectivity from physical connectivity.
LAN Resources VLAN or Virtual LAN • A single physical link can simultaneously serve several IP subnets when subnet-based VLANs are configured on that link. • Workgroups requiring increased security can be logically connected within the same broadcast domain. Broadcast traffic will be isolated within the secure group. • End-stations using VLANs can offer rudimentary class of service (CoS) locally by prioritizing traffic for certain activities.
LAN Resources Contacting Your HP Representative Contacting Your HP Representative If you do not have a service contract with HP, you may follow the procedure described below, but you will be billed accordingly for time and materials. If you have a service contract with HP, document the problem as a Service Request (SR) and forward it to your HP representative. Include the following information where applicable: • A characterization of the problem. Describe the events and symptoms leading up to the problem.
LAN Resources Contacting Your HP Representative • Create copies of any Internet Services or LAN/9000 link trace files that were active when the problem occurred for your HP representative to further analyze. • In the event of a system failure, obtain a full memory dump. If the directory /var/adm/crash exists, the HP-UX utility /usr/sbin/savecore automatically executes during reboot to save the memory dump.
LAN Resources Contacting Your HP Representative 120 Chapter 5
6 Network Addressing This chapter introduces network addressing concepts. It contains the following sections: • Overview of Network Addressing Schemes.
Network Addressing • Networking Terminology. • Network Addresses and Node Names. • Internet Addresses. • IP Multicast Addresses. • Subnet Addresses. • Configuring Gateway on Fixed-Length Subnets. • Variable-Length Subnet Addressing. • Configuring Gateway on Variable-Length Subnets. • CIDR - Classless Inter-Domain Routing.
Network Addressing Overview of Network Addressing Schemes Overview of Network Addressing Schemes With HP-UX 11i Release, Hewlett-Packard offers several types of addressing schemes. Table 6-1 below shows the advantages and disadvantages of each type of scheme.
Network Addressing Overview of Network Addressing Schemes NOTE If you are already using the fixed-length addressing scheme and do not need extra addressing space, then it is recommended that you not convert your network to one of the new addressing schemes. Refer to the “Subnet Addresses” subsection for information on fixed-length and variable-length addressing.
Network Addressing Networking Terminology Networking Terminology Following are descriptions of important networking terms. Nodes A node is a computer on the network. Local node (or host) refers to the computer or host to which your terminal is physically attached. A remote node is a computer on the network with which your local node can communicate. A remote node does not have to be directly attached to your terminal.
Network Addressing Networking Terminology You must configure the initial interface for a card/encapsulation type before you can configure subsequent interfaces for the same card/encapsulation type. For example, you must configure lan0:0 (or lan0) before you configure lan0:1 and lan0:2. Once you have configured the initial interface, you can configure the subsequent interfaces in any order. Note that the IP addresses assigned to a card may be on the same subnet or on different subnets.
Network Addressing Networking Terminology ARP Cache Each interface card on a system is identified by an IP address and a station address. The ARP cache contains the IP address of a remote interface and the station address which is used to send packets to that IP address. If the remote system is not on the same physical network, the station address in the ARP cache is for an interface on a gateway.
Network Addressing Network Addresses and Node Names Network Addresses and Node Names Several types of names and addresses are used in networking software. This can be confusing to first-time users. Table 6-2 illustrates which address type is used by each layer of the OSI model. A description of each address type and how it is used by LAN and the services which run on it follows inTable 6-3 . Refer to “Network and System Names” on page 54 for additional information on how these names are assigned.
Network Addressing Network Addresses and Node Names Table 6-3 Address Type link level address Network Address Types, Descriptions, and Examples Description Also referred to as MAC address or station address. A link level address is the unique address of the LAN interface card. This value can be configured in SAM and lanadmin. Recorded In Used By Interface card; can be changed in /etc/rc.config.d /hpbtlanconf file. Refer to Table 3-3 for correct filename.
Network Addressing Network Addresses and Node Names Table 6-3 Network Address Types, Descriptions, and Examples Address Type network address Description Recorded In Also, network number. /etc/networks. The network address is the network portion of an internet address that represents the local network on which a host exists. The network address is the same for all nodes on that network. Refer to “Internet Addresses” in this chapter for a definition of Internet address classes.
Network Addressing Network Addresses and Node Names Table 6-3 Address Type port address Network Address Types, Descriptions, and Examples Description Also referred to as TCP port number, UDP port number, or simply port. Recorded In Used By /etc/services. Service requests. Displayed by netstat -an. Socket address variables. Interprocess communication.
Network Addressing Network Addresses and Node Names Table 6-3 Network Address Types, Descriptions, and Examples Address Type system name Description Also referred to as the system host name and system node name. Recorded In Used By /etc/rc.config.d /netconf (as HOSTNAME variable). uucp facilities. /etc/hosts ; /etc/hosts.equiv (optional); $HOME/.rhosts (optional) ; $HOME/.netrc (optional) ; /usr/adm/inetd.s ec (optional) . All Internet Services and VT3K.
Network Addressing Internet Addresses Internet Addresses Internet addresses are used extensively by LAN and WAN products as well as Internet Services. An internet address (often referred to as the IP address) consists of two parts: • Network address. • Host address. The network address identifies the network. The host address identifies a node within the network. A network address is concatenated with a host address to form the internet address and to uniquely identify a node within a network.
Network Addressing Internet Addresses Figure 6-1 Internet Address Classes 31 23 Class A 0 0 Network Address Host Address Class B 31 30 15 0 1 0 Network Address Host Address Class C 31 29 7 0 1 10 Network Address Host Address The address classes can also be broken down by address ranges. Internet addresses are typically represented by converting the bits to decimal values an octet (8 bits) at a time, and separating each octet's decimal value by a period ( . ).
Network Addressing Internet Addresses Table 6-4 Internet Address Classes Class Nodes per Network Networks 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 To determine a network address and host address from an internet address, you must separate the network and host address fields. For example, the bit representation of internet address 192.6.1.
Network Addressing Internet Addresses Assigning Network Addresses To assign network addresses, follow these rules: • You must have a network address for each logical network. • If your system is attached to more than one physical network via a gateway, the network addresses of these interfaces may not be the same. Refer to Table 6-3 below for a gateway example. • All nodes in the same network, however, must have the same network address. • Do not assign the network addresses 0 or 255 (Class A), 0.0 or 255.
Network Addressing Internet Addresses NOTE Do not assign the host addresses 0.0.0 or 255.255.255 (Class A), 0.0 or 255.255 (Class B), or 0 or 255 (Class C) to any nodes; these addresses are reserved. IP Address for Loopback Interface (lo0) The loopback interface (lo0) is automatically configured when the system boots with the TCP/IP software. The loopback interface is really a “pseudo-device,” since there is no hardware card associated with it.
Network Addressing IP Multicast Addresses IP Multicast Addresses IP multicasting provides a mechanism for sending a single datagram to a group of systems. Generally, only systems that have joined the multicast group process the datagrams. Multicast datagrams are transmitted and delivered with the same “best effort” reliability as regular unicast IP datagrams. The datagrams are not guaranteed to arrive intact at all members of the destination group or in the same order as the datagrams were sent.
Network Addressing IP Multicast Addresses multicast address 01-00-5E-00-00-00 (hex). Ethernet multicast addresses can be in the range 01-00-5E-00-00-01 through 01-00-5E-7F-FF-FF. NOTE Several IP multicast addresses may share the same Ethernet multicast address because the IP multicast address has 28 significant bits. Multicast Routing Multicast datagrams are sent through the interface associated with the default route.
Network Addressing Subnet Addresses Subnet Addresses Subnetting is an optional addressing scheme that allows you to partition the host address portion of an internet address into discrete subnetworks. This allows you to have multiple physical networks without requiring you to obtain multiple network addresses. The physical networks are connected via gateways.
Network Addressing Subnet Addresses Figure 6-5 Internet Address 192.6.12.33 ANDed with Subnet Mask 255.255.255.224 255 Subnet Mask . 255 . 255 . 224 1 1 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 values in mask (00000) AND 192 . 6 . 12 . 33 Internet Address 1 1 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 1 1 0 0 0 0 1 0 0 0 0 1 overwrite value of 1 (00001) in IP address 192 . 6 . 12 .
Network Addressing Subnet Addresses release Hewlett-Packard systems now support variable-length subnet addressing. The advantages of using variable-length subnet addressing over fixed-length subnet addressing include the following: • Allows the local administrator to easily increase/decrease the size of individual subnets when variable-length subnet addressing is used in conjunction with a non-contiguous numbering system (and/or ranges of numbers for each subnet that are non-contiguous).
Network Addressing Subnet Addresses Figure 6-6 Subnet Address and Subnet Number of Class C Internet Address 192.6.12.33 Class C IP Address: 192 . 6 . 12 . 33 1 1 0 0 0 0 0 0 0 0 00 0 1 1 0 0 0 0 0 1 1 0 0 0 0 1 0 0 0 0 1 network address = 192.6.12 subnet number = 1 host address = 33 subnet address = 192.6.12.32 The following rules apply when choosing a subnet addressing scheme and an internet address: • All subnets on the same network must have the same network address.
Network Addressing Subnet Addresses A or Class B network. Assigning a Fixed-Length Subnet Mask Subnet addressing is implemented by specifying a 32-bit subnet mask in the ifconfig command or the netconf file when a LAN interface card is assigned an internet address. All nodes on a subnet must have the same subnet mask. Under the fixed-length subnet address scheme, all subnets on a network, must have the same subnet mask.
Network Addressing Subnet Addresses Table 6-5 Subnet Address (dot notation) Fixed-Length Subnet Addressing (Subnet Mask 255.255.255.224) 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.
Network Addressing Subnet Addresses Figure 6-8 Network Map for Subnetting R & D Dept. (Subnet 3) Marketing Dept. (Subnet 2) lan 1:0 192.6.12.97 lan1 192.6.12.65 C lan0:1 lan0:0 192.6.12.37 192.6.12.34 lan0 192.6.12.35 (Gateway) D A lan0 192.6.12.33 Facility LAN (Subnet 1) lan 1:1 192.6.12.98 lan0 192.6.12.36 B lan1 192.6.12.130 Manufacturing Dept. (Subnet 4) lan1 192.6.20.1 (network 192.6.20) Corporate Offices Summary network information: Company division network = 192.6.12 Subnet mask: 255.255.
Network Addressing Subnet Addresses Configuring Hosts on Fixed-Length Subnets Using the netconf file There are two ways to configure a subnet mask: • Use SAM to configure the subnet mask. • Use the ifconfig(1M) command. These changes will disappear, however, when the system reboots. To set a subnet mask, you may either include it in the SUBNET_MASK variable in the netconf file or the ifconfig command.
Network Addressing Subnet Addresses INTERFACE_NAME[3]=”lan1:1” IP_ADDRESS[3]=”192.6.12.98” SUBNET_MASK[3]=”255.255.255.224” Host D: INTERFACE_NAME[0]=”lan0” IP_ADDRESS[0]=”192.6.12.35” SUBNET_MASK[0]=”255.255.255.224” INTERFACE_NAME[1]=”lan1” IP_ADDRESS[1]=”192.6.20.1” SUBNET_MASK[1]= 255.255.255.0 In addition, every other host on each subnetwork would require the subnet mask 255.255.255.224 in their netconf file entries.
Network Addressing Subnet Addresses Figure 6-9 Network Map I Marketing Dept. (Subnet 2) A1 R & D Dept. A2 192.6.12.67 C1 C2 192.6.12.99 192.6.12.66 lan1 192.6.12.65 lan1:1 192.6.12.98 lan1:0 192.6.12.97 C A lan0:0 192.6.12.34 lan0 192.6.12.33 lan0 192.6.12.36 Facility LAN (Subnet 1) 192.6.12.98 lan0:1 192.6.12.37 lan0 192.6.12.35 B D Gateway lan1 192.6.20.1 (network 192.6.20) lan1 192.6.12.130 192.6.12.132 192.6.12.131 B1 RS232 Modem SLIP Div3 lan1 192.6.20.3 B2 192.1.1.
Network Addressing Subnet Addresses Table 6-6 Network Map I Worksheet Host Interface Alias Internet Address Station Address Cnode Type A1 mkt_a1 192.6.12.67 080009005201 Client 1 A2 mkt_a2 192.6.12.66 080009003001 Client 2 B mfg_32 mfg_128 192.6.12.36 192.6.12.130 080009005201 080009000C24 N/A B1 mfg__b1 b1_slip 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.
Network Addressing Configuring Gateways on Fixed-Length Subnets Configuring Gateways on Fixed-Length Subnets Besides using the appropriate subnet masks, each gateway needs to be configured so that it can properly route messages among the several subnetworks. Following are descriptions of two types of routing: explicit routing and dynamic routing. When using explicit routing, you must specify the IP address of each gateway to which you are directly connected.
Network Addressing Configuring Gateways on Fixed-Length Subnets ROUTE_DESTINATION[0]=”default” ROUTE_GATEWAY[0]=”192.6.12.35” ROUTE_COUNT[0]=”1” Host D (Site gateway): ROUTE_DESTINATION[0]=”net 192.6.12.64” ROUTE_GATEWAY[0]=”192.6.12.33” ROUTE_COUNT[0]=”1” ROUTE_DESTINATION[1]=”net 192.6.12.128” ROUTE_GATEWAY[1]=”192.6.12.36” ROUTE_COUNT[1]=”1” ROUTE_DESTINATION[2]=”net 192.6.12.96” ROUTE_GATEWAY[2]=”192.6.12.34” ROUTE_COUNT[2]=”1” ROUTE_DESTINATION[3]=”default” ROUTE_GATEWAY[3]=”192.6.20.
Network Addressing Configuring Gateways on Fixed-Length Subnets ARP server on the 192.6.20 network. If one does not exist, additional indirect route entries can be configured for each gateway that is directly connected to the 192.6.20 network. For example, referring to Figure 6-9, you might add the following indirect routes on Host D to send messages to Division 2 and Division 3. ROUTE_DESTINATION[4]=”net 192.6.14” ROUTE_GATEWAY[4]=”192.6.20.2” ROUTE_COUNT[4]=”1” ROUTE_DESTINATION[5]=”net 192.6.
Network Addressing Variable-Length Subnet Addressing Variable-Length Subnet Addressing For the most efficient use of address space and maximum flexibility in increasing/decreasing the size of your subnets, Hewlett-Packard recommends variable-length subnet addressing. To maximize the possibilities offered with this new approach, you should utilize mirror image counting, as described in this section, to select subnet numbers.
Network Addressing Variable-Length Subnet Addressing Figure 6-11 Entire Host Field Allocated subnet field host field 0s 1s & 0s 1s & 0s subnets can grow here To alleviate this restrictive situation, when you use the variable-length subnetting approach, you can, alternatively, assign subnet numbers from the left of the subnet field and work right. This is implemented using mirror-image counting.
Network Addressing Variable-Length Subnet Addressing Figure 6-12 Mirror Image Subnet and Host Field Allocation subnet field 1s & 0s host field 0s 1s & 0s Both hosts and subnets can grow here. In this case, both the host field and subnet field have considerably more growing space than before, although the combined growing space is the same.
Network Addressing Variable-Length Subnet Addressing Figure 6-13 Example of Variable-Length Subnet Mask Predetermined boundary Class C Subnet Mask: 255 . 255 . 255 . 240 1 1 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 network address subnet portion of host address growth portion of host address host portion of host address The example below shows how the bits might look in the host address portion of a Class C address in a network with four subnets using variable-length subnetting.
Network Addressing Variable-Length Subnet Addressing Table 6-9 Subnet Subnets with Subnet Mask (B) Modified 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 Notice that these additions caused A to change its leftmost g-bit into a subnet-bit (“s” bit).
Network Addressing Variable-Length Subnet Addressing network along with the netconf entries necessary to configure these subnetworks with variable-length subnet masks. Note that there are four different subnet masks used in this network. Also note that the subnet numbers in the network map correspond to the mirror image subnet numbers listed in Table 6-7. Figure 6-14 Network Map with Variable-Length Subnets Marketing Dept. (Subnet 1) 192.6.12.64, 255.255.255.192 R & D Dept. (Subnet 6) 192.6.12.
Network Addressing Variable-Length Subnet Addressing Table 6-11 Variable-Length Subnet Addressing in a Class C Network Subnet Mask 255.255.255 248 192 128 224 240 NOTE Mirror Image Subnet Number Subnet Number 16 1 (10000) (00001) 1 2 (01) (10) 1 2 (01) (10) 6 3 (110) (011) 2 4 (0010) (0100) Subnet Address Internet Address Range n.n.n.128 n.n.n.129 - n.n.n.134 n.n.n.64 n.n.n.65-n.n.n.126 n.n.n.0 n.n.n.1-n.n.n.126 n.n.n.129-n.n.n.254 n.n.n.192 n.n.n.193-n.n.n.222 n.n.n.
Network Addressing Variable-Length Subnet Addressing Subnet number: 1 Mirror image subnet number: 2 Subnet address: 192.6.12.64 Host address range: 65 to 126 Host A internet address: 192.6.12.65 for network interface lan1 Networking LAN subnet Subnet mask: 255.255.255.128 Subnet number: 17 Mirror image subnet number: 2 Subnet address: 192.6.12.0 Host address range: 1 to 126 and 129 to 254 Host A internet address: 192.6.12.1 for network interface lan0 Host B internet address: 192.6.12.
Network Addressing Variable-Length Subnet Addressing Figure 6-15 Network Map II Marketing Dept. (Subnet 1) A1 R & D Dept. (Subnet 6) A2 C1 192.6.12.66 255.255.255.192 192.6.12.67 255.255.255.192 lan1 A C lan0 192.6.12.131 255.255.255.248 lan0 lan0 B lan1 192.6.12.130 255.255.255.248 192.6.12.132 255.255.255.248 D 192.6.12.33 255.255.255.240 B1 192.6.20.1 255.255.255.0 (network 192.6.20) lan1 lan1 Div3 192.6.12.35 255.255.255.240 192.6.12.34 255.255.255.240 192.6.12.193 255.255.255.
Network Addressing Variable-Length Subnet Addressing Table 6-12 Network Map II Worksheet Interface Alias Host 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 Client 1 A2 mkt_a2 192.6.12.66 255.255.255.192 Client 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_ship 192.6.12.34 192.1.1.2 255.255.255.
Network Addressing Configuring Gateways on Variable-Length Subnets Configuring Gateways on Variable-Length Subnets Besides using the appropriate subnet masks, each gateway needs to be configured so that it can properly route messages among the several subnet works. Following are descriptions of two types of routing: explicit routing and dynamic routing. When using explicit routing, you must specify the IP address of each gateway to which you are directly connected.
Network Addressing Configuring Gateways on Variable-Length Subnets Hosts A, B and C: ROUTE_DESTINATION[0]=”default” ROUTE_GATEWAY[0]=”192.6.12.132” ROUTE_COUNT[0]=”1” Host D (Site gateway): ROUTE_DESTINATION[0]=”net 192.6.12.64” ROUTE_MASK[0]=”255.255.255.192” ROUTE_GATEWAY[0]=”192.6.12.129” ROUTE_COUNT[0]=”1” ROUTE_DESTINATION[1]=”net 192.6.12.192” ROUTE_MASK[1]=”255.255.255.224” ROUTE_GATEWAY[1]=”192.6.12.130” ROUTE_COUNT[1]=”1” ROUTE_DESTINATION[2]=”net 192.6.12.32” ROUTE_MASK[2]=”255.255.255.
Network Addressing Configuring Gateways on Variable-Length Subnets Proxy ARP Server The default direct route entry on Host D assumes that there is a proxy ARP server on the 192.6.20 network. If there is none, additional indirect route entries can be configured for each gateway that is directly connected to the 192.6.20 network. For example, referring to Figure 6-15, you might add the following indirect routes to send messages to Division 2 and Division 3. ROUTE_DESTINATION[4]=”net 192.6.
Network Addressing CIDR - Classless Inter-Domain Routing CIDR - Classless Inter-Domain Routing As the Internet has evolved and grown in recent years, it has become clear that it is facing several serious problems. These include: • Exhaustion of the Class B network address space. One fundamental cause of the problem is the lack of a network class of a size that is appropriate for a mid-sized organization.
Network Addressing CIDR - Classless Inter-Domain Routing 255.255.254.0 255 Net Mask . 255 . 254 . 0 1 1 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 values in mask AND 192 . 6 . 13 . 2 Internet Address 1 1 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 1 1 0 1 0 0 0 0 0 0 1 0 overwrite value 1 in network address 192 . 6 . 12 .
Network Addressing CIDR - Classless Inter-Domain Routing Figure 6-17 Network Map for Supernetting A 192.6.14.2 Gs Chapter 6 192.6.14.3 Network (Gateway) 192.6.12.1 255.255.254.0 B Gd 192.6.14.1 192.6.12.2 255.255.254.0 Supernet C 192.6.13.2 255.255.254.
Network Addressing Configuring Gateways on Supernets Configuring Gateways on Supernets If all the hosts and gateways in your networks support variable-length subnet masks, then the gateway configuration of the supernet will be the same as in gateway configuration for variable-length subnets. In Figure 6-17, if you use explicit routing, you may configure the following supernet route on Host A to enable Host A to communicate with any host on supernet 192.6.12 ROUTE_DESTINATION[0]=”net 192.6.
7 LAN Device and Interface Terminology Following is a description of terms used by the I/O subsystem to identify LAN cards and device files associated with LAN cards.
LAN Device and Interface Terminology Interfaces Interfaces HP-UX 11i allows you to configure multiple IP addresses for a single physical interface. This allows a single system to be seen as multiple systems, with multiple IP addresses and host names, even if the system has only one physical interface card. The IP addresses assigned to a card can generally be on the same subnet or on different subnets. Logical interfaces are also used when an interface card is used for both IP/Ethernet and IP/IEEE802.
LAN Device and Interface Terminology Interfaces initial interface, you can configure subsequent interfaces in any order.
LAN Device and Interface Terminology RARP Configuration RARP Configuration RARP (Reverse Address Resolution Protocol, RFC 903) configuration is an optional addressing scheme in which a freshly booted system queries a network server for the IP address of its own networking interface. For example, if you have a large installation with many nodes, you can centralize the IP address database onto a system that serves as a RARP server.
LAN Device and Interface Terminology RARP Configuration appropriate entry can be added to the server database. Setting Up a RARP Server A system is set up to be a RARP server when the RARPD variable in /etc/rc.config.d/netconf is set to 1. Usually, this variable is set to 0 so that a RARP server is not started. This can be done with a text editor such as vi. This will cause /usr/sbin/rarpd to be started at boot time. Another file which must be modified is /etc/rarpd.conf.
LAN Device and Interface Terminology RARP Configuration 176 Chapter 7
Index Symbols $HOME/.netrc, 132 $HOME/.rhosts, 132 /etc/hosts, 55, 129, 130, 132 creating, 54 editing manually, 54 editing with SAM, 37 permissions, 56 purpose of, 54 sample entry, 56 syntax, 55 /etc/hosts.equiv, 132 /etc/networks, 130 editing manually, 58 permissions, 60 purpose of, 58 sample entry, 60 syntax, 59 /etc/protocols editing manually, 60 permissions, 61 purpose of, 60 syntax, 60 /etc/rc.config.
Index network address, 133 reconfiguring, 40 subnetting, 140 Interprocess communication, 131 IP address See Internet address, 33 K Kernel and /stand/system file, 43 creating, 43 L LAN card configuring, 34 initializing, 34 LAN network interface, power-up, 36 LAN/9000 device terminology, 171 preinstalled, 26 lanadmin(1M) interface card statistics, 71 NMID, 71 status display, 71 status value definitions, 72 lanscan(1M), 26 manpage, 112 NMID, 39 linkloop(1M), 112 NMID, 39 Loading software, 28 Logging messages,
Index S SAM See System Administration Manager, 33 shutdown(2M), 30 Software configuring with SAM, 34 loading with swinstall, 28 Station address, 129 Subnet addressing, 140, 142 configuring gateways, 148, 151, 164 example, 145, 158 fixed-length addressing, 123, 144 variable-length addressing, 47, 48, 123, 154 Supernet addressing, 123, 167 configuring gateways, 170 swinstall(1M), 28 System Administration Manager configuring LAN cards, 34 configuring network connectivity, 37 description of, 33 initializing LA
