TCP/IPv6 Configuration and Management Manual (G06.24+)

SCF Reference for NonStop TCP/IPv6
HP NonStop TCP/IPv6 Configuration and Management Manual—524523-008
8-40
ADD SUBNET Command for TCP6MAN
TYPE TUNNEL
specifies that the SUBNET is used as a configured tunnel.
FAMILY INET6
specifies that the socket-family type of the SUBNET as AF_INET6 (IPv6). SUBNET
objects used with the IPv6 protocol must have the FAMILY attribute explicitly
specified as INET6. The default value for the FAMILY attribute is INET.
IPTDST ip-addr
specifies the remote end-point of the configured tunnel. This ip-addr must be an
IPv4 Internet address specified in dotted-decimal or hexadecimal notation. This
attribute is required and is valid only for SUBNETs of type TUNNEL.
IPTSRC ip-addr
sets the IPv4 source address in the encapsulating header. This IPv4 source
address must belong to an existing SUBNET on your system. This ip-addr must
be an IPv4 Internet address specified in dotted-decimal or hexadecimal notation.
This parameter is required and is valid only for SUBNETs of type TUNNEL.
Configured Tunnel Example
This example creates a configured-tunnel SUBNET and enables it for IPv6 operation.
You must have a DUAL-mode SUBNET on your host and you must know the IP
address of your destination. You must also have a default route to the IPT destination
(see ADD ROUTE Command for TCP6MAN on page 8-21).
-> ADD SUBNET $ZZTCP.*.IPT1, TYPE TUNNEL, FAMILY INET6, &
IPTSRC 16.140.16.86, IPTDST 16.140.16.91
-> ALTER SUBNET $ZZTCP.*.IPT1, FAMILY INET6, IPV6 UP
For more information regarding the ALTER command used in this example, see
ALTER SUBNET Command for TCP6MAN
on page 8-49.
Considerations
•
You can add up to 64 SUBNETs in the NonStop TCP/IPv6 environment.
•
When you add a SUBNET, you must do so to all configured TCP6MONs. Hence,
only the wild card (*) is supported for the TCP6MON name. The wild card,
however, is optional; if you do not specify it, the wild card is assumed.
•
When you specify the name of the route or SUBNET you are adding, be sure to
specify the process name in the ASSUME command or in the ADD command, as
shown in the examples. Verify that the name is unique for that process.
•
The SLSA subsystem must be operational for the ADD command to complete
successfully. For more information, see the LAN Configuration and Management
Manual.