TCP/IP Configuration and Management Manual

SCF Reference
TCP/IP Configuration and Management Manual—427132-004
4-2
ADDRMAP Object Type

PROCESS

ROUTE

SERVER

SUBNET
Figure 4-1 shows that the ROUTE, SUBNET, ENTRY, and ADDRMAP object types are
peers. The ROUTE, SUBNET, ENTRY, and ADDRMAP object types are subordinate to
the PROCESS object. The SERVER is subordinate to the SUBNET (and can only be
added or deleted when the SUBNET is in the STOPPED state.) This hierarchy is
important when issuing commands to the NonStop TCP/IP subsystem for processing.
For example, because the ROUTE, SUBNET, ENTRY, SERVER and ADDRMAP object
types are subordinate to the PROCESS object type, any commands pertaining to a
ROUTE, SUBNET, ENTRY, SERVER or ADDRMAP object type can be issued only
when the PROCESS object is in the STARTED summary state.
ADDRMAP Object Type
The ADDRMAP object specifies the name for the entry in the TCP/IP X25 address
table (an internal table that maps IP addresses to X.121 addresses). The name must
be preceded by a pound sign (#) and can have at most seven alphanumeric
characters. The first character following the pound sign must be a letter.
You must assign a unique addr-name to each ADDRMAP object associated with a
particular process. Names beginning with #ZADR are reserved for use by the process
when creating dynamic entries. Use other letters to begin an address map name; for
example, #ZADD.
ENTRY Object Type
The ENTRY object allows you to view and add to the Address Resolution Protocol
(ARP and ATMARP) tables and obtain physical (MAC or ATM) addresses for any given
IP address.
Figure 4-1. NonStop TCP/IP Subsystem Object Hierarchy
013VST .VSD
PROCESS
SUBNET ROUTE ADDRMAP ENTRY
SERVER