2216/N etw ork U tility (LS A ) P aram eter - R ... - IBM Redbooks

IBM 2216 and Network Utility
Host Channel Connections
Erol Lengerli, Jacinta Carbonell, Thomas Grueter
International Technical Support Organization
http://www.redbooks.ibm.com
SG24-5303-00

International Technical Support Organization
SG24-5303-00
IBM 2216 and Network Utility Host Channel Connections
March 1999

Take Note!
Before using this information and the product it supports, be sure to read the general information in Appendix A,
“Special Notices” on page 287.
First Edition (March 1999)
This edition applies to IBM 2216 Nways Multiaccess Connector and the IBM Network Utility for use with the MVS and
VM operating systems.
Comments may be addressed to:
IBM Corporation, International Technical Support Organization
Dept. HZ8 Building 678
P.O. Box 12195
Research Triangle Park, NC 27709-2195
When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way
it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 1999. All rights reserved.
Note to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions
set forth in GSA ADP Schedule Contract with IBM Corp.

Contents
Figures ......................................................vii
Preface ..................................................... xiii
The Team That Wrote This Redbook . ..................................xiii
CommentsWelcome ...............................................xiv
Chapter 1. Host Connectivity Overview. ............................1
1.1 AttachmentofI/ODevices .....................................1
1.1.1 S/370I/Ointerface .......................................2
1.1.2 ESA/390ESCONI/OInterface ..............................2
1.2 S/390ServerAccessGatewayOptions............................2
1.2.1 3172 Interconnect Controller . . . .............................3
1.2.2 OpenSystemsAdapter(OSA)...............................3
1.2.3 3745/3746 Communications Controllers .......................4
1.2.4 3174 Establishment Controller . .............................5
1.2.5 2216 Multiprotocol Connector . . .............................5
1.2.6 RISC System/6000 Gateway Function. . .......................6
Chapter 2. ESCON Channel Attachment ............................7
2.1 ESCON Channel Overview . . . ..................................7
2.1.1 Channel Elements ........................................7
2.1.2 CommunicationPath.....................................10
2.1.3 InformationandAddressingStructure........................10
2.1.4 I/OOperations..........................................11
2.2 HostAttachment............................................12
2.2.1 BasicMode............................................12
2.2.2 LPARMode............................................13
2.2.3 EMIFMode............................................13
2.3 2216 ESCON Overview. ......................................14
2.3.1 2216 ESCON Channel Adapter . ............................14
2.3.2 2216 ESCON Channel Adapter Features .....................15
2.3.3 2216 ESCON Channel Protocols. ...........................16
2.3.4 2216 ESCON Channel implementation . ......................17
2.3.5 ESCON Channel Attachment Support . . ......................20
Chapter 3. Sample Host Definitions. ..............................27
3.1 Overview.................................................27
3.2 Definitions at the Channel Subsystem Level . ......................27
3.2.1 SampleHostIOCPDefinitions..............................28
3.3 Defining the 2216 in the Operating System . . ......................31
3.3.1 2216 Definition for VM/SP .................................31
2216 Definition for VM/XA and VM/ESA . . . ...........................31
3.3.2 2216 Definition for MVS/XA and MVS/ESA without HCD ..........31
3.3.3 2216 Definition for MVS/ESA with HCD. ......................32
3.3.4 Network Utility Definition for VSE/ESA . ......................32
3.4 VTAMDefinitions ...........................................33
3.4.1 VTAMXCAMajorNodeDefinition...........................33
3.4.2 VTAM Definitions for an MPC+ Connection . . . .................34
3.4.3 VTAMDefinitionsforAPPN................................36
3.4.4 VTAM Static Definition of TN3270 Resources . .................36
3.4.5 VTAM Dynamic Definition of TN3270 Resources. ...............38
© Copyright IBM Corp. 1998 iii

3.4.6 DynamicDial-InExitOverview............................. 40
3.4.7 ImplementingDynamicDefinitions.......................... 40
3.5 HostIPDefinitions.......................................... 41
3.5.1 DEVICEStatement ..................................... 41
3.5.2 LINKStatement........................................ 42
3.5.3 HOMEStatement....................................... 42
3.5.4 GATEWAYStatement................................... 43
3.5.5 STARTStatement......................................44
3.5.6 HostTCP/IPDefinitionsforLCS ...........................44
3.5.7 HostTCP/IPDefinitionsforMPC+.......................... 45
3.6 HostHPDTUDPDefinitions .................................. 45
3.6.1 oeifconfig............................................. 46
3.6.2 oeroute .............................................. 47
3.6.3 oeping ...............................................48
3.6.4 oenetstat ............................................. 48
Chapter 4. Link Services Architecture ............................ 49
4.1 2216 LSA Support . ......................................... 49
4.1.1 LSA Direct Connection. .................................. 49
4.1.2 LSA DLSw Connection. .................................. 50
4.1.3 LSA APPN Connection .................................. 52
4.2 LLC Loopback ............................................. 54
4.3 2216 LSA vs. Host Parameter Relationships . . . ................... 55
4.4 LSA SNA Support Examples .................................. 59
4.4.1 HostDefinitions........................................ 59
4.4.2 LSA Direct Connection. .................................. 62
4.4.3 LSA Remote DLSw Connection . . . ......................... 69
4.4.4 LSA Local DLSw Connection (FR BAN) . . . ................... 87
4.4.5 LSA Local DLSw Connection (SDLC). ....................... 99
4.5 LSA APPN Support Example ................................. 112
4.5.1 HostDefinitions....................................... 112
4.5.2 NetworkEnvironmentDescription ......................... 113
4.5.3 2216 Configuration . ................................... 113
4.5.4 2216 Monitoring ....................................... 125
Chapter 5. LAN Channel Station ................................ 131
5.1 2216 LCS Support . ........................................ 131
5.1.1 LCSRouting ......................................... 132
5.1.2 LCSBridging......................................... 133
5.1.3 LCS 3172 Emulation Support. ............................ 135
5.2 2216 LCS vs Host Parameter Relationships . . . .................. 136
5.3 LCSConfigurationExamples................................. 139
5.3.1 HostDefinitions....................................... 139
5.3.2 LCS Routing Support ................................... 150
5.3.3 LCS Bridging Support .................................. 157
5.3.4 LCS 3172 Emulation Support. ............................ 161
Chapter 6. Multipath Channel+ Implementation (MPC+) ............. 169
6.1 2216 MPC+ Support ....................................... 169
6.2 2216 MPC+ Host Parameter Relationships ...................... 170
6.3 HostDefinitions........................................... 173
6.3.1 IOCPandMVSOperatingSystemDefinitions................ 173
6.3.2 VTAM Definitions for an MPC+ Connection .................. 173
6.3.3 TCP/IP DefinitionforMVS .............................. 175
iv IBM 2216 and Network Utility Host Channel Connections

6.3.4 2216 MPC+ and APPN . . ................................178
6.3.5 MPC+ConfigurationforAPPN ............................179
6.3.6 Add the APPN Package to the 2216 . . . .....................180
6.3.7 DefinethePhysicalInterfaces.............................180
6.3.8 Add/ConfigureMPC+VirtualInterface.......................181
6.3.9 Configure an MPC+ Subchannel ...........................183
6.3.10 ConfigureAPPN......................................184
6.4 2216 MPC+ and TCP/IP .....................................190
6.5 MonitoringESCONInterface..................................194
6.5.1 MonitoringESCONMPC+Interface ........................195
6.5.2 APPNMonitoring.......................................198
6.5.3 IPMonitoring..........................................200
6.6 2216 MPC and UDP. . ......................................201
6.6.1 2216 MPC+ Host Parameter Relationships . . . ................201
6.6.2 HostDefinitions........................................204
6.6.3 MonitoringESCONInterface..............................213
Chapter 7. TN3270 Server Channel-Attached Configuration ..........219
7.1 2216 vs Host Parameters Relationship ..........................219
7.1.1 TN3270E with LSA-SNA . ................................220
7.1.2 TN3270E with LSA-APPN/DLUR ...........................222
7.1.3 TN3270E with MPC+ and APPN/DLUR . .....................224
7.2 TN3270E Configuration Using SNA Subarea Links . ................226
7.2.1 NetworkEnvironmentDescription..........................226
7.2.2 HostProgramsDefinitions................................227
7.2.3 2216 Configuration .....................................229
7.2.4 2216 Monitoring . ......................................238
7.3 TN3270E Server Configuration with APPN/DLUR Links . . . ..........241
7.3.1 NetworkEnvironmentDescription..........................241
7.3.2 HostProgramsDefinitions................................242
7.3.3 2216 Configuration .....................................244
7.3.4 2216 Monitoring . ......................................251
Chapter 8. ESCON/PCA Comparison .............................255
8.1 HostPointofView.........................................255
8.2 2216 Point of View . . . ......................................256
Chapter 9. Backup Scenario. ...................................259
9.1 ESCON Channel Gateway - High Availability .....................259
9.1.1 NetworkEnvironmentDescription..........................259
9.1.2 HostProgramsDefinitions................................262
9.1.3 2216A Configuration ....................................264
9.1.4 2210A Configuration ....................................268
9.1.5 2216B Configuration ....................................271
9.1.6 2210B Configuration ....................................275
9.2 LSA Direct Connection Backup ................................278
9.2.1 NetworkEnvironmentDescription..........................278
9.2.2 RecoveryatHostFailure.................................279
9.2.3 Recovery at 2216 Channel Failure .........................279
9.2.4 HostProgramDefinitions ................................280
9.2.5 2216 Configuration .....................................281
v

Appendix A. Special Notices ......................................287
Appendix B. Related Publications .................................289
B.1 International Technical Support Organization Publications . . . ...........289
B.2 Redbooks on CD-ROMs . . . .....................................289
B.3 OtherPublications.............................................289
How to Get ITSO Redbooks .................................... 291
IBM Redbook Fax Order Form . . .....................................292
Index ...................................................... 293
ITSO Redbook Evaluation ..................................... 295
vi IBM 2216 and Network Utility Host Channel Connections

Figures
1. ESCONElements ...............................................8
2. ESCONI/OInterfaceAddressing...................................11
3. BasicMode ...................................................13
4. LPARMode...................................................13
5. EMIFMode....................................................14
6. IBM Channel Connectivity ........................................17
7. 2216 ESCON Channel Adapter Implementation . . .....................18
8. LAN to Subchannel Configuration ..................................19
9. Single ESCON Connection Example ................................21
10. Multiple System ESCON Connections Example . . .....................22
11. 2216 EMIF Attachment Example . ..................................22
12. LCS Subchannels Policy . ........................................24
13. LSA Subchannel Policy . . ........................................25
14. MPC+ Channel Policy . . . ........................................26
15. Sample Host IOCP Definitions for the 2216 (ESCON). ..................28
16. Sample Host IOCP Definitions for the 2216 (PCA) .....................30
17. 2216 Definitions for VM/SP .......................................31
18. VM/XAHCPRIODefinitionExample ................................31
19. VM/ESAHCPRIODefinitionExample...............................31
20. IODEVICE Macro for ESCON Channels Example. .....................31
21. IODEVICE Macro for Parallel Channels Example . .....................32
22. 2216 HCD Definition Example . . . ..................................32
23. Parallel Channel Definition without HCD for MVS/ESA ..................32
24. ESCON Channel Definition without HCD for MVS/ESA. .................32
25. 2216 Definition for VSE/ESA ......................................33
26. XCA Major Node Definition Sample for LSA Direct Connection . . . ........33
27. VTAMLocalMajorNodeDefinition .................................35
28. VTAMTransportResourceList(TRL)Definition.......................35
29. VTAMStartupParameters........................................36
30. VTAM Definitions for a TN3270E Server PU (DLUR/APPN) ..............37
31. VTAM Definitions for a TN3270E Server PU (Subarea) . . . ..............37
32. VTAMDynamicResourceDefinition................................39
33. LSA Direct Connection Appearance ................................50
34. LSARemoteDLSwConnectionAppearance..........................51
35. LSA Local DLSw Connection Appearance. ...........................51
36. LSAAPPNConnection ..........................................53
37. LLC Normal Connection vs. LLC Loopback Connection . . . ..............54
38. SNA Connection: 2216 LSA Host Parameter Relationship . ..............56
39. APPN Connection: 2216 LSA Host Parameter Relationship ..............58
40. LSA:IOCPandMVSOperatingSystemDefinitions ....................60
41. LSA:XCAMajorNodeDefinitions..................................60
42. LSA:SwitchedMajorNodeDefinitions ..............................61
43. OverviewofLSADirectTestEnvironment............................62
44. AddingthePhysicalInterfacestothe2216...........................63
45. ListoftheDevicesinsidethe2216 .................................63
46. SettingtheMACAddressoftheToken-RingInterface ..................63
47. AddingtheLSAVirtualInterface ...................................64
48. Configure an LSA Subchannel. . . ..................................65
49. ListoftheInterfacesinsidethe2216................................66
50. InterfaceListviaGWCON........................................66
© Copyright IBM Corp. 1998 vii

51. Change to the ESCON Base Net Prompt .............................66
52. List of Net and Subchannel from ESCON Base Net Prompt. . . ............67
53. List of Subcommands for the LSA Interface . . .........................67
54. List of Virtual Adapter ............................................68
55. ListSAPforLSA................................................68
56. ListLinkInformationforLSA.......................................69
57. LSA DLSw Connection Network Setup ...............................70
58. LSA DLSw: Adding the Physical Adapters to the 2216. ..................71
59. LSADLSw:LSAConfiguration.....................................71
60. LSA DLSw: LSA Subchannel Configuration . . .........................72
61. LSADLSw:IPConfiguration.......................................74
62. LSADLSw:ASRTConfiguration....................................76
63. LSADLSw:DLSwConfiguration....................................78
64. LSADLSw:ActivatingConfiguration.................................79
65. LSADLS:2210InterfaceConfiguration ..............................80
66. LSADLSw:2210IPConfiguration ..................................81
67. LSADLSw:2210ARSTConfiguration...............................82
68. LSADLSw:2210DLSwConfiguration...............................82
69. LSADLSw:2210ActivatingtheConfiguration.........................83
70. LSADLSw:InterfaceStateMonitoring...............................83
71. LSADLSw:LSAInterfaceMonitoring................................84
72. LSADLSw:DLSwMonitoring......................................86
73. LSADLSw:DLSwMonitoring......................................87
74. LSA Local DLSw Connection Network Setup . .........................88
75. LSALocalDLSw:2216ESCONInterfaceConfiguration .................89
76. LSALocalDLSw:2216FRInterfaceConfiguration .....................90
77. LSALocalLSA:2216IPConfiguration...............................91
78. LSALocalDLSw:2216BridgingConfiguration.........................91
79. LSALocalDLSw:2216DLSwConfiguration ..........................92
80. LSALocalDLSw:2216ActivatingtheConfiguration ....................92
81. LSA Local DLSw: 2210 FR Configuration . . . .........................93
82. LSALocalDLSw:2210BridgingConfiguration.........................94
83. LSALocalDLSw:2210BANConfiguration ...........................95
84. LSA Local DLSw: Activating the 2210 Configuration . ...................95
85. LSA Local DLSw: Listing of ESCON Subnets under DLSw . . . ............96
86. LSALocalDLSw:LSAInterfaceMonitoring...........................97
87. LSALocalDLSw:DLSwMonitoring.................................98
88. LSALocalDLSw:2210Monitoring..................................99
89. LSA Local DLSw Connection Network Setup (SDLC) ..................100
90. AddingthePhysicalInterfaceandDisplayNewStatus .................101
91. Adding the V.25bis Address . .....................................101
92. Configuring V.25bis Parameters ...................................102
93. AddingaDialCircuit............................................103
94. ConfiguringaDialCircuit ........................................103
95. Add/ConfigureLSAInterface .....................................104
96. SettingtheInternalIPAddress....................................104
97. ConfiguringtheDLSProtocol.....................................105
98. InterfaceListviaGWCON........................................107
99. Change to the ESCON Base Net Prompt ............................107
100.List of Net and Subchannel from the ESCON Base Net Prompt ..........107
101.List of Subcommands for the LSA Interface . . ........................108
102.List of Virtual Adapters ..........................................108
103.List of SAPs for LSA . ...........................................109
viii IBM 2216 and Network Utility Host Channel Connections

104.List of Link Information for LSA . . .................................109
105.List of TCP Sessions ...........................................110
106.List of DLS Sessions ...........................................110
107.List of SDLC Config ............................................111
108.List of SDLC Sessions . . . .......................................111
109.List of Link Configuration . .......................................111
110.List of All Stations .............................................112
111.LSA APPN: Switched Major Node Definitions ........................112
112.Overview of the APPN-LSA Test Environment . . . ....................113
113.Adding the APPN Package to the 2216. . . ..........................114
114.Adding the Physical Interfaces to the 2216 ..........................115
115.List of the Devices inside the 2216 ................................115
116.Setting the MAC Address of the Token-Ring Interface .................115
117.Adding the LSA Virtual Interface . .................................116
118.Enable Loopback for the LSA Interface. . . ..........................116
119.Configure an LSA Subchannel . . .................................117
120.List of the Interfaces inside the 2216 ...............................118
121.Adding the APPN Loopback Interface ..............................119
122.Setup of the 2216 for APPN Readiness . . ..........................119
123.List of the Interfaces inside the 2216 ...............................120
124.Add the APPN Port for the Token-Ring Interfaces ....................120
125.Add the Port and Link to the EIA Interface for APPN ..................121
126.Add the Port and the Link to the Loopback APPN-Channel Interface .....122
127.Set Up the 2210 for APPN Readiness. .............................123
128.Add the APPN Port for the Token-Ring Interfaces on 2210 .............123
129.Adding the Port and the Link to the WAN Interface of the 2210 . . . .......124
130.Interface List via GWCON .......................................125
131.Change to the ESCON Base Net Prompt . ..........................125
132.List of Nets and Subchannels from ESCON Base Net Prompt ...........126
133.List of Subcommands for the LSA Interface .........................126
134.List of Virtual Adapter . . . .......................................127
135.List SAP for LSA . .............................................127
136.List Link Information for LSA .....................................128
137.Overview of Test Environment. . . .................................129
138.List of Ports in APPN ...........................................129
139.List of Links in APPN ...........................................129
140.List of CP Sessions in APPN. ....................................130
141.List of APPC Sessions. . . .......................................130
142.RTP Connection Table . . .......................................130
143.LCS Routing Support Appearance ................................133
144.LCS Bridging Support Appearance ................................134
145.LCS 3172 Emulation Support Appearance ..........................136
146.2216 LCS Host Parameter Relationship . . ..........................138
147.LCS: IOCP and MVS Definitions . .................................140
148.LCS: orouted Definitions . .......................................149
149.LCS TCP/IP Routing Scenario. . . .................................150
150.LCS Routing: Adding the Physical Adapters to the 2216 . . .............151
151.LCS Routing: TKR Configuration. .................................151
152.LCS Routing: PPP Configuration. .................................152
153.LCS Routing: LCS Interface Configuration ..........................152
154.LCS Routing: LCS Subchannels Configuration . . . ....................153
155.LCS Routing: Network Numbers Information. ........................154
156.LCS TCP/IP Routing Support: IP Config . . ..........................155
ix

157.LCS Routing Interface Monitoring . . ...............................156
158.LCS Routing: IP Monitoring . .....................................157
159.LCS Bridging Scenario ..........................................158
160.LCS Bridging: ASRT Configuration . ...............................159
161.LCS Bridging Interface Monitoring . . ...............................160
162.LCS Bridging: ASRT Monitoring ...................................161
163.LCS 3172 Emulation Network Setup ...............................162
164.LCS 3172 Emulation: Adding Physical Interfaces . . . ..................163
165.LCS 3172 Emulation: Configuring the LAN Interface . ..................163
166.LCS 3172 Emulation: Configuring the LCS Interface . ..................164
167.LCS 3172 Emulation: LCS Subchannels Configuration .................165
168.LCS 3172 Emulation: Activating Configuration. .......................165
169.LCS 3172 Emulation Interface Monitoring . . . ........................166
170.MPC+ Host Parameter Relationship for IP and APPN Protocol ...........172
171.MPC+: IOCP and MVS Operating System Definitions ..................173
172.VTAM Local Major Node Definition . ...............................174
173.VTAM Transport Resource List (TRL) Definition ......................174
174.TCP/IP Profile Extract. ..........................................176
175.Start Statement from the TCP/IP Profile. ............................177
176.orouted Definitions . . ...........................................178
177.MPC+ Appearance between 2216 and Host for APPN .................179
178.Overview of the Test Environment . . ...............................180
179.Adding the APPN Package to the 2216 .............................180
180.Adding the Physical Interfaces to the 2216 . . ........................181
181.List of the Devices inside the 2216. . ...............................181
182.Adding the MPC+ Virtual Interface . ...............................182
183.Configure Read and Write Subchannel to the MPC+ . ..................183
184.List of the Devices inside the 2216. . ...............................184
185.Setup of the 2216 for APPN Readiness .............................184
186.Add the APPN Port to the Token-Ring Interfaces . . . ..................185
187.Add the Port and Link to the EIA Interface for APPN . ..................186
188.Add the Port and Link to the MPC+ Interface on the 2216. ..............187
189.Set up the 2210 for APPN Readiness ..............................188
190.Add the APPN Port for the Token-Ring Interfaces on 2210 . . . ...........188
191.Adding the Port and Link to the WAN Interface of the 2210. . . ...........189
192.MPC+ Appearance between 2216 and Host for TCP/IP ................190
193.MPC+ Appearance between 2216 and Host for TCP/IP and APPN. . . .....191
194.Test Environment for MPC+ and TCP/IP ............................192
195.List of the Devices inside the 2216. . ...............................192
196.Adding IP Address to the 2216 Interface ............................193
197.List of IP Addresses in the 2216. ..................................193
198.Adding IP Addresses to the 2210 Interface . . ........................193
199.Enable RIP and List of IP Addresses in the 2210 . . . ..................194
200.Interface List via GWCON . . .....................................194
201.Change to the ESCON Base Net Prompt. ...........................194
202.List of Net and Subchannels from ESCON Base Net Prompt . ...........195
203.List of Subcommand for the MPC+ Interface . ........................195
204.List of MPC+ Group . ...........................................196
205.List of MPC+ Subchannels . . .....................................196
206.List of MPC+ Connection Manager. . ...............................196
207.List of MPC+ Connections . . .....................................197
208.Test Environment with APPN and TCP/IP . . . ........................198
209.List of Ports in APPN ...........................................199
x IBM 2216 and Network Utility Host Channel Connections

210.List of Links in APPN ...........................................199
211.List of CP on APPN ............................................199
212.RTP Connection Table . . .......................................200
213.Dump Command on the IP Protocol ...............................200
214.MPC+ Host Parameter Relationship for UDP ........................203
215.MPC+: IOCP and MVS Operating System Definitions .................204
216.VTAM Transport Resource List (TRL) Definition . . ....................205
217. Sample for BPXPRMxx Member .................................206
218.MPC+ Appearance between 2216 and Host for UDP ..................207
219.Overview of the Test Environment. ................................207
220.Adding the Physical Interfaces to the 2216 ..........................208
221.List of the Devices inside the 2216 ................................208
222.Adding the MPC+ Virtual Interface ................................209
223.Set maxdata and enable UDP+ for the MPC+ Group ..................209
224.Configure Read and Write Subchannel to the MPC+ ..................211
225.List of the Devices inside the 2216 ................................212
226.Add IP Address to the Interfaces . .................................212
227.Interface List via GWCON .......................................213
228.Change to the ESCON Base Net Prompt . ..........................213
229.List of Net and Subchannel s from ESCON Base Net Prompt ...........214
230.List of Subcommands for the MPC+ Interface. .......................214
231.List of MPC+ Group ............................................215
232.List of MPC+ Subchannels ......................................215
233.List of MPC+ Connection Manager ................................216
234.List of MPC+ Connections .......................................216
235.Dump Command at the IP Protocol ................................217
236.TN3270E - LSA (SNA): 2216-Host Parameter Relationships ............221
237.TN3270E - LSA (APPN/DLUR): 2216-Host Parameter Relationships. .....223
238.TN3270E - MPC+ APPN/DLUR: 2216-Host Parameter Relationships .....225
239.TN3270E Server Configuration with SNA Subarea Links Network Setup . . . 227
240.TN3270E SNA: IOCP and MVS Operating System Definitions. ..........228
241.TN3270E SNA: XCA Major Node Definitions ........................228
242.TN3270E SNA: Switched Major Node Definitions . ....................229
243.TN3270E SNA: Adding the Physical Adapters to the 2216 .............230
244.TN3270E SNA: Adding the Packages ..............................231
245.TN3270E SNA Subarea Links: Configuring the LSA Interface ...........231
246.TN3270E SNA: APPN Loopback Interface Configuration . .............232
247.TN3270E SNA: Looking at Network Numbers. .......................232
248.TN3270E SNA: IP Configuration . .................................233
249.TN3270E SNA: Configuring APPN Support .........................235
250.TN3270E SNA: TN3270E Server Configuration . . ....................237
251.TN3270E SNA: Interface Status . .................................238
252.TN3270E SNA: LSA Monitoring. . .................................239
253.TN3270E SNA: TN3270E Server Monitoring. ........................240
254.TN3270E SNA: APPN Monitoring Commands . . . ....................241
255.TN3270E Server Using an APPN DLUR Link Network Setup ............242
256.TN3270E APPN/DLUR: IOCP and MVS Operating System Definitions ....243
257.TN3270E SNA: VTAM Transport Resource List (TRL) Definition . . .......243
258.TN3270E SNA: VTAM Local Major Node Definition ...................244
259.TN3270E SNA: Switched Major Node Definitions . ....................244
260.TN3270E APPN/DLUR: Loading the Packages . . ....................245
261.TN3270E APPN/DLUR: Listing the Packages. .......................245
262.TN3270 APPN/DLUR: Configuring the Interfaces . ....................246
xi

263.TN3270E APPN/DLUR: MPC+ Configuration ........................247
264.TN3270E APPN/DLUR: IP Configuration ............................247
265.TN3270E APPN/DLUR: APPN Configuration. ........................248
266.TN3270E APPN/DLUR: DLUR-TN3270E Server Configuration. ..........250
267.TN3270E APPN/DLUR: Interface Status ............................251
268.TN3270E APPN/DLUR: MPC+ Monitoring . . . ........................252
269.TN3270E APPN/DLUR: APPN Monitoring . . . ........................253
270.TN3270E APPN/DLUR: TN3270E Server Monitoring ..................253
271.Comparison between ESCON and PCA ............................257
272.ESCON Channel Gateway Backup Network Setup . . ..................260
273.BACKUP: IOCP Definitions . .....................................262
274.XCA Major Node 2216A Definitions . ...............................263
275.XCA Major Node 2216B Definitions . ...............................263
276.TCP/IP Definitions . . ...........................................264
277.2216A: DLSw Configuration . .....................................268
278.2216B: DLSw Configuration . .....................................275
279.LSA Direct Connection Backup ...................................279
280.Backup: IOCP Definitions . . . .....................................280
281.XCA Major Node Definitions on LPAR 1 ............................281
282.XCA Major Node Definitions on LPAR 4 ............................281
283.Adding the Devices. . ...........................................282
284.Configure the TR Adapter. . . .....................................282
285. Configure LSA on ESCON Adapter 1 ..............................283
286.Configure LSA on ESCON Adapter 2. ..............................284
287.Display the Active LSA Interface . . . ...............................285
xii IBM 2216 and Network Utility Host Channel Connections

Preface
This redbook will help you understand and use the functions offered by the IBM
2216 Nways Multiaccess Connector and the IBM Network Utility as host
channel-attached boxes. Proper understanding of the technology and following
the configuration examples given in this publication will be helpful in
implementing ESCON/parallel channel connections using the IBM 2216 and
Network Utility.
This redbook includes MPC+, LSA and LCS as channel protocols. In addition to
these channel protocols, such network protocols as TCP/IP, APPN/HPR,
APPN/ISR, SNA subarea, and DLSw, as well as TN3270E Server and 3172
emulation scenarios, are also included and presented with their corresponding
host (VTAM and TCP/IP) definitions.
The scenarios in this redbook were developed under Multiprotocol Access
Services (MAS) Version 3.2, but the LCS 3172 emulation section was run on MAS
Version 3.2 PTF 01.
The Team That Wrote This Redbook
This redbook was produced by a team of specialists from around the world
working at the International Technical Support Organization, Raleigh Center.
Erol Lengerli is an Advisory ITSO Specialist for Networking at the International
Technical Support Organization, Raleigh Center. He writes extensively and
teaches IBM classes worldwide on all areas of ATM/MSS switches, IBM 2216 and
Network Utility. Before joining the ITSO, Erol Lengerli worked in the Systems
Engineering and Networking departments in Turkey as a Networking Specialist.
Jacinta Carbonell works in IBM Routers for Fringes Systemas Informaticos, in
Valencia (Spain). She holds an Engineering degree in telecommunication and
has two years of experience in the networking field. She is part of the NHD
Valencia PE team, providing EMEA field support to IBM routers and she is also
involved in router courses given by Fringes Systemas Informaticos.
Thomas Grueter has been a Support Specialist for telecommunication hardware
in Germany for more than five years. He supports the IBM TP Controllers 37XX
including the IBM 3746-900/950 and the IBM NBBS Switch 2220. He was
assigned to the Technical Networking Support Center in La Gaude, France for
one year during which he provided EMEA-wide support for the IBM 2220 NBBS
Switch.
Thanks to the following people for their invaluable contributions to this project:
Carla Sadtler
Michael Haley
Tim Kearby
Jerzy Buczak
Karl Wozabal
Bob Haimowitz
International Technical Support Organization, Raleigh Center
© Copyright IBM Corp. 1998 xiii

Comments Welcome
Gail Christensen
Tate Renner
Shawn Walsh
Editing Team - International Technical Support Organization, Raleigh Center
James Goethals
Pat McClellan
John E Averi
Chris Chato
Larry E Troan
IBM NHD, Research Triangle Park,NC USA
Jan Devos
IBM Belgium
Your comments are important to us!
We want our redbooks to be as helpful as possible. Please send us your
comments about this or other redbooks in one of the following ways:
• Fax the evaluation form found in “ITSO Redbook Evaluation” on page 295 to
the fax number shown on the form.
• Use the online evaluation form found at http://www.redbooks.ibm.com.
• Send your comments in an Internet note to redbook@us.ibm.com.
xiv IBM 2216 and Network Utility Host Channel Connections

Chapter 1. Host Connectivity Overview
1.1 Attachment of I/O Devices
In this chapter, we concentrate on controllers that provide gateway functions for
mainframes running MVS or VM operating systems. The term local gateway is
used to refer to controllers that are channel attached to a host processor and
provide gateway functions for traffic between the mainframe host and the
downstream devices.
Logically, a system consists of main storage, one or more central processing units
(CPUs), operator facilities, a channel subsystem, and I/O devices. I/O devices are
attached to the channel subsystem through control units. The connection
between the channel subsystem and the control unit is called a channel path.
A channel path employs either a parallel transmission protocol or a serial
transmission protocol and, accordingly, is called either a parallel or a serial
channel path. A serial channel path may connect to a control unit through a
dynamic switch that is capable of providing different internal connections between
the ports of the switch.
Depending on the type of channel path, the facilities provided by the channel path
and the I/O device, an operation may occur in one of two modes, burst mode or
byte multiplex mode.
In burst mode, the I/O device monopolizes a channel path and stays logically
connected to the channel path for the transfer of a burst of information. No other
device can communicate over the channel path during the time a burst is
transferred. The facilities of the channel path capable of operating in burst mode
may be shared by a number of concurrently operating I/O devices.
In byte multiplex mode, the I/O device stays logically connected to the channel
path only for a short interval of time. In this mode all I/O operations are split into
shorts intervals of time during which only a segment of information is transferred
over the channel path. During such an interval, only one device and its associated
subchannel are logically connected to the channel path.
An I/O operation that occurs on a parallel I/O interface type of channel path may
occur in either mode, depending on the facilities provided by the channel path
and the I/O device.
An I/O operation that occurs on a serial I/O interface type of channel path may
occur only in burst mode.
These modes of operation affect only the protocol used to transfer information
over the channel path and the speed of transmission. No effects are observable
by CPU or channel programs with respect to the ways these programs are
executed.
The parallel channel is also called the S/370 I/O interface and the serial interface
is also called the ESCON (enterprise systems connection) channel.
© Copyright IBM Corp. 1998 1

1.1.1 S/370 I/O interface
The S/370 I/O interface uses two cables, called bus and tag cables. A bus cable
carries information and a tag cable indicates the meaning of the information on
the bus cable.
The bus and tag cables connect sequentially to all the control units. This is
referred to as daisy chaining. Daisy chaining better utilizes a channel for slow
control units, but a single failing control unit or a bad cable connection can
influence other control units chained on the channel.
The bus cable has a signal line for each bit value. A set of signal lines forming a
byte is called Bus Out and carries information from the channel to the control unit.
Another set of signal lines forms another byte, called Bus In, and carries
information from the control unit to the channel. The exact meaning of the
transmitted bytes is indicated by a signal on a tag signal line.
There are two main types of channels, byte multiplexer and block multiplexer
(burst) as explained above. Byte multiplexer channels are used with slow devices
while block multiplexer channels are used for devices that require a large amount
of data at high speed.
1.1.2 ESA/390 ESCON I/O Interface
ESCON is an integral part of the Enterprise Systems Architecture/390 (ESA/390).
ESCON brings enhancement to the previous S/360 and S/370 parallel OEMI with
the ESCON I/O interface supporting new media and providing new interface
protocols.
Replacing the previous bus and tag cables and their multiple data and control
lines, ESCON provides bidirectional serial bit transmission, in which the
communication protocol is implemented in sequences of special characters and
through formatted frames of characters.
In contrast to the copper cables used in the parallel channel, ESCON utilizes fiber
optic cables for data transmission.
ESCON introduces a new topology of control units and channel attachment.
ESCON control units and channels are attached in a switched point-to-point
arrangement. The switching capabilities allow multiple connections between
channels and control units without requiring permanent physical connections.
To implement the switching function of ESCON, the director was introduced to
connect channels and control units only for the duration of an I/O operation.
1.2 S/390 Server Access Gateway Options
Gateways store and forward packets of data between dissimilar networks. The
term gateway can be used in a generic sense that applies to any layer of the open
systems interconnection (OSI) model. A data link layer gateway is called a bridge
and a router is a gateway at the network layer. However, more commonly, a
gateway is used to mean a device that handles the interconnection and transfer of
data between entities in layers 4 through 7 of the systems network architecture
(SNA) or the OSI reference model. Thus, a gateway is required when an entity
using one protocol needs to communicate with another entity using a different
2 IBM 2216 and Network Utility Host Channel Connections

protocol, when the addressing structure of the two entities is inconsistent, or
when connection is required between independent networks.
The following products are channel-attached controllers that provide some level
of gateway function to an MVS or VM mainframe host:
• IBM 3172 Interconnect Controller
• IBM Open Systems Adapter (OSA)
• IBM 3745 Communication Controller
• IBM 3746 Nways Multiprotocol Controller
• IBM 3174 Establishment Controller
• IBM 2216 Nways Multiaccess Connector
• RS/6000
Although the main topic of this book is the host-attachment possibilities of the
IBM 2216, a brief description of the possible options of accessing a mainframe
will be discussed here so that we can compare it to the 2216.
1.2.1 3172 Interconnect Controller
The IBM 3172 Model 3 Interconnect Controller is a communications processor
that works as a high-speed channel-attached host gateway. The 3172 connects
multiple types of LANs and WANs to host processors via parallel or ESCON
channel attachment. It has options to support a wide variety of protocols (SNA,
TCP/IP, X.25 DECnet, IPX and NetBIOS), topologies and environments including
FDDI, frame relay, leased point-to-point and multi-point communications, and dial
access.
The 3172 Model 3, depending on the configuration, can function either as a
LAN-to-host gateway or a WAN-to-host gateway.
The 3172 running the Interconnect Controller Program (ICP) software provides a
simple pass-through for access to the S/390 server. The 3172 supports LAN
access to the S/390, when running the ICP.
Although the 3172 does not provide an outboard Advanced Peer-to-Peer
Networking (APPN) or IP router, it uses the routing functions of Communications
Server for OS/390, so it can connect both SNA and IP networks to the S/390.
Nowadays, this machine is being replaced by the 2216 Multiaccess Connector.
1.2.2 Open Systems Adapter (OSA)
The OSA is a card that is installed inside the S/390 server, and in ES/9000 711and
511-based models. It is supported on MVS/ESA, VM/ESA and VSE/ESA.
The OSA provides LAN and ATM access but no serial line interfaces. It provides a
similar level of function to the 3172. Also it has far superior connectivity and
performance.
SNA Environment: OSA supports the traditional hierarchical subarea
environment. In SNA networks the OSA is quite similar to the IBM 3172
Interconnect Controller and it is defined as an XCA major node to VTAM.
Host Connectivity Overview 3

APPN: OSA does not differentiate between SNA and APPN. The OSA is not an
APPN network node; thus, it does not provide dynamic APPN routing, but rather
provides static routing to VTAM based on the SAP address and the adapter port.
TCP/IP Passthru: Passthru mode is when the protocol processing of the IP layer
and above is done by TCP/IP. In this case there is a higher performance than in
the offload mode.
TCP/IP Offload: The TCP/IP protocol processing is performed on the adapter,
which reduces the CPU load.
LFS/ESA: OSA enables large-scale file serving for TCP/IP NFS clients via the
LFS/ESA program; OSA provides caching for NFS requests.
LANRES/MVS: OSA enables large-scale disk serving for NetWare NFS clients
via the LANRES/MVS program.
Each LAN port on an open system adapter can be shared across multiple logical
partitions (LPARs) when OSA is used for SNA, APPN, TCP/IP Passthru, and
LANRES. A LAN port is dedicated to an LPAR when running TCP/IP offload or
LFS/ESA modes.
1.2.3 3745/3746 Communications Controllers
The 3745/3746 family of communication controllers provides a full range of
networking functions, especially when acting as gateway to the S/390 server.
1.2.3.1 3745 Communications Controller
The 3745 manages the physical network, controls communications links and
routes data.
The network control program (NCP) running in the 3745 provides support for both
SNA and TCP/IP applications. For SNA applications, both subarea and
APPN/HPR are supported.
The 3745 can act as a local gateway (channel-attached) or as a remote gateway
(remote linked). As a gateway, the 3745 performs the function of routing data
through the network rather than relying on an attached mainframe.
The 3745 can act as a remote gateway for SNA and TCP/IP from token-ring LANs
and TCP/IP from Ethernet LANs to a S/390 by transporting data over the network
using the following protocols:
• SDLC (SNA only)
• X.25
• Frame relay
• Token-ring
• Ethernet (TCP/IP only)
1.2.3.2 3746 900 Multiprotocol Controller
The IBM 3746 Model 900 is an expansion unit that provides the IBM 3745 access
to ESCON channel adapters and additional communication line and token-ring
adapters. The 3746 Model 900 can operate as an APPN network node
independently of NCP and as an SNA subarea or composite network node (CNN)
controlled by NCP.
4 IBM 2216 and Network Utility Host Channel Connections

The 3746 900 supports three different APPN configurations:
• APPN network node provided by the NCP and VTAM
• APPN network node provided by the Network Node Processor (NNP)
• APPN network node provided by the Multi-Access Enclosure (MAE)
The 3746 900 under NCP control can act as a remote gateway for SNA on
token-ring LANs to the host by transporting data over the network using SDLC,
X.25, frame relay or token-ring.
IP function can run in conjunction with the NCP SNA subarea, APPN network
node and dependent LU requester (DLUR) and frame switching functions.
Where TCP applications are used, there are two main configurations:
• IP router provided by the NCP
• IP router provided by the NNP (this router also supports the MAE adapters
using the latest version of the product)
1.2.3.3 3746 950 Multiprotocol Controller
The 3746 950 provides the same APPN and IP functions as the 3746 900 NNP
but does not support the NCP.
1.2.3.4 3746 Multiaccess Enclosure (MAE)
The IBM 3746 Nways Controller provides a Multiaccess Enclosure using the IBM
2216 technology. It offers additional routing functions primarily oriented to high
speed technologies.
The Multiaccess Enclosure requires the Network Node Processor in the IBM
3746 Model 900 or 950 configuration.
1.2.4 3174 Establishment Controller
The IBM 3174 family of establishment controllers provides a wide range of
establishment gateway options. The 3174 family has been the gateway of choice
for users migrating from the traditional 3270 workstations to LANs. They provide
both local and remote gateway functions between the LAN workstations and the
host network.
Depending on the model, the 3174 can act as one of the following:
• Local gateway for SNA traffic on token-ring LANs to the host by sending data
over the channel, or if a CCA is installed, by sending data over an SDLC or
X.25 adapter.
• Remote gateway for SNA and TCP/IP on token-ring LANs or TCP/IP on an
Ethernet LAN to a S/390 host. The 3174 can have one LAN adapter, either
token-ring or Ethernet. TCP/IP traffic coming in from the LAN can be
transported only upstream using frame relay. SNA traffic coming in from the
LAN can be transported upstream over SDLC, X.25 or frame relay.
1.2.5 2216 Multiprotocol Connector
The 2216 is an APPN and IP router that provides a solution for mainframe access
using either an ESCON or a parallel channel adapter. It supports a wide range of
LAN, WAN and ATM adapters.
Host Connectivity Overview 5

For SNA applications, the 2216 acts as an APPN network node and provides full
APPN/HPR support including ANR routing and the RTP endpoint functions.
While the 2216 is optimized for high throughput and performance, the 3745/3746
offers greater connectivity, support for more SNA sessions, and the option of
supporting the NCP for traditional SNA subarea support.
1.2.6 RISC System/6000 Gateway Function
The RS/6000 can be used as a gateway for TCP/IP and SNA. The
Communications Server for AIX and SNA Client Access for AIX provide the SNA
gateway capability.
SNA Gateway as a feature of Communications Server for AIX can be separately
installed. It provides the ability for multiple downstream workstations to access
one or more hosts using one PU definition and one adapter per host. DLUR is
supported to make these functions available over an APPN network as well as a
subarea network.
SNA Client Access runs on top of Communications Server for AIX. It provides
TCP/IP to SNA protocol conversion from an industry-standard TN5250
workstation to an AS/400, or from TN3270 or TN3270E workstations to a
mainframe.
SNA Gateway and SNA Client Access provide connectivity over SDLC, X.25,
FDDI, token-ring, Ethernet and S/390 channels.
6 IBM 2216 and Network Utility Host Channel Connections

Chapter 2. ESCON Channel Attachment
2.1 ESCON Channel Overview
This chapter provides a brief description of the ESCON I/O Interface and its main
elements. The terms input and output are used to describe the transfer of data
between I/O devices and main storage. The facilities used to control I/O
operations are collectively called the channel subsystem. I/O devices and their
control units attach to the channel subsystem.
2216 ESCON support is also included in this chapter.
For the ESCON channel only, MAS V3R2 PTF01 raised the maximum number of
subchannels to 64 and the number of virtual net handlers to 32.
2.1.1 Channel Elements
The channel subsystem directs the flow of information between I/O devices and
main storage. I/O devices are attached by control units to the channel subsystem
by means of channel paths.
ESCON, also called serial I/O interface is a type of channel path that allows
attachment of one or more control units to an ESA/390 channel subsystem by
using optical fiber links and provides protocols required for information transfer
over that channel path.
ESCON provides bidirectional serial bit transmission, in which the communication
protocol is implemented through sequences of special characters and through
formatted frames of characters.
The signaling rate for the ESCON I/O interface is 200 Mbps. The maximum data
rate on different processors depends on the data transfer capability of the
channel subsystem on the processor. On today’s processors the maximum data
rate is 17 MBps.
The physical elements that make up a channel path are a channel, possibly one
or two dynamic switches, one or more control units, and one or more links. See
Figure 1 on page 8.
© Copyright IBM Corp. 1998 7

ESA/390
Channel subsystem
Figure 1. ESCON Elements
2.1.1.1 Channel
The channel subsystem directs the flow of information between the I/O devices
and main storage. It relieves the CPU of the task of communicating directly with
I/O devices and permits data processing to proceed concurrently with I/O
processing. The channel subsystem uses one or more communication paths as
the communication link in managing the flow of information to or from I/O devices.
Within the channel subsystem are subchannels. One subchannel is provided for
and dedicated to each I/O device accessible to the channel subsystem. The
subchannel is the means by which the channel subsystem provides information
about associated I/O devices to CPUs, which obtain this information by executing
I/O instructions.
What the channel does is, on a WRITE command it retrieves data from central
storage, encodes it and packages it into frames before sending it to the link. On a
READ command, the channel performs the opposite operation.
2.1.1.2 Link
The transmission medium for the ESCON I/O interface is a fiber optic cable. This
transmission medium is the link. Physically, it is a pair of optical fibers that
provides two dedicated unidirectional serial bit transmission lines. At any link
interface, one optical fiber is used to receive data while the other is used to
transmit data.
Although there are dedicated fibers for reception and transmission in a single link,
full duplex capabilities are not exploited for data transfer. The reason is that the
ESCON I/O protocol specifies that for normal I/O operations, frames flow serially
in both directions, but basically in a request/response fashion.
8 IBM 2216 and Network Utility Host Channel Connections
CH
01
CH
02
CH
03
ESCON Director
CU
I/O device I/O device
CPU A
CU
I/O device I/O device
ESA/390
Channel subsystem
CU
CH
01
CPU B
CH
02
I/O device I/O device
CH
03
Channel
Link
ESCD port

2.1.1.3 Control Unit
The control unit for the serial I/O interface provides the logical capability
necessary to operate and control one or more I/O devices and adapts the
characteristics of each I/O device to the link interface provided by the channel.
The control unit receives commands from the channel, receives data from and
transmits data to the channel, and controls execution of commands and data
transfer at associated devices. The control unit attaches to one or more links
through link interfaces.
The ESCON I/O interface does not allow multiple control units to reside on the
same link. A control unit however, can contain multiple images controlling a
shared or independent set of devices. The ESCON I/O interface provides for
addressing these multiple images. A control unit image can be considered to
operate independently from all other control images.
However, multiple control units can still be configured to the same channel
through an ESCON Director (ESCD).
2.1.1.4 ESCON Director
When a dynamic switch or ESCON Director is present in a channel path, a
channel path configuration called a switched point-to-point configuration is
provided. The ESCD provides the capability to interconnect physically any two
links that are attached to it. The link attachment point on the dynamic switch is
called a dynamic switch port.
Protocols are defined to allow a channel path attached to an ESCD to be shared
dynamically. Multiple channels may be attached to a single ESCD in order to
permit sharing of the I/O devices also attached to the same dynamic switch.
Only two dynamic switch ports may be interconnected in a single connection, but
multiple physical connections may exist simultaneously within the same ESCD.
The interconnection of two dynamic switch ports established by the ESCD does
not affect the existing interconnection of any other pair of dynamic switch ports,
nor does it affect the ability of the dynamic switch to remove those connections.
When a connection is established, two dynamic switch ports and their respective
point-to-point links are interconnected within the ESCD such that the two links
appear as one continuous link for the duration of the connection. When frames
are received by one of two connected switch ports, the frames are passed from
one port to the other for transmission on the other port's link.
Link Address
A link address is associated with each ESCD port number. Data arriving at an
ESCD port carries a link address that the switching function of the ESCON
Director uses to determine to which outbound port to send the data .
If a port has a dedicated connection to another port, the address included in the
transmitted data is not checked and the data is passed through to the destination
port. If a frame must travel through two ESCON Directors, only one can establish
a dynamic connection.
ESCON Channel Attachment 9

2.1.1.5 Link-Level Facility
The link-level facility performs link-level protocols and functions, such as
initialization, offline processing, and error recovery, and manages logical paths
and the attached link, including transmitter and receiver.
2.1.2 Communication Path
The communication path between a channel and a control unit is composed of
two different parts, the physical path or channel path and the logical path.
2.1.2.1 Physical Path
The physical path is the link, or the interconnection of two links by a dynamic
switch, that provides the physical transmission path between a channel and a
control unit.
Only one control unit at a time can be physically connected to the channel, and
similarly, only one channel at a time can be physically connected to the same
control unit over the same link interface; that is, the ESCD allows only a single
physical connection to exist between two dynamic switch ports.
2.1.2.2 Logical Path
Device-level operations can occur only after specific resources have been
established at the channel and control unit levels and related to one another. This
relationship between a channel and a control unit image that designates the
physical path to be used for device-level communication between both link-level
facilities is called a logical path. The logical path is established through a
link-level procedure and is usually accomplished at initialization.
Summarizing, a channel path is the collection of elements (links, ports, ESCD
connections) that provides a physical path for the information to flow. A logical
path is a representation of a communication path between the channel
subsystem and the control unit, including all the addressing information required
to establish a connection.
2.1.3 Information and Addressing Structure
All information transmitted over the ESCON I/O interface must be encoded into a
10-bit transmission code according to the ESCON I/O encoding rules.
Codification ensures data integrity, provides special control characters, and
provides a way of synchronizing transmitter and receiver.
On an ESCON interface a link interface achieves character synchronization and
recognition by retrieving the clocking from the data.
Apart from encoding, characters are packaged into frames with a specified
format. The ESCON I/O interface defines two types of frames, one to manage the
links and their operations, and another to control device operations. The first ones
are called link-level frames and the latter device-level frames. The format of the
link header and link trailer is common to both device-level frames and link-level
frames.
2.1.3.1 Addressing
In the ESCON I/O interface, the address is made up of the following elements:
1. Link value associated with the ESCD port number
10 IBM 2216 and Network Utility Host Channel Connections

2. Host logical address
3. Control unit images
4. Devices
The first three elements when specified together, constitute a full link address,
which uniquely identifies the recipient of a frame as seen from the ESCON I/O
interface. The second element, host logical address, is used only for shared
channels (ESCON multiple image facility - EMIF) in the logically partitioned
(LPAR) mode. From the host logical address, the channel subsystem determines
for which of the LPARs sharing the channel this frame is intended. The fourth
element, the device, is used when communication is to or from a device and is in
addition to the full logical address.
In summary, the full logical address determines the recipient of the frame, while
the device address is used by the recipient to either select a device in the case of
a control unit or to associate a frame with a subchannel in the case of a channel.
(A subchannel is the representation in the ESA/390 channel subsystem of a
device).
All frames have two full link addresses. One specifies the destination and another
the source address.
ESA/390
Channel subsystem
CH
01
CU
CH
02
CH
03
C1
CU
C9
CPU
CU
Image1 CU
Image2
CU
Imag16
Figure 2. ESCON I/O Interface Addressing
Link Header Information Field Link Trailer
Dest. Addr. Source. Addr.
Link Add:
C9
Log. Add: Link Add:
0 2 C1 0
2.1.4 I/O Operations
Part of the design criteria of the ESCON I/O interface was to minimize the number
of modifications to control programs and applications. So, the ESCON I/O
interface management being done on both sides of the link is performed by:
On the control unit side: There is a piece of hardware and logic to manage,
interpret, and execute commands received at the interface.
On the processor side: The ESA/390 channel subsystem does all the
addressing and protocol management to support the I/O operations
initiated by the software, based on configuration information provided
by the user, usually through the I/OConfiguration Program (IOCP).
SOF
frame
Link Header
Log. Add:
0
Link
Ctrl
No LPARs
in the host
ESCON Channel Attachment 11

2.2 Host Attachment
2.2.1 Basic Mode
Before an I/O operation can be initiated by the channel on a device, the channel
must establish a logical path to the control unit. While establishing this logical
path, the channel determines whether the control unit has the resources to
accept the logical path and informs the control unit of the pacing and Device
Information Block (DIB) sizes the channel can handle.
Logical paths are usually established at initialization, but if EMIF is used in LPAR
mode, logical paths are established at partition activation or later. Requests to
establish logical paths are based on information contained in the I/O configuration
data set (IOCDS).
On the I/O configuration of the ESA/390 channel subsystem only the link
addresses associated with the ESCD ports to which the control unit interfaces are
attached are provided. During initialization, before establishing logical paths, the
channel acquires its own link address (ALA) by executing a specific link level
procedure. Control units go through the same ALA procedure. Information about
the ALAs and the established logical paths is kept in the channels and control
units. This enables the channel and the control unit to identify the sender of the
frame by inspecting the source full link address included in the frame link header
as shown in Figure 2 on page 11.
Based on all of the information supplied in the IOCDS, and all the information
obtained during initialization, the ESA/390 channel subsystem can execute a
start subchannel (SSCH) instruction. Using the information and the subchannel
number specified in the SSCH, the channel subsystem identifies the device, the
possible access paths and their associated link addresses. The actual frames
and number of frames generated are dependent on the CCWs (channel
command words) associated with the SSCH, and the DIB size supported by the
channel and control unit.
Several data frames may be required to satisfy a read or write data request.
In summary, the management of the links that form the channel path is hidden
from the host operating system.
ESCON-capable host processors include the following:
• IBM System/390 Processor (S/390)
• IBM ES/9000 Processor
• IBM ES/3090J Processor (selected models)
• IBM ES/3090-9000T
The processors operate in Basic, LPAR, and EMIF modes.
The ESCON adapter on the control unit is connected to one host channel in a
point-to-point configuration. ESCD can connect one ESCON adapter to more
than one host and can switch the flow of traffic between different ESCON
adapters and different host channels.
A single channel path identifier (CHPID) must be defined because the ESCON on
the control unit communicates with the host through a single channel.
12 IBM 2216 and Network Utility Host Channel Connections

2.2.2 LPAR Mode
2.2.3 EMIF Mode
Figure 3. Basic Mode
The ESCON adapter on the control unit can be connected to many logical
partitions (LPARs) on a single host in a switched point-to-point configuration
controlled by an ESCD. LPAR requires a different channel for each partition, and
the channel path identifier must be defined for each host link.
Figure 4. LPAR Mode
LPAR 1
CH
01
HOST
Channel subsystem
CU & DEVICE
LPAR 2
CU & DEVICE
ESCD
HOST
ESCON multiple image facility (EMIF) enhances the capability of LPAR to share
resources. The ESCON adapter on the control unit is connected to several logical
partitions on the host through a single host channel using EMIF.
A single channel path identifier must be defined because the ESCON adapter
connects with the host through a single adapter.
CH
02
ESCON Channel Attachment 13

Logical channel
path images
Figure 5. EMIF Mode
2.3 2216 ESCON Overview
As seen in Figure 5 each partition has its own logical channel subsystem (logical
CSS), and its own view of each shared channel (logical channel path image) and
each control unit connected to the shared channel (subsystem image).
With EMIF the partition number is used as a logical address to identify the
partition to which a certain I/O belongs. All ESCON channels configured for a
processor operating in Basic mode, and non-shared ESCON channels for a
processor in LPAR mode, continue to use a host logical address field of zero.
The 2216 supports channel attachment by means of two different adapter cards,
the ESCON channel adapter and the parallel channel adapter. This chapter
describes how the ESCON channel has been implemented in the 2216, what it
supports and what it does not.
2.3.1 2216 ESCON Channel Adapter
The 2216 Model 400 contains a slot for the system card and eight slots for
network adapters. Two of the adapters supported in the 2216 are the one-port
ESCON channel adapter (LIC 287) and the one-port parallel channel adapter
(LIC 299).
The 2216 supports a maximum of four ESCON channel adapters, four parallel
channel adapters or four ESCON and parallel channel adapters mixed.
The one-port ESCON channel adapter provides one ESCON channel attachment,
which provides the ability to attach directly to the mainframe ESCON channel or
to an ESCON Director.
The maximum cable length between the S/390 host and the 2216 is 3 km. Longer
distances can be supported via an ESCON Director with an ESCON Extended
Distance interface (up to 23 km in total) or two cascade ESCON Directors with
ESCON Extended distance interface (up to 46 km in total).
14 IBM 2216 and Network Utility Host Channel Connections
LPAR 1 LPAR 2
Log.
CCS
Log.
CSS
CU & DEVICE
HOST
Shared
channel
path

The adapter supports a maximum of two IBM 9032 or 9033 ESCON Directors in
the path between the 2216 and the host.
The adapter supports 62.5/125 micron multimode fiber.
The serial data link is 200 Mbps and the data transfer rate is 17 MBps.
2.3.2 2216 ESCON Channel Adapter Features
Important Note
2216 and Network Utility with V3R2 PTF01 code raised the number of
subchannels to 64 and the maximum number of virtual net handlers to 32. This
is for ESCON channels only.
The ESCON channel adapter (FC 2287) provides the IBM 2216 with access to
SNA and TCP/IP host applications from LANs, WANs and ATM over a
duplex-to-duplex multimode fiber optic cable. The adapter features are the
following:
• Support for up to four ESCON adapters.
• The ESCON channel interface is divided into 256 logical addresses
(subchannels). Each host application interface uses one or more subchannels
to connect from the host application to the IBM 2216. Through configuration,
each subchannel is assigned a unique relative index, which may or may not
match its actual logical address. The ESCON channel may be shared by
multiple applications on multiple hosts, but each host application will have
dedicated use of its subchannels.The MPC+ subchannels cannot be shared
with non-MPC+ applications. The IBM 2216 ESCON channel adapter supports
up to 32 subchannels at a time. It now supports 64 subchannels with MAS
V3R2 PTF01.This provides the 2216 with access up to:
• 32 hosts for Link Services Architecture (LSA) since LSA uses one
bidirectional subchannel
• 16 hosts for LAN Channel Station (LCS) since LCS requires one
subchannel for reading and another one for writing
• 16 hosts for MPC+ since MPC+ requires also two subchannels, one for
reading and another one for writing
This assumes these types are not mixed on the adapter.
When used with an IBM 9032 or 9033 ESCON Director or EMIF-capable
processors operating in a logically partitioned (LPAR) mode, the adapter
provides support for up to 15 logical host images.
• Data link switching (DLSw) supports VTAM 3.4 (or higher) SNA applications.
DLSw allows local (single 2216) conversion from SDLC, FR BAN, QLLC and
LANs to the channel and remote (via DLSw partners) connectivity to SNA
devices.
• High performance Internet Protocol (IP) and SNA host application access,
featuring Multi-Path Channel+ (MPC+) support for high throughput APPN High
Performance Routing (HPR) to VTAM 4.4 SNA applications.
• APPN intermediate session routing (ISR) to VTAM 3.4 (or higher) SNA
applications.
ESCON Channel Attachment 15

• APPN and IP routing over any other 2216 interface including IP route selection
based on static, RIP, OSPF and BGP-4 routes and filtering of IP frames
coming from or destined for a channel.
• Dependent LU Requestor (DLUR) in APPN to provide connectivity between
dependent downstream SNA devices and SNA applications.
• Boundary access node (BAN) support in APPN to provide connectivity
between downstream BAN Frame Relay Access Devices (FRADs) and SNA
applications.
• ESCON channel-to-channel (CTC) connectivity for token-ring, Ethernet, FDDI
and ATM LAN emulation.
2.3.3 2216 ESCON Channel Protocols
The IBM 2216 ESCON channel adapter supports three types of channel
protocols. Each protocol uses different subchannels and a subchannel can
support only one protocol at a time. The three channel protocols are LAN
Channel Station (LCS), Link Services Architecture (LSA) and Multi-Path
Channel+ (MPC+). Each channel protocol supports one or several network
protocols as shown in Figure 6 on page 17.
2.3.3.1 LAN Channel Station (LCS)
LCS is the channel protocol that is supported by TCP/IP applications on the host.
Each application defines a consecutive pair of subchannels. One subchannel is
for TCP/IP to read from the channel and the other one is for TCP/IP to write to the
channel. The LCS interface allows LAN MAC frames to be transported over a
channel and it provides a command interface to activate, deactivate and query
the LAN interfaces. Each MAC frame has a header that identifies the virtual LAN
adapter destination of the frame.
2.3.3.2 Link Services Architecture (LSA)
LSA is an interface to support SNA traffic over the channel. Each LSA path is a
single bidirectional subchannel between the host application and the 2216
ESCON channel adapter. The host SNA application (VTAM) issues a READ
command immediately following each WRITE command to retrieve data from the
channel. The 2216 ESCON channel adapter also issues an Attention command
when it has something for the host application to read. LSA has a command
interface that allows VTAM to open service access points (SAPs) to communicate
with downstream workstations using the IEEE 802.2 Logical Link Control (LLC)
interface.
2.3.3.3 Multi-Path Channel+ (MPC+)
MPC+ is a data link control (DLC) interface for the channel. Each MPC+ path
consists of one or more read subchannels and one or more write subchannels.
These subchannels are bound together to form a transmission group. VTAM and
the 2216 ESCON channel adapter exchange IDs (XIDs) to identify the number
and direction of subchannels at initialization, and then each frame has a header
to indicate the sending and receiving applications.
16 IBM 2216 and Network Utility Host Channel Connections

Network
Protocols
Channel
Protocols
Figure 6. IBM Channel Connectivity
2.3.4 2216 ESCON Channel implementation
MPC+
LSA
TCP/IP SNA
UDP+ not supported in PCA
IBM Channel Connectivity
LCS
UDP+
APPN
HPR
APPN
ISR
TN3270
The host channel interface packages control data frames in blocks of up to 32 KB
(36 KB for MPC+). The format of data blocks is different for MPC+ and non-MPC+
host applications. LSA and LCS blocks consist of one or more contiguous frames,
each with a header that identifies the destination device by its LAN type and LAN
number. MPC+ blocks contain one or more discontiguous frames with the first 4
KB of the block containing MPC+ PDU headers and offsets of application data,
which is stored in the last 32 KB of the block. A block of data is transmitted either
when it is filled, or when the block delay timer (which determines how long the
adapter waits for the block to fill before transmitting) expires. The process of
receiving a block of data and forwarding the individual frames to the device
drivers is called deblocking.
2.3.4.1 LCS and LSA (2216 vs 3172)
The host LAN gateway function is a method that allows host applications to
communicate with LAN-based workstations. The two main host applications
supported by the host LAN gateway function are TCP/IP and VTAM. These
applications encapsulate LAN frames into channel control words (CCW) for
transport across the channel. This is also referred to as blocking since the CCW
blocks consists of a block of LAN frames sent as single logical units. The CCW is
then deblocked by the receiver into individual frames.
The 3172 Interconnect Controller Program transferred frames from a host
channel to one or more LANs. In its configuration each subchannel was
connected to one or more LAN device drivers. Data from the host was received by
a deblocker, which would distribute the frames to one of the LAN adapters based
on the LAN type and LAN number contained in the frame header. If a host
ESCON Channel Attachment 17

application needed access to multiple LAN adapters, the configuration file would
contain one entry for each LAN adapter.
In the IBM 2216, all of the subchannels are connected to the Base Net Handler,
which in turn is connected to one or more virtual net handlers. It is different from
the IBM 3172 Interconnect Controller Program in which each subchannel is
connected to one or more real LAN adapters. Each virtual net handler supports
one of the three channel protocols (LCS/LSA/MPC+) and sends and receives
frames with one of the protocol applications (LLC/IP/APPN), which sends the
data to another net handler representing a network connection. There may or
may not be any real LAN adapters connected to the IBM 2216.
Figure 7. 2216 ESCON Channel Adapter Implementation
The 2216 is replacing the 3172 as a gateway between the host and the users.
The hardware and software interfaces between the host and the 2216 are the
same as the interfaces between the host and the 3172 ICP. To preserve the
software interface, it is necessary for the 2216 to create the appearance of a LAN
adapter so that the host application still believes it is communicating with a real
LAN.
The 3172 ICP gateway function supported two channel interfaces, one for TCP/IP
(called LAN channel station or LCS), and one for SNA (called link services
architecture or LSA). Both of these channel interfaces are supported by the 2216
without any change to the host programs.
Then, in order to preserve the existing host interface, the IBM 2216 ESCON
channel adapter takes on the appearance of multiple LAN adapters for LCS and
LSA connections. Based on the configuration parameters, the virtual net handlers
register with the appropriate protocols as either token-ring, Ethernet or FDDI
adapters. The Base Net Handler allows the host to activate and deactivate this
virtual LAN adapter in the same manner it controls the 3172′s real LAN adapters.
Each virtual LAN adapter has its own MAC address, which allows the IBM 2216
ESCON channel adapter to appear to the host as one or more LAN adapters on
an actual local area network.
18 IBM 2216 and Network Utility Host Channel Connections
Host IBM 2216
IP
VTAM
APPN
...
...
IP forwarding
LLC
APPN
Bridging
Virtual net handlers
Subchannels
channel adapter

A single subchannel (or pair) may be connected to one or more virtual LAN
adapters. This is necessary to allow a single host application to communicate
with different types of LANs (token-ring, Ethernet, FDDI) over the same
subchannel. LAN-bound frames are directed to the correct destination by the LAN
type and LAN number in the frame header.
However, the inverse is true only for LSA connections. A single LCS virtual LAN
adapter may be connected to only one subchannel. This restriction improves data
throughput by allowing host-bound frames to be directed to the correct
subchannel by the virtual net handler, without forcing the net handler to examine
the MAC address or IP address of each host-bound frame. Multiple VTAMs can
share a single LSA net handler if each opens a SAP with a unique number. This
cannot be done for the LCS net handler because all TCP/IP traffic uses the
multiprotocol SAP number x′ AA′.
Host
Subchannel
IBM 2216
Virtual LAN adapters
Figure 8. LAN to Subchannel Configuration
Host
Subchannels
IBM 2216
Virtual LAN adapter
LSA and LCS Only LSA
2.3.4.2 MPC+
MPC+ does not use the virtual LAN adapter concepts common to both LCS and
LSA interfaces, since MPC+ does not support a LAN gateway appearance for the
2216 ESCON channel adapter. The equivalent interface for MPC+ is the MPC+
group. An MPC+ group is a set of ESCON subchannels configured to act as a
single data pipe between the host and the 2216. An MPC+ group consists of at
least one read subchannel and at least one write subchannel. As explained for
LCS and LSA all of the subchannels are connected to the Base Net Handler,
which is in turn connected to one or more virtual net handlers running LCS, LSA
or MPC+.
Any number of subchannels may be designated as read or write subchannels,
and the multiple MPC+ groups may be defined, subject to a maximum of 32
subchannels per 2216 ESCON channel adapter. (With MAS V3R2 this is raised to
64 subchannels.) If at least one read and one write subchannel is allocated
successfully, the MPC+ connection is activated. Additional paths (defined but not
online) in an MPC+ group can be dynamically added later to the active group
using the MVS vary on command in VTAM. Also, paths can be deleted from the
active group when they are no longer needed.
Data may be sent over any or all of the active subchannels in an MPC+ group.
The MPC+ endpoint is responsible for maintaining data order over a group. The
number of subchannels is fixed when the MPC+ group is defined. MPC+ groups
ESCON Channel Attachment 19

are identified in the microcode using the same LAN type and LAN number
destination as virtual LAN adapters. As frames are deblocked by the microcode,
each frame is given a LAN type of MPC+ and a LAN number which corresponds
to the MPC+ group associated with the subchannel it was received on. This
allows the microcode and net handler to process MPC+ frames in a manner
consistent with LCS and LSA frames.
2.3.5 ESCON Channel Attachment Support
2.3.5.1 Channel Connections
The IBM 2216 provides host attachment with the ESCON channel adapter. The
following ESCON channel connections are supported:
• ES/3090J Processor (selected models)
• 9021 ES/9000 Processor
• 9121 ES/9000 Processor
• 9221 ES/9000 Processor
• 9032 and 9033 ESCON Directors
• 9036 ESCON Remote Channel Extender
• 9672 System/390 Parallel Enterprise Server
• 9729 Optical Wavelength Division Multiplexer
• 2003 System/390 Multiprise 2000
2.3.5.2 Supported Configurations
The IBM 2216 with an ESCON channel adapter provides the following support:
• A maximum of four ESCON channel adapters per IBM 2216.
• A maximum of 32 logical paths (ESCON subchannels) per IBM 2216 ESCON
channel adapter to the connected hosts. This is increased to 64 subchannels
with MAS V3R2 PTF01.These logical paths can be defined to the same host
ESCON channel or divided among multiple ESCON channels.
• EMIF support for sharing ESCON channels for connection to multiple host
images in LPAR-capable hosts. This support can be used with the IBM
ESCON Directors connecting to multiple hosts, or for direct connection to a
single host processor.
• A maximum of two IBM 9032 or 9033 ESCON Directors (ESCDs) in the path
between the IBM 2216 ESCON channel adapter and the host.
• Distance of up to 43 km (26.7 mi) using the ESCON Extended Distance
Feature (XDF) available on host processors, ESCDs and ESCON Remote
Channel Extenders.
Single Attachment between a S/390 Processor and 2216
The maximum distance between the host and the 2216 can be 3 km (1.86 mi). An
example can be seen in CH 01 in Figure 9 on page 21.
Single Attachment between a S/390 Processor and 2216
The maximum distance between the S/390 host and the 2216 can vary from 3 km
(1.86 mi) to 43 km (26.7 mi). For connection CH 02 in Figure 9 on page 21, a
maximum distance of 9 km can be achieved with two ESCDs connected with
multimode fiber. You can achieve distances of up to 43 km by using IBM 9032 or
9033 ESCDs with the XDF or a combination of ESCDs and IBM 9036 Remote
Channel Extenders as shown in connections CH 03 and CH 04 in the same
figure. The host must also have the XDF.
20 IBM 2216 and Network Utility Host Channel Connections

The 9036 ESCON Remote Channel Extender extends ESCON link distance by
optical signal regeneration between the attached pair of fibers. It also converts
between multimode fiber (LED) and single-mode fiber (LASER). The ESCD does
the conversion as well.
The maximum distance for a single-mode optical fiber link is 20 km. The
maximum distance for a multimode fiber link is 3 km, but consider that the
adapter supports 62.5/125 micron multimode fiber, so the side of the link
attaching the 2216 has to be multimode fiber.
When two ESCON Directors are serially attached, the connection through one of
the directors must be dedicated.
3 km maximum
43 km maximum
ESCD
9036
CH 01 CH 02 CH 03 CH 04
2216 ESCD
2216
Figure 9. Single ESCON Connection Example
ESCD
2216
ESCD
ESCD
ESCD
HOST
Multi Systems Attachment with ESCDs
Figure 10 on page 22 shows the connection between multiple S/390 hosts and
single and multiple 2216s, with possible backup paths. A fault-tolerant solution
can be designed using backup channels, multiple ESCDs and or multiple 2216s.
2216
ESCON Director (9032/9033)
ESCON Remote Channel Extender (9036)
XDF Single-mode ESCON channel (20 km maximum)
Multi-mode ESCON channel (3 km maximum)
2216
2216
2216
ESCD
9036
9036
ESCD
2216
ESCON Channel Attachment 21

HOST A
2216
Figure 10. Multiple System ESCON Connections Example
EMIF Attachment between a S/390 Processor and a 2216
The ESCON multiple image facility (EMIF) allows the sharing of ESCON channels
across processor resource/systems manager (PR/SM) logical partitions (LPARs).
Prior to EMIF, dedicated channels to each logical partition were required.
The 2216 ESCON channel adapter supports EMIF connectivity. This connection
can be either direct host attachment or through an ESCD, and the logical hosts
can be on the same or different physical hosts. Figure 11 on page 22 shows the
connection of an LPAR host to single or multiple 2216s.
Figure 11. 2216 EMIF Attachment Example
22 IBM 2216 and Network Utility Host Channel Connections
HOST B HOST C HOST D
CH 1 CH 1 CH 2
CH 1 CH 2 CH 3
CH 1
Dynamic connections
ESCD ESCD
LPAR 1
ESCD
CH
01
2216
2216 2216 2216
LPAR 2
2216
LPAR 3
CH
02
2216
LPAR 4
HOST

In the example above, the logical hosts 3 and 4 are connected directly to the
2216. The logical hosts 1, 2 and 3 are connected to multiple 2216s with a single
ESCON connection from the ESCON Director. Each of these 2216s may be
connected to any of the logical hosts 1, 2 and 3.
2.3.5.3 Considerations
A 2216 can support a maximum of four ESCON channel adapters. Each channel
adapter can support a maximum of 32 subchannels (64 subchannels with MAS
V3R2 PTF01). This limits how many hosts programs running in the same or
different hosts or logical partitions and users can use the 2216.
The ESCON channel can be shared by multiple applications on multiple hosts,
but each host application will have dedicated use of its subchannels. Based on
that, a 2216 will need at least:
• One LSA subchannel for each VTAM host program instance. These VTAM
programs can run in the same or different host or logical partition and must not
use MPC+.
• One LCS interface (two subchannels) for each TCP/IP program running in the
same or different host or LPAR.
• Two subchannels for each host program instance that will be communicating
with the 2216 using MPC+ running in the same or different host or LPAR.
Be aware that multiple VTAMs can share an LSA interface, but not a subchannel.
If more than one VTAM needs to use the same LSA interface, each VTAM needs
to open a different SAP. In this case there will be at least one subchannel per
VTAM application in the LSA interface.
Regarding the number of users that can access host applications through a 2216,
we have to consider that:
• Each LSA interface supports 10240 (since MAS v3.2) link stations per SAP
and each LAN adapter can have multiple SAPs. For SNA this is the number of
PUs supported.
• For APPN over MPC+, the number of users is based on APPN and not on the
interface type.
Summarizing, the rules that govern the network interfaces in an ESCON channel
adapter are:
• Up to 16 interfaces can be configured per adapter.
• Up to 32 subchannels can be used per adapter (64 subchannels with MAS
V3R2 PTF01). A subchannel can support only one protocol at a time.
• One LCS interface is required per TCP/IP host application. And only two
subchannels, one for reading and one for writing can be used per LCS
interface. LCS subchannels can be shared by multiple LCS interfaces.
ESCON Channel Attachment 23

LCS A
passthru
LAN 1
Figure 12. LCS Subchannels Policy
Figure 12 on page 24 shows each LCS interface using only a pair of subchannels.
Each LCS interface is identified by a LAN type and LAN number, and based on
that the ESCON net handler is able to send the data coming through a
subchannel to the right LCS interface.
1. LCS A and B are LCS passthru or 3172 emulation interfaces, which means
they are associated with a LAN interface. Each LCS passthru interface is
associated with a single LAN and vice versa.
In this example, LCS A provides LAN 1 with access to TCP/IP A while LCS B
provides LAN 2 with access to TCP/IP B. TCP/IP A and TCP/IP B are TCP/IP
hosts.
2. LCS C and LCS D are LCS bridging interfaces. LCS C provides all the bridging
networks attached to the 2216 with access to TCP/IP A while LCS D provides
those same bridging networks attached to the 2216 with access to TCP/IP B.
3. Finally, LCS E and F are LCS routing interfaces, which means that they
provide all IP networks attached to the 2216 with access to TCP/IP A and B,
respectively.
For more information on the different types of LCS interfaces refer to Chapter 5,
“LAN Channel Station” on page 131.
One or more bidirectional subchannels are used for each VTAM host LAN/WAN
gateway (LSA). Several hosts can share an LSA interface provided they open
different SAPs. And also, LSA subchannels can be shared by multiple LSA
interfaces.
VTAM LSA interfaces must be defined as either gateway (TR, EN, LANE, FDDI,
FasTR) or loopback (APPN/DLSw). Gateway LSA interfaces are associated with
24 IBM 2216 and Network Utility Host Channel Connections
TCP/IP A TCP/IP B
SC0 SC1 SC2
LCS B
passthru
LCS C
bridging
Bridging
code
LCS D
bridging
SC3
LCS E
routing
IP code
2216
LCS F
routing
LAN 2 LAN 3 LAN 4 LAN 5 WAN 1 WAN 2 WAN 3 WAN 4

a specific LAN or LANE interface. LSA loopback interfaces can be used for APPN
and DLSw. An LSA interface cannot be both loopback and SNA gateway.
Figure 13. LSA Subchannel Policy
VTAM A VTAM B VTAM C VTAM D
SC4 SC5 SC6 SC7
LSA 1 LSA 2 LSA 3 LSA 4
DLSw code
IP code
LAN 1 LAN 2 WAN1 WAN 2
In the example of Figure 13 on page 25 we see that it is possible for an LSA
interface to use more than one subchannel, which means that more than one host
can share the same LSA interface (by opening each host’s different SAPs). Also
the subchannels can be shared by multiple LSA interfaces based on the LAN type
and LAN number that is assigned to each LSA interface.
1. LSA 1 uses subchannels 4 and 5 providing LAN1 with access to VTAM A and
B.
2. LSA 2 uses subchannel 5 and provides LAN 2 with access to VTAM B.
3. LSA 3 uses subchannels 6 and 8 providing LAN 1 with access to VTAM B and
C.
4. Finally, LSA 4 uses subchannels 7, 8 and 9 providing APPN and DLSw access
to all interfaces for hosts B, C and D.
5. LSA 1 and 3 have both a direct connection to LAN 1. Both LSA interfaces will
be operational at the same time provided the applications they provide access
to use different SAPs.
At least two subchannels (one for reading and one for writing) are required for
each MPC+ interface. MPC+ groups cannot share subchannels with other
MPC+ groups.
SC8
APPN
code
SC9
2216
ESCON Channel Attachment 25

TCP/IP
APPN
TCP/IP
APPN
HPDT
for UDP
TRLa
VTAM
TRLb
VTAM
VTAM
Figure 14. MPC+ Channel Policy
The rules for the definitions of MPC+ subchannels are shown in Figure 14 on
page 26 and are:
1. A subchannel that is configured as a write subchannel in VTAM is a read
subchannel in the 2216 configuration.
2. There can be multiple MPC+ groups on the same ESCON channel adapter as
seen in adapter A in the picture.
3. Parallel MPC+ groups are also supported as they are defined in a different
TRL entry in VTAM as seen in adapter B in the figure.
4. There must be at least two subchannels, one for reading and one for writing,
its being possible to define more.
5. UDP+ cannot share its MPC+ group with other protocols. Note that HPDT for
UDP is available in ESCON only.
6. An MPC+ group can be shared for TCP/IP and APPN.
26 IBM 2216 and Network Utility Host Channel Connections
read
read
write
read
write
write
read
read
write
write
read
write
SC12
SC11
SC10
SC9
SC8
SC7
SC6
SC5
SC4
SC3
SC2
SC1
Adapter A
write
write
read
write
read
read
Adapter B
write
write
read
read
write
read
MPC+
MPC+
MPC+
MPC+
host ESCD
2216
APPN
code
IP
code

Chapter 3. Sample Host Definitions
3.1 Overview
This chapter contains examples of host definitions for the 2216 in the
configurations used in this redbook.
Specifically, definitions for the following environments are presented:
• LSA
• LCS
• MPC+
Additionally, the differences between a 2216 with an ESCON channel adapter
and a parallel channel adapter are highlighted.
For more information on defining the 2216 to the host, refer to IBM 2216 Nways
Multiaccess Connector Software User's Guide, SC30-3886.
Follow these steps to define a channel-attached 2216 to the host:
1. Define the 2216 to the host channel subsystem. This will be done either from
the I/O configuration program (IOCP) or the Hardware Configuration Definition
(HCD), depending on your MVS version. (HCD requires MVS/ESA SP Version
4.2 or later with APAR# OY67361.)
The definition statements are slightly different for an ESCON
channel-attached device as compared to a parallel channel-attached device.
An example of these definitions is given in 3.2.1, “Sample Host IOCP
Definitions” on page 28.
2. Define the 2216 as a control unit to the host operating system. For most
systems, the definitions are the same for an ESCON adapter as they are for a
parallel channel adapter. Obviously, they depend on the operating system
being used. An example of these definitions is given in 3.3, “Defining the 2216
in the Operating System” on page 31.
3. Define the 2216 to the host TCP/IP or VTAM.
These definitions depend on whether you are defining an LSA (SNA), an LCS
(TCP/IP), or an MPC+ (SNA and/or TCP/IP) interface on the 2216. Section
3.4, “VTAM Definitions” on page 33 shows examples of the required VTAM
definitions. Section 3.5, “Host IP Definitions” on page 41 shows examples of
the required TCP/IP definitions.
3.2 Definitions at the Channel Subsystem Level
You make definitions at this level via the IOCP or with HCD. If HCD is available,
you will probably want to use it. HCD offers an improved method of defining
system hardware configuration. With HCD, several complex steps required for
entering hardware configuration data can be accomplished using an interactive
dialog. This chapter presents only the IOCP macros that would be generated from
HCD.
© Copyright IBM Corp. 1998 27

3.2.1 Sample Host IOCP Definitions
An example of the definitions required in the host I/O Configuration Program
(IOCP) for a 2216 configured with an ESCON adapter is shown in Figure 15.
CHPID PATH=((05)),TYPE=CNC
CNTLUNIT CUNUMBR=1E0,PATH=05,CUADD=0,
UNITADD=((E0,32)),LINK=3C,UNIT=3172
IODEVICE UNIT=3172,ADDRESS=((1E0,32)),
CUNUMBR=1E0
Figure 15. Sample Host IOCP Definitions for the 2216 (ESCON)
The following sections describe the IOCP macros that you need for defining the
2216 at the host.
3.2.1.1 RESOURCE Statement
This identifies the host logical partitions (LPARs) by name and number. This
statement is not present if the host is not partitioned, as is the case in the
example above.
•PART=((name1,x),(name2,y)...(nameX,z))
The name identifies the LPAR and is used in the rest of the channel path
definition. The number is the corresponding LPAR number. The LPAR number
is used in defining the subchannel on the 2216. If the host is not partitioned,
the LPAR number is always 0.
3.2.1.2 Channel Path ID (CHPID) Statement
The CHPID identifies the type of channel connection and who uses it.
•PATH=x
• This uniquely identifies the channel path. This value is often called the CHPID
number.
•TYPE=CNC
• This indicates that the channel is an ESCON channel. The channel type is
CNC for ESCON and BL for block multiplexer (parallel channel adapter).
•SWITCH=x
• This identifies which ESCON Director is in this path. If no director is being
used, this parameter is omitted.
•SHARED
• This indicates that the CHPID can be used by multiple LPARs simultaneously.
If not present, only one LPAR can use the CHPID at a time.
•PARTITION=(name1,name2,...,nameX)
• This is one form of the PARTITION parameter and it contains an access list of
LPARS that indicates which partitions have access to this channel. The names
must be included in the RESOURCE statement.
•PARTITION=((name1,...,nameX),(name2,...,nameY))
• This is the other form of the PARTITION parameter. In this form, the first
grouping of names is the access list of LPARs, as above. The second grouping
is the list of candidate LPARs that an operator could configure to have access
28 IBM 2216 and Network Utility Host Channel Connections

to the channel. The second grouping will have at least the same LPARs as the
first grouping and it may specify additional LPARs also.
3.2.1.3 Control Unit (CNTLUNIT) Statement
This statement, along with the IODEVICE statement, defines the path from the
host to the 2216. The CNTLUNIT and IODEVICE statements occur in pairs. If
multiple LPARs are being defined to use a single CHPID, there must be a
CNTLUNIT and IODEVICE statement for each LPAR.
•CUNUMBR=x
• This is an identifier for the control unit definition.
•PATH=x
• This number identifies the CHPID being used.
•UNIT=3172
• This identifies the type of control unit at the other end of the channel. The
value is always 3172 when talking to a 2216. The IBM 3172 was the
predecessor of the 2216 ESCON channel function.
•CUADD=x
• This value identifies the control unit address of the 2216. The default is 0. For
the 2216, each LPAR on a given CHPID must have a unique CUADD value.
Usually (but not always) the CUADD value will be chosen to match the LPAR
number.
•UNITADD=(( addr, number))
• This defines the range of addresses reserved for this control unit, where:
• addr is the hex address of the first subchannel assigned to this control unit
• number is the decimal number of subchannels being assigned to this control
unit
• The example above defines a maximum of 32 control unit addresses, or
subchannels, starting from E0 hex and going upwards. The device addresses
specified on the 2216 LCS, LSA, or MPC+ interface definition must be from
within this range. The 2216 can use a maximum of 32 subchannels.
•LINK=xx
• The value for the LINK parameter should be set to the port of the ESCON
Director (ESCD) that the 2216 is attached to. Because the ESCD is a switch,
you can think of the link parameter as the phone number that the host will use
to reach the 2216 through the switch.
3.2.1.4 IODEVICE Statement
This statement, along with the CNTLUNIT statement, identifies the 2216
connection to the host.
•ADDRESS=(addr, number)
This parameter identifies the range of addresses to the rest of the host, where:
addr is the hex address being assigned to the first address reserved
number is the decimal number of subchannels reserved
Sample Host Definitions 29

This address is different from the UNITADD. It is used in the TCP/IP profile (for
LCS), the VTAM XCA Major Node Definition (for LSA), and the VTAM TRL (for
MPC+) to identify the subchannels being used.
•CUNUMBR=x
This identifies the corresponding CNTLUNIT statement to this IODEVICE
statement. While the value for this parameter has to be the same for both the
CNTLUNIT and the IODEVICE macros, it does not have to relate to any other
parameter. It is a good idea, however, to make it the same value specified in
the ADDRESS parameter as in the IODEVICE macro. The value for
CUNUMBR has no significance outside the Channel Path Definition.
•UNIT=3172
This identifies the type of device that is downstream. It should always be 3172
if the control unit is a 2216. The IOCP software in the host does not look at this
field. If you are migrating from an IBM 3172 to the 2216, you might have a
value of UNIT=SCTC in the existing IOCP statement. This should be changed
to 3172 for the 2216.
•PARTITION=(name)
This is the device candidate list and it contains a list of one or more LPARs
that have access to the device. This list is a subset of the list of LPARs
specified in the CHPID statement and it is used to restrict which LPARs in the
channel candidate list are allowed to use these devices. If the host is not
partitioned, this field will not be present.
Figure 16 shows an example of the IOCP statements for defining a 2216 with a
parallel channel adapter (PCA).
CHPID PATH=((05)),TYPE=BL
CNTLUNIT CUNUMBR=640,PATH=05
PROTOCL=S4,UNIT=3172
SHARED=N,UNITADD=((40,32))
IODEVICE UNIT=3172,ADDRESS=((640,32))
STADET=N,CUNUMBR=640,TIMEOUT=Y
Figure 16. Sample Host IOCP Definitions for the 2216 (PCA)
Note the following points concerning the IOCP statements for a 2216 with a PCA:
• The TYPE is BL for Block Multiplexer.
• PROTOCL parameter can be set to the following values, depending on the
device capability:
D Direct-Coupled Interlock (DCI) mode
S Maximum 3.0 Mbps data streaming speed
S4 Maximum 4.5 Mbps data streaming speed
For the 2216, set the value to S4. The transfer mode and channel parameter
must conform with the PCA setting for transfer mode and channel transfer
speed.
• The UNIT parameter on the CNTLUNIT and IODEVICE statements must be
set to 3172.
• When an ESCON converter is the channel path, the CHPID TYPE parameter
must be set to CVC, otherwise it is set to BL.
30 IBM 2216 and Network Utility Host Channel Connections

3.3 Defining the 2216 in the Operating System
The following sections describe the definitions needed for various host operating
systems.
3.3.1 2216 Definition for VM/SP
You must define the 2216 to a VM/SP operating system by updating the real I/O
configuration file (DMKRIO) with entries for the 2216 in the RDEVICE and the
RCTLUNIT macros. In the following example, 640 is the base unit address and
the size of the address range is 32.
RDEVICE ADDRESS=(640,32),DEVTYPE=3088
RCTLUNIT ADDRESS=640,CUTYPE=3088,FEATURE=32-DEVICE
Figure 17. 2216 Definitions for VM/SP
2216 Definition for VM/XA and VM/ESA
You must define the 2216 to a VM/Extended Architecture (VM/XA or VM/ESA
operating system by updating the real I/O configuration file (HCPRIO) with an
entry for the 2216 in the RDEVICE macro. In the following examples, 640 and 2A0
are base control unit addresses. The address range size, as defined in the UCW
or IOCP, is 8 in both examples.
The following example is a VM/XA HCPRIO definition:
RDEVICE ADDRESS=(640,8),DEVTYPE=CTCA
Figure 18. VM/XA HCPRIO Definition Example
The following example is a VM/ESA HCPRIO definition:
RDEVICE ADDRESS=(2A0,8),DEVTYPE=CTCA
Figure 19. VM/ESA HCPRIO Definition Example
3.3.2 2216 Definition for MVS/XA and MVS/ESA without HCD
You must define the 2216 to an IBM Multiple Virtual Storage/Extended
Architecture (MVS/XA) or MVS/ESA operating system by updating the MVS
Control Program with an entry for the 2216 in the IODEVICE macro.
For ESCON channels, an example IODEVICE macro is:
IODEVICE UNIT=3172,ADDRESS(540,8)
Figure 20. IODEVICE Macro for ESCON Channels Example
For parallel channels, an example IODEVICE macro is:
Sample Host Definitions 31

IODEVICE UNIT=CTC,ADDRESS(640,8)
Figure 21. IODEVICE Macro for Parallel Channels Example
The base control unit addresses are 640 and 540. The address range size, as
defined in the UCW or IOCP, is 8 in both examples.
3.3.3 2216 Definition for MVS/ESA with HCD
The hardware configuration definition (HCD) component of MVS/ESA SP Version
4.2 and 4.3 with APAR #OY67361 offers an improved method of defining system
hardware configuration for 2216. You can accomplish the several complex steps
required for entering hardware configuration data by using an interactive dialog
with HCD.
The required configuration data for the 2216 is:
• When using HCD, with APAR #OY67361, define the 2216 as (UNIT=3172). For
example:
IODEVICE UNIT=3172,ADDRESS(740,8)
Figure 22. 2216 HCD Definition Example
• Without HCD, define the 2216 for:
• Parallel channels as a 3088 device (UNIT=3088 or CTC)
IODEVICE UNIT=CTC,ADDRESS(840,8)
Figure 23. Parallel Channel Definition without HCD for MVS/ESA
32 IBM 2216 and Network Utility Host Channel Connections
• ESCON channels as a serial CTC device (UNIT=SCTC)
IODEVICE UNIT=SCTC,ADDRESS(A40,8)
Figure 24. ESCON Channel Definition without HCD for MVS/ESA
Notes:
1. If you are using HCD for MVS Version 4 to define your ESCON host
connection, you will need APAR # OY67361 to obtain the UIM support for the
device definition (UNIT=3172).
2. When you are migrating your IOCP definition and operating system definitions
to the HCD environment, it is important that you change all 2216 device
statements to device type (UNIT=3172).
3.3.4 Network Utility Definition for VSE/ESA
You must define the 2216 to a VSE/ESA operating system by supplying an ADD
statement for each channel unit address at initial program load (IPL) time.
Code the device type on the ADD statement as CTCA,EML as shown in the
following example:

3.4 VTAM Definitions
ADD 640,CTCA,EML
Figure 25. 2216 Definition for VSE/ESA
The base control unit address is 640 in the example. For the number of channel
unit addresses added, increase the IOTAB storage macro by this count.
This section gives sample VTAM definitions for an XCA major node, an MPC+
local PU and Transport Resource List (TRL) major node, and an example of
defining VTAM for APPN and DLUR support. It also shows an example of a
switched major node for a PU in a TN3270 server. This section is not meant to be
a complete reference on the subject. For more information on configuring VTAM,
refer to the OS/390 eNetwork Communications Server SNA Resource Definition
Reference, SC31-8565.
3.4.1 VTAM XCA Major Node Definition
When defining a channel gateway using LSA to VTAM, a definition for an External
Communications Adapter (XCA) is required. This definition is the same as that
used for an IBM 3172. An example is shown in Figure 26 on page 33.
********************************************************************
RAINETU VBUILD TYPE=XCA 1
**
**
RANETUP PORT ADAPNO=0, 2 *X
CUADDR=285, 3 *X
MEDIUM=RING, 4 *X
SAPADDR=4, 5 *X
TIMER=60
**
********************************************************************
RANETUG1 GROUP DIAL=YES,CALL=INOUT,DYNPU=YES
*
RANETUL1 LINE ANSWER=ON,ISTATUS=ACTIVE
RANETUP1 PU ISTATUS=ACTIVE
RANETUL2 LINE ANSWER=ON,ISTATUS=ACTIVE
RANETUP2 PU ISTATUS=ACTIVE
RANETUL3 LINE ANSWER=ON,ISTATUS=ACTIVE
RANETUP3 PU ISTATUS=ACTIVE
RANETUL4 LINE ANSWER=ON,ISTATUS=ACTIVE
RANETUP4 PU ISTATUS=ACTIVE
RANETUL5 LINE ANSWER=ON,ISTATUS=ACTIVE
RANETUP5 PU ISTATUS=ACTIVE
RANETUL6 LINE ANSWER=ON,ISTATUS=ACTIVE
RANETUP6 PU ISTATUS=ACTIVE
RANETUL7 LINE ANSWER=ON,ISTATUS=ACTIVE
RANETUP7 PU ISTATUS=ACTIVE
RANETUL8 LINE ANSWER=ON,ISTATUS=ACTIVE
RANETUP8 PU ISTATUS=ACTIVE
RANETUL9 LINE ANSWER=ON,ISTATUS=ACTIVE
RANETUP9 PU ISTATUS=ACTIVE
Figure 26. XCA Major Node Definition Sample for LSA Direct Connection
Sample Host Definitions 33

Notes:
1 TYPE must be XCA.
2 ADAPNO is the LAN number for the 2216 interface. This value is assigned to
the 2216’s LSA interface when it is created. The value can be obtained from the
2216 by listing the configuration of the interface from the talk 6 menus, or it can
be retrieved by entering the list nets command from the ESCON console in talk
5. Note that a wrong value for this parameter is the single most common error in
LSA configuration.
3 CUADDR specifies the subchannel to be used to communicate with the 2216.
This value must be within the range of values specified in the IODEVICE
statement in the IOCP definition.
4 This specifies the physical LAN topology to which the LSA interface is attached.
This corresponds to the value specified for LAN type for the 2216 interface. Valid
values are MEDIUM=RING for token-ring, MEDIUM=CSMACD for Ethernet, and
MEDIUM=FDDI for a fiber distributed data interface (FDDI) network.
5 SAPADDR is the service access point number VTAM wishes to open on the 2216.
Note that it is the SOURCE SAP, not the DESTINATION SAP. When more than
one active XCA major node refers to the same LAN, all the XCA major nodes
have to use different SAPs.
LINE Statement
The CALL field can be one of the following:
• IN means only remote devices may establish connections.
• OUT means only VTAM can initiate connections.
• INOUT connections may be initiated at either end.
If VTAM is going to dial out, the switched major node definition must specify a
destination with a Path statement.
An asterisk in the first column indicates a statement has been commented out
and should be ignored. A character in the last column indicates the next line is a
continuation of this line.
3.4.2 VTAM Definitions for an MPC+ Connection
An MPC+ connection requires entries in two VTAM control blocks:
• The Local Major Node
• The Transport Resource List (TRL) Major Node
Figure 27 on page 35 shows a sample definition of a local SNA major node for a
2216 MPC+ connection. This is the local PU that resides in VTAM that supports
the channel connection defined in the TRL. The connection type must be APPN
and you also need to enable HPR.
34 IBM 2216 and Network Utility Host Channel Connections

LOCNETU VBUILD TYPE=LOCAL
MPCNETUP PU TRLE=MPCNETU,
XID=YES,
CONNTYPE=APPN,
CPCP=YES,
HPR=YES
Figure 27. VTAM Local Major Node Definition
Notes:
1. TYPE must equal LOCAL on the VBUILD statement.
2. TRLE identifies the TRL being used. The name must match the name of an
existing TRL.
3. XID indicates whether XIDs will be exchanged. It must be XID=YES.
4. CONNTYPE must be set to CONNTYPE=APPN since APPN is the only
protocol that VTAM uses with an MPC+ connection.
5. CPCP specifies that CP-CP connections with APPN can be established over
this MPC+ connection. This could be set to either YES or NO, depending upon
your APPN topology.
6. HPR specifies that APPN HPR traffic can flow over this MPC+ connection.
HPR is normally used by default, but setting this value to YES ensures it. This
is important because an MPC+ connection requires RTP (and HPR).
Next, you need a transport resource list for the MPC+ connection from the 2216.
An example definition is shown in Figure 28.
VBUILD TYPE=TRL
MPCNETU TRLE LNCTL=MPC,
MAXBFRU=9,
READ=280,
WRITE=281,
MPCLEVEL=HPDT,
REPLYTO=3.0
Figure 28. VTAM Transport Resource List (TRL) Definition
Notes:
1. TYPE must be TRL.
2. MPCNETU is the name that identifies the TRL. It must match what is specified
in the TRLE=field in the local major node definition. (See Figure 27 on page
35).
3. LNCTL identifies the connection type. It must be LCNTL=MPC.
4. MAXBFRU is the number of 4K pages per read subchannel.
5. READ/WRITE specifies the subchannels in the MPC+ group and indicates
their direction. The subchannel numbers must be in the range of addresses
specified in the IODEVICE statement in the IOCP definition. There can be
multiple READ and WRITE parameters in the TRLE statement, but there must
be at least one of each.
Sample Host Definitions 35

NOTE
3.4.3 VTAM Definitions for APPN
The designations READ and WRITE here are from the host perspective. In the
2216 MPC+ definition, the designations are from the 2216 perspective.
Therefore, subchannels designated as READ on the host must be designated
as WRITE on the 2216, and vice versa.
6. REPLYTO is the reply time-out value in seconds.
If VTAM is configured for the dependent logical unit server (DLUS), then it must
be an APPN network node. Configuring VTAM as an APPN network node
requires certain parameters to be specified in the VTAM start-up parameters.
These are shown in Figure 29 on page 36. Set the CONNTYPE to APPN and the
NODETYPE to a Network Node (NN).
ASYDE=TERM,IOPURGE=5M,
CONFIG=I0,
CONNTYPE=APPN,
CPCP=YES,
CSALIMIT=0,
DYNADJCP=YES,
ENCRYPTN=NO,
GWSSCP=YES,
HOSTPU=ISTPUS18,
HOSTSA=18,
HPR=RTP,
NETID=USIBMRA,
NODETYPE=NN,
NOTRACE,TYPE=VTAM,IOINT=0
PPOLOG=YES
SORDER=APPN,
SSCPDYN=YES,
SSCPID=18,
SSCPNAME=RAI,
SSCPORD=PRIORITY,
SUPP=NOSUP,
TNSTAT,CNSL,
VRTG=YES
OSITOPO=LLINES,
OSIMGMT=YES
XNETALS=YES
Figure 29. VTAM Startup Parameters
3.4.4 VTAM Static Definition of TN3270 Resources
VTAM definitions are required for the PUs used by the TN3270E Server. You need
a switched major node definition for each PU in the TN3270E Server. For
example, each PU in the TN3270E Server can support up to 253 LUs. If you need
500 3270 sessions, then you will need two PUs in the router and two PU
definitions in VTAM.
Figure 30 on page 37 shows an example of a VTAM switched major node
definition for a TN3270E Server PU that is connected via DLUR and APPN.
36 IBM 2216 and Network Utility Host Channel Connections

LOCNETU VBUILD TYPE=SWNET
MNETUA PU ADDR=01,ISTATUS=ACTIVE,VPACING=0, *
DISCNT=NO,PUTYPE=2,SSCPFM=USSSCS,USSTAB=US327X, *
IDBLK=077,IDNUM=02216,IRETRY=YES,MAXDATA=521, *
MAXOUT=7,MAXPATH=8,PASSLIM=7,PACING=0,ANS=CONTINUE
********************************************************************
PNETUA PATH PID=1,DLCADDR=(1,C,INTPU),DLCADDR=(2,X,07702216), *
DLURNAME=MNETUA
********************************************************************
JC7LU2 LU LOCADDR=2
JC7LU3 LU LOCADDR=3
JC7LU4 LU LOCADDR=4
Figure 30. VTAM Definitions for a TN3270E Server PU (DLUR/APPN)
Figure 31 on page 37 shows an example of a VTAM switched major node
definition for a TN3270E Server PU that uses a subarea connection to the host.
LSAP08T VBUILD TYPE=SWNET
PUPS08T PU ADDR=01,IDBLK=077,IDNUM=12244,
MAXOUT=7,PACING=0,VPACING=0,
DLOGMOD=B22NNE,PUTYPE=2, 1
SSCPFM=USSSCS,MAXDATA=2000,MODETAB=LMT3270
PT08LU2 LU LOCADDR=02,LOGAPPL=TSO
PT08LU3 LU LOCADDR=03,LOGAPPL=TSO
PT08LU4 LU LOCADDR=04,LOGAPPL=TSO
PT08LU5 LU LOCADDR=05,LOGAPPL=TSO
PT08LU6 LU LOCADDR=06,LOGAPPL=TSO
Figure 31. VTAM Definitions for a TN3270E Server PU (Subarea)
1 PUTYPE here is chosen as PUTYPE=2 but can be any other PUTYPE
depending on the configuration scenario.
The following sections provide an overview of the statements in the switched
major node definition.
3.4.4.1 VBUILD Statement
The TYPE field must be TYPE=SWNET.
3.4.4.2 PU Statement
This statement defines the type of data flow and the destination. The pertinent
parameters are:
• ADDR is an identifier.
• MAXDATA is the maximum packet size VTAM will support over this interface.
This value will be negotiated down with the 2216 during the XID exchange.
• IDBLK/IDNUM identify the remote device when VTAM is communicating with
PU 2.0 (dependent) devices.
3.4.4.3 LU Statement
These statements define the logical units (LUs) that can be contacted through
this PU. The name on the left of each statement is the name that the host uses to
address each LU. The LOCADDR is used by the 2216 to identify the correct LU in
VTAM.
Sample Host Definitions 37

3.4.4.4 Path Statement
If VTAM is going to dial out, the switched major node definition must specify a
destination with a Path statement. The Path statement will be different depending
on whether the TN3270E Server attaches via a subarea or a DLUR/APPN
connection.
For a subarea connection, the format is:
PATH DIALNO=xxyyzzzzzzzzzzzz
Where:
• xx is a place holder
• yy is the destination SAP number
• zzzzzzzzzzzz is the 12-digit destination MAC address
The example in Figure 31 on page 37 does not have a Path statement because in
this example, the downstream PU will contact VTAM instead of VTAM dialing out
to the device.
The example in Figure 30 on page 37 shows a Path statement for a TN3270E
Server PU that is using DLUR to connect to the host. Here, the Path statement
identifies the CP name of the 2216 (MNETUA) via the DLURNAME parameter.
This is needed in order for the LU6.2 conversation between the DLUR and DLUS
to be established. Once this session has been established, the SSCP-PU session
between VTAM and the TN3270E Server PU will be established using the
IDBLK/IDNUM value specified by DLCADDR=(2,X,07702216).
3.4.5 VTAM Dynamic Definition of TN3270 Resources
VTAM contains support for several facilities that reduce the amount of user coding
required to define its resources such as PUs and LUs. When implemented in
2216, TN3270 PUs and LUs appear as switched resources to the VTAM host and
require corresponding definitions in VTAM. When large TN3270E environments
are being implemented, the definition of these resources could be a very labor
intensive task.
VTAM provides a facility that allows switched resources to be defined
dynamically. TN3270E can take advantage of this facility to reduce the amount of
VTAM definitions the user has to provide. This facility is called VTAM Dynamic
Dial-In Support. This function should not be confused with a similar VTAM
function call Dynamic Definition of Dependent LUs (DDDLUs), which requires
co-requisite function to be present in the TN3270 Server. The 2216 supports this
co-requisite function since MAS V3.2.
The details for Dynamic Dial-In Support are in VTAM Customization, LY43-0075
(available to IBM-licensed customers only) for the release level of VTAM that is
installed on your VTAM host. A brief description of this function and its potential
use in a TN3270E environment follows.
3.4.5.1 General Overview
Dynamic Dial-In Support makes use of a VTAM exit called the Configuration
Services Exit (ISTEXCCS), and a set of model PU/LU definitions that you must
define. Each time VTAM receives a connection request from a PU that is not
defined to VTAM, the Configuration Services Exit is driven and a set of PU and
LU definitions is dynamically generated based on the model definitions. These
38 IBM 2216 and Network Utility Host Channel Connections

definitions are associated with the PU requesting connection. This set of
definitions can be tailored to the specific PU level, with matching based on
information contained in the dial-in PU's XID. This process is repeated each time
a connection request is received from a PU that is not defined to VTAM.
Figure 32 on page 39 contains a VTAM definition for a set of model definitions
that could be used to implement Dynamic Dial-In Support. Notice that the
definition is created in a VTAM member with a VBUILD TYPE=MODEL. This
example contains two PU models and two models for LUs. They are the
prototypes from which VTAM will generate its dynamic resource definitions. From
a practical point of view, if all of the PUs and LUs configured for TN3270E have
similar characteristics such as logmode and pacing values, then a single PU and
LU definition in the model definition would be sufficient.
The VTAM Configuration Services Exit mentioned above could be used to select
the appropriate model definition based on XID parameters such as CPNAME and
IDNUM/IDBLK. The corresponding values stored in the VTAM data sets CPNDEF
and NIDDEF indicate which model should be used. If these data sets are not
defined, the exit has an internal algorithm to select the model and generate LU
resource names. This exit routine can be used as is or modified to fit user needs.
See 3.4.7, “Implementing Dynamic Definitions” on page 40 for a description of the
default name generation algorithm and how you can control what resource names
are generated.
Model Major Node
VBUILD
TYPE=MODEL
PUMOD1 PU
ADDR=C1,ANS=,...
LUMOD1 LU LOCADDR=2,..
PUMOD2 PU ADDR=C2
LUMOD2 LU LOCADDR=3,...
Figure 32. VTAM Dynamic Resource Definition
VTAM Host
2216 Definitions:
PUV1 PU IDNUM=11111,,,,
LU1_1 LOCADDR=2,,,
LU1_2 LOCADDR=3,,,
...
LU120 LOCADDR=20
PUV2 PU IDNUM=22222,,,
LU2_1 LOCADDR=2,,,
LU2_2 LOCADDR=3,,,
....
LU2_10 LOCADDR=10
PU1 IDNUM=11111,POOL=20
PU2 IDNUM=22222,POOL=10
ISTDSWMN
In Figure 32 on page 39, the 2216 has two PUs defined. PU1 has 20 pooled LU
resources defined and PU2 has 10 pooled LU resources defined. In the VTAM
host a model major node that contains two PU and two LUs is defined. These
model definitions will contain all of the normal PU and LU parameters such as
polling address, logmode tables, maxdata values, and PU type that would
normally be defined for specific PUs and LUs. As mentioned earlier, if all of the
Sample Host Definitions 39

characteristics of the connecting devices are similar a single PU and LU definition
in the model would be sufficient.
In this example, VTAM would dynamically generate the definitions shown in
ISTDSWMN, a dynamically created major node. ISTDSWMN contains definitions
for a PUV1 and 20 LUs (LU1_1 through LU1_20) and for a PUV2 with 10 LUs
(LU2_1 through LU2_10). Notice that the PU names in the 2216 configuration do
not have to match the names that VTAM generates. The PUs in the 2216 are
correlated to the VTAM PUs based on matching IDNUM values. Notice also that
the only definitions required to implement the dynamic definitions are done on the
VTAM host. The 2216 does not know that VTAM is performing the dynamic
definition process.
3.4.6 Dynamic Dial-In Exit Overview
The Configuration Services Installation Exit (ISTEXCCS) is shipped with VTAM
and can be found in the data set SYS1.SAMPLIB. This exit is described in an
appendix of the VTAM Customization, LY43-0075 (available to IBM-licensed
customers only) for the release of VTAM installed on your host.
If the exit is installed in the VTAMLIB data set at VTAM initialization time, it will be
loaded and started during VTAM initialization. VTAM calls the exit whenever it
receives a REQCONT RU from a real switched PU, or a REQACTPU from a
DLUR node representing a PU. These RUs are generated by the receipt of an XID
from the connecting device. They contain XID information such as NETID,
CPNAME and IDNUM/IDBLK. The exit uses this information to construct a build
vector. The build vector contains the model names for PU and LU definitions
contained in an active model major node, and the names to be used for the PU
and LU definitions that VTAM is to create. VTAM then builds the definitions for the
connecting PU in the dynamic switched major node ISTDSWMN. From this point
on, VTAM treats these resources just as if they had been predefined by you.
3.4.7 Implementing Dynamic Definitions
Resource Name Generation: There are two ways for you to influence what
resource names will be associated with the resources that VTAM dynamically
generates. The first permits complete control by allowing you to supply specific
LU and PU names for the resource definitions that VTAM generates. This support
is implemented by coding the appropriate information in the VTAM data sets
CPNDEF and/or NIDDEF. These data sets provide the information that the
configuration services exit uses to construct the build vector that VTAM uses to
generate the dynamic resources. While this approach requires more user VTAM
definitions, it is much less definition intensive than manually defining the required
VTAM definitions.
At the other extreme, you can allow VTAM to generate the resource names based
on an internal algorithm. Implementations not requiring unique naming
conventions would be candidates for this approach, which requires minimal VTAM
definitions.
The name generated for the PU is of the form cnnnnnss, where:
• c can be user-specified in a name definition table
• nnnnn is the IDNUM extracted from the received XID
40 IBM 2216 and Network Utility Host Channel Connections

3.5 Host IP Definitions
• ss is the station address (if specified), otherwise it consists of two blank
characters
The name generated for the LU is of the form cnnnnnll, where:
• c is a user-specified name prefix
• nnnnn is the IDNUM extracted from the received XID
• ll is the local address of the LU
The details for both of these approaches to resource name generation can be
found in VTAM Customization, LY43-0075 (available to IBM-licensed customers
only).
Operational Considerations: The dynamically created definitions in the
dynamic switched major node ISTDSWMN are kept as long as there are active
LU sessions on the LU. If you specify DISCNT=YES on the Model PU definition,
all of the dynamic resources associated with the PU will be deleted from
ISTDSWMN when all of the sessions on the PU have ended. If you specify
DISCNT=NO, these definitions will not be deleted as long as the PU remains
active to VTAM.
Security Considerations: When the Configuration Services Exit dynamically
defines resources, VTAM has no predefined IDNUM/IDBLK or CPNAME to
validate the identity of connecting devices. If this is considered a security
exposure, the exit can be modified to consult a list of acceptable IDNUM/IDBLKs
or CPNAMEs and compare these values to those contained in the XID from the
connecting device. Note that the XID from the connecting device is passed to the
exit.
Sources for Additional Information: The details for this facility and additional
information can be found in the following VTAM library documents:
VTAM V4R4 Customization, LY43-0075 (available to IBM-licensed customers
only)
VTAM V4R4 Resource Definition Reference, SC31-8377
VTAM V4R4 Network Implementation Guide, SC31-8370
You should use the manuals corresponding to the release level of the VTAM
installed on your VTAM host.
Defining the 2216 to the host for a TCP/IP connection requires you to make
changes to the host TCP/IP profile. This section gives an overview of the relevant
statements that need to be changed.
3.5.1 DEVICE Statement
This statement defines the subchannel pair being used by TCP/IP. The format is:
DEVICE name LCS subchannel
Where:
• name identifies the subchannel path being used. It has local significance only
and can be anything.
Sample Host Definitions 41

• subchannel identifies the even subchannel being used for this connection. This
value comes from the IODEVICE statement in the IOCP definition. When
specified, that subchannel and the next one are both being used.
A TCP/IP profile must contain one DEVICE statement for each subchannel pair
being used.
3.5.2 LINK Statement
This statement identifies which LCS interfaces on the 2216 are being used on a
given subchannel pair. The format is:
LINK name lantype lannumber devicename
Where:
• name identifies the LCS interface. It has local significance only, and can be
anything.
• lantype identifies the type of LAN interface that the 2216 LCS interface is
emulating. The allowable values are:
• IBMTR for token-ring
• ETHERNET for Ethernet V2
• 802.3 for Ethernet (IEEE 802.3)
• ETHER or 802.3 for either Ethernet format accepted
• FDDI for FDDI
• lannumber identifies which LCS interface on the 2216 is being used. The LAN
number is generated sequentially for each LAN type on the 2216 when you
add an LCS interface. The LAN number can be found by entering list nets
from the ESCON console in talk 5. Note that the LAN number is not the net
number. Having the wrong LAN number is the single most common
configuration error for an LCS interface.
• devicename correlates the LCS interface to a subchannel pair. It must match a
previously defined DEVICE statement.
There can be multiple LINK statements associated with a single DEVICE
statement. There must be an LCS interface on the 2216 for each LINK statement.
3.5.3 HOME Statement
This statement specifies the IP address(es) of the host TCP/IP stack. The format
is:
HOME ipaddress1 link1
ipaddress2 link2
Where:
• ipaddressx specifies an IP address on the host.
• linkx specifies which link is associated with this IP address.
There must be only one HOME address for each LINK statement. If LCS routing
is being implemented in the 2216, the HOME IP address must be in the same
subnet as the LCS IP address.
42 IBM 2216 and Network Utility Host Channel Connections

3.5.4 GATEWAY Statement
This statement identifies the IP routing information for the host. It is divided into
three sections:
• Direct Routes are routes directly connected to the host. The subnet containing
the 2216 LCS interface is a direct route.
• Indirect Routes are routes that are accessible via routers. The subnets of the
LANs on the 2216 are indirect routes, for example.
• Default Route is the route to be used if the host doesn't have a direct or
indirect route to an IP address.
3.5.4.1 Direct Routes
The format for Direct Routes is:
network firsthop linkname pktsize submask subvalue
Where:
• network is the non-subnetted part of the IP address.
• firsthop indicates the IP address of the next hop in the IP network. For Direct
Routes, this should be an equal sign (=).
• linkname identifies which link the host should use to get to the addresses on
this route. For routes accessible via the 2216, this should be the name from
the LINK statement associated with the LCS interface on this subnet.
• pktsize is the maximum frame size to be used on the interface. It should be
less than or equal to the packet size defined in the LCS configuration on the
2216. A value of DEFAULTSIZE indicates the default packet size will be used.
• submask specifies the subnet mask used on this link. The subnet mask should
correspond to the subnet mask defined for the LCS interface in the IP
configuration on the 2216. This field may also be set to host to identify a
point-to-point connection. In this case, the network field should contain the full
IP address of the LCS interface.
• subvalue specifies the subnetted part of the IP address, and together with the
network field, should fully specify the IP subnet associated with this LCS
interface.
3.5.4.2 Indirect Routes
The format for Indirect Routes is:
network firsthop linkname pktsize submask subvalue
Where:
• network is the full address of the IP subnet.
• firsthop indicates the IP address of the next hop in the IP network. For Indirect
Routes accessible via the 2216, this should be the IP address of the 2216 LCS
interface.
• linkname identifies which link the host should use to get to the addresses on
this route. For routes accessible via the 2216, this should be the name from
the LINK statement associated with the LCS interface on this subnet.
• pktsize is the same value as for Direct Routes.
Sample Host Definitions 43

3.5.5 START Statement
• submask should either be 0 or blank if the network field contains the full subnet
address.
• subvalue should be left blank if there is no subnet mask specified.
Default Routes
The format for Default Routes is:
network firsthop linkname pktsize submask subvalue
Where:
• network should be DEFAULTNET.
• firsthop indicates the IP address of the next hop in the IP network. For Default
Routes to the 2216, this should be the IP address of the 2216 LCS interface.
• linkname identifies which link the host should use to get to the addresses on
this route. For routes accessible via the 2216, this should be the name from
the LINK statement associated with the LCS interface on this subnet.
• pktsize is the same value as for Direct Routes.
• submask should either be 0 or blank.
• subvalue should be blank.
This statement causes the specified subchannels to be started. The format is:
START devicename
Where devicename is the name on the DEVICE statement above.
There must be a START statement for every DEVICE statement if the customer
wishes to activate the devices when TCP/IP is started. If the START statement is
not here, the devices can be started using the OBEY file. Note that the name here
is the one from the DEVICE statement, not the LINK statement. Note also that the
2216 LCS interface will remain in the DOWN state until the START statement has
been issued from TCP/IP.
3.5.6 Host TCP/IP Definitions for LCS
This section gives you examples of the above statements required if you are
defining an LCS connection.
1. DEVICE statement:
DEVICE LCS1 LCS 210
Where LCS1 is the device name being defined, LCS isthetypeofdevice,and210
is the host read (2216 write) subchannel used for this definition.
2. LINK statement
LINK ETHLCS1 802.3 0 LCS1
Where ETHLCS1 is the link name, 802.3 is the LAN type to which the LCS
interface attaches on the 2216, 0 is the LAN number assigned by the 2216,
and LCS1 is the name of the device (from the device statement above).
44 IBM 2216 and Network Utility Host Channel Connections
Note: Remember that the LAN number is automatically assigned by the 2216
when you define the LCS interface. You can obtain it by issuing a list of all

commands from the ESCON Config> prompt in the talk 6 process on the 2216
console.
3. HOME command
HOME 9.24.106.72 ETHLCS1
Where 9.24.106.72 is the IP address of this LCS interface, and ETHLCS1 is the
name of the link.
4. GATEWAY command
GATEWAY 9.24.106 9.24.106.1 ETHLCS1 4096 0
Where 9.24.106 is the IP address for the network, 9.24.106.1 is the IP address
of the default router, ETHLCS1 is the link name defined by the LINK statement
above, 4096 is the MTU size, 0 is the subnet mask, and the subnet value has
been left blank.
5. Activate the TCP/IP profile
To activate the device defined in 1, issue the start lcs1 command.
3.5.7 Host TCP/IP Definitions for MPC+
The steps for configuring TCP/IP in the host for an MPC+ connection are the
same as for an LCS connection. However, the command syntax for the device
and link commands is slightly different. For an MPC+ connection, the syntax for
the device command is:
DEVICE IPTRL1 MPCPTP
Where IPTRL1 is the name of the TRL that this connection will use, and MPCPTP
specifies an MPC point-to-point link.
To define the link, the syntax is:
LINK LINK1 MPCPTP IPTRL1
3.6 Host HPDT UDP Definitions
Where LINK1 is the link name and the other two parameters are the same as those
used in the device statement.
High-performance data transfer (HPDT) for User Datagram Protocol (UDP), also
called High Speed UDP extends the existing HPDT services capability introduced
in VTAM V4R4 to include support for applications using the UDP of the TCP/IP
protocol suite. High Speed UDP reduces CPU cycle consumption and achieves a
more efficient transfer of data. OS/390 applications that issue OpenEdition socket
calls over UDP can achieve these benefits when transferring data over certain
high-bandwidth HPDT configurations.
For OS/390 Release 3, HPDT for UDP is available through the following
program temporary fixes (PTFs), associated with APAR PQ03737:
• UQ07222, for TCP/IP for MVS V3R2
• UQ07223, for OS/390 TCP/IP OpenEdition
For setting up HPTD for UDP in the host, refer to OS/390 TCP/IP Update Guide,
GC31-8553.
Sample Host Definitions 45

3.6.1 oeifconfig
In this section we describe commands that are used to configure and display
information about HPDT UDP. The commands in this chapter can be used after
you have prepared your system as described in "Setting Up the HPDT
Connection for UDP" in the book mentioned above. All commands are issued
from the OpenEdition/MVS shell. Issuing a command with no parameters displays
the syntax of the command.
Because settings by the oeifconfig and oeroute configuration commands are for
the duration of an IPL, the best place for them is in the /etc/rc shell script, so the
OpenEdition initialization always configures the HPDT UDP stack. For more
information about customizing the OpenEdition shell, as well as the sample
/etc/rc script, see OS/390 UNIX System Services Planning, SC28-1890.
This command assigns an IP address to the network interface and configures
network interface parameters. A network interface must be configured and
activated before applications can use HPDT UDP. This command can be used to
perform the following specific tasks:
• Configure an OSA FDDI network interface for HPDT UDP
• Configure an ESCON network interface for HPDT UDP
• Activate, deactivate, or remove the configuration of an HPDT UDP network
interface
• Query the status of an HPDT UDP network interface
This command might typically be issued from the /etc/rc script that executes
when OpenEdition initializes. Superuser authority is required to configure,
activate, deactivate, or remove the configuration of an HPDT UDP network
interface.
The format for configuring an ESCON network interface for HPDT UDP is:
oeifconfig interface_name source_IP_address destination_IP_address optional parameters
Where:
• interface_name specifies the 1- to 8- character name of the interface
corresponding to the label specified on the VTAM TRLE definition statement
for the connection.
• source_IP_address specifies the OS/390 home IP address of this interface. This
address must be unique for the entire OS/390 image, which includes the
full-function TCP/IP stack. The IP address can be expressed either in dotted
decimal format (for example, 9.117.81.65) or as a symbolic name known to a
domain name server (for example, abc.def.ibm.com).
• destination_IP_address specifies the IP address of the destination of a
point-to-point connection (for example, an ESCON-channel attached 2216).
The IP address can be expressed either in dotted decimal format (for example,
9.117.81.65) or as a symbolic name known to a domain name server (for
example, abc.def.ibm.com).
• optional parameters are:
46 IBM 2216 and Network Utility Host Channel Connections
checksum: Determines whether checksum support is enabled for this network
interface.

3.6.2 oeroute
up/down Activates/deactivates a network interface.
metrics Specifies the number of hops for the interface in a range from 0 to
16. The OpenEdition common INET component uses this number
to determine the best route to a host.
mtu Specifies the maximum transmission unit size for the interface. All
hosts connected to the same ESCON link must agree on a
common maximum transmission unit size.
netmask Specifies the subnet mask associated with the interface. If
netmask is not specified, the subnet mask is based on the local
address portion of the destination address.
The oeroute command is used to add or delete an entry in the HPDT UDP routing
table. Routes are typically added to connect to remote hosts. Since oeifconfig
builds the routes for the local hosts, oeroute is only necessary for remote
connections beyond the ESCON link or OSA LAN. HPDT UDP supports static
routes added by HPDT UDP commands, but does not support dynamic routing
using a route daemon.
The oeroute command distinguishes between routes to hosts and routes to
networks by interpreting the destination IP address. If the destination has a local
address part of 0 or if the destination is the symbolic name of a network, then the
route is assumed to be to a network. Otherwise, the destination is presumed to be
a route to a host. You can force the destination to be interpreted as a network or
as a host by specifying the optional keywords -net and -host.
This command might typically be issued from the /etc/rc script that executes
when OpenEdition initializes. Superuser authority is required to update the HPDT
UDP network routing table.
oeroute flags add/delete inet destination_IP_address gateway_IP_address metric
host/net netmask
Where:
• flags may be one of the following:
-n indicates that numeric IP addresses rather than symbolic names
are displayed in any output from the oeroute command.
-q: suppresses output of the oeroute command (quiet mode).
-v: displays information as output for the oeroute command (verbose
mode).
• add/delete adds a new route to the HPDT UDP routing table or deletes an
existing route from the HPDT UDP routing table.
• -inet specifies the address_family for this interface. The only supported
address_family for this command is -inet, which is the default.
• destination_IP_address specifies the IP address of the destination for the route.
The address can indicate either a destination host or a destination network. A
default route can be indicated by specifying default instead of an IP address.
• gateway_IP_address specifies the IP address of the gateway or next hop to reach
the destination address.
Sample Host Definitions 47

3.6.3 oeping
3.6.4 oenetstat
• metric specifies the metric number (number of hops) associated with this
route (from 0 to 16). The OpenEdition common INET component uses this
number to determine the best route to a host.
• -host forces the destination address to be treated as a host address rather
than a network address. This parameter is incompatible with the -net and
-netmask parameters.
• -net forces the destination address to be treated as a network address rather
than a host address.
• -netmask subnet_mask: specifies the subnet mask associated with the destination
address. Do not confuse this parameter with subnet mask assigned to a local
interface using the oeifconfig command. -netmask here applies only to the
destination address(es) of the route being defined.
The oeping command sends an echo request to obtain an echo response from a
host or gateway.
This command uses the ICMP protocol. If you experience any problems using
oeping, examine /etc/protocols to ensure that the ICMP statement is specified.
oeping flags host
The oenetstat command displays HPDT UDP network information gathered from
the internal data structures of the HPDT UDP communication stack.
The format of this command is:
oenetstat -i/I interface -m -n -r -s -p protocol
Where:
• -i shows the state of all configured interfaces.
• -I interface shows the state or statistics of a specific configured interface.
• -m shows memory-related statistics.
• -n shows network addresses as numbers. When this flag is not specified, the
command interprets addresses and displays them symbolically where
possible. If this is not possible, then numbers in dotted decimal format are
used instead.
• -r shows routing table data.
• -s shows packet or routing related statistics for different protocols.
• -p protocol specifies the name of the protocol to be displayed.
48 IBM 2216 and Network Utility Host Channel Connections

Chapter 4. Link Services Architecture
4.1 2216 LSA Support
The LSA protocol was created to communicate two different processors in a way
that one of the processors contains the lower two layer levels of the protocol
stack, and the other processor contains the remaining upper layers. The two
lower layers can then run on a control unit or other processor device and the
upper layers can run on the IBM host.
LSA provides support for SNA over the channel. Each LSA path is a single
bidirectional subchannel between the host application and the control unit. The
host application (VTAM) issues a READ command immediately following each WRITE
command to retrieve data from the channel. The control unit also issues an
ATTENTION command when it has something for the host application to read.
LSA has a command interface that allows VTAM to open service access points
(SAPs) to communicate with downstream workstations using the IEEE 802.2
Logical Link control (LLC) interface.
Multiple VTAMs can share the same LSA net handler if each opens a different
SAP so that the traffic destined to different hosts is multiplexed over the same net
handler by extending the network address with the SAP.
SNA supports multiple SAPs. The SAP allows traffic to pass to and from different
end-to-end logical connections. TCP/IP does not support multiple SAPs, that’s
why the same LCS net handler cannot be shared for TCP/IP host applications
running on different hosts.
The channel blocking/deblocking mechanism for LSA subchannels is the same as
for LCS subchannel pairs.
LSA provides support for hierarchical SNA (including DLSw), APPN ISR and
APPN HPR.
LSA support on the 2216 has three possibilities that provide three different
appearances from the 2216 point of view:
1. LSA Direct Connection: Local LAN interfaces are associated to the host
channel. The LAN can be token-ring, Ethernet, FDDI or an emulated LAN.
This is an SNA Passthru connection.
2. LSA DLSw connection: It may be local or remote DLSw. The SNA traffic will be
encapsulated on IP (remote DLSw) or converted to SDLC, FR BAN, X.25
QLLC, DLC (local DLSw).
3. LSA APPN connection: Apart from adding the LSA interface, the APPN
loopback interface is added also to the 2216. In this connection the 2216
becomes an adjacent network node of the host.
4.1.1 LSA Direct Connection
With the LSA direct connection there is an association between the LSA interface
and one of the LAN interfaces on the 2216. The LAN can be token-ring, Ethernet,
FDDI or an emulated LAN. Only one LAN can be associated per LSA interface.
© Copyright IBM Corp. 1998 49

As has been explained previously in this chapter, the LSA protocol allows the
protocol stack to be separated into two parts, one part running on the host and
the other on the 2216. With this configuration the 2216 LAN interface is
considered a LAN interface on the host, creating the appearance that the host is
on the LAN. Then, the MAC address defined on that LAN interface on the 2216
will be the one that identifies the host in the network.
Every frame with a destination MAC address of the LAN interface on the 2216 will
be forwarded automatically over the channel to the host.
LSA
Token ring
network
Figure 33. LSA Direct Connection Appearance
Based on Figure 33 the parameters that have to be configured on the 2216 for
having a direct connection are:
Subchannel: LSA uses a single bidirectional subchannel between the host
and the 2216.
Net Link: This is the network interface number of the LAN adapter to which
the LSA network is linked. This is the interface used by the 2216
to transmit data from the host to the network.
4.1.2 LSA DLSw Connection
DLSw is a forwarding mechanism for the LLC2, SDLC, and QLLC (SNA over
X.25) protocols. It relies on the bridging function of the router, the
switch-to-switch protocol (SSP), and TCP/IP to provide a reliable transport of
SNA traffic over an internet. DLSw does not provide full routing capabilities, but it
provides switching at the data link layer. Rather than bridging LLC2 frames, DLSw
encapsulates their data in TCP frames and forwards the resulting messages over
the WAN link to a peer DLSw router for delivery to their intended end-station
addresses.
There are two types of data link switching:
1. Remote Data Link Switching: Stations attached to two or more DLSw routers
communicate across an IP network using DLSw.
2. Local Data Link Switching: The DLSw function is performed within a single
2216. Local DLSw can support conversion to LLC2 from DLC, Frame Relay
BAN or X.25 QLLC attached devices.
50 IBM 2216 and Network Utility Host Channel Connections
HOST
Base Net Handler
LSA
Ethernet
network
LSA
FDDI
network
2216
Logical
Appearance:
host

When an LSA interface is defined, a new interface is created in the 2216. By
enabling loopback on the LSA interface a virtual LAN is simulated inside the
router on which the only devices are the LSA interface (endpoint of the host) and
the endpoint of the DLSw network.
LLC loopback is an extension of the virtual LAN adapter concept to allow VTAM
connections with the APPN and DLSw functions in the 2216. For more
information about the loopback refer to 4.2, “LLC Loopback” on page 54.
The remote DLSw connection appearance is shown in Figure 34.
2216
Base Net Handler
LSA
loopback
enabled
DLSw
Figure 34. LSA Remote DLSw Connection Appearance
The local DLSw connection appearance is shown in Figure 35 on page 51:
LSA
MAC @1
HOST
Base Net Handler
MAC @1
FR BAN
connection
IP Code
HOST
DLSw
SDLC
adapters
loopback
enabled
Figure 35. LSA Local DLSw Connection Appearance
adapters
supporting
IP
2216
X.25
QLLC
LAN
adapters
Logical
Appearance:
host
2216
IP
Network
2216
Logical
Appearance:
host
2216
DLSw
Peers
Link Services Architecture 51

As shown in Figure 34 on page 51 and Figure 35 on page 51, the following need
to be configured on the DLSw connection:
Subchannel: LSA uses a single bidirectional subchannel between the host
and the 2216. One or more subchannels can be configured
per LSA interface.
Enable loopback: On the LSA interface for simulating the virtual LAN.
LAN type: Type of LAN connection, token-ring, Ethernet or FDDI. This
is the frame type that the host expects to send and receive.
MAC address: Marked as MAC@1 in the figures, it is a unique MAC
address to identify the host side of the loopback connection.
Then the DLSw protocol has to be configured.
4.1.3 LSA APPN Connection
Advanced peer-to-peer networking (APPN) extends the SNA architecture by
enabling Type 2.1 (T2.1) nodes to communicate directly without requiring the
services of an SNA host computer.
The APPN architecture allows four types of nodes in a network:
• APPN network nodes
• APPN end nodes
• Low-entry networking (LEN) end nodes
• PU 2.0 nodes supported by DLUR
The router can be configured as an APPN network node that supports
connections with all four node types. The router cannot function as an end node
for APPN.
As a network node, the router can act as a server to attached APPN end nodes
and LEN end nodes and provide functions that include directory services,
topology and routing services and management services.
LSA provides support for APPN ISR and HPR where HPR is an enhancement to
APPN architecture that provides better performance over high speed, low error
rate links using existing hardware. HPR replaces the normal APPN intermediate
session routing (ISR) with a Network Control Layer (NCL) containing a new type
of source routing function called Automatic Network Routing (ANR). The
complete HPR route is contained in the ANR packet allowing intermediate routing
nodes to route the packets with less processing overhead and storage.
HPR also eliminates the error recovery and flow control (session-level pacing)
procedures for each link between nodes and moves the error recovery and
flow/congestion control procedures to the endpoints of an HPR connection. A
transport layer using a new error recovery procedure called rapid transport
protocol (RTP) is used by the endpoints of the HPR connection. HPR
intermediate nodes have no session or RTP connection awareness.
The LSA APPN connection is configured in two stages:
1. The LSA interface is added to the router creating a new interface inside the
router which will have assigned a network number.
52 IBM 2216 and Network Utility Host Channel Connections

Then, loopback is enabled on the LSA interface simulating the LAN to which
the LSA interface attaches. See 4.2, “LLC Loopback” on page 54 for details on
LLC loopback.
The LSA interface represents the host attached to the LAN. The MAC address
assigned to this interface will be the MAC address that will identify the host in
the APPN network.
2. APPN loopback interface is added creating a new interface inside the 2216
with a new network number. This interface will be attached to the same virtual
LAN than the LSA interface (the loopback connection).
This new interface represents the 2216 attached to the LAN. The MAC
address assigned to this interface will be the MAC address that the host will
see as the MAC address of its adjacent network node.
The appearance of this configuration is seen in Figure 36:
LSA
loopback
enabled
Base Net Handler
MAC @1
MAC @2
APPN
loopback
Figure 36. LSA APPN Connection
HOST
APPN
LAN
adapters
WAN
Adapters
Logical
Appearance:
host
2216
Rest of APPN
Network
Based on Figure 36 on page 53, the following need to be configured on the APPN
connection:
Subchannel: Configure the subchannel or subchannels used by this
connection.
Enable loopback: On the LSA interface for simulating the virtual LAN and
configure for this interface:
LAN type: Type of the virtual LAN that appears when the loopback is
enabled. This LAN type must be configured for both, the LSA
net and the APPN loopback net, and must match in both cases
since both interfaces are attached to the same LAN.
MAC@1: MAC address to identify the host end of the loopback
connection. If the LAN type is Ethernet, then the MAC address
must be in canonical format.
Add the APPN loopback interface, and configure for this interface:
2216
Link Services Architecture 53

4.2 LLC Loopback
LAN type: Type of the virtual LAN that appears when loopback is
enabled. This LAN type must match the LAN type of the LSA
loopback since logically both interfaces, LSA and APPN
loopback, are attached to the same virtual LAN.
MAC@2: MAC address to identify the 2216 (APPN) end of the loopback
connection. As before, the MAC address must be in a format
along with the LAN type.
And finally, the APPN protocol has to be configured.
LLC loopback is an extension of the virtual LAN adapter concept to allow VTAM
connections with the APPN and DLSw functions in the 2216.
To establish a connection the LSA interface creates an LLC connection between
itself and the remote device across the LAN using IEEE 802.2 frames. In the 3172
there was an association between the subchannels belonging to the LSA
interface and a LAN adapter which made this behavior possible. This is not the
case for the 2216. Due to the way the 2216 has been designed, only in the LSA
direct connection there is a real association between the LSA interface and a LAN
interface. So, for the other two connection types (DLSw and APPN), the LAN that
the LSA interface expects to find between itself and the remote device has to be
simulated someway inside the router. This LAN is simulated by enabling LLC
loopback on the LSA interface.
HOST
Remote Application
Figure 37. LLC Normal Connection vs. LLC Loopback Connection
LLC loopback allows the 2216 ESCON channel adapter to communicate directly
with other LLC users (APPN and DLSw) in the 2216. Instead of turning
commands from LSA into 802.2 frames, they are converted into LLC notifications
and sent to the appropriate LLC user. So, the process is not exactly the same as
having a LAN but the result is the same.
LLC loopback allows the APPN network node in the 2216 to act as the adjacent
node to VTAM. It also permits VTAM to connect to remote devices and
applications using DLSw without requiring changes to VTAM’s LSA support, since
the loopback connection appears the same as a normal LLC connection to VTAM.
54 IBM 2216 and Network Utility Host Channel Connections
LSA
LLC
LSA primitive
LLC command
802.2 frame
LLC
LLC notification
HOST
LSA
LSA primitive
LLC command
LLC loopback
DLSw / APPN
LLC notification
2216

4.3 2216 LSA vs. Host Parameter Relationships
There are three steps to defining a channel-attached 2216 to the host when using
LSA as the channel protocol:
1. Define the 2216 to the host channel subsystem via the I/O configuration
program (IOCP) or the hardware configuration definition (HCD).
The IOCP macros needed for defining the 2216 to the host are:
• RESOURCE Statement: Identifies logical partitions.
• CHPID Statement: Identifies type of channel connection and who uses it.
• CNTLUNIT and IODEVICE Statements: Identify the 2216 connection to the
host.
2. Define the 2216 as a control unit to the host operating system.
3. Define the 2216 to the host VTAM.
• VTAM XCA Major Node Definition: This definition is the same as that one
used for an IBM 3172.
• Switched Major Node Definition file.
For more information about the host parameters refer to Chapter 3, “Sample Host
Definitions” on page 27.
The relationship between the definitions in the host and in the 2216 can be seen
in the following figures.
The 2216 LSA and host parameter relationship for an SNA connection is shown in
Figure 38 on page 56, and the parameter relationship for an APPN connection in
Figure 39 on page 58.
Link Services Architecture 55

2216/NetworkUtility (LSA) Parameter - Relationships - SNA
VTAM XCA Major Node Definition
X5303 VBUILD TYPE=XCA
RESOURCE PART=((A1,1))
CHPID PATH=((2C),TYPE=CNC,PART=(A1),SWITCH=E1)
Figure 38. SNA Connection: 2216 LSA Host Parameter Relationship
56 IBM 2216 and Network Utility Host Channel Connections
X5303PRT PORT CUADDR=284,MEDIUM=RING,ADAPNO=0
TIMER=60,SAPADDR=04
X5303 GROUP DIAL=YES,CALL=INOUT,DYNPU=YES,
AUTOGEN=(10,L,P)
MVSIOCPDefinitions
VTAM Switched Major Node Definition
CNTLUNIT CUNMBR=0280,PATH=(2C),CUADD=1,
SW5303V VBUILD TYPE=SWNET
UNITADD=((00,032)),LINK=(C9),UNIT=3172
P2216V PU ADDR=02,IDBLK=05D,IDNUM=99999,
PUTYPE=2,
USSTAB=US327X,DLOGMOD=D4C32XX3
L2216LU2 LU LOCADDR=02,
L2216LU3 LU LOCADDR=03,
L2216LU4 LU LOCADDR=04,
L2216LU5 LU LOCADDR=05,
L2216LU6 LU LOCADDR=06,
IODEVICE UNIT=3172,ADDRESS=(280,032),
CUNMBR=(0280)
LPAR 1
CHPID=2C
CC
ESCON
Director E1
C9
2216
PC Definitions:
USIBMRA.VALENCIA
BLOCKID=05D
PU ID=99999
Destin add=400022160001
Remote SAP=04
ESCON LSA Definitions:
LPAR 1
CU 1
Device 04
Link CC
Token
Ring
LAN number 0 (use "list all" to determine from the
ESCON config prompt)

Note
The destination MAC address that has to be set in the PC depends on the
implementation of the LSA in the 2216. If the LSA direct connection is being
used, the destination MAC address of the PC will be the MAC address of the
LAN associated to the LSA interface in the 2216. If the LSA local or remote
DLSw is being used the destination MAC address in the PC will be the MAC of
the LSA loopback interface (the one configured from the LSA interface config).
To run APPN over a 2216 LSA connection we have to add a PU statement for the
2216 to the VTAM switched major node definition, as seen in Figure 39 on page
58.
Link Services Architecture 57

2216/NetworkUtility (LSA) Parameter - Relationships - APPN
VTAM XCA Major Node Definition
VTAM Start List
X5303 VBUILD TYPE=XCA
NETID=USIBMRA
X5303PRT PORT CUADDR=284,MEDIUM=RING,ADAPNO=0
RESOURCE PART=((A1,1))
CHPID PATH=((2C),TYPE=CNC,PART=(A1),SWITCH=E1)
Figure 39. APPN Connection: 2216 LSA Host Parameter Relationship
58 IBM 2216 and Network Utility Host Channel Connections
TIMER=60,SAPADDR=04
X5303 GROUP DIAL=YES,CALL=INOUT,DYNPU=YES,
AUTOGEN=(10,L,P)
MVSIOCPDefinitions
VTAM Switched Major Node Definition
CNTLUNIT CUNMBR=0280,PATH=(2C),CUADD=1,
SW5303N VBUILD TYPE=SWNET
P2216N PU ADDR=02,
PUTYPE=2,
CPCP=YES,
CONNTYPE=APPN,
NN=YES,
DYNLU=YES
CPNAME=NN2216
UNITADD=((00,032)),LINK=(C9),UNIT=3172
IODEVICE UNIT=3172,ADDRESS=(280,032),
CUNMBR=(0280)
LPAR 1
CHPID=2C
ESCON
CC
Director E1
C9
2216
ESCON LSA Definitions:
PC Definitions:
LPAR 1
USIBMRA.VALENCIA
Destin add=400022160001
Remote SAP=04
Token
Ring
CU 1
Device 04
Link CC
Net ID=USIBMRA CP Name=NN2216
LAN number 0 (use "list all" to determine from the
ESCON config prompt)

Note
4.4 LSA SNA Support Examples
The destination MAC address of the PC for the case of the APPN connection
will be the MAC address of the adjacent node. In case the PC is in the local
LAN of the 2216, the destination MAC address will be the MAC address of this
LAN interface of the 2216.
The following steps must be followed in order to configure LSA support in the
2216:
1. Add the physical interface.
2. Add and configure the LSA handler depending on the type of LSA connection
you want the 2216 to provide, direct or DLSw.
3. Configure the subchannel.
4. If DLSw support, configure DLSw on the 2216.
4.4.1 Host Definitions
Before we can attach the 2216 to an ESCON channel, the host system must be
configured correctly.
4.4.1.1 IOCP and MVS Operating System Definitions
The IOCP definitions for the 2216 with ESCON channel attached are shown in
Figure 40. These definitions are the same ones used for LCS.
The CNTLUNIT statement defines the path from the host to the 2216 and is used
for the IOCP definitions.
The 2216 must be defined to an IBM Multiple Virtual Storage/Extended
Architecture (MVS/XA) or MVS/ESA operating system. This definition is
accomplished by updating the MVS control program with an entry for the 2216 in
the IODEVICE macro.
The IODEVICE statement in Figure 40 is for the MVS operating system.
Link Services Architecture 59

RESOURCE PARTITION=((A1,1) 1 ,(A2,2),(A3,3),(A4,4),(A5,5),(C1,6), *
(C2,7))
CHPID PATH=(2C),SHARED, *
PARTITION=((A1,A2,A3,A4),(A1,A2,A3,A4,A5)),SWITCH=E1, *
TYPE=CNC
CNTLUNIT CUNUMBR=0280,PATH=(2C),UNITADD=((00,032)) 2 ,LINK=(C9), *
CUADD=1 3 ,UNIT=3172
CNTLUNIT CUNUMBR=02A0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=2,UNIT=3172
CNTLUNIT CUNUMBR=02C0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=4,UNIT=3172
IODEVICE ADDRESS=(280,032),UNITADD=00,CUNUMBR=(0280),STADET=Y, *
PARTITION=(A1),UNIT=3172
IODEVICE ADDRESS=(2A0,032),UNITADD=00,CUNUMBR=(02A0),STADET=Y, *
PARTITION=(A2),UNIT=3172
IODEVICE ADDRESS=(2C0,032),UNITADD=00,CUNUMBR=(02C0),STADET=Y, *
PARTITION=(A4),UNIT=3172
Figure 40. LSA: IOCP and MVS Operating System Definitions
1 In this scenario we will connect to LPAR 1.
2 UNITADD defines the range of addresses reserved for this control unit. The first
number is the hex of the first subchannel assigned to this control unit. The second
number is the decimal number of subchannels assigned to this control unit. The
parameter device address defined in the 2216 must be in this range of addresses.
In this scenario we will use device address 04.
3 This value identifies the control unit address of the 2216. For the 2216, each
LPAR on a given CHPID must have a unique CUADD value. This value must
match the control unit parameter specified in the 2216.
4.4.1.2 VTAM Definitions
Configuring the VM or MVS host requires entries in two VTAM control blocks:
• XCA Major Node Definitions
• Switched Major Node Definitions
XCA Major Node Definitions
When defining a channel gateway using LSA to VTAM, a definition for an external
communications adapter (XCA) is required. This definition is the same as that
used for IBM 3172.
*******************************************************************
X5303 VBUILD TYPE=XCA 1
**
**
X5303PRT PORT ADAPNO=0, 2 *
CUADDR=284, 3 *
SAPADDR=4, 4 *
MEDIUM=RING 5
X5303GRP GROUP DIAL=YES,CALL=INOUT,DYNPU=YES, *
AUTOGEN=(10,L,P)
Figure 41. LSA: XCA Major Node Definitions
1 TYPE must be XCA
60 IBM 2216 and Network Utility Host Channel Connections

2 ADAPNO is the LAN number for the 2216 interface. This value is assigned to
the LSA 2216’s interface when it is created. The value can be obtained from the
2216 by listing the configuration of the interface from the talk 6 menus or can be
retrieved from the field LAN number by entering the list net command from the
ESCON console in talk 5. Note that this value is not the interface number for the
LSA interface that can be seen in list devices from talk 6. Also note that a wrong
value for this parameter is the single most common error in LSA configuration.
3 CUADDR specifies the subchannel to be used to communicate with the 2216.
This value must be within the range of values specified in the IODEVICE
statement in the IOCP definition for the ADDRESS parameter.
4 SAPADDR is the service access point VTAM wishes to open on the 2216. Note
that it is the SOURCE SAP, not the DESTINATION SAP. When more than one
XCA major node refers to the same LAN number all the XCA major nodes have to
use different SAPs.
5 This specifies the physical LAN topology to which the LSA interface is attached.
This value must match the LANtype parameter in the 2216 LSA interface. Valid
values are MEDIUM=RING for token-ring, MEDIUM=CSMACD for Ethernet and
MEDIUM=FDDI for a fiber distributed data interface (FDDI) network.
Switched Major Node Definitions
The switched major node defines PUs and LUs on the PCs accessing the host.
*************************** TOP OF DATA *****************************
SW5303V VBUILD TYPE=SWNET 1
P2216V PU ADDR=02, X
IDBLK=05D, X
IDNUM=99999, X
PUTYPE=2, X
CPNAME=VALENCIA, X
USSTAB=US327X, X
DLOGMOD=D4C32XX3
L2216LU2 LU LOCADDR=02
L2216LU3 LU LOCADDR=03
L2216LU4 LU LOCADDR=04
L2216LU5 LU LOCADDR=05
L2216LU6 LU LOCADDR=06
******************************* BOTTOM OF DATA ***************************
******************************** TOP OF DATA *******************************
SW5303M VBUILD TYPE=SWNET 1
P2216M PU ADDR=02, X
CPNAME=MAINZ, X
IDBLK=05D, X
IDNUM=99998, X
DLOGMOD=D4C32XX3, X
USSTAB=US327X, X
PUTYPE=2
L2216LU7 LU LOCADDR=02
L2216LU8 LU LOCADDR=03
L2216LU9 LU LOCADDR=04
L2216LUA LU LOCADDR=05
L2216LUB LU LOCADDR=06
******************************* BOTTOM OF DATA *****************************
Figure 42. LSA: Switched Major Node Definitions
Link Services Architecture 61

4.4.2 LSA Direct Connection
In this scenario we have defined a different member for each PC. Both are in
Figure 42 on page 61.
1 The TYPE field must be SWNET.
4.4.2.1 Network Environment Description
XCA Major Node Definitions
ADAPTNO=0
SAPADDR=4
MEDIUM=RING
------------------------------
SW Major Node Definitions
VALENCIA ...
MAINZ ...
------------------------------
MVSIOCPDefinitions
UNITADD=04
CUADD=1
Figure 43. Overview of LSA Direct Test Environment
4.4.2.2 2216 Configuration
The following steps must be followed in order to configure LSA support on the
2216 for a direct connection to the host:
• Add the physical interface to the 2216.
• Add an LSA virtual interface.
• Configure a LSA virtual interface.
• Configure the LSA subchannel.
In this section we will perform these items step by step and explain the
configuration parameters with regard to our test environment which is shown in
Figure 43 on page 62. Not all config parameters will be highlighted here but may
be needed to tune your network. For further details about those parameters
please see:
62 IBM 2216 and Network Utility Host Channel Connections
400000004020
RA03
LPAR
1
MAINZ
RA28
LPAR
2
ESCD
LSA
LAN
TR
CC
C9
RA39
LPAR
4
S/390
2216
400022160001
'NET' link
40000A000042
VALENCIA

• Nways MAS Protocol Configuration and Monitoring Reference Vol.1 V2R2,
SC30-3884
• Nways Multiprotocol Access Services Protocol Configuration and Monitoring
Reference Vol. 2 Version 3.2, SC30-3885
Add the Physical Interface
Regarding our test environment we are going to add the physical interfaces via
the T6 add device command:
• LAN adapter (token-ring)
• ESCON adapter
Figure 44 reflects the result of adding the devices to the 2216 (TR/ESCON).
2216 Config>
2216 Config>add dev token
Device Slot #(1-8) [1]? 1
Device Port #(1-2) [1]? 1
Adding Token Ring device in slot 1 port 1 as interface #0
Use "net 0" to configure Token Ring parameters
2216 Config>add dev escon
Device Slot #(1-8) [1]? 3
Adding ESCON Channel device in slot 3 port 1 as interface #1
Use "net 1" to configure ESCON Channel parameters
Figure 44. Adding the Physical Interfaces to the 2216
Via the list device command (see Figure 45 on page 63) from the config
command prompt we can get the logical interface numbers, the device type and
their physical position inside the 2216.
2216 Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 ESCON Channel Slot: 3 Port: 1
Figure 45. List of the Devices inside the 2216
After the add dev command the net parameters have to be set up. We will add
here in more detail only the parameter for the ESCON adapter which is in our
scenario, the net number 1 (see Figure 45). For the configuration of the
token-ring interface we will display only the MAC address setting seen in Figure
46 (take care about the speed and the media of your TR). For all other parameter
configurations refer to Nways Multiprotocol Access Services Software User's
Guide Version 2, Release 2, SC30-3886.
2216 Config>net 0
Token-Ring interface configuration
2216 TKR config>
2216 TKR config>set phy 40:00:22:16:00:01 1
2216 TKR config>
Figure 46. Setting the MAC Address of the Token-Ring Interface
Link Services Architecture 63

1 Set the MAC address which will be used to identify the host when configuring
the virtual LSA channel for direct connection. The link is done via the net
command at the ESCON/PCA Add Virtual> Prompt. See Figure 48 on page 65.
Add/Configure the LSA Virtual Interface
Now that the physical interfaces have been set we can start to configure the
ESCON/PCA (via the net command) and use the add LSA command (see Figure
47) to add an LSA virtual interface and get to the ESCON/PCA Add Virtual>
prompt from which you can enter other interface and subchannel parameters:
2216 Config>net 1
2216 ESCON Config>add lsa
2216 ESCON Add Virtual>
Figure 47. Adding the LSA Virtual Interface
There are five commands available to configure the LSA virtual interface for a
direct connection with the host on an ESCON/PCA adapter:
•acklen
•blktimer
•maxdata
•net
•subchannel
We will focus on only the net and subchannel commands and their values; all
others will remain the default in our case. For more information about the other
parameters see Nways Multiprotocol Access Services Software User's Guide,
SC30-3886.
net interface# This parameter is available only when loopback is disabled. It
is used to indicate the LAN adapter over which this LSA net
will communicate. The LAN adapter must have been
configured previously and can only be token-ring, Ethernet
(including emulated LANs), or FDDI. Regarding our test
environment the interface# is 0 (see Figure 45 on page 63).
The subchannel command places you at the next prompt based on the value of the
command. The command can be one of the following:
add sub add Add a subchannel and display the ESCON Add Subchannel>
prompt or PCA Add Subchannel> prompt from which you can
add device address, LPAR number, link address, and CU
logical address. (Note: LPAR, LINK,CU parameters don’t
apply to PCA).
delete sub delete Deletes a configured LSA subchannel. It lists the
configuration for the configured LSA subchannels and allows
you to delete one of them by specifying the “sub” number from
the list.
list sub list Lists information for the LSA subchannels.
mod sub mod Modifies a configured LSA subchannel. It lists the
configuration of the configured LSA subchannels and allows
you to modify one of them by specifying the “sub” number
from the list. Once you have selected the subchannel, you
64 IBM 2216 and Network Utility Host Channel Connections

can change the device address, LPAR number, link address,
and CU logical address.
Configure the LSA Subchannels
LSA uses a single bidirectional subchannel between the host and the 2216.
VTAM issues a READ command immediately following each WRITE command to
retrieve data from the channel. From the ESCON/PCA Add Virtual> prompt the
subchannel has to be added and configured to reflect the definitions made in the
host. See Figure 48 on page 65 for the subchannel configuration parameters.
Note also the net command in this figure; it has the value 0 which is our token-ring
interface.
2216 ESCON Add Virtual>net 0
2216 ESCON Add Virtual>sub add
2216 ESCON Add LSA Subchannel>device 4 1
2216 ESCON Add LSA Subchannel>lpar 1 2
2216 ESCON Add LSA Subchannel>cu 1 3
2216 ESCON Add LSA Subchannel>link cc 4
2216 ESCON Add LSA Subchannel>ex
216 ESCON Add Virtual>ex
2216 ESCON Config>ex
ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]: y
2216 Config>
Figure 48. Configure an LSA Subchannel
The parameters that have to be configured regarding our test environment
(ESCON adapter) in the subchannel are:
1 device: The unit address transmitted on the channel path to select a 2216
device. This value must be in the range specified in the UNITADD
parameter in the CNTLUNIT macro of the IOCP definitions in the host.
2 lpar: Logical partition number in the host. Specifying this parameter allows
multiple LPARs to share one ESCON fiber. This value is defined in the
IOCP by the RESOURCE macro instruction. If the host is not using
EMIF, the default of 0 must be used for the LPAR number.
3 cu: The control unit address defined in the host for the 2216. This value is
defined in the host Input/Output configuration program (IOCP) by the
CUADD statement on the CNTLUNIT macro instruction. The control
unit address must be unique for each LPAR defined on the same host.
4 link: If one ESCON Director (ESCD) is in the communication path, the link
address is the ESCD port number that is attached to the host. If two
ESCDs are in the path, it is the host-side port number of the ESCD
defined with the dynamic connection. When no ESCD is in the
communication path, this value must be set to X'01'.
The list device command (see Figure 49 on page 66) from the config prompt
reflects the new status of the interfaces for the 2216; the LSA got its own interface
number.
Link Services Architecture 65

2216 Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 ESCON Channel Slot: 3 Port: 1
Ifc 2 LSA - ESCON Channel Base Net: 1
Figure 49. List of the Interfaces inside the 2216
To complete the configuration of our test scenario we have to reload the 2216
with the new configuration and we have to configure our PCs with the data to
match the host definitions. The software we use to connect the PCs to the
SNA-host is the IBM Personal Communication.
After this has been done the 2216/LSA-direct connection to the host is complete
and can be monitored as described in, “Monitoring ESCON LSA Interface
(Direct)” on page 67.
4.4.2.3 Monitoring ESCON Interface
The monitoring commands are available from the GWCON prompt which you get
via the T5 process. You access the talk 5 commands that show the status of
channel resources hierarchically as follows:
• From the * prompt, type talk 5 and press Enter to reach the + prompt.
• From the + prompt, type int and press Enter and note the logical interface
number for the physical ESCON or PCA interface you are interested in. The
physical interface is commonly called the base net and may have a number of
LSA, LCS, or MPC+ virtual interfaces defined on top of it. The base net and all
virtual interfaces each have a different logical interface number (see Figure
50).
2216 *t5
2216 +int
Self-Test Self-Test Ma
Net Net' Interface Slot-Port Passed Failed
0 0 TKR/0 Slot: 1 Port: 1 2 1
1 1 ESCON/0 Slot: 3 Port: 1 1 0
2 1 LSA/0 Slot: 0 Port: 0 1 2
Figure 50. Interface List via GWCON
• From the + prompt, type net base n (where n is the number) and press Enter to
reach the ESCON or PCA console subprocess. The command prompt
changes to ESCON> or PCA> as appropriate (see Figure 51).
2216 +net 1
ESCON Base Console
2216 ESCON>
Figure 51. Change to the ESCON Base Net Prompt
At these prompts, you can use the li net command to see the current state of
every (LSA, LCS, MPC+) virtual interface using this base net. You can also type
li sub to view the currently running subchannel configuration for this base net
(see Figure 52 on page 67).
66 IBM 2216 and Network Utility Host Channel Connections

2216 ESCON>list ?
SUbchannels
NEts
2216 ESCON>list sub
The following subchannels are defined:
1 Local address: 00 Device address: 04 CU Logical Address: 01
Link: CC LPAR: 01
2 Type: LSA
The following lantypes/lannums are using this subchannel:
3 LAN type: Token-Ring/802.5 LAN number: 0 4
2216 ESCON>li net
Net: 2 Type: LSA LAN Type: Token-Ring/802.5 LAN Number: 0
Net state: Up 5
Figure 52. List of Net and Subchannel from ESCON Base Net Prompt
1 Local Address The subchannel address index used internally by the
device.
2 Type Type of virtual interface: LCS, LSA, or MPC+.
3 LAN Type LAN type, either token-ring/802.5, Ethernet/802.3,
Ethernet/V2, Ethernet or FDDI.
4 LAN Number Interface number of the LAN.
5 Net State State of the network: Up, Down, Disabled, Not Present,
HW Mismatch, or Testing. Up indicates that the link is up.
Monitoring ESCON LSA Interface (Direct)
From the base net ESCON> or PCA> prompt or directly from the + prompt, type
net virtual net number and press Enter to see more detail on a particular virtual
interface that uses this base net. The command prompt changes to LSA>, LCS>,
or MPC+>, depending on the type of the virtual interface you select.
Each of these prompts supports a list command to show configuration and
current status information relevant to the virtual interface type (see Figure 53 on
page 67).
2216 +net 2
LSA Console
2216 LSA>list ?
ADapter
SAp
LInk station
Figure 53. List of Subcommands for the LSA Interface
The next figures reflect these list commands one by one regarding our test
environment.
The li adapter command lists virtual adapters for LSA (Figure 54 on page 68).
Link Services Architecture 67

2216 LSA>li adapter
LSA Virtual Adapter
LSA Information for Net 2
--- ----------- --- --- --
LAN Type: Token-Ring/802.5 LAN Number: 0
MAC Address: 400022160001
Downstream network: Token-Ring/802.5 - Net 0
Status: Host connected
#SAPs Open: 1 1 #Link Stations Open: 2 2
Maximum frame size: 2052 (0x804) 3
Host User ID 4 Subchannel 5
------------ ----------
00000000 0
1 host user(s)
Figure 54. List of Virtual Adapter
1 #SAPs Open Number of SAPs opened by VTAM on this LSA
interface
2 #Link Stations Open Number of link stations open for all SAPs on this
LSA interface
3 Maximum Frame Size Maximum frame size supported over this LSA interface
4 Host User ID A unique ID generated by VTAM to identify the host
user on a given subchannel
5 Subchannel The local subchannel being used by this host user.
The sap command lists service access points (SAPS) for LSA (see Figure 55).
2216 LSA>li sap
SAP Provider User Max Link Open Link
Number SAP ID SAP ID Stations Stations
1 2 3 4 5
------ -------- -------- -------- ---------
4 00000000 00000001 10 2
1 SAPs currently open
Figure 55. List SAP for LSA
1 SAP Number Identifies the SAP to LLC
2 Provider SAP ID A unique ID generated by VTAM to identify this SAP
3 User SAP ID A unique ID generated by device to identify this SAP
4 Max Link Stations Maximum number of link stations VTAM can open on this
SAP.
5 Open Link Stations Number of link stations currently open on this SAP
The link command lists link information for LSA (Figure 56)
68 IBM 2216 and Network Utility Host Channel Connections

Figure 56. List Link Information for LSA
4.4.3 LSA Remote DLSw Connection
2216 LSA>li link
Please specify a SAP number (0-236): [4]?
Link Stations on SAP 4
1 2 3 4 5 6
Station Destination Destination Link Frames Frames
ID MAC Address SAP Number Status Sent Received
------- ----------- ----------- ------ ------ --------
00000001 40000A000042 4 Connected 28 28
00000002 400000004020 4 Connected 6 6
2 link station(s) open on SAP 4
1 Station ID A unique ID generated by device to identify this
link station
2 Destination MAC Address MAC address of the remote LLC link station
3 Destination SAP Number SAP value of the remote LLC link station
4 Link Status Current status of the LLC connection
5 Frames Sent Number of packets sent to VTAM for this link
station
6 Frames Received Number of packets received from VTAM for this
link station
4.4.3.1 Network Environment Description
The scenario for this type of connection is made up of the 2216 and a 2210, both
attached to an IP network which in this case is a point-to-point link. The 2216 and
the 2210 are TCP partners.
At the same time, a local DLSw connection is possible between the token-ring
network attached to the 2216 and the LSA loopback network where the host is
located.
Consequently, the 2216 has two TCP partners, the 2210 for the remote
connection and itself for the local connection.
See Figure 57 on page 70 for details on the network setup.
Link Services Architecture 69

XCA Major Node Definitions
ADAPNO=0
SAPADDR=4
MEDIUM=RING
.....
------------------------------
SW Major Node Definitions
VALENCIA ...
MAINZ ...
------------------------------
MVSIOCPDefinitions
UNITADD=04
CUADD=1
Figure 57. LSA DLSw Connection Network Setup
4.4.3.2 2216 Configuration
To configure the 2216 for DLSw, the following steps must be followed:
1. Define the physical interface.
2. Add an LSA virtual interface. Enable loopback on the LSA virtual interface and
configure it.
3. Configure the LSA subchannel.
4. Configure DLS.
Add the Physical Interface
The physical interface will be the ESCON channel adapter. It has to be added
using the add device command, in the same way as all other interfaces.
With the list devices command, we can see the network numbers that have been
assigned to the added interfaces.
70 IBM 2216 and Network Utility Host Channel Connections
RA03
LPAR 1
LAN
16.0.0.0
RA28
LPAR 2
ESCD
LSA
CC
C9
WAN
RA39
LPAR 4
2216
S/390
LSA MAC@
40002216000A
PPP
192.194.200.0
2210
10.0.0.0
S/390
2216
40002216000A

2216 *t 6
2216 Config>add dev token
Device Slot #(1-8) [1]? 1
Device Port #(1-2) [1]? 1
Adding Token Ring device in slot 1 port 1 as interface #0
Use "net 0" to configure Token Ring parameters
2216 Config>add dev eia
Device Slot #(1-8) [1]? 8
Device Port #(0-7) [1]? 0
Defaulting Data-link protocol to PPP
Adding EIA-232E/V.24 PPP device in slot 8 port 0 as interface #1
Use "set data-link" command to change the data-link protocol
Use "net 1" to configure EIA-232E/V.24 PPP parameters
2216 Config>add dev escon
Device Slot #(1-8) [1]? 3
Adding ESCON Channel device in slot 3 port 1 as interface #2
Use "net 2" to configure ESCON Channel parameters
2216 Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 EIA-232E/V.24 PPP Slot: 8 Port: 0
Ifc 2 ESCON Channel Slot: 3 Port: 1
Figure 58. LSA DLSw: Adding the Physical Adapters to the 2216
Configure the LSA Virtual Interface
To add the LSA interface, the add lsa command has to be used, which takes us to
the LSA config prompt. From there we will be able to enable loopback. When
loopback is enabled the appearance of a LAN is created in the 2216 between the
host (LSA interface) and the 2216. See 4.2, “LLC Loopback” on page 54 for a
detailed explanation.
Once loopback has been enabled we have to specify the LAN type, token-ring,
Ethernet or FDDI this simulated LAN is. This LAN type needs to match the LAN
type specified on the XCA major node definitions on VTAM because it determines
the frame type that the host expects to send and receive.
Also a MAC address has to be configured on this LSA loopback network. This
MAC address identifies the LSA/VTAM side of the loopback connection.
2216 Config>net 2
2216 ESCON Config>add lsa
2216 ESCON Add Virtual>?
ENable loopback
MAXdata
BLKtimer
ACKlen
NET link
SUBchannels
Exit
2216 ESCON Add Virtual>enable loopback
Enabling loopback through network 3.
Please set the MAC address using the "MAC" command
2216 ESCON Add Virtual>mac 40:00:22:16:00:0A
2216 ESCON Add Virtual>lantype token
Figure 59. LSA DLSw: LSA Configuration
Link Services Architecture 71

Configure the LSA Subchannels
LSA uses a single bidirectional subchannel between the host and the 2216.
VTAM issues a READ command immediately following each WRITE command to
retrieve data from the channel.
The parameters that have to be configured in the subchannel are:
device: The unit address transmitted on the channel path to select a 2216
device. This value must be in the range specified in the UNITADD
parameter in the CNTLUNIT macro of the IOCP definitions in the
host.
lpar: Logical partition number in the host. Specifying this parameter allows
multiple LPARs to share one ESCON fiber. This value is defined in the
IOCP by the RESOURCE macro instruction. If the host is not using
EMIF, the default of 0 must be used for the LPAR number.
link: If one ESCON Director (ESCD) is in the communication path, the link
address is the ESCD port number that is attached to the host. If two
ESCDs are in the path, it is the host-side port number of the ESCD
defined with the dynamic connection. When no ESCD is in the
communication path, this value must be set to X'01'.
cu: The control unit address defined in the host for the 2216. This value is
defined in the host Input/Output configuration program (IOCP) by the
CUADD statement on the CNTLUNIT macro instruction. The control
unit address must be unique for each LPAR defined on the same host.
By issuing the sub add command, we will get the subchannel config prompt, which
is where we configure the subchannel.
2216 ESCON Add Virtual>sub add
2216 ESCON Add LSA Subchannel>device 04
2216 ESCON Add LSA Subchannel>link cc
2216 ESCON Add LSA Subchannel>lpar 01
2216 ESCON Add LSA Subchannel>cu 01
2216 ESCON Add LSA Subchannel>ex
2216 ESCON Add Virtual>sub list
Sub 0 Device address : 4 LPAR number : 1
Link address : CC CU Logical Address : 1
2216 ESCON Add Virtual>exit
2216 ESCON Config>ex
ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]:
2216 Config>
Figure 60. LSA DLSw: LSA Subchannel Configuration
Configure DLSw
When configuring DLSw support on the router the following steps are required:
• Configure IP. An internal IP address will be assigned to the 2216 to be used by
DLSw. Routing capabilities are needed also for allowing the 2216 to reach its
TCP partners.
• Configure Bridging. Bridging has to be configured on the LAN interfaces
(endpoints of the DLSw circuit). One endpoint for the DLSw circuit is the 2216
endpoint of the loopback connection, but we do not need to enable bridging
there.
72 IBM 2216 and Network Utility Host Channel Connections

• Configure DLSw. DLSw is enabled by specifying the IP address of the partner,
enabling dynamic neighbors or joining the router to a multicast group. In this
example the IP address of the partner is the method used for the router to
know its partners. SAPs are opened on the LAN interfaces to let the router
know which protocols are going to be encapsulated on DLSw. SAPs will have
to be opened on the LSA loopback interface since it is the 2216 LAN end of
the DLSw circuit.
The first step is to configure IP and the routing protocol. As seen in Figure 61 on
page 74, OSPF is the routing protocol used in this example. Both 2210 and 2216
are attached to the backbone area, which is the only area in this scenario. With
the set interface command, we have specified which interfaces on the 2216 have
to participate in the OSPF protocol.
Link Services Architecture 73

2216 Config>pip
Internet protocol user configuration
2216 IP config>add addr 0 16.0.0.1 255.255.255.0
2216 IP config>add addr 1 192.194.200.1 255.255.255.0
2216 IP config>set internal 9.9.9.1
2216 IP config>list addr
IP addresses for each interface:
intf 0 16.0.0.1 255.255.255.0 Local wire broadcast, fill 1
intf 1 192.194.200.1 255.255.255.0 Local wire broadcast, fill 1
intf 2 IP disabled on this interface
intf 3 IP disabled on this interface
Internal IP address: 9.9.9.1
2216 IP config>ex
2216 Config>p ospf
Open SPF-Based Routing Protocol configuration console
2216 OSPF Config>ena ospf
Estimated # external routes [100]?
Estimated # OSPF routers [50]?
Maximum Size LSA [2048]?
2216 OSPF Config>set inter 16.0.0.1
Attaches to area [0.0.0.0]?
Retransmission Interval (in seconds) [5]?
Transmission Delay (in seconds) [1]?
Router Priority [1]?
Hello Interval (in seconds) [10]?
Dead Router Interval (in seconds) [40]?
TOS 0 cost [1]?
Demand Circuit (Yes or No)? [No]:
Authentication Type (0 - None, 1 - Simple) [0]?
2216 OSPF Config>set inter 192.194.200.1
Attaches to area [0.0.0.0]?
Retransmission Interval (in seconds) [5]?
Transmission Delay (in seconds) [1]?
Router Priority [1]?
Hello Interval (in seconds) [10]?
Dead Router Interval (in seconds) [40]?
TOS 0 cost [1]?
Demand Circuit (Yes or No)? [No]:
Authentication Type (0 - None, 1 - Simple) [0]?
2216 OSPF Config>list all
--Global configuration--
OSPF Protocol: Enabled
# AS ext. routes: 100
Estimated # routers: 50
Maximum LSA size: : 2048
External comparison: Type 2
RFC 1583 compatibility: Enabled
AS boundary capability: Disabled
Multicast forwarding: Disabled
Demand Circuits: Enabled
Least Cost Area Ranges: Disabled
Maximum Random LSA Age: 0
--Area configuration--
Area ID Stub? Default-cost Import-summaries?
0.0.0.0(Implicit) No N/A N/A
--Interface configuration--
IP address Area Auth Cost Rtrns Delay Pri Hello Dead
16.0.0.1 0.0.0.0 0 1 5 1 1 10 40
192.194.200.1 0.0.0.0 0 1 5 1 1 10 40
2216 OSPF Config>ex
2216 Config>
Figure 61. LSA DLSw: IP Configuration
74 IBM 2216 and Network Utility Host Channel Connections

Now, bridging has to be configured as mentioned above on the LAN endpoints of
the DLSw circuit. The 2216 endpoint of the loopback connection does not need
us to enable bridging. So, for the remote DLSw connection we do not need to add
any interface to the bridging network, therefore, we do not need to go into this
step. For the local DLSw connection we will need to enable bridging on the
token-ring interface due to the local DLS configured between this token-ring
interface and the LSA loopback.
Link Services Architecture 75

2216 Config>p asrt
Adaptive Source Routing Transparent Bridge user configuration
2216 ASRT config>ena bridge
2216 ASRT config>ena dls
2216 ASRT config>li port 1
Port ID (dec) : 128:01, (hex): 80-01
Port State : Enabled
STP Participation: Enabled
Port Supports : Transparent Bridging Only
Assoc Interface : 0
Path Cost : 0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2216 ASRT config>disable trans 1 2a
2216 ASRT config>ena source 1 2b
Segment Number for the port in hex(1 - FFF) [001]? 100
Bridge number in hex (0 - 9, A - F) [0]? 1
2216 ASRT config>li port
Port ID (dec) : 128:01, (hex): 80-01
Port State : Enabled
STP Participation: Enabled
Port Supports : Source Route Bridging Only
SRB: Segment Number: 0x100 MTU: 4399 STE: Enabled
Assoc Interface : 0
Path Cost : 0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2216 ASRT config>li bri
Source Routing Transparent Bridge Configuration
===============================================
Bridge: Enabled Bridge Behavior: SRB
+----------------------------+
---------------| SOURCE ROUTING INFORMATION |-------------------------------
+----------------------------+
Bridge Number: 01 Segments: 1
Max ARE Hop Cnt: 14 Max STE Hop cnt: 14
1:N SRB: Not Active Internal Segment: 0x000
LF-bit interpret: Extended
+-------------------+
----------------| SR-TB INFORMATION |----------------------------------------
+-------------------+
SR-TB Conversion: Disabled
TB-Virtual Segment: 0x000 MTU of TB-Domain: 0
+------------------------------------+
----------------| SPANNING TREE PROTOCOL INFORMATION |-----------------------
+------------------------------------+
Bridge Address: Default Bridge Priority: 32768/0x8000
SRB Bridge Address: Default SRB Bridge Priority: 32768/0x8000
STP Participation: IBM-SRB proprietary
+-------------------------+
----------------| TRANSLATION INFORMATION |----------------------------------
+-------------------------+
FAGA Conversion: Enabled UB-Encapsulation: Disabled
DLS for the bridge: Enabled
+------------------+
----------------| PORT INFORMATION |-----------------------------------------
+------------------+
Number of ports added: 1
Port: 1 Interface: 0 Behavior: SRB Only STP: Enabled
2216 ASRT config>ex
2216 config>
Figure 62. LSA DLSw: ASRT Configuration
76 IBM 2216 and Network Utility Host Channel Connections

1 By default when bridging is enabled on the 2216 with the enable bridge
command, all the LAN interfaces on the router are enabled for bridging using
transparent bridging. That’s why we have not needed to add a port for the
token-ring interface. We only have changed from transparent to source route
bridging on this interface, 2a and 2b.
Once IP and bridging are configured we can configure DLSw.
Link Services Architecture 77

.
2216 Config>pdls
DLSw protocol user configuration
2216 DLSw config>ena dls
Data Link Switching is now enabled
2216 DLSw config>add tcp 10.0.0.1 1a
Connectivity Setup Type (a/p) [p]?
Transmit Buffer Size (Decimal) [5120]?
Receive Buffer Size (Decimal) [5120]?
Maximum Segment Size (Decimal) [1024]?
TCP Keepalive (E/D) [D]?
NetBIOS SessionAlive Spoofing (E/D) [D]?
Neighbor Priority (H/M/L) [M]?
TCP Neighbor has been added
2216 DLSw config>add tcp 9.9.9.1 1b
Adding local transport connection
Neighbor Priority (H/M/L) [M]?
Local transport TCP Neighbor has been added
2216 DLSw config>open 0 2a
Enter SAP in hex (range 0-FE), 'SNA', 'NB' or 'LNM' [4]? sna
SAP(s) 0 4 8 C opened on interface 0
2216 DLSw config>open 3 2b
Enter SAP in hex (range 0-FE), 'SNA', 'NB' or 'LNM' [4]? sna
SAP(s) 0 4 8 C opened on interface 3
2216 DLSw config>set srb d01
DLSw segment number has been set.
2216 DLSw config>list dls global
DLSw is ENABLED
LLC2 send Disconnect is ENABLED
Dynamic Neighbors is ENABLED
IPv4 DLSw Precedence is DISABLED
SRB Segment number D01
MAC IP mapping cache size 128
Max DLSw sessions 1000
DLSw global memory allotment 141312
LLC per-session memory allotment 8192
SDLC per-session memory allotment 4096
QLLC per-session memory allotment 4096
NetBIOS UI-frame memory allotment 40960
Dynamic Neighbor Transmit Buffer Size 5120
Dynamic Neighbor Receive Buffer Size 5120
Dynamic Neighbor Maximum Segment Size 1024
Dynamic Neighbor Keep Alive DISABLED
Dynamic Neighbor SessionAlive Spoofing DISABLED
Dynamic Neighbor Priority MEDIUM
QLLC base source MAC address 40514C430000
QLLC maximum dynamic addresses 64
Type of local MAC list NON-EXCLUSIVE
Use of local MAC list is ENABLED
Use of remote MAC list is ENABLED
The forwarding of explorers is ENABLED for all DLSw partners
2216 DLSw config>lis tcp neighb
Xmit Rcv Max Keep- SesAlive
Neighbor CST Bufsize Bufsize Segsize Alive Spoofing Priority
--------------- --- ------- ------- ------- -------- -------- --------
10.0.0.1 p 5120 5120 1024 DISABLED DISABLED MEDIUM
9.9.9.1 (LOCAL-CONVERSION CONNECTION) MEDIUM
2216 DLSw config>ex
Figure 63. LSA DLSw: DLSw Configuration
78 IBM 2216 and Network Utility Host Channel Connections

1 These are the IP addresses of the TCP partners. 1a is the internal IP address of
the 2210 (the remote DLSw partner) and 1b is the internal IP address of the 2216
(its own IP address for the local DLSw).
2 SAPs are opened on the LAN interfaces. 2a on the token-ring interface (local
DLSw) and 2b on the LSA loopback interface (for the local and remote DLSw).
Once the 2216 is configured, the configuration has to be saved on the hard drive
by using the write command, and the box must be reloaded for the configuration
to become active. The config we have just made is available on NVRAM; with the
reload it will be loaded from the NVRAM to the DRAM.
2216 Config>write
Config Save: Using bank B and config number 2
2216 Config>
2216 *reload y
Figure 64. LSA DLSw: Activating Configuration
4.4.3.3 2210 Configuration
The 2210 has to be configured as a DLSw router. As in the 2216, IP, Bridging and
DLSw protocols have to be configured.
The 2210 used in this scenario is a 2210-24T, so it has two token-ring interfaces,
four WAN interfaces and one slot for an adapter, as we can see in the output of
the list devices command from the config prompt in Figure 65 on page 80. In the
2210 we do not need to add the physical devices because they are fixed in the
2210 chassis.
Link Services Architecture 79

2210 *t6
2210 Config>li dev
Ifc 0 Token Ring CSR 6000000, vector 95
Ifc 1 WAN PPP CSR 81600, CSR2 80C00, vector 94
Ifc 2 WAN PPP CSR 81620, CSR2 80D00, vector 93
Ifc 3 WAN PPP CSR 81640, CSR2 80E00, vector 92
Ifc 4 WAN PPP CSR 81660, CSR2 80F00, vector 91
Ifc 5 Token Ring CSR 6000100, vector 90
2210 Config>net 0
Token-Ring interface configuration
2210 TKR config>speed 16
2210 TKR config>set phy 40:00:22:10:00:01
2210 TKR config>list
Token-Ring configuration:
acket size (INFO field): 2052
Speed: 16 Mb/sec
Media: Shielded
IF Aging Timer: 120
Source Routing: Enabled
MAC Address: 400022100001
IPX interface configuration record missing
210 TKR config>ex
2210 Config>net 1
Point-to-Point user configuration
2210 PPP 1 Config>set hdlc clock internal 19200
Must also set the line speed to a valid value
2210 PPP 1 Config>set hdlc cable rs-232 dce
2210 PPP 1 Config>li hdlc
Encoding: NRZ
Idle State: Flag
Clocking: Internal
Cable type: RS-232 DCE
Speed (bps): 19200
Transmit Delay Counter: 0
Lower DTR: Disabled
2210 PPP 1 Config>ex
2210 Config>
Figure 65. LSA DLS: 2210 Interface Configuration
Once the interfaces are configured, the IP protocol is configured:
80 IBM 2216 and Network Utility Host Channel Connections

2210 Config>pip
Internet protocol user configuration
2210 IP config>add add 0 10.0.0.1 255.255.255.0
2210 IP config>add add 1 192.194.200.2 255.255.255.0
2210 IP config>set int 10.0.0.1
2210 IP config>ex
2210 Config>p ospf
Open SPF-Based Routing Protocol configuration console
2210 OSPF Config>ena ospf
Estimated # external routes [100]?
Estimated # OSPF routers [50]?
Maximum Size LSA [2048]?
2210 OSPF Config>set int 10.0.0.1
Attaches to area [0.0.0.0]?
Retransmission Interval (in seconds) [5]?
Transmission Delay (in seconds) [1]?
Router Priority [1]?
Hello Interval (in seconds) [10]?
Dead Router Interval (in seconds) [40]?
Type Of Service 0 cost [1]?
Demand Circuit (Yes or No)? [No]:
Authentication Key []?
Retype Auth. Key []?
2210 OSPF Config>set int 192.194.200.2
Attaches to area [0.0.0.0]?
Retransmission Interval (in seconds) [5]?
Transmission Delay (in seconds) [1]?
Router Priority [1]?
Hello Interval (in seconds) [10]?
Dead Router Interval (in seconds) [40]?
Type Of Service 0 cost [1]?
Demand Circuit (Yes or No)? [No]:
Authentication Key []?
Retype Auth. Key []?
2210 OSPF Config>exit
Figure 66. LSA DLSw: 2210 IP Configuration
Next, bridging has to be configured:
Link Services Architecture 81

2210 Config>p asrt
Adaptive Source Routing Transparent Bridge user configuration
2210 ASRT config>en bridge
2210 ASRT config>ena dls
2210 ASRT config>list port 1
Port ID (dec) : 128:01, (hex): 80-01
Port State : Enabled
STP Participation: Enabled
Port Supports : Transparent Bridging Only
Assoc Interface : 0
Path Cost : 0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Port ID (dec) : 128:02, (hex): 80-02
Port State : Enabled
STP Participation: Enabled
Port Supports : Transparent Bridging Only
Assoc Interface : 5
Path Cost : 0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2210 ASRT config>dis trans 1
2210 ASRT config>ena source 1
Segment Number for the port in hex(1 - FFF) [001]? 200
Bridge number in hex (0 - 9, A - F) [0]? 2
2210 ASRT config>ex
2210 config>
Figure 67. LSA DLSw: 2210 ARST Configuration
1 By default when we enable bridging, all the LAN interfaces in the 2210 are
added as bridging ports to the 2210 configuration. We use only the first token-ring
interface and not the second one, so we have to configure correctly the port
number one only.
Finally we configure the DLSw protocol:
2210 Config>pdls
DLSw protocol user configuration
2210 DLSw config>ena dls
2210 DLSw config>add tcp 9.9.9.1 1
Connectivity Setup Type (a/p) [p]?
Transmit Buffer Size (Decimal) [5120]?
Receive Buffer Size (Decimal) [5120]?
Maximum Segment Size (Decimal) [1024]?
Enable/Disable Keepalive (E/D) [D]?
Enable/Disable NetBIOS SessionAlive Spoofing (E/D) [D]?
Neighbor Priority (H/M/L) [M]?
2210 DLSw config>set srb d01
2210 DLSw config>open 0
Enter SAP in hex (range 0-FE), 'SNA', 'NB' or 'LNM' [4]? sna
SAPs 0 4 8 C opened on interface 0
2210 DLSw config>ex
2210 config>
Figure 68. LSA DLSw: 2210 DLSw Configuration
1 This is the internal IP address of the 2216, which is the remote TCP partner.
This new configuration is available in the NVRAM; we have to make it active but
load it into DRAM. For this we use the RESTART command. Because this command
does not exist in the 2216, we have to write the new configuration in the 2216 and
then reload the box.
82 IBM 2216 and Network Utility Host Channel Connections

2210 *restart
Are you sure you want to restart the gateway? (Yes or [No]): y
Figure 69. LSA DLSw: 2210 Activating the Configuration
4.4.3.4 2216 Monitoring
When monitoring the DLS support via LSA on the 2216, we have to check that:
• The ESCON and LSA interfaces are UP. If they are not, check that the
parameters that must match on the host and 2216 definitions effectively
match.
• The status of the LSA virtual adapter is host-connected. This means that the
host has allocated the subchannel, has opened the SAP and is waiting for
user connections.
• If there are problems with DLSw:
• Check the IP connectivity. Make sure the router can reach the TCP partner.
• Check the state of the bridging ports. They must be UP.
• Check the DLSw configuration and make sure that DLSw is enabled under
bridging and the SAPs are opened on the right interfaces.
2216 *t5
2216 +conf
ultiprotocol Access Services
2216-MAS Feature 2821 V3.2 Mod 0 PTF 0 RPQ 0 MAS.EF6 cc4_12a
Num Name Protocol
0 IP DOD-IP
3 ARP Address Resolution
11 SNMP Simple Network Management Protocol
12 OSPF Open SPF-Based Routing Protocol
23 ASRT Adaptive Source Routing Transparent Enhanced Bridge
26 DLS Data Link Switching
29 NHRP Next Hop Resolution Protocol
Num Name Feature
2 MCF MAC Filtering
7 CMPRS Data Compression Subsystem
9 DIALs Dial-in Access to LANs
10 AUTH Authentication
11 IPSec IPSecurity
Total Networks:
Net Interface MAC/Data-Link Hardware State
0 TKR/0 Token-Ring/802.5 Token-Ring Up
1 PPP/0 Point to Point EIA-232E/V.24 Up
2 ESCON/0 ESCON ESCON Channel Up
3 LSA/0 LSA ESCON Channel Up
Figure 70. LSA DLSw: Interface State Monitoring
Link Services Architecture 83

2216 +net 2
ESCON Base Console
2216 ESCON>list net 1
Net: 3 Type: LSA LAN Type: Token-Ring/802.5 LAN Number: 0
Net state: Up
2216 ESCON>list sub 2
The following subchannels are defined:
Local address: 00 Device address: 04 CU Logical Address: 01
Link: CC LPAR: 01
Type: LSA
The following lantypes/lannums are using this subchannel:
LAN type: Token-Ring/802.5 LAN number: 0
2216 ESCON>exit
2216 +net 3
LSA Console
2216 LSA>list adapter 3
LSA Virtual Adapter
LSA Information for Net 3
--- ----------- --- --- --
LAN Type: Token-Ring/802.5 LAN Number: 0
MAC Address: 40002216000A
Downstream network: Loopback - Net 3
Status: Host connected
#SAPs Open: 1 #Link Stations Open: 2
Maximum frame size: 2052 (0x804)
Host User ID Subchannel
------------ ----------
00000000 0
1 host user(s)
2216 LSA>li link 4
Please specify a SAP number (0-236): [4]?
Link Stations on SAP 4
Station Destination Destination Link Frames Frames
ID MAC Address SAP Number Status Sent Received
------- ----------- ----------- ------ ------ --------
00000001 400000004020 4 Connected 6 6
00000002 40000A000042 4 Connected 7 7
2 link station(s) open on SAP 4
2216 LSA>list sap 5
SAP Provider User Max Link Open Link
Number SAP ID SAP ID Stations Stations
------ -------- -------- -------- ---------
4 00000000 00000001 10 2
1 SAPs currently open
Figure 71. LSA DLSw: LSA Interface Monitoring
1 Lists all the network interfaces defined on this ESCON adapter. This command
also provides the status of each network interface. The status must be UP, which
means that the link is active.
2 This command lists all of the subchannels configured on this ESCON adapter.
For each subchannel, the Type field shows the virtual network handler that owns
this subchannel. Also, a list of all the network interfaces, identified by LAN type
and LAN number, that share each subchannel is also available with this
command.
84 IBM 2216 and Network Utility Host Channel Connections

3 This command lists a virtual adapter for the LSA. It provides some information,
for example, the LAN type, LAN number, the MAC address of the LSA interface,
which is the MAC address identifying the host end of the connection, etc.
This command also shows some details about the VTAM connection with the
2216, like the SAPs being used, the number of link stations currently opened on
the SAPs on this interface, etc.
4 This command lists link information for the LSA, for example, the identifier of the
link station, the MAC address of the LLC link station, the status of the link, etc.
5 Lists information on the SAPs opened by VTAM.
To monitor the DLSw protocol, IP and bridging may be monitored also:
Link Services Architecture 85

2216 +pip
2216 IP>dump
Type Dest net Mask Cost Age Next hop(s)
Sbnt 9.0.0.0 FF000000 1 740 None
SPF 9.9.9.1 FFFFFFFF 0 761 SINK/0
Sbnt 10.0.0.0 FF000000 1 740 None
SPF 10.0.0.0 FFFFFF00 2 757 192.194.200.2
SPF 10.0.0.1 FFFFFFFF 1 757 192.194.200.2
Sbnt 16.0.0.0 FF000000 1 590 None
SPF* 16.0.0.0 FFFFFF00 1 605 TKR/0
Dir* 192.194.200.0 FFFFFF00 1 740 PPP/0
SPF 192.194.200.1 FFFFFFFF 2 757 PPP/0
SPF 192.194.200.2 FFFFFFFF 1 757 192.194.200.2
Routing table size: 768 nets (52224 bytes), 10 nets known
0 nets hidden, 0 nets deleted, 1 nets inactive
0 routes used internally, 757 routes free
2216 IP>exit
2216 +p asrt
2216 ASRT>li bridge
SRB Bridge ID (prio/add): 32768/10-00-5A-7F-80-11
Bridge state: Enabled
UB-Encapsulation: Disabled
Bridge type: SRB
Number of ports: 1
STP Participation: IBM-SRB proprietary
**Bridge is enabled for Data Link Switching**
Maximum
Port Interface State MAC Address Modes MSDU Segment Flags
1 TKR /0 Up 02-00-44-68-00-80 SR 2096 100 RD,LD
Flags:RE = IBMRT PC behavior Enabled, RD = IBMRT PC behavior Disabled
LE = LNM Enabled, LD = LNM Disabled, LF = LNM Failed
SR bridge number: 1
SR virtual segment: 000 (1:N SRB Not Active)
Adaptive segment: 000
2216 +p dls
2216 DLSw>list tcp ses all
Group/Mcast@ IP Address Conn State CST Version ActSes SesCreates
------------ ---------- ------------ --- ------- ------ ----------
1 9.9.9.1 ESTABLISHED a AIW V2R0 2 138
2 10.0.0.1 ESTABLISHED p AIW V2R0 1 11
2216 DLSw>list dls ses all 1
Source Destination State Flags Dest IP Addr Id
--------------- --------------- --------- ------ -------------- ----
1 40000A000042 04 40002216000A 04 CONNECTED LOCAL 146
2 40002216000A 04 400000004020 04 CONNECTED 10.0.0.1 148
3 40002216000A 04 40000A000042 04 CONNECTED LOCAL 147
Figure 72. LSA DLSw: DLSw Monitoring
1 In local DLSw, two DLSw sessions are generated internally per pair of MAC
addresses.
4.4.3.5 2210 Monitoring
If a problem is encountered in the 2210, it has to be monitored as in the 2216, by
checking the IP, bridging and DLSw configuration.
86 IBM 2216 and Network Utility Host Channel Connections

2210 DLSw>li tcp ses all
Group/Mcast@ IP Address Conn State CST Version ActSes SesCreates
------------ ---------- -------------- --- -------- ------ ----------
1 9.9.9.1 ESTABLISHED p AIW V2R0 1 1
2210 DLSw>li dls ses all
Source Destination State Flags Dest IP Addr Id
-------------- -------------- --------- ------- -------------- ----
1 400000004020 04 40002216000A 04 CONNECTED 9.9.9.1 0
Figure 73. LSA DLSw: DLSw Monitoring
4.4.4 LSA Local DLSw Connection (FR BAN)
In this example frame relay BAN (FR BAN) has been used.
The BAN feature is an enhancement of the frame relay, DLSw, and Adaptive
Source Route Bridging (ASRT) capabilities of the 2210 and 2216 software. This
feature enables IBM Type 2.0 and 2.1 end stations connected to a 2210/6 to make
a direct connection via frame relay to an SNA node supporting the RFC 1490
bridged 802.5 (token-ring) frame format.
When using BAN, end stations function as if they are connected directly to an
SNA node via a token-ring, Ethernet, FDDI, or SDLC line. Though their data
actually passes through a 2210/6 and over a frame-relay network, this is
transparent to the end stations.
4.4.4.1 Network Environment Description
In this example the conversion is done between FR BAN and LLC2. The 2216 is
configured for doing the conversion with local DLSw. The 2216 is attached to the
VTAM host through the ESCON channel adapter and to a 2210 through a framerelay
network.
The 2210 is configured as a BAN router allowing end stations connected to its
local LAN to access the mainframe which is accessible through the 2216. The
2216 is defined as the BAN catcher.
Link Services Architecture 87

XCA Major Node Definitions
ADAPNO=0
SAPADDR=4
MEDIUM=RING
.....
------------------------------
SW Major Node Definitions
VALENCIA ...
MAINZ ...
------------------------------
MVS IOCP Definitions
UNITADD=04
CUADD=1
Figure 74. LSA Local DLSw Connection Network Setup
4.4.4.2 2216 Configuration
For configuring the 2216 as a BAN catcher, the following steps must be followed:
1. Add the physical interfaces.
2. Add the LSA virtual interface, enable loopback and configure it.
3. Configure the subchannels.
4. Configure local DLSw.
Add and Configure the ESCON Interface
Add the physical interfaces by using the add device command and then access the
particular network config prompt with the net x command, where x is the
network number assigned by the 2216 to each interface.
Once we get the ESCON config prompt we enable LSA loopback to create the
LAN between the LSA interface (host end of the loopback connection) and the
DLSw code in the 2216.
Finally we configure the subchannels.
88 IBM 2216 and Network Utility Host Channel Connections
RA03
LPAR 1
RA28
LPAR 2
ESCD
LSA
WAN
2210
CC
C9
RA39
LPAR 4
2216
Frame Relay
S/390
LSA MAC@
40002216000A
BAN DLCI MAC@
400022100002
S/390
2216
40002216000A

2216 Config>add dev escon
Device Slot #(1-8) [1]? 3
Adding ESCON Channel device in slot 3 port 1 as interface #0
Use "net 0" to configure ESCON Channel parameters
22216 Config>net 0
2216 ESCON Config>add lsa
2216 ESCON Add Virtual>ena loopback
Enabling loopback through network 1.
Please set the MAC address using the "MAC" command
2216 ESCON Add Virtual>lan token
2216 ESCON Add Virtual>mac 40:00:22:16:00:0A
2216 ESCON Add Virtual>sub add
2216 ESCON Add LSA Subchannel>lpar 1
2216 ESCON Add LSA Subchannel>cu 1
2216 ESCON Add LSA Subchannel>link cc
2216 ESCON Add LSA Subchannel>device 04
2216 ESCON Add LSA Subchannel>ex
2216 ESCON Add Virtual>ex
2216 ESCON Config>ex
ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]:
2216 Config>
Figure 75. LSA Local DLSw: 2216 ESCON Interface Configuration
Add and Configure the Frame Relay Interface
The frame relay connection we have used in this scenario is a frame relay
back-to-back connection. As there is no real FR switch in between both routers,
LMI has to be disabled and the dlci number must match at both ends, in the 2216
and in the 2210.
Link Services Architecture 89

2216 Config>add dev eia
Device Slot #(1-8) [1]? 8
Device Port #(0-7) [1]? 0
Defaulting Data-link protocol to PPP
Adding EIA-232E/V.24 PPP device in slot 8 port 0 as interface #2
Use "set data-link" command to change the data-link protocol
Use "net 2" to configure EIA-232E/V.24 PPP parameters
2216 Config>set data frame 2
2216 Config>net 2
Frame Relay user configuration
2216 FR 2 Config>dis lmi
2216 FR 2 Config>add perm
Circuit number [16]?
Committed Information Rate (CIR) in bps [64000]?
Committed Burst Size (Bc) in bits [64000]?
Excess Burst Size (Be) in bits [0]?
Assign circuit name []? frban
Is circuit required for interface operation [N]?
2216 FR 2 Config>set line 64000
2216 FR 2 Config>li all
Frame Relay HDLC Configuration
Interface maximum frame size (bytes) = 2048
Encoding = NRZ
Idle state = Flag
Clocking = External
Cable type = RS-232 DTE
Line speed (bps) = 64000
Transmit delay = 0
Lower DTR = Disabled
Frame Relay Configuration
LMI enabled = No LMI DLCI = 0
LMI type = ANSI LMI Orphans OK = Yes
CLLM enabled = No Timer Ty seconds = 11
SVCs enabled = No
Protocol broadcast = Yes Congestion monitoring = Yes
Emulate multicast = Yes CIR monitoring = No
Notify FECN source = No Throttle transmit on FECN = No
Data compression = No
Figure 76. LSA Local DLSw: 2216 FR Interface Configuration
90 IBM 2216 and Network Utility Host Channel Connections
Number VCs P1 allowed = 64 Interface down if no PVCs = No
Timer T1 seconds = 10 Counter N1 increments = 6
LMI N2 error threshold = 3 LMI N3 error threshold window = 4
MIR % of CIR = 25 IR % Increment = 12
IR % Decrement = 25 DECnet length field = No
Default CIR =64000 Default Burst Size =64000
Default Excess Burst = 0
Maximum circuits allowable = 64
Total circuits configured = 1
Total PVCs configured = 1
Circuit Circuit Circuit CIR Burst Excess
Name Number Type in bps Size Burst
--------------------- ------- ----------- ------- ------- ------frban
16 Permanent 64000 64000 0
= circuit is required
# = circuit is required and belongs to a required PVC group
@ = circuit is data compression capable
No required PVC groups have been defined
No SVCs configured
No address translations configured

DLSw Configuration
When configuring DLSw, IP and bridging have to be configured also because
DLSw uses these two protocols.
The only thing that needs to be configured in this scenario for IP is the internal IP
address that DLSw will use as TCP partner. We do not need to configure any
routing protocol or IP on any interface because there is no IP traffic in this
scenario. The 2216 is handling only SNA in this example.
2216 Config>pip
Internet protocol user configuration
2216 IP config>set int 9.9.9.1
2216 IP config>ex
2216 config>
Figure 77. LSA Local LSA: 2216 IP Configuration
Bridging has to be configured in the endpoints of the local DLSw connection. As
we do not need to enable bridging on the 2216 endpoint of the loopback
connection we will do it only on the frame relay permanent virtual channel (PVC).
2216 Config>p asrt
Adaptive Source Routing Transparent Bridge user configuration
2216 ASRT config>ena bridge
2216 ASRT config>ena dls
2216 ASRT config>add port
Interface Number [0]? 2
Port Number [1]?
Use FR PVC? [Yes]:
Frame Relay Circuit number [16]?
2216 ASRT config>dis trans 1 1a
2216 ASRT config>ena sour 1 1b
Segment Number for the port in hex(1 - FFF) [001]? 400
Bridge number in hex (0 - 9, A - F) [0]? 1
2216 ASRT config>set bridge srb 2
Bridge Address (in 12-digit hex) []? 4000221600BD
2216 ASRT config>ex
2216 config>
Figure 78. LSA Local DLSw: 2216 Bridging Configuration
1 As fr BAN uses the RFC1490 bridged 802.5 frame format, the frame relay PVC
should be configured as a source route bridge.
2 This is the low-order six-octet bridge address found in the bridge identifier. By
default, the bridge-addr-value is set to the MAC address of the lowest-numbered
port at initialization time. In cases where a serial line interface is the lowestnumbered
port, it is mandatory to use this command so that the bridge will have a
unique address when restarted. This process is necessary because serial lines
do not have their own MAC address.
Each bridge in the network must have a unique address for the spanning tree
protocol to operate correctly.
Finally, DLSw can be configured.
Link Services Architecture 91

2216 Config>pdls
DLSw protocol user configuration
2216 DLSw config>ena dls
Data Link Switching is now enabled
2216 DLSw config>add tcp 1
Enter the DLSw neighbor IP Address [0.0.0.0]? 9.9.9.1
Adding local transport connection
Neighbor Priority (H/M/L) [M]?
Local transport TCP Neighbor has been added
2216 DLSw config>open 1 sna 2a
SAP(s) 0 4 8 C opened on interface 1
2216 DLSw config>open 2 sna 2b
SAP(s) 0 4 8 C opened on interface 2
2216 DLSw config>set srb d01
DLSw segment number has been set.
2216 DLSw config>ex
2216 Config>
Figure 79. LSA Local DLSw: 2216 DLSw Configuration
1 The IP address of the TCP partner will be the internal IP address of the 2216
because the local DLSw is being configured.
2 SAPs are opened in the LSA and FR interfaces for the 2216 to know which
protocols will be encapsulated on DLSw.
Once the 2216 is configured, the configuration has to be saved on the hard drive
by using the write command, and the box must be reloaded for the configuration
to become active. The config we have just made is available on NVRAM; with the
reload it will be loaded from the NVRAM to the DRAM.
2216 Config>write
Config Save: Using bank B and config number 2
2216 Config>
2216 *reload y
Figure 80. LSA Local DLSw: 2216 Activating the Configuration
4.4.4.3 2210 Configuration
The 2210 has to be configured as a BAN router. The following steps have to be
completed:
1. Configure frame relay in the 2210.
2. Configure bridging.
3. Configure the router for BAN.
4. Configure the router for DLSw if BAN DLSw terminated only. We will skip this
step because in our setup we are using BAN bridged terminated.
Configure Frame Relay
As mentioned in the 2216 configuration, there is a back-to-back connection
between the 2210 and the 2216. That’s why LMI must be disabled and the dlci
number must match in both routers.
92 IBM 2216 and Network Utility Host Channel Connections

2210 *t6
2210 Config>set data frame 1
2210 Config>net 1
Frame Relay user configuration
2210 FR 1 Config>set clock internal 64000
Must also set the line speed to a valid value
2210 FR 1 Config>set cable rs-232 dce
2210 FR 1 Config>dis lmi
2210 FR 1 Config>add perm
Circuit number [16]?
Committed Information Rate (CIR) in bps [64000]?
Committed Burst Size (Bc) in bits [64000]?
Excess Burst Size (Be) in bits [0]?
Assign circuit name []? frban
Is circuit required for interface operation [N]?
2210 FR 1 Config>li all
Frame Relay HDLC Configuration
Interface maximum frame size (bytes) = 2048
Encoding = NRZ
Idle state = Flag
Clocking = Internal
Cable type = RS-232 DCE
Line speed (bps) = 64000
Transmit delay = 0
Lower DTR = Disabled
Frame Relay Configuration
LMI enabled = No LMI DLCI = 0
LMI type = ANSI LMI Orphans OK = Yes
CLLM enabled = No Timer Ty seconds = 11
Protocol broadcast = Yes Congestion monitoring = Yes
Emulate multicast = Yes CIR monitoring = No
Notify FECN source = No Throttle transmit on FECN = No
Data compression = No
PVCs P1 allowed = 64 Interface down if no PVCs = No
Timer T1 seconds = 10 Counter N1 increments = 6
LMI N2 error threshold = 3 LMI N3 error threshold window = 4
MIR % of CIR = 25 IR % Increment = 12
IR % Decrement = 25
Default CIR =64000 Default Burst Size = 64000
Default Excess Burst = 0
Maximum PVCs allowable = 64
Total PVCs configured = 1
Circuit Circuit Circuit CIR Burst Excess
Name Number Type in bps Size Burst
------------------------ ------- ----------- ------- ------- ------frban
16 Permanent 64000 64000 0
= circuit is required
# = circuit is required and belongs to a required PVC group
@ = circuit is data compression capable
No required PVC groups have been defined
No address translations configured
2210 FR 1 Config>ex
2210 Config>
Figure 81. LSA Local DLSw: 2210 FR Configuration
Link Services Architecture 93

Configure Bridging
The second step is to configure bridging on the token-ring interface and in the FR
PVC used for FR BAN.
2210 Config>p asrt
Adaptive Source Routing Transparent Bridge user configuration
2210 ASRT config>ena bridge
2210 ASRT config>li port
Port ID (dec) : 128:01, (hex): 80-01
Port State : Enabled
STP Participation: Enabled
Port Supports : Transparent Bridging Only
Assoc Interface : 0
Path Cost : 0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Port ID (dec) : 128:02, (hex): 80-02
Port State : Enabled
STP Participation: Enabled
Port Supports : Transparent Bridging Only
Assoc Interface : 5
Path Cost : 0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2210 ASRT config>del port 2 1
2210 ASRT config>add port 1 2
Port Number [2]?
Circuit number [16]?
2210 ASRT config>dis trans 1
2210 ASRT config>dis trans 2
2210 ASRT config>ena source 1
Segment Number for the port in hex(1 - FFF) [001]? 100
Bridge number in hex (0 - 9, A - F) [0]? 2
2210 ASRT config>ena source 2
Segment Number for the port in hex(1 - FFF) [001]? 400
2210 ASRT config>exit
2210 config>
Figure 82. LSA Local DLSw: 2210 Bridging Configuration
1 By default all the LAN interfaces in the router are added as bridging ports when
bridging is enabled. As we will not use the second token-ring on this 2210 24T,
we will disable it for bridging.
2 The frame relay interface (interface 1) is added as port number 2.
Configure BAN
BAN is configured on the router from the ASRT config prompt.
94 IBM 2216 and Network Utility Host Channel Connections

2210 ASRT config>ban
BAN (Boundary Access Node) configuration
2210 BAN config>add 2 1
Enter the BAN DLCI MAC Address []? 400022100002 2
Enter the Boundary Node Identifier MAC Address [4FFF00000000]?
40002216000A 3
Do you want the traffic bridged (b) or DLSw terminated (t) (b/t) [b]?
BAN port record added.
Reminder: enable source-routing on the port if you have not already done so.
2210 BAN config>li all
bridge BAN Boundary bridged or
port DLCI MAC Address Node Identifier DLSw terminated
2 40:00:22:10:00:02 40:00:22:16:00:0A bridged
2210 BAN config>ex
2210 ASRT config>
Figure 83. LSA Local DLSw: 2210 BAN Configuration
1 This is the bridge port where we want to enable the BAN feature.
2 This is the address to which attached end stations will send data.
3 The boundary node identifier corresponds to the destination MAC address
placed in the bridged 802.5 frames sent from the 2210 to the SNA node. This is
the MAC address of the LSA interface.
This new configuration is available in the NVRAM; we have to make it active but
load it into DRAM. For this we use the RESTART command because this command
does not exist in the 2216. That’s why in the 2216 we have to write the new
configuration and then reload the box.
2210 *restart
Are you sure you want to restart the gateway? (Yes or [No]): y
Figure 84. LSA Local DLSw: Activating the 2210 Configuration
4.4.4.4 2216 Monitoring
When monitoring the local DLSw connection on the 2216 the points that have to
be checked are:
• The ESCON and LSA interface are UP. If they are not, check that the
parameters that must match on the host and 2216 definitions effectively
match.
• The status of the LSA virtual adapter must be host connected. This means
that the host has allocated the subchannel, has opened the SAP and is waiting
for user connections.
• If there are problems with DLSw:
• Check the state of the bridging ports. They must be UP.
• Check the DLSw configuration; make sure that DLSw is enabled under
bridging and the SAPs are opened on the right interfaces.
Link Services Architecture 95

2216 +conf
Multiprotocol Access Services
2216-MAS Feature 2821 V3.2 Mod 0 PTF 0 RPQ 0 MAS.EF6 cc4_12a
Num Name Protocol
0 IP DOD-IP
3 ARP Address Resolution
11 SNMP Simple Network Management Protocol
23 ASRT Adaptive Source Routing Transparent Enhanced Bridge
26 DLS Data Link Switching
29 NHRP Next Hop Resolution Protocol
Num Name Feature
2 MCF MAC Filtering
7 CMPRS Data Compression Subsystem
9 DIALs Dial-in Access to LANs
10 AUTH Authentication
11 IPSec IPSecurity
Total Networks:
Net Interface MAC/Data-Link Hardware State
0 FR/0 Frame Relay EIA-232E/V.24 Up
1 ESCON/0 ESCON ESCON Channel Up
2 LSA/0 LSA ESCON Channel Up
2216 +net 0
ESCON Base Console
2216 ESCON>li net 1
Net: 1 Type: LSA LAN Type: Token-Ring/802.5 LAN Number: 0
Net state: Up
2216 ESCON>li sub 2
The following subchannels are defined:
Local address: 00 Device address: 04 CU Logical Address: 01
Link: CC LPAR: 01
Type: LSA
The following lantypes/lannums are using this subchannel:
LAN type: Token-Ring/802.5 LAN number: 0
2216 ESCON>exit
Figure 85. LSA Local DLSw: Listing of ESCON Subnets under DLSw
96 IBM 2216 and Network Utility Host Channel Connections

2216 +net 1
LSA Console
2216 LSA>li adapter 3
LSA Virtual Adapter
LSA Information for Net 1
--- ----------- --- --- --
LAN Type: Token-Ring/802.5 LAN Number: 0
MAC Address: 40002216000A
Downstream network: Loopback - Net 1
Status: Host connected
#SAPs Open: 1 #Link Stations Open: 1
Maximum frame size: 2052 (0x804)
Host User ID Subchannel
------------ ----------
00000000 0
1 host user(s)
2216 LSA>li link 4
Please specify a SAP number (0-236): [4]?
Link Stations on SAP 4
Station Destination Destination Link Frames Frames
ID MAC Address SAP Number Status Sent Received
------- ----------- ----------- ------ ------ --------
00000001 400000004020 4 Connected 22 22
1 link station(s) open on SAP 4
2216 LSA>li sap 5
SAP Provider User Max Link Open Link
Number SAP ID SAP ID Stations Stations
------ -------- -------- -------- ---------
4 00000000 00000001 10 1
1 SAPs currently open
2216 LSA>ex
Figure 86. LSA Local DLSw: LSA Interface Monitoring
1 Lists all the network interfaces defined on this ESCON adapter. This command
also provides the status of each network interface. The status must be UP, which
means that the link is active.
2 This command lists all the subchannels configured on this ESCON adapter. For
each subchannel, the Type field indicates the virtual network handler that owns
this subchannel. A list of all the network interfaces, identified by LAN type and
LAN number, that share each subchannel is also available with this command.
3 This command lists a virtual adapter for the LSA. It provides some information,
for example, the LAN type, LAN number, the MAC address of the LSA interface,
which is the MAC address identifying the host end of the connection, etc.
This command also shows some details about the VTAM connection with the
2216, for example, the SAPs being used, the number of link stations currently
opened on the SAPs on this interface, etc.
4 This command lists link information for LSA, for example, the identifier of the
link station, the MAC address of the LLC link station, the status of the link, etc.
5 Lists information on the SAPs opened by VTAM.
Link Services Architecture 97

To monitor the DLSw connection, do as shown in Figure 87:
2216>p asrt
2216 ASRT>li bridge
SRB Bridge ID (prio/add): 32768/40-00-22-16-00-BD
Bridge state: Enabled
UB-Encapsulation: Disabled
Bridge type: SRB
Number of ports: 1
STP Participation: IBM-SRB proprietary
**Bridge is enabled for Data Link Switching**
Maximum
Port Interface State MAC Address Modes MSDU Segment Flags
1 FR /0:16 Up 00-00-00-00-00-00 SR 2038 400 RD
Flags:RE = IBMRT PC behavior Enabled, RD = IBMRT PC behavior Disabled
SR bridge number: 1
SR virtual segment: 000 (1:N SRB Not Active)
Adaptive segment: 000
2216 ASRT>ex
2216 +p dls
Data Link Switching Console
2216 DLSw>li tcp ses all
Group/Mcast@ IP Address Conn State CST Version ActSes SesCreates
------------ ---------- ---------- --- ------- ------ ----------
1 9.9.9.1 ESTABLISHED a AIW V2R0 2 14
2216 DLSw>li dls ses all 1
Source Destination State Flags Dest IP Addr Id
--------------- --------------- --------- ------ ------------ ---
1 400000004020 04 40002216000A 04 CONNECTED LOCAL 12
2 40002216000A 04 400000004020 04 CONNECTED LOCAL 13
Figure 87. LSA Local DLSw: DLSw Monitoring
1 In local DLSw two DLSw sessions are generated internally per pair of MAC
addresses. In this example the sessions are generated between the PC MAC
address and the LSA loopback interface MAC address.
4.4.4.5 2210 Monitoring
To monitor the FR BAN connection as it is FR BAN bridge terminated, we have to
check the status of the bridging ports and the BAN ports.
98 IBM 2216 and Network Utility Host Channel Connections

2210 *t5
2210 +p asrt
2210 ASRT>li bridge
SRB Bridge ID (prio/add): 32768/00-04-AC-70-0F-B8
Bridge state: Enabled
UB-Encapsulation: Disabled
Bridge type: SRB
Number of ports: 2
STP Participation: IBM-SRB proprietary
Maximum
Port Interface State MAC Address Modes MSDU Segment Flags
1 TKR /0 Up 00-04-AC-70-0F-B8 SR 2096 100 RD,LD
2 FR /0:16 Up 00-00-00-00-00-00 SR 2038 400 RD
Flags:RE = IBMRT PC behavior Enabled, RD = IBMRT PC behavior Disabled
LE = LNM Enabled, LD = LNM Disabled, LF = LNM Failed
SR bridge number: 2
SR virtual segment: 000 (1:N SRB Not Active)
Adaptive segment: 000
2210 ASRT>ban
BAN (Boundary Access Node) console
2210 BAN>li
bridge BAN Boundary bridged or
port DLCI MAC Address Node Identifier DLSw terminated Status
2 40:00:22:10:00:02 40:00:22:16:00:0A bridged Up
2210 BAN>
Figure 88. LSA Local DLSw: 2210 Monitoring
4.4.5 LSA Local DLSw Connection (SDLC)
In this topic we are using the LSA local DLSW connection with the host to convert
synchronous data link control (SDLC) traffic to LLC2. The SDLC traffic can be
forwarded using only data link switching (DLSw) or advanced peer-to-peer
networking (APPN).
4.4.5.1 Network Environment Description
In our example the 2216 is attached via an ESCON adapter to the host and the
connection to the PC is done via a switched SDLC interface as seen in Figure 89
on page 100. A switched SDLC call-in interface allows a PU type 2.0 device to
dial into a 2216. Using a switched SDLC line provides an additional connectivity
option to your network. The interface is restricted to PU type 2.0 devices and can
run DLSw only.
Note: You cannot configure APPN over a switched SDLC call-in interface.
Link Services Architecture 99

XCA Major Node Definitions
ADAPNO=0
SAPADDR=4
MEDIUM=RING
.....
------------------------------
SW Major Node Definitions
VALENCIA ...
MAINZ ...
------------------------------
MVSIOCPDefinitions
UNITADD=04
CUADD=1
Figure 89. LSA Local DLSw Connection Network Setup (SDLC)
4.4.5.2 2216 Configuration
To configure the 2216 using the SDLC interface and connecting to the host via
LSA complete the following steps:
• Add the physical interfaces.
• Add V.25bis addresses.
• Configure V.25bis parameters.
• Add dial circuits.
• Configure dial circuits.
• Add/Configure the LSA interface.
• Configure the DLSw.
In this section we will go through these configuration steps one by one. Because
not all of the config parameters are highlighted here, we recommend that you
check your network. Please see the following resources for further details about
these parameters:
• Nways Multiprotocol Access Services Software User's Guide Version 2,
Release 2, SC30-3886
• Nways MAS Protocol Configuration and Monitoring Reference Vol.1 V2R2,
SC30-3884
Add the Physical Interfaces
Regarding our test environment, Figure 89, we add the EIA and ESCON interface
via the talk 6 command as seen in Figure 90 on page 101.
100 IBM 2216 and Network Utility Host Channel Connections
RA03
LPAR 1
LAN
RA28
LPAR 2
ESCD
LSA
CC
C9
WAN
RA39
LPAR 4
2216
S/390
LSA MAC@
40002216000A
SLDC (SW)
S/390
2216
VALENCIA
MAC@ 400052005107
40002216000A

2216 *t6
2216 Config>add dev eia
Device Slot #(1-8) [1]? 8
Device Port #(0-7) [1]? 0
Defaulting Data-link protocol to PPP
Adding EIA-232E/V.24 PPP device in slot 8 port 0 as interface #0
Use "set data-link" command to change the data-link protocol
Use "net 0" to configure EIA-232E/V.24 PPP parameters
2216 Config>add dev escon
Device Slot #(1-8) [1]? 3
Adding ESCON Channel device in slot 3 port 1 as interface #1
Use "net 1" to configure ESCON Channel parameters
2216 Config>lis dev
Ifc 0 EIA-232E/V.24 PPP Slot: 8 Port: 0
Ifc 1 ESCON Channel Slot: 3 Port: 1
2216 Config>
Figure 90. Adding the Physical Interface and Display New Status
Adding the V.25bis Address
The V.25bis interface allows routers to establish serial connections over switched
telephone lines using V.25bis modems. When adding a V.25bis address you will
be asked for the Address Name and the Network Dial Address belonging to that
address. Because we are dialing into the 2216, we have to define only a local
address. The V.25bis address is entered from the Config> command prompt, as
shown in Figure 91.
2216 Config>add v25
Assign address name [1-23] chars []? ral2216
Assign network dial address [1-30 digits] []? 13457
2216 Config>
Figure 91. Adding the V.25bis Address
Configuring V.25bis Parameters
To configure the V.25bis parameter complete the following steps (see Figure 91
on page 101):
1 To set up a serial line interface for V.25bis, set the data-link protocol for the
serial line interface. From the Config> prompt, use the set data-link v25bis
command.
2 Display the V.25bis Config> prompt by entering the network command
followed by the number of the interface.
3 Use the set local-address command to specify the network address name of
the local port. You must enter one of the address names you defined using the
add v25bis-address command.
Note: You must restart the router for configuration changes to take effect.
Link Services Architecture 101

2216 Config>set data-link v25bis 1
Interface Number [0]? 0
2216 Config>
2216 Config>net 0 2
V.25bis Data Link Configuration
2216 V25bis Config>
2216 V25bis Config>set local ral2216 3
2216 V25bis Config>list
V.25bis Configuration
Duplex = FULL
Local Network Address Name = ral2216
Local Network Address = 13457
Non-Responding addresses:
Retries = 1
Timeout = 0 seconds
Call timeouts:
Command Delay = 0 ms
Connect = 60 seconds
Disconnect = 2 seconds
Cable type = RS-232 DTE
Speed (bps) = 9600
Encoding = NRZ
2216 V25bis Config>ex
2216 Config>
Figure 92. Configuring V.25bis Parameters
• For configuring and setting the V.25bis parameter please refer to Nways
Multiprotocol Access Services Software User's Guide Version 2, Release 2,
SC30-3886.
Adding Dial Circuits
Dial circuits are mapped to V.25bis serial line interfaces. You can map multiple
dial circuits to one serial line interface.
In Figure 93 on page 103 you see the adding of the dial circuit and setting of the
protocol for that circuit. To add a dial circuit, use the add device dial circuit
command from the Config> prompt 1. The software assigns an interface number
to each circuit 4. Use this number to configure the dial circuit.
Note: Dial circuits default to the point-to-point protocol (PPP 2). You can also set
the dial circuit to use frame relay (FR) or SDLC for scenario 3.
102 IBM 2216 and Network Utility Host Channel Connections

2216 Config>add dev dial 1
Enter the number of PPP Dial Circuit interfaces [1]? 1
Adding device as interface 2
Defaulting data-link protocol to PPP 2
Base net for the circuit(s) [0]? 0
Use "set data-link" command to change the data-link protocol
Use "net " command to configure dial circuit parameters
2216 Config>list dev
Ifc 0 EIA-232E/V.24 V.25bis Slot: 8 Port: 0
Ifc 1 ESCON Channel Slot: 3 Port: 1
Ifc 2 PPP Dial Circuit 2
2216 Config>set data sdlc 3
Interface Number [0]? 2
2216 Config>list dev
Ifc 0 EIA-232E/V.24 V.25bis Slot: 8 Port: 0
Ifc 1 ESCON Channel Slot: 3 Port: 1
Ifc 2 SDLC Dial Circuit 4
2216 Config>
Figure 93. Adding a Dial Circuit
Configuring Dial Circuits
Note: If the encapsulation type is SDLC 1, the only dial circuit parameter that you
can set is the base net number. You are not able to set any other dial circuit
parameters as the software takes defaults for all other parameter values. Via the
list command we see that the base net number already matches our requirements
2, so no additional action is required.
2216 Config>net 2
Circuit configuration
2216 Circuit config: 2>encapsulator 1
SDLC user configuration
Creating a default configuration for this link
2216 SDLC 2 Config>ex
2216 Circuit config: 2>list
Base net = 0 2
2216 Circuit config: 2>ex
2216 Config>
Figure 94. Configuring a Dial Circuit
Add/Configure the LSA Interface
As described in 4.4.3, “LSA Remote DLSw Connection” on page 69 and 4.4.4,
“LSA Local DLSw Connection (FR BAN)” on page 87, we have to enable loopback
on the LSA interface and set the LAN type and a MAC address for that loopback.
Also the subchannels have to be configured. This is shown in Figure 95 on page
104.
Link Services Architecture 103

2216 Config>
2216 Config>net 1
2216 ESCON Config>add lsa
2216 ESCON Add Virtual>ena loop
Enabling loopback through network 3.
Please set the MAC address using the "MAC" command
2216 ESCON Add Virtual>lan token
2216 ESCON Add Virtual>mac 40:00:22:16:00:0A
2216 ESCON Add Virtual>sub add
2216 ESCON Add LSA Subchannel>lpar 1
2216 ESCON Add LSA Subchannel>link cc
2216 ESCON Add LSA Subchannel>cu 1
2216 ESCON Add LSA Subchannel>device 4
2216 ESCON Add LSA Subchannel>ex
2216 ESCON Add Virtual>ex
2216 ESCON Config>ex
ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]:
2216 Config>
Figure 95. Add/Configure LSA Interface
Configure the DLSw
When configuring DLSw, IP and bridging have to be configured also because
DLSw uses these two protocols. But since bridging doesn’t need to be configured
in the LSA and SDLC interfaces, we will skip the bridging step and configure only
IP and DLSw.
The only thing that needs to be configured in this scenario for IP is the internal IP
address that DLSw uses as a TCP partner (see Figure 96).
2216 Config>p
Protocol name or number [IP]?
Internet protocol user configuration
2216 IP config>set int 9.9.9.1
2216 IP config>ex
Figure 96. Setting the Internal IP Address
104 IBM 2216 and Network Utility Host Channel Connections

2216 Config>pdls
DLSw protocol user configuration
2216 DLSw config>ena dls 1
Data Link Switching is now enabled
2216 DLSw config>set srb d01 2
DLSw segment number has been set.
2216 DLSw config>add sdlc 3
Interface # [0]? 2
SDLC Address or 'sw' (switched call-in) [C1]? sw 4
Source MAC address [4007E40002FF]? 400052005107 5
Source SAP in hex [4]?
Destination MAC address [000000000000]? 40002216000A 6
Destination SAP in hex [0]? 4
** For a switched call-in link station .....
** - PU type is forced to be 2
** - Configured XID block/id num is used to override
** fields in the XID0 from the SDLC station
** - if block/id set to zeroes, XID0 is not modified
** - otherwise configured fields are put into XID0
** - Poll type is not configured (not used)
XID0 block num in hex (0-0xfff) [0]? 05d 7
XID0 id num in hex (0-0xfffff) [0]? 99999 8
2216 DLSw config>add tcp 9.9.9.1 9
Adding local transport connection
Neighbor Priority (H/M/L) [M]?
Local transport TCP Neighbor has been added
2216 DLSw config>
2216 DLSw config>open 3 10
Enter SAP in hex (range 0-FE), 'SNA', 'NB' or 'LNM' [4]? sna
SAP(s) 0 4 8 C opened on interface 3
2216 DLSw config>ex
2216 Config>
2216 *t 6
2216 Config>write
Config Save: Using bank A and config number 4
216 Config>
2216 Config>
2216 *reload y 11
Figure 97. Configuring the DLS Protocol
1 Enable DLSw protocol.
2 Enter the set srb command to designate the source-route bridge (SRB) segment
number for the DLS router.
3 Add the SDLC link station.
4 Specify “sw” which indicates that this is a switched SDLC call-in interface.
5 The MAC address for this SDLC PU. This value identifies the attached SDLC
station within the DLSw domain. It must be unique among the SDLC and QLLC
stations attached to this router, and it should be unique among all LAN, SDLC, and
QLLC stations.
Link Services Architecture 105

6 The MAC address of the remote link station to which you are connecting. The
MAC address is in noncanonical bit order (token-ring) format. This is true even if
the remote endstation is on the Ethernet. In such cases, use the ASRT
monitoring flip command to help flip the MAC address.
7 The ID block of the PU type 2 in our case, if set, has to match the switch major
node definitions.
Note: If you set this parameter to a nonzero value for a switched SDLC call-in
circuit, the configured information is placed in XID_0. For a switched SDLC call-in
circuit, the configured XID_0 block num is used differently. The software assumes
that the call-in station always builds its own XID_0. If this parameter is set to a
nonzero value, the station’s XID_0 is modified with the configured value. If this
parameter is set to a zero value, the station’s XID_0 is not modified.
8 ID num of the attached PU type 2 device.
9 The IP address of the TCP partner will be the internal IP address of the 2216
because the local DLSw is being configured.
10 Allows DLSw to transmit data over the specified SAP. DLSw uses SAPs for
communication on interfaces that support LLC.
11 After saving the config reload the 2216 so that the new config becomes active.
After the 2216 has been configured we need to set up the modems and the PC.
For the PC we are using the IBM Personal Communication software. We defined
the PCOM to use the COM port with the Hayes AutoSync attachment. Therefore
our modem on the PC side has to have the capability to be set to the AutoSync
mode. The modem on the 2216 has to be a V.25bis modem that supports
synchronous V.25bis commands and the 1988 ITU/CCITT V.25bis specification
and has to be set to AutoAnswer mode to react to the incoming call.
Now that everything has been set up regarding our test environment (Figure 89
on page 100), we can monitor the connections.
4.4.5.3 2216 Monitoring
Monitoring the ESCON Interface
The monitoring command is available from the GWCON prompt, which you get
via the T5 process. You access the talk 5 commands that show the status of
channel resources hierarchically as follows:
• From the * prompt, type talk 5 and press Enter to reach the + prompt.
• From the + prompt, type int and press Enter and note the logical interface
number for the physical ESCON interface you are interested in. The physical
interface is commonly called the base net and might have a number of LSA,
LCS, or MPC+ virtual interfaces defined on top of it. The base net and all
virtual interfaces each have a different logical interface number (see Figure 98
on page 107).
106 IBM 2216 and Network Utility Host Channel Connections

2216 *t5
2216 +int
Self-Test Self-Test Maintenance
Net Net' Interface Slot-Port Passed Failed Failed
0 0 V.25/0 Slot: 8 Port: 0 2 1 1
1 1 ESCON/0 Slot: 3 Port: 1 1 0 0
2 0 SDLC/0 1 12 0
3 1 LSA/0 Slot: 0 Port: 0 1 2 0
2216 +
Figure 98. Interface List via GWCON
• From the + prompt, type net base n number and press Enter to reach the
ESCON console subprocess. The command prompt changes to ESCON> as
appropriate (see Figure 99).
2216 +net 1
ESCON Base Console
2216 ESCON>
Figure 99. Change to the ESCON Base Net Prompt
At these prompts, you can use the li nets command to see the current state of
every (LSA, LCS, MPC+) virtual interface using this base net. You can also type
li sub to view the currently running subchannel configuration for this base net
(see Figure 100).
2216 ESCON>list ?
SUbchannels
NEts
2216 ESCON>list sub
The following subchannels are defined:
1 Local address: 00 Device address: 04 CU Logical Address: 01
Link: CC LPAR: 01
2 Type: LSA
The following lantypes/lannums are using this subchannel:
3 LAN type: Token-Ring/802.5 LAN number: 0 4
2216 ESCON>li net
Net: 3 Type: LSA LAN Type: Token-Ring/802.5 LAN Number: 0
Net state: Up 5
Figure 100. List of Net and Subchannel from the ESCON Base Net Prompt
1 Local Address The subchannel address index used internally by the device.
2 Type Type of virtual interface: LCS, LSA, or MPC+.
3 LAN Type LAN type, either token-ring/802.5, Ethernet/802.3,
Ethernet/V2, Ethernet or FDDI.
4 LAN Number Interface number of the LAN.
5 Net State State of the network: Up, Down, Disabled, Not Present, HW
Mismatch, or Testing. Up indicates that the link is up.
Monitoring ESCON LSA Interface (SDLC)
From the base net ESCON> prompt or directly from the + prompt, type net virtual
net number and press Enter to see more detail on a particular virtual interface that
Link Services Architecture 107

uses this base net. The command prompt changes to LSA>, LCS>, or MPC+>,
depending on the type of virtual interface you select.
Each of these prompts supports a list command to show configuration and
current status information relevant to the virtual interface type (see Figure 101).
2216 +net 3
LSA Console
2216 LSA>list ?
ADapter
SAp
LInk station
Figure 101. List of Subcommands for the LSA Interface
The next figures reflect these list commands one by one regarding our test
environment (see Figure 89 on page 100).
The adapter command lists virtual adapters for LSA (Figure 102).
2216 LSA>li adapter
LSA Virtual Adapter
LSA Information for Net 3
--- ----------- --- --- --
LAN Type: Token-Ring/802.5 LAN Number: 0
MAC Address: 40002216000A
Downstream network: Loopback - Net 3
Status: Host connected
#SAPs Open: 1 1 #Link Stations Open: 1 2
Maximum frame size: 2052 (0x804) 3
Host User ID 4 Subchannel 5
------------ ----------
00000000 0
1 host user(s)
Figure 102. List of Virtual Adapters
1 #SAPs Open Number of SAPs opened by VTAM on this LSA
interface
2 #Link Stations Open Number of link stations open for all SAPs on this
LSA interface
3 Maximum Frame Size Maximum frame size supported over this LSA interface
4 Host User ID A unique ID generated by VTAM to identify the host
user on a given subchannel
5 Subchannel The local subchannel being used by this host user
The SAP command lists service access points (SAPs) for LSA (see Figure 103 on
page 109).
108 IBM 2216 and Network Utility Host Channel Connections

2216 LSA>li sap
SAP Provider User Max Link Open Link
Number SAP ID SAP ID Stations Stations
1 2 3 4 5
------ -------- -------- -------- ---------
4 00000000 00000001 10 1
1 SAPs currently open
Figure 103. List of SAPs for LSA
1 SAP Number Identifies the SAP to LLC
2 Provider SAP ID A unique ID generated by VTAM to identify this SAP
3 User SAP ID A unique ID generated by device to identify this SAP
4 Max Link Stations Maximum number of link stations VTAM can open on this
SAP
5 Open Link Stations Number of link stations currently open on this SAP
The link command lists link information for LSA (Figure 104).
2216 LSA>li link
Please specify a SAP number (0-236): [4]?
Link Stations on SAP 4
1 2 3 4 5 6
Station Destination Destination Link Frames Frames
ID MAC Address SAP Number Status Sent Received
------- ----------- ----------- ------ ------ --------
00000001 400052005107 4 Connected 7 7
1 link station(s) open on SAP 4
Figure 104. List of Link Information for LSA
1 Station ID A unique ID generated by device to identify this
link station
2 Destination MAC Address MAC address of the remote LLC link station (our
PC)
3 Destination SAP Number SAP value of the remote LLC link station
4 Link Status Current status of the LLC connection
5 Frames Sent Number of packets sent to VTAM for this link
station
6 Frames Received Number of packets received from VTAM for this
link station
Monitor DLSw
We will provide a few listings of monitoring commands which are available for the
DLSw protocol. For more detailed information please refer to Nways
Multiprotocol Access Services Protocol Configuration and Monitoring Reference
Vol. 1 Version 3.2, SC30-3884.
Link Services Architecture 109

From the GWCON type protocol dls to get the DLS> prompt to set up monitoring
commands. We are using only some list commands here:
The tcp sessions command displays the status of all known TCP sessions to peer
DLSw routers. See Figure 105.
2216 +p dls
Data Link Switching Console
2216 DLSw>li tcp ses
Group/Mcast@ IP Address 1 Conn State CST Version ActSes SesCreates
--------------- --------------- -------------- --- -------- ------ ----------
1 9.9.9.1 ESTABLISHED a AIW V2R0 2 2
2216 DLSw>
Figure 105. List of TCP Sessions
1 The neighbor IP address used for DLSw and the internal IP address of the
2216.
The dls sessions command displays current DLS session information including
source, destination, state, flags, destination IP address, and a session ID (Figure
106).
2216 DLSw>list dls ses all 1
Source Destination State Flags Dest IP Addr Id
-------2-------- --------------- --------- ------- -------------- ----
1 40002216000A 04 400052005107 04 CONNECTED LOCAL 1
2 SDLC 0002-FF 04 40002216000A 04 CONNECTED LOCAL 0
2216 DLSw>
Figure 106. List of DLS Sessions
1 In local DLSw two DLSw sessions are generated internally per pair of MAC
addresses. In this example the sessions are generated between the PC MAC
address/SDLC interface on net 2 and the LSA loopback interface MAC address.
2 The source MAC address and SAP of the session. For sessions with an SDLC
source, the MAC address is replaced by the following character strings so that
these sessions can be identified easily:
Characters Content:
1-5 "SDLC "
6-7 Interface number
8 "-"
9-10 SDLC station address
11-12 " "
The sdlc config command displays configured parameters for the SDLC attached
PU (Figure 107 on page 111).
110 IBM 2216 and Network Utility Host Channel Connections

2216 DLSw>list sdlc config
Interface #, or 'ALL' [0]? all
Net Addr Status Source SAP/MAC Dest SAP/MAC PU Blk/IdNum PollType
2 FF(sw) Enabled 04 400052005107 04 40002216000A 2 05D/99999
2216 DLSw>
Figure 107. List of SDLC Config
The sdlc sessions command displays information about all SDLC dls sessions
within the router. There is only one session on net 2 (Figure 108).
2216 DLSw>list sdlc sess
Net Address Source SAP/MAC Dest SAP/MAC PU OutQ State
1. 2 FF(01) 04 400052005107 04 40002216000A 2 0 CONTACTED
2216 DLSw>
Figure 108. List of SDLC Sessions
Monitor SDLC
To be able to monitor SDLC we have to enter the net command with the
appropriate net# of the SDLC interface from the GWCON> prompt. In our case it
is net 2. See Figure 98 on page 107. For more information about SDLC
monitoring see Nways Multiprotocol Access Services Software User's Guide,
SC30-3886.
The link configuration command displays information for all configured SDLC link
stations on the interface. Displays information for the SDLC counters since the
last router restart or the last clear counters (Figure 109).
2216 +net 2
SDLC Console
2216 SDLC-2>lis link
Link counters for: LNK00002 (ENABLED)
I-Frames I-Bytes Re-Xmit UI-Frames UI-Bytes
--------- --------- --------- --------- ---------
Send 7 93 0 0 0
Recv 7 174 0 0
RR RNR REJ UP
--------- --------- --------- ---------
Send 136 0 0 0
Recv 133 0 0 0
216 SDLC-2>
Figure 109. List of Link Configuration
The station all command displays the status of all stations (Figure 110 on page
112). The software displays an * 1 next to the stations that were not explicitly
configured using the add station command but were added to the configuration
because they were defined and activated in the protocol layer (DLSw or APPN).
Link Services Architecture 111

Figure 110. List of All Stations
4.5 LSA APPN Support Example
4.5.1 Host Definitions
2216 SDLC-2>li station all
Address Name Status Max BTU Rx Window Tx Window
------- -------- ---------- ------- --------- ---------
1* 01 SDLC_1 CONNECTED 2048 7 7
-------
* denotes defaulted configuration in use.
216 SDLC-2>
4.5.1.1 IOCP and MVS Operating System Definitions
The IOCP and MVS operating system definitions are exactly the same as for LSA
SNA support. For more details refer to Figure 40 on page 60.
4.5.1.2 VTAM Definitions
XCA Major Node Definitions
The XCA Major Node definitions for APPN on LSA are exactly the same as for
LSA SNA support. For more details refer to Figure 41 on page 60.
XCA Switched Major Node Definitions
To run APPN over a 2216 LSA connection we have to add a PU statement for the
2216 into the VTAM switched major node definition. The relationship between the
definitions in the host and in the 2216 can be seen in Figure 39 on page 58.
Switched Major Node Definitions
The switched major node defines the PU for the 2216 to run APPN over an LSA
connection.
******************************** TOP OF DATA *********************************
SW5303N VBUILD TYPE=SWNET 1
P2216N PU ADDR=02, X
PUTYPE=2,
CPCP=YES,
CONNTYPE=APPN, 2
NN=YES, 3
DYNLU=YES
CPNAME=NN2216 4
******************************* BOTTOM OF DATA *******************************
Figure 111. LSA APPN: Switched Major Node Definitions
In this scenario we have defined a member for the 2216. In an LSA APPN
connection environment, the switched major node defines the 2216 as an
adjacent network node:
1 The TYPE field must be SWNET.
2 The connection type is set to APPN.
3 The 2216 is set to an adjacent network node.
112 IBM 2216 and Network Utility Host Channel Connections

4 Define the 2216 CP’s name.
4.5.2 Network Environment Description
4.5.3 2216 Configuration
XCA Major Node Definitions
ADAPTNO=0
SAPADDR=4
MEDIUM=RING
------------------------------
SW Major Node Definitions
NN2216..
------------------------------
MVS IOCP Definitions
UNITADD=04
CUADD=1
RA03
LPAR 1
RA28
LPAR 2
Figure 112. Overview of the APPN-LSA Test Environment
TR
LAN
ESCD
usibmra.valencia
WAN
RA39
LPAR 4
LSA 2216
-----
S/390
2210
To run APPN over an LSA interface, the following steps are required:
• Add the APPN package to the 2216.
• Define the physical interfaces.
• Add an LSA virtual interface.
• Configure an LSA virtual interface
• Configure an LSA subchannel
• Configure the APPN loopback.
• Configure APPN for the 2216.
CC
C9
usibmra.nn2216
PPP
TR
usibmra.mainz
usibmra.ra03m
Loopback
LSA
MAC@1:
40002216000A
APPN
MAC@2:
40002216000B
usibmra.nn2210
Link Services Architecture 113

In this section we will perform these items step by step and explain the
configuration parameters regarding our test environment which is shown in Figure
112 on page 113. Because not all config parameters are highlighted here, we
recommend that you check your network. For further details about these
parameters please see:
• Nways Multiprotocol Access Services Software User's Guide Version 2,
Release 2, SC30-3886
• Nways Multiprotocol Access Services Protocol Configuration and Monitoring
Reference Vol. 1 Version 3.2, SC30-3884
• Nways Multiprotocol Access Services Protocol Configuration and Monitoring
Reference Vol. 2 Version 3.2, SC30-3885
4.5.3.1 Add the APPN Package to the 2216
Provided that your 2216 code supports APPN, the APPN package will be
included in the 2216 via talk 6 on the command line, which requires a reload of
the whole device. The 2216 will tell you this as you can see in Figure 113:
Config>load add pack appn
appn package configured successfully
This change requires a reload.
2216 Config>write
Config Save: Using bank A and config number 2
216 Config>
2216 *reload y
Figure 113. Adding the APPN Package to the 2216
4.5.3.2 Define the Physical Interfaces
Regarding our test environment we are going to add the physical interfaces via
the T6 on the command line:
• LAN adapter (token-ring)
• WAN adapter (EIA-232)
• ESCON adapter
Figure 114 reflects the result of adding the devices to the 2216 (TR/EIA/ESCON).
The EIA device reminds you to set up the data link protocol besides how to
configure the interfaces via the set data-link command. For our test environment
this default value (PPP) matches.
114 IBM 2216 and Network Utility Host Channel Connections

Config>add dev to
Device Slot #(1-8) [1]? 1
Device Port #(1-2) [1]? 1
Adding Token Ring device in slot 1 port 1 as interface #0
Use "net 0" to configure Token Ring parameters
Config>add dev eia
Device Slot #(1-8) [1]? 8
Device Port #(0-7) [1]? 0
Defaulting Data-link protocol to PPP
Adding EIA-232E/V.24 PPP device in slot 8 port 0 as interface #1
Use "set data-link" command to change the data-link protocol
Use "net 1" to configure EIA-232E/V.24 PPP parameters
Config>add dev escon
Device Slot #(1-8) [1]? 3
Adding ESCON Channel device in slot 3 port 1 as interface #2
Use "net 2" to configure ESCON Channel parameters
Figure 114. Adding the Physical Interfaces to the 2216
Via the list device command (see Figure 115) from the config command prompt
we can get the logical interface numbers, the device type and their physical
position inside the 2216.
Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 EIA-232E/V.24 PPP Slot: 8 Port: 0
Ifc 2 ESCON Channel Slot: 3 Port: 1
Figure 115. List of the Devices inside the 2216
After the add dev command the net parameters have to be set up. We will add
only the parameter for the ESCON adapter which in our scenario is the net
number 2 (see Figure 115) for the configuration of the token-ring interface. We
will display only the MAC address setting as seen in Figure 116. This address will
be used later by the PC software to connect to the host. For all other parameter
configurations refer to Nways Multiprotocol Access Services Software User's
Guide, SC30-3886.
2216 Config>net 0
Token-Ring interface configuration
2216 TKR config>
2216 TKR config>set phy 40:00:22:16:00:01
2216 TKR config>
Figure 116. Setting the MAC Address of the Token-Ring Interface
4.5.3.3 Add/Configure the LSA Virtual Interface
Now that the physical interfaces have been set we can configure the
ESCON/PCA via the net command and use the add LSA command (see Figure
117) to add an LSA virtual interface and get to the ESCON/PCA Add Virtual>
prompt from which you can enter other interface and subchannel parameters:
Link Services Architecture 115

2216 Config>net 2
2216 ESCON Config>add lsa
2216 ESCON Add Virtual>
Figure 117. Adding the LSA Virtual Interface
There are seven commands available to configure the LSA virtual interface for an
APPN connection with the host on an ESCON/PCA adapter:
• enable-disable
• acklen
• blktimer
• lantype
• mac
• maxdata
• subchannel
We will focus only on the enable-disable, lantype, mac and subchannel commands
and their values. In our case, all others will stay by their defaults. For more
information about the other parameters see Nways Multiprotocol Access Services
Software User's Guide, SC30-3886.
2216 ESCON Add Virtual>ena loopback 1
Enabling loopback through network 3.
Please set the MAC address using the "MAC" command
2216 ESCON Add Virtual>mac 40:00:22:16:00:0A 2
2216 ESCON Add Virtual>lan tok 3
Figure 118. Enable Loopback for the LSA Interface
1 enable or disable Enables or disables loopback on an LSA interface.
Note: Only one of these parameters can be entered, depending on the state of
the loopback function. If the loopback is disabled, you can enable it; if it is
enabled, you can disable it.
Loopback is enabled on the LSA interface to simulate the LAN the LSA interface
is attached to.
The LSA interface represents the host attached to the LAN. And the MAC
address assigned to this interface will be the MAC address that will identify the
host in the APPN network (see Figure 118).
2 mac address A unique MAC address to identify this virtual interface. This
parameter is available only when loopback is enabled. It is the MAC address of
the LSA/VTAM side of the loopback connection. The MAC address of the APPN
side of the loopback connection is specified using ADD APPN.
3 lantype LAN type, either Ethernet, or Token-Ring. The type has to match the
host definitions.
The subchannels command places you at the next prompt based on the value of
command. The command can be one of the following:
add sub add Add a subchannel displays the ESCON Add Subchannel>
prompt or PCA Add Subchannel> prompt from which you
116 IBM 2216 and Network Utility Host Channel Connections

can add device address, LPAR number, link address, and
CU logical address.
Note: LPAR, LINK,CU parameters don’t apply to PCA.
delete sub delete Deletes a configured LSA subchannel. It lists the
configuration for the configured LSA subchannels and
allows you to delete one of them by specifying the “sub”
number from the list.
list sub list Lists information for the LSA subchannels.
mod sub mod Modifies a configured LSA subchannel. It lists the
configuration of the configured LSA subchannels and
allows you to modify one of them by specifying the “sub”
number from the list. Once you have selected the
subchannel, you can change the device address, LPAR
number, Link Address, and CU Logical Address.
4.5.3.4 Configure the LSA Subchannels
LSA uses a single bidirectional subchannel between the host and the 2216.
VTAM issues a READ command immediately following each WRITE command to
retrieve data from the channel. From the ESCON/PCA Add Virtual> prompt the
subchannel has to be added and configured to reflect the definitions made in the
host. See Figure 119 on page 117 for the subchannel configuration parameters.
2216 ESCON Add Virtual>sub add
2216 ESCON Add LSA Subchannel>device 4 1
2216 ESCON Add LSA Subchannel>lpar 1 2
2216 ESCON Add LSA Subchannel>cu 1 3
2216 ESCON Add LSA Subchannel>link cc 4
2216 ESCON Add LSA Subchannel>ex
216 ESCON Add Virtual>ex
2216 ESCON Config>ex
ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]: y
2216 Config>
Figure 119. Configure an LSA Subchannel
The parameters that have to be configured regarding our test environment
(ESCON adapter) in the subchannel are:
1 device The unit address transmitted on the channel path to select a 2216
device. This value must be in the range specified in the UNITADD
parameter in the CNTLUNIT macro of the IOCP definitions in the
host.
2 lpar Logical Partition number in the host. Specifying this parameter
allows multiple LPARs to share one ESCON fiber. This value is
defined in the IOCP by the RESOURCE macro instruction. If the host
is not using EMIF, the default of 0 must be used for the LPAR
number.
3 cu The Control Unit address defined in the host for the 2216. This value
is defined in the host input/output configuration program (IOCP) by
the CUADD statement on the CNTLUNIT macro instruction. The
Control Unit address must be unique for each LPAR defined on the
same host.
Link Services Architecture 117

4 link: If one ESCON Director (ESCD) is in the communication path, the link
address is the ESCD port number that is attached to the host. If two
ESCDs are in the path, it is the host-side port number of the ESCD
defined with the dynamic connection. When no ESCD is in the
communication path, this value must be set to X'01'.
The list device command (see Figure 120 on page 118) from the config prompt
reflects the new status of the interfaces for the 2216; the LSA has its own
interface number.
2216 Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 EIA-232E/V.24 PPP Slot: 8 Port: 0
Ifc 2 ESCON Channel Slot: 3 Port: 1
Ifc 3 LSA - ESCON Channel Base Net: 2
Figure 120. List of the Interfaces inside the 2216
4.5.3.5 Configure APPN Loopback
APPN loopback interface is added creating a new interface inside the 2216 with a
new network number. This interface will be attached to the same virtual LAN as
the LSA interface.
Note
1. APPN loopback cannot be added unless loopback has been enabled on an
LSA virtual net.
2. You can add APPN loopback only once for each physical 2216. If you
configure APPN loopback on an ESCON channel, you do not need to enable it
on a PCA or other ESCON channel in the same 2216.
3. Any LSA nets connection to APPN must have the same LAN type as the
APPN loopback net.
This new interface represents the 2216 attached to the LAN. And the MAC
address assigned to this interface will be the MAC address that the host will see
as the MAC address of its adjacent network node.
So the first three steps to configure APPN loopback are:
• Add the APPN loopback interface 1
• Define the LAN type (Note: This has to match the LAN type of the LSA) 2
• Define the MAC address 3
These steps are shown in Figure 121. Also in this figure the list net command
from the ESCON Config> prompt is displayed which reflects the new net number
for the APPN loopback. To continue with the APPN configuration for the 2216, the
new status has to be saved and the 2216 has to be reloaded.
118 IBM 2216 and Network Utility Host Channel Connections

2216 Config>net 2
2216 ESCON Config>add appn 1
2216 ESCON Add Virtual>?
LAN type
MAC address
Exit
2216 ESCON Add Virtual>lan toke 2
2216 ESCON Add Virtual>mac 40:00:22:16:00:0B 3
2216 ESCON Add Virtual>ex
2216 ESCON Config>li net
Net: 4 Protocol: APPN Loopback LAN type: Token-Ring/802.5
APPN loopback MAC address: 40002216000B
Net: 3 Protocol: LSA LAN type: Token Ring LAN number: 0
Maxdata: 2052
Loopback is enabled.
MAC address: 40002216000A
Block Timer: 10 ms ACK length: 10 bytes
Figure 121. Adding the APPN Loopback Interface
4.5.3.6 Configure APPN Protocol
To configure the APPN protocol for the 2216, the next step is to set up the APPN
node of the 2216. After the node is set, we have to reload the 2216 otherwise we
are not able to configure the APPN port definitions for the different interfaces. In
our test environment, these interfaces are the Loopback APPN-Channel, the TR
and the EIA interface. The node is setup via the APPN protocol. Here the APPN
will be set, and the NETID (network ID) where our 2216 resides and the control
point (CP) name of the 2216 has to be defined. These three parameters (enable
APPN, NETID, CP name) are the main objects to configure; to set up the
availability of APPN in the 2216, the other parameters can be left by their default
if not needed. Figure 122 shows the APPN setup of our 2216 used in the test
environment via the talk 6 command line.
2216 Config>p appn
2216 APPN config>set node
Enable APPN (Y)es (N)o [Y]? y
Network ID (Max 8 characters) [ ]? usibmra 1
Control point name (Max 8 characters) [ ]? nn2216 2
Enable branch extender or border node
(0=Neither, 1=Branch Extender, 2=Border Node) [0]?
Route addition resistance(0-255) [128]?
XID ID number for subarea connection (5 hex digits) [00000]?
Use enhanced #BATCH COS (Y)es (N)o [Y]?
Use enhanced #BATCHSC COS (Y)es (N)o [Y]?
Use enhanced #INTER COS (Y)es (N)o [Y]?
Use enhanced #INTERSC COS (Y)es (N)o [Y]?
Write this record? [Y]?
The record has been written.
2216 APPN config>
Config>reload ****> needed to be able to configure APPN port defs
Figure 122. Setup of the 2216 for APPN Readiness
1 Set the network ID where the 2216 resides.
2 Define the unique CP name for the 2216.
Link Services Architecture 119

The 2216 has been set up to run APPN traffic on its interfaces. Now the
interfaces have to be configured regarding our test scenario. For the connection
to the host we have to configure a PORT and a LINK for the Loopback APPN-
Channel. The same applies to the EIA interface which is connected to the 2210
via PPP. For the TR interface only the port definition has to be set; the station will
be added dynamically during session establishment. Notice the interface number
when configuring APPN PORT/LINK for the host connection. The Loopback
APPN-Channel will be configured but not the ESCON interface. From Figure 123
you can see it is Ifc 4 in our scenario.
2216 Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 EIA-232E/V.24 PPP Slot: 8 Port: 0
Ifc 2 ESCON Channel Slot: 3 Port: 1
Ifc 3 LSA - ESCON Channel Base Net: 2
Ifc 4 Loopback APPN - Channel Slot: 0 Port: 0
Figure 123. List of the Interfaces inside the 2216
The following figures show the configuration for the interfaces in the 2216 to run
APPN traffic through it, starting with Figure 124 on page 120 for the token-ring
interface. In our test environment we take the defaults given by the 2216 for the
different parameters and are only concerned with the interface number which is 0
for the token-ring interface.
2216 Config>p appn
2216 APPN config>add port
APPN Port
Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING,
(M)PC, (S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P [ ]? t
Interface number(Default 0): [0]? 0
Port name (Max 8 characters) [T00000]? 1
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Support multiple PU (Y)es (N)o [N]?
Service any node: (Y)es (N)o [Y]?
High performance routing: (Y)es (N)o [Y]?
Maximum BTU size (768-17745) [2048]?
Maximum number of link stations (1-976) [512]?
Percent of link stations reserved for incoming calls (0-100) [0]?
Percent of link stations reserved for outgoing calls (0-100) [0]?
Local SAP address (04-EC) [4]?
Local HPR SAP address (04-EC) [C8]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
2216 APPN config>
Figure 124. Add the APPN Port for the Token-Ring Interfaces
1 APPN port name for the token-ring interface
For the EIA interface the port and the link have to be added. Again we stay with
the defaults given by the 2216 for the different configuration parameter as seen in
Figure 125 on page 121. The port name for the EIA interface is needed when we
configure the link. A station name has to be placed during the add link process
120 IBM 2216 and Network Utility Host Channel Connections

and also the type of the adjacent node where the link is connected. The name for
the port and the link will be seen later when monitoring the APPN ports and links.
2216 APPN config>
2216 APPN config>add port
APPN Port
Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING,
(M)PC, (S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P [ ]? p
Interface number(Default 0): [0]? 1
Port name (Max 8 characters) [PPP00001]? 1
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Service any node: (Y)es (N)o [Y]?
High performance routing: (Y)es (N)o [Y]?
Maximum BTU size (768-4086) [2048]?
Local SAP address (04-EC) [4]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
2216 APPN config>add link
2216 APPN Station
Port name for the link station [ ]? ppp00001
Station name (Max 8 characters) [ ]? to2210 2
Activate link automatically (Y)es (N)o [Y]?
Adjacent node type: 0 = APPN network node,
1 = APPN end node or Unknown node type,
2 = LEN end node [0]? 0
TG Number (0-20) [0]?
High performance routing: (Y)es (N)o [Y]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
2216 APPN config>
Figure 125. Add the Port and Link to the EIA Interface for APPN
1 APPN port name for the PPP link on the 2216, which is needed when we define
the station name for that link (2)
2 Station name for the PPP link
In Figure 126 on page 122 the port and link are configured for the loopback APPN
channel interface. Like the EIA interface we accept the defaults given by the 2216
and choose the name for the station to reflect our test environment. See Figure
112 on page 113.
Link Services Architecture 121

2216 APPN config>add port
APPN Port
Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING,
(M)PC, (S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P [ ]? t
Interface number(Default 0): [0]? 4 1
Port name (Max 8 characters) [T00004]? 2
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Support multiple PU (Y)es (N)o [N]?
Service any node: (Y)es (N)o [Y]?
High performance routing: (Y)es (N)o [Y]?
Maximum BTU size (768-17745) [2048]?
Maximum number of link stations (1-976) [512]?
Percent of link stations reserved for incoming calls (0-100) [0]?
Percent of link stations reserved for outgoing calls (0-100) [0]?
Local SAP address (04-EC) [4]?
Local HPR SAP address (04-EC) [C8]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
2216 APPN config>add link
APPN Station
Port name for the link station [ ]? t00004
Station name (Max 8 characters) [ ]? tovtam 3
Activate link automatically (Y)es (N)o [Y]?
MAC address of adjacent node [000000000000]? 40002216000A 4
Does link support APPN function: (Y)es (N)o [Y]?
Adjacent node type: 0 = APPN network node,
1 = APPN end node or Unknown node type,
2 = LEN end node [0]?
High performance routing: (Y)es (N)o [Y]?
TG Number (0-20) [0]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]? y
Fully-qualified CP name of adjacent node (netID.CPname) []?
5 usibmra.ra03m
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
Figure 126. Add the Port and the Link to the Loopback APPN-Channel Interface
1 Interface number of the loopback APPN channel
2 APPN port name for the loopback APPN channel link on the 2216, which is
needed when we define the station name for that link (3)
3 Station name of the loopback APPN channel link
4 MAC Address of the LSA/VTAM side of the loopback connection
5 CP name of the adjacent node, the host
At last we have to configure our PCs as EN (end node) and the 2210 as a NN
(network node) for our test scenario. For the PCs we use the IBM Personal
Communication software and the Communication Server/2 (including HPR
122 IBM 2216 and Network Utility Host Channel Connections

support) to connect them to an APPN network. The main items to configure at the
PCs are the fully qualified CP name and the destination MAC address from the
token-ring interface, either the 2216 or the 2210. Of course this depends on what
type of connection you want to have with the host.
The same rule applies to the 2210 and 2216, so we have to set the node first (see
Figure 127 on page 123), and then we have to configure the interface for APPN,
here the WAN (wide area network) and token-ring interface.
2210 Config>p appn
2210 APPN config>set node
Enable APPN (Y)es (N)o [Y]? y
Network ID (Max 8 characters) [ ]? usibmra 1
Control point name (Max 8 characters) [ ]? nn2210 2
Enable branch extender or border node
(0=Neither, 1=Branch Extender, 2=Border Node) [0]?
Route addition resistance(0-255) [128]?
XID ID number for subarea connection (5 hex digits) [00000]?
Use enhanced #BATCH COS (Y)es (N)o [Y]?
Use enhanced #BATCHSC COS (Y)es (N)o [Y]?
Use enhanced #INTER COS (Y)es (N)o [Y]?
Use enhanced #INTERSC COS (Y)es (N)o [Y]?
Write this record? [Y]?
The record has been written.
Figure 127. Set Up the 2210 for APPN Readiness
1 Set the network ID where the 2210 resides.
2 Define the unique CP name for the 2210.
Regarding the internal interface numbers in the 2210, the affected token-ring
configuration for APPN (add port only) is seen in Figure 128.
2210 APPN config>add port
2210 APPN Port
Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING,
(S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P [ ]? t
Interface number(Default 0): [0]? 0
Port name (Max 8 characters) [T00000]? 1
Enable APPN on this port (Y)es (N)o [Y]? y
Port Definition
Support multiple PU (Y)es (N)o [N]?
Service any node: (Y)es (N)o [Y]?
High performance routing: (Y)es (N)o [Y]?
Maximum BTU size (768-17745) [2048]?
Maximum number of link stations (1-976) [512]?
Percent of link stations reserved for incoming calls (0-100) [0]?
Percent of link stations reserved for outgoing calls (0-100) [0]?
Local SAP address (04-EC) [4]?
Local HPR SAP address (04-EC) [C8]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>
Figure 128. Add the APPN Port for the Token-Ring Interfaces on 2210
Link Services Architecture 123

1 APPN port name for the token-ring interface
The configuration for the WAN interface for the 2210 is much like the EIA interface
for the 2216 as you can see in Figure 129 on page 124. First the port has to be
added and then the link.
APPN config>add port
APPN Port
Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING,
(S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P [ ]? p
Interface number(Default 0): [0]? 1
Port name (Max 8 characters) [PPP00001]? 1
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Service any node: (Y)es (N)o [Y]?
High performance routing: (Y)es (N)o [Y]?
Maximum BTU size (768-4086) [2048]?
Local SAP address (04-EC) [4]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>add link
APPN Station
Port name for the link station [ ]? ppp00001
Station name (Max 8 characters) [ ]? to2216 2
Activate link automatically (Y)es (N)o [Y]?
Adjacent node type: 0 = APPN network node,
1 = APPN end node or Unknown node type,
2 = LEN end node [0]? 0
High performance routing: (Y)es (N)o [Y]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>
Figure 129. Adding the Port and the Link to the WAN Interface of the 2210
1 APPN port name for the PPP link on the 2210, which is needed when we define
the station name for that link (2)
2 Station name for the PPP link
Now the configuration of our test environment for an APPN connection between
the host and the 2216 via the LSA interface is complete. After we reload the 2216
and the 2210 with their new configurations, the host connection can be monitored
as described in 4.5.4.1, “Monitoring ESCON Interface” on page 125.
For the monitoring of the LSA interface in general, please see 4.5.4.2,
“Monitoring ESCON LSA Interface (APPN)” on page 126.
124 IBM 2216 and Network Utility Host Channel Connections

4.5.4 2216 Monitoring
4.5.4.1 Monitoring ESCON Interface
The monitoring command is available from the GWCON prompt which you get via
the T5 process. Access the talk 5 commands that show the status of channel
resources hierarchically by following these steps:
• From the * prompt, type talk 5 and press Enter to reach the + prompt.
• From the + prompt, type int and press Enter and note the logical interface
number for the physical ESCON or PCA interface you are interested in. The
physical interface is commonly called the base net, and may have a number of
LSA, LCS, or MPC+ virtual interfaces defined on top of it. The base net and all
virtual interfaces each have a different logical interface number (see Figure
130 on page 125).
2216 *t5
2216 +int
Self-Test Self-Test Maintenance
Net Net' Interface Slot-Port Passed Failed Failed
0 0 TKR/0 Slot: 1 Port: 1 1 0 0
1 1 PPP/0 Slot: 8 Port: 0 1 0 0
2 2 ESCON/0 Slot: 3 Port: 1 1 0 0
3 2 LSA/0 Slot: 0 Port: 0 1 2 0
4 4 TKR/1 Slot: 0 Port: 0 1 0 0
Figure 130. Interface List via GWCON
• From the + prompt, type net base n number and press Enter to reach the
ESCON or PCA Console subprocess. The command prompt changes to
ESCON> or PCA> as appropriate (see Figure 131).
2216 +net 2
ESCON Base Console
2216 ESCON>
Figure 131. Change to the ESCON Base Net Prompt
At these prompts, you can use the li nets command to see the current state of
every virtual interface (LSA, LCS, MPC+) using this base net. You can also type
li sub to view the currently running subchannel configuration for this base net
(see Figure 132 on page 126).
Link Services Architecture 125

2216 ESCON>list ?
SUbchannels
NEts
2216 ESCON>list sub
The following subchannels are defined:
1 Local address: 00 Device address: 04 CU Logical Address: 01
Link: CC LPAR: 01
2 Type: LSA
The following lantypes/lannums are using this subchannel:
3 LAN type: Token-Ring/802.5 LAN number: 0 4
2216 ESCON>li net
Net: 3 Type: LSA LAN Type: Token-Ring/802.5 LAN Number: 0
Net state: Up 5
Figure 132. List of Nets and Subchannels from ESCON Base Net Prompt
1 Local Address The subchannel address index used internally by the device
2 Type Type of virtual interface: LCS, LSA, or MPC+
3 LAN Type LAN type, either Token-Ring/802.5, Ethernet/802.3,
Ethernet/V2, Ethernet or FDDI
4 LAN Number Interface number of the LAN
5 Net State State of the network: Up, Down, Disabled, Not Present, HW
Mismatch, or Testing. Up indicates that the link is up.
4.5.4.2 Monitoring ESCON LSA Interface (APPN)
From the base net ESCON> or PCA> prompt or directly from the + prompt, type
net virtual net number and press Enter to see more detail on a particular virtual
interface that uses this base net. The command prompt changes to LSA>, LCS>,
or MPC+>, depending on the type of the virtual interface you select.
Each of these prompts supports a List command to show configuration and
current status information relevant to the virtual interface type (see Figure 133 on
page 126).
2216 +net 3
LSA Console
2216 LSA>list ?
ADapter
SAp
LInk station
Figure 133. List of Subcommands for the LSA Interface
The following figures reflect these listing commands one by one regarding our
test environment (see Figure 112 on page 113).
The li adapter command lists virtual adapters for LSA (Figure 134 on page 127).
126 IBM 2216 and Network Utility Host Channel Connections

2216 LSA>li adapter
LSA Virtual Adapter
LSA Information for Net 3
--- ----------- --- --- --
LAN Type: Token-Ring/802.5 LAN Number: 0
MAC Address: 40002216000A
Downstream network: Loopback - Net 3
Status: Host connected
#SAPs Open: 1 1 #Link Stations Open: 1 2
Maximum frame size: 2052 (0x804) 3
Host User ID 4 Subchannel 5
------------ ----------
00000000 0
1 host user(s)
Figure 134. List of Virtual Adapter
1 #SAPs Open Number of SAPs opened by VTAM on this LSA
interface
2 #Link Stations Open Number of link stations open for all SAPs on
this LSA interface
3 Maximum Frame Size Maximum frame size supported over this LSA
interface
4 Host User ID A unique ID generated by VTAM to identify the host
user on a given subchannel
5 Subchannel The local subchannel being used by this host user.
The li sap command lists service access points (SAPs) for LSA (see Figure 135)
2216 LSA>li sap
SAP Provider User Max Link Open Link
Number SAP ID SAP ID Stations Stations
1 2 3 4 5
------ -------- -------- -------- ---------
4 00000000 00000001 10 1
1 SAPs currently open
Figure 135. List SAP for LSA
1 SAP Number Identifies the SAP to LLC
2 Provider SAP ID A unique ID generated by VTAM to identify this SAP
3 User SAP ID A unique ID generated by a device to identify this SAP
4 Max Link Stations Maximum number of link stations VTAM can open on
this SAP
5 Open Link Stations Number of link stations currently open on this SAP
The link command lists link information for LSA (Figure 136)
Link Services Architecture 127

2216 LSA>li link
Please specify a SAP number (0-236): [4]?
Link Stations on SAP 4
1 2 3 4 5 6
Station Destination Destination Link Frames Frames
ID MAC Address SAP Number Status Sent Received
------- ----------- ----------- ------ ------ --------
00000001 40002216000B 4 Connected 101 138
1 link station(s) open on SAP 4
Figure 136. List Link Information for LSA
1 Station ID A unique ID generated by a device to identify this
link station
2 Destination MAC Address MAC address of the remote LLC link station
3 Destination SAP Number SAP value of the remote LLC link station
4 Link Status Current status of the LLC connection
5 Frames Sent Number of packets sent to VTAM for this link
station
6 Frames Received Number of packets received from VTAM for this
link station
4.5.4.3 Monitoring APPN (LSA)
Use the following procedure to access the APPN monitoring commands. This
process gives you access to an APPN’s monitoring process.
At the OPCON prompt, enter talk 5. After you enter the talk 5 command, the
GWCON prompt (+) displays on the terminal. If the prompt does not appear when
you first enter the configuration, press Return again. After you get the GWCON
prompt (+) type protocol APPN.
Use the list command to display information about the APPN configuration. Besides
the list command, there are more monitoring commands available for APPN (APING,
DUMP, MEMORY, RESTART, STOP, TN3270, TRANSMIT) to get more detailed information about
specific items. We will focus on only some of the list commands here. For more
information about APPN monitoring refer to Nways Multiprotocol Access Services
Protocol Configuration and Monitoring Reference Vol. 2 Version 3.2, SC30-3885.
The following list commands are based on our test environment, which is shown
again in Figure 137 on page 129.
128 IBM 2216 and Network Utility Host Channel Connections

usibmra.ra03m
TR
RA03
LPAR 1
LAN
usibmra.valencia
HPR Support=NO
Figure 137. Overview of Test Environment
The list port command displays a summary table of all ports (Figure 138 on
page 129).
Figure 138. List of Ports in APPN
The list link command displays a summary table of all links (Figure 139).
Figure 139. List of Links in APPN
RA28
LPAR 2
ESCD
LSA
-----
CC
C9
WAN
RA39
LPAR 4
2216
S/390
usibmra.nn2216
2210 TR
usibmra.nn2210
2216 *t 5
2216 +p appn
2216 APPN >li port
Intf Name DLC Type HPR State
============================================================
0 T00000 IBMTRNET TRUE ACT_PORT
1 PPP00001 PPP TRUE ACT_PORT
4 T00004 IBMTRNET TRUE ACT_PORT
usibmra.mainz
HPR Support=YES
2216 APPN >li link
Name Port Name Intf Adj CP Name Type HPR State
========================================================================
TO2210 PPP00001 1 USIBMRA.NN2210 NN ACTIVE ACT_LS
TOVTAM T00004 4 USIBMRA.RA03M NN ACTIVE ACT_LS
@@6 T00000 0 USIBMRA.VALENCIA EN INACTIVE ACT_LS
Link Services Architecture 129

In Figure 139 you see also a LINK for the token-ring interface even though we
don’t define one. This link is dynamically added, marked by the @@ sign. One of
the PCs (with a CP name of VALENCIA) is connected (as EN) on this link with
HPR inactive.
The list cp command displays a table of all CP sessions (Figure 140).
2216 APPN >li cp
CP Name Type Status Connwinner ID Conloser ID
========================================================================
USIBMRA.VALENCIA EN Active 365A9438 365A9434
USIBMRA.RA03M NN Active 365A9368 365A936A
USIBMRA.NN2210 NN Active 365A92D8 365A92D7
Figure 140. List of CP Sessions in APPN
The list appc command displays information about APPC sessions (Figure 141).
2216 APPN >li appc
LU Name Mode Type FSM
=====================================
USIBMRA.NN2210 CPSVCMG Pri ACT
USIBMRA.NN2210 CPSVCMG Sec ACT
USIBMRA.RA03M CPSVCMG Pri ACT
USIBMRA.RA03M CPSVCMG Sec ACT
USIBMRA.VALENCIA CPSVCMG Sec ACT
USIBMRA.VALENCIA CPSVCMG Pri ACT
USIBMRA.MAINZ SNASVCMG Sec ACT
USIBMRA.MAINZ #INTER Sec ACT
Figure 141. List of APPC Sessions
The list rtp command displays a table of all RTP connections (Figure 142).
2216 APPN >li rtp
RTP PARTNER TABLE:
Remote Partner Name Remote Boundary Name TG Number
======================================================
USIBMRA.MAINZ USIBMRA.MAINZ -1
RTP CONNECTION TABLE:
TCID CP Name ISR APPC Pathswitch Alive COS TPF TG Number
=================================================================================
1E9F358 USIBMRA.NN2210 0 1 180 180 CPSVCMG 21
1EA9888 USIBMRA.NN2210 0 1 180 180 CPSVCMG 21
1ED0778 USIBMRA.NN2210 0 0 0 180 RSETUP 21
1E9F7E8 USIBMRA.RA03M 1 0 180 180 SNASVCMG 0
1ED02E8 USIBMRA.RA03M 1 0 180 180 #INTER 0
1EB6BE8 USIBMRA.MAINZ 0 1 180 61 SNASVCMG 21
1EB5E38 USIBMRA.MAINZ 0 1 180 61 #INTER 21
Figure 142. RTP Connection Table
130 IBM 2216 and Network Utility Host Channel Connections

Chapter 5. LAN Channel Station
5.1 2216 LCS Support
LCS is a channel protocol supported by TCP/IP host applications on the host.
Each application defines a consecutive pair of subchannels, one for the TCP/IP to
read from the channel and another one for TCP/IP to write to the channel. The
LCS interface allows LAN MAC frames to be transported over the channel, and
provides a common interface to activate, deactivate, and query the LAN
interfaces. Each MAC frame has a header that identifies the virtual LAN adapter
destination of the frame.
The host channel interface packages control and data frames in blocks of up to
32 KB. LCS blocks consist of one or more contiguous frames, each with a header
which identifies the destination device by its LAN type and LAN number. Then,
the block is deblocked at the destination, which means that the block is received
and the individual frames are forwarded to the device driver.
LCS uses an asynchronous protocol for transferring frames between the two
ends, in a way that the control unit cannot send a block of data until the channel
has issued the READ command. Once the channel has read the data from the
control unit, it sends the data back to the control unit to let it know that the
process has been completed. When the control unit does not have data to send, it
sends keepalive messages to let the channel know that it is operational. Control
unit keepalives are acknowledged. Channel writes are not acknowledged by the
control unit.
When an LCS interface is added to the 2216, a LAN is created inside the router.
There are two stations attached to this LAN, the host and the LCS interface of the
2216. A MAC address is not configured but obtained from the NET that is pointed
to by the LCS interface.
The fact that the 2216 emulates a LAN is only intended to maintain the existing
host interfaces of the 3172 Interconnect Controller to eliminate host support
changes. In the 3172 each subchannel was connected to one LAN device driver.
In the 2216 instead of each subchannel being connected to one or more real LAN
adapters, all of the subchannels are connected to the base net handler, which is
in turn connected to one or more virtual net handlers supporting one of the three
channel protocols (LCS/LSA/MPC). This virtual net handler sends and receives
data via one of the protocol applications (LLC/IP/APPN), which sends data to
another net handler representing a network connection. So, in the case of the
2216 a real LAN adapter may or may not exist.
At this point the 2216 can perform three different functions: LCS routing, LCS
bridging and LCS 3172 emulation, depending on whether the 2216 is bridging or
routing IP frames between the LCS interface and other interfaces of the router or
it is simply passing the frames between the LCS 3172 emulation interface and the
LAN interfaces. The TCP/IP support provided by the 2216 may be:
1. LCS routing. In this case, an IP address will have to be configured on the LCS
interface. This IP address must be different from any other IP address
configured on any other interface of the 2216.
© Copyright IBM Corp. 1998 131

2. LCS bridging. The 2216 is configured as a bridge. In this case the LCS
bridging and the LAN interfaces do not have any IP address associated with
them. All IP and ARP frames pass through the router unmodified. They are
bridged between the LCS interface and other bridging ports in the router.
3. LCS 3172 emulation. The 2216 appears like a 3172, with the advantage of
being easier to migrate from 3172 to 2216. Each LCS interface is associated
with a single LAN interface and vice versa. The 2216 LCS 3172 emulation and
LAN interfaces have no IP address associated with them.
5.1.1 LCS Routing
The 2216 LAN interfaces are configured with a MAC address and an IP address.
The 2216 LCS interface is configured with a subchannel pair of LAN type/LAN
number, a MAC address and an IP address. This IP address must be in the same
subnet as the host and must be unique in the 2216. This means that each 2216
interface must be in a unique subnet.
The TCP/IP host is configured with a single subchannel pair of LAN type/LAN
number and IP address for each LCS interface.
When TCP/IP is started the host is notified with the MAC address of the LCS
interface. Then it can send MAC frames over the subchannel pair to the 2216.
The 2216 uses the LAN type and LAN number in the MAC header for directing the
frames to the right LCS interface. The LCS interface strips off the MAC header
and passes the IP packet to the IP forwarder, which routes the frame according to
its routing table to the right outgoing interface. If a frame gets to the router and it
is addressed for the host, the IP forwarder passes the frame to the LCS interface,
which builds the MAC header and sends the frame to the TCP/IP host.
So, the traffic from/to the host can be routed to any interface in the router.
Multicast frames are broadcast to all the interfaces.
This type of support may be used if:
• The 2216 is going to be used as an IP router or Web Server Cache
• We want to assign each channel-attached TCP/IP host to its own subnet
• We want each channel-attached host to have access to all 2216 LANs
• We want multiple TCP/IP hosts to have access to the same LAN interface
• We want access to any IP-capable downstream network
An LCS routing interface may not be configured for bridging.
Figure 143 on page 133 shows the appearance of this type of LCS support.
Based on the appearance it is easy to know what parameters need to be
configured in the 2216 LCS routing interface.
Those parameters are:
MAC address: When the LCS interface is added a LAN is created inside the
router. The two stations attached to this LAN are the host and the LCS interface
of the 2216. So, a MAC address will have to be assigned to the LCS interface.
LAN type: This parameter specifies the LAN type for the LCS interface. It can be
either token-ring, Ethernet or FDDI.
132 IBM 2216 and Network Utility Host Channel Connections

Subchannels: LCS uses two subchannels between the 2216 and the host, one
for reading and another one for writing.
Then the IP protocol has to be configured.
LAN
interface
HOST
Base Net Handler
LCS
IP Code
WAN
interface
Figure 143. LCS Routing Support Appearance
5.1.2 LCS Bridging
The 2216 LAN interfaces are configured with a MAC address and bridge port.
The 2216 LCS interface is configured with a subchannel pair of LAN type/LAN
number, MAC address and bridge port.
2216
Logical
Appearance
host
LCS
IP address
IP routing
code
Rest of IP
Network
The TCP/IP host is configured with a single subchannel pair, LAN type/LAN
number and IP address for each LCS interface.
The TCP/IP host is notified of the LCS MAC address when TCP/IP is started.
TCP/IP sends MAC frames over a single subchannel pair to the 2216, which uses
the LAN type/LAN number in the LCS header to direct the frames to the correct
LCS interface. The LCS interface passes the frame to the bridging function, which
bridges the frame to the appropriate LAN interface, converting the MAC format if
appropriate. Inbound frames received from the LAN interface are passed to the
bridging function, which bridges the MAC frame to the appropriate LCS interface.
Traffic from any LCS can be bridged to any LAN interface and vice versa.
Multicast frames are bridged to all the interfaces.
The 2216 LCS bridging and LAN interfaces have no IP addresses associated with
them. All IP and ARP frames pass through the 2216 unmodified. TCP/IP hosts
can be in the same or different subnets, based on the router topology of the IP
network.
2216 interfaces cannot be configured for bridging and routing at the same time. A
TCP/IP host may perform bridging and routing concurrently on the same ESCON
LAN Channel Station 133

or parallel channel to the same 2216, provided that separate LCS bridging and
LCS routing interfaces are defined and they use separate subchannel pairs.
This type of support might be used in the following situations:
• When we want to use the 2216 as a bridge
• When we want to have multiple channel-attached TCP/IP hosts on the same
subnet
• When we want each channel-attached TCP/IP host to have access to all 2216
LANs
• When we want multiple TCP/IP hosts to have access to the same LAN
interface
• When we want access to downstream bridges
The appearance of this type of support can be seen in Figure 144 on page 134.
LAN interface
bridging port
HOST
Base Net Handler
LCS
Bridging Code
Figure 144. LCS Bridging Support Appearance
Based on Figure 144, the parameters to be configured on the LCS bridging
interface are:
MAC address: When the LCS interface is added a LAN is created inside the
router. The two stations attached to this LAN are the host and the LCS interface
of the 2216. So, a MAC address will have to be assigned to the LCS interface.
LAN type: This parameter specifies the LAN type for the LCS interface. It can be
either token-ring, Ethernet or FDDI.
Subchannels: LCS uses two subchannels between the 2216 and the host, one
for reading and another one for writing.
134 IBM 2216 and Network Utility Host Channel Connections
WAN interface
bridging port
2216
Logical
Appearance
host
LCS
IP address
Bridging
code
Rest of the
Network

Then the Adaptive Source Routing Transparent (ASRT) bridge protocol has to be
configured.
5.1.3 LCS 3172 Emulation Support
The 2216 LAN interface is configured with a MAC address. The 2216 LCS
interface is configured with a subchannel pair and downstream net number. The
LAN type and LAN number are calculated based on the LAN type of the
downstream net. No MAC address is configured on that LCS interface. That is
obtained from the LAN pointed to by that LCS interface.
The TCP/IP host is configured with a single subchannel pair, LAN type/LAN
number, and IP address and subnet for each LCS interface.
The TCP/IP host is notified of the LAN MAC address when TCP/IP is started.
TCP/IP sends MAC frames over a single subchannel pair to the 2216, which uses
the LAN type/LAN number in the LCS header to direct frames to the correct LCS
interface. The LCS interface passes the MAC frame directly to the appropriate
LAN interface, which sends the frame out. All incoming IP frames are passed
directly to the appropriate LCS interface which sends the frames to the TCP/IP
host.
Each LCS interface is associated with a single LAN interface, and vice versa. No
bridging or routing of IP traffic is possible with LCS 3172 emulation interfaces.
Multicast frames received by either interface are passed only to the
corresponding 3172 emulation interface.
The LCS 3172 emulation and LAN interfaces have no IP addresses associated
with them. All IP and ARP frames are passed through the 2216 unmodified.
TCP/IP hosts may be in the same or different subnets, based on the topology of
the IP network.
LCS 3172 emulation interfaces cannot be configured for bridging or IP routing.
3172 emulation LAN interfaces can be configured for bridging or routing of non-IP
protocols only. A TCP/IP host can perform LCS bridging, routing and 3172
emulation concurrently on the same ESCON or parallel channel to the same
2216, provided that separate LCS interfaces are defined and separate
subchannel pairs are used.
LCS 3172 emulation will be used when:
• We want to use the 2216 as a drop-in 3172 replacement.
• We want to have multiple channel-attached hosts on the same subnet.
• We want each channel-attached TCP/IP host to have access to all LANs.
• We only need access to token-ring, Ethernet, FDDI or ATM LE networks.
• We want to dedicate a LAN interface to a single TCP/IP host.
The appearance of this type of support is seen in Figure 145 on page 136.
LAN Channel Station 135

Token ring
network
Figure 145. LCS 3172 Emulation Support Appearance
Based on Figure 145 on page 136 the following have to be configured on the LCS
3172 emulation interface:
Enable 3172 emulation: Enabling this mode of operation will allow the 2216 to
appear as a 3172. In this way, the 2216 does no bridging or routing of IP traffic
between interfaces. All IP traffic received from one LCS interface goes to the
associated downstream LAN interface and vice versa.
net: By using this command we will associate a LAN interface in the 2216 with an
LCS interface.
Subchannels: LCS uses two subchannels, one for reading and one for writing.
Neither IP nor ASRT has to be configured.
5.2 2216 LCS vs Host Parameter Relationships
LCS
Ethernet
network
Before we can attach a 2216 to an ESCON channel, the host must be configured
correctly. The following steps are required to define a 2216 connection to the
host:
1. Define the 2216 to the host channel subsystem using either the host I/O
configuration program (IOCP) or hardware configuration definition (HCD)
program.
The IOCP macros needed for defining the 2216 to the host are:
• RESOURCE Statement: Identifies logical partitions
• CHPID Statement: Identifies type of channel connection and who uses it
• CNTLUNIT and IODEVICE Statements: Identify the 2216 connection to the
host.
2. Define the 2216 control unit to the host operating system.
3. Define the 2216 and configuration to the host program (TCP/IP).
TCP/IP is configured on the host by modifying the TCP/IP profile. Each
channel connection requires:
136 IBM 2216 and Network Utility Host Channel Connections
HOST
Base Net Handler
LCS LCS LCS
FDDI
network
ATM LE
network
2216
Logical
appearance
host

• One LINK and one DEVICE statement in the TCP/IP profile. The LINK
statement identifies which LCS interfaces on the 2216 are being used on a
given subchannel pair. On the other hand, the DEVICE statement defines
the subchannel pair being used by TCP/IP.
• An entry in the HOME statement. This statement specifies the IP
address(es) of the host TCP/IP stack.
• Entries in the GATEWAY statement for the link to be used (if ROUTED is
not being used).
• A START command for the device. This command causes the specified
subchannels to be started.
The relationship between the definition on the host and in the 2216 can be seen
in the following figure:
LAN Channel Station 137

Host Channel Definitions
RESOURCE PART=((A1,1))
S/390 TCP/IP Profile -D2216
CHPID PATH=((2C),TYPE=CNC,PART=(A1),SWITCH=E1)
Figure 146. 2216 LCS Host Parameter Relationship
CNTLUNIT CUNMBR=0280,PATH=(2C),CUADD=1,
DEVICE D2216 LCS 282
LINK LD2216 IBMTR 0 D2216
LPAR A
CHPID=2C
138 IBM 2216 and Network Utility Host Channel Connections
UNITADD=((00,032)),LINK=(C9),UNIT=3172
HOME 192.168.125.1 LD2216
IODEVICE UNIT=3172,ADDRESS=(280,032),
CUNMBR=(0280)
; orouted Routing Information
; Link Maxmtu Metric Subnet Mask Dest Addr
BSDROUITNGPARMS false
LD2216 4000 0 255.255.255.0 0
ENDBSDROUTING PARMS
START D2216
192.168.125.1
CC
ESCON
Director E1
C9
PC IP definitions
2216
LCS Routing:
PC IP@ and Host IP@ on different subnet
LCS Bridging and LCS Passthru:
PC IP@ and Host IP@ on same subnet
ESCON LCS Definitions:
Token
Ring
LPAR 1
CU 1
Device 02
Link CC
LAN number 0 (use talk6 "list all" from the
ESCON config prompt to determine) NOTE: All Subnet Masks = 255.255.255.0

Note
5.3 LCS Configuration Examples
In Figure 146 on page 138, the IP address of the PC will be in the same or
different subnet from the host LCS IP address depending on the type of support
the 2216 is providing. For LCS routing, the subnet on the PC will be different
from the subnet on the host and the LCS and token-ring interfaces in the 2216
will have to be assigned IP addresses on the host and PC subnets respectively.
If LCS bridging or LCS 3172 emulation is being used the PC and the host will
be in the same subnet and the LCS and LAN interface in the 2216 will not be
assigned IP addresses.
The following steps must be followed in order to configure LCS support on the
2216:
1. Add the physical interface.
2. Add and configure the LCS handler.
3. Configure the subchannel pair.
4. Configure IP or ASRT protocol if the 2216 is supporting LCS routing or LCS
bridging.
5.3.1 Host Definitions
Before we can attach the 2216 to an ESCON channel, the host system must be
configured correctly. This will require adding some definitions in IOCP, the host
operating subsystem and the TCP/IP profile as seen in 5.2, “2216 LCS vs Host
Parameter Relationships” on page 136.
5.3.1.1 IOCP and MVS Operating System Definitions
These definitions can be seen in Figure 147 on page 140. These definitions are
common to all the channel protocols and have been used for the LCS, LSA and
MPC+ scenarios.
The CNTLUNIT statement defines the path from the host to the 2216 and is used
for the IOCP definitions.
The 2216 must be defined to an IBM Multiple Virtual Storage/Extended
Architecture (MVS/XA) or MVS/ESA operating system. This definition is
accomplished by updating the MVS control program with an entry for the 2216 in
the IODEVICE macro.
LAN Channel Station 139

RESOURCE PARTITION=((A1,1) 1 ,(A2,2),(A3,3),(A4,4),(A5,5),(C1,6), *
(C2,7))
CHPID PATH=(2C),SHARED, *
PARTITION=((A1,A2,A3,A4),(A1,A2,A3,A4,A5)),SWITCH=E1, *
TYPE=CNC
CNTLUNIT CUNUMBR=0280,PATH=(2C),UNITADD=((00,032)) 2 ,LINK=(C9), *
CUADD=1 3 ,UNIT=3172
CNTLUNIT CUNUMBR=02A0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=2,UNIT=3172
CNTLUNIT CUNUMBR=02C0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=4,UNIT=3172
IODEVICE ADDRESS=(280,032),UNITADD=00,CUNUMBR=(0280), *
PARTITION=(A1),UNIT=3172
IODEVICE ADDRESS=(2A0,032),UNITADD=00,CUNUMBR=(02A0), *
PARTITION=(A2),UNIT=3172
IODEVICE ADDRESS=(2C0,032),UNITADD=00,CUNUMBR=(02C0), *
PARTITION=(A4),UNIT=3172
Figure 147. LCS: IOCP and MVS Definitions
1 In this scenario we will connect to LPAR 1.
2 UNITADD defines the range of addresses reserved for this control unit. The first
number is the hex of the first subchannel assigned to this control unit. The second
number is the decimal number of subchannels being assigned to this control unit.
The parameter device address defined in the 2216 must be in this range of
addresses. In this scenario we will use device address 04.
3 This value identifies the control unit address of the 2216. For the 2216, each
LPAR on a given CHPID must have a unique CUADD value. This value must
match the control unit parameter specified in the 2216.
5.3.1.2 TCP/IP Definitions for MVS
TCP/IP is configured on the host by modifying the TCP/IP profile. Following is the
TCP/IP profile that has been used in this scenario:
;******************************** Top of Data ***********************
; Member TCP.TCPPARMS(PROF03A)
; ******************************************************************
; For more information about this file, see "Configuring the TCPIP
; Address Space" and "Configuring the Telnet Server" in the
; Configuration Guide.
; ******************************************************************
; You can specify DATASETPREFIX in the PROFILE.TCPIP and
; TCPIP.DATA data sets. If this statement is used in a profile or
; configuration data set that is allocated to a client or a server, then
; that client or server dynamically allocates additional required data
; sets using the value specified for DATASETPREFIX as the data set name
; prefix. The DATASETPREFIX parameter can be up to 26 characters long,
; and the parameter must NOT end with a period.
;
; For more information please see "Understanding TCP/IP Data Set
; Names" in the Customization and Administration Guide.
;
DATASETPREFIX TCP
;
140 IBM 2216 and Network Utility Host Channel Connections

;
TCPCONFIG
; INTerval 5 ; In minutes - Keep alive packet 0-35791
; RESTRICTLowports
UNRESTRICTLowports
; TCPSENDBfrsize 16384 ; Range is 256-256K - Default is 16K
; TCPRCVBufrsize 16384 ; Range is 256-256K - Default is 16K
TCPSENDBfrsize 65536 ; Range is 256-256K - Default is 16K
TCPRCVBufrsize 65536 ; Range is 256-256K - Default is 16K
SENDGARBAGE FALSE ; Packet contains no data
; SENDGARBAGE TRUE ; Packet contains 1 byte of random data
UDPCONFIG
; RESTRICTLowports
UNRESTRICTLowports
UDPCHKsum ; Do checksum
; NOUDPCHKsum ; Don't do checksum
UDPSENDBfrsize 16384 ; Range is ???-???K (Default is 16K)
UDPRCVBufrsize 16384 ; Range is ???-???K (Default is 16K)
; UDPQueuelimit ; Limit inbound UDP Queue ????
; NOUDPQueuelimit ; Do not Limit inbound UDP Queue ????
;
; *********************************************************
IPCONFig
ARPTO 1200 ; In seconds
;CLAWUSEDoublenop ; Applies only to first-level MVS systems
DATAGRamfwd
;NODATAGRamfwd
;FIREWALL
;NOSOURCEVIPA
SOURCEVIPA
;NOVARSUBNETTING ; For RIPV1
VARSUBNETTING ; For RIPV2
;NOSYSPLEXRouting
SYSPLEXRouting
IGNORERedirect
REASSEMBLytimeout 15 ; In seconds
STOPONclawerror
TTL 60 ; In seconds, but actually Hop count
; ----------------------------------------------------------------------
SACONFIG
OSASF 760
ENABLED
ATMENABLED
SETSENABLED
; SETSDISABLED
; ----------------------------------------------------------------------
;
; AUTOLOG the following servers.
;
AUTOLOG 1
; T03AFTP JOBNAME T03AFTP1 ; FTP Server
; T03DNS JOBNAME T03DNS1 ; Domain Name Server
; T03FTPSV
; FTPD JOBNAME FTPD1 ; FTP Server
LAN Channel Station 141

; T03ALPD ; LPD Server
; T03AT25A ; SNALINK
; T03NPFQM ; NPF queue manager
; NCPROUT ; NCPROUTE Server
; PORTMAP ; Portmap Server
T03AROU ; RouteD Server
; RXSERVE ; Remote Execution Server
; SMTP ; SMTP Server
; T03SNMPD ; SNMP Agent Server
; SNMPQE ; SNMP Client
; TCPIPX25 ; X25 Server
; WEBQM ; DOMINO
ENDAUTOLOG
;
; ----------------------------------------------------------------------
;
; Reserve ports for the following servers.
;
; NOTES:
;
; A port that is not reserved in this list can be used by any user.
; If you have TCP/IP hosts in your network that reserve ports
; in the range 1-1023 for privileged applications, you should
; reserve them here to prevent users from using them.
;
; The port values below are from RFC 1060, "Assigned Numbers."
;
PORT
7 UDP MISCSERV ; Miscellaneous Server
7 TCP MISCSERV
9 UDP MISCSERV
9 TCP MISCSERV
19 UDP MISCSERV
19 TCP MISCSERV
; 20 TCP T03FTP1 NOAUTOLOG ; FTP Server
20 TCP OMVS NOAUTOLOG ; FTP Server
21 TCP T03AFTP1 ; FTP Server
; 23 TCP INTCLIEN ; Telnet Server
25 TCP SMTP ; SMTP Server
53 TCP T03DNS ; Domain Name Server - Parent Process
53 UDP T03DNS ; Domain Name Server - Parent Process
80 TCP WEBQM ; Domino webserver
111 TCP OMVS ; Portmap Server
111 UDP OMVS ; Portmap Server
135 UDP LLBD ; NCS Location Broker
161 UDP T03SNMPD ; SNMP Agent
162 UDP T03SNMPQ ; SNMP Query Engine
443 TCP OMVS ; Domino webserver
512 TCP T03AREX ; Remote Execution Server
514 TCP T03AREX ; Remote Execution Server
515 TCP T03ALPD ; LPD Server
520 UDP T03AROU ; RouteD Server
580 UDP NCPROUT ; NCPROUTE Server
750 TCP MVSKERB ; Kerberos
750 UDP MVSKERB ; Kerberos
751 TCP ADM@SRV ; Kerberos Admin Server
142 IBM 2216 and Network Utility Host Channel Connections

751 UDP ADM@SRV ; Kerberos Admin Server
760 UDP IOASNMP ; osa/sf
760 TCP IOASNMP ; osa/sf
20000 TCP RA03C ; CICS Sockets
20001 TCP RA03C ; CICS Sockets Server
3005 TCP T03AHWS ; IMS Sockets (OTMA)
3012 TCP T03AIMSL ; IMS Sockets (Listener)
;
; -----------------------------------------------------------------------
;
; Hardware definitions:
;
; NOTE: To use these device and link statements, update the statements
; to reflect your installation configuration and remove the semicolon
;
; *********************************************************
; CTC Definition
; CTC attach to T18 - Rel Adapter 1 - Device # C14-C15
; IOBuf must match at both sides (could now cfg 64K size)
; *********************************************************
; DEVICE ctc25 CTC c14 IOBUFFERSIZE 32768 autorestart
; LINK lctc25 CTC 1 ctc25
;
; *********************************************************
; VIPA Definition (For V2R5)
; *********************************************************
DEVICE VIPA3A VIRTUAL 0
LINK VIPA3A VIRTUAL 0 VIPA3A
;
;
; *********************************************************
; netfinity tcp/ip passthru
; *********************************************************
;
;
; *********************************************************
; SAMEHOST Definition (For V2R5)
; *********************************************************
DEVICE IUTSAMEH MPCPTP
LINK IUTSAMEH MPCPTP IUTSAMEH
;
; *********************************************************
; LCS Definition
; osa ch 78 Device # 2060-2061
; *********************************************************
DEVICE TR1 LCS 2060 autorestart
LINK TR1 IBMTR 0 TR1
;
; *********************************************************
; LCS Definition to test DHCP/DDNS
; osa ch 24 Device # 2020-2021
; *********************************************************
DEVICE TR2 LCS 2020 autorestart
LINK TR2 IBMTR 0 TR2
;
; *********************************************************
; LCS Definition
LAN Channel Station 143

; 3172 T/R attach - Rel Adapter 0 - Device # 320-321
; *********************************************************
DEVICE icp1 LCS 320 autorestart
LINK icp1 IBMTR 0 icp1
; DEVICE icp2 LCS 324 autorestart
; LINK icp2 IBMTR 0 icp2
DEVICE icp11 LCS 328 autorestart ; for VIPA on LAN
LINK icp11 IBMTR 0 icp11
; *********************************************************
; LCS Definition
; osa 00 fddi - Device # 2080-2081
; *********************************************************
DEVICE FDDI1 LCS 2080 AUTORESTART
LINK FDDI1 FDDI 0 FDDI1
;
; *********************************************************
; CLAW Definition
; 3172 T/R attach - Rel Adapter 0 - Device # 344-345
; Second level MVS under VM should be defined as V=R
; *********************************************************
; DEVICE iccp CLAW 350 HOST PSCA NONE 20 20 4096 4096 autorestart
; LINK iccp IP 0 iccp
;
; *********************************************************
; LCS Definition
; 2216 T/R attach - Rel Adapter 0 - Device # 282-283
; *********************************************************
DEVICE D2216 LCS 282 autorestart 1a
LINK LD2216 IBMTR 0 D2216 1b
;
; ****************************************************************
; * 3172-3 2nd floor *
; * *
;DEVICE DEVEN1 LCS 302 **********************
;LINK EN1 802.3 0 DEVEN1
;DEVICE DEVEN1 LCS 2026
;LINK EN1 ETHEROR802.3 1 DEVEN1
;DEVICE EN1 LCS 2026
;LINK EN1 ETHEROR802.3 1 EN1
;DEVICE EN2 LCS 2064
;LINK EN2 ETHEROR802.3 1 EN2
; *********************************************************
; ATM OSA Definition
; *********************************************************
; DEVICE atm ATM
; LINK atm ATM atm
ATMLIS LIS1 192.168.21.0 255.255.255.0
DFLTMTU 8000 INACTVTO 0 MINH 0
CEAGE 300 ARPRETR 6 ARPTO 4 PEAKCR 100
DEVICE OSARA03 ATM PORTNAME OSA58 ENABLEIN NOAUTOR
LINK LATM1 ATM OSARA03 LIS LIS1
;LINK LATM2 ATM OSARA03
;
;
;ATMPVC PVC300 LATM2
;
ATMARPSV ARPSV1 LIS1 SVC 192.168.21.10 NSAP
; 3999999999999900009999010140008210000000
144 IBM 2216 and Network Utility Host Channel Connections

;
; *********************************************************
4970341525543207999998010108005A99814100
; MPC Definition
; APAR PQ04890 for OS/390 R3
; VTAM requirement for TRLE Definition in VTAM VBUILD=TRL
; The DEVICE name must match the TRLE name in VTAM
; The TRLE entry must have MPCLEVEL=HPDT (default)
; Support is for ESCON and 2216 (future)
; *********************************************************
; DEVICE MPC25 MPCPTP AUTORESTART
; LINK MPC25 MPCPTP MPC25
DEVICE M3A2216A MPCPTP AUTORESTART
LINK M3A2216A MPCPTP M3A2216A
; DEVICE M3A2216B MPCPTP AUTORESTART
; LINK M3A2216B MPCPTP M3A2216B
;
; *********************************************************
; XCF Definition
; APAR PQ04890 for OS/390 R3
; APAR OW26845 for VTAM V4.4
; VTAM requirement for TRLE Definition in VTAM VBUILD=TRL
; The DEVICE name must match the host name of VTAM on other side of XCF
; The DEVICE name must match the TRLE name in VTAM
; The TRLE entry can be dynamically created if XCFINIT=YES in VTAM start
; Support is for Cross-system Coupling Facility
; *********************************************************
DEVICE RA28M MPCPTP autorestart
LINK RA28M MPCPTP RA28M
; Conection with RA39 HOST
DEVICE RA39M MPCPTP autorestart
LINK RA39M MPCPTP RA39M
;
;
; LCS1 is a 3172 Model 1 with a Token-Ring and Ethernet adapter.
;
;DEVICE LCS1 LCS BA0
;LINK TR1 IBMTR 0 LCS1
;LINK ETH1 ETHERNET 1 LCS1
;
; LCS2 is a 3172 Model 2 with a FDDI adapter.
;
;DEVICE LCS2 LCS BE0
;LINK FDDI1 FDDI 0 LCS2
;
; SNALU0 is an SNA Link.
;
; DEVICE DEVT25A SNAIUCV SNALINK RAPT25A T03AT25A
; LINK LINKT25A SAMEHOST 0 DEVT25A
;
LAN Channel Station 145

; DEV3746 is an 3746 IP over Channel attachment
; To 3746-9x0 IP Router
; DEVICE A3746 CDLC 901 15 15 4096 4096
; LINK A3746 CDLC 0 A3746
;
;DEVICE B3746 CDLC 902 15 15 4096 4096
;LINK B3746 CDLC 0 B3746
;
; -----------------------------------------------------------------------
;
; HOME Internet (IP) addresses of each link on the host.
;
; NOTE: To use this home statement, update the ipaddress and linknames
; to reflect your installation configuration and remove the semicolon
;
; HOME Internet (IP) addresses of each link on the host.
HOME
192.168.250.3 VIPA3A ; 1st VIPA Link (for V2R5)
9.24.104.231 TR1
192.168.125.1 LD2216 2
192.168.221.7 ICP11 ;for VIPA address on LAN
; 192.168.249.3 T03CTCP ; For SAMEHOST - IUTSAMEH - Connection
192.168.236.3 RA28M ; XCF TO MVS28
192.168.233.3 RA39M ; XCF TO MVS39
192.169.232.41 IUTSAMEH ;
; 9.24.105.126 EN1 ; 9.24.105.0
; 9.24.105.76 EN2 ; 9.24.105.0
; 192.168.230.1 LOOPBACK ; extra address for NDR Cluster
; 192.168.239.3 LINKT25A
; 192.168.202.3 A3746
; 192.168.203.3 B3746
192.168.221.03 icp1
192.168.221.05 icp2
192.168.109.3 iccp
192.168.229.3 fddi1
192.168.21.3 latm1
192.168.100.100 TR2 ; Testing DHCP + DDNS
; 192.168.235.3 MPC25 ; MPC TO MVS25
192.166.236.1 M3A2216A ; MPC TO 2216 A
; 192.168.240.3 M3A2216B ; MPC TO 2216 B
;
;
; ---------------------------------------------------------------------
;
; The PRIMARYINTERFACE statement is used to specify which interface
; is the primary interface.
;
; If PRIMARYINTERFACE is not specified, then the first link in the HOME
; statement is the primary interface, as usual.
;
; NOTE: To use this primary statement, update the and linkname
; to reflect your installation configuration and remove the semicolon
;
; PRIMARYINTERFACE tr1
146 IBM 2216 and Network Utility Host Channel Connections

; PRIMARYINTERFACE ICP1
;
; **********************************************************************-
;
; IP routing information for the host. All static IP routes should
; be added here.
;
; NOTE: To use this GATEWAY statement, update the addresses and links
; to reflect your installation configuration and remove the semicolon
;
; **********************************************************************-
;INCLUDE TCP.TCPPARMS(PR03AGW)
; -----------------------------------------------------------------------
;
; orouted Routing Information
;
; if you are using orouted, comment out the GATEWAY statement and
; update the BSDROUTINGPARMS statement to reflect your installation
; configuration and remove the semicolon
;
;
; **********************************************************************-
INCLUDE TCP.TCPPARMS(PR03ABSD) 3
; **********************************************************************-
;
; Use TRANSLATE to specify the hardware address of a specific IP
; address. See the Customization and Administration Guide for more
; information.
;
;TRANSLATE
; A null translate statement issues the warning message EZZ0323I
;
; -----------------------------------------------------------------------
;
; Turn off all tracing. If tracing is to be used, change the following
; line. To trace the configuration component, for example, change
; the line to ITRACE ON CONFIG 1
;
ITRACE OFF
;
; -----------------------------------------------------------------------
; The ASSORTEDPARMS NOFWD will prevent the forwarding of IP packets
; between different networks. If NOFWD is not specified, IP packets
; will be forwarded between networks when this host is a gateway.
;
; Even though RESTRICTLOWPORTS was specified on TCPCONFIG and UDPCONFIG,
; ASSORTEDPARMS default would have been to reset RESTRICTLOWPORTS to off
; So it is respecified here.
; If the TCPCONFIG and UDPCONFIG followed ASSORTEDPARMS, RESTRICTLOWPORT
; would not have to be done twice.
;
; NOTE: COMMENT out ASSORTEDPARMS for V2R5 to avoid confusion.
LAN Channel Station 147

;ASSORTEDPARMS
; NOFWD
; RESTRICTLOWPORTS
;ENDASSORTEDPARMS
; NOFWD issues the informational message EZZ0334I
; RESTRICTLOWPORTS issues the informational message EZZ0338I
;
; ----------------------------------------------------------------------
;
; the VTAM parameters are in telnet3a
;
INCLUDE TCP.TCPPARMS(TELN03A)
;;;TRUNC 72
; -----------------------------------------------------------------------
;
; Start all the defined devices.
;
; NOTE: To use these START statements, update the device name
; to reflect your installation configuration and remove the semicolon
;
; Start all the defined devices.
;START ctc25
START icp1
;START icp2
START icp11
;START DEVT25A
;START A3746
;START B3746
START iccp
START D2216 4
START TR1
;START TR2
;START MPC25
START OSARA03
START RA28M
START RA39M
;START EN1 ; 3172-3 ICP Ethernet
;START EN2 ; 3172-3 ICP Ethernet
START IUTSAMEH ; SAMEHOST LINK (IUTSAMEH)
START M3A2216A ; mpc to 2216 A
;START M3A2216B ; mpc to 2216 B
START FDDI1 ; osa 00
1 This is the definition of the DEVICE and LINK statements for the LCS
connection on the 2216 ESCON channel adapter.
1a is the DEVICE statement which defines the subchannel pair being used by
TCP/IP.
1b is the LINK statement that identifies which LCS interfaces on the 2216 are
being used on a given subchannel pair. This identification is done by using the
LAN type and LAN number, which are the third and fourth fields of the statement.
In our scenario, the LCS interface configured in the 2216 is LAN type TKR and
LAN number 0. Note that the LAN number is not the net number. The LAN
148 IBM 2216 and Network Utility Host Channel Connections

number can be found entering list all or list nets from the 2216 ESCON config
prompt while the net number can be found by entering list devices from the 2216
config prompt.
2 This parameter specifies the IP address for LCS on the host. This second field
of the sentence specifies the link associated with this IP address, which in our
case is LD2216.
3 We are not using the GATEWAY statement in this scenario but orouted because
dynamic routing is being used instead of static routing. With communications
server for OS/390 Version 2.5, it is possible to have the orouted routing
information in a separate file. The routing information for this host can be seen in
Figure 148 on page 149.
4 This sentence is the starting interface for the 2216. This command causes the
subchannels to be started.
Figure 148 specifies which links on the host are RIP capable. For those links in a
point-to-point network the destination IP address has to be specified. For the
other links in a broadcast or nonbroadcast multiaccess network we do not need to
specify the destination IP address from where the host received RIP
advertisement or where it will send RIP advertisements.
;******************************** Top of Data ***********************
; profile 03a orouted
; ******************************************************************
;
; orouted Routing Information
;
;
; Link Maxmtu Metric Subnet Mask Dest Addr
BSDROUTINGPARMS false
VIPA3A DEFAULTSIZE 0 255.255.255.0 0
IUTSAMEH DEFAULTSIZE 0 255.255.255.0 0
RA28M 32768 0 0 0
RA39M 32768 0 0 192.168.233.39
; EN1 1500 0 255.255.255.0 0
; EN2 1500 0 255.255.255.0 0
; T03CTCP 4096 0 0 192.168.249.4
; A3746 4092 0 0 192.168.202.1
; B3746 4092 0 0 192.168.203.1
ICP1 4000 0 255.255.255.0 0
; ICP2 4000 0 255.255.255.0 0
; LINKT25A 2000 0 0 192.168.239.27
; iccp 4000 0 0 192.168.109.2
LATM1 8000 0 255.255.255.0 0
LD2216 4000 0 255.255.255.0 0 1
TR1 4000 0 255.255.255.0 0
TR2 4000 0 255.255.255.0 0
M3A2216A 2000 0 0 192.166.236.2
; M3A2216B 32768 0 0 192.168.240.13
; MPC25 32768 0 0 192.168.235.25
FDDI1 4000 0 255.255.255.0 0
ENDBSDROUTINGPARMS
Figure 148. LCS: orouted Definitions
LAN Channel Station 149

5.3.2 LCS Routing Support
1 This sentence specifies the routing capabilities for the LCS link. Because the
downstream network is a broadcast network, in our case, a token-ring network,
we do not need to specifiy the IP address of the other end of the link.
5.3.2.1 Network Environment Description
In the network setup used for this scenario the 2216 is attached to the host
through an ESCD. They are connected using the LCS function available on the
2216 ESCON channel adapter.
The 2216 is also attached to a token-ring LAN where there are workstations that
will access to the host. It is connected to a 2210 through a PPP link. On the other
side of the 2210 there is a token-ring LAN with more users.
S/390 TCP/IP Profile
HOME 192.168.125.1
------------------------------
MVS IOCP Definitions
UNITADD=02 & 03
CUADD=1
Figure 149. LCS TCP/IP Routing Scenario
150 IBM 2216 and Network Utility Host Channel Connections
RA03
LPAR 1
16.0.0.0
LAN
RA28
LPAR 2
ESCD
LCS
CC
C9
WAN
RA39
LPAR 4
2216
S/390
192.168.125.2
PPP
192.194.200.0
2210
10.0.0.0

All the masks in this scenario are 255.255.255.0.
5.3.2.2 2216 Configuration
Add the Physical Interfaces
The physical interface will be the ESCON channel adapter. All the other interfaces
that will connect the 2216 to the networks must be added also. The command to
use is add device.
Later, with the list devices command we can see the network numbers for each
one of the devices we have added.
2216 * t6
2216 Config>add dev toke
Device Slot #(1-8) [1]?
Device Port #(1-2) [1]?
Adding Token Ring device in slot 1 port 1 as interface #0
Use "net 0" to configure Token Ring parameters
2216 Config>add dev eia
Device Slot #(1-8) [1]? 8
Device Port #(0-7) [1]? 0
Defaulting Data-link protocol to PPP
Adding EIA-232E/V.24 PPP device in slot 8 port 0 as interface #1
Use "set data-link" command to change the data-link protocol
Use "net 1" to configure EIA-232E/V.24 PPP parameters
2216 Config>add dev escon
Device Slot #(1-8) [1]? 3
Adding ESCON Channel device in slot 3 port 1 as interface #2
Use "net 2" to configure ESCON Channel parameters
2216 Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 EIA-232E/V.24 PPP Slot: 8 Port: 0
Ifc 2 ESCON Channel Slot: 3 Port: 1
Figure 150. LCS Routing: Adding the Physical Adapters to the 2216
Configure the LAN and WAN Interfaces
The token-ring and PPP interfaces have been configured according to our needs,
and reflect the proper ring speed, media etc. used for this scenario.
2216 Config>net 0
Token-Ring interface configuration
2216 TKR config>set phy 40:00:22:16:00:01
2216 TKR config>lis
Token-Ring configuration:
Packet size (INFO field): 2052
Speed: 16 Mb/sec
Media: Unshielded
RIF Aging Timer: 120
Source Routing: Enabled
MAC Address: 400022160001
2216 TKR config>ex
2216 config>
Figure 151. LCS Routing: TKR Configuration
LAN Channel Station 151

The PPP connection between the 2216 and the 2210 is a back-to-back
connection. The 2210 will be the one providing the clocking in this connection.
2216 Config>net 1
Point-to-Point user configuration
2216 PPP 1 Config>li hdlc
Encoding: NRZ
Idle State: Flag
Clocking: External
Cable type: RS-232 DTE
Speed (bps): 19200
Transmit Delay Counter: 0
Lower DTR: Disabled
2216 PPP 1 Config>ex
2216 Config>
Figure 152. LCS Routing: PPP Configuration
Configure the LCS Virtual Interface
By typing the add lcs command from the ESCON config prompt we get the LCS
config prompt which allows us to configure the LCS interface. The parameters
that need to be configured on the 2216 when defining the LCS interface are:
LAN type: Type of LAN connection, Ethernet, token-ring or FDDI. This
parameter is defining the type of virtual LAN that will be created
between the 2216 and the host. This is the frame type that the
host expects to send and receive.
MAC address: MAC address of the virtual net handler, the LCS interface. If the
LAN type is Ethernet, then the MAC address will have to be in
canonical format.
Optional parameters are maxdata, acklen and blktimer. By typing ? you will see
all the parameters that are configurable from this prompt.
2216 Config>net 2
2216 ESCON Config>add lcs
2216 ESCON Add Virtual>?
LANtype
MAC address
MAXdata
BLKtimer
ACKlen
SUBchannels
Exit
2216 ESCON Add Virtual>lan token
2216 ESCON Add Virtual>mac 40:00:22:16:00:0A
2216 ESCON Add Virtual>
Figure 153. LCS Routing: LCS Interface Configuration
Configure the LCS Subchannels
LCS uses a pair of subchannels, one for reading and one for writing. When
configuring the subchannels used by the LCS interface, we actually need to add
only one subchannel. LCS automatically assigns the second adjacent subchannel
for the LCS connection, one for read (device address is odd) and one for write
(device address is even). The subchannel is added by using the command sub
152 IBM 2216 and Network Utility Host Channel Connections

add. This command will place us at the subchannel config prompt from where we
can configure the subchannel parameters.
The following parameters have to be configured in the subchannel. All of them
must match other parameters specified on the host.
device The unit address transmitted on the channel path to select a 2216
device. This value must be in the range specified in the UNITADD
parameter in the CNTLUNIT macro of the IOCP definitions on the
host.
lpar Logical partition number on the host. Specifying this parameter allows
multiple LPARs to share one ESCON fiber. This value is defined in the
IOCP by the RESOURCE macro instruction. If the host is not using
EMIF, the default of 0 must be used for the LPAR number.
link If one ESCON Director (ESCD) is in the communication path, the link
address is the ESCD port number that is attached to the host. If two
ESCDs are in the path, it is the host-side port number of the ESCD
defined with the dynamic connection. When no ESCD is in the
communication path, this value must be set to X'01'.
cu The control unit address defined on the host for the 2216. This value
is defined on the host Input/output configuration program (IOCP) by
the CUADD statement on the CNTLUNIT macro instruction. The
Control Unit address must be unique for each LPAR defined on the
same host.
2216 ESCON Add Virtual>sub add
Please add or configure one subchannel for an LCS virtual interface.
Although LCS requires two subchannels, it is only necessary to specify
one subchannel. An adjacent subchannel will be chosen such that the
two subchannels will form a sequential pair with the write subchannel
(device address is even) before the read subchannel (device address is
odd).
2216 ESCON Config LCS Subchannel>?
LINk address (ESCD Port)
LPAR number
CU logical address
Device address
Exit
2216 ESCON Config LCS Subchannel>link cc
2216 ESCON Config LCS Subchannel>lpar 1
2216 ESCON Config LCS Subchannel>cu 1
2216 ESCON Config LCS Subchannel>device 02
2216 ESCON Config LCS Subchannel>ex
2216 ESCON Add Virtual>sub list
Read Subchannels:
Sub 0 Device address : 3 LPAR number : 1
Link address : CC CU Logical Address : 1
Write Subchannels:
Sub 1 Device address : 2 LPAR number : 1
Link address : CC CU Logical Address : 1
2216 ESCON Add Virtual>ex
2216 ESCON Config>ex
ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]:
2216 Config>
Figure 154. LCS Routing: LCS Subchannels Configuration
LAN Channel Station 153

Once the LCS interface has been added, the 2216 will assign a network number
to this interface, as seen in the output of the list devices command.
2216 Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 EIA-232E/V.24 PPP Slot: 8 Port: 0
Ifc 2 ESCON Channel Slot: 3 Port: 1
Ifc 3 LCS - ESCON Channel Base Net: 2
Figure 155. LCS Routing: Network Numbers Information
Configure IP Protocol
When the LCS interface is added to the 2216 a virtual LAN is created within the
2216. The only two stations which are on this LAN are the 2216 and the host. For
the 2216 to provide TCP/IP routing support IP has to be configured. The IP
configuration on the LCS interface is performed exactly in the same way as if it
were a genuine LAN interface.
Remember the following points when configuring the IP routing support:
• The IP subnet of the virtual LAN where the LCS interface of the 2216 and the
host are attached must be unique. That means that the IP address of the LCS
interface must be on a different subnet from any other interfaces on the 2216.
• The host and the LCS interface on the 2216 must have a different IP address
on the same subnet.
• For OS/390 TCP/IP versions previous to V3.6 and 2216 versions previous to
V3.2 only RIP and static routing are supported on the host and the LCS
interface. With OS/390 V3.6 and 2216 V3.2, it is possible to run routing
protocols such as OSPF which use IP multicast addressing. So, with 2216
V3.2 IP multicast can be used across the channel.
2216 Config>p ip
Internet protocol user configuration
2216 IP config>add add 0 16.0.0.1 255.255.255.0
2216 IP config>add add 1 192.194.200.2 255.255.255.0
2216 IP config>add add 3 192.168.125.2 255.255.255.0
2216 IP config>ena rip
2216 IP config>li all
Interface addresses
IP addresses for each interface:
intf 0 16.0.0.1 255.255.255.0 Local wire broadcast, fill 1
intf 1 192.194.200.2 255.255.255.0 Local wire broadcast, fill 1
intf 2 IP disabled on this interface
intf 3 192.168.125.2 255.255.255.0 Local wire broadcast, fill 1
Routing
Protocols
BOOTP forwarding: disabled
IP Time-to-live: 64
Source Routing: enabled
Echo Reply: enabled
TFTP Server: enabled
Directed broadcasts: enabled
ARP subnet routing: disabled
ARP network routing: disabled
154 IBM 2216 and Network Utility Host Channel Connections

Per-packet-multipath: disabled
OSPF: disabled
BGP: disabled
RIP: enabled
RIP default origination: disabled
Per-interface address flags:
intf 0 16.0.0.1 RIP Version 1
Send net and subnet routes
Receive No Dynamic host routes
RIP interface input metric: 1
RIP interface output metric: 0
intf 1 192.194.200.2 RIP Version 1
Send net and subnet routes
Receive No Dynamic host routes
RIP interface input metric: 1
RIP interface output metric: 0
intf 2 IP & RIP are disabled on this interface
intf 3 192.168.125.2 RIP Version 1
Send net and subnet routes
Receive No Dynamic host routes
RIP interface input metric: 1
RIP interface output metric: 0
Accept RIP updates always for:
[NONE]
Parameters
ARP-SUBNET-ROUTING : disabled
ARP-NET-ROUTING : disabled
CLASSLESS : disabled
DIRECTED-BROADCAST : enabled
ECHO-REPLY : enabled
FRAGMENT-OFFSET-CHECK : disabled
PER-PACKET-MULTIPATH : disabled
REASSEMBLY-SIZE : 12000 bytes
RECORD-ROUTE : enabled
ROUTING TABLE-SIZE : 768 entries (52224 bytes)
(Routing) CACHE-SIZE : 64 entries
SAME-SUBNET : disabled
SOURCE-ROUTING : enabled
TIMESTAMP : enabled
TTL : 64
Figure 156. LCS TCP/IP Routing Support: IP Config
5.3.2.3 2216 Monitoring
When monitoring the TCP/IP routing support via LCS on the 2216, we have to
check that:
• ESCON, LCS interface and subchannels are UP.
• If they are not, check that the parameters that must match on the 2216 and on
the host effectively match for the LCS link. See Figure 146 on page 138 for
details.
• Check the IP configuration.
LAN Channel Station 155

2216 *t5
2216 +conf
Multiprotocol Access Services
2216-MAS Feature 2821 V3.2 Mod 0 PTF 0 RPQ 0 MAS.EF6 cc4_12a
Num Name Protocol
0 IP DOD-IP
3 ARP Address Resolution
11 SNMP Simple Network Management Protocol
29 NHRP Next Hop Resolution Protocol
Num Name Feature
2 MCF MAC Filtering
7 CMPRS Data Compression Subsystem
9 DIALs Dial-in Access to LANs
10 AUTH Authentication
11 IPSec IPSecurity
Total Networks:
Net Interface MAC/Data-Link Hardware State
0 TKR/0 Token-Ring/802.5 Token-Ring Up
1 PPP/0 Point to Point EIA-232E/V.24 Up
2 ESCON/0 ESCON ESCON Channel Up
3 LCS/0 LCS ESCON Channel Up
2216 +net 2
ESCON Base Console
2216 ESCON>list sub 1
The following subchannels are defined:
Local address: 00 Device address: 02 CU Logical Address: 01
Link: CC LPAR: 01
Type: LCS
The following lantypes/lannums are using this subchannel:
LAN type: Token-Ring/802.5 LAN number: 0
Local address: 01 Device address: 03 CU Logical Address: 01
Link: CC LPAR: 01
Type: LCS
The following lantypes/lannums are using this subchannel:
LAN type: Token-Ring/802.5 LAN number: 0
2216 ESCON>li net 2
Net: 3 Type: LCS LAN Type: Token-Ring/802.5 LAN Number: 0
Net state: Up
2216 ESCON>exit
2216 +net 3
LCS Console
2216 LCS>list 3
LCS Virtual Adapter
LCS Information for Net 3
--- ----------- --- --- --
LAN Type: Token-Ring LAN Number: 0
Local Read Subchannel number: 1
Local Write Subchannel number: 0
MAC Address: 40002216000A
Local IP Address: 192.168.125.2
Status: Up
Figure 157. LCS Routing Interface Monitoring
1 This command lists all the subchannels defined in this ESCON interface. The
field type gives you the type of virtual network handler that owns this subchannel.
156 IBM 2216 and Network Utility Host Channel Connections

5.3.3 LCS Bridging Support
2 This command lists all network interfaces defined on this ESCON adapter. It will
list LCS, LSA or MPC+ interfaces on this ESCON channel. It shows also the
status of each one of the networks. In this case, the status of the LCS link is UP.
3 This command displays information for the LCS interface, like the LAN type and
number, the subchannel through which the device sends and receives data, etc. It
displays also the type of support the LCS interface is providing. As it is TCP/IP
routing, the command provides the local IP address used by the 2216 on the
connection to the host. Finally, it shows also the status of this network, it is UP
what means that the network connection to the host is established.
The next step is to check the IP connectivity of the 2216 by looking at the
contents of the routing table.
2216 +pip
2216 IP>dump
Type Dest net Mask Cost Age Next hop(s)
RIP 9.0.0.0 FF000000 2 20 192.168.125.1
RIP 10.0.0.0 FF000000 2 10 192.194.200.1
Sbnt 16.0.0.0 FF000000 1 12373 None
RIP 10.0.0.0 FF000000 2 10 192.194.200.1
Sbnt 16.0.0.0 FF000000 1 12373 None
Dir* 16.0.0.0 FFFFFF00 1 12379 TKR/0
RIP 192.168.120.0 FFFFFF00 3 20 192.168.125.1
Dir* 192.168.125.0 FFFFFF00 1 140 LCS/0
RIP 192.168.221.0 FFFFFF00 2 20 192.168.125.1
RIP 192.168.233.0 FFFFFF00 2 20 192.168.125.1
RIP 192.168.237.0 FFFFFF00 3 20 192.168.125.1
RIP 192.168.250.0 FFFFFF00 2 20 192.168.125.1
RIP 192.168.253.0 FFFFFF00 3 20 192.168.125.1
RIP 192.168.254.0 FFFFFF00 3 20 192.168.125.1
Dir* 192.194.200.0 FFFFFF00 1 12395 PPP/0
Routing table size: 768 nets (52224 bytes), 13 nets known
0 nets hidden, 0 nets deleted, 4 nets inactive
0 routes used internally, 751 routes free
Figure 158. LCS Routing: IP Monitoring
5.3.3.1 Network Environment Description
In this scenario the 2216 is attached to the host using the LCS protocol on the
ESCON channel. The 2216 is also attached to a token-ring LAN where the users
are located.
LAN Channel Station 157

S/390 TCP/IP Profile
HOME 192.168.125.1
------------------------------
MVS IOCP Definitions
UNITADD=02 & 03
CUADD=1
Figure 159. LCS Bridging Scenario
5.3.3.2 2216 Configuration
From the device’s point of view the configuration of the 2216 is the same one
used for LCS routing. Regarding the PPP link used in the LCS routing scenario
between the 2216 and the 2210, a link not used in this case, the PPP interface in
the 2216 is still there but it is not used. Refer to “Add the Physical Interfaces” on
page 162, “Configure the LCS Virtual Interface” on page 163 and“Configure the
LCS Subchannels” on page 152 for details on the configuration commands.
Configure Protocol ASRT (Bridging)
In this case, instead of routing IP frames between the LCS interface and the rest
of the interfaces, the 2216 is bridging the IP frames. So, the 2216 has to be
configured as a bridge. As the router is just bridging IP, the IP subnet of those
interfaces attached to the 2216 that have bridging enabled will be the same.
158 IBM 2216 and Network Utility Host Channel Connections
RA03
LPAR 1
RA28
LPAR 2
ESCD
LCS
LAN
100
CC
C9
RA39
LPAR 4
2216
S/390
192.168.125.10
S/390
101
2216

2216 Config>p asrt
Adaptive Source Routing Transparent Bridge user configuration
2216 ASRT config>ena bridge
2216 ASRT config>list port 1
Port ID (dec) : 128:01, (hex): 80-01
Port State : Enabled
STP Participation: Enabled
Port Supports : Transparent Bridging Only
Assoc Interface : 0
Path Cost : 0
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2216 ASRT config>add port
Interface Number [0]? 3
Port Number [2]?
2216 ASRT config>disable trans 1
2216 ASRT config>disable trans 2 2a
2216 ASRT config>ena source 1 100
Bridge number in hex (0 - 9, A - F) [0]? 1
2216 ASRT config>ena source 2 101 2b
2216 ASRT config>list port
Port ID (dec) : 128:01, (hex): 80-01
Port State : Enabled
STP Participation: Enabled
Port Supports : Source Route Bridging Only
SRB: Segment Number: 0x100 MTU: 4399 STE: Enabled
Assoc Interface : 0
Path Cost : 0
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Port ID (dec) : 128:02, (hex): 80-02
Port State : Enabled
STP Participation: Enabled
Port Supports : Source Route Bridging Only
SRB: Segment Number: 0x101 MTU: 4399 STE: Enabled
Assoc Interface : 3
Path Cost : 0
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Figure 160. LCS Bridging: ASRT Configuration
1 When bridging is enabled on the router, by default all the LAN interfaces are
enabled for bridging. So, we only have to add the LCS interface to the bridging
environment.
2 LCS interface network number.
3 The LAN type in this example is token-ring, that’s why source route bridging is
configured on the LCS interface. If this LAN is an Ethernet, transparent bridging
will have to be configured. Do not forget to enable sr-tb conversion if there is
another port in the router using source route bridging.
5.3.3.3 2216 Monitoring
When monitoring the LCS bridging support we have to make sure that:
• ESCON, the LCS interface and subchannels are UP.
• If they are not, check that the parameters that must match on the 2216 and on
the host effectively match for the LCS link. See Figure 146 on page 138 for
details.
LAN Channel Station 159

• Check the ASRT configuration.
2216 +net 2
2216 ESCON>li net
Net: 3 Type: LCS LAN Type: Token-Ring/802.5 LAN Number: 0
Net state: Up
2216 ESCON>li sub
The following subchannels are defined:
Local address: 00 Device address: 02 CU Logical Address: 01
Link: CC LPAR: 01
Type: LCS
The following lantypes/lannums are using this subchannel:
LAN type: Token-Ring/802.5 LAN number: 0
Local address: 01 Device address: 03 CU Logical Address: 01
Link: CC LPAR: 01
Type: LCS
The following lantypes/lannums are using this subchannel:
LAN type: Token-Ring/802.5 LAN number: 0
2216 ESCON>exit
2216 +net 3
LCS Console
2216 LCS>list
LCS Virtual Adapter
LCS Information for Net 3
--- ----------- --- --- --
LAN Type: Token-Ring LAN Number: 0
Local Read Subchannel number: 1
Local Write Subchannel number: 0
MAC Address: 40002216000A
LCS Bridging 1
Status: Up
Figure 161. LCS Bridging Interface Monitoring
1 The support provided by 2216 on this LCS interface is TCP/IP Passthru, that’s
why it appears as LCS bridging.
Then, check the bridging configuration.
160 IBM 2216 and Network Utility Host Channel Connections

Figure 162. LCS Bridging: ASRT Monitoring
5.3.4 LCS 3172 Emulation Support
2216 +pasrt
2216 ASRT>lis bridge
SRB Bridge ID (prio/add): 32768/02-00-44-68-00-80
Bridge state: Enabled
UB-Encapsulation: Disabled
Bridge type: SRB
Number of ports: 2
STP Participation: IBM-SRB proprietary
Maximum
Port Interface State MAC Address Modes MSDU Segment Flags
1 TKR /0 Up 02-00-44-68-00-80 SR 2096 100 RD,LD
2 LCS /0 Up 02-00-44-68-00-33 SR 2096 101 RD
Flags: RE = IBMRT PC behavior Enabled, RD = IBMRT PC behavior Disabled
LE = LNM Enabled, LD = LNM Disabled, LF = LNM Failed
SR bridge number: 1
SR virtual segment: 000 (1:N SRB Not Active)
Adaptive segment: 000
2216 ASRT>list port
Port Id (dec) : 128: 1, (hex): 80-01
Port State : Forwarding
STP Participation: Enabled
Port Supports : Source Route Bridging Only
SRB: Segment Number: 0x100 MTU: 2052 STE Forwarding: Auto
Assoc Interface #/name : 0/TKR/0
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Port Id (dec) : 128: 2, (hex): 80-02
Port State : Forwarding
STP Participation: Disabled
Port Supports : Source Route Bridging Only
SRB: Segment Number: 0x101 MTU: 2052 STE Forwarding: Yes
Assoc Interface #/name : 3/LCS/0
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
5.3.4.1 Network Environment Description
In this scenario the 2216 is connected to the host channel through the ESCON
channel adapter and to a token-ring LAN where the users are located. The
following figure shows the network setup:
LAN Channel Station 161

S/390 TCP/IP Profile
HOME 192.168.125.1
------------------------------
MVS IOCP Definitions
UNITADD=02 & 03
CUADD=1
Figure 163. LCS 3172 Emulation Network Setup
5.3.4.2 2216 Configuration
For configuring the 3172 emulation in the 2216 the following steps must be
followed:
Add the Physical Interfaces
The physical interface for the ESCON channel and the token-ring interface has to
be added by using the add device command from the 2216 config prompt.
The list devices command will give us the network number for each interface so
that we can go into the config prompt for each interface and configure it.
162 IBM 2216 and Network Utility Host Channel Connections
RA03
LPAR 1
RA28
LPAR 2
ESCD
LCS
CC
C9
RA39
LPAR 4
2216
S/390
LAN
400022160001
192.168.125.10

2216 *t6
2216 Config>add dev token
Device Slot #(1-8) [1]?
Device Port #(1-2) [1]?
Adding Token Ring device in slot 1 port 1 as interface #0
Use "net 0" to configure Token Ring parameters
2216 Config>add dev escon
Device Slot #(1-8) [1]? 3
Adding ESCON Channel device in slot 3 port 1 as interface #1
Use "net 1" to configure ESCON Channel parameters
2216 Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 ESCON Channel Slot: 3 Port: 1
Figure 164. LCS 3172 Emulation: Adding Physical Interfaces
Configure the LAN Interface
The LAN interface in our scenario is the token-ring network. The way it has to be
configured to fit our requirements, cable type, speed, etc. follows:
2216 Config>net 0
Token-Ring interface configuration
2216 TKR config>spee 16
2216 TKR config>medi unshie
2216 TKR config>set phy 40:00:22:16:00:01 1
2216 TKR config>li
Token-Ring configuration:
Packet size (INFO field): 2052
Speed: 16 Mb/sec
Media: Unshielded
IF Aging Timer: 120
Source Routing: Enabled
MAC Address: 400022160001
2216 TKR config>ex
2216 Config>
Figure 165. LCS 3172 Emulation: Configuring the LAN Interface
1 The MAC address of the LAN interface associated with the LCS interface will be
assigned to the LCS interface.
Configure the LCS Virtual Interface
For configuring the LCS interface we need to get the LCS config prompt. We do it
by issuing the add lcs command from the ESCON config prompt.
LAN Channel Station 163

2216 Config>net 1
2216 ESCON Config>add lcs
2216 ESCON Add Virtual>? 1a
LANtype
MAC address
MAXdata
BLKtimer
ACKlen
SUBchannels
ENable 3172 Emulation
Exit
2216 ESCON Add Virtual>enable
Enabling LCS 3172 Emulation for network 2.
Please set the Network link using the "NET" command.
2216 ESCON Add Virtual>? 1b
BLKtimer
ACKlen
SUBchannels
DISable 3172 Emulation
NET link
Exit
2216 ESCON Add Virtual>net
Networks available for LCS connections:
0
Select a network for the LCS connection: [0]? 0 2
2216 ESCON Add Virtual>
Figure 166. LCS 3172 Emulation: Configuring the LCS Interface
1 Note that the output of the ? in 1a and 1b is slightly different. In 1b we cannot
configure the LAN type because the LAN type will be set to the LAN interface
associated with the LCS interface. Also, the net command let’s the 2216 know
which LAN (by specifying the network number) is associated with that particular
LCS.
2 The LCS interface is associated with the token-ring interface, which is network
number 0.
Configure the LCS Subchannels
LCS uses two subchannels, one for reading and another one for writing. Only one
subchannel needs to be configured, the other one is automatically added by the
2216.
The subchannels are configured in the same way it has been done for LCS
routing and bridging. Refer to “Configure the LCS Subchannels” on page 152 for
details on what each parameter means.
164 IBM 2216 and Network Utility Host Channel Connections

2216 ESCON Add Virtual>sub add
Please add or configure one subchannel for an LCS virtual interface.
Although LCS requires two subchannels, it is only necessary to specify
one subchannel. An adjacent subchannel will be chosen such that the
two subchannels will form a sequential pair with the write subchannel
(device address is even) before the read subchannel (device address is
odd).
2216 ESCON Config LCS Subchannel>device 02
2216 ESCON Config LCS Subchannel>link cc
2216 ESCON Config LCS Subchannel>cu 1
2216 ESCON Config LCS Subchannel>lpar 1
2216 ESCON Config LCS Subchannel>ex
2216 ESCON Add Virtual>sub list
Read Subchannels:
Sub 0 Device address : 3 LPAR number : 1
Link address : CC CU Logical Address : 1
Write Subchannels:
Sub 1 Device address : 2 LPAR number : 1
Link address : CC CU Logical Address : 1
2216 ESCON Add Virtual>ex
2216 ESCON Config>list net 1
Net: 2 Protocol: LCS LAN type: Token Ring LAN number: 0
3172 Emulation is enabled.
MAC address: Obtained from net 0
Block Timer: 5 ms ACK length: 10 bytes
2216 ESCON Config>ex
ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]:
2216 Config>
Figure 167. LCS 3172 Emulation: LCS Subchannels Configuration
1 The output of this command specifies that 3172 emulation is being used and
that the MAC address for the LCS interface is taken from the LAN interface
associated with it.
Once the 2216 is configured, the configuration has to be saved on the hard drive
by using the write command, and the box must be reloaded for the configuration
to become active. The config we have just made is available on NVRAM. With the
reload it will be loaded from the NVRAM to the DRAM.
2216 Config>write
Config Save: Using bank B and config number 2
2216 Config>
2216 *reload y
Figure 168. LCS 3172 Emulation: Activating Configuration
5.3.4.3 2216 Monitoring
When monitoring the LCS 3172 emulation support on the 2216 we have to check,
as on the other types of support, the following points:
• ESCON, the LCS interface and subchannels are UP.
• If they are not, check that the parameters that must match on the 2216 and on
the host effectively match for the LCS link. See Figure 146 on page 138 for
details.
LAN Channel Station 165

2216 *t5
2216 +conf
Multiprotocol Access Services
2216-MAS Feature 2821 V3.2 Mod 0 PTF 1 RPQ 0 MAS.EF6 cc4ptf_56PB
Num Name Protocol
3 ARP Address Resolution
11 SNMP Simple Network Management Protocol
Num Name Feature
2 MCF MAC Filtering
7 CMPRS Data Compression Subsystem
9 DIALs Dial-in Access to LANs
10 AUTH Authentication
11 IPSec IPSecurity
Total Networks:
Net Interface MAC/Data-Link Hardware State
0 TKR/0 Token-Ring/802.5 Token-Ring Up
1 ESCON/0 ESCON ESCON Channel Up
2 LCS/0 LCS ESCON Channel Up
2216 +net 1
ESCON Base Console
2216 ESCON>list ?
SUbchannels
NEts
LOGpath
2216 ESCON>list net 1
Net: 2 Type: LCS LAN Type: Token-Ring/802.5 LAN Number: 0
Net state: Up
2216 ESCON>list sub 2
The following subchannels are defined:
Local address: 00 Device address: 02 CU Logical Address: 01
Link: CC LPAR: 01
Type: LCS
The following lantypes/lannums are using this subchannel:
LAN type: Token-Ring/802.5 LAN number: 0
Local address: 01 Device address: 03 CU Logical Address: 01
Link: CC LPAR: 01
Type: LCS
The following lantypes/lannums are using this subchannel:
LAN type: Token-Ring/802.5 LAN number: 0
2216 ESCON>ex
2216 +net 2
LCS Console
2216 LCS>list 3
LCS Virtual Adapter
LCS Information for Net 2
--- ----------- --- --- --
LAN Type: Token-Ring LAN Number: 0
Local Read Subchannel number: 1
Local Write Subchannel number: 0
MAC Address: 400022160001
LCS 3172 Emulation to net 0
Status: Up
2216 LCS>exit
2216 +
Figure 169. LCS 3172 Emulation Interface Monitoring
166 IBM 2216 and Network Utility Host Channel Connections

1 This command provides a list of all the network interfaces configured on this
ESCON channel adapter. If applicable, as in the case of LCS and LSA, it provides
the LAN type and LAN number of the interfaces.
2 This command lists all the subchannels configured on this ESCON channel
adapter. It provides also a list with all the LCS interfaces that are using these
subchannels, identified by LAN type and LAN number.
3 This command displays information for the LCS interface. The MAC address
assigned to the LCS interface is the MAC address of the LAN associated with it.
The output of this command also specifies that this LCS interface is supporting
3172 emulation and that the associated LAN interface is network 0, which is the
token-ring interface in this scenario.
LAN Channel Station 167

168 IBM 2216 and Network Utility Host Channel Connections

Chapter 6. Multipath Channel+ Implementation (MPC+)
6.1 2216 MPC+ Support
MPC is a data link control (DLC) interface for the channel. Each MPC path
consists of one or more read subchannels and one or more write subchannels,
bound together to form a transmission group. Since each subchannel operates in
only one direction, the half-duplex turnaround time that occurs with other
channel-to-channel connections is reduced. For the ESCON channel only MAS
V3R2 PTF01 raised the maximum number of subchannels to 64 and the number
of virtual net handlers to 32.
This interface is used to run APPN/HPR (HPDT MPC requires VTAM V4R4) and
also TCP/IP traffic between the host and the downstream devices. Both protocols
can be run simultaneously on the same MPC+ interface; no extra definition has to
be made on the host. The same Transport Resource List (TRL) can be used for
APPN/HPR and TCP/IP.
The host channel interface packages control and data frames in blocks of up to
36 KB. MPC blocks contain one or more discontiguous frames, with the first 4 KB
of the block containing MPC Protocol Data Unit (PDU) headers and offsets of
application data, which is stored in the last 32 KB of the block.
If at least one read and one write path are allocated successfully, the MPC+
channel connection is activated. Additional paths (defined but not online) in an
MPC+ group can be dynamically added later to the active group using the MVS
VARY device ONLINE command.
The MPC+ does not use the virtual LAN adapter concepts common to both LSA
and LCS interfaces, since MPC does not support LAN gateway appearance for
the 2216 channel adapter. Each channel adapter in the 2216 can support up to
32 subchannels (64 subchannels with MAS V3R2 PTF01). For an MPC+ interface
we need at least one read and one write subchannel to build up an MPC+ group,
so a maximum of 16 MPC+ interfaces per adapter can be configured. Even so
there is a maximum of 16 virtual network handlers per adapter, which of course
can be a mix of LCS/LSA/MPC+.
MPC+ groups are identified in the microcode using the same LAN type and LAN
number destination as virtual LAN adapters. As frames are deblocked by the
microcode, each frame is given a LAN type of MPC+ and a LAN number which
corresponds to the MPC+ group associated with the subchannel it was received
on. This allows the microcode and net handler to process MPC+ frames in a
manner consistent with LCS and LSA frames.
So to establish an MPC+ interface to the host we have to add a virtual interface
either to an ESCON or to a Parallel channel adapter (PCA) via the ADD MPC
command. This leads us to configure the subchannels regarding the host
definitions. One important aspect to remember about the read and write
subchannel definitions is that read on the host means write on the 2216 side, and
write on the host means read on the 2216. The 2216 Model 400 and Network
Utility MPC+ do not allow the subchannels of an MPC+ group to be on more than
one physical channel.
© Copyright IBM Corp. 1998 169

MPC+ in the 2216 Model 400 and Network Utility supports APPN HPR and
TCP/IP. For ESCON only, MPC+ also supports HPDT for UDP (UDP+).
Note: For either channel adapter, the terms MPC+ group and MPC+ virtual
interface mean the same thing.
If either partner node does not support MPC+, non-HPDT MPC is automatically
used.
Neither the 2216 Model 400 nor Network Utility supports non-HPDT MPC.
6.2 2216 MPC+ Host Parameter Relationships
Before we can attach a 2216 to a channel, the host must be configured correctly.
The following steps are required to define a 2216 connection to the host:
1. Define the 2216 to the host channel subsystem using either the host I/O
configuration program (IOCP) or hardware configuration definition (HCD)
program. The IOCP macros needed for defining the 2216 to the host are:
• RESOURCE Statement: Identifies logical partitions
• CHPID Statement: Identifies type of channel connection and who uses it
• CNTLUNIT and IODEVICE Statements: Identify the 2216 connection to the
host.
2. Define the 2216 control unit to the host operating system.
3. Define the 2216 and configuration to the host program (TCP/IP and/or VTAM).
Configuring the VTAM host requires entries in two VTAM control blocks:
• The local SNA major node (only for APPN)
• The transport resource list (TRL) major node
You also have to change to the VTAM startup parameters for using APPN
HPR.
TCP/IP is configured on the host by modifying the TCP/IP profile. Each
channel connection requires:
• One LINK and one DEVICE statement in the TCP/IP profile.
170 IBM 2216 and Network Utility Host Channel Connections
The steps for configuring TCP/IP on the host for an MPC+ connection are
the same as for an LCS connection. However, the command syntax for the
device and link commands is slightly different. For an MPC+ connection,
the syntax for the device command is:

DEVICE IPTRL1 MPCPTP
where IPTRL1 is the name of the TRL that this connection will use and MPCPTP
specifies an MPC point-to-point link.
To define the link, the syntax is:
LINK LINK1 MPCPTP IPTRL1
where LINK1 is the link name and the other two parameters are the same as
those used in the device statement.
• An entry in the HOME statement. This statement specifies the IP
address(es) of the host TCP/IP stack.
• Entries in the GATEWAY statement for the link to be used (if ROUTED is
not being used).
• A START command for the device. This command causes the specified
subchannels to be started.
The relationship between the definition on the host and in the 2216 can be seen
in Figure 170 on page 172:
Multipath Channel+ Implementation (MPC+) 171

VTAM Local PU Definition
VTAM Start List
LOC2216 VBUILD TYPE=LOCAL
NETID=USIBMRA
PU2216 PU TRLE=M3A2216A,XID=YES,CONNTYPE=APPN,
CPCP=YES,HPR=YES
MVS IOCP Definitions
VTAM Transport Resource List Major Node
TRL2216 VBUILD TYPE=TRL
M3A2216A TRLE LNCTL=MPC,
MAXBFRU=9,
READ=(280)
WRITE=(281),
REPLYTO=3.0
RESOURCE PART=((A1,1))
CHPID PATH=((2C),TYPE=CNC,PART=(A1),SWITCH=E1)
Figure 170. MPC+ Host Parameter Relationship for IP and APPN Protocol
172 IBM 2216 and Network Utility Host Channel Connections
CNTLUNIT CUNMBR=0280,PATH=2C,CUADD=1,
UNITADD=((00,32)),LINK=C9,UNIT=3172
S/390 TCP/IP Profile - MPC+
IODEVICE UNIT=3172,ADDRESS=((280,032)),
CUNMBR=0280
DEVICE M3A2216A MPCPTP
LINK M3A2216A MPCPTP M3A2216A
LPAR 1
CHPID=2C
192.166.236.1
HOME 192.166.236.1 M3A2216A
CC
START M3A2216A
ESCON
Director E1
C9
192.166.236.2
2216
ESCON MPC+ Definitions:
PC Definitions:
NETID=USIBMRA
Local Node Name=MAINZ
EN HPR Support
Destin add=400022160001
16.0.0.16
LPAR 1
CU 1
Device 01 (READ)
Device 00 (Write)
Link CC
APPN Definitions:
NETID=USIBMRA CP Name=NN2216
IP Address=16.0.0.16
16.0.0.1 Token
Ring
'MPC-IP Address'=192.166.236.2
TR: IP Address=16.0.0.1 / MAC@=400022160001

6.3 Host Definitions
Before we can attach the 2216 to an ESCON channel, the host system must be
configured correctly.
6.3.1 IOCP and MVS Operating System Definitions
The IOCP definitions for the 2216 with ESCON channel attached are shown in
Figure 171. These definitions are the same ones used for LCS/LSA.
The CNTLUNIT statement defines the path from the host to the 2216 and is used
for the IOCP definitions.
The 2216 must be defined to an IBM Multiple Virtual Storage/Extended
Architecture (MVS/XA) or MVS/ESA operating system. This definition is
accomplished by updating the MVS control program with an entry for the 2216 in
the IODEVICE macro.
The IODEVICE statement in Figure 171 is for the MVS operating system.
RESOURCE PARTITION=((A1,1) 1 ,(A2,2),(A3,3),(A4,4),(A5,5),(C1,6), *
(C2,7))
CHPID PATH=(2C),SHARED, *
PARTITION=((A1,A2,A3,A4),(A1,A2,A3,A4,A5)),SWITCH=E1, *
TYPE=CNC
CNTLUNIT CUNUMBR=0280,PATH=(2C),UNITADD=((00,032)) 2 ,LINK=(C9), *
CUADD=1 3 ,UNIT=3172
CNTLUNIT CUNUMBR=02A0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=2,UNIT=3172
CNTLUNIT CUNUMBR=02C0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=4,UNIT=3172
IODEVICE ADDRESS=(280,032),UNITADD=00,CUNUMBR=(0280),STADET=Y, *
PARTITION=(A1),UNIT=3172
IODEVICE ADDRESS=(2A0,032),UNITADD=00,CUNUMBR=(02A0),STADET=Y, *
PARTITION=(A2),UNIT=3172
IODEVICE ADDRESS=(2C0,032),UNITADD=00,CUNUMBR=(02C0),STADET=Y, *
PARTITION=(A4),UNIT=3172
Figure 171. MPC+: IOCP and MVS Operating System Definitions
1 In this scenario we will connect to LPAR 1.
2 UNITADD defines the range of addresses reserved for this control unit. The first
number is the hex of the first subchannel assigned to this control unit. The second
number is the decimal number of subchannels being assigned to this control unit.
The parameter device address defined in the 2216 must be in this range of
addresses. In this scenario we will use device address 04.
3 This value identifies the control unit address of the 2216. This restriction has
been removed with MAS V3R2 PTF01.
6.3.2 VTAM Definitions for an MPC+ Connection
An MPC+ connection requires entries in two VTAM control blocks:
• The local major node (only for APPN)
• The transport resource list (TRL) major node
Multipath Channel+ Implementation (MPC+) 173

Figure 172 shows a sample definition for a local SNA major node for a 2216
MPC+ connection. This is the local PU that resides in VTAM that supports the
channel connection defined in the TRL. The connection type must be APPN and
HPR needs to enabled.
I*********************************************************************
* *
* VTAM APPN NODE FOR 2216 MPC *
* *
**********************************************************************
LOC2216 VBUILD TYPE=LOCAL 1
PU2216 PU TRLE=M3A2216A, 2 X
XID=YES, 3 X
CONNTYPE=APPN, 4 X
CPCP=YES, 5 X
HPR=YES 6
Figure 172. VTAM Local Major Node Definition
Notes:
1 TYPE must be LOCAL on the VBUILD statement.
174 IBM 2216 and Network Utility Host Channel Connections
2 TRLE identifies the TRL being used. The name must match the name of an
existing TRL.
3 XID indicates whether XIDs will be exchanged. It must be XID=YES.
4 CONNTYPE must be set to CONNTYPE=APPN because APPN is the only
protocol that VTAM uses with an MPC+ connection.
5 CPCP specifies that CP-CP connections with APPN can be established over
this MPC+ connection. This could be set to either YES or NO, depending upon
your APPN topology.
6 HPR specifies that APPN HPR traffic can flow over this MPC+ connection.
HPR is normally used by default, but setting this value to YES ensures it. This
is important because an MPC+ connection requires RTP (and HPR).
Next, you need a transport resource list (TRL) for the MPC+ connection from the
2216. An example definition is shown in Figure 173 on page 174. This TRL is
used in our test environment for both protocols, the TCP/IP and the APPN.
**********************************************************************
* *
* VTAM TRL NODE FOR 2216 MPC *
**********************************************************************
TRL2216 VBUILD TYPE=TRL 1
M3A2216A 2 TRLE LNCTL=MPC, 3 X
MAXBFRU=9, 4 X
READ=280, 5 X
WRITE=281, X
MPCLEVEL=HPDT, X
REPLYTO=3.0 6
Figure 173. VTAM Transport Resource List (TRL) Definition
Notes:
1 TYPE must be TRL.

2 M3A2216A is the name that identifies the TRL. It must match what is specified in
the TRLE= field in the local major node definition (see Figure 172 on page
174) and also the DEVICE statement in the TCP/IP profile (see Figure 174 on
page 176).
3 LNCTL identifies the connection type. It must be LCNTL=MPC.
4 MAXBFRU is the number of 4K pages per read subchannel.
5 READ/WRITE specifies the subchannels in the MPC+ group, and indicates
their direction. The subchannel numbers must be in the range of addresses
specified in the IODEVICE statement in the IOCP definition. There can be
multiple READ and WRITE parameters in the TRLE statement, but there must
be at least one of each.
Note: The designations READ and WRITE here are from the host
perspective. In the 2216 MPC+ definition, the designations are from the 2216.
Therefore, subchannels designated as READ on the host must be designated
as WRITE on the 2216, and vice versa.
6 REPLYTO is the reply timeout value in seconds.
6.3.3 TCP/IP Definition for MVS
TCP is configured on a host by modifying the TCP/IP profile. We put here only a
part of the whole profile and marked the important parameter as shown in Figure
174 on page 176.
Multipath Channel+ Implementation (MPC+) 175

;******************************** Top of Data ***********************
; Member TCP.TCPPARMS(PROF03A)
....
...
; MPC Definition
; APAR PQ04890 for OS/390 R3
; VTAM requirement for TRLE Definition in VTAM VBUILD=TRL
; The DEVICE name must match the TRLE name in VTAM
; The TRLE entry must have MPCLEVEL=HPDT (default)
; Support is for ESCON and 2216 (future)
; *********************************************************
; DEVICE MPC25 MPCPTP AUTORESTART
; LINK MPC25 MPCPTP MPC25
DEVICE M3A2216A MPCPTP AUTORESTART 1
LINK M3A2216A MPCPTP M3A2216A 2
; DEVICE M3A2216B MPCPTP AUTORESTART
; LINK M3A2216B MPCPTP M3A2216B
....
...
; HOME Internet (IP) addresses of each link on the host.
;
; NOTE: To use this home statement, update the ipaddress and linknames
; to reflect your installation configuration and remove the semicolon
;
;
; HOME Internet (IP) addresses of each link on the host.
HOME
192.168.250.3 VIPA3A ; 1st VIPA Link (for V2R5)
9.24.104.231 TR1
192.168.125.1 LD2216
192.168.221.7 ICP11 ;for VIPA address on LAN
; 192.168.249.3 T03CTCP ; For SAMEHOST - IUTSAMEH - Connection
192.168.236.3 RA28M ; XCF TO MVS28
192.168.233.3 RA39M ; XCF TO MVS39
192.169.232.41 IUTSAMEH ;
; 9.24.105.126 EN1 ; 9.24.105.0
; 9.24.105.76 EN2 ; 9.24.105.0
; 192.168.230.1 LOOPBACK ; extra address for NDR Cluster
; 192.168.239.3 LINKT25A
; 192.168.202.3 A3746
; 192.168.203.3 B3746
192.168.221.03 icp1
192.168.221.05 icp2
192.168.109.3 iccp
192.168.229.3 fddi1
192.168.21.3 latm1
192.168.100.100 TR2 ; Testing DHCP + DDNS
; 192.168.235.3 MPC25 ; MPC TO MVS25
192.166.236.1 M3A2216A ; MPC TO 2216 A 3
; 192.168.240.3 M3A2216B ; MPC TO 2216 B
....
...
; orouted Routing Information 4
;
; if you are using orouted, comment out the GATEWAY statement and
; update the BSDROUTINGPARMS statement to reflect your installation
; configuration and remove the semicolon
;
;
; **********************************************************************-
INCLUDE TCP.TCPPARMS(PR03ABSD)
; **********************************************************************-
Figure 174. TCP/IP Profile Extract
176 IBM 2216 and Network Utility Host Channel Connections

Notes:
1 M3A2216A is the name of the TRL that this connection will use and MPCPTP
specifies an MPC point-to-point link.
2 The first name after the DEVICE statement (M3A2216A) is the link name and
the other two parameters are the same as those used in the device statement.
So here the link name is chosen as the name of the TRL.
3 192.166.236.1 is the IP address of this MPC+ interface and M3A2216A is the
name of the link.
4 We are not using the GATEWAY statement in this scenario but orouted, since
dynamic routing is being used instead of static routing. With Communications
Server for OS/390 Version 2.5 it is possible to have the orouted Routing
Information in a separate file. The routing information for this host can be seen
in Figure 176 on page 178.
; Start all the defined devices.
;
; NOTE: To use these START statements, update the device name
; to reflect your installation configuration and remove the semicolon
;
; Start all the defined devices.
;START ctc25
START icp1
;START icp2
START icp11
;START DEVT25A
;START A3746
;START B3746
START iccp
START D2216
START TR1
;START TR2
;START MPC25
START OSARA03
START RA28M
START RA39M
;START EN1 ; 3172-3 ICP Ethernet
;START EN2 ; 3172-3 ICP Ethernet
START IUTSAMEH ; SAMEHOST LINK (IUTSAMEH)
START M3A2216A ; mpc to 2216 A 1
;START M3A2216B ; mpc to 2216 B
START FDDI1 ; osa 00
Figure 175. Start Statement from the TCP/IP Profile
1 This sentence is the starting interface for the 2216. This command causes the
subchannels to be started.
In Figure 176 on page 178, BSDROUTINGPARMS specifies which links on the
host are RIP capable. For those links in a point-to-point network the destination
IP address has to be specified. For the other links in a broadcast or nonbroadcast
multiaccess network we do not need to specify the destination IP address from
where the host received RIP advertisement or where it will send RIP
advertisements.
Multipath Channel+ Implementation (MPC+) 177

;******************************** Top of Data ***********************
; profile 03a orouted
; ******************************************************************
;
; orouted Routing Information
;
;
; Link Maxmtu Metric Subnet Mask Dest Addr
BSDROUTINGPARMS false
VIPA3A DEFAULTSIZE 0 255.255.255.0 0
IUTSAMEH DEFAULTSIZE 0 255.255.255.0 0
RA28M 32768 0 0 0
RA39M 32768 0 0 192.168.233.39
; EN1 1500 0 255.255.255.0 0
; EN2 1500 0 255.255.255.0 0
; T03CTCP 4096 0 0 192.168.249.4
; A3746 4092 0 0 192.168.202.1
; B3746 4092 0 0 192.168.203.1
ICP1 4000 0 255.255.255.0 0
; ICP2 4000 0 255.255.255.0 0
; LINKT25A 2000 0 0 192.168.239.27
; iccp 4000 0 0 192.168.109.2
LATM1 8000 0 255.255.255.0 0
LD2216 4000 0 255.255.255.0 0
TR1 4000 0 255.255.255.0 0
TR2 4000 0 255.255.255.0 0
M3A2216A 2000 0 0 192.166.236.2 1
; M3A2216B 32768 0 0 192.168.240.13
; MPC25 32768 0 0 192.168.235.25
FDDI1 4000 0 255.255.255.0 0
ENDBSDROUTINGPARMS
Figure 176. orouted Definitions
1 This sentence specifies the routing capabilities for the MPC+ link. As the
downstream network on the MPC+ interface is point to point we have to define a
destination IP Address.
6.3.4 2216 MPC+ and APPN
When an MPC+ interface is added, a new interface is created. When APPN is
defined, a port and link station are defined as for all other APPN interfaces. The
only slight changes are:
When adding a port, the link type is MPC+. The interface is the MPC+ interface,
not the ESCON/PCA interface.
The difference in the appearance between the APPN support via MPC+ versus
that provided by LSA is that in LSA the 2216 and the host appear as if they are
connected via a LAN. With MPC+ the appearance is of the host being directly
attached to the 2216 (no intervening LAN), which is shown in Figure 177 on page
179.
178 IBM 2216 and Network Utility Host Channel Connections

MPC+
APPN
6.3.5 MPC+ Configuration for APPN
HOST
Base Net Handler
2216
Figure 177. MPC+ Appearance between 2216 and Host for APPN
To run APPN over MPC+, the following steps have to be done:
• Add the APPN package to the 2216.
• Define the physical interfaces.
• Add an MPC+ virtual interface.
• Configure an MPC+ virtual interface.
• Configure an MPC+ subchannel.
• Configure APPN.
Logical
Appearance:
host
APPN
2216
Rest of APPN
Network
In this section we will perform these items step by step and explain the
configuration parameters with regard to our test environment which is shown in
Figure 178. Due to this not all config parameters will be highlighted here so we
recommend that you check your network. For further details about these
parameters please see:
• Nways Multiprotocol Access Services Software User's Guide Version 2,
Release 2, SC30-3886
• Nways Multiprotocol Access Services Protocol Configuration and Monitoring
Reference Vol. 1 Version 3.2, SC30-3884
• Nways Multiprotocol Access Services Protocol Configuration and Monitoring
Reference Vol. 2 Version 3.2, SC30-3885
Multipath Channel+ Implementation (MPC+) 179

VTAM Start Option
NETID=USIBMRA
SSCPNAME=RA03M
------------------------------
MVS IOCP Definitions
UNITADD=00 & 01
CUADD=1
Figure 178. Overview of the Test Environment
6.3.6 Add the APPN Package to the 2216
Provided that your 2216 code supports APPN, the APPN package will be
included in the 2216 via talk 6 on the command line, which requires a reload of
the whole device. The 2216 will tell you also to do this as you can see in Figure
179:
Figure 179. Adding the APPN Package to the 2216
6.3.7 Define the Physical Interfaces
Regarding our test environment we are going to add the physical interfaces via
the T6 on the command line:
• LAN adapter (token-ring)
• WAN adapter (EIA-232)
180 IBM 2216 and Network Utility Host Channel Connections
RA03
LPAR 1
TR
LAN
usibmra.mainz
Config>load add pack appn
appn package configured successfully
This change requires a reload.
RA28
LPAR 2
ESCD
CC
C9
MPC+ 2216
WAN
RA39
LPAR 4
S/390
usibmra.nn2216
PPP
2210
TR
usibmra.valencia
usibmra.nn2210

• ESCON adapter
Figure 180 reflects the result of adding the devices to the 2216 (TR/EIA/ESCON).
For the EIA device we recommend that you set up the data link protocol and
configure the interfaces via the net X command. For our test environment this
default value which is PPP is selected.
Config>add dev to
Device Slot #(1-8) [1]? 1
Device Port #(1-2) [1]? 1
Adding Token Ring device in slot 1 port 1 as interface #0
Use "net 0" to configure Token Ring parameters
Config>add dev eia
Device Slot #(1-8) [1]? 8
Device Port #(0-7) [1]? 0
Defaulting Data-link protocol to PPP
Adding EIA-232E/V.24 PPP device in slot 8 port 0 as interface #1
Use "set data-link" command to change the data-link protocol
Use "net 1" to configure EIA-232E/V.24 PPP parameters
Config>add dev escon
Device Slot #(1-8) [1]? 3
Adding ESCON Channel device in slot 3 port 1 as interface #2
Use "net 2" to configure ESCON Channel parameters
Figure 180. Adding the Physical Interfaces to the 2216
Via the list device command (see Figure 181) from the config command prompt
we can get the logical interface numbers, the device type and their physical
position inside the 2216.
Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 EIA-232E/V.24 PPP Slot: 8 Port: 0
Ifc 2 ESCON Channel Slot: 3 Port: 1
Figure 181. List of the Devices inside the 2216
After the add dev command the net parameters have to be set up. We will add
here only the parameter for the ESCON adapter which is in our scenario. The net
number is 2 (see Figure 181). For the configuration of the other interfaces refer to
Nways Multiprotocol Access Services Software User's Guide Version 2, Release
2, SC30-3886.
6.3.8 Add/Configure MPC+ Virtual Interface
Now the physical interfaces have been configured. We can start to use the add mpc
command (see Figure 182) to add an MPC+ virtual interface and get to the ESCON
Add Virtual> prompt from which you can enter other interface and subchannel
parameters:
Multipath Channel+ Implementation (MPC+) 181

Config>net 2
ESCON Config>add mpc
ESCON Add Virtual>
Figure 182. Adding the MPC+ Virtual Interface
There are eight commands available to configure the MPC+ virtual interface for
an ESCON adapter:
• acklen
• blktimer
• disable_o, enable_o outbound protocol blocking
• disable, enable udp+ exclusive use
• maxdata
• reply timeout
• sequencing interval timer
• subchannel
However, we will focus only on the subchannel command and its values. All others
will be used in their default values in our case. For more information about the
other parameters see the Nways Multiprotocol Access Services Software User's
Guide Version 2, Release 2, SC30-3886.
The subchannel command places you at the next prompt based on the value of
command, as shown in Figure 183 on page 183. Commands can be one of the
following:
addr sub addr Adds a read subchannel and displays the ESCON Add
MPC+ Read subchannel> prompt from which you can add
device address, LPAR number, link address, and CU logical
address.
addw sub addw Adds a write subchannel and displays the ESCON Add
MPC+ Write subchannel> prompt from which you can add
device address, LPAR number, link address, and CU logical
address.
mod sub mod Modifies a configured MPC+ subchannel. It lists the
configuration for the configured MPC+ subchannels and
allows you to modify one of them by specifying the sub
number from the list. Once you have selected the
subchannel, you can change the device address, LPAR
number, link address, and CU logical address.
delete sub delete Deletes a configured MPC+ subchannel. It lists the
configuration for the configured MPC+ subchannels and
allows you to delete one of them by specifying the sub
number from the list.
list list sub Lists information for the MPC+ subchannels
From the ESCON add virtual> prompt, the subchannels have to be added and
configured to reflect the definitions made on the host. Remember a subchannel
defined as read to VTAM is a write subchannel for the 2216, and a subchannel
defined as write to VTAM is a read subchannel for the 2216.
182 IBM 2216 and Network Utility Host Channel Connections

6.3.9 Configure an MPC+ Subchannel
There are four parameters required to configure each read and write subchannel.
At least one read and one write channel has to be configured so that the MPC+
connection can be activated. You can get to the ESCON Add MPC+ Read/Write
Subchannel> prompt after you have entered the sub addr/addw command from
ESCON add virtual> prompt. The configuration of the parameter reflecting our
test environment is seen in Figure 183 on page 183 and has to match the host
parameter.
ESCON Add Virtual>sub addr
ESCON Add MPC+ Read Subchannel>device 1
Device address (range 0x00-0xFF): [0]? 1
ESCON Add MPC+ Read Subchannel>cu 1 2
ESCON Add MPC+ Read Subchannel>lpar 1 3
ESCON Add MPC+ Read Subchannel>link 4
Link address (ESCD Port) (range 0x01-0xFE): [1]? cc
ESCON Add MPC+ Read Subchannel>ex
ESCON Add Virtual>sub addw
ESCON Add MPC+ Write Subchannel>device 0
ESCON Add MPC+ Write Subchannel>cu 1
ESCON Add MPC+ Write Subchannel>lpar 1
ESCON Add MPC+ Write Subchannel>link cc
ESCON Add MPC+ Write Subchannel>ex
ESCON Add Virtual>sub li
Read Subchannels:
Sub 0 Device address : 1 LPAR number : 1
Link address : CC CU Logical Address : 1
Write Subchannels:
Sub 1 Device address : 0 LPAR number : 1
Link address : CC CU Logical Address : 1
ESCON Add Virtual>ex
ESCON Config>ex
ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]: y
Figure 183. Configure Read and Write Subchannel to the MPC+
The four subparameters for addr/addw and their meanings are as follows:
1 device The unit address transmitted on the channel path to select a 2216
device. It is also referred to as subchannel number in S/3X0 I/O
architecture. It is a two-digit hexadecimal value whose range is
00-FF. This value is defined on the host IOCP by the UNITADD
statement on the CNTLUNIT macro instruction for the real device.
2 cu The control unit address defined on the host for the 2216. This
value is defined on the host Input/Output configuration program
(IOCP) by the CUADD statement on the CNTLUNIT macro
instruction. The control unit address must be unique for each
logical partition defined on the same host. This restriction is
removedwithMASV3R2PTF01.
3 lpar Logical partition number. This allows multiple logical host partitions
(LPARs) to share one ESCON channel. This value is defined on the
host Input/Output configuration program (IOCP) by the
RESOURCE macro instruction. If the host is not using EMIF, use
the default of 0 for the LPAR number.
Multipath Channel+ Implementation (MPC+) 183

184 IBM 2216 and Network Utility Host Channel Connections
4 link If one ESCON Director (ESCD) is in the communication path, the
link address is the ESCD port number that is attached to the host. If
two ESCDs are in the path, it is the host-side port number of the
ESCD defined with the dynamic connection. When no ESCD is in
the communication path, this value must be set to X'01'.
The list device command (Figure 181) at the config prompt reflects the new
status of the interfaces for the 2216. The MPC+ got its own interface number as
shown in Figure 184 below and is now ready to be configured to its protocol
needs which should run over this interface.
Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 EIA-232E/V.24 PPP Slot: 8 Port: 0
Ifc 2 ESCON Channel Slot: 3 Port: 1
Ifc 3 MPC - ESCON Channel Base Net: 2
Figure 184. List of the Devices inside the 2216
6.3.10 Configure APPN
To configure the APPN protocol for the 2216, the next step is to set up the APPN
node of the 2216. After the node is set, we have to reload the 2216 otherwise we
will not be able to configure the APPN port definitions for the different interfaces,
which are the MPC+, the TR and the EIA interface in our test environment. The
node is set up via the APPN protocol. Here the APPN will be set, the NETID
(network id) where our 2216 resides and the CP name (control point name) of the
2216 have to be defined. These three parameters (enable APPN, NETID, CP
name) are the main objects to configure, to set up the availability of APPN in the
2216. The other parameters can be left by their default if not specially needed.
Figure 185 shows the APPN setup of our 2216 used in the test environment via
the talk 6 command line.
Config>p appn
APPN config>set node
Enable APPN (Y)es (N)o [Y]? y
Network ID (Max 8 characters) [ ]? usibmra 1
Control point name (Max 8 characters) [ ]? nn2216 2
Enable branch extender or border node
(0=Neither, 1=Branch Extender, 2=Border Node) [0]?
Route addition resistance(0-255) [128]?
XID ID number for subarea connection (5 hex digits) [00000]?
Use enhanced #BATCH COS (Y)es (N)o [Y]?
Use enhanced #BATCHSC COS (Y)es (N)o [Y]?
Use enhanced #INTER COS (Y)es (N)o [Y]?
Use enhanced #INTERSC COS (Y)es (N)o [Y]?
Write this record? [Y]?
The record has been written.
APPN config>
Config>reload ****> needed to be able to configure APPN port defs
Figure 185. Setup of the 2216 for APPN Readiness
1 Set the network ID where the 2216 resides.

2 Define the unique CP name to the 2216.
The 2216 has been set up to run APPN traffic on its interfaces. Now the
interfaces have to be configured regarding our test scenario. For our MPC+
connection to the host we have to configure a PORT and also the LINK. The
same applies to the EIA interface which is connected to the 2210 via PPP. For
the TR interface only the port definition has to be set; the station will be added
dynamically during session establishment. Please be careful with the interface
number when configuring APPN for the host connection, not the ESCON interface
but the MPC+ interface itself. From Figure 184 on page 184 you can see it is Ifc 3
in our scenario.
The next figures show the configuration for the interfaces in the 2216 to run APPN
traffic through it, starting with Figure 186 on page 185 for the token-ring interface.
In our test environment we take the defaults given by the 2216 for the different
parameters. We have to remember only the interface number which is 0 for the
token-ring interface.
Config>p appn
APPN config>add port
APPN Port
Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING,
(M)PC, (S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P [ ]? t
Interface number(Default 0): [0]? 0
Port name (Max 8 characters) [T00000]? 1
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Support multiple PU (Y)es (N)o [N]?
Service any node: (Y)es (N)o [Y]?
High performance routing: (Y)es (N)o [Y]?
Maximum BTU size (768-17745) [2048]?
Maximum number of link stations (1-976) [512]?
Percent of link stations reserved for incoming calls (0-100) [0]?
Percent of link stations reserved for outgoing calls (0-100) [0]?
Local SAP address (04-EC) [4]?
Local HPR SAP address (04-EC) [C8]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>
Figure 186. Add the APPN Port to the Token-Ring Interfaces
1 APPN port name for the token-ring interface
For the EIA interface the port and the link have to be added. Again we stay with
the defaults given by the 2216 for the different configuration parameter as seen in
Figure 187 on page 186. The port name for the EIA interface will be needed when
we configure the link. A station name has to be placed during the add link process
and also the type of the adjacent node where the link is connected. The name for
the port and the link will be seen later when monitoring the APPN ports and links.
Multipath Channel+ Implementation (MPC+) 185

APPN config>
APPN config>add port
APPN Port
Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING,
(M)PC, (S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P [ ]? p
Interface number(Default 0): [0]? 1
Port name (Max 8 characters) [PPP00001]? 1
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Service any node: (Y)es (N)o [Y]?
High performance routing: (Y)es (N)o [Y]?
Maximum BTU size (768-4086) [2048]?
Local SAP address (04-EC) [4]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>
APPN config>add link
APPN Station
Port name for the link station [ ]? ppp00001
Station name (Max 8 characters) [ ]? to2210 2
Activate link automatically (Y)es (N)o [Y]?
Adjacent node type: 0 = APPN network node,
1 = APPN end node or Unknown node type,
2 = LEN end node [0]? 0
TG Number (0-20) [0]?
High performance routing: (Y)es (N)o [Y]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>
Figure 187. Add the Port and Link to the EIA Interface for APPN
1 APPN port name for the PPP link on the 2216, which is needed when we define
the station name for that link (2)
2 Station name for the PPP link
In Figure 188 the port and link are configured for the MPC+ interface. Like for the
EIA interface we accept the defaults given by the 2216 and choose the name for
the station to reflect our test environment as seen in Figure 178 on page 180.
186 IBM 2216 and Network Utility Host Channel Connections

Config>p appn
APPN config>add port
APPN Port
Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING,
(M)PC, (S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P [ ]? m
Interface number(Default 0): [0]? 3
Port name (Max 8 characters) [MPC00003]? 1
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Service any node: (Y)es (N)o [Y]?
Maximum BTU size (768-32768) [2048]?
Edit MPC+ Sequencing Interval Timer: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>add link
APPN Station
Port name for the link station [ ]? mpc00003
Station name (Max 8 characters) [ ]? tovtam 2
Adjacent node type: 0 = APPN network node,
1 = APPN end node or Unknown node type [0]? 0
TG Number (0-20) [0]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]? y
Fully-qualified CP name of adjacent node (netID.CPname) []
3 usibmra.ra03m
Edit TG Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
Figure 188. Add the Port and Link to the MPC+ Interface on the 2216
1 APPN port name for the MPC+ link, which is needed when we define the station
name for that link (2)
2 Station name for the MPC+ link
3 CP name of the adjacent node, the host
At last we have to configure our PCs as EN (End Node) and the 2210 as an NN
(Network Node) in our test scenario. For the PCs we use the IBM Personal
Communication software and the Communication Server/2 (including HPR
support) to connect them to an APPN network. The main items to configure are
the fully qualified CP name and the Destination MAC Address from the token-ring
interface, from both, the 2216 and the 2210. Of course this depends on what type
of connection you want to have with the host.
For the 2210 the same rules apply as to the 2216, so we have first set the node
(see Figure 189 on page 188) and then configured the interface for APPN, here
the WAN- (Wide Area Network) and the TR-Interface.
Multipath Channel+ Implementation (MPC+) 187

Config>p appn
APPN config>set node
Enable APPN (Y)es (N)o [Y]? y
Network ID (Max 8 characters) [ ]? usibmra 1
Control point name (Max 8 characters) [ ]? nn2210 2
Enable branch extender or border node
(0=Neither, 1=Branch Extender, 2=Border Node) [0]?
Route addition resistance(0-255) [128]?
XID ID number for subarea connection (5 hex digits) [00000]?
Use enhanced #BATCH COS (Y)es (N)o [Y]?
Use enhanced #BATCHSC COS (Y)es (N)o [Y]?
Use enhanced #INTER COS (Y)es (N)o [Y]?
Use enhanced #INTERSC COS (Y)es (N)o [Y]?
Write this record? [Y]?
The record has been written.
Figure 189. Set up the 2210 for APPN Readiness
1 Set the network ID where the 2210 resides
2 Define the unique CP name for the 2210
The internal interface numbers in the 2210, the affected token-ring configuration
for APPN (add port only) as seen in Figure 190.
APPN config>add port
APPN Port
Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING,
(S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P [ ]? t
Interface number(Default 0): [0]? 0
Port name (Max 8 characters) [T00000]? 1
Enable APPN on this port (Y)es (N)o [Y]? y
Port Definition
Support multiple PU (Y)es (N)o [N]?
Service any node: (Y)es (N)o [Y]?
High performance routing: (Y)es (N)o [Y]?
Maximum BTU size (768-17745) [2048]?
Maximum number of link stations (1-976) [512]?
Percent of link stations reserved for incoming calls (0-100) [0]?
Percent of link stations reserved for outgoing calls (0-100) [0]?
Local SAP address (04-EC) [4]?
Local HPR SAP address (04-EC) [C8]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>
Figure 190. Add the APPN Port for the Token-Ring Interfaces on 2210
1 APPN port name for the token-ring interface
The configuration for the WAN interface for the 2210 is much the same as the EIA
interface for the 2216 as you can see in Figure 191 on page 189. First the port
has to be added and then the link.
188 IBM 2216 and Network Utility Host Channel Connections

APPN config>add port
APPN Port
Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING,
(S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P [ ]? p
Interface number(Default 0): [0]? 1
Port name (Max 8 characters) [PPP00001]? 1
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Service any node: (Y)es (N)o [Y]?
High performance routing: (Y)es (N)o [Y]?
Maximum BTU size (768-4086) [2048]?
Local SAP address (04-EC) [4]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>
APPN config>add link
APPN Station
Port name for the link station [ ]? ppp00001
Station name (Max 8 characters) [ ]? to2216 2
Activate link automatically (Y)es (N)o [Y]?
Adjacent node type: 0 = APPN network node,
1 = APPN end node or Unknown node type,
2 = LEN end node [0]? 0
High performance routing: (Y)es (N)o [Y]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]? y
Fully-qualified CP name of adjacent node (netID.CPname) []?
3 usibmra.nn2216
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>
Figure 191. Adding the Port and Link to the WAN Interface of the 2210
1 APPN port name for the PPP link on the 2210, which is needed when we define
the station name for that link (2)
2 Station name for the PPP link
3 CP name of the adjacent node, the 2216
Now the configuration of our test environment for an APPN connection between
the host and the 2216 via the MPC+ interface is complete (the new configuration
has to be activated in the 2216/2210) and can be monitored as described in 6.5.2,
“APPN Monitoring” on page 198.
For the monitoring of the MPC+ interface in general, see 6.5.1, “Monitoring
ESCON MPC+ Interface” on page 195.
Multipath Channel+ Implementation (MPC+) 189

6.4 2216 MPC+ and TCP/IP
IP is configured on the MPC+ interface in the same manner as any other
interface. The IP address specified in the TCP/IP HOME IP address on the host
must be in the same subnetwork as the MPC+ interface and clearly that must be
a different subnetwork from those already present in the IP network.
Multiple TCP/IP connections over MPC+ interface connections can be
established over a single MPC+ interface. The advantage to this is that if there
are multiple TCP/IP instances on the host, which are on the same IP subnetwork
as the MPC+ interface, multiple connections will be established to the MPC+ IP
address.
The value of maxdata must be less than or equal to the value defined on the host
(MAXBFRU field). The 2216 will never send an IP packet longer than the
maxdata value across the MPC+ group. But the 2216 still can accept larger IP
packets from the host depending on the configuration of other virtual network
handlers using the same base ESCON interface.
For the configuration of the MPC+ interface to the 2216 the same rules apply as
described in the previous explanation for APPN and MPC+ starting from 6.3.7,
“Define the Physical Interfaces” on page 180 up to 6.3.9, “Configure an MPC+
Subchannel” on page 183. Unlike in LCS where a virtual LAN adapter is used, in
MPC+ the 2216 seems to be connected directly to the host as it is shown in
Figure 192 on page 190.
TCP/IP
MPC+
IP Forwarding code
Other IP interfaces
VTAM
Figure 192. MPC+ Appearance between 2216 and Host for TCP/IP
Because we are using normal APPN and TCP/IP operation in our test
environment, no dedicated enhancement is in use like UDP+, which needs to be
on its own MPC+ interface. Also due to the host definitions pointing to the same
TRL for APPN and IP, we are sharing the same MPC+ interface. So the overall
appearance of our test environment between the host and the 2216 looks like
Figure 193.
190 IBM 2216 and Network Utility Host Channel Connections
HOST
Base Net Handler
2216
Logical
Appearance:
host
IP
2216
Rest of IP
Network

TCP/IP
IP Forwarding
code
Other IP
interfaces
MPC+
VTAM
HOST
APPN
2216
Figure 193. MPC+ Appearance between 2216 and Host for TCP/IP and APPN
Taking into account that the MPC+ interface has to be on the same subnet as the
host IP address and all other interfaces on the 2216 have to be on different
subnets our test environment from the IP point of view now looks like Figure 194.
IP
Logical
Appearance:
host
2216
Rest of IP/APPN
Network
APPN
Multipath Channel+ Implementation (MPC+) 191

S/390 TCP/IP Profile
HOME 192.166.236.1
------------------------------
MVS IOCP Definitions
UNITADD=00 & 01
CUADD=1
Figure 194. Test Environment for MPC+ and TCP/IP
To run IP on the 2216 all the affected interfaces have to be configured. Each
interface has to be added with an IP address and the new configuration has to be
activated. As for APPN, the channel connection which has to be set up is not the
ESCON interface itself but the virtual MPC+. The MPC+ interface has the number
3 in our environment as seen in Figure 195, shown via the list device command
from the config prompt.
Figure 195. List of the Devices inside the 2216
To do so first we have to move to the IP protocol command prompt and then add
the IP addresses regarding our test environment (see Figure 194 on page 192)
via the add address command. We directly place the command add address net
IP-address Netmask, where net is the internal interface number of the 2216,
IP-address is the address that belongs to this interface, and Netmask is the subnet
mask of the IP network. These steps are seen in Figure 196.
192 IBM 2216 and Network Utility Host Channel Connections
16.0.0.1
RA03
LPAR
1
TR
2216
16.0.0.16
LAN
RA28
LPAR
2
ESCD
MPC+
CC
C9
WAN
RA39
LPAR
4
S/390
PPP
192.166.236.2
2210
TR
192.194.200.2
10.0.0.10
2216 Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 EIA-232E/V.24 PPP Slot: 8 Port: 0
Ifc 2 ESCON Channel Slot: 3 Port: 1
Ifc 3 MPC - ESCON Channel Base Net: 2

2216 Config>
2216 Config>p
Protocol name or number [IP]?
Internet protocol user configuration 1
2216 IP config>add addr 0 16.0.0.1 255.255.255.0
2216 IP config>add addr 1 192.194.200.2 255.255.255.0
2216 IP config>add addr 3 192.166.236.2 255.255.255.0
Figure 196. Adding IP Address to the 2216 Interface
1 Setting the IP addresses/Netmask for the TR/EIA/MPC+ on the 2216.
At last we have to set up a routing protocol inside the 2216. In our case we
enabled RIP as seen in Figure 197 on page 193 and a list of IP addresses for the
2216.
2216 IP config>ena rip
2216 IP config>li addr
IP addresses for each interface:
intf 0 16.0.0.1 255.255.255.0 Local wire broadcast, fill 1
intf 1 192.194.200.1 255.255.255.0 Local wire broadcast, fill 1
intf 2 IP disabled on this interface
intf 3 192.166.236.2 255.255.255.0 Local wire broadcast, fill 1
Figure 197. List of IP Addresses in the 2216
Referring to our test environment as seen in Figure 194 on page 192 we have to
set up the PCs with the requested address and subnetmask. Also the interfaces
of the 2210 have to be configured with the requested parameters. Figure 198
shows the configuration of the TR interface (Ifc 0) and the WAN Interface (Ifc 1).
2210 *t6
2210 Config>p
Protocol name or number [IP]?
Internet protocol user configuration 1
2210 IP config>add addr 0 10.0.0.1 255.255.255.0
2210 IP config>add addr 1 192.194.200.2 255.255.255.0
Figure 198. Adding IP Addresses to the 2210 Interface
1 Setting the IP addresses/Netmask for the TR/EIA on the 2210.
As for the 2216 we enable RIP for the 2210 as the routing protocol in our test
scenario, which is the last step to make the 2210 ready for our IP test network.
Figure 199 on page 194 shows the command for enabling the routing protocol
and gives the list of the actual used IP interfaces.
Multipath Channel+ Implementation (MPC+) 193

6.5 Monitoring ESCON Interface
2210 IP config>ena rip
2210 IP config>li addr
IP addresses for each interface:
intf 0 10.0.0.1 255.255.255.0 Local wire broadcast, fill 1
intf 1 192.194.200.2 255.255.255.0 Local wire broadcast, fill 1
.....
...
Figure 199. Enable RIP and List of IP Addresses in the 2210
Now the configuration of our test environment for an IP connection between the
host and the 2216 via the MPC+ interface is complete and can be monitored as
described in 6.5.3, “IP Monitoring” on page 200.
For monitoring the ESCON and the MPC+ interface see 6.5, “Monitoring ESCON
Interface” on page 194.
The monitoring commands are available from the GWCON prompt which you get
via the T5 process. You access the talk 5 commands that show the status of
channel resources hierarchically as follows:
• From the * prompt, type talk 5 and press Enter to reach the + prompt.
• From the + prompt, type int and press Enter and note the logical interface
number for the physical ESCON or PCA interface you are interested in. The
physical interface is commonly called the base net and can have a number of
LSA, LCS, or MPC+ virtual interfaces defined on top of it. The base net and all
virtual interfaces each have a different logical interface number (see Figure
200).
2216 *t5
2216 +int
Self-Test Self-Test Ma
Net Net' Interface Slot-Port Passed Failed
0 0 TKR/0 Slot: 1 Port: 1 2 1
1 1 PPP/0 Slot: 8 Port: 0 1 0
2 2 ESCON/0 Slot: 3 Port: 1 1 0
3 2 MPC/0 Slot: 0 Port: 0 1 2
Figure 200. Interface List via GWCON
• From the + prompt, type net base n number and press Enter to reach the
ESCON or PCA console subprocess. The command prompt changes to
ESCON>or PCA> as appropriate (see Figure 201).
2216 +net 2
ESCON Base Console
2216 ESCON>
Figure 201. Change to the ESCON Base Net Prompt
At these prompts, you can use the li nets command to see the current state of
every (LSA, LCS, MPC+) virtual interface using this base net. You can also type
194 IBM 2216 and Network Utility Host Channel Connections

li sub to view the currently running subchannel configuration for this base net
(see Figure 202).
2216 ESCON>li net
Net: 3 Type: MPC+ Group Number: 0
Net state: Up 1
2216 ESCON>li sub
The following subchannels are defined:
2 Local address: 00 Device address: 00 CU Logical Address: 01
Link: CC LPAR: 01
3 Type: MPC+
The following lantypes/lannums are using this subchannel:
4 Group No.: 0
Local address: 01 Device address: 01 CU Logical Address: 01
Link: CC LPAR: 01
Type: MPC+
The following lantypes/lannums are using this subchannel:
Group No.: 0
Figure 202. List of Net and Subchannels from ESCON Base Net Prompt
1 Net State State of the network: Up, Down, Disabled, Not Present, HW
Mismatch, or Testing. Up Indicates that the link is up.
2 Local Address The subchannel address index used internally by the device.
3 Type Type of virtual interface: LCS, LSA, or MPC+
4 Group Number The group number is used internally by the device to identify
a virtual MPC+ net interface on the channel adapter.
6.5.1 Monitoring ESCON MPC+ Interface
From the base net ESCON> or PCA> prompt or directly from the + prompt, type
net virtual net number and press Enter to see more detail on a particular virtual
interface that uses this base net. The command prompt changes to LSA>, LCS>,
or MPC+>, depending on the type of virtual interface you select.
Each of these prompts supports a list command, to show configuration and
current status information relevant to the virtual interface type (see Figure 203).
2216 +net 3
MPC+ Console
2216 MPC+>
2216 MPC+>list ?
MPc group
SUbchannel
CM
COnnection
Figure 203. List of Subcommand for the MPC+ Interface
The next figures reflect these listing commands one by one regarding our test
environment.
The mpc command displays information about the MPC+ group. It displays the
local and remote registration token, if known, and the current state of the MPC+
group. Also, if the MPC+ is for the exclusive use of UDP+, that will be indicated. If
the MPC+ group is not for the exclusive use of UDP+, exclusive use will not be
mentioned in the display.
Multipath Channel+ Implementation (MPC+) 195

Note: UDP+ is not supported on a Parallel Channel Adapter (PCA).
2216 MPC+>list mpc
MPC+ Group
Local registration token = 0902295FA000000000 1
Remote registration token = 050001013F 2
state = Active 3
Outbound protocol data blocking is enabled for the MPC+ Group
Figure 204. List of MPC+ Group
1 Local registration token Token in the device representing this MPC+ group.
2 Remote registration token Token on the host representing this MPC+ group.
This field is blank if not known.
3 State The state of the MPC+ group: Active and usable.
The subchannel command shows information about the subchannels that are part
of the MPC+ group. It shows the local subchannel number, logical partition
number, link address, control unit (CU) logical address, device address, type of
subchannel (READ or WRITE), and the current state of the subchannel. The type
should be the opposite of what is configured at the host.
2216 MPC+>li sub
MPC+ Subchannels
Local Link CU Log. Device
number LPAR addr address address type state
------- ----- ----- ------- --------- ---------- ----------
1 2 3
1 1 CC 1 1 READ Active
0 1 CC 1 0 WRITE Active
Figure 205. List of MPC+ Subchannels
1 Local number The subchannel address index used internally by the
device.
Note: CU logical address, link address, and LPAR are
displayed for ESCON adapters only.
2 Type Whether this is a read or write subchannel.
3 State The state of the subchannel: Active. The subchannel is
active and part of an MPC+ group.
The cm command shows information on the connection manager that is running
on the MPC+ group. The information shown is the group token, the type of
connection manager, and the current state.
2216 MPC+>li cm
MPC+ Connection Managers(CM)
Group Token type state
------------------------- ------- ----------
1 2
09025F1A5800000052 PTP Active
Figure 206. List of MPC+ Connection Manager
196 IBM 2216 and Network Utility Host Channel Connections

1 Type PTP Point to point
2 State Active Active and usable
The connection command shows information on the connections running on the
MPC+ group/connection manager. The information shown is in two parts: the
virtual circuit and the connections under the virtual circuit. The following
information is shown for the virtual circuit: the local and remote virtual circuit
tokens, the protocol type, and the current state (see Figure 207 on page 197).
2216 MPC+>li connect
MPC+ Connections
Virtual Circuit Token = 09025F614000000055 1
Remote Registration Token(s) = 050001015B 2
Protocol = TCP/IP 3, State = Active-both sides 4
Local Connection Token = 09025F659000000059 5
Remote Connection Token = 0500010164 6
State = Active 7
Local IP address = 192.166.236.2 8
Destination IP address = 192.166.236.1 9
Virtual Circuit Token = 09025F64CC00000056
Remote Registration Token(s) = 0500010147
Protocol = APPN, State = Active-both sides
Local Connection Token = 09025F583800000058
Remote Connection Token = 0500010149
State = Active
Figure 207. List of MPC+ Connections
1 Local Virtual Circuit Token Token in the device representing this virtual
circuit.
2 Remote Virtual Circuit Token Token on the host representing this virtual
circuit. This field is blank if not known.
3 Protocol The upper layer protocol that this virtual circuit is
using.
4 State Active-both sides Both sides of the virtual circuit are accepting
calls (connections) for this virtual circuit.
The information shown for the connection is the local and remote connection
tokens and the current state. For IP protocols (that is, UDP+ and TCP/IP), the
local and destination IP addresses associated with the connection will also be
shown, if known.
5 Local Connection Token The token in the device representing this
connection.
6 Remote Connection Token The token on the host representing this
connection. This field is blank if not known.
7 States Active Active and usable.
Multipath Channel+ Implementation (MPC+) 197

8 Local IP address The IP address on the MPC+ interface in the
device that is associated with this connection. This
field will be displayed only for IP protocols.
9 Destination IP Address The IP address on the host that is associated with
this connection. This field will be displayed only for
IP protocols.
To back out from any of these nested levels, type exit and press Ctrl-p to go back
to the * prompt.
For more examples and a detailed explanation of the output of these commands,
see also the chapter "Configuring and Monitoring the ESCON and Parallel
Channel Adapters" in the Nways Multiprotocol Access Services Software User's
Guide Version 2, Release 2, SC30-3886.
Looking at the figure of our test environment (see Figure 208) with APPN and
TCP/IP active there are also different monitoring commands available to check
out these protocols. We will place here some of these commands which are
useful regarding our scenario.
S/390 TCP/IP Profile
HOME 192.166.236.1
------------------------------
NETID=USIBMRA
SCCPNAME=RA03M
------------------------------
MVS IOCP Definitions
UNITADD=00 & 01
CUADD=1
16.0.0.1
usibmra.mainz
Figure 208. Test Environment with APPN and TCP/IP
6.5.2 APPN Monitoring
Use the following procedure to access the APPN monitoring commands. This
process gives you access to an APPN’s monitoring process.
198 IBM 2216 and Network Utility Host Channel Connections
RA03
LPAR 1
TR
2216
16.0.0.16
LAN
RA28
LPAR 2
ESCD
CC
WAN
RA39
LPAR 4
S/390
C9
usibmra.nn2216
MPC+ 192.166.236.2
PPP
2210
TR
10.0.0.10
192.194.200.2
usibmusibmra.nn2210
usibmra.valencia

At the OPCON prompt, enter talk 5. After you enter the talk 5 command, the
GWCON prompt (+) displays on the terminal. If the prompt does not appear when
you first enter the configuration, press Return again. After you got the GWCON
prompt (+) type protocol APPN.
Use the list command to display information about the APPN configuration. Besides
the list command there are more monitoring commands for APPN available (such
as APING/ DUMP/ MOEMORY/ RESTART/ STOP/ TN3270/ TRANSMIT) to get detailed information
about specific items, but we will focus here on only some of the list commands. For
more information about APPN monitoring refer to Nways Multiprotocol Access
Services Protocol Configuration and Monitoring Reference Vol. 2 Version 3.2,
SC30-3885.
The list port command displays a summary table of all ports (Figure 209).
2216 *t5
2216 +p appn
2216 APPN >list port
Intf Name DLC Type HPR State
============================================================
0 T00000 IBMTRNET TRUE ACT_PORT
1 PPP00001 PPP TRUE ACT_PORT
3 MPC00003 MPC+ TRUE ACT_PORT
Figure 209. List of Ports in APPN
The list link command displays a summary table of all links (Figure 210).
2216 APPN >li link
Name Port Name Intf Adj CP Name Type HPR State
========================================================================
TO2210 PPP00001 1 USIBMRA.NN2210 NN ACTIVE ACT_LS
TOVTAM MPC00003 3 USIBMRA.RA03M NN ACTIVE ACT_LS
@@0 T00000 0 USIBMRA.MAINZ EN ACTIVE ACT_LS
Figure 210. List of Links in APPN
In Figure 210 we see also a LINK for the token-ring interface even we don’t define
one. This link is dynamically added which is marked by the @@ sign. One of the
PCs is connected (as EN) on this link with HPR active.
The list cp command displays a table of all cp sessions (Figure 211).
2216 APPN >li cp
CP Name Type Status Connwinner ID Conloser ID
========================================================================
USIBMRA.MAINZ EN Active 3646DEA4 3646DEA0
USIBMRA.NN2210 NN Active 3646DE8D 3646DE8B
USIBMRA.RA03M NN Active 3646DE70 3646DE73
Figure 211. List of CP on APPN
The list rtp command displays a table of all RTP connections (Figure 212 on
page 200).
Multipath Channel+ Implementation (MPC+) 199

2216 APPN >li rtp
RTP PARTNER TABLE:
Remote Partner Name Remote Boundary Name TG Number
======================================================
USIBMRA.MAINZ USIBMRA.MAINZ + -1
RTP CONNECTION TABLE:
TCID CP Name ISR APPC Pathswitch Alive COS TPF TG Number
=================================================================================
1E9F7E8 USIBMRA.RA03M 0 1 180 180 CPSVCMG 21
1EA8F68 USIBMRA.RA03M 0 1 180 180 CPSVCMG 21
1EA9888 USIBMRA.NN2210 0 1 180 180 CPSVCMG 21
1EA8648 USIBMRA.NN2210 0 1 180 180 CPSVCMG 21
1EB9160 USIBMRA.MAINZ 0 2 180 61 CPSVCMG 21
1EB8840 USIBMRA.NN2210 0 0 0 180 RSETUP 21
1EB8CD0 USIBMRA.RA03M 0 0 0 180 RSETUP 21
1EB9A80 USIBMRA.MAINZ 0 0 0 61 RSETUP 21
1EC3B20 USIBMRA.MAINZ 0 1 180 61 SNASVCMG 21
1EC2450 USIBMRA.MAINZ 0 1 180 61 #INTER 21
Figure 212. RTP Connection Table
Rapid transport protocol is a connection-oriented, full-duplex transport protocol
used in HPR for transporting data across HPR subnets. All data flowing over an
RTP connection is carried in network layer packets (NLPs).There is no
connection information held at intermediate nodes; only the endpoints know the
route. RTP provides end-to-end recovery with selective retransmission,
nondisruptive path switch, and adaptive rate-based (ARB) flow and congestion
control procedures. RTP provides translation between base APPN intermediate
session routing (ISR) and HPR protocols for sessions that have both HPR and
non-HPR portions. RTP can be implemented on both end nodes and network
nodes.
6.5.3 IP Monitoring
For IP monitoring, an important command is the dump command (Figure 213). Of
course, there are a lot more commands available to monitor the IP protocol. For
detailed information about these, please refer to Nways Multiprotocol Access
Services Protocol Configuration and Monitoring Reference Vol. 1 Version 3.2,
SC30-3884.
2216 *t 5
CGW Operator Console
2216 +
2216 +p
Protocol name or number [IP]?
2216 IP>dump
Type Dest net Mask Cost Age Next hop(s)
RIP 10.0.0.0 FF000000 2 20 192.194.200.2
Sbnt 16.0.0.0 FF000000 1 139 None
Dir* 16.0.0.0 FFFFFF00 1 144 TKR/0
Dir* 192.166.236.0 FFFFFF00 1 154 MPC/0
Dir* 192.194.200.0 FFFFFF00 1 161 PPP/0
Figure 213. Dump Command on the IP Protocol
200 IBM 2216 and Network Utility Host Channel Connections

6.6 2216 MPC and UDP
6.6.1 2216 MPC+ Host Parameter Relationships
Before we can attach the 2216 to an ESCCON channel, the host must be
configured correctly.The following steps are required to define a 2216 connection
to the host for HPDT (High Performance Data Traffic) UDP.
1. Define the 2216 to the host channel subsystem using either the host I/O
configuration program (IOCP) or hardware configuration definition (HCD)
program. The IOCP macros needed for defining the 2216 to the host are:
• RESOURCE Statement: Identifies logical partitions
• CHPID Statement: Identifies type of channel connection and who uses it
• CNTLUNIT and IODEVICE Statements: Identify the 2216 connection to the
host.
2. Define the 2216 control unit to the host operating system.
3. Define the 2216 and configuration to the host program.
• The transport resource list (TRL) major node
4. Configure HPDT UDP using OS/390 TCP/IP OpenEdition (OE)
HPDT UDP can connect to the 2216 only through an ESCON channel adapter
using MPC+. OS/390 TCP/IP OpenEdition must be installed on the host.
Note
Before you configure your S/390 host for HPDT UPD, you must have APAR
#OW31305 installed.
HPDT UDP commands are used to configure and control HPDT UDP resources.
See OS/390 TCP/IP Update Guide, GC31-8553 for details on installing and using
OE for HPDT UDP.
To configure and activate an HPDT UDP connection on the 2216, issue the
oeifconfig command, shown in the following example.
oeifconfig interface_name source_IP_address destination_IP_address mtu nnnn
where:
interface_name
is the name of the TRL for the HPDT UDP connection. This will cause the TRL
to be activated if it is not already active.
source_IP_address
is the local IP address on the host for HPDT UDP connection. This local IP
address must be in the same IP subnetwork as the IP address coded for the
UDP+ MPC+ network handler in the 2216.
destination_IP_address
is the destination IP address in the 2216 for this HPDT UDP connection. This
destination IP address must equal the IP address coded on the UDP+ MPC+
network handler in the 2216.
Multipath Channel+ Implementation (MPC+) 201

mtu nnnn
where nnnn is the maximum transmission unit size for the HPDT UDP
connection.
This mtu size must be equal to the maxdata value coded on the UDP+ MPC+
network handler in the 2216. If the values are not equal, then the HPDT UDP
connection will not come up.
202 IBM 2216 and Network Utility Host Channel Connections
Note: Because this is a point-to-point connection, there is no need to code the
netmask parameter on this command.
The relationship between the definition on the host and in the 2216 can be
seen in Figure 214 on page 203.

2216/NetworkUtility (MPC+) Parameter Relationships for UDP
HPDT UDP ACT/CONFIG
VTAM Start List
oeifconfig UDP2216A 192.166.240.1 192.166.240.2 mtu 32768
oeroute add default 192.166.240.2
MVS IOCP Definitions
VTAM Transport Resource List Major Node
RESOURCE PART=((A4,4))
CHPID PATH=((2C),TYPE=CNC,PART=(A4),SWITCH=E1)
TRL2216 VBUILD TYPE=TRL
UDP2216A TRLE LNCTL=MPC,
MAXBFRU=9,
READ=(286)
WRITE=(287),
REPLYTO=3.0
Figure 214. MPC+ Host Parameter Relationship for UDP
CNTLUNIT CUNMBR=0280,PATH=2C,CUADD=1,
UNITADD=((00,32)),LINK=C9,UNIT=3172
IODEVICE UNIT=3172,ADDRESS=((280,032)),
CUNMBR=0280
SYS1.PARMLIB(BPXPRMxx)
FILESYSTYPE TYPE(CINET)
ENTRYPOINT(BPXTCINT)
NETWORK DOMAINNAME(AF_INET)
DOMAINNUMBER(2)
MAXSOCKETS(10000)
TYPE(CINET)
INADDRANYPORT(4000)
INADDRANYCOUNT(2000)
LPAR 4
CHPID=2C
192.166.240.1
CC
ESCON
Director E1
C9
192.166.240.2
2216
SUBFILESYSTYPE NAME(OESTACK)
TYPE(CINET)
ENTRYPOINT(BPXUIINT)
ESCON MPC+ Definitions:
PC Definitions:
Default GW=16.0.0.1
IP Address=16.0.0.16
LPAR 4
CU 1
Device 07 (READ)
Device 06 (Write)
Link CC
'MPC maxdata'=32768
16.0.0.16
16.0.0.1 Token
Ring
'MPC-IP Address'=192.166.240.2
TR: IP Address=16.0.0.1
Multipath Channel+ Implementation (MPC+) 203

6.6.2 Host Definitions
The following configuration definitions are based on our test environment.
6.6.2.1 IOCP and MVS Operating System Definitions
The IOCP definitions for the 2216 with ESCON channel attached are shown in
Figure 215 on page 204. These definitions are the same ones used for LCS/LSA.
The CNTLUNIT statement defines the path from the host to the 2216 and is used
for the IOCP definitions.
The 2216 must be defined to an IBM Multiple Virtual Storage/Extended
Architecture (MVS/XA) or MVS/ESA operating system. This definition is
accomplished by updating the MVS control program with an entry for the 2216 in
the IODEVICE macro.
The IODEVICE statement in Figure 215 is for the MVS operating system.
RESOURCE PARTITION=((A1,1),(A2,2),(A3,3),(A4,4)1,(A5,5),(C1,6), *
(C2,7))
CHPID PATH=(2C),SHARED, *
PARTITION=((A1,A2,A3,A4),(A1,A2,A3,A4,A5)),SWITCH=E1, *
TYPE=CNC
CNTLUNIT CUNUMBR=0280,PATH=(2C),UNITADD=((00,032)) 2 ,LINK=(C9), *
CUADD=1 3 ,UNIT=3172
CNTLUNIT CUNUMBR=02A0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=2,UNIT=3172
CNTLUNIT CUNUMBR=02C0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=4,UNIT=3172
IODEVICE ADDRESS=(280,032),UNITADD=00,CUNUMBR=(0280),STADET=Y, *
PARTITION=(A1),UNIT=3172
IODEVICE ADDRESS=(2A0,032),UNITADD=00,CUNUMBR=(02A0),STADET=Y, *
PARTITION=(A2),UNIT=3172
IODEVICE ADDRESS=(2C0,032),UNITADD=00,CUNUMBR=(02C0),STADET=Y, *
PARTITION=(A4),UNIT=3172
Figure 215. MPC+: IOCP and MVS Operating System Definitions
1 In this scenario we will connect to LPAR 4.
2 UNITADD defines the range of addresses reserved for this control unit. The first
number is the hex of the first subchannel assigned to this control unit. The second
number is the decimal number of subchannels being assigned to this control unit.
The parameter device address defined in the 2216 must be in this range of
addresses. In this scenario we will use device address 04.
3 This value identifies the control unit address of the 2216. For the 2216, each
LPAR on a given CHPID must have a unique CUADD value. This value must
match the control unit parameter specified in the 2216.
6.6.2.2 VTAM Definitions for an MPC+ Connection
You need to define a TRL (Transport Resource List) exclusively for the MPC+
connection to the 2216 using the UDP protocol. The TRL from our test scenario is
shown in Figure 216.
204 IBM 2216 and Network Utility Host Channel Connections

**********************************************************************
* *
* VTAM TRL NODE FOR 2216 MPC *
**********************************************************************
TRL2216 VBUILD TYPE=TRL 1
UDP2216A 2 TRLE LNCTL=MPC, 3 X
MAXBFRU=9, 4 X
READ=286, 5 X
WRITE=287, X
MPCLEVEL=HPDT, X
REPLYTO=3.0 6
Figure 216. VTAM Transport Resource List (TRL) Definition
Notes:
1 TYPE must be TRL.
2 UDP2216A is the name that identifies the TRL. It must match what is specified
as the interface_name in the oeifconfig command for the HPDT UDP
activation.
3 LNCTL identifies the connection type. It must be LCNTL=MPC.
4 MAXBFRU is the number of 4K pages per read subchannel.
5 READ/WRITE specifies the subchannels in the MPC+ group and indicates
their direction. The subchannel numbers must be in the range of addresses
specified in the IODEVICE statement in the IOCP definition. There can be
multiple READ and WRITE parameters in the TRLE statement, but there must
be at least one of each.
Note: The designations READ and WRITE here are from the host
perspective. In the 2216 MPC+ definition, the designations are from the 2216.
Therefore, subchannels designated as READ on the host must be designated
as WRITE on the 2216, and vice versa.
6 REPLYTO is the reply timeout value in seconds.
6.6.2.3 HPDT UDP Definitions
High Speed UDP (previously documented as HPDT for UDP) is one part of the
HSAS (High Speed Access Service). It extends the existing HPDT services
capability introduced in VTAM V4R4 to include support for applications using the
User Datagram Protocol (UDP) of the TCP/IP protocol suite. High Speed UDP
reduces CPU cycle consumption and achieves a more efficient transfer of data.
OS/390 applications that issue OpenEdition socket calls over UDP can achieve
these benefits when transferring data over certain high-bandwidth HPDT
configurations.
High Speed UDP supports the following applications:
• DCE (Distributed Computing Environment)
• NFS (Network File System)
• SAP R/3 (Systems, Applications, and Products in Data Processing)
You must define the OpenEdition Common INET physical file system to include
the High Speed Access Services Communication stack, which is done via the
SUBFILESYSTYPE NAME(OESTACK). You must code this statement exactly as
shown by 1 in Figure 217 on page 206, and you can code only one such
Multipath Channel+ Implementation (MPC+) 205

statement. Unlike other IP communication stacks that require a separate address
space, the HSAS communications stack resides within the OpenEdition kernel.
Define the HSAS communication stack through the BPXPRMxx member in
SYS1.PARMLIB as seen in Figure 217 on page 206.
FILESYSTYPE TYPE(CINET)
ENTRYPOINT(BPXTCINT)
NETWORK DOMAINNAME(AF_INET)
DOMAINNUMBER(2)
MAXSOCKETS(10000)
TYPE(CINET)
INADDRANYPORT(4000)
INADDRANYCOUNT(2000)
SUBFILESYSTYPE NAME(OESTACK) 1
TYPE(CINET)
ENTRYPOINT(BPXUIINT)
Figure 217. Sample for BPXPRMxx Member
Next configure and activate the High Speed Access Services using the oeifconfig
command.
oeifconfig UDP2216A 2 192.166.240.1 3 192.166.240.2 4 mtu 32768 5
2 TRLNameinVTAM
3 Host IP address
4 2216 MPC+ IP address
5 Maximum transmission unit size (=maxdata on 2216 MPC+ channel)
Take in account that routes are needed to reach the destination hosts. This has
to be done via the oroute command which adds or deletes an entry in the HSAS
routing table. Only static routes can be defined. For more detailed information on
HSAS and their commands refer to:
• OS/390 eNetwork Communications Server High Speed Access Services
User’s Guide, GC31-8676
• OS/390 TCP/IP Update Guide, GC31-8553
6.6.2.4 Network Environment Description
The general logical appearance between the 2216 and the host for UDP+ is
shown in Figure 218 on page 207. For the scenario we use in our test
environment see Figure 219 on page 207.
206 IBM 2216 and Network Utility Host Channel Connections

HPDT
MPC+
IP Forwarding code
Other IP interfaces
VTAM
HOST
2216
Figure 218. MPC+ Appearance between 2216 and Host for UDP
192.166.240.2
Base Net Handler
RA03
LPAR
1
S/390
16.0.0.16
RA28
LPAR
2
ESCD
MPC+
2216
LAN
TR
Figure 219. Overview of the Test Environment
CC
C9
RA39
LPAR
4
Appearance:
Data Base Server
Host Gateway
Application
Servers and
users
16.0.0.1
host
2216
Campus
network
MVS IOCP Definitions
UNITADD=06 & 07
CUADD=1
IP
Multipath Channel+ Implementation (MPC+) 207

6.6.2.5 2216 Configuration
The following steps must be followed in order to configure MPC+ support on the
2216 for HPDT UDP connection to the host:
• Add the physical interface to the 2216.
• Add an MPC+ virtual interface.
• Configure an MPC+ virtual interface.
• Configure the MPC+ Subchannel.
• Add IP Address to the interface.
In this section we will perform these items step by step and explain the
configuration parameters with regard to our test environment which is shown in
Figure 219 on page 207. Due to this, not all config parameters will be highlighted
here so we recommend that you check your network. For further details about
those parameters please see:
• Nways Multiprotocol Access Services Software User's Guide Version 2,
Release 2, SC30-3886
• Nways Multiprotocol Access Services Protocol Configuration and Monitoring
Reference Vol. 1 Version 3.2, SC30-3884
• Nways Multiprotocol Access Services Protocol Configuration and Monitoring
Reference Vol. 2 Version 3.2, SC30-3885
Add the Physical Interface
In our test environment we are going to add the physical interfaces by typing the
T6 add device command on the command line:
• LAN adapter (token-ring)
• ESCON adapter
Figure 220 reflects the result of adding the devices to the 2216 (TR/ESCON).
2216 Config>
2216 Config>add dev token
Device Slot #(1-8) [1]? 1
Device Port #(1-2) [1]? 1
Adding Token Ring device in slot 1 port 1 as interface #0
Use "net 0" to configure Token Ring parameters
2216 Config>add dev escon
Device Slot #(1-8) [1]? 3
Adding ESCON Channel device in slot 3 port 1 as interface #1
Use "net 1" to configure ESCON Channel parameters
Figure 220. Adding the Physical Interfaces to the 2216
Via the list device command (see Figure 221 on page 208) from the config
command prompt we can get the logical interface numbers, the device type and
their physical position inside the 2216.
2216 Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 ESCON Channel Slot: 3 Port: 1
Figure 221. List of the Devices inside the 2216
208 IBM 2216 and Network Utility Host Channel Connections

After the add dev command the net parameters have to be set up. We will add
here in detail only the parameter for the ESCON adapter which is the net number
1 in our scenario (see Figure 221).
Add/Configure MPC+Virtual Interface
Now that the physical interfaces has been configured we can start to use the add
mpc command (see Figure 222) to add an MPC+ virtual interface and get to the
ESCON Add Virtual> prompt from which you can enter other interface and
subchannel parameters:
Config>net 1
ESCON Config>add mpc
ESCON Add Virtual>
Figure 222. Adding the MPC+ Virtual Interface
There are eight commands available to configure the MPC+ virtual interface for
an ESCON adapter:
•acklen
•blktimer
•disable_o, enable_o outbound protocol blocking
•disable, enable udp+ exclusive use
•maxdata
•reply timeout
•sequencing interval timer
• subchannel
For our UDP+ connection, the most important commands are maxdata, enable
udp+, and of course subchannel. The maxdata and enable udp+ commands are shown
in Figure 223 on page 209.
2216 ESCON Add Virtual>maxdata 32768 1
2216 ESCON Add Virtual>ena 2
Enabling UDP+ Exclusive Use of MPC Group.
Figure 223. Set maxdata and enable UDP+ for the MPC+ Group
1 maxdata bytes Maximum size of data handled by this virtual network handler.
This value has to match the mtu size of the oeifconfig
command on the host. This parameter applies to ESCON
interfaces only.
2 enable udp+ exclusive use To dedicate the MPC+ interface to UDP+. This
means that only HPDT UDP on the host will be able to
establish a connection across this MPC+ group. UDP+ can
never share an MPC+ group with other protocols (for
example, APPN, TCP/IP).
The subchannel command places you at the next prompt based on the value of the
command as shown in Figure 224 on page 211. The command can be one of the
following:
Multipath Channel+ Implementation (MPC+) 209

addr sub addr Adds a read subchannel and displays the ESCON Add MPC+
Readsubchannel> prompt from which you can add device
address, LPAR number, link address, and CU logical address.
addw sub addw Adds a write subchannel and displays the ESCON Add MPC+
Write subchannel> prompt from which you can add Device
Address, LPAR number, Link Address, and CU Logical
Address.
mod sub mod Modifies a configured MPC+ subchannel. It lists the
configuration for the configured MPC+ subchannels and allows
you to modify one of them by specifying the sub number from
the list. Once you have selected the subchannel, you can
change the device address, LPAR number, link address, and
CU logical address.
delete sub delete Deletes a configured MPC+ subchannel. It lists the
configuration for the configured MPC+ subchannels and allows
you to delete one of them by specifying the sub number from
the list.
list list sub List information for the MPC+ subchannels
From the ESCON Add Virtual> prompt the subchannels have to be added and
configured to reflect the definitions made on the host. Remember a subchannel
defined as read to VTAM is a write subchannel for the 2216 and a subchannel
defined as write to VTAM is a read subchannel for the 2216.
Configure an MPC+ Subchannel
There are four parameters required to configure each, the read and the write
subchannel. At least one read and one write channel have to be configured so
that the MPC+ connection can be activated. You can get to the ESCON Add
MPC+ Read/Write Subchannel> prompt after you have entered the sub addr/addw
command from ESCON Add Virtual> prompt. The configuration of the parameter
reflecting our test environment is seen in Figure 224 on page 211 and has to
match the host parameter.
210 IBM 2216 and Network Utility Host Channel Connections

2216 ESCON Add Virtual>sub addr
2216 ESCON Add MPC+ Read Subchannel>device 7 1
2216 ESCON Add MPC+ Read Subchannel>cu 1 2
2216 ESCON Add MPC+ Read Subchannel>lpar 4 3
2216 ESCON Add MPC+ Read Subchannel>link cc 4
2216 ESCON Add MPC+ Read Subchannel>ex
2216 ESCON Add Virtual>sub addw
2216 ESCON Add MPC+ Write Subchannel>device 6
2216 ESCON Add MPC+ Write Subchannel>cu 1
2216 ESCON Add MPC+ Write Subchannel>lpar 4
2216 ESCON Add MPC+ Write Subchannel>link cc
2216 ESCON Add MPC+ Write Subchannel>ex
2216 ESCON Add Virtual>sub li
Read Subchannels:
Sub 0 Device address : 7 LPAR number : 4
Link address : CC CU Logical Address : 1
Write Subchannels:
Sub 1 Device address : 6 LPAR number : 4
Link address : CC CU Logical Address : 1
2216 ESCON Add Virtual>ex
2216 ESCON Config>ex
ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]: y
2216 Config>
Figure 224. Configure Read and Write Subchannel to the MPC+
The four subparameters for addr/addw and their meanings are the following:
1 device The unit address transmitted on the channel path to select a 2216
device. It is also referred to as subchannel number in S/370 I/O
architecture. It is a two-digit hexadecimal value that can range from
00-FF. This value is defined on the host IOCP by the UNITADD
statement on the CNTLUNIT macro instruction for the real device.
2 cu The control unit address defined on the host for the 2216. This value is
defined on the host Input/Output configuration program (IOCP) by the
CUADD statement on the CNTLUNIT macro instruction. The control
unit address must be unique for each logical partition defined on the
same host.
3 lpar Logical partition number. This allows multiple logical host partitions,
(LPARs) to share one ESCON channel. This value is defined on the
host Input/Output configuration program (IOCP) by the RESOURCE
macro instruction. If the host is not using EMIF, use the default of 0 for
the LPAR number.
4 link If one ESCON Director (ESCD) is in the communication path, the link
address is the ESCD port number that is attached to the host. If two
ESCDs are in the path, it is the host-side port number of the ESCD
defined with the dynamic connection. When no ESCD is in the
communication path, this value must be set to X'01'.
The list device command from the config prompt reflects the new status of the
interfaces for the 2216. The MPC+ has its own interface number as shown in
Figure 225 below and is now ready to be configured to its protocol needs which
should run over these interfaces.
Multipath Channel+ Implementation (MPC+) 211

2216 Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 ESCON Channel Slot: 3 Port: 1
Ifc 2 MPC - ESCON Channel Base Net: 1
Figure 225. List of the Devices inside the 2216
Add IP Address
To run HPDT UPD via our MPC+ interface we have to set an IP address for the
virtual MPC+ channel which has to match the destination_IP_address from the
oeifconfig command placed at activation/ configuration time on the host. Because
the MPC+ connection is seen as PTP (point-to-point) the address has to be in the
same subnetwork as the source_IP_address.
In our test environment we also have to define the IP address of the token-ring to
which we connect a PC to proof the functioning of the UDP PIPE to the host via
the ping command.
2216 Config>p
Protocol name or number [IP]?
Internet protocol user configuration
2216 IP config>add addr 0 16.0.0.1 255.255.255.0 1
2216 IP config>add addr 2 192.166.240.2 255.255.255.0 2
2216 IP config>li addr
IP addresses for each interface:
intf 0 16.0.0.1 255.255.255.0 Local wire broadcast, fill 1
intf 1 IP disabled on this interface
intf 2 192.166.240.2 255.255.255.0 Local wire broadcast, fill 1
2216 IP config>ex
2216 Config>write 3
Config Save: Using bank A and config number 4
216 Config>
2216 *reload y 4
Figure 226. Add IP Address to the Interfaces
1 Add the IP address to the token-ring
2 Add the IP address to the MPC+ interface (=destination_IP_address)
3 Save the config
4 Reload to become the new config active
After the 2216 has been reloaded and ready again we can perform the HPDT
UDP activation on the host with the following command:
oeifconfig UDP2216A 192.166.240.1 192.166.240.2 mtu 32768
Also we have to define a route on the host to be able to connect to remote hosts,
here our PC at the token-ring of the 2216. The entry in the HPDT UDP routing
table is added via the oeroute command:
oeroute add default 192.166.240.2
212 IBM 2216 and Network Utility Host Channel Connections

For more detailed information on HPDT UDP commands on the host, refer to:
• OS/390 eNetwork Communications Server High Speed Access Services
User’s Guide, GC31-8676
• OS/390 TCP/IP Update Guide, GC31-8553
Now the configuration of our test environment for an HPDT UDP connection
between the host and the 2216 via the MPC+ interface is complete and can be
monitored as described in 6.6.3.1, “Monitoring ESCON MPC+ Interface” on page
214.
6.6.3 Monitoring ESCON Interface
The monitoring commands are available from the GWCON prompt which you get
via the T5 process. You access the talk 5 commands that show the status of
channel resources hierarchically as follows:
• From the * prompt, type talk 5 and press Enter to reach the + prompt.
• From the + prompt, type int and press Enter and note the logical interface
number for the physical ESCON interface you are interested in. The physical
interface is commonly called the base net, and might have a number of LSA,
LCS, or MPC+ virtual interfaces defined on top of it. The base net and all
virtual interfaces each have a different logical interface number (see Figure
227 below).
2216 *t5
2216 +int
Self-Test Self-Test Maintenance
Net Net' Interface Slot-Port Passed Failed Failed
0 0 TKR/0 Slot: 1 Port: 1 2 1 0
1 1 ESCON/0 Slot: 3 Port: 1 1 0 0
2 1 MPC/0 Slot: 0 Port: 0 1 13 0
Figure 227. Interface List via GWCON
• From the + prompt, type net base n number and press Enter to reach the
ESCON Console subprocess. The command prompt changes to ESCON> (see
Figure 228 on page 213).
2216 +net 1
ESCON Base Console
2216 ESCON>
Figure 228. Change to the ESCON Base Net Prompt
At these prompts, you can use the li nets command to see the current state of
every (LSA, LCS, MPC+) virtual interface using this base net. You can also type
li sub to view the currently running subchannel configuration for this base net
(see Figure 229 on page 214).
Multipath Channel+ Implementation (MPC+) 213

2216 ESCON>li net
Net: 2 Type: MPC+ Group Number: 0
1 Net state: Up
2216 ESCON> li sub
The following subchannels are defined:
2 Local address: 00 Device address: 06 CU Logical Address: 01
Link: CC LPAR: 04
3 Type: MPC+
The following lantypes/lannums are using this subchannel:
4 Group No.: 0
Local address: 01 Device address: 07 CU Logical Address: 01
Link: CC LPAR: 04
Type: MPC+
The following lantypes/lannums are using this subchannel:
Group No.: 0
Figure 229. List of Net and Subchannel s from ESCON Base Net Prompt
1 Net State State of the network: Up, Down, Disabled, Not Present, HW
Mismatch, or Testing. Up Indicates that the link is up.
2 Local Address The subchannel address index used internally by the
device.
3 Type Type of virtual interface: LCS, LSA, or MPC+.
4 Group Number The group number is used internally by the device to
identify a virtual MPC+ net interface on the channel
adapter.
6.6.3.1 Monitoring ESCON MPC+ Interface
From the base net ESCON> prompt or directly from the + prompt, type net
virtual net number and press Enter to see more detail on a particular virtual
interface that uses this base net. The command prompt changes to LSA>, LCS>,
or MPC+>, depending on the type of virtual interface you select.
Each of these prompts supports a list command, to show configuration and
current status information relevant to the virtual interface type (see Figure 230 on
page 214).
2216 +net 2
MPC+ Console
2216 MPC+>
2216 MPC+>list ?
MPc group
SUbchannel
CM
COnnection
Figure 230. List of Subcommands for the MPC+ Interface
The next figures reflect these listing commands one by one regarding our test
environment.
The mpc command displays information about the MPC+ group. It displays the
local and remote registration token, if known, and the current state of the MPC+
group. Also, if the MPC+ is for the exclusive use of UDP+, that will be indicated
214 IBM 2216 and Network Utility Host Channel Connections

(4 ). If the MPC+ group is not for the exclusive use of UDP+, exclusive use will not
be mentioned in the display.
Note: UDP+ is not supported on a parallel channel adapter (PCA).
2216 MPC+>li mpc
MPC+ Group
Local registration token = 09017B519800000000 1
Remote registration token = 05000104F2 2
state = Active 3
This MPC+ Group is for the exclusive use of UDP+. 4
Outbound protocol data blocking is enabled for the MPC+ Group.
Figure 231. List of MPC+ Group
1 Local registration token Token in the device representing this MPC+
group.
2 Remote registration token Token on the host representing this MPC+ group.
This field is blank if not known.
3 State The state of the MPC+ group: Active and usable.
4 Indicates the exclusive use of UDP.
The subchannel command shows information about the subchannels that are part
of the MPC+ group. It shows the local subchannel number, logical partition
number, link address, control unit (CU) logical address, device address, type of
subchannel (READ or WRITE), and the current state of the subchannel (see
Figure 232 on page 215). The type should be the opposite of what is configured
at the host.
2216 MPC+>li sub
MPC+ Subchannels
Local Link CU Log. Device
number LPAR addr address address type state
------- ----- ----- ------- --------- ---------- ----------
1 2 3
1 4 CC 1 7 READ Active
0 4 CC 1 6 WRITE Active
Figure 232. List of MPC+ Subchannels
1 Local number The subchannel address index used internally by the device.
Note: CU logical address, link address, and LPAR are
displayed for ESCON adapters only.
2 Type Whether this is a read or write subchannel.
3 State The subchannel is active and part of an MPC+ group.
The cm command shows information on the connection manager that is running on
the MPC+ group. The information shown is the group token, the type of
connection manager, and the current state.
Multipath Channel+ Implementation (MPC+) 215

2216 MPC+>li cm
MPC+ Connection Managers(CM)
Group Token type state
------------------------- ------- ----------
1 2
09022701680000000A PTP Active
Figure 233. List of MPC+ Connection Manager
1 Type PTP Point-to-point
2 State Active Active and usable
The connection command shows information on the connections running on the
MPC+ group/connection manager. The information shown is in two parts (see
Figure 234 on page 216): the virtual circuit and the connections under the virtual
circuit. The following information is shown for the virtual circuit: the local and
remote virtual circuit tokens, the protocol type, and the current state.
2216 MPC+>li con
MPC+ Connections
Virtual Circuit Token = 09022702940000000E 1
Remote Registration Token(s) = 05000104B5 2
Protocol = 3 UDP+, State = Active-both sides 4
Local Connection Token = 09022703580000000F 5
Remote Connection Token = 050001051C 6
State = Active 7
Local IP address = 192.166.240.2 8
Destination IP address = 192.166.240.1 9
Figure 234. List of MPC+ Connections
1 Local Virtual Circuit Token Token in the device representing this virtual
circuit.
2 Remote Virtual Circuit Token Token on the host representing this virtual
circuit. This field is blank if not known.
3 Protocol The upper layer protocol that this virtual circuit
is using.
4 State Active-both sides Both sides of the virtual circuit are accepting
calls (connections) for this virtual circuit.
The information shown for the connection is the local and remote connection
tokens and the current state. For IP protocols (that is, UDP+ and TCP/IP), the
local and destination IP addresses associated with the connection will also be
shown, if known.
5 Local Connection Token The token in the device representing this
connection.
6 Remote Connection Token The token on the host representing this
connection. This field is blank if not known.
7 State Active Active and usable.
8 Local IP address The IP address on the MPC+ interface in the
device that is associated with this connection.
This field will be displayed for IP protocols only.
216 IBM 2216 and Network Utility Host Channel Connections

(=destination_IP_address from the oeifconfig
command)
9 Destination IP Address The IP address on the host that is associated
with this connection. This field will be displayed
only for IP protocols. (=source_IP_address from
the oeifconfig command)
To back out from any of these nested levels, type exit and press Ctrl+P to go
back to the * prompt.
Due to the very simple configuration of our test environment, no routing protocol
is needed inside the 2216. The IP monitoring via the dump command does not
show much. See Figure 235 on page 217.
2216 *t 5
CGW Operator Console
2216 +
2216 +p
Protocol name or number [IP]?
2216 IP>dump
Type Dest net Mask Cost Age Next hop(s)
Sbnt 16.0.0.0 FF000000 1 159 None
Dir* 16.0.0.0 FFFFFF00 1 168 TKR/0
Dir* 192.166.240.0 FFFFFF00 1 4459 MPC/0
Figure 235. Dump Command at the IP Protocol
For more examples and a detailed explanation of the output of these commands,
see the chapter "Configuring and Monitoring the ESCON and Parallel Channel
Adapters" in the Nways Multiprotocol Access Services Software User's Guide
Version 2, Release 2, SC30-3886.
Multipath Channel+ Implementation (MPC+) 217

218 IBM 2216 and Network Utility Host Channel Connections

Chapter 7. TN3270 Server Channel-Attached Configuration
Many companies today are considering the consolidation of their WAN traffic onto
a single IP-only backbone. At the same time, other companies are simplifying
their workstation configurations and attempting to run only the TCP/IP protocol
stack at the desktop. However, most of these companies still require access to
SNA application hosts.
The TN3270E Server provides a TN3270 gateway function for TN3270 clients
that are downstream of an SNA host running a 3270 application. These clients
connect to the server using a TCP connection. This connection is mapped to an
SNA-dependent LU-LU session that the server maintains with the SNA host. The
TN3270E Server handles the conversion between the TN3270 datastream and an
SNA 3270 datastream. The TN3270E Server function complies with RFC 1646
and RFC 1647.
As mentioned above, the path from a TN3270 client to the SNA host consists of
two pieces:
1. A TCP connection over IP from the client to the server
2. An SNA LU-LU session from the server to the host
Connecting to a host for establishing an dependent LU-LU session can be
accomplished using a traditional subarea connection or using an APPN
connection in conjunction with the APPN DLUS/DLUR function. The APPN
DLUS/DLUR solution allows the node to appear to VTAM as multiple PU devices,
each supporting up to 253 dependent LUs. A node wishing to provide TN3270E
Server services over a subarea connection for more than 253 clients must
simultaneously also appear as multiple PUs to an attached host.
Support for subarea SNA connections for TN3270E Server services eliminates
the need for APPN in the host. However, APPN must still be configured in the
router.
The 2216 as a TN3270E server can be deployed in several configurations. For
example, it can be placed either in the remote branch or in the data center. It can
attach to the host via a traditional SNA subarea connection or it can use APPN. In
the data center, it can be placed in a channel-attached configuration or it can be a
stand-alone server that resides on the campus LAN (or ATM cloud) using the
channel-attached connection provided by an existing IBM 3745/46
Communication Controller, another 2216-400, Network Utility, 3172 Interconnect
Controller, OSA adapter, or OEM gateway.
The subject of this book is the ESCON channel, so we will focus on the TN3270 in
a channel-attached configuration. For more information on the other
configurations refer to Network Utility Installation, Getting Started and User’s
Guide, GA27-4167.
7.1 2216 vs Host Parameters Relationship
Before we can attach a 2216 to the host we need some definitions in the host.
These definitions will depend on the protocol running in the ESCON channel. For
these definitions that depend on the protocol, we will add switched major node
© Copyright IBM Corp. 1998 219

definitions to the PUs used by the TN3270E Server that will be independent of the
protocol.
The two protocols that can be used for accessing SNA applications in the host
are LSA and MPC+. LSA may be used to transport SNA and APPN traffic
between the 2216 and the host while MPC+ can transport only APPN.
7.1.1 TN3270E with LSA-SNA
When transporting SNA we may configure in the same 2216 the TN3270E Server
using SNA subarea links. The definitions that will be needed in the host with this
configuration are:
• XCA Major Node Definition
• Switched Major Node Definitions for the TN3270E Server PUs
The relationships between the 2216 and the host for the LSA connection are the
same ones described in 4.3, “2216 LSA vs. Host Parameter Relationships” on
page 55 in Figure 236. These definitions have been included in the TN3270E
definitions. The whole matching can be seen in Figure 236 on page 221.
220 IBM 2216 and Network Utility Host Channel Connections

2216/NetworkUtility (LSA) Parameter - Relationships - SNA - TN3270E
VTAM XCA Major Node Definition
MVSIOCPDefinitions
X5303 VBUILD TYPE=XCA
RESOURCE PART=((A1,1))
CHPID PATH=((2C),TYPE=CNC,PART=(A1),SWITCH=E1)
X5303PRT PORT CUADDR=284,MEDIUM=RING,ADAPNO=0
CNTLUNIT CUNMBR=0280,PATH=(2C),CUADD=1,
TIMER=60,SAPADDR=04
UNITADD=((00,032)),LINK=(C9),UNIT=3172
X5303 GROUP DIAL=YES,CALL=INOUT,DYNPU=YES,
AUTOGEN=(10,L,P)
IODEVICE UNIT=3172,ADDRESS=(280,032),
CUNMBR=(0280)
VTAM Switched Major Node Definition-TN3270
LPAR 1
CHPID=2C
Figure 236. TN3270E - LSA (SNA): 2216-Host Parameter Relationships
SW5303D VBUILD TYPE=SWNET
CC
ESCON
Director E1
P2216D PU ADDR=02,IDBLK=077,IDNUM=02216,
PUTYPE=2,
USSTAB=US327X,DLOGMOD=D4C32XX3
L2216D1 LU LOCADDR=02,
L2216D2 LU LOCADDR=03,
L2216D3 LU LOCADDR=04,
C9
2216
2216 Definitions:
LPAR 1
CU 1
Device 04
Link CC
LAN number 0 (use "list all" to determine from the
ESCON config prompt)
PC Definitions:
Token
Ring
APPN:
Node: Network ID=USIBMRA
CP Name=NN2216
Port ( APPN loopback)
Link: Solicit SSCP sess=yes
Local Node ID=02216
Support APPN=no
TN3270E:
Server IP@=192.194.200.1
TN3270 Server Channel-Attached Configuration 221
Destin IP@=192.194.200.1

7.1.2 TN3270E with LSA-APPN/DLUR
When transporting APPN we can configure in the same box the TN3270E Server
support via DLUR. We need in the host:
• XCA Major Node Definition
• Switched Major Node Definitions for the 2216 network node
• Switched Major Node Definitions for the TN3270E Server PUs that are
connected via DLUR
As before, the definitions between the 2216 and the host for the LSA APPN
connection are the same ones described in 7.1, “2216 vs Host Parameters
Relationship” on page 219 in Figure 237. They have been included in Figure 237
on page 223 with the TN3270E definitions.
222 IBM 2216 and Network Utility Host Channel Connections

2216/NetworkUtility (LSA) Parameter - Relationships - APPN-TN3270E
VTAM Start List
VTAM XCA Major Node Definition
NETID=USIBMRA
X5303 VBUILD TYPE=XCA
X5303PRT PORT CUADDR=284,MEDIUM=RING,ADAPNO=0
MVS IOCP Definitions
TIMER=60,SAPADDR=04
RESOURCE PART=((A1,1))
CHPID PATH=((2C),TYPE=CNC,PART=(A1),SWITCH=E1)
X5303 GROUP DIAL=YES,CALL=INOUT,DYNPU=YES,
AUTOGEN=(10,L,P)
CNTLUNIT CUNMBR=0280,PATH=(2C),CUADD=1,
UNITADD=((00,032)),LINK=(C9),UNIT=3172
VTAM Switched Major Node Definition
IODEVICE UNIT=3172,ADDRESS=(280,032),
CUNMBR=(0280)
SW5303N VBUILD TYPE=SWNET
P2216N PU ADDR=02,
PUTYPE=2,
CPCP=YES,
CONNTYPE=APPN,
NN=YES,
DYNLU=YES
CPNAME=NN2216
LPAR 1
CHPID=2C
Figure 237. TN3270E - LSA (APPN/DLUR): 2216-Host Parameter Relationships
CC
ESCON
Director E1
C9
VTAM Switched Major Node Definition-TN3270
2216 Definitions:
SW5303D VBUILD TYPE=SWNET
LPAR 1
P2216D PU ADDR=02,IDBLK=077,IDNUM=02216,
PUTYPE=2,
USSTAB=US327X,DLOGMOD=D4C32XX3
L2216D1 LU LOCADDR=02,
L2216D2 LU LOCADDR=03,
L2216D3 LU LOCADDR=04,
CU 1
Device 04
Link CC
LAN number 0 (use "list all" to determine from the
ESCON config prompt)
PC Definitions:
Token
Ring
APPN:
Node: Network ID=USIBMRA
CP Name=NN2216
Port ( APPN loopback)
Link
DLUR: DLUS=USIBMRA.RA03M
Local PU: Local Node ID=02216
TN3270E:
Server IP@=192.194.200.1
TN3270 Server Channel-Attached Configuration 223
Destin IP@=192.194.200.1

7.1.3 TN3270E with MPC+ and APPN/DLUR
MPC+ can be used only with APPN, so MPC+ can be configured with the
TN3270E Server in the same box via the DLUR function in the router. The
definitions that have to be active in the host are:
• Transport Resource List Major Node Definitions
• Local Major Node Definitions
• Switched Major Node Definitions for the TN3270E Server PUs that are
connected via DLUR
The support we need in the router in this case is the MPC+ support. That’s why
the definitions we need in this case are the same ones needed for an MPC+
connection whether or not we are implementing the TN3270E Server in the same
box. So the parameter relationship between the 2216 and the host is also the
same one we saw in 6.2, “2216 MPC+ Host Parameter Relationships” on page
170. Then we need the definitions for the TN3270E Server which will have to
match the TN3270E Server configuration in the router. See Figure 238 on page
225.
224 IBM 2216 and Network Utility Host Channel Connections

2216/NetworkUtility (MPC+) Parameter Relationships - TN3270E
VTAM Local PU Definition
VTAM Start List
LOC2216 VBUILD TYPE=LOCAL
NETID=USIBMRA
PU2216 PU TRLE=M3A2216A,XID=YES,CONNTYPE=APPN,
CPCP=YES,HPR=YES
MVS IOCP Definitions
VTAM Transport Resource List Major Node
RESOURCE PART=((A1,1))
CHPID PATH=((2C),TYPE=CNC,PART=(A1),SWITCH=E1)
TRL2216 VBUILD TYPE=TRL
M3A2216A TRLE LNCTL=MPC,
MAXBFRU=9,
READ=(280)
WRITE=(281),
REPLYTO=3.0
LPAR 1
CHPID=2C
Figure 238. TN3270E - MPC+ APPN/DLUR: 2216-Host Parameter Relationships
CNTLUNIT CUNMBR=0280,PATH=2C,CUADD=1,
UNITADD=((00,32)),LINK=C9,UNIT=3172
IODEVICE UNIT=3172,ADDRESS=((280,032)),
CUNMBR=0280
VTAM Switched Major Node Definition-TN3270
SW5303D VBUILD TYPE=SWNET
P2216D PU ADDR=02,IDBLK=077,IDNUM=02216,
PUTYPE=2,
USSTAB=US327X,DLOGMOD=D4C32XX3
L2216D1 LU LOCADDR=02,
L2216D2 LU LOCADDR=03,
L2216D3 LU LOCADDR=04,
CC
ESCON
Director E1
C9
2216
ESCON MPC+ Definitions:
LPAR 1
CU 1
Device 01 (READ)
Device 00 (Write)
Link CC
PC Definitions:
Token
Ring
TN3270 Server Channel-Attached Configuration 225
Destin IP@=192.194.200.1
APPN:
Node: Network ID=USIBMRA
CP Name=NN2216
Port ( MPC+ interface))
Link
DLUR: DLUS=USIBMRA.RA03M
Local PU: Local Node ID=02216
TN3270E:
Server IP@=192.194.200.1

7.2 TN3270E Configuration Using SNA Subarea Links
This option is used when APPN is not running at the host. A separate DLC-layer
link to the host is configured for every PU (maximum of 253 LUs per PU). Multiple
PUs require multiple parallel host links. SNA frames arriving at 2216 on one of
these links flow directly to the corresponding internal PU. Subarea host links must
be a single DLC-layer hop to the host. They can traverse bridges or other
DLC-layer forwarding mechanisms (such as protocol converters or external DLSw
routers).
The scenario discussed in this chapter deals with the 2216 acting as a TN3270E
Server and as a LAN Channel Gateway via the ESCON channel adapter. As a
LAN Channel Gateway it is using the external communication adapter (XCA)
pass-through and does not provide the SNA boundary function normally provided
by an NCP. With a gateway this function is provided by VTAM.
From the three channel protocols that can be used to communicate with the
channel, only link services architecture (LSA) can be used for transporting SNA
traffic. So, when using the TN3270E Server with SNA subarea links, LSA is the
only option for communicating with the host channel through the ESCON channel
adapter.
7.2.1 Network Environment Description
In this scenario the 2216 is attached to the host through the ESCON channel
adapter running the LSA protocol and to an IP network through a PPP link.
Acting as a TN3270E Server, the 2216 will provide the stations in the IP network
with access to the 3270 applications in the host.
226 IBM 2216 and Network Utility Host Channel Connections

XCA Major Node Definitions
ADAPNO=0
SAPADDR=4
MEDIUM=RING
.....
------------------------------
SW Major Node Definitions
IDBLK=077
IDNUM=02216
.....
------------------------------
MVS IOCP Definitions
UNITADD=04
CUADD=1
7.2.2 Host Programs Definitions
RA03
LPAR 1
192.194.200.1
PPP
RA28
LPAR 2
ESCD
RA39
LPAR 4
Figure 239. TN3270E Server Configuration with SNA Subarea Links Network Setup
Before we can attach the 2216 to the ESCON channel using LSA we need some
definitions in the host besides some VTAM definitions that are required for the
PUs used by the TN3270E Server.
7.2.2.1 IOCP and MVS Operating System Definitions
The CNTLUNIT statement defines the path from the host to the 2216 and is used
for the IOCP definitions.
The 2216 must be defined to an IBM Multiple Virtual Storage/Extended
Architecture (MVS/XA) or MVS/ESA operating system. This definition is
accomplished by updating the MVS control program with an entry for the 2216 in
the IODEVICE macro.
S/390
The IODEVICE statement is for the MVS operating system.
LSA
WAN
2210
CC
C9
10.0.0.0
2216
192.194.200.2
S/390
2216
40002216000A
40002216000B
SNA
LSA MAC@ 40002216000A
APPN loopback MAC @ 40002216000B
SNA
network
TN3270E server
IP
network
TN3270 Server Channel-Attached Configuration 227

RESOURCE PARTITION=((A1,1) 1 ,(A2,2),(A3,3),(A4,4),(A5,5),(C1,6), *
(C2,7))
CHPID PATH=(2C),SHARED, *
PARTITION=((A1,A2,A3,A4),(A1,A2,A3,A4,A5)),SWITCH=E1, *
TYPE=CNC
CNTLUNIT CUNUMBR=0280,PATH=(2C),UNITADD=((00,032)) 2 ,LINK=(C9), *
CUADD=1 3 ,UNIT=3172
CNTLUNIT CUNUMBR=02A0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=2,UNIT=3172
CNTLUNIT CUNUMBR=02C0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=4,UNIT=3172
IODEVICE ADDRESS=(280,032),UNITADD=00,CUNUMBR=(0280),STADET=Y, *
PARTITION=(A1),UNIT=3172
IODEVICE ADDRESS=(2A0,032),UNITADD=00,CUNUMBR=(02A0),STADET=Y, *
PARTITION=(A2),UNIT=3172
IODEVICE ADDRESS=(2C0,032),UNITADD=00,CUNUMBR=(02C0),STADET=Y, *
PARTITION=(A4),UNIT=3172
Figure 240. TN3270E SNA: IOCP and MVS Operating System Definitions
1 In this scenario we will connect to LPAR 1.
2 UNITADD defines the range of addresses reserved for this control unit. The first
number is the hex of the first subchannel assigned to this control unit. The second
number is the decimal number of subchannels being assigned to this control unit.
The parameter device address defined in the 2216 must be in this range of
addresses. In this scenario we will use device address 04.
3 This value identifies the control unit address of the 2216. For the 2216, each
LPAR on a given CHPID must have a unique CUADD value. This value must
match the control unit parameter specified in the 2216.
7.2.2.2 VTAM Definitions
Entries in the following VTAM control blocks are required.
XCA Major Node Definitions
When defining a channel gateway using LSA to VTAM, a definition for an external
communications adapter (XCA) is required. This definition is the same as that
used for IBM 3172.
*******************************************************************
X5303 VBUILD TYPE=XCA 1
**
**
X5303PRT PORT ADAPNO=0, 2 *
CUADDR=284, 3 *
SAPADDR=4, 4 *
MEDIUM=RING 5
X5303GRP GROUP DIAL=YES,CALL=INOUT,DYNPU=YES, *
AUTOGEN=(10,L,P)
Figure 241. TN3270E SNA: XCA Major Node Definitions
1 TYPE must be XCA
2 ADAPNO is the LAN number for the 2216 interface. This value is assigned to
the LSA 2216’s interface when it is created. The value can be obtained from the
228 IBM 2216 and Network Utility Host Channel Connections

2216 by listing the configuration of the interface from the talk 6 menus or can be
retrieved from the field LAN number by entering the list net command from the
ESCON console in talk 5. Note that this value is not the interface number for the
LSA interface that can be seen in list devices from talk 6. Also note that a wrong
value for this parameter is the single most common error in LSA configuration.
3 CUADDR specifies the subchannel to be used to communicate with the 2216.
This value must be within the range of values specified in the IODEVICE
statement in the IOCP definition for the ADDRESS parameter.
4 SAPADDR is the Service Access Point VTAM wishes to open on the 2216. Note
that it is the SOURCE SAP, not the DESTINATION SAP. When more than one
XCA major node refers to the same LAN number all the XCA major nodes have to
use different SAPs.
5 This specifies the physical LAN topology to which the LSA interface is attached.
This value must match the LANtype parameter in the 2216 LSA interface. Valid
values are MEDIUM=RING for token-ring, MEDIUM=CSMACD for Ethernet and
MEDIUM=FDDI for a fiber distributed data interface (FDDI) network.
Switched Major Node Definitions
A switched major node definition is required for each PU in the TN3270E Server.
In this scenario we are using only one PU, that’s why there is only one definition.
For example, each PU in the TN3270E Server can support up to 253 LUs. If 500
3270 sessions are needed, then we will need two PUs in the router and two PU
definitions in VTAM will be needed as well.
************************* TOP OF DATA ****************************
SW5303D VBUILD TYPE=SWNET
P2216D PU ADDR=02, X
PUTYPE=2, X
IDBLK=077,IDNUM=02216, 1 X
SSCPFM=USSSCS,USSTAB=US327X, X
DLOGMOD=D4C32XX3, X
PACING=0,ANS=CONTINUE
L2216D1 LU LOCADDR=2
L2216D2 LU LOCADDR=3
L2216D3 LU LOCADDR=4
*********************** BOTTOM OF DATA ***************************
Figure 242. TN3270E SNA: Switched Major Node Definitions
1 These two values, IDBLK/IDNUM, identify the remote device (in this case it is
the 2216) when VTAM is communicating with dependent devices. The value of the
IDNUM field has to be set up as a Local Node ID in the link station to VTAM in the
2216 configuration.
7.2.3 2216 Configuration
When configuring the 2216 as a TN3270E Server and channel-attached gateway
at the same time for SNA support the following steps must be followed:
1. Load the APPN and TN3270E packages.
2. Add and configure the physical interfaces.
3. Add and configure the LSA virtual interface.
TN3270 Server Channel-Attached Configuration 229

4. Add and configure the APPN loopback interface.
5. Configure IP.
6. Enable APPN support, define a port and one or more link stations to VTAM.
7. Set the parameters for the TN3270E Server, including the IP address that will
identify the TN3270E Server in the IP cloud and define downstream LUs,
either as implicit or explicit.
Note
In both, the APPN and the subarea implementation of the TN3270E Server, it is
required to install the APPN support in the 2216 and both are configured within
the APPN configuration process. This is true even though a pure subarea
configuration does not use the APPN function. This is an implementation
statement as the TN3270E Server function uses the APPN SNA stack for both
subarea and APPN connections to the host.
7.2.3.1 Add and Configure Physical Interfaces
The physical interfaces have to be added with the add device command from the
2216 config prompt. The 2216 will assign a network number to all the interfaces.
We can display these network numbers with the list devices command as seen in
Figure 247 on page 232.
2216 *t6
2216 Config>add dev eia
Device Slot #(1-8) [1]? 8
Device Port #(0-7) [1]? 0
Defaulting Data-link protocol to PPP
Adding EIA-232E/V.24 PPP device in slot 8 port 0 as interface #0
Use "set data-link" command to change the data-link protocol
Use "net 0" to configure EIA-232E/V.24 PPP parameters
2216 Config>add dev escon
Device Slot #(1-8) [1]? 3
Adding ESCON Channel device in slot 3 port 1 as interface #1
Use "net 1" to configure ESCON Channel parameters
2216 Config>net 0
Point-to-Point user configuration
2216 PPP 0 Config>li hdlc
Encoding: NRZ
Idle State: Flag
Clocking: External
Cable type: RS-232 DTE
Speed (bps): 19200
Transmit Delay Counter: 0
Lower DTR: Disabled
2216 PPP 0 Config>ex
2216 Config>
Figure 243. TN3270E SNA: Adding the Physical Adapters to the 2216
7.2.3.2 Load the Packages
The talk 6 code required to configure APPN or TN3270 resides on the
corresponding DLL, and that DLL is not loaded unless you have enabled the
corresponding function. If you use the Configuration Program to configure the
device, this will be taken care of automatically. If you use talk 6 commands to
230 IBM 2216 and Network Utility Host Channel Connections

configure the device, you must issue the load add package command and then
reboot prior to being able to invoke the talk 6 APPN or TN3270 commands.
2216 Config>load add pack appn
appn package configured successfully
This change requires a reload.
2216 Config>load add pack tn3270e
tn3270e package configured successfully
This change requires a reload.
2216 Config>
2216 *reload
Are you sure you want to reload the gateway? (Yes or [No]): y
The configuration has been changed, save it? (Yes or [No] or Abort): y
Config Save: Using bank A and config number 4
Figure 244. TN3270E SNA: Adding the Packages
7.2.3.3 Configuring the LSA Virtual Interface
The next step is to add and configure the LSA interface. As a new interface is
created inside the 2216 a network number is assigned to this interface, as can be
seen in Figure 247 on page 232.
The subchannels have to be added and configured also. LSA uses only one
bidirectional subchannel.
2216 Config>net 1
2216 ESCON Config>add lsa
2216 ESCON Add Virtual>ena loop
Enabling loopback through network 2.
Please set the MAC address using the "MAC" command
2216 ESCON Add Virtual>lanty toke
2216 ESCON Add Virtual>mac 40:00:22:16:00:0A
2216 ESCON Add Virtual>sub add
2216 ESCON Add LSA Subchannel>lpar 1
2216 ESCON Add LSA Subchannel>cu 1
2216 ESCON Add LSA Subchannel>link cc
2216 ESCON Add LSA Subchannel>device 4
2216 ESCON Add LSA Subchannel>ex
2216 ESCON Add Virtual>ex
2216 ESCON Config>li all
Net: 2 Protocol: LSA LAN type: Token Ring LAN number: 0
Maxdata: 2052
Loopback is enabled.
MAC address: 40002216000A
Block Timer: 10 ms ACK length: 10 bytes
Sub 0 Dev addr: 4 LPAR: 1 Link addr: CC CU addr: 1
Figure 245. TN3270E SNA Subarea Links: Configuring the LSA Interface
7.2.3.4 Add and Configure the APPN Loopback Interface
Once the LSA/host end of the loopback connection has been set, the APPN end
of the loopback connection has to be configured also.
TN3270 Server Channel-Attached Configuration 231

As with the LSA loopback interface, when the APPN loopback interface is added
a new interface is created inside the 2216. Then, the 2216 assigns a network
number to this interface as seen in Figure 247 on page 232.
The LAN type for this interface needs to match the LAN type of the LSA virtual
interface, since both interfaces are supposed to be on the same LAN.
2216 ESCON Config>add appn
2216 ESCON Add Virtual>lan toke
2216 ESCON Add Virtual>mac 40:00:22:16:00:0B
2216 ESCON Config>li all
Net: 3 Protocol: APPN Loopback LAN type: Token-Ring/802.5
APPN loopback MAC address: 40002216000B
Net: 2 Protocol: LSA LAN type: Token Ring LAN number: 0
Maxdata: 2052
Loopback is enabled.
MAC address: 40002216000A
Block Timer: 10 ms ACK length: 10 bytes
Sub 0 Dev addr: 4 LPAR: 1 Link addr: CC CU addr: 1
2216 ESCON Config>ex
ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]:
2216 Config>
Figure 246. TN3270E SNA: APPN Loopback Interface Configuration
To see the network number for all the interfaces that have been added to the
2216, we can use the list devices command, as seen in the following figure.
2216 Config>li dev
Ifc 0 EIA-232E/V.24 PPP Slot: 8 Port: 0
Ifc 1 ESCON Channel Slot: 3 Port: 1
Ifc 2 LSA - ESCON Channel Base Net: 1
Ifc 3 Loopback APPN - Channel Slot: 0 Port: 0
2216 Config>
Figure 247. TN3270E SNA: Looking at Network Numbers
7.2.3.5 Configure IP
The IP protocol has to be configured on those interfaces that attach to the IP
cloud where the TN3270 clients are located.
232 IBM 2216 and Network Utility Host Channel Connections

2216 Config>pip
Internet protocol user configuration
2216 IP config>add add 0 192.194.200.1 255.255.255.0
2216 IP config>ena rip
2216 IP config>li all
Interface addresses
IP addresses for each interface:
intf 0 192.194.200.1 255.255.255.0 Local wire broadcast, fill 1
intf 1 IP disabled on this interface
intf 2 IP disabled on this interface
intf 3 IP disabled on this interface
Routing
Protocols
BOOTP forwarding: disabled
IP Time-to-live: 64
Source Routing: enabled
Echo Reply: enabled
TFTP Server: enabled
Directed broadcasts: enabled
ARP subnet routing: disabled
ARP network routing: disabled
Per-packet-multipath: disabled
OSPF: disabled
BGP: disabled
RIP: enabled
RIP default origination: disabled
Per-interface address flags:
intf 0 192.194.200.1 RIP Version 1
Send net and subnet routes
Receive No Dynamic host routes
RIP interface input metric: 1
RIP interface output metric: 0
intf 1 IP & RIP are disabled on this interface
intf 2 IP & RIP are disabled on this interface
intf 3 IP & RIP are disabled on this interface
Accept RIP updates always for:
[NONE]
Parameters
ARP-SUBNET-ROUTING : disabled
ARP-NET-ROUTING : disabled
CLASSLESS : disabled
DIRECTED-BROADCAST : enabled
ECHO-REPLY : enabled
FRAGMENT-OFFSET-CHECK : disabled
PER-PACKET-MULTIPATH : disabled
REASSEMBLY-SIZE : 12000 bytes
RECORD-ROUTE : enabled
ROUTING TABLE-SIZE : 768 entries (52224 bytes)
(Routing) CACHE-SIZE : 64 entries
SAME-SUBNET : disabled
SOURCE-ROUTING : enabled
TIMESTAMP : enabled
TTL : 64
2216 IP config>ex
2216 Config>
Figure 248. TN3270E SNA: IP Configuration
TN3270 Server Channel-Attached Configuration 233

7.2.3.6 Configure TN3270 Subarea under the APPN Protocol
Because of the 2216 implementation it is important to notice that all SNA
functions are bundled within the APPN protocol. This means that even when we
are configuring an SNA subarea attachment and our SNA host is not running
APPN, we must use the configuration and console services of the APPN protocol.
In particular, we must go through the APPN protocol at the command line and the
configuration program to configure ports, links, and TN3270 server functions. We
must also go through the APPN protocol at the command line to use TN3270
monitoring commands.
We must still configure APPN at the node level.
When we configure an SNA subarea support, the 2216 does still function as an
APPN network node, but only on links to other APPN nodes. If the only ports and
links we configure are those for an SNA subarea host attachment, then the APPN
function serves no purpose.
Enable APPN Support
APPN protocol has to be enabled for TN3270 to work.
234 IBM 2216 and Network Utility Host Channel Connections

2216 Config>p appn
2216 APPN config>set node
Enable APPN (Y)es (N)o [Y]?
Network ID (Max 8 characters) [ ]? usibmra
Control point name (Max 8 characters) [ ]? NN2216
Enable branch extender or border node
(0=Neither, 1=Branch Extender, 2=Border Node) [0]?
Route addition resistance(0-255) [128]?
XID ID number for subarea connection (5 hex digits) [00000]?
Use enhanced #BATCH COS (Y)es (N)o [Y]?
Use enhanced #BATCHSC COS (Y)es (N)o [Y]?
Use enhanced #INTER COS (Y)es (N)o [Y]?
Use enhanced #INTERSC COS (Y)es (N)o [Y]?
Write this record? [Y]?
The record has been written.
2216 APPN config>ex
2216 Config>write
Config Save: Using bank A and config number 1
2216 Config>
2216 *reload y
2216 APPN config>add port
APPN Port
Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING,
(M)PC, (S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P [ ]? t 1
Interface number(Default 0): [0]? 3 2
Port name (Max 8 characters) [T00003]?
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Support multiple PU (Y)es (N)o [N]? 3
Service any node: (Y)es (N)o [Y]?
High performance routing: (Y)es (N)o [Y]? n
Maximum BTU size (768-17745) [2048]?
Maximum number of link stations (1-976) [512]?
Percent of link stations reserved for incoming calls (0-100) [0]?
Percent of link stations reserved for outgoing calls (0-100) [0]?
Local SAP address (04-EC) [4]?
Local HPR SAP address (04-EC) [C8]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
2216 APPN config>add link
APPN Station
Port name for the link station [ ]? t00003 4
Station name (Max 8 characters) [ ]? tovtam
Activate link automatically (Y)es (N)o [Y]?
MAC address of adjacent node [000000000000]? 40002216000A 5
Solicit SSCP Session: (Y)es (N)o [N]? y 6
Local Node ID (5 hex digits) [00000]? 02216 7
Does link support APPN function: (Y)es (N)o [Y]? n 8
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
2216 APPN config>
Figure 249. TN3270E SNA: Configuring APPN Support
1 The link type is token-ring, since the APPN loopback LAN type is token-ring.
TN3270 Server Channel-Attached Configuration 235

2 This is the interface number of the APPN loopback interface as we can see in
Figure 247 on page 232.
3 We do not need to support multiple PUs in this scenario, since we need less
than 253 LUs. A PU supports up to 253 downstream LUs.
4 This is the port name for the APPN loopback interface.
5 This is the LSA MAC address, since the LSA interface is the host end of the
loopback connection.
6 This question is available only if the TN3270E package is loaded. For subarea
connections, defining a link station and specifying to solicit an SSCP session
implicitly defines a PU on the 2216. This PU will support up to 253 downstream
LUs. If you need more than 253 LUs, then you need to define more than one link
station. Each link station needs to use a different service access point (SAP) and
a different Local Node ID (IDNUM).
7 This is the IDNUM in the VTAM Switched Major Node, the value is the same one
that appears in Figure 242 on page 229.
8 The link does not support APPN because we are using it for subarea
connections.
Configuring TN3270E Server
The TN3270E config prompt is from the APPN config prompt. In the TN3270E
config prompt we will be able to configure all the TN3270E Server parameters.
236 IBM 2216 and Network Utility Host Channel Connections

2216 APPN config>tn3270e
2216 TN3270E config>set
TN3270E Server Parameters
Invalid value please re-enter
Enable TN3270E Server (Y/N) [Y]?
TN3270E Server IP Address [0.0.0.0]? 192.194.200.1 1
Port Number [23]?
NetDisp Advisor Port Number [10008]?
Keepalive type:
0 = none,
1 = Timing Mark,
2=NOP[0]?
Automatic Logoff (Y/N) [N]?
Enable IP Precedence (Y/N) [N]?
Write this record? [Y]?
The record has been written.
2216 TN3270E config>add implicit 2
TN3270E Server LU Implicit Pool
Station name (Max 8 characters) []? tovtam 3
LU Name Mask (Max 5 characters) [@01LU]?
Number of Implicit LUs in Pool(1-253) [1]? 10
Write this record? [Y]?
The record has been written.
2216 TN3270E config>li all
TN3270E Server Definitions
TN3270E enabled: YES
TN3270E IP Address: 192.194.200.1
TN3270E Port Number: 23
NetDisp Advisor Port Number: 10008
Keepalive type: NONE
Automatic Logoff: N Timeout: 30
Enable IP Precedence: N
Link Station: TOVTAM
Local Node ID: 02216
Auto activate : YES
Implicit Pool Information
Number of LUs: 10
LU Mask: @01LU
LU Name NAU addr Class Assoc LU Name Assoc NAU addr
-------------------------------------------------------------------
2216 TN3270E config>
Figure 250. TN3270E SNA: TN3270E Server Configuration
1 There are two Telnet servers in the device, the remote console and the
TN3270E Server. When configuring the parameters for the TN3270E Server, you
can set the IP address of the server to either the internal box IP address or to one
of the interface IP addresses. Remember that the address you select for TN3270
may be unavailable for using normal IP Telnet to manage the box. We have to
specify here the IP address of the interface.
2 The downstream LUs can be defined either as explicit or implicit. Use explicit
definitions when you need to ensure that the device will always use the same LU
name. Use implicit definitions when you have a large group of devices that can
use a common pool of available LUs and do not need to use the same LU name
every time.
3 This is the station name defined earlier in the APPN loopback port.
TN3270 Server Channel-Attached Configuration 237

The next step is to save the configuration by using the write command from the
config prompt and to reload the box for the new configuration to become active.
7.2.4 2216 Monitoring
When monitoring the TN3270E Server and the channel connection to the host,
the following steps must be performed:
• Check that all the interfaces are UP.
• Check that the status of the LSA virtual adapter is host connected.
• Check the IP connectivity of the TN3270E Server.
• Check the status of the TN3270E Server.
Check the status of the interfaces by using the configuration command from the
GWCON prompt.
2216 +conf
ultiprotocol Access Services
2216-MAS Feature 2821 V3.2 Mod 0 PTF 0 RPQ 0 MAS.EF6 cc4_12a
Num Name Protocol
0 IP DOD-IP
3 ARP Address Resolution
11 SNMP Simple Network Management Protocol
28 APPN Advanced Peer-to-Peer Networking [HPR]
29 NHRP Next Hop Resolution Protocol
30 APPN Advanced Peer-to-Peer Networking [ISR]
Num Name Feature
2 MCF MAC Filtering
7 CMPRS Data Compression Subsystem
9 DIALs Dial-in Access to LANs
10 AUTH Authentication
11 IPSec IPSecurity
Total Networks:
Net Interface MAC/Data-Link Hardware State
0 PPP/0 Point to Point EIA-232E/V.24 Up
1 ESCON/0 ESCON ESCON Channel Up
2 LSA/0 LSA ESCON Channel Up
3 TKR/0 Token-Ring/802.5 Channel APPN Loopback Up
2216 +
Figure 251. TN3270E SNA: Interface Status
Then, the status of the LSA interface can be monitored by using the following
commands:
238 IBM 2216 and Network Utility Host Channel Connections

2216 +net 2
LSA console
2216 LSA>li adap
LSA Virtual Adapter
LSA Information for Net 2
--- ----------- --- --- --
LAN Type: Token-Ring/802.5 LAN Number: 0
MAC Address: 40002216000A 1
Downstream network: Loopback - Net 2
Status: Host connected
#SAPs Open: 1 #Link Stations Open: 1
Maximum frame size: 2052 (0x804)
Host User ID Subchannel
------------ ----------
00000000 0
1 host user(s)
2216 LSA>li sap
SAP Provider User Max Link Open Link
Number SAP ID SAP ID Stations Stations
------ -------- -------- -------- ---------
4 00000000 00000001 10 1
1 SAPs currently open
2216 LSA>li link
Please specify a SAP number (0-236): [4]?
Link Stations on SAP 4
Station Destination Destination Link Frames Frames
ID MAC Address SAP Number Status Sent Received
------- ----------- ----------- ------ ------ --------
00000001 40002216000B 2 4 Connected 6 6
1 link station(s) open on SAP 4
2216 LSA>
Figure 252. TN3270E SNA: LSA Monitoring
1 This is the MAC address of the LSA/host end of the loopback connection.
2 MAC address of the APPN loopback interface because the PUs are located
there.
To monitor the TN3270E Server we can use the following commands, which are
available through the APPN monitoring prompt:
TN3270 Server Channel-Attached Configuration 239

2216 APPN >tn3270
TN3270E GWCON
2216 TN3270E >list ?
STATUS
CONNECTIONS
2216 TN3270E >list status 1
TN3270E Server Status Summary
TN3270E IP Address: 192.194.200.1 TN3270E Port Number: 23
NetDisp Advisor Port Number: 10008
Keepalive type: None
Automatic Logoff: N
Number of connections: 1
Number of connections in SSCP-LU state: 1
Number of connections in LU-LU state: 0
2216 TN3270E >li status 2
TN3270E Server Status Summary
TN3270E IP Address: 192.194.200.1 TN3270E Port Number: 23
NetDisp Advisor Port Number: 10008
Keepalive type: None
Automatic Logoff: N
Number of connections: 1
Number of connections in SSCP-LU state: 0
Number of connections in LU-LU state: 1
2216 TN3270E >li connect 3
Connection information about all the LUs
Local LU Class Assoc LU Client Addr Status Prim LU Sec LU Idle Min
------------------------------------------------------------------------------
@01LU3 IW 10.0.0.10 LU-LU RA03N005 L2216D2 0
2216 TN3270E >
Figure 253. TN3270E SNA: TN3270E Server Monitoring
1 and 2 show the status of the TN3270E Server in different stages of the
connection. The number of connections specifies the current number of active
TCP connections from TN3270 clients. The number of connections in an
SSCP-LU state is the number of currently active client TCP connections that have
an associated LU in this state (received an ACTLU but not yet a BIND). This is
the case for 1. And finally the number of connections in LU-LU state is the number
of currently active client TCP connections that have an associated LU in this state
(received BIND, fully active). This is the final state, 2.
3 This command displays all the connections currently active.
Besides the above list commands, a TN3270 server user needs to be able to
query the status of other APPN or SNA resources on which the function depends.
The following APPN monitoring commands are of general use:
240 IBM 2216 and Network Utility Host Channel Connections

2216 APPN >li port
Intf Name DLC Type HPR State
=============================================================
3 T00003 IBMTRNET FALSE ACT_PORT
2216 APPN >li link
Name Port Name Intf Adj CP Name Type HPR State
=========================================================================
TOVTAM T00003 3 USIBMRA.RA03M NN INACTIVE ACT_LS
2216 APPN >
Figure 254. TN3270E SNA: APPN Monitoring Commands
7.3 TN3270E Server Configuration with APPN/DLUR Links
When you are running APPN with its dependent LU server (DLUS) function at the
host, configure one DLC-layer link to the host to carry the DLUR-DLUS pipe even
if you are defining multiple local PUs. SNA frames arriving at 2216 on this link
flow to the DLUR function, which redirects them to the correct internal PU. When
you are using DLUR, you can route through an APPN network using either ISR or
HPR routing to reach the host.
We are interested in the TN3270E Server support combined with the
channel-attached gateway support provided by the 2216 and will focus on that.
From the three channel protocols supported by the ESCON channel adapter in
the 2216, the ones that transport APPN traffic over the channel are LSA and
MPC+ as shown in Figure 6 on page 17. The example we are going to see in this
subchapter uses MPC+ as a channel protocol.
7.3.1 Network Environment Description
In this scenario the 2216 is connected through a PPP link to an IP network while
it is connected through the ESCON channel adapter to the host via the channel
protocol MPC+.
TN3270 Server Channel-Attached Configuration 241

Switched Major Node Definitions
IDBLK=077
IDNUM=02216
.....
------------------------------
Local Major Node Definitions
CONNTYPE=APPN
HPR=YES
.....
------------------------------
TRL Major Node Definitions
READ=280
WRITE=281
......
------------------------------
MVS IOCP Definitions
UNITADD=00 & 01
CUADD=1
7.3.2 Host Programs Definitions
Figure 255. TN3270E Server Using an APPN DLUR Link Network Setup
For this scenario to work we need some definitions in the host. The definitions we
need are exactly the same ones we used for the MPC+ APPN connection plus the
VTAM definitions for the TN3270E Server PU (DLUR/APPN).
7.3.2.1 IOCP and MVS Operating System Definitions
The CNTLUNIT statement defines the path from the host to the 2216 and is used
for the IOCP definitions.
The 2216 must be defined to an IBM Multiple Virtual Storage/Extended
Architecture (MVS/XA) or MVS/ESA operating system. This definition is
accomplished by updating the MVS control program with an entry for the 2216 in
the IODEVICE macro.
The IODEVICE statement in Figure 256 on page 243 is for the MVS operating
system.
242 IBM 2216 and Network Utility Host Channel Connections
RA03
LPAR 1
CC
C9
PPP
RA28
LPAR 2
ESCD
LSA
WAN
2210
10.0.0.0
RA39
LPAR 4
2216
S/390
USIBMRA.RA03M
USIBMRA.NN2216
192.194.200.1
192.194.200.2
APPN
DLUS
TN3270E server
DLUR
APPN network
IP network

RESOURCE PARTITION=((A1,1) 1 ,(A2,2),(A3,3),(A4,4),(A5,5),(C1,6), *
(C2,7))
CHPID PATH=(2C),SHARED, *
PARTITION=((A1,A2,A3,A4),(A1,A2,A3,A4,A5)),SWITCH=E1, *
TYPE=CNC
CNTLUNIT CUNUMBR=0280,PATH=(2C),UNITADD=((00,032)) 2 ,LINK=(C9), *
CUADD=1 3 ,UNIT=3172
CNTLUNIT CUNUMBR=02A0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=2,UNIT=3172
CNTLUNIT CUNUMBR=02C0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=4,UNIT=3172
IODEVICE ADDRESS=(280,032),UNITADD=00,CUNUMBR=(0280),STADET=Y, *
PARTITION=(A1),UNIT=3172
IODEVICE ADDRESS=(2A0,032),UNITADD=00,CUNUMBR=(02A0),STADET=Y, *
PARTITION=(A2),UNIT=3172
IODEVICE ADDRESS=(2C0,032),UNITADD=00,CUNUMBR=(02C0),STADET=Y, *
PARTITION=(A4),UNIT=3172
Figure 256. TN3270E APPN/DLUR: IOCP and MVS Operating System Definitions
1 In this scenario we will connect to LPAR 1.
2 UNITADD defines the range of addresses reserved for this control unit. The first
number is the hex of the first subchannel assigned to this control unit. The second
number is the decimal number of subchannels being assigned to this control unit.
The parameter device address defined in the 2216 must be in this range of
addresses. In this scenario we will use device address 04.
3 This value identifies the control unit address of the 2216. For the 2216, each
LPAR on a given CHPID must have a unique CUADD value. This value must
match the control unit parameter specified in the 2216.
7.3.2.2 VTAM Definitions
Entries in the following VTAM control blocks are required.
The Transport Resource List (TRL) Major Node
The transport resource list used in this scenario is below:
**********************************************************************
* *
* VTAM TRL NODE FOR 2216 MPC *
**********************************************************************
TRL2216 VBUILD TYPE=TRL 1
M3A2216A TRLE LNCTL=MPC, X
MAXBFRU=9, X
READ=280, X
WRITE=281, X
MPCLEVEL=HPDT, X
REPLYTO=3.0
Figure 257. TN3270E SNA: VTAM Transport Resource List (TRL) Definition
1 TYPE must be TRL.
The Local Major Node
This is the local PU that resides in VTAM that supports the channel connection
defined in the TRL.
TN3270 Server Channel-Attached Configuration 243

I*********************************************************************
* *
* VTAM APPN NODE FOR 2216 MPC *
* *
**********************************************************************
LOC2216 VBUILD TYPE=LOCAL 1
PU2216 PU TRLE=M3A2216A, 2 X
XID=YES, X
CONNTYPE=APPN, X
CPCP=YES, X
HPR=YES
Figure 258. TN3270E SNA: VTAM Local Major Node Definition
1 TYPE must equal LOCAL on the VBUILD statement.
2 TRLE identifies the TRL being used. The name must match the name of an
existing TRL.
VTAM Static Definition of TN3270 Resources
We need a Switched Major Node definition for each PU in the TN3270 Server.
This definition is the same one used in Figure 242 on page 229.
************************* TOP OF DATA ****************************
SW5303D VBUILD TYPE=SWNET
P2216D PU ADDR=02, X
PUTYPE=2, X
IDBLK=077,IDNUM=02216, 1 X
SSCPFM=USSSCS,USSTAB=US327X, X
DLOGMOD=D4C32XX3, X
PACING=0,ANS=CONTINUE
L2216D1 LU LOCADDR=2
L2216D2 LU LOCADDR=3
L2216D3 LU LOCADDR=4
*********************** BOTTOM OF DATA ***************************
Figure 259. TN3270E SNA: Switched Major Node Definitions
1 These two values, IDBLK/IDNUM, identify the remote device (in this case it is
the 2216) when VTAM is communicating with dependent devices. The value of the
IDNUM field has to be set up as a Local Node ID in the link station to VTAM in the
2216 configuration.
7.3.3 2216 Configuration
The 2216 will be configured for MPC+ APPN support, and afterwards over this
configuration we will add the TN3270E Server configuration (and DLUR). For
configuring this type of support in the 2216 complete the following steps:
1. Add the APPN and TN3270E packages.
2. Add and configure the physical devices.
3. Configure the MPC+ interface.
4. Configure APPN.
5. Configure DLUR.
6. Configure the TN3270E Server.
244 IBM 2216 and Network Utility Host Channel Connections

7.3.3.1 Add the APPN and TN3270 Packages
The part of the code required to configure APPN and TN3270 is not loaded
unless you specify to do it. If you use the Configuration Program to configure the
device, this will be taken care of automatically. If you use talk 6 commands to
configure the device, you must load the package and then reboot prior to being
able to invoke the talk 6 APPN or TN3270 commands.
2216 Config>load add pack appn
appn package configured successfully
This change requires a reload.
2216 Config>load add pack tn3270e
tn3270e package configured successfully
This change requires a reload.
2216 Config>
2216 *reload
Are you sure you want to reload the gateway? (Yes or [No]): y
The configuration has been changed, save it? (Yes or [No] or Abort): y
Config Save: Using bank A and config number 4
Figure 260. TN3270E APPN/DLUR: Loading the Packages
After the reload the 2216 will come up in Config only mode because prior to
loading the packages, we had issued clear all and clear devices commands. As
there is no protocol configuration present the router starts in config only mode.
Config (only)>set host 2216
Host name updated successfully
Config (only)>load list confi pack
Configured Packages
------------------appn
package
tn3270e package
Config (only)>
Figure 261. TN3270E APPN/DLUR: Listing the Packages
7.3.3.2 Add and Configure the Physical Interfaces
As in the previous scenario, the devices that have to be added are the ESCON
channel and the EIA RS-323.
TN3270 Server Channel-Attached Configuration 245

Config (only)>add dev eia
Device Slot #(1-8) [1]? 8
Device Port #(0-7) [1]? 0
Defaulting Data-link protocol to PPP
Adding EIA-232E/V.24 PPP device in slot 8 port 0 as interface #0
Use "set data-link" command to change the data-link protocol
Use "net 0" to configure EIA-232E/V.24 PPP parameters
Config (only)>add dev escon
Device Slot #(1-8) [1]? 3
Adding ESCON Channel device in slot 3 port 1 as interface #1
Use "net 1" to configure ESCON Channel parameters
Config (only)>net 0
Point-to-Point user configuration
2216 PPP 0 Config>list hdlc
Encoding: NRZ
Idle State: Flag
Clocking: External
Cable type: RS-232 DTE
Speed (bps): 19200
Transmit Delay Counter: 0
Lower DTR: Disabled
2216 PPP 0 Config>ex
Config (only)>
Figure 262. TN3270 APPN/DLUR: Configuring the Interfaces
7.3.3.3 Add and Configure the MPC+ Interface
The next step is to configure the MPC+ interface. We have to add two
subchannels, one for reading and another one for writing. Keep in mind that a
read subchannel to VTAM is a write subchannel to the 2216 and vice versa.
246 IBM 2216 and Network Utility Host Channel Connections

Config (only)>net 1
2216 ESCON Config>add mpc
2216 ESCON Add Virtual>sub addr
2216 ESCON Add MPC+ Read Subchannel>device 1
2216 ESCON Add MPC+ Read Subchannel>lpar 1
2216 ESCON Add MPC+ Read Subchannel>cu 1
2216 ESCON Add MPC+ Read Subchannel>link cc
2216 ESCON Add MPC+ Read Subchannel>ex
2216 ESCON Add Virtual>sub addw
2216 ESCON Add MPC+ Write Subchannel>device 0
2216 ESCON Add MPC+ Write Subchannel>lpar 1
2216 ESCON Add MPC+ Write Subchannel>cu 1
2216 ESCON Add MPC+ Write Subchannel>link cc
2216 ESCON Add MPC+ Write Subchannel>ex
2216 ESCON Add Virtual>ex
2216 ESCON Config>li all
Net: 2 Protocol: MPC+ LAN type: MPC+ LAN number: 0
Maxdata: 2048
Reply TO: 45000 Sequencing Interval Timer: 3000
Outbound protocol data blocking is enabled
Block Timer: 5 ms ACK length: 10 bytes
Read Subchannels:
Sub 0 Dev addr: 1 LPAR: 1 Link addr: CC CU addr: 1
Write Subchannels:
Sub 1 Dev addr: 0 LPAR: 1 Link addr: CC CU addr: 1
2216 ESCON Config>ex
ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]: y
Config (only)>li dev
Ifc 0 EIA-232E/V.24 PPP Slot: 8 Port: 0
Ifc 1 ESCON Channel Slot: 3 Port: 1
Ifc 2 MPC - ESCON Channel Base Net: 1
Config (only)>
Figure 263. TN3270E APPN/DLUR: MPC+ Configuration
7.3.3.4 Configure IP
IP has to be configured in the 2216 in those interfaces which are attached to the
IP network. Also, the TN3270 clients will have to be able to reach the 2216 which
is its TN3270 Server.
Config (only)>pip
Internet protocol user configuration
2216 IP config>add addr 0 192.194.200.1 255.255.255.0
2216 IP config>ena rip
2216 IP config>exit
Config (only)>
Figure 264. TN3270E APPN/DLUR: IP Configuration
7.3.3.5 Configure APPN
The router will act as an APPN NN.
TN3270 Server Channel-Attached Configuration 247

Config (only)>p appn
2216 APPN config>set node
Enable APPN (Y)es (N)o [Y]?
Network ID (Max 8 characters) [ ]? usibmra
Control point name (Max 8 characters) [ ]? nn2216
Enable branch extender or border node
(0=Neither, 1=Branch Extender, 2=Border Node) [0]?
Route addition resistance(0-255) [128]?
XID ID number for subarea connection (5 hex digits) [00000]?
Use enhanced #BATCH COS (Y)es (N)o [Y]?
Use enhanced #BATCHSC COS (Y)es (N)o [Y]?
Use enhanced #INTER COS (Y)es (N)o [Y]?
Use enhanced #INTERSC COS (Y)es (N)o [Y]?
Write this record? [Y]?
The record has been written.
Config (only)>write
Config Save: Using bank A and config number 1
Config (only)>reload y 1
2216 APPN config>add port
APPN Port
Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING,
(M)PC, (S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P [ ]? m
Interface number(Default 0): [0]? 2 2
Port name (Max 8 characters) [MPC00002]?
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Service any node: (Y)es (N)o [Y]?
Maximum BTU size (768-32768) [2048]?
Edit MPC+ Sequencing Interval Timer: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
2216 APPN config>add link
APPN Station
Port name for the link station [ ]? mpc00002
Station name (Max 8 characters) [ ]? tovtam
Adjacent node type: 0 = APPN network node,
1 = APPN end node or Unknown node type [0]?
TG Number (0-20) [0]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]? y
Fully-qualified CP name of adjacent node (netID.CPname)
[]? usibmra.ra03m
Edit TG Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
2216 APPN config>
Figure 265. TN3270E APPN/DLUR: APPN Configuration
1 Before we can configure any other APPN parameter, the router must be
reloaded.
2 This is the MPC+ interface number, as we can see in the output of the list
devices command in Figure 263 on page 247.
248 IBM 2216 and Network Utility Host Channel Connections

7.3.3.6 Configuring DLUR and TN3270E Server
The 2216, acting as a TN3270E Server, will establish TCP connections with the
TN3270 clients and SNA connections with the host.
As the router and the host are running APPN we need the DLUR function on the
2216 in conjunction with the dependent LU server (DLUS) in the host in order to
be able to support the dependent SNA connections between the 2216 and the
host.
The following commands are used to configure the TN3270E Server in
conjunction with the DLUR function in the router:
TN3270 Server Channel-Attached Configuration 249

2216 APPN config>set dlur 1
Enable DLUR (Y)es (N)o [N]? y
Fully-qualified CP name of primary DLUS []? usibmra.ra03m
Fully-qualified CP name of backup DLUS []?
Perform retries to restore disrupted pipe [Y]?
Delay before initiating retries(0-2756000 seconds) [120]?
Perform short retries to restore disrupted pipe [Y]?
Short retry timer(0-2756000 seconds) [120]?
Short retry count(0-65535) [5]?
Perform long retry to restore disrupted pipe [Y]?
Long retry timer(0-2756000 seconds) [300]?
Write this record? [Y]?
The record has been written.
2216 APPN config>tn3270e 2
2216 TN3270E config>set 3
TN3270E Server Parameters
Enable TN3270E Server (Y/N) [Y]? y
TN3270E Server IP Address [0.0.0.0]? 192.194.200.1
Port Number [23]?
NetDisp Advisor Port Number [10008]?
Keepalive type:
0 = none,
1 = Timing Mark,
2=NOP[0]?
Automatic Logoff (Y/N) [N]?
Enable IP Precedence (Y/N) [N]?
Write this record? [Y]?
The record has been written.
2216 TN3270E config>ex
2216 APPN config>add local 4
Local PU information
Station name (Max 8 characters) []? pumpc1
Fully-qualified CP name of primary DLUS [USIBMRA.RA03M]?
Fully-qualified CP name of a backup DLUS []?
Local Node ID (5 hex digits) [00000]? 02216
Autoactivate (y/n) [Y]?
Write this record? [Y]?
The record has been written.
2216 APPN config>tn3270e
2216 TN3270E config>add imp 5
TN3270E Server LU Implicit Pool
Station name (Max 8 characters) []? pumpc1
LU Name Mask (Max 5 characters) [@01LU]?
Number of Implicit LUs in Pool(1-253) [1]? 10
Write this record? [Y]?
The record has been written.
2216 TN3270E config>ex
2216 APPN config>ex
2216 Config>
Figure 266. TN3270E APPN/DLUR: DLUR-TN3270E Server Configuration
1 The CP name of the primary DLUS is the CP name of the VTAM host.
2 By typing TN3270E from the APPN config prompt we get the TN3270E config
prompt, from where we can configure the TN3270E Server parameters.
3 The IP address of the TN3270E Server is any IP address configured in the
2216; we are using the IP address of the interface. Remember that the IP address
for Telnet 3270 cannot be used for telneting the 2216 console.
250 IBM 2216 and Network Utility Host Channel Connections

4 With the command add local-PU we define the PU in the 2216. The local node
ID entered must match the IDNUM field in the PU definitions in the host VTAM.
5 With this command we define a pool of LUs.The station name specifies the
name representing the link between the DLUR and the PU or the subarea link
over which SNA data will flow.
Finally, the configuration has to be saved and the box has to be reloaded for the
new configuration to become active.
7.3.4 2216 Monitoring
When monitoring the TN3270E Server along with MPC+, we have to follow these
steps:
• Check that all the interfaces are UP.
• Check that the MPC+ interface is active.
• Check the IP connectivity of the TN3270E Server.
• Check that APPN is running correctly.
• Check the status of the TN3270E Server.
The first step is to check that all the interfaces are UP. This will tell us that they
are configured correctly physically and that there is no physical problem. We can
check it with the conf command from the GWCON prompt.
2216 *t 5
2216 +conf
Multiprotocol Access Services
2216-MAS Feature 2821 V3.2 Mod 0 PTF 0 RPQ 0 MAS.EF6 cc4_12a
Num Name Protocol
0 IP DOD-IP
3 ARP Address Resolution
11 SNMP Simple Network Management Protocol
28 APPN Advanced Peer-to-Peer Networking [HPR]
29 NHRP Next Hop Resolution Protocol
30 APPN Advanced Peer-to-Peer Networking [ISR]
Num Name Feature
2 MCF MAC Filtering
7 CMPRS Data Compression Subsystem
9 DIALs Dial-in Access to LANs
10 AUTH Authentication
11 IPSec IPSecurity
Total Networks:
Net Interface MAC/Data-Link Hardware State
0 PPP/0 Point to Point EIA-232E/V.24 Up
1 ESCON/0 ESCON ESCON Channel Up
2 MPC/0 MPC ESCON Channel Up
2216 +
Figure 267. TN3270E APPN/DLUR: Interface Status
To check the status of the MPC+ interface we use the following commands:
TN3270 Server Channel-Attached Configuration 251

2216 +net 2
MPC+ Console
2216 MPC+>list mpc 1
MPC+ Group
Local registration token = 09022D768800000000
Remote registration token = 050001012C
state = Active
Outbound protocol data blocking is enabled for the MPC+ Group.
216 MPC+>lis cm
MPC+ Connection Managers(CM)
Group Token type state
------------------------- ------- ----------
090261813400000035 PTP Active
216 MPC+>li conn 2
MPC+ Connections
Virtual Circuit Token = 090261898400000039
Remote Registration Token(s) = 0500010134
Protocol = APPN, State = Active-both sides
Local Connection Token = 0902618A480000003A
Remote Connection Token = 0500010135
State = Active
2216 MPC+>li sub 3
MPC+ Subchannels
Local Link CU Log. Device
number LPAR addr address address type state
------- ----- ----- ------- --------- ---------- ----------
1 1 CC 1 1 READ Active
0 1 CC 1 0 WRITE Active
2216 MPC+>ex
2216 +
Figure 268. TN3270E APPN/DLUR: MPC+ Monitoring
1 This command displays information about this MPC+ group. The state must be
active if everything is working properly.
2 Shows information about the connections running on the MPC+
group/connection manager. The information is shown in two parts: the virtual
circuit and the connections under the virtual circuit.
3 This command shows the active configuration for the subchannels. These
parameters must match the corresponding parameters in the host as seen in
Figure 238 on page 225.
To check all the protocols involved in this scenario, we will get each protocol
GWCON prompt. The first one is to check that the 2216 has the right IP
connectivity. Then we will check the APPN side of the scenario.
The base protocol is APPN, so we will check that it is running correctly, that the
link station to the host is active and that there is a CP-CP session established
between the 2216 and the host.
252 IBM 2216 and Network Utility Host Channel Connections

2216 +p appn
APPN GWCON
2216 APPN >li link
Name Port Name Intf Adj CP Name Type HPR State
=========================================================================
TOVTAM MPC00002 2 USIBMRA.RA03M NN ACTIVE ACT_LS
2216 APPN >li cp
CP Name Type Status Connwinner ID Conloser ID
========================================================================
USIBMRA.RA03M NN Active 366D2948 366D2947
2216 APPN >
Figure 269. TN3270E APPN/DLUR: APPN Monitoring
Then, we will check the status of the TN3270E Server. We will access the
TN3270E Server GWCON prompt from the APPN prompt.
2216 APPN >tn3270
TN3270E GWCON
2216 TN3270E >list ?
STATUS
CONNECTIONS
2216 TN3270E >lis status 1
TN3270E Server Status Summary
TN3270E IP Address: 192.194.200.1 TN3270E Port Number: 23
NetDisp Advisor Port Number: 10008
Keepalive type: None
Automatic Logoff: N
Number of connections: 1
Number of connections in SSCP-LU state: 0
Number of connections in LU-LU state: 1
2216 TN3270E >li connection 2
Connection information about all the LUs
Local LU Class Assoc LU Client Addr Status Prim LU Sec LU Idle Min
------------------------------------------------------------------------------
@01LU4 IW 10.0.0.10 LU-LU RA03N008 L2216D3 1
2216 TN3270E >
Figure 270. TN3270E APPN/DLUR: TN3270E Server Monitoring
1 The number of connections specifies the current number of active TCP
connections from TN3270 clients. The number of connections in LU-LU state is
the number of currently active client TCP connections that have an associated LU
in this state (received BIND, fully active).
2 This command displays all the connections currently active.
TN3270 Server Channel-Attached Configuration 253

254 IBM 2216 and Network Utility Host Channel Connections

Chapter 8. ESCON/PCA Comparison
8.1 Host Point of View
This appendix contains a brief description of the differences when defining an
ESCON or a PCA channel to the 2216.
We don’t explain in detail all the host and 2216 parameters that have to be set
during the configuration process, but we highlight the differences that have to be
considered when choosing the type of adapter.
For additional information about channel connectivity, please see IBM 2216
Nways Multiaccess Connector Installation and Initial Congfiguration Guide,
GA27-4106.
In fact the only differences when configuring an ESCON or a PCA adapter inside
the host are related to the IOCP Definitions.The VTAM definitions which are
needed for LSA, LCS and MPC+ are not affected.
With ESCON we can have access to different logical partitions using a single
ESCON port. For this we need an ESCON Director and the EMIF (ESCON
multiple image facility) functionality.
With PCA only one host or LP is accessible per physical interface.
What has to be defined exclusively for ESCON (ESCD in use)?
THE RESOURCE Definition of the logical host partition.
SWITCH This identifies which ESCON Director is in this path.
CUADD This value identifies the control unit address.
LINK The value for the LINK parameter should be set to the port of
the ESCON Director (ESCD) that the 2216 is attached to.
What has to be defined exclusively for PCA?
PROTOCOL Define the channel data transfer mode and speed.
What parameters are common but need to be configured due to the type of
channel, ESCON or PCA?
CHPID
Note
UDP+ is not supported on the Parallel Channel Adapter.
TYPE ESCON is either CNC (channel direct attached or through an
ESCON Director) or CVC (when an ESCON converter is
attached).
PCA is either BL (Block Multiplexer) or FX (ESCON converter
in the channel path).
© Copyright IBM Corp. 1998 255

CNTLUNIT
SHARED Shared specifies that the channel paths on the CHPID
macroinstruction are shared. The SHARED keyword has to
be set to ’N’ for the PCA.
IODEVICE
8.2 2216 Point of View
STADET STADET allows disabling of the Status Verification Facility.
STADET=Y enables the facility; STADET=N disables the
facility. The default for parallel devices is STADET=N. The
default for ESCON devices and devices assigned to OSA
channel paths is STADET=Y.
TIMEOUT Time-out specifies whether the I/O interface timeout
function is to be active for the following I/O interface
sequences between the channel and the I/O device:
4-second timeout for initial selection
30-second timeout for data transfer.
The TIMEOUT keyword is meaningful only for BL and CVC
channel paths.
Because the PCA cannot be connected to an ESCON Director, the only
differences during the configuration process are:
• At the configuration step for the SUBCHANNELS we cannot define the LPAR,
CU and LINK statement for an PCA channel, only DEVICE statement can be
set.
• For the PCA we have to set the data transfer mode and speed by typing at the
PCA> prompt: set Tmode value.
tmode value specifies the mode of transfer that the 2216 uses to transfer data to
the host, either DC interlock or data streaming and the channel transfer speed
when using data streaming.
Valid values:
D Specifies direct-coupled (DC) interlock mode. This mode is the
standard I/O interface that requires a response to a demand.
256 IBM 2216 and Network Utility Host Channel Connections
S Specifies speeds less than or equal to a 3.0 MB data streaming
mode.
S4 Specifies speeds less than or equal to a 4.5 MB data streaming
mode.
In Figure 271 on page 257 we display the comparison between ESCON and PCA
adapters while referring to the above description.

2216 Multiaccess Connector ESCON/PCA
Host Channel Definition Relationship
Host Channel Definitions
Host Channel Definitions
Figure 271. Comparison between ESCON and PCA
RESOURCE PART=((A1,1))
CHPID PATH=((2C),TYPE=BL
CHPID PATH=((2C),TYPE=CNC,PART=(A1),SWITCH=E1)
CNTLUNIT CUNMBR=0280,PATH=(2C),PROTOCL=S4,
SHARED=N
UNITADD+((00,032)),UNIT=3172
CNTLUNIT CUNMBR=0280,PATH=(2C),CUADD=1,
UNITADD+((00,032)),LINK=C9,UNIT=3172
IODEVICE UNIT=3172,ADDRESS=(280,32),
CUNMBR=(0280),STADET=N,TIMEOUT=Y
IODEVICE UNIT=3172,ADDRESS=(280,32),
CUNMBR=(0280)
LPAR 1
CHPID=2C
CHPID=2C
Address Range
00-FF (32 addresses)
Address Range
00-FF (32 addresses)
CC
ESCON
Director E1
C9
2216
2216
PCA Definitions:
ESCON Definitions:
Device 4
Tmode=S4
LPAR 1
CU 1
Device 4
Link CC
ESCON/PCA Comparison 257

258 IBM 2216 and Network Utility Host Channel Connections

Chapter 9. Backup Scenario
This chapter provides some backup recovery scenarios for the 2216 and the host.
9.1 ESCON Channel Gateway - High Availability
This scenario utilizes redundant 2216, each with an ESCON channel connection
to the host. Both uses different backbones so that the network is also recovered
from any failure in the path between the users and the host. In this configuration
the complete path between the end stations and the host is redundant, so that the
network is able to deal with any failure either in the cabling or in the networking
devices. The traffic coming in from the end stations will have a valid path to the
host through one campus backbone or through the other one. This is true for both
IP and SNA traffic.
This scenario does not consider a host failure. If you want to consider a possible
problem on the host, you can use two ESCON adapters per 2216. One ESCON
channel will attach to the primary host and the second ESCON channel will attach
to the backup host.
9.1.1 Network Environment Description
The network setup is shown in Figure 272 on page 260.
© Copyright IBM Corp. 1998 259

TCP/IP
VIPA= 192.168.250.3
------------------------------
XCA Major Node Definitions
CUADDR=284
ADAPNO=0
SAPADDR=4
MEDIUM=RING
.....
CUADDR=384
ADAPNO=0
SAPADDR=4
MEDIUM=RING
------------------------------
SW Major Node Definitions
VALENCIA ...
MAINZ ...
------------------------------
MVS IOCP Definitions
CHPID PATH=2C
....
CHPID PATH=4C
....
LSA MAC@
40002216000A
LCS IP@
192.168.125.4
8.8.8.1
18.18.18.1
Figure 272. ESCON Channel Gateway Backup Network Setup
In Figure 272 on page 260 each 2216 provides access to TCP/IP and SNA
applications on the host by means of an LSA and an LCS interface.
For SNA each 2216 will establish a TCP connection with the downstream 2210.
The DLSw sessions between the end stations and the host will run over this TCP
connection.
The primary link will be made up of 2210A and 2216A, path A, while the backup
will be formed by 2210B and 2216B, path B. In the DLSw configuration of the
2210s, some parameters available in MRS and MAS V3.2 have been used to
prevent path B from being used when path A is available. It is also possible to do
load balancing, by defining as partners of 2210A, 2216A and 2216B and playing
260 IBM 2216 and Network Utility Host Channel Connections
RA03
LPAR 1
D0
C2
2216A
192.194.100.0
2210A
RA28
LPAR 2
ESCD
10.0.0.0
16.0.0.0
RA39
LPAR 4
S/390
CC
C9
2216B
2210B
9.9.9.1
192.194.200.0
19.19.19.1
VRID 1 - MASTER VRID 1 - BACKUP
SNA: Dest MAC@=LSA MAC@
IP: Default Gateway=2210A IP@
LSA MAC@
40002216000A
LCS IP@
192.168.125.2

with the priority of the partners. For more information on DLSw configurations
refer to Nways Multiprotocol Access Services Protocol Configuration and
Monitoring Reference Volume 1, Version 3.2, SC30-3884.
On the host the configuration is as follows:
• 2216A is attached to the host. To activate this connection, the following
definitions have been made on the host:
• The 2216A has been defined in the IOCP definitions.
• An XCA major node definition has been included for this 2216A.
• To activate the connection between the host and 2216B, the definitions that
have been made are:
• The 2216B has been defined in IOCP.
• An XCA major node definition has been included for this 2216B.
Both XCA major node definitions are active at the same time, so that when a
problem is encountered and the SNA sessions switch from path A to B, no
manual intervention is needed on the host.
With this configuration, depending on where the failure occurs, there is or is not
SNA session disruption.
If there is a failure in the path between the DLSw partners, which means between
2216A/B and 2210A/B respectively, there is no session loss. The TCP connection
is established between the internal IP addresses of the partners. The internal IP
address is always up independently of the state of the interfaces in the router. So,
when there is a failure in the path between the two partners, the routing protocol,
OSPF in our case, will detect the failure and update the routing tables. After the
routing tables have been updated, the 2210 will be able to reach the partner 2216
through a different way. No SNA session disruption is possible thanks to the TKR
between both 2216s.
If the failure occurs in a place different from the path between the DLSw partners
there will be SNA session loss. In this case the SNA sessions will have to be
established through a different path, including different DLSw routers.
For the TCP/IP case, all the users in the network will access the host using the
VIPA address. By using the VIPA address and the RouteD functions on the host,
we will have fault-tolerant TCP connections providing automatic and transparent
recovery from controller and interface failure.
VIPA uses a virtual device and a virtual IP address. The virtual device will always
be active and never fail. A virtual IP address will be the HOME address for the
virtual device, but there will be no physical interface associated with it. Inbound
packets that have the virtual IP address as the destination will be routed through
any one of the real physical interfaces to MVS.
The LCS type of support that has been used in this scenario is LCS routing.
In the network there will be two autonomous systems, one running RIP and
another running OSPF. The LCS interface of the 2216A and B and the host will
run RIP while the rest of the IP network will run OSPF. The 2216s will then be AS
boundary routers.
Backup Scenario 261

Note
Be aware that with MAS V3.2 it is possible to run OSPF between the 2216 and
OS/390 when using LCS.
For having a full redundancy environment, VRRP (Virtual Router Redundancy
Protocol) has been configured in 2210A and 2210B. This will provide a redundant
default gateway.
9.1.2 Host Programs Definitions
Before we can attach both 2216s to the host, we need to define them.
9.1.2.1 IOCP and MVS Operating System Definitions
The IOCP definitions are shown in the following figure:
RESOURCE PARTITION=((A1,1) 1 ,(A2,2),(A3,3),(A4,4),(A5,5),(C1,6), *
(C2,7))
CHPID PATH=(2C),SHARED, *
PARTITION=((A1,A2,A3,A4),(A1,A2,A3,A4,A5)),SWITCH=E1, *
TYPE=CNC
CNTLUNIT CUNUMBR=0280,PATH=(2C),UNITADD=((00,032)) 2 ,LINK=(C9), *
CUADD=1 3 ,UNIT=3172
CNTLUNIT CUNUMBR=02A0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=2,UNIT=3172
CNTLUNIT CUNUMBR=02C0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=4,UNIT=3172
IODEVICE ADDRESS=(280,032),UNITADD=00,CUNUMBR=(0280),STADET=Y, *
PARTITION=(A1),UNIT=3172
IODEVICE ADDRESS=(2A0,032),UNITADD=00,CUNUMBR=(02A0),STADET=Y, *
PARTITION=(A2),UNIT=3172
IODEVICE ADDRESS=(2C0,032),UNITADD=00,CUNUMBR=(02C0),STADET=Y, *
PARTITION=(A4),UNIT=3172
CHPID PATH=(4C),SHARED, *
PARTITION=((A1,A2,A3,A4),(A1,A2,A3,A4,A5)),SWITCH=E1, *
TYPE=CNC
CNTLUNIT CUNUMBR=0380,PATH=(4C),UNITADD=((00,032)) 4 ,LINK=(C2), *
CUADD=1 5 ,UNIT=3172
CNTLUNIT CUNUMBR=03A0,PATH=(4C),UNITADD=((00,032)),LINK=(C2), *
CUADD=2,UNIT=3172
CNTLUNIT CUNUMBR=03C0,PATH=(4C),UNITADD=((00,032)),LINK=(C2), *
CUADD=4,UNIT=3172
IODEVICE ADDRESS=(380,032),UNITADD=00,CUNUMBR=(0380),STADET=Y, *
PARTITION=(A1),UNIT=3172
IODEVICE ADDRESS=(3A0,032),UNITADD=00,CUNUMBR=(03A0),STADET=Y, *
PARTITION=(A2),UNIT=3172
IODEVICE ADDRESS=(3C0,032),UNITADD=00,CUNUMBR=(03C0),STADET=Y, *
PARTITION=(A4),UNIT=3172
Figure 273. BACKUP: IOCP Definitions
1 Both 2216s will connect to LPAR 1.
2 The device address used for 2216B is 04 which is in the range of addresses.
3 Control unit address of the 2216B.
4 The device address used for 2216A is 04 which is in the range of addresses.
262 IBM 2216 and Network Utility Host Channel Connections

5 Control unit address of the 2216A.
For more information on what each parameter means, refer to Chapter 3,
“Sample Host Definitions” on page 27.
9.1.2.2 VTAM Definitions
The definitions we will need in VTAM are XCA Major Node, Switched Major Node,
and TCP/IP definitions.
XCA Major Node Definitions
There will be one definition per 2216.
The definitions for 2210A are in 9.1.4, “2210A Configuration” on page 268.
*******************************************************************
X5304 VBUILD TYPE=XCA
**
**
X5304PRT PORT ADAPNO=0, *
CUADDR=384, *
SAPADDR=4, *
MEDIUM=RING
X5304GRP GROUP DIAL=YES,CALL=INOUT,DYNPU=YES, *
AUTOGEN=(10,L,P)
Figure 274. XCA Major Node 2216A Definitions
The definitions for 2216B are:
*******************************************************************
X5303 VBUILD TYPE=XCA
**
**
X5303PRT PORT ADAPNO=0, *
CUADDR=284, *
SAPADDR=4, *
MEDIUM=RING
X5303GRP GROUP DIAL=YES,CALL=INOUT,DYNPU=YES, *
AUTOGEN=(10,L,P)
Figure 275. XCA Major Node 2216B Definitions
For more information on LSA definitions, refer to 4.3, “2216 LSA vs. Host
Parameter Relationships” on page 55.
Switched Major Node Definitions
These definitions will be the same ones used throughout the book. You can find
them in “Switched Major Node Definitions” on page 61.
9.1.2.3 TCP/IP Definitions
The TCP/IP profile will be the same used in 5.3.1.2, “TCP/IP Definitions for MVS”
on page 140 with some definitions added for 2216A. The definitions for both
2216s are shown in Figure 276 on page 264.
Backup Scenario 263

9.1.3 2216A Configuration
; *********************************************************
; VIPA Definition (For V2R5)
; *********************************************************
DEVICE VIPA3A VIRTUAL 0
LINK VIPA3A VIRTUAL 0 VIPA3A
;
;; *********************************************************
; LCS Definition
; 2216 T/R attach - Device # 3282-283
; *********************************************************
DEVICE D2216 LCS 282 autorestart
LINK LD2216 IBMTR 0 D2216
;
; *********************************************************
; LCS Definition
; 2216 T/R attach - Device # 382-383
; *********************************************************
DEVICE D2216A LCS 382 autorestart
LINK LD2216A IBMTR 0 D2216A
;
; **********************************************************
; -----------------------------------------------------------------------
;
; HOME Internet (IP) addresses of each link on the host.
;
; NOTE: To use this home statement, update the ipaddress and linknames
; to reflect your installation configuration and remove the semicolon
;
; HOME Internet (IP) addresses of each link on the host.
HOME
192.168.250.3 VIPA3A ; 1st VIPA Link (for V2R5)
192.168.125.1 LD2216
192.168.125.3 LD2216A
; -----------------------------------------------------------------------
;
; Start all the defined devices.
;
; NOTE: To use these START statements, update the device name
; to reflect your installation configuration and remove the semicolon
;
; Start all the defined devices.
START D2216
START D2216A
Figure 276. TCP/IP Definitions
The configuration of 2216A includes the ESCON and token-ring interfaces. From
the ESCON point of view the configuration is very similar to the ones in 4.4.2.2,
“2216 Configuration” on page 62 and 5.3.2.2, “2216 Configuration” on page 151.
9.1.3.1 Add and Configure the Interfaces
The interfaces will be two token-ring interfaces and an ESCON interface that will
include an LSA and an LCS virtual network interface.
264 IBM 2216 and Network Utility Host Channel Connections

Config (only)>add dev token
Device Slot #(1-8) [1]? 1
Device Port #(1-2) [1]? 1
Adding Token Ring device in slot 1 port 1 as interface #0
Use "net 0" to configure Token Ring parameters
Config (only)>add dev escon
Device Slot #(1-8) [1]? 3
Adding ESCON Channel device in slot 3 port 1 as interface #1
Use "net 1" to configure ESCON Channel parameters
Config (only)>net 1
ESCON Config>add lsa
ESCON Add Virtual>ena loopback
Enabling loopback through network 2.
Please set the MAC address using the "MAC" command
ESCON Add Virtual>lan token
ESCON Add Virtual>mac 40:00:22:16:00:0A 1
ESCON Add Virtual>sub add
ESCON Add LSA Subchannel>device 4
ESCON Add LSA Subchannel>link d0
ESCON Add LSA Subchannel>lpar 1
ESCON Add LSA Subchannel>cu 1
ESCON Add LSA Subchannel>ex
ESCON Add Virtual>ex
ESCON Config>add lcs
ESCON Add Virtual>lan token
ESCON Add Virtual>mac 40:00:22:16:00:A1
ESCON Add Virtual>sub add
Please add or configure one subchannel for an LCS virtual interface.
Although LCS requires two subchannels, it is only necessary to specify
one subchannel. An adjacent subchannel will be chosen such that the
two subchannels will form a sequential pair with the write subchannel
(device address is even) before the read subchannel (device address is
odd).
ESCON Config LCS Subchannel>device 2
ESCON Config LCS Subchannel>link d0
ESCON Config LCS Subchannel>lpar 1
ESCON Config LCS Subchannel>cu 1
ESCON Config LCS Subchannel>ex
ESCON Add Virtual>ex
ESCON Config>list all
Net: 2 Protocol: LSA LAN type: Token Ring LAN number: 0 2
Maxdata: 2052
Loopback is enabled.
MAC address: 40002216000A
Block Timer: 10 ms ACK length: 10 bytes
Sub 0 Dev addr: 4 LPAR: 1 Link addr: D0 CU addr: 1
Net: 3 Protocol: LCS LAN type: Token Ring LAN number: 1 3
Maxdata: 2052
MAC address: 4000221600A1
Block Timer: 5 ms ACK length: 10 bytes
Backup Scenario 265

266 IBM 2216 and Network Utility Host Channel Connections
Read Subchannels:
Sub 0 Dev addr: 3 LPAR: 1 Link addr: D0 CU addr: 1
Write Subchannels:
Sub 1 Dev addr: 2 LPAR: 1 Link addr: D0 CU addr: 1
ESCON Config>ex
ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]: y
Config (only)>
Config (only)>add dev token
Device Slot #(1-8) [1]?
Device Port #(1-2) [2]?
Adding Token Ring device in slot 1 port 2 as interface #4
Use "net 4" to configure Token Ring parameters
Config (only)>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 ESCON Channel Slot: 3 Port: 1
Ifc 2 LSA - ESCON Channel Base Net: 1
Ifc 3 LCS - ESCON Channel Base Net: 1
Ifc 4 Token Ring Slot: 1 Port: 2
1 This is the MAC address that will identify the host in the network. This same
MAC address will be configured in the LSA interface of 2216B. In this way, when a
problem occurs in the network and the SNA sessions flow through path B, it will
be transparent to the stations that they address will always be the same host
MAC address.
2 and 3 are the LAN numbers assigned by the 2216 to these virtual LANs. These
values need to match the definitions on the host as explained in previous
chapters.
9.1.3.2 Protocol IP Configuration
We need the IP support for running DLSw and also because the stations will need
IP access to the host for the TCP/IP applications.
The LCS interface will be in a different subnet from all the other interfaces in the
2216. Due to our host configuration, this LCS interface and the LCS interface in
2216B will be in the same subnet. This does not necessarily have to be like this,
since the VIPA address is reachable through any link on the host.
Config (only)>p ip
Internet protocol user configuration
IP config>add add 0 192.194.100.1 255.255.255.0
IP config>add add 3 192.168.125.4 255.255.255.0 1
IP config>add add 4 10.0.0.2 255.255.255.0
IP config>set int 8.8.8.1
IP config>ena rip 2
IP config>ex
Config (only)>p ospf
Open SPF-Based Routing Protocol configuration console
OSPF config>ena ospf
Estimated # external routes [100]?
Estimated # OSPF routers [50]?

Maximum Size LSA [2048]?
OSPF config>set int 192.194.100.1
Attaches to area [0.0.0.0]?
Retransmission Interval (in seconds) [5]?
Transmission Delay (in seconds) [1]?
Router Priority [1]?
Hello Interval (in seconds) [10]?
Dead Router Interval (in seconds) [40]?
TOS 0 cost [1]?
Demand Circuit (Yes or No)? [No]:
Authentication Type (0 - None, 1 - Simple) [0]?
OSPF config>set int 10.0.0.2
Attaches to area [0.0.0.0]?
Retransmission Interval (in seconds) [5]?
Transmission Delay (in seconds) [1]?
Router Priority [1]?
Hello Interval (in seconds) [10]?
Dead Router Interval (in seconds) [40]?
TOS 0 cost [1]?
Demand Circuit (Yes or No)? [No]:
Authentication Type (0 - None, 1 - Simple) [0]?
OSPF config>ena as
Import BGP routes? [No]:
Import RIP routes? [No]: yes
Import static routes? [No]:
Import direct routes? [No]: yes
Import subnet routes? [Yes]:
Always originate default route? [No]:
Originate default if BGP routes available? [No]:
OSPF config>li all
--Global configuration--
OSPF Protocol: Enabled
# AS ext. routes: 100
Estimated # routers: 50
Maximum LSA size: : 2048
External comparison: Type 2
RFC 1583 compatibility: Enabled
AS boundary capability: Enabled
Import external routes: RIP DIR SUB
Orig. default route: No (0,0.0.0.0)
Default route cost: (1, Type 2)
Default forward. addr.: 0.0.0.0
Multicast forwarding: Disabled
Demand Circuits: Enabled
Least Cost Area Ranges: Disabled
Maximum Random LSA Age: 0
--Area configuration--
Area ID Stub? Default-cost Import-summaries?
0.0.0.0(Implicit) No N/A N/A
--Interface configuration--
IP address Area Auth Cost Rtrns Delay Pri Hello Dead
192.194.100.1 0.0.0.0 0 1 5 1 1 10 40
Backup Scenario 267

10.0.0.2 0.0.0.0 0 1 5 1 1 10 40
OSPF Config>ex
Config (only)>
1 The IP address of the LCS interface needs to be in the same subnet as the
HOME address for the link to the 2216 on the host. It has to be in a different
subnet from all the other interfaces in this 2216.
2 RIP is enabled in the path between the 2216And the host since our host is
running RIP. If your host is running OSPF, you will have to use MAS V3.2 in the
2216.
9.1.3.3 DLS Configuration
We do not need to configure bridging since we do not need to do it in the DLSw
end of the loopback connection in the LSA interface. So, we will configure DLSw
since the IP support needed in DLSw has been configured in the previous step.
DLSw protocol user configuration
DLSw config>ena dls
Data Link Switching is now enabled
DLSw config>add tcp 18.18.18.1
Connectivity Setup Type (a/p) [p]?
Transmit Buffer Size (Decimal) [5120]?
Receive Buffer Size (Decimal) [5120]?
Maximum Segment Size (Decimal) [1024]?
TCP Keepalive (E/D) [D]?
NetBIOS SessionAlive Spoofing (E/D) [D]?
Neighbor Priority (H/M/L) [M]?
TCP Neighbor has been added
DLSw config>set srb d0A
DLSw segment number has been set.
DLSw config>open 2 sna 1
SAP(s) 0 4 8 C opened on interface 2
DLSw config>ex
Config (only)>
Figure 277. 2216A: DLSw Configuration
1 SNA SAPs are opened in the LSA interface.
9.1.4 2210A Configuration
The 2210A is configured for DLSw and for TCP/IP.
The 2210A token-ring IP address is the default gateway for all the PCs attached
to the token-ring 16.0.0.0. For redundant purposes, VRRP has been configured
as 2210A, the master (owner of the default gateway IP address), and 2210B, the
backup. For more information on VRRP refer to Nways Multiprotocol Access
Services Protocol Configuration and Monitoring Reference Volume 1, Version 3.2,
SC30-3884.
Config (only)>li dev
Ifc 0 Token Ring CSR 6000000, vector 95
Ifc 1 WAN PPP CSR 81600, CSR2 80C00, vector 94
Ifc 2 WAN PPP CSR 81620, CSR2 80D00, vector 93
268 IBM 2216 and Network Utility Host Channel Connections

Ifc 3 WAN PPP CSR 81640, CSR2 80E00, vector 92
Ifc 4 WAN PPP CSR 81660, CSR2 80F00, vector 91
Ifc 5 Token Ring CSR 6000100, vector 90
Ifc 6 1-port ISDN Primary T1/J1 CSR 0, vector 0
Config (only)>p ip
Internet protocol user configuration
2210A IP config>add add 0 16.0.0.1 255.255.255.0
2210A IP config>add add 5 192.194.100.2 255.255.255.0
2210A IP config>set int 18.18.18.1
2210A IP config>ex
Config (only)>p ospf
Open SPF-Based Routing Protocol configuration console
2210A OSPF Config>ena ospf
Estimated # external routes [100]?
Estimated # OSPF routers [50]?
Maximum Size LSA [2048]?
2210A OSPF Config>set int 192.194.100.2
Attaches to area [0.0.0.0]?
Retransmission Interval (in seconds) [5]?
Transmission Delay (in seconds) [1]?
Router Priority [1]?
Hello Interval (in seconds) [10]?
Dead Router Interval (in seconds) [40]?
TOS 0 cost [1]?
Demand Circuit (Yes or No)? [No]:
Authentication Type (0 - None, 1 - Simple) [0]?
2210A OSPF Config>set int 16.0.0.1
Attaches to area [0.0.0.0]?
Retransmission Interval (in seconds) [5]?
Transmission Delay (in seconds) [1]?
Router Priority [1]?
Hello Interval (in seconds) [10]?
Dead Router Interval (in seconds) [40]?
TOS 0 cost [1]?
Demand Circuit (Yes or No)? [No]:
Authentication Type (0 - None, 1 - Simple) [0]?
2210A OSPF Config>li all
--Global configuration--
OSPF Protocol: Enabled
# AS ext. routes: 100
Estimated # routers: 50
Maximum LSA size: : 2048
External comparison: Type 2
RFC 1583 compatibility: Enabled
AS boundary capability: Disabled
Multicast forwarding: Disabled
Demand Circuits: Enabled
Least Cost Area Ranges: Disabled
Maximum Random LSA Age: 0
--Area configuration--
Area ID Stub? Default-cost Import-summaries?
Backup Scenario 269

0.0.0.0(Implicit) No N/A N/A
--Interface configuration--
IP address Area Auth Cost Rtrns Delay Pri Hello Dead
192.194.100.2 0.0.0.0 0 1 5 1 1 10 40
16.0.0.1 0.0.0.0 0 1 5 1 1 10 40
2210A OSPF Config>ex
Config (only)>
Config (only)>p asrt
Adaptive Source Routing Transparent Bridge user configuration
2210A ASRT config>ena bridge
2210A ASRT config>ena dls
2210A ASRT config>li port
Port ID (dec) : 128:01, (hex): 80-01
Port State : Enabled
STP Participation: Enabled
Port Supports : Transparent Bridging Only
Assoc Interface : 0
Path Cost : 0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Port ID (dec) : 128:02, (hex): 80-02
Port State : Enabled
STP Participation: Enabled
Port Supports : Transparent Bridging Only
Assoc Interface : 5
Path Cost : 0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2210A ASRT config>del port 2
2210A ASRT config>dis trans 1
2210A ASRT config>ena sour 1
Segment Number for the port in hex(1 - FFF) [001]? 100
Bridge number in hex (0 - 9, A - F) [0]? 2
2210A ASRT config>ex
Config (only)>
Config (only)>p dls
DLSw protocol user configuration
2210A DLSw config>ena dls
Data Link Switching is now enabled
2210A DLSw config>add tcp 8.8.8.1
Connectivity Setup Type (a/p) [p]?
Transmit Buffer Size (Decimal) [5120]?
Receive Buffer Size (Decimal) [5120]?
Maximum Segment Size (Decimal) [1024]?
TCP Keepalive (E/D) [D]?
NetBIOS SessionAlive Spoofing (E/D) [D]?
Neighbor Priority (H/M/L) [M]?
TCP Neighbor has been added
2210A DLSw config>set srb d0A
DLSw segment number has been set.
2210A DLSw config>open 0 sna
SAP(s) 0 4 8 C opened on interface 0
2210A DLSw config>add explorer 1
Enter MAC Address Value [000000000000]? 40002216000A
270 IBM 2216 and Network Utility Host Channel Connections

Enter MAC Address Mask [FFFFFFFFFFFF]?
Database age timeout (0-10000 secs. Decimal) [1200]?
Max wait timer ICANREACH (1-1000 secs. Decimal) [20]?
Neighbor priority wait timer (0, 1.0-5.0 secs. Decimal) [2.0]? 0
Time to delay sending test response (0.0-5.0 secs. Decimal) [0.0]?
Forwarding Explorers (E/L/D) [E]?
Enter position in explorer override list to insert new entry .....
Record number (0=add at end of list) [0]?
Explorer override record has been created.
2210A DLSw config>ex
Config (only)>
Config (only)>p ip
Internet protocol user configuration
2210A IP config>ena vrrp
2210A IP config>add vrid
IP Interface []? 16.0.0.1
VRID (1-255) [0]? 1
Advertisement Interval (1-255) [1]?
Backup Virtual Router? [No]:
Use Functional/Group Address? [No]:
Authentication Type (0 - None, 1 - Simple) [0]?
VRID 16.0.0.1/1 added successfully
2210A IP config>li vrid
VRRP Enabled
--VRID Definitions--
IP address Priority Interval Auth Auth-key Flags Address(es)
16.0.0.1 1 255 1 None N/A X
2210A IP config>ex
Config (only)>
9.1.5 2216B Configuration
1 With this command and by setting the wait neighbor priority timer to 0 we
specify that the DSLw partner information is not cached for this MAC address,
which is the MAC address of the host. In this way we prevent the 2210A from
replying to the test frames from the stations just because the destination MAC
address of the frames is in its cache, in case it cannot reach the destination MAC
address. If the destination MAC address is not in its cache the router will try to
contact this MAC address before replying to the test.
9.1.5.1 Add and Configure the Interfaces
The interfaces that have to be configured in this 2216 are the token-ring, PPP and
ESCON interfaces. The ESCON adapter will have an LSA and an LCS virtual
interfaces.
2216B Config>add dev eia
Device Slot #(1-8) [1]? 8
Device Port #(0-7) [1]? 0
Defaulting Data-link protocol to PPP
Adding EIA-232E/V.24 PPP device in slot 8 port 0 as interface #0
Backup Scenario 271

Use "set data-link" command to change the data-link protocol
Use "net 0" to configure EIA-232E/V.24 PPP parameters
2216B Config>add dev escon
Device Slot #(1-8) [1]? 3
Adding ESCON Channel device in slot 3 port 1 as interface #1
Use "net 1" to configure ESCON Channel parameters
2216B Config>net 1
2216B ESCON Config>add lsa
2216B ESCON Add Virtual>ena loopback
Enabling loopback through network 2.
Please set the MAC address using the "MAC" command
2216B ESCON Add Virtual>lan token
2216B ESCON Add Virtual>mac 40:00:22:16:00:0A 1
2216B ESCON Add Virtual>sub add
2216B ESCON Add LSA Subchannel>device 4
2216B ESCON Add LSA Subchannel>link cc
2216B ESCON Add LSA Subchannel>lpar 1
2216B ESCON Add LSA Subchannel>cu 1
2216B ESCON Add LSA Subchannel>ex
2216B ESCON Add Virtual>ex
2216B ESCON Config>add lcs
2216B ESCON Add Virtual>lan token
2216B ESCON Add Virtual>mac 40:00:22:16:00:B1
2216B ESCON Add Virtual>sub add
Please add or configure one subchannel for an LCS virtual interface.
Although LCS requires two subchannels, it is only necessary to specify
one subchannel. An adjacent subchannel will be chosen such that the two
subchannels will form a sequential pair with the write subchannel (device
address is even) before the read subchannel (device address is odd).
2216B ESCON Config LCS Subchannel>device 2
2216B ESCON Config LCS Subchannel>link cc
2216B ESCON Config LCS Subchannel>lpar 1
2216B ESCON Config LCS Subchannel>cu 1
2216B ESCON Config LCS Subchannel>ex
2216B ESCON Add Virtual>ex
2216B ESCON Config>list all
Net: 2 Protocol: LSA LAN type: Token Ring LAN number: 0 2
Maxdata: 2052
Loopback is enabled.
MAC address: 40002216000A
Block Timer: 10 ms ACK length: 10 bytes
Sub 0 Dev addr: 4 LPAR: 1 Link addr: CC CU addr: 1
Net: 3 Protocol: LCS LAN type: Token Ring LAN number: 1 3
Maxdata: 2052
MAC address: 4000221600B1
Block Timer: 5 ms ACK length: 10 bytes
Read Subchannels:
Sub 0 Dev addr: 3 LPAR: 1 Link addr: CC CU addr: 1
Write Subchannels:
Sub 1 Dev addr: 2 LPAR: 1 Link addr: CC CU addr: 1
2216B ESCON Config>ex
272 IBM 2216 and Network Utility Host Channel Connections

ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]: y
216B Config>add dev token
Device Slot #(1-8) [1]?
Device Port #(1-2) [1]? 2
Adding Token Ring device in slot 1 port 2 as interface #4
Use "net 4" to configure Token Ring parameters
2216B Config>li dev
Ifc 0 EIA-232E/V.24 PPP Slot: 8 Port: 0
Ifc 1 ESCON Channel Slot: 3 Port: 1
Ifc 2 LSA - ESCON Channel Base Net: 1
Ifc 3 LCS - ESCON Channel Base Net: 1
Ifc 4 Token Ring Slot: 1 Port: 2
1 This is the same MAC address that has been configured before in the LSA
interface of the 2216A and that will identify the host in the network.
2 and 3 are the LAN numbers assigned to these interfaces internally by the 2216
and that need to match the definitions on the host. If these values do not match
the definitions on the host the link between the 2216 and the host will not become
active. For more information about the relationship between these values in the
2216 and on the host, refer to Figure 38 on page 56 and Figure 146 on page 138
for LSA and LCS respectively.
9.1.5.2 Configure IP Protocol
The IP configuration will be as follows:
2216B Config>p ip
Internet protocol user configuration
2216B IP config>add addr 0 192.194.200.1 255.255.255.0
2216B IP config>add addr 3 192.168.125.2 255.255.255.0 1
2216B IP config>add add 4 10.0.0.1 255.255.255.0
2216B IP config>set int 9.9.9.1
2216B IP config>ena rip 2
2216B IP config>ex
2216B Config>p ospf
Open SPF-Based Routing Protocol configuration console
2216B OSPF Config>ena ospf
Estimated # external routes [100]?
Estimated # OSPF routers [50]?
Maximum Size LSA [2048]?
2216B OSPF Config>set int 192.194.200.1
Attaches to area [0.0.0.0]?
Retransmission Interval (in seconds) [5]?
Transmission Delay (in seconds) [1]?
Router Priority [1]?
Hello Interval (in seconds) [10]?
Dead Router Interval (in seconds) [40]?
TOS 0 cost [1]?
Demand Circuit (Yes or No)? [No]:
Authentication Type (0 - None, 1 - Simple) [0]?
2216B OSPF Config>set int 10.0.0.1
Attaches to area [0.0.0.0]?
Backup Scenario 273

Retransmission Interval (in seconds) [5]?
Transmission Delay (in seconds) [1]?
Router Priority [1]?
Hello Interval (in seconds) [10]?
Dead Router Interval (in seconds) [40]?
TOS 0 cost [1]?
Demand Circuit (Yes or No)? [No]:
Authentication Type (0 - None, 1 - Simple) [0]?
2216B OSPF Config>ena as
Import BGP routes? [No]:
Import RIP routes? [No]: yes
Import static routes? [No]:
Import direct routes? [No]: yes
Import subnet routes? [Yes]:
Always originate default route? [No]:
Originate default if BGP routes available? [No]:
2216B OSPF Config>li all
274 IBM 2216 and Network Utility Host Channel Connections
--Global configuration--
OSPF Protocol: Enabled
# AS ext. routes: 100
Estimated # routers: 50
Maximum LSA size: : 2048
External comparison: Type 2
RFC 1583 compatibility: Enabled
AS boundary capability: Enabled
Import external routes: RIP DIR SUB
Orig. default route: No (0,0.0.0.0)
Default route cost: (1, Type 2)
Default forward. addr.: 0.0.0.0
Multicast forwarding: Disabled
Demand Circuits: Enabled
Least Cost Area Ranges: Disabled
Maximum Random LSA Age: 0
--Area configuration--
Area ID Stub? Default-cost Import-summaries?
0.0.0.0(Implicit) No N/A N/A
--Interface configuration--
IP address Area Auth Cost Rtrns Delay Pri Hello Dead
192.194.200.1 0.0.0.0 0 1 5 1 1 10 40
10.0.0.1 0.0.0.0 0 1 5 1 1 10 40
2216B OSPF Config>ex
2216B Config>
1 The IP address of the LCS interface has to be in the same subnet as the HOME
address of the link to this 2216 on the host.
2 We configure RIP in the connection between the 2216 and the host since the
host supports RIP.

9.1.5.3 DLSw Configuration
After configuring IP and because we do not have to configure bridging, we
configure DLSw. We do not need to configure bridging because the LSA interface
does not need it even it is the endpoint of the DLSw circuit.
2216B Config>p dls
DLSw protocol user configuration
2216B DLSw config>ena dls
Data Link Switching is now enabled
2216B DLSw config>add tcp 19.19.19.1
Connectivity Setup Type (a/p) [p]?
Transmit Buffer Size (Decimal) [5120]?
Receive Buffer Size (Decimal) [5120]?
Maximum Segment Size (Decimal) [1024]?
TCP Keepalive (E/D) [D]?
NetBIOS SessionAlive Spoofing (E/D) [D]?
Neighbor Priority (H/M/L) [M]?
TCP Neighbor has been added
2216B DLSw config>set srb d0B
DLSw segment number has been set.
2216B DLSw config>open 2 sna 1
SAP(s) 0 4 8 C opened on interface 2
2216B DLSw config>ex
2216B Config>
Figure 278. 2216B: DLSw Configuration
1 SAPs are opened in the LSA interface.
9.1.6 2210B Configuration
The 2210B configuration is practically the same as for the 2210A.
Config (only)>li dev
Ifc 0 Token Ring CSR 6000000, vector 95
Ifc 1 WAN PPP CSR 81600, CSR2 80C00, vector 94
Ifc 2 WAN PPP CSR 81620, CSR2 80D00, vector 93
Ifc 3 WAN PPP CSR 81640, CSR2 80E00, vector 92
Ifc 4 WAN PPP CSR 81660, CSR2 80F00, vector 91
Config (only)>p ip
Internet protocol user configuration
2210B IP config>add add 0 16.0.0.2 255.255.255.0
2210B IP config>add add 1 192.194.200.2 255.255.255.0
2210B IP config>set int 19.19.19.1
Config (only)>p ospf
Open SPF-Based Routing Protocol configuration console
2210B OSPF Config>ena ospf
Estimated # external routes [100]?
Estimated # OSPF routers [50]?
Maximum Size LSA [2048]?
2210B OSPF Config>set int 192.194.200.2
Attaches to area [0.0.0.0]?
Retransmission Interval (in seconds) [5]?
Backup Scenario 275

Transmission Delay (in seconds) [1]?
Router Priority [1]?
Hello Interval (in seconds) [10]?
Dead Router Interval (in seconds) [40]?
TOS 0 cost [1]?
Demand Circuit (Yes or No)? [No]:
Authentication Type (0 - None, 1 - Simple) [0]?
2210B OSPF Config>set int 16.0.0.2
Attaches to area [0.0.0.0]?
Retransmission Interval (in seconds) [5]?
Transmission Delay (in seconds) [1]?
Router Priority [1]?
Hello Interval (in seconds) [10]?
Dead Router Interval (in seconds) [40]?
TOS 0 cost [1]?
Demand Circuit (Yes or No)? [No]:
Authentication Type (0 - None, 1 - Simple) [0]?
2210B OSPF Config>li all
276 IBM 2216 and Network Utility Host Channel Connections
--Global configuration--
OSPF Protocol: Enabled
# AS ext. routes: 100
Estimated # routers: 50
Maximum LSA size: : 2048
External comparison: Type 2
RFC 1583 compatibility: Enabled
AS boundary capability: Disabled
Multicast forwarding: Disabled
Demand Circuits: Enabled
Least Cost Area Ranges: Disabled
Maximum Random LSA Age: 0
--Area configuration--
Area ID Stub? Default-cost Import-summaries?
0.0.0.0(Implicit) No N/A N/A
--Interface configuration--
IP address Area Auth Cost Rtrns Delay Pri Hello Dead
192.194.200.2 0.0.0.0 0 1 5 1 1 10 40
16.0.0.2 0.0.0.0 0 1 5 1 1 10 40
2210B OSPF Config>ex
Config (only)>p asrt
Adaptive Source Routing Transparent Bridge user configuration
2210B ASRT config>ena bridge
2210B ASRT config>ena dls
2210B ASRT config>li port
Port ID (dec) : 128:01, (hex): 80-01
Port State : Enabled
STP Participation: Enabled
Port Supports : Transparent Bridging Only
Assoc Interface : 0
Path Cost : 0
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2210B ASRT config>dis trans 1

2210B ASRT config>ena sour 1
Segment Number for the port in hex(1 - FFF) [001]? 100
Bridge number in hex (0 - 9, A - F) [0]? 1
2210B ASRT config>ex
Config (only)>p dls
DLSw protocol user configuration
2210B DLSw config>ena dls
Data Link Switching is now enabled
2210B DLSw config>add tcp 9.9.9.1
Connectivity Setup Type (a/p) [p]?
Transmit Buffer Size (Decimal) [5120]?
Receive Buffer Size (Decimal) [5120]?
Maximum Segment Size (Decimal) [1024]?
TCP Keepalive (E/D) [D]?
NetBIOS SessionAlive Spoofing (E/D) [D]?
Neighbor Priority (H/M/L) [M]?
TCP Neighbor has been added
2210B DLSw config>open 0 sna
SAP(s) 0 4 8 C opened on interface 0
2210B DLSw config>set srb d0B
DLSw segment number has been set.
2210B DLSw config>add explorer 1
Enter MAC Address Value [000000000000]? 40002216000A
Enter MAC Address Mask [FFFFFFFFFFFF]?
Database age timeout (0-10000 secs. Decimal) [1200]?
Max wait timer ICANREACH (1-1000 secs. Decimal) [20]?
Neighbor priority wait timer (0, 1.0-5.0 secs. Decimal) [2.0]? 0
Time to delay sending test response (0.0-5.0 secs. Decimal) [0.0]? 2
Forwarding Explorers (E/L/D) [E]?
Enter position in explorer override list to insert new entry .....
Record number (0=add at end of list) [0]?
Explorer override record has been created.
2210B DLSw config>ex
Config (only)>
Config (only)>p ip
Internet protocol user configuration
2210B IP config>ena vrrp
2210B IP config>add vrid
IP Interface []? 16.0.0.2
VRID (1-255) [0]? 1
Advertisement Interval (1-255) [1]?
Backup Virtual Router? [No]: yes
Backup IP address []? 16.0.0.1
Priority (1-254) [100]?
Use Functional/Group Address? [No]:
Authentication Type (0 - None, 1 - Simple) [0]?
VRID 16.0.0.2/1 added successfully
2210B IP config>li vrid
VRRP Enabled
--VRID Definitions--
IP address VRID Priority Interval Auth Auth-key Flags Address(es)
Backup Scenario 277

16.0.0.2 1 100 1 None N/A B,X 16.0.0.1
2210B IP config>ex
Config (only)>
1 With this command and by setting the wait neighbor priority timer to 0 we
specify that the DSLw partner information is not cached for this MAC address,
which is the MAC address of the host. By this way we prevent the 2210A from
replying to test frames from end stations when it cannot reach the destination
MAC address just because this destination MAC address is in its cache. If the
destination MAC address is not in its cache the router will try to contact this MAC
address before replying to the test.
Delay sending TEST response is the amount of time to wait after completing
exploration for a MAC address before sending the TEST response. This will allow
us to control which path is the primary and which one is the backup. Putting in
this 2210A value different from 0 will prevent the stations from establishing the
DLSw session through path B if path A is available.
9.2 LSA Direct Connection Backup
In this scenario we would like to show a very simple backup for SNA connection
against host failure and ESCON adapter malfunction in the 2216. To do so, we
are connecting two different ESCON adapters in the 2216 to two different LPARs
(representing two different hosts) using the LSA direct connection. Both LSA
interfaces (each on a separate physical adapter) on the 2216 are connected via
the net command at the ESCON/PCA Add Virtual> prompt to the same LAN
adapter.
9.2.1 Network Environment Description
Figure 279 describes our network setup:
278 IBM 2216 and Network Utility Host Channel Connections

XCA Major Node Definitions
ADAPTNO=0
SAPADDR=4
MEDIUM=RING
CUADDR=284
------------------------------
SW Major Node Definitions
VALENCIA ...
MAINZ ...
------------------------------
MVSIOCPDefinitions
UNITADD=04
CUADD=1
PATH=2C
9.2.2 Recovery at Host Failure
400000004020
RA03
LPAR 1
MAINZ
Figure 279. LSA Direct Connection Backup
RA28
LPAR 2
RA39
LPAR 4
For our backup description the initial position is that LPAR 1 is the primary host
which is connected to LSA 1 on the 2216. LPAR 4 is our backup system. The
XCA major node for this system is inactive.
In our scenario two LSA interfaces are linked to the same LAN adapter in the
2216 with the same SAP address defined in the XCA major node definition, so
only one XCA can be active at a time. This is true also when both LSAs are
configured on the same physical ESCON/PCA adapter.
In case of LPAR 1 failure, and the XCA for LPAR 1 becomes inactive, we have to
activate the XCA for LPAR 4 on the host via the V NET,ACT,ID=XCAname4 command. Of
course the user (here PCs VALENCIA and MAINZ) will face a temporary session
loss.
9.2.3 Recovery at 2216 Channel Failure
At channel adapter failure on the 2216, we have to deactivate the XCA major
node on LPAR 1 first (V NET,INACT,ID=XCAname1) and then we have to activate the
XCA major node for LPAR 4 (V NET,ACT,ID=XCAname4). The user will face a temporary
session loss.
CC
C9
LSA1
2C 4C
ESCD
LAN 2216
TR
D0
C2
LSA2
40002216000A
S/390
'NET' link
40000A000042
VALENCIA
XCA Major Node Definitions
ADAPTNO=0
SAPADDR=4
MEDIUM=RING
CUADDR=384
------------------------------
SW Major Node Definitions
VALENCIA ...
MAINZ ...
------------------------------
MVSIOCPDefinitions
UNITADD=04
CUADD=1
PATH=4C
Backup Scenario 279

9.2.4 Host Program Definitions
Before we can attach the 2216 to the host, we need to define it.
9.2.4.1 IOCP and MVS Operating System Definitions
The IOCP definitions are shown in the following figure:
RESOURCE PARTITION=((A1,1) 1 ,(A2,2),(A3,3),(A4,4) ,(A5,5),(C1,6), *
(C2,7))
CHPID PATH=(2C),SHARED, *
PARTITION=((A1,A2,A3,A4),(A1,A2,A3,A4,A5)),SWITCH=E1, *
TYPE=CNC
CNTLUNIT CUNUMBR=0280,PATH=(2C),UNITADD=((00,032)) 2 ,LINK=(C9), *
CUADD=1 3 ,UNIT=3172
CNTLUNIT CUNUMBR=02A0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=2,UNIT=3172
CNTLUNIT CUNUMBR=02C0,PATH=(2C),UNITADD=((00,032)),LINK=(C9), *
CUADD=4,UNIT=3172
IODEVICE ADDRESS=(280,032),UNITADD=00,CUNUMBR=(0280),STADET=Y, *
PARTITION=(A1),UNIT=3172
IODEVICE ADDRESS=(2A0,032),UNITADD=00,CUNUMBR=(02A0),STADET=Y, *
PARTITION=(A2),UNIT=3172
IODEVICE ADDRESS=(2C0,032),UNITADD=00,CUNUMBR=(02C0),STADET=Y, *
PARTITION=(A4),UNIT=3172
CHPID PATH=(4C),SHARED, *
PARTITION=((A1,A2,A3,A4),(A1,A2,A3,A4,A5)) 4,SWITCH=E1, *
TYPE=CNC
CNTLUNIT CUNUMBR=0380,PATH=(4C),UNITADD=((00,032)) 5 ,LINK=(C2), *
CUADD=1 6 ,UNIT=3172
CNTLUNIT CUNUMBR=03A0,PATH=(4C),UNITADD=((00,032)),LINK=(C2), *
CUADD=2,UNIT=3172
CNTLUNIT CUNUMBR=03C0,PATH=(4C),UNITADD=((00,032)),LINK=(C2), *
CUADD=4,UNIT=3172
IODEVICE ADDRESS=(380,032),UNITADD=00,CUNUMBR=(0380),STADET=Y, *
PARTITION=(A1),UNIT=3172
IODEVICE ADDRESS=(3A0,032),UNITADD=00,CUNUMBR=(03A0),STADET=Y, *
PARTITION=(A2),UNIT=3172
IODEVICE ADDRESS=(3C0,032),UNITADD=00,CUNUMBR=(03C0),STADET=Y, *
PARTITION=(A4),UNIT=3172
Figure 280. Backup: IOCP Definitions
1 The LSA on the first ESCON adapter will connect to LPAR 1.
2 The device address used for the LSA on the first ESCON Adapter is 04 which is
in the range of addresses.
3 Control unit address of the 2216B.
4 The LSA on the second ESCON adapter will connect to LPAR 4.
5 The device address used for the LSA on the second ESCON Adapter is 04
which is in the range of addresses.
6 Control unit address of the 2216B.
For more information on what each parameter means, refer to Chapter 3,
“Sample Host Definitions” on page 27.
280 IBM 2216 and Network Utility Host Channel Connections

9.2.4.2 VTAM Definitions
The definitions we will need in VTAM are:
• XCA Major Node Definitions
There will be one definition for each LSA connection, one on LPAR 1 and one
on LPAR 4. The definitions for LPAR 1 are shown in Figure 281; the definitions
for LPAR 4 are shown in Figure 282:
*******************************************************************
X5303 VBUILD TYPE=XCA
**
**
X5303PRT PORT ADAPNO=0, *
CUADDR=284, *
SAPADDR=4, *
MEDIUM=RING
X5303GRP GROUP DIAL=YES,CALL=INOUT,DYNPU=YES, *
AUTOGEN=(10,L,P)
Figure 281. XCA Major Node Definitions on LPAR 1
*******************************************************************
X5304 VBUILD TYPE=XCA
**
**
X5303PRT PORT ADAPNO=0, *
CUADDR=384, *
SAPADDR=4, *
MEDIUM=RING
X5303GRP GROUP DIAL=YES,CALL=INOUT,DYNPU=YES, *
AUTOGEN=(10,L,P)
Figure 282. XCA Major Node Definitions on LPAR 4
For more information on LSA definitions, refer to 4.3, “2216 LSA vs. Host
Parameter Relationships” on page 55.
• Switched Major Node Definitions
These definitions will be the same ones used in 3.4.1, “VTAM XCA Major Node
Definition” on page 33.
9.2.5 2216 Configuration
The configuration on the 2216 is very similar to the configuration described in
4.1.2, “LSA DLSw Connection” on page 50. Here we have to add and configure
the token-ring adapter and two ESCON adapters, each with an LSA for direct
connection to the host.
Backup Scenario 281

9.2.5.1 Add the Devices
*t6
2216B Config>add dev token
Device Slot #(1-8) [1]? 1
Device Port #(1-2) [1]? 1
Adding Token Ring device in slot 1 port 1 as interface #0
Use "net 0" to configure Token Ring parameters
2216B Config>add dev escon
Device Slot #(1-8) [1]? 2
Adding ESCON Channel device in slot 2 port 1 as interface #1
Use "net 1" to configure ESCON Channel parameters
2216B Config>add dev escon
Device Slot #(1-8) [1]? 3
Adding ESCON Channel device in slot 3 port 1 as interface #2
Use "net 2" to configure ESCON Channel parameters
2216B Config>li dev
Ifc 0 Token Ring Slot: 1 Port: 1
Ifc 1 ESCON Channel Slot: 2 Port: 1
Ifc 2 ESCON Channel Slot: 3 Port: 1
2216B Config>
Figure 283. Adding the Devices
9.2.5.2 Configure the Token-Ring
The token-ring has to be configured with a MAC Address which is used by the
LSA direct connection to communicate with the host (Figure 284 on page 282).
2216B Config>net 0
Token-Ring interface configuration
2216B TKR config>speed 16
2216B TKR config>media unshield
2216B TKR config>set phy 40:00:00:22:16:00:0a 1
2216B TKR config>li
Token-Ring configuration:
acket size (INFO field): 2052
Speed: 16 Mb/sec
Media: Unshielded
IF Aging Timer: 120
Source Routing: Enabled
MAC Address: 40002216000A
2216B TKR config>ex
2216B Config>
Figure 284. Configure the TR Adapter
1 Set the MAC address which will be used to identify the host when configure the
virtual LSA channel for direct connection. The link is done via the net command at
the ’ESCON/PCA Add Virtual> Prompt (see Figure 285).
9.2.5.3 Add/Configure the LSA Interfaces
Both ESCON adapters have to be configured for LSA direct connection. Both
LSA interfaces have the same TR adapter (net 0) as reference.
282 IBM 2216 and Network Utility Host Channel Connections

2216B Config>net 1 1
2216B ESCON Config>add lsa 2
2216B ESCON Add Virtual>net 0 3
2216B ESCON Add Virtual>sub add 4
2216B ESCON Add LSA Subchannel>dev 4
2216B ESCON Add LSA Subchannel>lpar 1 5
2216B ESCON Add LSA Subchannel>cu 1
2216B ESCON Add LSA Subchannel>link cc 6
2216B ESCON Add LSA Subchannel>ex
2216B ESCON Add Virtual>ex
2216B ESCON Config>li all 7
Net: 3 Protocol: LSA LAN type: Token Ring LAN number: 0
Maxdata: 2052
Loopback is not enabled.
MAC address: Obtained from net 0
Block Timer: 10 ms ACK length: 10 bytes
Sub 0 Dev addr: 4 LPAR: 1 Link addr: CC CU addr: 1
2216B ESCON Config>ex
ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]: y
Figure 285. Configure LSA on ESCON Adapter 1
1 Change to the first ESCON adapter to be configured.
2 Add an LSA interface to the adapter.
3 Link the LSA interface to the TR-LAN interface (Ifc 0). See Figure 283 on
page 282.
4 Add the subchannel to the LSA interface.
5 Define the logical partition number on the host (LPAR 1).
6 Define the link port of the ESCON Director the host is attached to.
7 Display the virtual channel interfaces on the ESCON adapter 1.
Backup Scenario 283

2216B Config>net 2 1
2216B ESCON Config>add lsa 2
2216B ESCON Add Virtual>net 0 3
2216B ESCON Add Virtual>sub add 4
2216B ESCON Add LSA Subchannel>dev 4
2216B ESCON Add LSA Subchannel>lpar 4 5
2216B ESCON Add LSA Subchannel>cu 1
2216B ESCON Add LSA Subchannel>link d0 6
2216B ESCON Add LSA Subchannel>ex
2216B ESCON Add Virtual>ex
2216B ESCON Config>li all 7
Net: 4 Protocol: LSA LAN type: Token Ring LAN number: 0
Maxdata: 2052
Loopback is not enabled.
MAC address: Obtained from net 0
Block Timer: 10 ms ACK length: 10 bytes
Sub 0 Dev addr: 4 LPAR: 4 Link addr: D0 CU addr: 1
2216B ESCON Config>ex
ESCON configuration has been changed.
Do you wish to keep the changes? [Yes]: y
2216B Config>write
Config Save: Using bank A and config number 1
216B Config>
2216B *reload y 8
Figure 286. Configure LSA on ESCON Adapter 2
1 Change to the second ESCON adapter to be configured.
2 Add an LSA interface to the adapter.
3 Link the LSA interface to the TR-LAN interface (Ifc 0). See Figure 283 on page
282.
4 Add the subchannel to the LSA interface.
5 Define the logical partition number on the host.
6 Define the link port of the ESCON director the host is attached to.
7 Display the virtual channel interfaces on the ESCON adapter 2.
8 Reload the 2216 to become the new active configuration.
After the second ESCON adapter has been configured and the new configuration
has become active, we have to configure the PCs, using the IBM Personal
Communication with the MAC Address for the host connection, which is for the
LSA direct connection here in our scenario. The MAC Address is set at the
token-ring interface (40002216000A) configuration (see Figure 284 on page 282).
In Figure 287 all the interfaces are listed and also the active virtual LSA interface
for the primary host connection is displayed.
284 IBM 2216 and Network Utility Host Channel Connections

2216B *t5
2216B +int 1
Self-Test Self-Test Maintenance
Net Net' Interface Slot-Port Passed Failed Failed
0 0 TKR/0 Slot: 1 Port: 1 1 0 0
1 1 ESCON/0 Slot: 2 Port: 1 1 0 0
2 2 ESCON/1 Slot: 3 Port: 1 1 0 0
3 1 LSA/0 Slot: 0 Port: 0 1 3 0
4 2 LSA/1 Slot: 0 Port: 0 0 5
2216B +
2216 +net 3 2
LSA Console
2216 LSA>li adap 3
LSA Virtual Adapter
LSA Information for Net 3
--- ----------- --- --- --
LAN Type: Token-Ring/802.5 LAN Number: 0
MAC Address: 40002216000A 4
Downstream network: Token-Ring/802.5 - Net 0
Status: Host connected
#SAPs Open: 1 #Link Stations Open: 1
Maximum frame size: 2052 (0x804)
Host User ID Subchannel
------------ ----------
00000000 0
1 host user(s)
2216 LSA>
Figure 287. Display the Active LSA Interface
1 List the configured interfaces.
2 Change to the virtual active LSA channel adapter.
3 Display the status of the virtual active LSA channel adapter.
4 The MAC Address of the LSA interface. Read from the 2216 LAN interface due
to the net link command at LSA configuration. See Figure 285 on page 283.
Backup Scenario 285

286 IBM 2216 and Network Utility Host Channel Connections

Appendix A. Special Notices
This publication is intended to help networking professionals understand the host
channel attachments and apply the corresponding scenarios to their customer
sites. The information in this publication is not intended as the specification of any
programming interfaces that are provided by IBM 2216 and Network Utility. See
the PUBLICATIONS section of the IBM Programming Announcement for IBM
2216 and Network Utility for more information about what publications are
considered to be product documentation.
References in this publication to IBM products, programs or services do not imply
that IBM intends to make these available in all countries in which IBM operates.
Any reference to an IBM product, program, or service is not intended to state or
imply that only IBM's product, program, or service may be used. Any functionally
equivalent program that does not infringe any of IBM's intellectual property rights
may be used instead of the IBM product, program or service.
Information in this book was developed in conjunction with use of the equipment
specified, and is limited in application to those specific hardware and software
products and levels.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to the IBM Director of
Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, NY 10594 USA.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact IBM Corporation, Dept.
600A, Mail Drop 1329, Somers, NY 10589 USA.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The information contained in this document has not been submitted to any formal
IBM test and is distributed AS IS. The information about non-IBM ("vendor")
products in this manual has been supplied by the vendor and IBM assumes no
responsibility for its accuracy or completeness. The use of this information or the
implementation of any of these techniques is a customer responsibility and
depends on the customer's ability to evaluate and integrate them into the
customer's operational environment. While each item may have been reviewed by
IBM for accuracy in a specific situation, there is no guarantee that the same or
similar results will be obtained elsewhere. Customers attempting to adapt these
techniques to their own environments do so at their own risk.
Any pointers in this publication to external Web sites are provided for
convenience only and do not in any manner serve as an endorsement of these
Web sites.
Any performance data contained in this document was determined in a controlled
environment, and therefore, the results that may be obtained in other operating
environments may vary significantly. Users of this document should verify the
applicable data for their specific environment.
© Copyright IBM Corp. 1998 287

Reference to PTF numbers that have not been released through the normal
distribution process does not imply general availability. The purpose of including
these reference numbers is to alert IBM customers to specific information relative
to the implementation of the PTF when it becomes available to each customer
according to the normal IBM PTF distribution process.
The following terms are trademarks of the International Business Machines
Corporation in the United States and/or other countries:
Advanced Peer-to-Peer Networking AIX
APPN AS/400
BookManager CICS
eNetwork Enterprise Systems Architecture/390
ES/3090 ES/9000
ESA/390 ESCON
IBM IMS
Multiprise MVS/ESA
MVS/XA Nways
OpenEdition OS/390
RISC System/6000 RS/6000
S/370 S/390
SP System/390
VM/ESA VSE/ESA
VTAM 400
The following terms are trademarks of other companies:
C-bus is a trademark of Corollary, Inc.
Java and HotJava are trademarks of Sun Microsystems, Incorporated.
Microsoft, Windows, Windows NT, and the Windows 95 logo are trademarks
or registered trademarks of Microsoft Corporation.
PC Direct is a trademark of Ziff Communications Company and is used
by IBM Corporation under license.
Pentium, MMX, ProShare, LANDesk, and ActionMedia are trademarks or
registered trademarks of Intel Corporation in the U.S. and other
countries.
UNIX is a registered trademark in the United States and other
countries licensed exclusively through X/Open Company Limited.
Other company, product, and service names may be trademarks or
service marks of others.
288 IBM 2216 and Network Utility Host Channel Connections

Appendix B. Related Publications
The publications listed in this section are considered particularly suitable for a
more detailed discussion of the topics covered in this redbook.
B.1 International Technical Support Organization Publications
B.2 Redbooks on CD-ROMs
B.3 Other Publications
For information on ordering these ITSO publications see “How to Get ITSO
Redbooks” on page 291.
• IBM Network Utility Description and Configuration Scenarios, SG24-5289
• Inside APPN and HPR - The Essential Guide to the New SNA, SG24-3669
• IBM Nways 2216 Multiaccess Connector Description and Configuration
Scenarios - Volume I, SG24-4957
• TCP/IP Tutorial and Technical Overview, GG24-3376
Redbooks are also available on the following CD-ROMs.
CD-ROM Title Subscription Collection Kit
Number Number
System/390 Redbooks Collection SBOF-7201 SK2T-2177
Networking and Systems Management Redbooks Collection SBOF-7370 SK2T-6022
Transaction Processing and Data Management Redbook SBOF-7240 SK2T-8038
Lotus Redbooks Collection SBOF-6899 SK2T-8039
Tivoli Redbooks Collection SBOF-6898 SK2T-8044
AS/400 Redbooks Collection SBOF-7270 SK2T-2849
RS/6000 Redbooks Collection (HTML, BkMgr) SBOF-7230 SK2T-8040
RS/6000 Redbooks Collection (PostScript) SBOF-7205 SK2T-8041
RS/6000 Redbooks Collection (PDF Format) SBOF-8700 SK2T-8043
Application Development Redbooks Collection SBOF-7290 SK2T-8037
These publications are also relevant as further information sources:
• Network Utility Installation, Getting Started, and User’s Guide, GA27-4167
• IBM 2216 Nways Multiaccess Connector and Network Utility Introduction and
Planning Guide, GA27-4105
• IBM 2216 Nways Multiaccess Connector and Network Utility Service and
Maintenance Manual, SY27-0350
• IBM 2216 Nways Multiaccess Connector Installation and Initial Configuration
Guide, GA27-4106
• Nways Multiprotocol Access Services Using and Configuring Features Version
3.2, SC30-3993
• Nways MAS Protocol Configuration and Monitoring Reference Vol.1 V2R2,
SC30-3884
© Copyright IBM Corp. 1998 289

• Nways Multiprotocol Access Services Protocol Configuration and Monitoring
Reference Vol. 2 Version 3.2, SC30-3885
• Nways Event Logging System Messages Guide, SC30-3682 (latest version
available at http://www.networking.ibm.com)
• Nways AIS/MAS/MRS/MSS/MSSC Configuration Program User's Guide for
Nways Multiprotocol and Access Services Products, GC30-3830
• VTAM Network Implementation Guide V4R4 for MVS/ESA, SC31-8370
• VTAM Resource Definition Reference V4R4 for MVS/ESA, SC31-8377
• Planning for Fiber Optic Channel Links, GA23-0367
• SNA APPN Architecture Reference, SC30-3422
• OS/390 eNetwork Communications Server SNA Resource Definition
Reference, SC31-8565
• OS/390 TCP/IP Update Guide, GC31-8553
• Nways Multiprotocol Access Services Software User's Guide Version 2,
Release 2, SC30-3886
• OS/390 eNetwork Communications Server High Speed Access Services
User’s Guide, GC31-8676
• VTAM Customization V4R4 for MVS/ESA, LY43-0075 (available to
IBM-licensed customers only)
• VTAM Resource Definition Reference V4R4 for MVS/ESA, SC31-8377
• VTAM Network Implementation Guide V4R4 for MVS/ESA, SC31-8370
• OS/390 UNIX System Services Planning, SC28-1890 (available in PDF format
on the Web at http://www.s390.ibm.com/products/oe/bpxa1pu5.html)
290 IBM 2216 and Network Utility Host Channel Connections

How to Get ITSO Redbooks
This section explains how both customers and IBM employees can find out about ITSO redbooks, redpieces, and
CD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided.
• Redbooks Web Site http://www.redbooks.ibm.com/
Search for, view, download or order hardcopy/CD-ROM redbooks from the redbooks web site. Also read
redpieces and download additional materials (code samples or diskette/CD-ROM images) from this redbooks site.
Redpieces are redbooks in progress; not all redbooks become redpieces and sometimes just a few chapters will
be published this way. The intent is to get the information out much quicker than the formal publishing process
allows.
• E-mail Orders
Send orders via e-mail including information from the redbooks fax order form to:
In United States
Outside North America
• Telephone Orders
United States (toll free)
Canada (toll free)
Outside North America
• Fax Orders
United States (toll free)
Canada
Outside North America
e-mail address
usib6fpl@ibmmail.com
Contact information is in the “How to Order” section at this site:
http://www.elink.ibmlink.ibm.com/pbl/pbl/
1-800-879-2755
1-800-IBM-4YOU
Country coordinator phone number is in the “How to Order” section at
this site:
http://www.elink.ibmlink.ibm.com/pbl/pbl/
This information was current at the time of publication, but is continually subject to change. The latest information for
customer may be found at http://www.redbooks.ibm.com/ and for IBM employees at http://w3.itso.ibm.com/.
IBM Intranet for Employees
1-800-445-9269
1-403-267-4455
Fax phone number is in the “How to Order” section at this site:
http://www.elink.ibmlink.ibm.com/pbl/pbl/
IBM employees may register for information on workshops, residencies, and redbooks by accessing the IBM
Intranet Web site at http://w3.itso.ibm.com/ and clicking the ITSO Mailing List button. Look in the Materials
repository for workshops, presentations, papers, and Web pages developed and written by the ITSO technical
professionals; click the Additional Materials button. Employees may also view redbook. residency, and workshop
announcements at http://inews.ibm.com/.
© Copyright IBM Corp. 1998 291

IBM Redbook Fax Order Form
Please send me the following:
Title Order Number Quantity
First name Last name
Company
Address
City Postal code
Telephone number Telefax number VAT number
Invoice to customer number
Credit card number
We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card not
available in all countries. Signature mandatory for credit card payment.
292 IBM 2216 and Network Utility Host Channel Connections
Country
Credit card expiration date Card issued to
Signature

Index
Numerics
3172 3
3174 5
3745/3746 4
A
APPN 36, 184
APPN Monitoring 198
APPN Package addition 114
B
Backup
2216 Configuration 281
Channel Failure 279
Host definition 280
Host Failure 279
LSA Direct 278
Backup Scenario 259
BAN 94
C
channel path 1
CHPID 28
CNTLUNIT 29
Control Unit 9
D
Define the Physical Interfaces 114
DEVICE 41
Direct Routes 43
DLUR 219
DLUS 219
E
EMIF 13
ESCON 2, 7
2216 Channel Protocols 16
Control Unit 9
Director 9
EMIF 13
ESCD 21
Host Attachment 12
I/O Interface 2
Link 8
LPAR 13
PCA Comparison 255
examples 27
G
GATEWAY 43
H
HOME 42
Host IP Definitions 41
host TCP/IP
DEVICE 41
GATEWAY 43
HOME 42
START 44
HPDT UDP
Host Definitions 45
oenetstat 48
oeping 48
oeroute 47
I
I/O interface 2
Indirect Routes 43
IOCP 27
IODEVICE 29
L
LAN Channel Station 131
LCS 16, 27, 131, 132
2216 Support 131
3172 Emulation 135
Bridging 133
Configuration Examples 139
Host Parameter Relationships 136
Host TCP/IP Definitions 44
Link 8
Link Services Architecture 49
LPAR 13
LSA 16, 27, 49
2216 Monitoring 83
2216 Support 49
APPN Connection 52
APPN Support Example 112
Direct Connection 49, 62
DLSw Connection 50
Host Parameter Relationships 55
LLC Loopback 54
Local DLSw 87
Local DLSw Connection SDLC 99
loopback 52, 53
Monitoring ESCON LSA 67
Remote DLSw 69
SNA Support Examples 59
Subchannel 65
Virtual interface 71, 115
M
MAE 5
MPC+ 16, 27, 169
APPN 178, 198
Host Parameter Relationships 170
HPDT UDP 205
© Copyright IBM Corp. 1998 293

IOCP 173
IP ’Monitoring’ 200
Monitoring ESCON 194
Subchannel 183
TCP/IP 190
TCP/IP Definitions 175
UDP 201
Virtual Interface 181
VTAM Definitions 173, 204
Multipath Channel+ 169
O
oeifconfig 46
OSA 3
P
PART 28
PART=((name1,x) 28
Physical Interfaces 180
R
RESOURCE Statement 28
S
SDLC 99
START 44
T
TN3270
APPN Loopback 231
DLUR 249
Host Definitions 242
Host Parameters Relationship 219
IOCP Definitions 227
LSA-APPN/DLUR 222
LSA-SNA 220
Monitoring 238, 251
MPC+ and APPN/DLUR 224
Subarea under APPN 234
TN3270E Server configuration 236, 241
VTAM Definitions 228, 243
VTAM TN3270 Resources 244
TN3270 Server 219
Transport Resource List 243
TRL 243
V
VM/ESA 31
VM/SP 31
VM/XA 31
VSE/ESA 32
VTAM Definitions 33
X
XCA Major Node 33
294 IBM 2216 and Network Utility Host Channel Connections

ITSO Redbook Evaluation
IBM 2216 and Network Utility Host Channel Connections
SG24-5303-00
Your feedback is very important to help us maintain the quality of ITSO redbooks. Please complete this
questionnaire and return it using one of the following methods:
• Use the on-line evaluation form found at http://www.redbooks.ibm.com
• Fax this form to: USA International Access Code + 1 914 432 8264
• Send your comments in an Internet note to redbook@us.ibm.com
Which of the following best describes you?
_ Customer _ Business Partner _ Solution Developer _ IBM employee
_ None of the above
Please rate your overall satisfaction with this book using the scale:
(1 = very good, 2 = good, 3 = average, 4 = poor, 5 = very poor)
Overall Satisfaction __________
Please answer the following questions:
Was this redbook published in time for your needs? Yes___ No___
If no, please explain:
What other redbooks would you like to see published?
Comments/Suggestions: (THANK YOU FOR YOUR FEEDBACK!)
© Copyright IBM Corp. 1998 295

SG24-5303-00
Printed in the U.S.A.
IBM 2216 and Network Utility Host Channel Connections SG24-5303-00