Configuring IP-DLC Link Service for IBM Enterprise Extender：对于IBM企业扩展配置ip-dlc链接服务

1、Configuring IP-DLC Link Service for IBM Enterprise ExtenderWhite PaperUpdated: February 2007 For the latest information, please see HYPERLINK :/ microsoft /hiserveroft /hiserverCopyrightThe information contained in this document represents the current view of Microsoft Corporation on the issues disc

2、ussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.This White Paper is for

3、informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT.Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or

4、 introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.Microsoft may have patents, patent applications, trademarks, copyrights

5、, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. 2007

6、 Microsoft Corporation. All rights reserved.Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail ad

7、dress, logo, person, place or event is intended or should be inferred.Microsoft, BizTalk, Visual Basic, Visual C+, Visual C#, Visual Studio, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.The names of ac

8、tual companies and products mentioned herein may be the trademarks of their respective owners.Contents TOC f h z HYPERLINK l _Toc82505533 Introduction PAGEREF _Toc82505533 h 3 HYPERLINK l _Toc82505534 IP-DLC Configuration (Mainframe) PAGEREF _Toc82505534 h 3 HYPERLINK l _Toc82505535 Host Requirement

9、s PAGEREF _Toc82505535 h 3 HYPERLINK l _Toc82505536 Network Adapter Requirements PAGEREF _Toc82505536 h 3 HYPERLINK l _Toc82505537 OS/390 VTAM and TCP/IP components Configuration PAGEREF _Toc82505537 h 3 HYPERLINK l _Toc82505538 1. HPR and CP-CP Session Start Option (SYS1.VTAMLST(ATCSTR00) PAGEREF _

10、Toc82505538 h 3 HYPERLINK l _Toc82505539 2. XCA Major Node (SYS1.VTAMLST(member) PAGEREF _Toc82505539 h 3 HYPERLINK l _Toc82505540 3. Configure VTAM to TCP/IP (TCPIP.PROFILE.TCPIP) PAGEREF _Toc82505540 h 3 HYPERLINK l _Toc82505541 4. Switched Major Nodes for PUs SYS1.VTAMST(member) PAGEREF _Toc82505

11、541 h 3 HYPERLINK l _Toc82505542 How to Verify IP-DLC (Enterprise Extender) PAGEREF _Toc82505542 h 3 HYPERLINK l _Toc82505543 1. D TCPIP,TCPIP,NETSTAT,DEV PAGEREF _Toc82505543 h 3 HYPERLINK l _Toc82505544 2. D NET,ID=XCAEE,E PAGEREF _Toc82505544 h 3 HYPERLINK l _Toc82505545 3. D NET,ID=PU3270,E PAGE

12、REF _Toc82505545 h 3 HYPERLINK l _Toc82505546 Host Integration Server Configuration PAGEREF _Toc82505546 h 3 HYPERLINK l _Toc82505547 Link Service Configuration PAGEREF _Toc82505547 h 3 HYPERLINK l _Toc82505548 IP-DLC Connection Configuration PAGEREF _Toc82505548 h 3 HYPERLINK l _Toc82505549 HIS 200

13、4 Supported Features over IP-DLC PAGEREF _Toc82505549 h 3 HYPERLINK l _Toc82505550 Fault Tolerance and Load Balancing Features PAGEREF _Toc82505550 h 3 HYPERLINK l _Toc82505551 Fault Tolerance Features PAGEREF _Toc82505551 h 3 HYPERLINK l _Toc82505553 Scalability PAGEREF _Toc82505553 h 3 HYPERLINK l

14、 _Toc82505554 IP-DLC Link Service Limitations PAGEREF _Toc82505554 h 3 HYPERLINK l _Toc82505555 Supported Network Configurations with Dependent LUs PAGEREF _Toc82505555 h 3 HYPERLINK l _Toc82505556 Direct IPDLC Connection to CS/390 (DLUS) and NNS PAGEREF _Toc82505556 h 3 HYPERLINK l _Toc82505557 IPD

15、LC Connection to CS/390 (DLUS) through Separate NNS PAGEREF _Toc82505557 h 3 HYPERLINK l _Toc82505558 Separate IPDLC Connections to CS/390 (DLUS) and NNS PAGEREF _Toc82505558 h 3 HYPERLINK l _Toc82505559 Simultaneous IPDLC Connections to Multiple CS/390 Hosts PAGEREF _Toc82505559 h 3 HYPERLINK l _To

16、c82505560 PU Concentration with Multiple IPDLC Host Connections PAGEREF _Toc82505560 h 3 HYPERLINK l _Toc82505561 Supported Network Configurations with Independent LUs PAGEREF _Toc82505561 h 3 HYPERLINK l _Toc82505562 IPDLC Connection to APPN “Peer-to-Peer” Network PAGEREF _Toc82505562 h 3 HYPERLINK

17、 l _Toc82505563 IP-DLC Connection to APPN “Peer-to-Peer” Network PAGEREF _Toc82505563 h 3 HYPERLINK l _Toc82505564 Secure Deployment PAGEREF _Toc82505564 h 3 HYPERLINK l _Toc82505565 UDP Sockets for HPR/IP Protocol Traffic PAGEREF _Toc82505565 h 3 HYPERLINK l _Toc82505566 Firewall Configuration PAGE

18、REF _Toc82505566 h 3 HYPERLINK l _Toc82505567 Securing HIS 2004 IP-DLC Connections PAGEREF _Toc82505567 h 3 HYPERLINK l _Toc82505568 Problem Determination and Troubleshooting PAGEREF _Toc82505568 h 3 HYPERLINK l _Toc82505569 Event Logs PAGEREF _Toc82505569 h 3 HYPERLINK l _Toc82505570 Four types of

19、IP-DLC Event logs PAGEREF _Toc82505570 h 3 HYPERLINK l _Toc82505571 Typical IP-DLC Link Service Event Log Entry PAGEREF _Toc82505571 h 3 HYPERLINK l _Toc82505572 UDP Trace PAGEREF _Toc82505572 h 3 HYPERLINK l _Toc82505573 Internal Trace PAGEREF _Toc82505573 h 3 HYPERLINK l _Toc82505574 Crash Dumps P

20、AGEREF _Toc82505574 h 3 HYPERLINK l _Toc82505575 Diagnostic Gathering Tool PAGEREF _Toc82505575 h 3 HYPERLINK l _Toc82505576 Diagnosing Misconfiguration PAGEREF _Toc82505576 h 3 HYPERLINK l _Toc82505577 Detailed Diagnostics Tool PAGEREF _Toc82505577 h 3 HYPERLINK l _Toc82505578 Qryipdlc Command Line

21、 Syntax PAGEREF _Toc82505578 h 3 HYPERLINK l _Toc82505579 Qryipdlc from Diagnostics Tool (Display.exe) PAGEREF _Toc82505579 h 3 HYPERLINK l _Toc82505580 QRYIPDLC Sample Output PAGEREF _Toc82505580 h 3 HYPERLINK l _Toc82505581 Performance Monitor Statistics PAGEREF _Toc82505581 h 3 HYPERLINK l _Toc82

22、505582 APPENDIX A - Concepts and Terminology PAGEREF _Toc82505582 h 3 HYPERLINK l _Toc82505583 APPENDIX B - Glossary PAGEREF _Toc82505583 h 3 HYPERLINK l _Toc82505584 APPENDIX C - Qryipdlc (Full Log) PAGEREF _Toc82505584 h 3 HYPERLINK l _Toc82505585 APPENDIX D - Automated Configuration PAGEREF _Toc8

23、2505585 h 3 HYPERLINK l _Toc82505586 LinkCFG PAGEREF _Toc82505586 h 3 HYPERLINK l _Toc82505587 SNACFG PAGEREF _Toc82505587 h 3 HYPERLINK l _Toc82505588 WMI PAGEREF _Toc82505588 h 3 HYPERLINK l _Toc82505589 REFERENCES PAGEREF _Toc82505589 h 3Introduction TC Introduction f C l 1 Host Integration Serve

24、r (HIS) 2004 offers an efficient means to integrate Systems Network Architecture (SNA) within data centers, across wide area networks (WANs) and in branch offices through a new link service, IP-DLC (Internet Protocol Date Link Control), also known as IBM Enterprise Extender. The IP-DLC link service

25、provides SNA connectivity for applications using dependent and independent sessions over a native IP network.SNA has evolved from the traditional subarea networks. Advanced Peer-to-Peer Networking (APPN) was an enhancement to SNA that brought the ability to move logical units and change routing with

26、out coordinated system definition. High Performance Routing (HPR) is an extension of the APPN architecture; it provides the following functions:Rapid Transport Protocol (RTP) minimizes processing cycles and storage requirements for routing network layer packets through intermediate nodes on a sessio

27、n route.Automatic network routing (ANR) enables APPN networks to automatically reroute sessions if a portion of the originally computed route fails.Enterprise Extender (EE) is another evolution, providing a means for the efficient transport of SNA data across an IP network. Enterprise Extender is an

28、 industry-standard solution defined by IETF (RFC 2353). With Enterprise Extender, the RTP endpoint views its interface with the UDP layer of the stack as just another data link control, and treats the connection across the IP network the same as it would any SNA connection.This purpose of this White

29、 Paper is to assist Mainframe Programmers and HIS 2004 administrators in configuring for IP-DLC. It also serves as a reference for HIS 2004, to be used in conjunction with online help in diagnosing and troubleshooting connectivity and configuration issues. IP-DLC Configuration (Mainframe) TC IP-DLC

30、Configuration (Mainframe) f C l 1 This section describes how to configure IPDLC support on an IBM Mainframe running the OS/390 or z/OS operating system. IPDLC is also known as IBM Enterprise Extender.To support IPDLC on OS/390, you need OS/390 (version 2.7 or later) or z/OS.Host Requirements TC Host

31、 Requirements f C l 2 “IBM Enterprise Extender” solutionOS/390 (V2R7 or higher) or z/OSCommunication Server for OS/390 V6 or higherNetwork Adapter Requirements TC Network Adapter Requirements f C l 2 OSA or OSA Express Modes SNA and TCP/IP (non-QDIO)TCP/IP only (QDIO)The OS/390 VTAM and TCP/IP compo

32、nents must be configured as follows: TC OS/390 VTAM and TCP/IP components Configuration f C l 2 Switch on the HPR support and CP-CP session support start optionsDefine an XCA (External Communications Adapter) Major Node for HPR/IPEnable VTAM to be a TCP/IP application.Switched Major Nodes for PUs SY

33、S1.VTAMST(member)Each of the configuration steps above is described briefly in the following sections. For more detailed explanations on configuring Enterprise Extender as well as additional examples from the VTAM and TCP/IP configuration files (including a Switched Major Node Definition for some of

34、 the Physical Units), see the following IBM manuals and White Paper:OS/390 eNetwork Communications Server SNA Resource Definition Reference (SC31-8565-02)OS/390 eNetwork Communications Server IP Configuration (SC31-8513-02) HYPERLINK :/ 1.ibm /servers/eserver/zseries/library/techpapers/enterprise_ex

35、tender.html 1. HPR and CP-CP Session Start Option (SYS1.VTAMLST(ATCSTR00) TC 1. HPR and CP-CP Session Start Option (SYS1.VTAMLST(ATCSTR00) f C l 3 The HPR and CP-CP Session start options are set by adding the following line to the start options in SYS1.VTAMLST(ATCSTR00): HPR=RTP,CPCP=YESA typical AT

36、CSTR00 file is displayed below:CONFIG=00,SUPP=NOSUP, SSCPID=06,NOPROMPT, HOSTSA=1,SACONNS=YES, SSCPNAME=P390,HOSTPU=P390$PU, NETID=APPN, NODETYPE=NN,CPCP=YES, DYNLU=YES,CDSERVR=YES,HPR=RTP,CDRDYN=YES,CONNTYPE=APPN,DYNADJCP=YES, CMPVTAM=4,BN=YES, DIRTIME=90000S, CRPLBUF=(208,15,1,16), IOBUF=(400,508,

37、19,1,20), LFBUF=(104,0,1,1), LPBUF=(64,0,1,1), SFBUF=(163,0,1,1) */* */* LIB: SYS1.VTAMLST(ATCSTR00) */* GDE: CBIPO COMMUNICATIONS */* DOC: THIS MEMBER CONTAINS THE ACF/VTAM DEFAULT */* START OPTIONS ON THE MODEL INSTALLATION SYSTEM. */* 2. XCA Major Node (SYS1.VTAMLST(member) TC 2. XCA Major Node (

38、SYS1.VTAMLST(member) f C l 3 A new dataset member containing an IPDLC XCA Major Node definition must be added to SYS1.VTAMLST. An example of SYS1.VTAMLST is displayed below:*/* SYS1.VTAMLST(XCAE40EE) */* */* */* ENTERPRISE EXTENDER OVER TOKEN RING ADAPTER1 (E40) */* */* */* XCAE40EE VBUILD TYPE=XCA

39、*/* XPE40EE PORT MEDIUM=HPRIP, -VNNAME=EEJEB, -VNGROUP=EEGRPJ, -LIVTIME=15, -SRQTIME=15, -SRQRETRY=9, -SAPADDR=04 */* EEGRPJ GROUP ANSWER=ON, -AUTOGEN=(64,L,P), -CALL=INOUT, -DIAL=YES, -DYNPU=YES, -DYNPUPFX=$E, -ISTATUS=ACTIVE */* It may be possible to add the new dataset member to the list of nodes

40、 that are activated during VTAM startup (SYS1.VTAMLST(ATCCON00). However, in order to do so, the TCP/IP stack first requires initialization. If adding the dataset member to the VTAM startup fails, try adding it to the VTAM application startup list (SYS1.PARMLIB(VTAMAPPL) by appending the following l

41、ines:v net,act,id=xcae40ee (id= should be the XCA member name)Pause 120The Pause command is specified in seconds and should be coded long enough to let TCP/IP initialize on the target platform. An example of a VTAMAPPL file is displayed below:CommandPrefix=None /* This is the default value */*/* Aut

42、omatically Start Several VTAM Applications */*/Pause 10 /* Wait for sys to get up first */S vlf,sub=mstrPause 10 /* Wait for sys to get up first */S lla,sub=mstrS Tcas /* Time Sharing Option */*S rmf*/ /* RMF */S tcpip/*s irlmproc*/Pause 10 /* Wait for sys to get up first */* s imwebsrv */* s nfss *

43、/Pause 10 /* Wait extended for TCAS */s sdsfs cicsaPause 135 /* Wait extended for TCAS */v net,act,id=xcae40eePause 120$S LOGON(1)Pause 30$s LINE(*)Pause 30$s RMT(*)Pause 60S BAZ1Pause 60F BAZ1,S,ALLPause 60S NVDMPause 60F NVDM,START/*-START DB2*/D T /* Display Ending time */* Comment lines may also

44、 start with a single asterisk.* Remember - blank lines are a BIG no-no.*CommandPrefix=) /* Require all Vtamappl commands to start with ) */* * * IPL startup is complete! * * Have a nice day! qryipdlcMicrosoft (R) Microsoft Host Integration Server IP-DLC Detailed Diagnostics Tool Version 6.0.1701.0 C

45、opyright (C) 1993-2004 Microsoft CorporationThe syntax of this command is: QRYIPDLC /S server-name /L link-service-names /A /O output-file-name /? Prints this usage message. /S server-name The name of the server on which the IP-DLC link services are running. If omitted, the local machine is assumed.

46、 /L link-service-names The names of the IP-DLC link services to query, separated by semicolons (e.g. snaip1;snaip2). If omitted, all IP-DLC link services will be queried. /A Append to the output file. /O output-file-name The name of the file to write the diagnostics to.An example of a typical comman

47、d line syntax (if running on the HIS 2004 machine) is shown below: Qryipdlc from Diagnostics Tool (Display.exe) TC Qryipdlc from Diagnostics Tool (Display.exe) f C l 3 Secondly, you can execute Qryipdlc via the Diagnostics Utility from the Tools menu in SNA Server manager. Configure the Server name

48、or IP Address in the appropriate field and click on Status button. The Diagnostics tool will automatically query all link services configured on the server. A copy of the log file is automatically saved to the traces directory with the name of .QRYIPDLC Sample Output TC QRYIPDLC Sample Output f C l

49、3 The Qryipdlc utility interrogates the selected link service(s) and prints detailed state information (either to a file specified via command line or QueryIPDLC.txt via Diagnostics tool). Note however, that this information is intended for use by Product Support Services (PSS) to aid in problem dia

50、gnosis. The file is retained on disk so that it can be sent to PSS if necessary.The following is an excerpt from a Qryipdlc log (see Appendix C for a complete Qryipdlc log).Detailed Diagnostics for IP-DLC Link Service SNAIP1 on HISERVER Created at Tue Aug 03 2004 16:46:52 Pacific Time.Link Service S

51、tatusCreate parameters: Node type Branch Network Node FQCP name MYNET.HISERVER CP alias HISERVER Node ID (IDBLK/IDNUM) X05D.FFFFFNetwork Node Server StatusLS name | State | Adjacent CP name | Default NNS | Remote address+N000001 | Active | MVSRUS.P390SSCP | Yes | MVSRUSPeer Connection StatusHost Con

52、nection StatusConnection name | Internal LS state | External LS state | External LS name | Preferred route+MVSRUS | Active | N/A | None | NoneInternal Link Station StatusLink station name MVSRUS Determined data: Link station state Active Link station sub-state Active Adjacent CP name IPDLCNET.C00000

53、1 Adjacent CP type End NodeExternal Link Station StatusRTP Connection StatusRTP connection name | First hop LS name | Destination node name | COS name | # active sessions+R000001 | N000001 | MVSRUS.P390SSCP | CPSVCMG | 2R000002 | N000001 | MVSRUS.P390SSCP | SNASVCMG | 2R000003 | N000001 | MVSRUS.P39

54、0SSCP | RSETUP | 0R000007 | N000001 | MVSRUS.P390SSCP | #CONNECT | 1Performance Monitor Statistics TC Performance Monitor Statistics f C l 2 The IPDLC link service supports performance monitor counters. The following HIS performance monitor counters are included when installing an IP-DLC link servic

55、e:TotalBytesThroughputTotalFramesThroughputTotalBytesReceivedTotalBytesTransmittedTotalFramesReceivedTotalFramesTransmittedSuccessfulConnectsConnectionFailuresAdapterFailures.Note: all of the counters above are visible in the Windows Performance Monitor while the IPDLC link service is running.APPEND

56、IX A - Concepts and Terminology TC APPENDIX A - Concepts and Terminology f C l 1 This section is a brief introduction to the terminology and concepts that are referred to in this document, including APPN and HPR. For a more complete description of APPN and HPR, a good book is “Inside APPN and HPR: T

57、he Essential Guide to New SNA” by Brian Dorling, Peter Lenhard, Peter Lennon, Velibor Uskokovic, Prentice Hall, 1997.SessionA session is a logical connection between two network accessible units (NAUs). The most common example of an NAU is a Logical Unit (see below).Physical Unit (PU)The component t

58、hat manages and monitors the resources (such as attached links and adjacent link stations) associated with a node. This term applies to non-APPN nodes only.Logical Unit (LU)A Logical Unit (LU) is a port through which an application or end user accesses the SNA network in order to communicate with an

59、other application or end user. An LU may be capable of supporting many sessions with other LUs.Dependent LUA Dependent LU is an LU that requires assistance from a mainframe to establish a session with another LU. These are also sometimes referred to as “old LUs”.Independent LUAn Independent LU is an

60、 LU that can establish a session with another LU without the assistance of a mainframe.APPNAdvanced Peer-to-Peer Networking (APPN) is a network architecture that supports distributed network control. It makes networks easier to configure and use, provides centralized network management, and supports