Cisco WS C4224V 8FXS Software Guide - Page 262

Scenarios for SNA-to-IP Integration, Line Consolidation, FEP Replacement

Page 262 highlights

IBM SNA Chapter 12 Configuring Other Routing Protocols Scenarios for SNA-to-IP Integration There are common elements or scenarios for integrating TCP/IP with SNA networks. This section describes three elements or scenarios, the corresponding phase from the Cisco four-phase integration model, and the Cisco products and software features deployed in these scenarios. This section discusses the following scenarios: • Line Consolidation, page 12-10 • FEP Replacement, page 12-10 • Desktop Consolidation, page 12-11 Line Consolidation Line consolidation involves simplifying the network by providing a single network infrastructure, based on TCP/IP. This structure accommodates SNA and other traffic and allows the elimination of multiple single-protocol lines to each location. Phase two of SNA-to-IP integration dictates the building of a single network backbone based upon TCP/IP. This setup often allows organizations to consolidate the number of communication lines in the network which simplifies the support and maintenance. The primary product in a line consolidation project is a multiprotocol router that encapsulates and converts the traffic from the SNA lines. RSRB and DLSw+ are the Cisco IOS technologies used for this conversion. In addition, Cisco routers also support the tunneling of both bisynchronous and certain asynchronous protocols with Cisco IOS features such as STUN and BSTUN and the Airline Product Set (ALPS). FEP Replacement FEP replacement involves replacing FEPs (and possibly other special-purpose mainframe channel-attached equipment) with new channel-attached routers that offer high throughput, low costs, and flexible software functionality. Throughout all phases of the SNA-to-IP integration, high-capacity throughput to the mainframe is a key requirement. Organizations are replacing FEPs with routers with direct channel attachments. 12-10 Catalyst 4224 Access Gateway Switch Software Configuration Guide OL-2031-02

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310

Chapter 12
Configuring Other Routing Protocols
IBM SNA
12-10
Catalyst 4224 Access Gateway Switch Software Configuration Guide
OL-2031-02
Scenarios for SNA-to-IP Integration
There are common elements or scenarios for integrating TCP/IP with SNA
networks. This section describes three elements or scenarios, the corresponding
phase from the Cisco four-phase integration model, and the Cisco products and
software features deployed in these scenarios. This section discusses the
following scenarios:
Line Consolidation, page 12-10
FEP Replacement, page 12-10
Desktop Consolidation, page 12-11
Line Consolidation
Line consolidation involves simplifying the network by providing a single
network infrastructure, based on TCP/IP. This structure accommodates SNA and
other traffic and allows the elimination of multiple single-protocol lines to each
location.
Phase two of SNA-to-IP integration dictates the building of a single network
backbone based upon TCP/IP. This setup often allows organizations to
consolidate the number of communication lines in the network which simplifies
the support and maintenance.
The primary product in a line consolidation project is a multiprotocol router that
encapsulates and converts the traffic from the SNA lines. RSRB and DLSw+ are
the Cisco IOS technologies used for this conversion. In addition, Cisco routers
also support the tunneling of both bisynchronous and certain asynchronous
protocols with Cisco IOS features such as STUN and BSTUN and the Airline
Product Set (ALPS).
FEP Replacement
FEP replacement involves replacing FEPs (and possibly other special-purpose
mainframe channel-attached equipment) with new channel-attached routers that
offer high throughput, low costs, and flexible software functionality.
Throughout all phases of the SNA-to-IP integration, high-capacity throughput to
the mainframe is a key requirement. Organizations are replacing FEPs with
routers with direct channel attachments.