TCP/IPv6 Migration Guide

Migration Considerations
HP NonStop TCP/IPv6 Migration Guide—524524-004
3-6
Management Interfaces
SCF
For complete reference information about SCF and the SCF command syntax, see the
TCP/IPv6 Configuration and Management Manual. See also SCF on page 2-5 for
information about the SCF interface to TCP6SAM.
Object Name Syntax
Another level of qualification is required for the SUBNET, ROUTE, and ENTRY objects.
In NonStop TCP/IPv6, the name syntax for these objects includes the MON object. The
pound sign (#) still precedes the MON name but the SUBNET, ROUTE, and ENTRY
objects no longer require the pound sign. Although placing a pound sign (#) in front of
those objects does not generate an error, the preferred way to specify the lowest-level
object is without the pound sign (#) as shown in the following naming specifications:
SCF Objects
The following SCF objects from NonStop TCP/IP are not supported in NonStop
TCP/IPv6:
•
SERVER
•
ADDRMAP
The MON object is new for NonStop TCP/IPv6.
SCF Commands
The following SCF commands from NonStop TCP/IP are not supported in NonStop
TCP/IPv6:
•
ALTER PROCESS
•
STATS/RESET PROCESS
Equivalent commands in NonStop TCP/IPv6 are:
•
ALTER MON
•
STATS/RESET MON
New SCF Object Attributes
A new attribute, MASTER, has been added and applies to the TCP6MON object. See
Master TCP6MON.
SUBNET $TCP6MAN-name.#TCP6MON-name.subnet-name
ROUTE $TCP6MAN-name.#TCP6MON-name.route-name
ENTRY $TCP6MAN-name.#TCP6MON-name.entry-name