Configuring SNAplus2 for Enterprise Extender White Paper 1 SNAPLUS2 RELEASE 7 December 2010 Configuring SNAplus2 for Enterprise Extender White Paper Written by Philippe Barthet IBM Worldwide Technology Expert Center – Global Solutions Engineering
Configuring SNAplus2 for Enterprise Extender White Paper 2 Contents Abstract.............................................................................................................................................. 3 SNAPLus2 Release 7 Features over HPR/IP ............................................................................................. 4 Benefits of SNAPlus2 and Enterprise Extender .........................................................................................
Configuring SNAplus2 for Enterprise Extender White Paper 3 Abstract The HP-UX SNAPlus2 family of products has been enhanced with a new release (Release 7) running on HP-UX versions 11i v1, 11i v2, and 11i v3. Among several new features, SNAPlus2 Release 7 offers Enterprise Extender (EE) Links. SNAplus2 Enterprise Extender, also known as High Performance Routing over IP (HPR over IP), provides a standard base method to efficiently transport SNAplus2 data across an IP network.
Configuring SNAplus2 for Enterprise Extender White Paper SNAPLus2 Release 7 Features over HPR/IP The following features are supported over HPR/IP links: LU types 0, 1, 2, 3, 6.
Configuring SNAplus2 for Enterprise Extender White Paper 5 Benefits of SNAPlus2 and Enterprise Extender Running SNAPlus2 with HPR protocols over an IP backbone offers combined SNA and IP best features. The benefits are in the three major areas of availability, performance and usability. Failure protection ¾ One of the key features of HPR is the ability to allow nondisruptive rerouting upon path failures.
Configuring SNAplus2 for Enterprise Extender White Paper 6 HPR/IP Configuration on Mainframe This section describes how to configure HPR/IP support on an IBM Mainframe running OS/390 or z/OS operating systems. HPR over IP is known as Enterprise Extender on IBM Mainframes. To support Enterprise Extender on OS/390, you need OS/390 version 2.7 or later (or OS/390 version 2.6 with APAR number OW36113).
Configuring SNAplus2 for Enterprise Extender White Paper VTAM and TCP/IP VTAM and TCP/IP need to be configured to 1. Switch on the HPR support and CP-CP session support start options 2. Define an XCA (Externat Communications Adapter) Major Node for HPR/IP 3. Enable VTAM to be a TCP/IP application Each of these is described briefly in the following sections.
Configuring SNAplus2 for Enterprise Extender White Paper 8 2. XCA Major Node (SYS1.VTAMLST (member)) A new dataset member containing an HPR/IP XCA Major Node definition must be added to SYS1.VTAMLST. An example is provided below: */* SYS1.
Configuring SNAplus2 for Enterprise Extender White Paper 9 CommandPrefix=None /* This is the default value */ /*--------------------------------------------------------------------*/ /* Automatically Start Several VTAM Applications */ /*--------------------------------------------------------------------*/ Pause 10 /* Wait for sys to get up first */ S vlf,sub=mstr Pause 10 /* Wait for sys to get up first */ S lla,sub=mstr S Tcas /* Time Sharing Option */ /*S rmf*/ /* RMF */ S tcpip /*s irlmproc*/ Pause 10
Configuring SNAplus2 for Enterprise Extender White Paper 10 3. Configure VTAM to TCP/IP (TCPIP.PROFILE.TCPIP) The TCP/IP profile file must be updated as follows: Add an IUTSAMEH device and link as follows so that VTAM can access the TCP/IP stack. DEVICE IUTSAMEH MPCPTP AUTORESTART LINK samehlnk MPCPTP IUTSAMEH Add a VIPA device and link for HPR/IP, for example DEVICE VIPADEV2 VIRT 0 LINK P390IP VIRT 0 VIPADEV2 Add the VIPA link to the head of the HOME list, for example, HOME 172.1.1.
Configuring SNAplus2 for Enterprise Extender White Paper 11 ;ACBPOOLSIZE 1000 ;ADDRESSTRANSLATIONPOOLSIZE 1500 ;CCBPOOLSIZE 150 ;DATABUFFERPOOLSIZE 160 32768 ;ENVELOPEPOOLSIZE 2500 ;750 ;IPROUTEPOOLSIZE 300 ;LARGEENVELOPEPOOLSIZE 50 32768 ;RCBPOOLSIZE 50 ;SCBPOOLSIZE 768 ; default 256 ;SKCBPOOLSIZE 256 ;SMALLDATABUFFERPOOLSIZE 1200 ;TCBPOOLSIZE 256 ;TINYDATABUFFERPOOLSIZE 500 ;UCBPOOLSIZE 256 ; ; ----------------------------------------------------------------------; ; Inform the following users of seriou
Configuring SNAplus2 for Enterprise Extender White Paper 12 ; ; --------------------------------------------------------------------; ; Set Telnet time-out to 10 minutes.
Configuring SNAplus2 for Enterprise Extender White Paper 13 PORT ; ; ; ; ; ; ; ; ; 7 UDP MISCSERV 7 TCP MISCSERV 9 UDP MISCSERV 9 TCP MISCSERV 19 UDP MISCSERV 19 TCP MISCSERV 20 TCP OMVS 21 TCP OMVS 23 TCP INTCLIEN 25 TCP SMTP 53 TCP NAMESRV 53 UDP NAMESRV 69 UDP OMVS 80 TCP OMVS 111 TCP PORTMAP 111 UDP PORTMAP 135 UDP LLBD 161 UDP OSNMPD 162 UDP SNMPQE 433 TCP OMVS 443 TCP OMVS 446 TCP OMVS 512 TCP RXSERVE 513 UDP OMVS 514 UDP OMVS 514 TCP RXSERVE 515 TCP LPSERVE 520 UDP OROUTED 580 UDP NCPROUT 750 TC
Configuring SNAplus2 for Enterprise Extender White Paper 14 ; ; LCS2 is a 3172 Model 2 with a FDDI adapter. ; ;DEVICE LCS2 LCS ;LINK FDDI1 FDDI BE0 0 LCS2 ; ; SNALU0 is an SNA Link.
Configuring SNAplus2 for Enterprise Extender White Paper GATEWAY ; ; Direct Routes - Routes that are directly connected to my interfaces. ; ; Network First Hop Link Name Packet Size Subnet Mask Subnet Value ; ; ; ; ; 172.19 172.20 9 130.50 193.5.2 9 193.7.2.2 = = = = = = = P390 P390X ETH1 TR1 ETH1 FDDI1 SNA1 1500 1500 1500 2000 1500 4000 2000 0 0 0.255.255.0 0.0.255.0 0 0.255.255.0 HOST 0.117.56.0 0.0.10.0 0.67.43.0 ; ; Indirect Routes - Routes that are reachable through routers on my ; network.
Configuring SNAplus2 for Enterprise Extender White Paper 16 ;TRANSLATE ; A null translate statement issues the warning message EZZ0323I ; ; ------------------------------------------------------------------; ; Turn off all tracing. If tracing is to be used, change the following ; line.
Configuring SNAplus2 for Enterprise Extender White Paper 17 ; Define the LUs to be used for general users.
Configuring SNAplus2 for Enterprise Extender White Paper 18 4. Switched Major Nodes for PU(SYS1.VTAMLST(member)) It is also possible to define each PU is a switched Major Node. However, the preferred method is to configure the VTAM user exit ISTEXCCS to dynamically define PUs as connections made over HPR/IP. These PU definitions are not specific to HPR/IP and can be used by PUs to connect over any External Communication Adapter (XCA). An example of such a Switched Major Node is given below: */* SYS1.
Configuring SNAplus2 for Enterprise Extender White Paper 19 */* 3278/9 DISPLAY TERMINALS WSIC0201 LU LOCADDR=1,DLOGMOD=SNX32702 WSIC0202 LU LOCADDR=2,DLOGMOD=SNX32702 WSIC0203 LU LOCADDR=3,DLOGMOD=SNX32702 WSIC0204 LU LOCADDR=4,DLOGMOD=SNX32702 WSIC0205 LU LOCADDR=5,DLOGMOD=SNX32702 WSIC0206 LU LOCADDR=6,DLOGMOD=SNX32702 WSIC0207 LU LOCADDR=7,DLOGMOD=SNX32702 */* LU TYPE 1 PRINTER WSIC0208 LU LOCADDR=8,DLOGMOD=SCS,USSTAB=ISTINCDT */* RJE TERMINALS WSIC0209 LU LOCADDR=9,DLOGMOD=BATCHS1,USSTAB=ISTINCDT WSIC
Configuring SNAplus2 for Enterprise Extender White Paper 20 WSIC0403 LU LOCADDR=3,DLOGMOD=SNX32702 WSIC0404 LU LOCADDR=4,DLOGMOD=SNX32702 WSIC0405 LU LOCADDR=5,DLOGMOD=SNX32702 WSIC0406 LU LOCADDR=6,DLOGMOD=SNX32702 WSIC0407 LU LOCADDR=7,DLOGMOD=SNX32702 */* LU TYPE 1 PRINTER WSIC0408 LU LOCADDR=8,DLOGMOD=SCS,USSTAB=ISTINCDT */* RJE TERMINALS WSIC0409 LU LOCADDR=9,DLOGMOD=BATCHS1,USSTAB=ISTINCDT WSIC0410 LU LOCADDR=10,DLOGMOD=BATCHS1,USSTAB=ISTINCDT WSIC0411 LU LOCADDR=11,DLOGMOD=BATCHS1,USSTAB=ISTINCDT *
Configuring SNAplus2 for Enterprise Extender White Paper 21 HPR/IP verification After HPR/IP is activated, issue the following three commands to verify Enterprise Extender is running: 1. D TCPIP, TCPIP, NETSTAT, DEV 2. D NET, ID=XCAEE 3. D NET, ID=PUTO65, E 1. D TCPIP, TCPIP, NETSTAT, DEV D TCPIP, TCPIP, NETSTAT, DEV shows the status of Virtual IP Adapter (VIPA) and IUTSAMEH (VTAM) devices used for Enterprise Extender.
Configuring SNAplus2 for Enterprise Extender White Paper 22 3. D NET,ID=PU3270,E D NET, ID=PU3270, E shows a display of the Physical Unit used for Enterprise Extender. D NET, ID=PU3270, E IST097I DISPLAY ACCEPTED IST075I NAME = PU33270, TYPE = PU_T2.
Configuring SNAplus2 for Enterprise Extender White Paper 23 HPR/IP configuration in SNAPlus2 SNAPlus2 configuration is done by launching the Motif-based tool xsnapadmin. The configuration steps are: 1. Node Configuration 2. Port Configuration 3. Link Station Configuration 1. Configuring the SNAPlus2 Node The node appears as ‘Unconfigured’ a. Double-click on the node icon or select the Node and click ‘Properties’. The Node parameters window is displayed.
Configuring SNAplus2 for Enterprise Extender White Paper 24 b. APPN support This field appears on the Motif dialog only if the SNAplus2 software installed on the server supports more than one type of node. Select the level of SNA and APPN connectivity that the node is to support. If in doubt, consult your SNA network planner on how to set this field. This can be one of End node Network node Branch network node c. Control point name This is the CP name of the node.
Configuring SNAplus2 for Enterprise Extender White Paper 25 common default is the second part of the CP name. This alias can be used by APPC applications to refer to the control point LU. e. Node ID The node ID consists of a total of 8 hexadecimal digits. The first 3 digits are known as the block number. The remaining 5 digits are the node ID number. The node ID is used when you are setting up a link for dependent traffic, usually to a host.
Configuring SNAplus2 for Enterprise Extender White Paper 26 This dialog allows you to set or change the configuration of an enterprise extender (HPR/IP) port. a. Port name This is a name for you to use to identify the IP port. Note: This name can be up to eight characters long. b. Local IP interface This is an optional field. It allows you to specify the local IP network interface name or a local IP Address to be used for the port.
Configuring SNAplus2 for Enterprise Extender White Paper c. Initially active 27 If you select this, the IP port is activated automatically when the node is started. Once the port is configured, you need to configure the HPR/IP Link Station. Focus on the configured Port; Clicking ‘New’ will bring the following panel: Select ‘Link station to port . Click ‘OK’.
Configuring SNAplus2 for Enterprise Extender White Paper 28 3. Enterprise Extender (HPR/IP) Link Station Configuration This dialog allows you to configure the characteristics of a link station to an adjacent remote node in the SNA network. It is used when you are defining a link station that uses Enterprise Extender (HPR/IP). a. Name This is a name for you to use to identify the link station locally. b. SNA port name Select the port that is to be used to access the remote node.
Configuring SNAplus2 for Enterprise Extender White Paper 29 This is the fully qualified CP name of the remote node. It consists of two type A EBCDIC strings each of 1 – 8 characters. This can be obtained by examining the configuration of the remote node. If you want to define a new remote node, you need to specify the remote node type rather than choosing 'Discover'.
Configuring SNAplus2 for Enterprise Extender White Paper 30 This dialog allows you to configure some advanced parameters on an Enterprise Extender link station. Most users do not need to alter these parameters, but these parameters can be used to improve performance. The fields in this dialog, and their default settings, vary according to the settings in the standard link station dialog. Complete the standard dialog before altering the settings in this dialog. a.
Configuring SNAplus2 for Enterprise Extender White Paper g. Liveness timeout 31 This is the maximum idle time before checking whether the link has failed. The range is 1-65535.
Configuring SNAplus2 for Enterprise Extender White Paper 32 Appendix A – Concepts and Terminology This section is a brief and non exhaustive introduction to the concepts and terminology used in this document, including APPN and HPR. For a more complete description of APPN and HPR, refer to the reference appendix. Session A session is a logical connection between two network accessible units (NAUs). The most common example of an NAU is a Logical Unit (see below).
Configuring SNAplus2 for Enterprise Extender White Paper 33 APPN Nodes Introduction In an APPN network, nodes can be of the following types. Network Nodes (NN) End Nodes (EN) Low-entry networking nodes (LEN nodes) Branch Network Nodes (BrNN) Each node in an APPN network is connected to at least one other node in the APPN network.
Configuring SNAplus2 for Enterprise Extender White Paper 34 An End Node can also have a direct connection to another End Node or LEN node, but CP-CP sessions are never established between the two nodes. LEN Node A LEN Node is of type 2.1 node that uses independent LU 6.2 protocols, but does not support CP-CP sessions. It can be connected to a Network Node or End Node but does not support APPN functions.
Configuring SNAplus2 for Enterprise Extender White Paper 35 ¾ Automatic network routing (ANR) enables APPN networks to automatically reroute sessions if a portion of the originally computed route fails. Enterprise Extender Port and LS These are SNAPlus2 configuration resources, which provide SNA connectivity for applications using dependent and independent sessions over a native IP network. It implements the “HPR/IP” protocol, which is also known as “HPR over IP” or “Enterprise Extender”.
Configuring SNAplus2 for Enterprise Extender White Paper 36 Appendix B - References HP-UX SNAplus2 Administration Guide HP-UX SNAplus2 General Information IBM SG24-3669 Inside APPN – The essential Guide to the NextGeneration SNA IBM SG24-5957 Migrating Sub area Networks to an IP Infrastructure Using Enterprise Extender IBM SG24-5204 Sub area to APPN Migration: HPR and DLUR Implementation IBM SG24-4656 Sub area to APPN Migration: VTAM and APPN implementation IBM GA27-3136 SNA Formats
Configuring SNAplus2 for Enterprise Extender White Paper For more information http://docs.hp.com/en/netcom.html SNAplus2 Release 7 documentation http://docs.hp.com/en/J6380-90003/index.html SNAplus2 R7 11iv1 Release Notes http://docs.hp.com/en/J6380-90004/J6380-90004.pdf SNAplus2 R7 11iv2 Release Note Call to action http://h20219.www2.hp.com/services/cache/110263-0-0-225-121.html HP ValuePack Services © 2010 Hewlett-Packard Development Company, L.P.
