TCP/IPv6 Configuration and Management Manual (G06.29+, H06.03+, J06.03+)
SCF Reference for NonStop TCP/IPv6
HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012
8-40
ADD SUBNET Command for TCP6MAN
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.
When a SUBNET is added, a corresponding route to this SUBNET is added
automatically. Both the SUBNET and the route are placed in the STOPPED state.
To initiate the operation of the object, you must start it with the START command.
When adding a SLSA SUBNET type, the DEVICENAME does not begin with a
dollar sign ($) character.
SUBNETs from the conventional TCP/IP and NonStop TCP/IPv6 environments
cannot share a LIF.
When using LNP in a DUAL-mode environment, if you want to use tunneling, you
should use configured tunneling rather than automatic tunneling because the
automatic tunnel associates itself with the first available DUAL-mode SUBNET and
is not available to applications in LNPs that differ from the LNP of that SUBNET. To
use tunneling in an LNP environment, add a configured tunnel to each LNP that
needs tunneling. The configured tunnel is associated with the LNP by the IPTSRC
attribute; the LNPTPLIST attribute is not valid for the configured-tunnel type
SUBNET.
An IPv6 SUBNET is ready for data transfer as soon as you add and start it. But if
you want to enable the tunnels on the IPv6 SUBNET, you have to alter the
SUBNET and specify FAMILY INET6, IPV6 UP.