3Com 3C63311 Reference Guide - Page 234

Ethernet Interface, DLCI 1022 or 16-991 for one FR DLCI to one ATM VPI/VCI. The FR-SSCS

Page 234 highlights

222 APPENDIX B: PATHBUILDER S330/S310 MODULE AND APPLICATION OVERVIEW Ethernet Interface n The PathBuilder S330/S310 performs all the required translation and management functions between these two networks, implementing the stacks as indicated in Figure 162 and performing the following key functions: n Translating from Q.922 Frame to FR-SSCS/ATM AAL5 PDU and from FR-SSCS/ATM AAL5 PDU to Q.922 Frame n Supporting 2-octet-not 3-octet or 4-octet-FR header (10-bit DLCI) n Allowing you to configure DLCI to VPI/VCI mapping n Providing one-to-one mapping: maps one FR-SSCS DLCI (default FR-SSCS DLCI (1022) or 16-991) for one FR DLCI to one ATM VPI/VCI. (The FR-SSCS DLCI(s) for the two end systems should be configured to be the same.) n Managing traffic n Handling congestion The PathBuilder S330/S310 Ethernet LAN modules provide multiple connections to Ethernet segments over ATM WAN. When the Ethernet interface receives data from the LAN, any packets appearing on the 10BASE-T ports are checked for packet integrity and stored in the shared memory area. The system then performs a bridge operation to determine if the packet will be sent on to any other interface. See "Bridge Operation" below, for details. n If the packet is to go on the HDLC port, it is bridged directly after being encapsulated properly for Frame Relay. n If the packet is to go on an ATM interface, the bridge determines the VCI connection for the packet destination. The packet is then encapsulated according to RFC 1483, and the descriptor is handed off to the SAR, together with the associated ATM header descriptor. The SAR appends the AAL5 convergence sublayer to the packets and queues them according to the shaper you specify for that connection. The packet is then segmented according to the rate of the traffic descriptor, and the cells are sent to the CTX where ATM switching and queueing is performed. The SAR contains 15 traffic shapers, each of which can be programmed for sustained cell rate of transmission (SCR), peak cell rate (PCR), and maximum burst size (MBS). The traffic shapers work as follows: n The packet is segmented using a dual leaky buffer algorithm, whereby the cells are transmitted from each connection in the shaper at an average rate until the bucket of token fills up (a token is given to the connection at an average rate if it has no cells to transmit at that moment). n The shaper then turns the burst mode on and transmits at the peak rate for a burst length. Note that the shaper serves every connection independently. n Cells received from the ATM WAN are switched via the CTX chip to the SAR queues. You can enable shaping on the SAR queues to slow down the incoming traffic on the SAR.

  • 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

222
A
PPENDIX
B: P
ATH
B
UILDER
S330/S310 M
ODULE
AND
A
PPLICATION
O
VERVIEW
n
The PathBuilder S330/S310 performs all the required translation and
management functions between these two networks, implementing the stacks
as indicated in Figure 162 and performing the following key functions:
n
Translating from Q.922 Frame to FR-SSCS/ATM AAL5 PDU and from
FR-SSCS/ATM AAL5 PDU to Q.922 Frame
n
Supporting 2-octet—not 3-octet or 4-octet—FR header (10-bit DLCI)
n
Allowing you to configure DLCI to VPI/VCI mapping
n
Providing one-to-one mapping: maps one FR-SSCS DLCI (default FR-SSCS
DLCI (1022) or 16-991) for one FR DLCI to one ATM VPI/VCI. (The FR-SSCS
DLCI(s) for the two end systems should be configured to be the same.)
n
Managing traffic
n
Handling congestion
Ethernet Interface
The PathBuilder S330/S310 Ethernet LAN modules provide multiple connections to
Ethernet segments over ATM WAN.
When the Ethernet interface receives data from the LAN, any packets appearing
on the 10BASE-T ports are checked for packet integrity and stored in the shared
memory area. The system then performs a bridge operation to determine if the
packet will be sent on to any other interface. See “Bridge Operation” below, for
details.
n
If the packet is to go on the HDLC port, it is bridged directly after being
encapsulated properly for Frame Relay.
n
If the packet is to go on an ATM interface, the bridge determines the VCI
connection for the packet destination. The packet is then encapsulated
according to RFC 1483, and the descriptor is handed off to the SAR, together
with the associated ATM header descriptor. The SAR appends the AAL5
convergence sublayer to the packets and queues them according to the shaper
you specify for that connection. The packet is then segmented according to the
rate of the traffic descriptor, and the cells are sent to the CTX where ATM
switching and queueing is performed.
The SAR contains 15 traffic shapers, each of which can be programmed for
sustained cell rate of transmission (SCR), peak cell rate (PCR), and maximum burst
size (MBS).
The traffic shapers work as follows:
n
The packet is segmented using a dual leaky buffer algorithm, whereby the cells
are transmitted from each connection in the shaper at an average rate until the
bucket of token fills up (a token is given to the connection at an average rate if
it has no cells to transmit at that moment).
n
The shaper then turns the burst mode on and transmits at the peak rate for a
burst length. Note that the shaper serves every connection independently.
n
Cells received from the ATM WAN are switched via the CTX chip to the SAR
queues. You can enable shaping on the SAR queues to slow down the
incoming traffic on the SAR.