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-25
ADD SUBNET Command for TCP6MAN
Considerations
Routes also can be created dynamically through internal routing logic.
Routes created by internal route-redirect logic have names in the format:
DDcpu_n
where cpu is the processor number, in hexadecimal format, of the processor in
which the route is generated and n is a decimal number.
Routes created by ARP link-level logic have names in the format:
DAcpu_n
where cpu is the processor number, in hexadecimal format, of the processor in
which the route is generated and n is a decimal number.
Routes created by internal IRDP logic have names in the format
DRcpu_n
where cpu is the processor number, in hexadecimal format, of the processor in
which the route is generated and n is a decimal number.
Routes created by internal ND6 cache logic have names in the format
NDcpu_n
where cpu is the processor number, in hexadecimal format, of the processor in
which the route is generated and n is a decimal number.
Routes generated implicitly because of an ADD SUBNET or ALTER SUBNET,
SUBNETMASK command have names starting with RT. These route types are called
implicit routes.
The link-level route generated from ADD ENTRY commands have the same name
as the entry name. Entry name must start with EA.
All the above route names are reserved; that is, names starting with DDcpu,
DAcpu, DRcpu, RT, NDcpu, and EA are reserved.
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 the SUBNET with the START
command.
Special considerations apply for LNP environments. See LNP Guidelines on
page 6-24.
ADD SUBNET Command for TCP6MAN
The ADD SUBNET command creates a SUBNET in the NonStop TCP/IPv6
environment.
A SUBNET can be configured to support: