Extended border node configuration

The example shows the definitions you might have between two interconnected partners. This configuration would replace an SNA network interconnect (SNI) connection between two front-end processors (such as 3745s).

The example includes the type of extended border node implementation definitions you see under VTAM at both organizations. There are most likely firewall definitions, and ports 12000 - 12004 need to be opened.

Consult your security administrator for the firewall definitions.

Figure 1. Extended border node configuration

* VTAM Start options for EBN in ATCSTR05 member (NZCP5 definition shown)
* ORGCP1 will have similar ATCSTRxx definitions, IPADDR will be: 182.20.5.20
BN=YES
NODETYPE=NN
TCPNAME=TCPIP
IPADDR=10.192.25.10
  
* VTAM XCA major node required on both NZCP5 and ORGCP1
* VTAM Switched Major node on NZCP5 for ORGCP1

EESWN1     VBUILD TYPE=SWNET
EE2ORG1    PU     CPCP=YES,
                  CONNTYPE=APPN,
                  HPR=YES,
                  TGP=ESCON,
                  DYNLU=YES,
                  DISCNT=NO,
                  DWACT=YES,
                  NETID=ORGNET,
                  CPNAME=ORGCP1,
                  ISTATUS=ACTIVE
EEPATH      PATH  IPADDR=192.20.5.20, remote TCP/IP address for connection.
                  GRPNM=EEGRPIO,SAPADDR=4
  
* VTAM Switched Major node on ORGCP1 for NZCP5
EESWN5     VBUILD TYPE=SWNET
EE2NZC5    PU     CPCP=YES,
                  CONNTYPE=APPN,
                  HPR=YES,
                  TGP=ESCON,
                  DYNLU=YES,
                  DISCNT=NO,
                  DWACT=YES,
                  NETID=NZNET
                  CPNAME=NZCP5,
                  ISTATUS=ACTIVE
EEPATH      PATH  IPADDR=10.192.25.10, remote TCP/IP address for connection.
                  GRPNM=EEGRPIO,SAPADDR=4

The existing VTAM application definitions remain the same.