TCP/IP Configuration and Management Manual

SCF Reference
TCP/IP Configuration and Management Manual—427132-004
4-4
ROUTE Object Type
ROUTE Object Type
The ROUTE object establishes the path a data packet travels to reach its destination.
Instead of specifying a full path, a route specifies the packet’s first host address and
the packet’s destination. The first host then routes the packet to the next appropriate
address in-route to the destination. This sequence repeats until the packet reaches the
destination.
Often, a NonStop system routes all packets to a default host, which in turn maintains a
more complete routing table.
Each time you add a SUBNET, a route is created automatically. You can add more
routes as necessary. Refer to Appendix B, NonStop TCP/IP Processes and Protocols,
for a full explanation of routes and routing.
You must assign a unique ROUTE object name to each route associated with a given
process. Precede the name with a pound sign (#). The ROUTE object name can have
at most seven alphanumeric characters. The first character following the pound sign
must be a letter. Table 4-1 shows an example of ROUTE object naming conventions.
Routes that are associated with different processes can have identical names;
therefore, you must specify the process name, a period, and the route name to
distinguish a particular route on a particular process from other routes that might have
the same name on other processes. To omit the process name and period and just
specify the route name, set a default process name with the ASSUME command.
Names beginning with #RTn and #DRTn are reserved. Otherwise, use other letters to
begin a route name; for example, #ROU5.
For further information on the ASSUME command, including the required syntax, refer
to the SCF Reference Manual for G-Series RVUs or the SCF Reference Manual for H-
Series RVUs.
SERVER Object Type
The SERVER object allows you to add to a specific SUBNET the ATM address of
ATMARP servers for use in resolving IP addresses. More than one server object can
be added to a SUBNET but only one can be in use at a time. If communication is lost
to an ATMARP server and a SUBNET is configured with more then one SERVER
object, the next one in the list is tried.
Table 4-1. Route Object Naming Conventions
PROCESS $A ROUTE Object Name
Route 1 #ABC1
Route 2 #ABC2
Route3 #ABC3