IBM Communications Server for AIX, V6 New Features and Implementation Scenarios

92 IBM Communications Server for AIX, V6: New Features and Implementation Scenarios

Remote node type Network node, end node, or discover.

Remote IP host name To configure a selective link station enter the IP

hostname or dotted-decimal IP address of the

remote station.

Advanced parameters In most cases you can use the default settings

for these parameters, so you do not need to alter

the settings in the advanced dialog.

d. Click the OK button and the link station will appear beneath the port to

which it belongs in the Connectivity pane of the Node window.

Note that Enterprise Extender links support only independent LU traffic. That

means that if dependent LUs must be supported, DLUR must be configured

on the CS/AIX node.

6.4 Scenario

For this section we used the following equipment:

• Two RS/6000s running AIX Version 4.3.3.0 with the latest maintenance

level, and

Communications Server for AIX, Version 6

• A PC running Windows NT and IBM Personal Communications for

Windows NT

,

Version 4.3 (PCOMM)

• A host running CS for OS/390

We used DLUR to show that Enterprise Extender provides a mechanism for

transporting SNA protocols over the IP network.

DLUR is an APPN feature that allows dependent LU sessions without a direct

connection to a host. The Dependent LU Requester (DLUR) communicates

with a Dependent LU Server (DLUS) over an APPN network. DLUR must be

available on the node where the LUs are located but DLUR is not required on

any intermediate nodes in the session route.

By using HPR/IP links, the session route between DLUR and DLUS will take

place in an IP network but taking advantage of APPN features such as HPR.

Sessions between DLUR and DLUS will be routed over an RTP connection.

The following configuration steps are required for this scenario:

1. Configure EE support on the rs60003 machine including DLUR

2. Configure EE support on the rs60004 machine

3. Activate CS/AIX resources on both nodes

Chapter 6. Enterprise Extender 93

4. Configure EE support in VTAM and TCP/IP on the host

5. Test the EE connections using PCOMM

The test scenario is shown in Figure 58. Refer to this figure when reviewing

the following configuration steps.

Figure 58. Test scenario

6.4.1 Configure the rs60003 machine

On the rs60003 machine:

1. Configure the node as an End Node, as shown in Figure 59.

OSA

PCOMM

TN3270 Client

Network Node

DLUR

TN3270 Server

CS for OS/390

NN DLUS

EE - IP VIPA

USIBMRA.RA03M

172.16.250.3

End Node

rs60004

9.24.104.27

rs60003

9.24.104.23

mk23bk63p

9.24.104.205

IP

IP

IP

EE

EE

94 IBM Communications Server for AIX, V6: New Features and Implementation Scenarios

Figure 59. Configuration of rs60003 EN

2. Define a DLUR PU. Click Services -> Connectivity -> New DLUR PU.

Figure 60. Definition of DLUR PU

The DLUR PU ID that you enter here must match the ID by which the PU is

defined within the VTAM configuration.

For assistance configuring the DLUR PU refer to

IBM Communications

Server for AIX Quick Beginnings, Version 6,

GC31-8583 and

IBM

Communications Server for AIX Administration Guide, Version 6,

SC31-8586.

3. Define the Dependent LUs

Chapter 6. Enterprise Extender 95

Figure 61. Definition of dependent LUs

For assistance configuring Dependent LUs refer to

IBM Communications

Server for AIX Quick Beginnings, Version 6,

SC31-8583 and

IBM

Communications Server for AIX Administration Guide, Version 6,

SC31-8586.

4. Configure the TN3270 server access records. Click Services -> TN

Server -> TN Server...

96 IBM Communications Server for AIX, V6: New Features and Implementation Scenarios

Figure 62. TN3270 server access

The LU Pool assigned for access by the TN3270 client contains the

dependent LUs defined to DLUR. Port 9000 was chosen as the TN Server

port.

For more information on TN3270 refer to

IBM Communications Server for AIX

Quick Beginnings, Version 6,

GC31-8583 and

IBM Communications Server

for AIX Administration Guide, Version 6,

SC31-8586.

5. Configure HPR/IP connectivity to the rs60004 NN as shown in Figure 56

on page 90 and Figure 57 on page 91.

The definition of the port adds the following define_ip_dlc and

define_ip_port sections to the /etc/sna/sna_node.cfg file:

[define_ip_dlc]

dlc_name =

IP0

description = ““

initially_active =

NO

udp_port_llc = 12000

udp_port_network = 12001