HP-UX IPv6 Transport Administrator Guide HP-UX 11i v3 (5992-6426, May 2013)

Table Of Contents
Network Configuration and Troubleshooting Utilities for both IPv4 and IPv6:
ifconfig, netstat, ping, route, ndd, ndp (neighbor-discovery command for
IPv6 only) and traceroute. There have also been enhancements to nettl and
netfmt for IPv6 tracing and formatting.
The netconf-ipv6 file stores IPv6 settings. The
/etc/rc.config.d/netconf-ipv6 configuration file stores IPv6 configuration
information similar to IPv4’s /etc/rc.config.d/netconf file.
The /etc/hosts file now supports IPv6 and IPv4 addresses. The /etc/hosts
file contains IP addresses and corresponding host names. The file can contain IPv4
and IPv6 addresses for the same host. Lookup policies are identical to IPv4. For
example:
15.15.15.15 hpindon
2001:db8::1234 hpindon hpindon6
Name Service Switch: /etc/nsswitch.conf is a configuration file for the name
service switch. The ipnodes entity specifies which name services resolve IPv6
addresses and host names. Refer to the nsswitch.conf(4) man page for more
information.
Limitations
The following section describes limitations of IPv6 transport in HP-UX 11i v3.
setparms Not Enhanced for IPv6 Configuration
On HP-UX 11i v3, the setparms utility has not been enhanced to support IPv6
configuration.
Following are the changed and unsupported features in the B.11.31.08.09 version of
IPv6:
The usage of IPv6 site-local unicast addresses with prefix fec0::/10 is deprecated.
The unique Local IPv6 unicast addresses (RFC 4193) with prefix fc00::/7 must
be used for local communications.
The IPv4-compatible IPv6 address, (for example, ::a.b.c.d) is deprecated.
Multihomed Host Limitation
In the absence of a router that is advertising prefixes, no more than one interface can
be configured with IPv6 addresses on a host with multiple physical network interfaces.
If multiple physical interfaces are configured with IPv6 addresses, and if there is no Router
Advertisement received on any interfaces, the host has no way of knowing which interface
to send packets out on. If packets are sent out on the interface that is on a different link
than the destination node, then communication will fail. This configuration is neither
recommended nor supported.
Limitations 21