Defining Unique CP Names and Connection Network Names

For configurations that have two or more SNA over TCP/IP gateways connecting an SNA network with two or more IP networks, you must define a unique SNA control point (CP) name and a unique SNA connection network name for each IP network.

All LUs that reside on access nodes in the IP network appear to reside on a node with this CP name.

Use the reverse data file of the domain name server or the HOSTS file to define the CP name and the connection network name for a given IP network. Map the IP address 127.0.0.3 to the CP name and map the IP address 127.0.0.4 to the connection network name.

The following example shows entries in the reverse data file. For an IP network with SNA network ID NETA, CP name MYCPNAME, and connection network name MYCNET, you would define the following entries:

127.0.0.3       NETA.MYCPNAME.
127.0.0.4       NETA.MYCNET.

Note:

A period is required at the end of the name only if the definition is in the DNS reverse data file. No period is used in HOSTS file definitions.
Do not include the SNA domain name suffix.

The AnyNet® SNA over TCP/IP function of Personal Communications provides a default CP name ($ANYNET.$GWCP) and a default connection network name ($ANYNET.$GWCNET). In configurations with one IP network, you can use the default by not defining a CP name or a connection network name. In configurations with multiple gateways connecting multiple IP networks, one IP network can use the default. You must, however, define a unique CP name and connection network name for all other IP networks.

Figure 1 shows how to define the CP name and the connection network name for a configuration with two IP networks. An example is provided in Quick Beginnings.

Figure 1. Defining a CP Name and a Connection Network Name