HP-UX IPv6 Transport Administrator’s Guide for TOUR 2.0 HP-UX 11i v2 Manufacturing Part Number : 5990-7278 April 2004 United States © Copyright 2004 Hewlett-Packard Development Company L.P. All rights reserved.
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.
Contents About This Document 1. Features Overview TOUR 2.0 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IPv6 Transport (bundled as part of TOUR 2.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP-UX 11i v2 IPv6 Transport Features Available with TOUR 2.0 . . . . . . . . . . . . . . . HP-UX 11i v2 IPv6 Transport Features Available since HP-UX 11i v2 (not new to TOUR 2.0 release). . . . . . . . . . . . . . . . . . . . .
Contents Activating netconf-ipv6 file Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example ifconfig and route Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Host Names and IPv6 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating the /etc/hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Name and Address Lookup for IPv6 . . . . . . . . . . .
Contents Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Network Interface Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 7. IPv6 Software and Interface Technology Name and Address Lookup for IPv6 . . . . . . . . . . . . . . . . . . .
Contents vi
About This Document This document describes how to install, configure, and troubleshoot HP-UX 11i v2 IPv6 transport bundled as part of TOUR (Transport Optional Upgrade Release) 2.0. The document printing date and part number indicate the document’s 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 document part number will change when extensive changes are made.
Publishing History Table 1 Publishing History Details Document Manufacturin g Part Number Title Operating Systems Supported Publication Date 5990-7278 HP-UX IPv6 Transport Administrator’s Guide for TOUR 2.0 (HP-UX 11i v2) HP-UX 11i v2 with TOUR 2.
Chapter 7 IPv6 Software and Interface Technology discusses IPv6 deployment and migration. Appendix A IPv6 ndd Tunable Parameters: provides a list of supported ndd IPv6 tunable parameters that allow for advanced performance tuning. If you are unfamiliar with IPv6 networking concepts, refer to Chapter 6, “IPv6 Addressing and Concepts,” on page 55 and Chapter 7, “IPv6 Software and Interface Technology,” on page 69, before configuring IPv6 interfaces.
Table 3 IPv6 RFCs Supported RFCs Description RFC 1981 Path MTU Discovery for IPv6 *RFC 2292 Advanced Sockets API for IPv6 RFC 2373 IPv6 Addressing Architecture RFC 2374 IPv6 Aggregatable Global Unicast Address Format RFC 2375 IPv6 Multicast Address Assignments RFC 2452 IPv6 MIB for TCP RFC 2454 IPv6 MIB for UDP RFC 2460 IPv6 Specification RFC 2461 Neighbor Discovery for IPv6 RFC 2462 IPv6 Stateless Address Autoconfiguration RFC 2463 ICMPv6 for IPv6 Specification RFC 2464 Transmiss
• * Advanced Socket API features from RFC 2292bis, such as Routing Header, Hop-by-Hop, and Destination Option processing are also supported. The inet6_rth_*() and inet6_opt_*() functions provide these features. The inet6_rth_*() and inet6_opt_*() functions are in /usr/lib/libipv6.1.
HP Welcomes Your Comments HP welcomes your comments concerning this document. We are truly committed to providing documentation that meets your needs. Please send comments to: netinfo_feedback@cup.hp.com Please include document title, manufacturing part number, and any comment, error found, or suggestion for improvement you have concerning this document. Also, please include what we did right so we can incorporate it into other documents.
1 Features Overview This chapter provides an overview of TOUR 2.0 and a features summary of HP-UX 11i v2 IPv6 transport in TOUR 2.0.
Features Overview TOUR 2.0 Overview TOUR 2.0 Overview Transport functionality is typically delivered as part of HP-UX. TOUR (Transport Optional Upgrade Release) is an additional, fully supported product bundle, available from the web, which delivers new transport functionality and other networking functionality independent of major HP-UX releases. Later versions of TOUR completely supersede previous TOUR versions. All features available in a TOUR release will be rolled into a later HP-UX release. TOUR 2.
Features Overview IPv6 Transport (bundled as part of TOUR 2.0) IPv6 Transport (bundled as part of TOUR 2.0) IPv6 is the next generation Internet Protocol. The IPv6 protocol is also referred to as "IPng" (IP next generation). It provides the infrastructure for the next wave of Internet devices, such as PDAs, mobile phones and appliances. It also provides greater connectivity for existing devices such as laptop computers.
Features Overview IPv6 Transport (bundled as part of TOUR 2.0) For more information on InfiniBand and the IPoIB protocol, refer to the HP-UX InfiniBand Support Guide available at http://www.docs.hp.com/hpux/netcom/index.html#InfiniBand. • Multicast Listener Discovery (MLD) Support (Host Portion Only): The host part of Multicast Listener Discovery (MLD) protocol for IPv6 based on RFC 2710 “Multicast Listener Discovery (MLD) for IPv6”, is supported.
Features Overview IPv6 Transport (bundled as part of TOUR 2.0) RFC 2473 - Packet Tunneling in IPv6 RFC 2893 - Transition Mechanisms for IPv6 Hosts and Routers RFC 3056 - Connection of IPv6 Domains via IPv4 Clouds IMPORTANT As a result of supporting RFC 2893, tunnel configuration on HP-UX 11i v2 IPv6 bundled as part of TOUR 2.0, requires specific changes from tunnel configurations on base (default) HP-UX 11i v2.
Features Overview IPv6 Transport (bundled as part of TOUR 2.0) — HP-UX server can be configured as a “6to4” router: Starting with TOUR 2.0, the HP-UX server can perform the role of a router in a “6to4” configuration. Prior to TOUR 2.0, the HP-UX server was only able to perform the role of a host in a “6to4” configuration. — IP6-in-IP6 and IP-in-IP6 Support: Starting with TOUR 2.0, two additional tunneling types are supported, IP6-in-IP6 and IP-in-IP6.
Features Overview IPv6 Transport (bundled as part of TOUR 2.0) • IPv6/IPv4 Dual Stack support: HP-UX 11i v2 IPv6 supports both IPv4 and IPv6 applications. Programmers can write IPv6 applications that communicate with both IPv6 and IPv4 peers. Existing IPv4 applications do not need to be modified. • IPv6 tunneling enables IPv6/IPv4 hosts and routers to connect with other IPv6/IPv4 hosts and routers over the existing IPv4 network. IPv6 tunneling encapsulates IPv6 datagrams within IPv4 packets.
Features Overview Limitations Limitations The following section describes limitations of HP-UX 11i v2 IPv6 in TOUR 2.0 transport. These limitations also exist in base (default) HP-UX 11i v2 IPv6 transport. setparms Not Enhanced for IPv6 Configuration On HP-UX 11i v2, the setparms utility has not been enhanced to support IPv6 configuration.
2 Installation This chapter discusses the following topics related to installing TOUR 2.
Installation NOTE • Installing TOUR 2.0 • Verifying the TOUR 2.0 installation • Removing (Un-installing) TOUR 2.0 For additional information on TOUR 2.0 components, features and installation, refer to the Transport Optional Upgrade Release (TOUR) 2.0 Release Notes located at http://www.docs.hp.com/hpux/netcom/index.html#IPv6. If you have already completed your installation of TOUR 2.0, you may skip this chapter and proceed to Chapter 3, “Configuration,” on page 19.
Installation System Requirements System Requirements This section lists the resources needed and the software requirements for installing and running TOUR 2.0 on HP-UX 11i v2. Supported Operating Systems TOUR 2.0 is supported on the following 32- or 64-bit systems: • HP-UX 11i Version 1.0 (B.11.11) PA-RISC servers • HP-UX 11i Version 2.0 (B.11.23) Intel Itanium servers Minimum System Resources for HP-UX 11i v2 HP-UX 11i v2 TOUR 2.
Installation System Requirements You can retrieve patches from http://www.itrc.hp.com.
Installation Installing TOUR 2.0 Installing TOUR 2.0 This section includes information on obtaining and installing TOUR 2.0. It includes information needed before and after the TOUR 2.0 installation. NOTE TOUR 2.0 is not compatible with some versions of IPSec. Before installing TOUR 2.0, refer to the section titled “TOUR 2.0 and IPSec” on page 15 of this guide. Installation Instructions To install TOUR 2.0, complete the following steps: Step 1.
Installation Installing TOUR 2.0 swinstall -x autoreboot=true -s /tmp/TOUR.depot TOUR Notice that the target selection specified in the swinstall example is “TOUR”, not “TOUR2”,since the TOUR 2.0 product bundle name is “TOUR”. The product bundle version reflects the version change from 1.0 to 2.0. The Mobile IPv6 product is optional. If you do not want to install Mobile IPv6, use interactive swinstall and deselect the Mobile IPv6 product.
Installation Installing TOUR 2.0 ERROR: The Transport Optional Upgrade Release (TOUR) is already installed. HP-UX cumulative ARPA Transport patches can NOT be removed because removing them would corrupt TOUR. If you must remove this patch PHNE_nnnnn, then first remove TOUR. If you attempt to install or remove a PPP patch, similar messages are displayed. TOUR 2.0 and IPSec TOUR 2.0 is only compatible with, and is a software requirement for, (when available) IPSec (J4256AA) version A.02.00 or greater.
Installation Verifying the TOUR 2.0 Installation Verifying the TOUR 2.0 Installation Use the following steps after swinstall finishes installing TOUR 2.0 to verify that the installation was successful: Step 1. Examine the following log files for error messages: • /var/adm/sw/swinstall.log • /var/adm/sw/swagent.log Step 2. Use the swlist -l bundle TOUR command. If TOUR 2.0 installed successfully, the following messages is displayed: TOUR A.02.00 Transport Optional Upgrade Release for B.11.23 Step 3.
Installation Removing (Un-installing) TOUR 2.0 Removing (Un-installing) TOUR 2.0 This section describes how to remove TOUR 2.0. If you need to remove TOUR 2.0, be aware of the following: • The save area under /usr/contrib/TOUR/save_area must be intact (after installing TOUR 2.0, files in this directory must not be removed). • As part of removing TOUR 2.0, the base (default) HP-UX 11i v2 transport software is restored. To remove (un-install) TOUR 2.0, do the following: Step 1.
Installation Removing (Un-installing) TOUR 2.
3 Configuration This chapter summarizes the steps to configure LAN interfaces, assign IPv6 addresses, optionally enabling IPv6 tunneling through IPv4 networks, and assigning host names to IPv6 addresses.
Configuration Configuring IPv6 Interfaces and Addresses The first interface configured on a physical LAN interface is called the primary interface. Additional interfaces configured on the same physical device are called secondary interfaces. You must configure an IPv6 primary interface to use IPv6 over that interface. Configuring IPv6 Interfaces and Addresses This section describes IPv6 interface and address configuration tasks that involve editing the /etc/rc.config.d/netconf-ipv6 file.
Configuration Stateless Autoconfiguration Configure IPv6 interfaces and routing using one of the following methods: • Stateless autoconfiguration • Manual configuration These methods are described in the following sections. Stateless Autoconfiguration Addresses on IPv6 interfaces, unlike IPv4 interfaces, can be configured without manual intervention.
Configuration Stateless Autoconfiguration Again, in the above example, the address is automatically assigned. Note that autoconfiguration is not mandatory, manual specification of the address is also allowed and is described below. Configuring Secondary Interfaces If an IPv6 router that advertises network prefixes resides on the LAN, a secondary interface is automatically configured after the primary interface comes up. IPv6 builds additional secondary interfaces for each network prefix advertised.
Configuration Manual Configuration Manual Configuration The following section describes the manual configuration process for HP-UX 11i v2 IPv6. Configuring a Primary Interface To configure an IPv6 link-local address for a primary interface, edit the IPV6_INTERFACE[0] statement in the /etc/rc.config.d/netconf-ipv6 file to specify the interface name and the interface state, either up or down. The interface name must be the name of the physical interface card, as reported by lanscan.
Configuration Manual Configuration IPV6_SECONDARY_INTERFACE_NAME[1]="lan0:1" IPV6_ADDRESS[1]="2345::5432" IPV6_PREFIXLEN[1]="64" IPV6_SECONDARY_INTERFACE_STATE[1]="up" DHCPV6_ENABLE[1]=0 Always set DHCPV6_ENABLE to 0. For more information about specifying interface names for multiple interfaces, refer to Chapter 6, “IPv6 Addressing and Concepts,” on page 55. Configuring a Default IPv6 Route In the absence of router advertisements, you can add the default IPv6 router information to the /etc/rc.config.
Configuration Manual Configuration — Automatic tunneling using the IPv4-compatible address is not supported. The following sections provides basic examples for configuring an IP6-in-IP tunnel and a “6to4” tunnel. For more information including additional optional tunnel parameters not mentioned in these examples, refer to the /etc/rc.config.d/netconf-ipv6 file and the ifconfig(1M) man page that ship with HP-UX 11i v2 TOUR 2.0. For more information on the tunneling mechanisms supported in TOUR 2.
Configuration Manual Configuration Creating a “6to4” Point-to-Multipoint Configured Tunnel “6to4” offers a point-to-multipoint router-to-router tunneling mechanism for traffic going between IPv6 domains over an IPv4 network. One of the advantages of “6to4” over configured tunneling is that the source router can talk to any other “6to4” router without the need for any manual configuration on the destination router. Thus, “6to4” tunnels do not suffer the scalability problem that configured tunnels do.
Configuration Manual Configuration Required Steps: To configure the HP-UX system to run rtradvd, and enable the Router Advertisement functionality, the following steps must be taken: the /etc/rtradvd.conf file must be edited as needed; the “private” interface flag must be cleared (“-private” for each enabled interface) and the rtradvd daemon must be enabled. More specifically: • Edit the /etc/rtradvd.
Configuration Manual Configuration Activating netconf-ipv6 file Configuration You can activate the netconf-ipv6 configuration in one of the following ways: NOTE • By rebooting the system. • Or alternatively, by executing the ifconfig and route commands, as needed, to make equivalent configuration settings. HP recommends rebooting your system to activate any changes you made to your netconf-ipv6 file.
Configuration Manual Configuration To create an IP6-in-IP tunnel, enter: ifconfig iptu0 inet6 tunnel ip6inip tsrc 192.1.1.1 tdst 192.2.2.2 up To create a “6to4” tunnel, enter: ifconfig iptu0 inet6 tunnel 6to4 2002:f0e:8cc::1 tsrc 15.13.1.2 up NOTE Chapter 3 Remember that configuration using ifconfig and route is ephemeral, and not maintained after a system reboot.
Configuration Host Names and IPv6 Addresses Host Names and IPv6 Addresses The following section provides additional information on how addressing works on HP-UX 11i v2 IPv6 bundled as part of TOUR 2.0.
Configuration Host Names and IPv6 Addresses System name in swinstall screen: host3 /etc/hosts file: 3ffe:ffff:101::230:6eff:fe04:d9ff 192.1.2.34 hpfcrm loghost NOTE host3 host3.site2.region4 HP-UX 11i v2 IPv6 bundled as part of TOUR 2.0 is a dual stack implementation. A single host name can have entries for both an IPv6 address and an IPv4 address in /etc/hosts. Name and Address Lookup for IPv6 /etc/nsswitch.conf (nsswitch.conf(4)) is a configuration file for the name service switch.
Configuration Host Names and IPv6 Addresses ipnodes: dns [NOTFOUND=continue] files Or if /etc/hosts is to be the primary Name Service, the entry would be set as follows: ipnodes: files [NOTFOUND=continue] dns NOTE You can not specify NIS or NIS+ on the ipnodes entry. Manually editing nsswitch.conf If the current system has no nsswitch.conf file, use a text editor to create an /etc/nsswitch.conf file containing one of the following lines, or copy the /etc/nsswitch.defaults file and modify as needed.
4 Troubleshooting This chapter provides guidelines for troubleshooting HP-UX 11i v2 IPv6 bundled as part of TOUR 2.0. It contains a troubleshooting overview and diagnostic flowcharts.
Troubleshooting Troubleshooting Overview Troubleshooting Overview Troubleshooting problems on HP-UX 11i v2 IPv6 bundled as part of TOUR 2.0, can involve a variety of hardware and software components. The problem impacting your system might originate in another part of the network. Because HP-UX 11i v2 IPv6 supports an IPv6/IPv4 Dual Stack, test IPv4 connectivity before testing IPv6 connectivity. Refer to the HP-UX LAN Administrator’s Guide (available at http://www.docs.hp.
Troubleshooting Diagnostic Flowcharts Diagnostic Flowcharts Below is a summary of the types of network tests in the diagnostic flowcharts. To diagnose your problem, first verify the connections and configuration on your system (Flowcharts 1 through 5). If this does not solve your problem, use Flowchart 6 to test and/or verify connectivity with a remote system.
Troubleshooting Diagnostic Flowcharts Flowchart 1: Transport Level Testing using Internet Services Figure 4-1 Flowchart 1 1 A Execute: telnet hostname to remote host B yes Stop Succeeds? no C Connection Refused? yes no D no E F Check for Network Connectivity 2 36 Network Reachable? yes Ensure IPv6 installed on remote node 1 Chapter 4
Troubleshooting Diagnostic Flowcharts Flowchart 1 Procedures A. Execute: telnet to remote host. Try to connect using telnet to a remote host. B. Succeeds? If telnet succeeds, stop. The system connects using TCP over IPv6 through the Transport Layer (OSI Layer 4). C. Connection Refused? Trying to connect to a remote system where HP-UX 11i v2 IPv6 is not installed can cause this message. D. Network Reachable? If it is, go to F, otherwise continue to E. E. Check for Network Connectivity.
Troubleshooting Diagnostic Flowcharts Flowchart 2: Network Connectivity Test Figure 4-2 Flowchart 2 2 A B Execute: ping -f inet6 Execute: -f inet6 to remoteping hostname to remote hostname successful? yes Stop no C Execute: ping -f inet6 to remote IPv6 addr.
Troubleshooting Diagnostic Flowcharts Flowchart 2 Procedures A. Execute ping to remote IPv6 “host name”. Using ping, send an ICMPv6 message to the remote host with which you are having problems connecting. For example, the remote host name is hpindon. Enter: ping -f inet6 hpindon B. ping successful? A message is printed on stdout for each ping packet returned by the remote host. If packets are being returned, your system has network level connectivity to the remote host. C.
Troubleshooting Diagnostic Flowcharts Flowchart 3: Name Service Test Figure 4-3 Flowchart 3 3 A Check nsswitch.conf setting. C B Using DNS? E no yes D Can add Name to DNS Server? F yes Add Entry to DNS Server 2 no Add entry to /etc/hosts, ensure that nsswitch.
Troubleshooting Diagnostic Flowcharts Flowchart 3 Procedures A. Check /etc/hosts and /etc/nsswitch.conf files. If needed, add a missing host name or IPv6 address. If the IPv6 address for the host is in /etc/hosts, ensure that you have an /etc/nsswitch.conf file entry with an appropriate ipnodes policy. For example, ipnodes: DNS [NOTFOUND=continue] files and start again with Flowchart 3. B. Using DNS? If your name and IPv6 address resolution policy use DNS as the primary resolver, go to C.
Troubleshooting Diagnostic Flowcharts Flowchart 4: Interface Test Figure 4-4 Flowchart 4 4 A ifconfig inet6 B D C ifconfig successful ? E Any error message returned? no yes no Correct ifconfig flag settings 4 yes 5 Execute netstat -in to look for LAN card I/O problems 2 yes G F Suspect LAN card I/O problem ? yes H Execute: lanadmin Problem resolved ? no Call HP no 2 42 Chapter 4
Troubleshooting Diagnostic Flowcharts Flowchart 4 Procedures A. Execute: ifconfig inet6. Execute ifconfig on the interface you want to test. For example, to view LAN interface lan0, enter: ifconfig lan0 inet6 B. ifconfig successful? ifconfig succeeds when the output shows an Internet address and the flags: UP, RUNNING, MULTICAST, ONLINK. If successful, go to E, if not continue to C. C. Any error message returned? If ifconfig fails and displays an error message, go to Flowchart 5.
Troubleshooting Diagnostic Flowcharts Flowchart 5: Interface Test continued Figure 4-5 Flowchart 5 5 F A No such interface yes 4 Any other error message B Execute: lanscan same C no Was correct interface name used? 4 Call HP yes D Call HP yes Is Hardware State UP? no E Execute: lanadmin 4 44 Chapter 4
Troubleshooting Diagnostic Flowcharts Flowchart 5 Procedures A. Is error message “No such interface name”? If not, go to F. If so, the interface name passed to ifconfig does not exist on the system. Using lanscan, verify the spelling and names of the interfaces on the system. If the system contains more than one LAN card, make sure the correct number of LAN cards was configured into the kernel and that an ifconfig command was executed for each interface. B. Execute: lanscan.
Troubleshooting Diagnostic Flowcharts Flowchart 6: Router Remote Loopback Test Figure 4-6 Flowchart 6 6 A B Execute: ping from known good host through router to known good remote host ping -f inet6 successful ? 2 yes no C Execute: netstat -rnf inet6 E D Add route entry on local system no Default route to gateway? yes 6 G F Correct Router Configured ? no Change route entry on local system or router yes 6 46 Now try same test from remote node 3 Chapter 4
Troubleshooting Diagnostic Flowcharts Flowchart 6 Procedures A. Execute: ping from known good host through gateway to known good host on remote network. This tests router connectivity to the remote network. For more information on ping, refer to the ping(1M) man page. B. ping successful? If ping -f inet6 succeeded, return to Flowchart 2. If ping -f inet6 failed, the problem may exist in the routing table for the problem host. Continue to C. C. Execute: netstat -rnf inet6.
Troubleshooting Diagnostic Flowcharts 48 Chapter 4
5 Utilities HP-UX 11i v2 IPv6, bundled as part of TOUR 2.0, for the most part uses IPv6-enhanced IPv4 network utilities. This section summarizes the utilities required for administration of HP-UX 11i v2 IPv6 bundled as part of TOUR 2.0.
Utilities Configuration Utilities Configuration Utilities This section describes configuration utilities available to configure HP-UX 11i v2 IPv6 in TOUR 2.0. The ifconfig “inet6” Address Family Use ifconfig to assign an IPv6 address to an interface and configure parameters, such as the network prefix. (In IPv6, prefix replaces netmask.) The ifconfig keyword inet6 required to configure IPv6 interfaces. It is not required to examine IPv6 interfaces. Refer to the ifconfig(1M) man page for details.
Utilities Network Diagnostic Utilities Network Diagnostic Utilities This section lists network diagnostic utilities available for use as part of the process of administering HP-UX 11i v2 IPv6. Chapter 5 • lanadmin(1M) resets or reports status of the LAN card. • lanscan(1M) displays LAN device configuration and status. • ndd(1M) displays and modifies network driver parameters. • ndp(1M) displays and modifies the IPv6 neighbor discovery cache.
Utilities IPv6 Additions to Network Tracing and Logging IPv6 Additions to Network Tracing and Logging Use nettl to trace traffic through IPv6 Subsystems, or use nettladm. Table 5-1 below lists the subsystems available for IPv6 packet tracing. Table 5-1 Network Trace Subsystems Description Subsystem Name IPv6 Packets NS_LS_IPV6 ICMPV6 Packets NS_LS_ICMPV6 IPv6 Loopback packets NS_LS_LOOPBACK6 Use netfmt to format trace records captured by nettl from the IPv6 subsystems.
Utilities 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.
Utilities Contacting Your HP Representative • Create copies of any Internet Services or HP-UX 11i v2 IPv6 for TOUR 2.0 software 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.
6 IPv6 Addressing and Concepts This chapter introduces network addressing concepts for IPv6. It contains sections on Obtaining IPv6 Addresses, IPv6 Address Formats, Neighbor Discovery, Stateless Address Autoconfiguration and some basic general Networking Terminology.
IPv6 Addressing and Concepts Where to Get IPv6 Addresses Where to Get IPv6 Addresses To obtain an IPv6 address, contact a local ISP or the Regional Internet Registries from the following list: ARIN - American IPv6 registration services APNIC- Asia Pacific Network Information Center RIPE - European Regional Internet Registry The amount of addresses allocated varies according to your network requirements.
IPv6 Addressing and Concepts IPv6 Address Formats To indicate a subnetwork address, IPv6 uses subnet prefixes similar to IPv4 CIDR format. Figure 6-1shows a 128-bit IPv6 node address with a 64-bit subnet prefix.
IPv6 Addressing and Concepts IPv6 Address Formats Address Scope Link-local An IPv6 address used on a single link. Global An IPv6 address that uniquely identifies a node on the Internet such that packets can be routed to the node from any other node on the Internet. Address Type Unicast 58 Identifies a single interface.
IPv6 Addressing and Concepts Neighbor Discovery Neighbor Discovery IPv6 hosts and routers use the IPv6 Neighbor Discovery Protocol to: • advertise their link-layer address on the local link • find neighbors’ link-layer addresses on the local link • find neighboring routers able to forward IPv6 packets • actively track which neighbors are reachable • search for alternate routers when a path to a router fails The IPv6 Neighbor Discovery Protocol (ndp) uses ICMPv6.
IPv6 Addressing and Concepts Stateless Address Autoconfiguration Stateless Address Autoconfiguration Stateless address autoconfiguration requires no manual configuration of hosts, minimal configuration of routers, and no additional servers. The primary interface (lanX:0) is automatically assigned a link-local address by the system when the interface is configured. This allows each IPv6 interface to have at least one source address that can be used by Neighbor Discovery.
IPv6 Addressing and Concepts Stateless Address Autoconfiguration Link-Local Address Assigned Automatically A link-local address is formed by prepending the well-known link-local prefix FE80::/10 to the interface identifier which is typically 64 bits long and based on EUI-64 identifiers. Link-local addresses are sufficient for allowing communication among IPv6 hosts attached to the same link.
IPv6 Addressing and Concepts Stateless Address Autoconfiguration 4. Forming a 128-bit link-local unicast address for the primary interface fe80::a00:9ff:fe78:f339 View the configuration by typing ifconfig lan0 inet6 lan0: flags=4800841 inet6 fe80::a00:9ff:fe78:f339 prefix 10 Secondary Interface Autoconfiguration If an IPv6 router on the network advertises network prefixes in router advertisements, IPv6 derives a second IPv6 address based on the interface identifier.
IPv6 Addressing and Concepts Stateless Address Autoconfiguration Figure 6-4 shows a general example of Secondary Interface Autoconfiguration. Figure 6-4 Secondary Interface Autoconfiguration From an IPv6 Router 1. Primary Interface up 2. Router Solicitation IPv6 Router lan0 fe80::a00:9ff:fe78:f339 3. Router Advertisement prefix 3ffe:2000:0:13/64 4. Secondary Interface Autoconfigured lan0:1 3ffe:2220:0:13:a00:9ff:fe78:f339 lan0 fe80::a00:9ff:fe78:f339 1.
IPv6 Addressing and Concepts Stateless Address Autoconfiguration Manual Configuration and Router Advertisements Note that even if a primary interface is manually configured, if the host receives prefixes from router advertisements, then secondary interfaces are autoconfigured. In this case, the addresses on the secondary interfaces are derived from the interface ID portion of the manually specified primary interface address.
IPv6 Addressing and Concepts Stateless Address Autoconfiguration The primary interface (for example, lan1) can then be removed from the system with the ifconfig command, as in the following example: ifconfig lan1 inet6 unplumb A loopback interface does not have a hardware device associated with it. The name of the loopback interface is lo0. A loopback interface is automatically created by the system. You cannot delete it.
IPv6 Addressing and Concepts Networking Terminology Networking Terminology The following are descriptions of some important IPv6 networking terms. Node A node is a device that implements IP on the network. A node can be a host or a router. A local node (or host) is the computer (or host) where you have logged-in. A remote node is a computer on the IP network where you are not logged in. A remote node does not have to be directly attached to your terminal.
IPv6 Addressing and Concepts Networking Terminology The interface name may include a colon (:), followed by an interface index number that denotes the interface number. The interface index number 0 is the first interface number for a card/encapsulation type and is known as the primary interface. The interface name lan0 is equivalent to lan0:0. The syntax is as follows: nameX[:interface-index-number] In the preceding syntax, name is the class of the interface. Valid name is lan (Ethernet LAN).
IPv6 Addressing and Concepts Networking Terminology 68 Chapter 6
7 IPv6 Software and Interface Technology The topics discussed in this section concern IPv6 deployment and migration.
IPv6 Software and Interface Technology Name and Address Lookup for IPv6 Name and Address Lookup for IPv6 It is generally recommended to add IPv6 addresses (known as AAAA records) to a DNS Name Server only when the following conditions are true: • The IPv6 address is assigned to the interface on the node. • The address is configured on the interface. • The interface is on a link which connects to the IPv6 infrastructure.
IPv6 Software and Interface Technology Name and Address Lookup for IPv6 Thus, if DNS has not been set up as the definitive source, and files (/etc/hosts) may need to be used for address and host name resolution, HP recommends adding the following entry to /etc/nsswitch.conf: ipnodes: dns [NOTFOUND=continue] files Or if /etc/hosts is to be the primary Name Service ipnodes: files [NOTFOUND=continue] dns NOTE You can not specify NIS or NIS+ on the ipnodes entry.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 Migrating from IPv4 to IPv6 IPv6 is the next generation Internet protocol and is designed to be a replacement for IPv4. However, it is expected that IPv6 adoption will be gradual and there will be a lengthy transition period during which IPv4 and IPv6 protocols will have to coexist. The IETF (ngtrans working group) has developed a number of transition mechanisms that facilitates IPv6 deployment.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 Tunneling can be used in a variety of ways: • Router-to-Router: IPv6/IPv4 dual stack routers interconnected by an IPv4 infrastructure can tunnel IPv6 packets between themselves. In this case, the tunnel spans one segment of the end-to-end path that the IPv6 packet takes. • Host-to-Router: IPv6/IPv4 dual stack hosts can tunnel IPv6 packets to an intermediary IPv6/IPv4 router that is reachable over an IPv4 infrastructure.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 — Tunnel interface name: This is a local identifier name for each tunnel configured. (It need not be the same on both ends of the configured tunnel.) For IP6-in-IP and “6to4” tunnels this would be iptu<#> (e.g. iptu0, iptu1). For IP6-in-IP6 and IP-in-IP6 tunnels it would be ip6tu<#> (e.g. ip6tu0, ipt6u1). — Tunnel Type: Type of tunnel. Supported tunnels are: “ip6inip”, “6to4”, “ip6inip6”, and “ipinip6”.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 Automatic tunnels are point-to-multipoint tunnels. The IETF is in the process of deprecating automatic tunnels with IPv4-compatible address in favor of “6to4”. For more information on “6to4”, refer to ““6to4” Connecting IPv6 Domains over IPv4 Clouds” on page 78 of this guide. IMPORTANT Starting with TOUR 2.0, automatic tunnels with IPv4-compatible addresses are not supported. These were supported in base (default) HP-UX 11i v2.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 TUN_INTERFACE_NAME[0]=”iptu0” TUN_TYPE[0]=”ip6inip” TUN_LOCAL_ADDRESS[0]=”fe80::1” TUN_REMOTE_ADDRESS[0]=”fe80::2” TUN_ENCAP_SRC_ADDRESS[0]=”192.168.1.1” TUN_ENCAP_DST_ADDRESS[0]=”10.13.2.2” TUN_INTERFACE_STATE[0]=”up” On Host B: — Using ifconfig (ephemeral), enter: ifconfig iptu0 inet6 tunnel ip6inip fe80::2 fe80::1 tsrc 10.13.2.2 tdst 192.168.1.1 up — Editing /etc/rc.config.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 — Using ifconfig (ephemeral), enter: ifconfig ip6tu0 inet6 tunnel ip6inip6 fe80::2 fe80::1 tsrc 3ffe::1 tdst 2ffe::1 up — Editing /etc/rc.config.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 TUN_ENCAP_SRC_ADDRESS[0]=”3ffe::1” TUN_ENCAP_DST_ADDRESS[0]=”2ffe::1” TUN_INTERFACE_STATE[0]=”up” NOTE Refer to the ifconfig(1m) man page and the /etc/rc.config.d/netfconf-ipv6 file for more detailed information on tunneling parameters.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 The “6to4” prefix provides a network prefix for the local IPv6 host or network. The IPv4 address is the endpoint for all external IPv4 connections. Figure 7-2 “6to4” Prefix 0 3 001 16 0x002 2002::/16 48 IPv4 Address SLA ID 74 127 Interface ID 15.1.1.1 2002:0f01:0101::/48 “6to4” Encapsulation IPv6 packets from a “6to4” site are encapsulated in IPv4 packets when they leave the site over its external IPv4 connection.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 Starting with TOUR 2.0, the HP-UX 11i v2 nodes can perform the role of the “6to4” router. Host configuration continues to be supported in TOUR 2.0 (as was the case in base (default) HP-UX 11i v2). Figure 7-3 “6to4” Topology Example 6to4 router IPv4: 15.1.1.1 IPv6 prefix: 2002:0f01:0101::/48 6to4 host IPv6 network R1 R2 IPv6 host IPv6 internet 6to4 relay router IPv4: 16.2.2.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 As shown in the “6to4” topology example of Figure 7-3: 6to4 host: An IPv6 host that has at least one “6to4” address configured. The "6to4" address is autoconfigured using the "6to4" prefix advertised by the "6to4" router. It has a default route to the "6to4" router. All non-local "6to4" addressed packets and native IPv6 packets are sent to the "6to4" router.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 In all three cases, you do not need to explicitly specify the address of the tunnel entry point, as this special "6to4" address will be automatically created based on the globally unique IPv4 address that will be the source address in the encapsulating (outer) header. To configure R1 using the /etc/rc.config.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 Using rtradvd to Advertise “6to4” Routing Prefix This section provides a simple example to show how to advertise “6to4” routing. In this example, the globally unique IPv4 address of the host is 15.13.1.2. #example beginsdefaults { AdvSendAdvertisement on ; }; interface lan0 { prefixinfo 2002:f0d:0101::/64 { }; }; #example ends For more examples, refer to the rtradvd.conf(4) man page.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 84 Chapter 7
A IPv6 ndd Tunable Parameters The following IPv6 tunable parameters allow advanced fine-tuning of HP-UX 11i v2 IPv6 performance.
IPv6 ndd Tunable Parameters Supported IPv6-related ndd parameters Supported IPv6-related ndd parameters To obtain a list of supported IPv6-related ndd parameters, enter: ndd -h supported | grep ip6 NOTE For more information on a specific parameter (if help text is provided for that parameter), enter: ndd -h Table A-1 lists the output received from entering, “ndd -h supported | grep ip6”: Table A-1 Supported IPv6 ndd parameters Parameter Description IPv6: 86 ip6_def_hop_limit - Controls
IPv6 ndd Tunable Parameters Supported IPv6-related ndd parameters Table A-1 Supported IPv6 ndd parameters (Continued) Parameter Description ip6_ire_hash - Displays all IPv6 routing table entries, in the order searched when resolving an IPv6 address ip6_ire_pathmtu_interval - Controls the probe interval for IPv6 PMTU ip6_ire_redirect_interval - Controls IPv6 ‘Redirect’ routing table entries ip6_ire_status - Displays all IPv6 routing table entries ip6_raw_status - Reports IPv6 level RAWIP fanout t
IPv6 ndd Tunable Parameters Supported IPv6-related ndd parameters Table A-1 Supported IPv6 ndd parameters (Continued) Parameter Description ip6_nd_multicast_solicit_ count - Controls the ND MAX_MULTICAST_SOLICIT ip6_nd_probe_delay - Controls the ND DELAY_FIRST_PROBE_TIME ip6_nd_transmit_interval - Controls the ND RETRANS_TIMER ip6_nd_unicast_solicit_ count - Controls the ND MAX_UNICAST_SOLICIT ip6_rd_solicit_count - Controls the ND MAX_RTR_SOLICITATIONS ip6_rd_solicit_delay - Controls the ND M
Index Symbols /etc/hosts, 7, 30, 41, 70, 71 Numerics 6to4, 6, 26, 72, 74, 79, 80, 81, 82 6to4 configured tunnel, 26, 29 A activating configuration changes, 28 address autoconfiguration, 7, 21, 60 address formats, 56 address scope, 58 address type, 58 addressing, 30, 56 anycast address, 58 autoconfiguration, 7, 21, 60 automatic tunneling, 6 C configuration, 7, 20 configuration (manual), 64 configured tunnel, 25, 26 configured tunneling, 5, 73 Contacting HP, 53 D default router information, 24 deployment, 69
Index nfs, 8 nis, 8 nis+, 8 node, 66 NS_LS_ICMPV6, 52 NS_LS_IPV6, 52 NS_LS_LOOPBACK, 52 nsswitch.conf(4), 7, 31, 41, 70 P ping(1M), 7, 39, 47, 51 PPPoe/v6, 2 prefix, 57 prefix length, 57 prerequisite software patches (TOUR 2.0), 11 R removing an interface, 64 removing TOUR 2.0, 17 RFCs, ix route(1M), 7, 20, 28, 47, 50 router, 66 router advertisement, 26 Router Advertisement Daemon, 4 router configuration, 22 rtradvd, 4, 26 rtradvd.
