HP-UX IPv6 Transport Administrator’s Guide for TOUR 1.0 HP-UX 11i Manufacturing Part Number : 5187-4159 E0703 United States © Copyright 2003 Hewlett-Packard Development Company L.P. All rights reserved.
DRAFT COPY 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 1.0 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IPv6 Transport (bundled as part of TOUR 1.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP-UX 11i IPv6 Transport Features New with TOUR 1.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional HP-UX 11i IPv6 Transport Features. . . . .
Contents Troubleshooting Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostic Flowcharts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowchart 1: Transport Level Testing using Internet Services . . . . . . . . . . . . . . . . . Flowchart 2: Network Connectivity Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowchart 3: Name Service Test . . . . . . . . . . . .
Contents Migrating from IPv4 to IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Connecting IPv6 Domains over IPv4 Clouds (6to4) . . . . . . . . . . . . . . . . . . . . . . . . . . 70 A.
Contents vi
About This Document This document describes how to install, configure, and troubleshoot HP-UX 11i IPv6 transport bundled as part of TOUR 1.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 Manufacturing Part Number Title OS Supported/ Release Publication Date 5187-4159 HP-UX IPv6 Transport Administrator’s Guide for TOUR 1.0 HP-UX 11i : TOUR 1.
Appendix A IPv6 ndd Tunable Parameters: provides a list of new ndd Ipv6 tunable paramters that allow for advanced performance tuning. If you are unfamiliar with IPv6 networking concepts, refer to Chapter 6, “IPv6 Addressing and Concepts,” on page 51 and Chapter 7, “IPv6 Software and Interface Technology,” on page 65, before configuring IPv6 interfaces. Related Documents HP Documentation Additional information about HP-UX IPv6 can be found on docs.hp.
Table 2 IPv6 RFCs Supported (Continued) RFCs Description RFC 2460 IPv6 Specification RFC 2461 Neighbor Discovery for IPv6 RFC 2462 IPv6 Stateless Address Autoconfiguration RFC 2463 ICMPv6 for IPv6 Specification RFC 2464 Transmission of IPv6 Packets over Ethernet Networks RFC 2465 MIB for IPv6: Textual Conventions and General Group RFC 2466 MIB for IPv6: ICMPv6 Group RFC 2553 Basic Socket Interface Extensions for IPv6 RFC 2710 Multicast Listener Discovery (MLD) for IPv6 (Host Part) RFC
HP Welcomes Your Comments HP welcomes your comments concerning this document. HP is 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 you like, so we can incorporate it into other documents.
xii
1 Features Overview This chapter provides an overview of TOUR 1.0 and a features summary of HP-UX 11i IPv6 transport for TOUR 1.0.
Features Overview TOUR 1.0 Overview TOUR 1.0 Overview Typically, transport functionality is delivered as part of the HP-UX OS. TOUR (Transport Optional Upgrade Release) is an additional, fully supported product bundle, available from the web, to deliver transport functionality and other networking functionality independently from the major HP-UX releases. All features of a TOUR release will be rolled into a later HP-UX release. New versions of TOUR will completely supersede previous TOUR versions. TOUR 1.
Features Overview IPv6 Transport (bundled as part of TOUR 1.0) IPv6 Transport (bundled as part of TOUR 1.0) IPv6 Overview: 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 1.0) neighboring nodes. This protocol is referred to as Multicast Listener Discovery or MLD. MLD is derived from version 2 of IPv4’s InternetGroup Management Protocol, IGMPv2. One important difference to note is that MLD uses ICMPv6 (IP Protocol 58) message types, rather than IGMP (IP Protocol 2) message types. For more MLD information refer to RFC 2710, “Multicast Listener Discovery (MLD) for IPv6”.
Features Overview IPv6 Transport (bundled as part of TOUR 1.0) forwarding them as needed. IPv6 tunneling eases IPv6 deployment by maintaining compatibility with the large existing base of IPv4 hosts and routers. • Full Ethernet Link Support. • IPv6 Stateless Address Autoconfiguration. • IPv6 Neighbor Discovery (which includes Router Discovery and Duplicate Address Detection). • TCP/UDP over IPv6, PMTUv6, ICMPv6, IPv6 MIBs and Sockets APIs.
Features Overview IPv6 Transport (bundled as part of TOUR 1.0) — telnet — r* commands — name and address resolution resolver routine — inetd.sec over IPv6 The following Internet Services have been IPv6-enhanced (but are not included as part of TOUR 1.0): — WU-FTPD 2.6.1 — Sendmail 8.11.1 — BIND 9.2.0 These IPv6-enhanced products are available separately at www.software.hp.com. Download these web releases if you want to use FTP, Sendmail, or DNS server to handle IPv6 addresses.
2 Installation This chapter briefly describes how to install HP-UX 11i IPv6 bundled as part of TOUR 1.0 on your system.
Installation NOTE • Installation of TOUR 1.0 • Verification of the TOUR 1.0 installation • Verification of IPv6 Loopback The entire TOUR 1.0 bundle must be installed to obtain HP-UX 11i IPv6 as part of TOUR 1.0. In addition to HP-UX 11i IPv6, the TOUR 1.0 bundle also contains: IPv4 transport enhancements and PPP enhancements (PPPoE and PPPv6). For more information on TOUR 1.0 components, features and installation, refer to the TOUR 1.0 Release Notes.
Installation Installing HP-UX 11i IPv6 (bundled as part of TOUR 1.0) Installing HP-UX 11i IPv6 (bundled as part of TOUR 1.0) HP-UX 11i IPv6 is a component of TOUR 1.0. The complete TOUR 1.0 product bundle must be installed. You can download the TOUR 1.0 depot from www.software.hp.com (Keyword “TOUR”). You can follow the Installation instructions provided on the web. These steps are also summarized below. For additional information, refer to the TOUR 1.0 Release Notes. System Requirements TOUR 1.
Installation Installing HP-UX 11i IPv6 (bundled as part of TOUR 1.0) — PHNE_28895 - “cumulative ARPA Transport patch” You can retrieve individual patches from www.itrc.com. NOTE: Future versions of Quality Pack (GOLDQPK11i) may include these four patches. In this case, you will not have to retrieve the patches individually. 2. Complete the registration form at www.software.hp.com with appropriate information. 3. Download the TOUR 1.0 software depot to a directory, for example, /tmp/TOUR.depot. 4.
Installation Verifying Your TOUR 1.0 Installation Verifying Your TOUR 1.0 Installation To verify your TOUR 1.0 installation, execute the following at the command prompt: swlist -l bundle TOUR You should see the following: TOUR A.01.00 Transport Optional Upgrade Release for B.11.11 To verify that there were no errors during the TOUR1.0 installation, execute the following at the command prompt: swverify TOUR If TOUR 1.
Installation Verifying IPv6 Loopback 12 Chapter 2
3 Configuration This chapter summarizes the steps for configuring LAN interfaces, assigning 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 • Stateless autoconfiguration • Manual configuration These methods are described in more detail below. Stateless Autoconfiguration Addresses on IPv6 interfaces, unlike IPv4 interfaces, can be configured without manual intervention. With stateless address autoconfiguration, the primary interface (lanX:0) is automatically assigned a link-local IPv6 address by the system when the interface is configured (marked “up”).
Configuration Stateless Autoconfiguration 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 manual configuration processes for HP-UX 11i IPv6, bundled as part of TOUR 1.0. 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 (for example, lan0) and the interface state, either up or down.
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 51. 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 • Assign the following parameters: destination IPv6 network, gateway address (for configured tunnels this is an IPv4-compatible IPv6 address), route_count (if set to 1 the gateway is remote, if set to 0 the gateway is local), and any route arguments (for configured tunnels, specify the -t option). Refer to the commented text in the netconf-ipv6 file and the route(1m) man page for more information.
Configuration Manual Configuration #example begins defaults { AdvSendAdvertisement on ; }; interface lan0 { prefixinfo 2008:65::/64 { }; }; #example ends For more examples, refer to the rtradvd.conf(4) man page. • Edit the /etc/rc.config.d/netconf-ipv6 file to enable rtradvd to start up at boot. Also, clear the “private” interface flag (-private), on the appropriate interface(s) to enable forwarding.
Configuration Manual Configuration made to your netconf-ipv6 file. A reboot is the cleanest way to reconfigure an interface because the reboot handles any network initialization dependencies. • Or alternatively, by executing the ifconfig and route commands, as needed, to make equivalent configuration settings. HP recognizes that system reboots are disruptive to end users.
Configuration Manual Configuration NOTE 22 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 IPv6 bundled as part of TOUR 1.0.
Configuration Host Names and IPv6 Addresses 3ffe:ffff:101::230:6eff:fe04:d9ff 192.1.2.34 NOTE host3 host3.site2.region4 hpfcrm loghost HP-UX 11i IPv6 bundled as part of TOUR 1.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 Or if /etc/hosts is to be the primary Name Service, the entry should be set as follows: ipnodes: files [NOTFOUND=continue] dns IMPORTANT If you have an /etc/nsswitch.conf file, and if you have set a hosts entry in that file, then you must set a similar ipnodes entry. You must do this even if you do not use IPv6 addresses. Also, be aware that you cannot use NIS or NIS+ on the ipnodes entry. Manually editing nsswitch.conf If the current system has no nsswitch.
Configuration Host Names and IPv6 Addresses 26 Chapter 3
4 Troubleshooting This chapter provides guidelines for troubleshooting HP-UX 11i IPv6 bundled as part of TOUR 1.0. It contains a troubleshooting overview and diagnostic flowcharts.
Troubleshooting Troubleshooting Overview Troubleshooting Overview Troubleshooting problems on HP-UX 11i IPv6, bundled as part of TOUR 1.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 IPv6, bundled as part of TOUR 1.0, supports an IPv4/IPv6 Dual Stack, test IPv4 connectivity before testing IPv6 connectivity. Refer to the HP-UX LAN Administrator’s Guide (available on 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 check the connections and configuration on your system (Flowcharts 1 through 5). If this does not solve your problem, use flowcharts 6 through 8 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 30 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 TCP6 over IPv6 through the Transport Layer (OSI Layer 4). C. Connection Refused? Trying to connect to a remote system where HP-UX 11i 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 36 Chapter 4
Troubleshooting Diagnostic Flowcharts Flowchart 4 Procedures A. Execute: ifconfig inet6. Execute ifconfig on the interface you want to test. For example, to check 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 38 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, check 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 40 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 42 Chapter 4
5 Utilities HP-UX 11i IPv6, bundled as part of TOUR 1.0, for the most part uses IPv6-enhanced IPv4 network utilities. This section summarizes the utilities required for administration of HP-UX 11i IPv6 bundled as part of TOUR 1.0.
Utilities Configuration Utilities Configuration Utilities This section describes configuration utilities available to configure HP-UX 11i IPv6 bundled as part of TOUR 1.0. New ifconfig “inet6” address family Use ifconfig to assign an IPv6 address to an interface and configure parameters, such as the network prefix. (InIPv6, prefix replaces netmask.) The new ifconfig keyword inet6 is required to configure IPv6 interfaces. It is not required to examine IPv6 interfaces.
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 IPv6 bundled as part of TOUR 1.0. 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 new IPv6 Subsystems, or use nettladm. Table 5-1 below lists the new subsystems available for IPv6 packet tracing. Table 5-1 New 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 new IPv6 subsystems.
Utilities IPv6 Additions to Network Tracing and Logging Table 5-2 New IPv6 Network Filter Criteria (Continued) Filter Description Connection per port and IPv6 address Chapter 5 Entry in the netfmt configuration file filter connection6 |
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 IPv6 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.
Utilities Contacting Your HP Representative 50 Chapter 5
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 Contact a local ISP or the Regional Internet Registries below 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. Small Internet Service Providers (ISPs) or end nodes acquire IPv6 addresses from their upstream provider.
IPv6 Addressing and Concepts IPv6 Address Formats To indicate a subnetwork address, IPv6 uses subnet prefixes similar to IPv4 CIDR format. Figure 5-1 shows 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. Site-local An IPv6 address used inside a single site. 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 54 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 Check 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 5-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 fec0:0:0:13/64 4. Secondary Interface Autoconfigured lan0:1 fec0:0: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 note 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 64 Chapter 6
7 IPv6 Software and Interface Technology The topics discussed in this section concern HP-UX 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 IMPORTANT If you have an /etc/nsswitch.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 Migrating from IPv4 to IPv6 To successfully migrate to IPv6, maintain compatibility with the large installed base of IPv4 hosts and routers. Staying compatible with IPv4 when deploying IPv6 eases the task of moving the Internet to IPv6. HP-UX 11i IPv6, bundled as part of TOUR 1.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 Host-to-Router IPv6/IPv4 hosts can tunnel IPv6 packets to an intermediary IPv6/IPv4 router that is reachable via an IPv4 infrastructure. This type of tunnel spans the first segment of the packet’s end-to-end path. Host-to-Host IPv6/IPv4 hosts that are interconnected by an IPv4 infrastructure can tunnel IPv6 packets between themselves. In this case, the tunnel spans the entire end-to-end path that the packet takes.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 Connecting IPv6 Domains over IPv4 Clouds (6to4) Isolated IPv6 nodes and networks can communicate over an IPv4 network without explicitly configuring tunnels, by using “6to4” mechanism (RFC 3056). “6to4” effectively uses the IPv4 wide area network as a unicast point-to-point layer. “6to4” requires no end-node reconfiguration and minimal router configuration.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 Example “6to4” Topology Figure 6-2 shows two IPv6 subnetworks. The end nodes have their routers globally unique IPv4 addresses embedded in their network prefixes. The routers have “6to4” addresses and corresponding globally unique IPv4 addresses. From the IPv6 end-node view, each host’s subnetwork is connected to the other’s through a 6to4 router. All IPv4 tunneling is transparent to the IPv6 end nodes.
IPv6 Software and Interface Technology Migrating from IPv4 to IPv6 Figure 6-3 shows the same routers from the IPv4 network perspective. Router Brussels and Router Tokyo are IPv4 Routers. All IPv6 traffic is tunneled transparently through the IPv4 network. Figure 7-3 6to4 IPv4 Internet View IPv6 Brussels Site IPv6 Tokyo Site 6to4 Router Brussels 6to4 Router Tokyo 128.2.3.4 5.6.7.
A IPv6 ndd Tunable Parameters The following new IPv6 tunable parameters allow advanced performance fine-tuning of HP-UX 11i IPv6, bundled as part of TOUR 1.0.
IPv6 ndd Tunable Parameters NOTE To obtain a list of supported IPv6 ndd parameters, enter: ndd /dev/ip6 ? For more information on a specific parameter, enter: ndd -h Below is the output received from entering, “ndd /dev/ip6 ?”: 74 ip6_ill_status (read only) ip6_ipif_status (read only) ip6_ifhash_status (read only) ip6_ire_status (read only) ip6_raw_status (read only) ip6_tcp_status (read only) ip6_udp_status (read only) ip6_ire_hash (read only) ip6_ire_hash_summary (read onl
IPv6 ndd Tunable Parameters ip6_wroff_extra (read and write) ip6_dl_sap (read and write) ip6_dl_snap_sap (read and write) ip6_bogus_sap (read and write) ip6_encap_hop_limit (read and write) ip6_nd_dad_solicit_count (read and write) ip6_nd_multicast_solicit_count(read and write) Appendix A ip6_nd_unicast_solicit_count (read and write) ip6_nd_advertise_count (read and write) ip6_rd_solicit_count (read and write) ip6_nd_transmit_interval (read and write) ip6_nd_anycast_delay (read and w
IPv6 ndd Tunable Parameters 76 Appendix A
