Cisco 3825 Software Configuration Guide - Page 255

umts-iub backhaul-timer

Page 255 highlights

Appendix A Cisco 3825 Mobile Wireless Edge Router RAN-O Command Reference umts-iub backhaul-timer umts-iub backhaul-timer To determine how often backhaul packets are sent for UMTS, use the umts-iub backhaul-timer Interface configuration command. This option is commonly used for High Speed Downlink Data Packet Access (HSDPA) offload environments. HSDPA traffic requires much more bandwidth than voice/signaling traffic on UMTS. Customers can offload the HSDPA traffic to an alternate backhaul media, such as metro-Ethernet while still maintaining low latency traffic (voice/signaling) on the existing T1/E1s. By configuring a separate UMTS peer for the HSPDA interface(s) and a timer value in the 3 ms to 8 ms range, customers can reduce CPU utilization on the Cisco 3825 router and save backhaul costs by sending HSDPA across the lower cost metro-Ethernet. Note The value should be carefully selected. Typically, it should not exceed 2 ms when the backhaul is T1/E1 MLPPP. However for alternate backhaul Frame Forwarding (FF) or Gigabit Ethernet (GE), this value can be selected at a greater value to reduce the CPU load on the platform. Depending on the load the UMTS interface and timer selected, the UMTS payload could exceed the Maximum Transmission Unit (MTU). In this case, the backhaul packets will be sent when they reach the backhaul MTU (for non-MLPPP backhauls). A maximum MTU of 450 bytes is used for MLPPP backhauls. umts-iub backhaul-timer ? [1-8] timer value(in ms) Syntax Description This command has no arguments or keywords. Defaults Timer value of 1 ms. Command Modes Interface configuration Command History Release 12.4(4)MR Modification This command was introduced. Examples The following example shows how to determine how often the backhaul packets are sent for UMTS: Router(config)# interface a0/3/0 Router(config-if) umts-iub backhaul-timer ? timer value(in msec) Router(config-if)# OL-15667-03 Cisco 3825 Mobile Wireless Edge Router Software Configuration Guide A-123

  • 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
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358

A-123
Cisco 3825 Mobile Wireless Edge Router Software Configuration Guide
OL-15667-03
Appendix A
Cisco 3825 Mobile Wireless Edge Router RAN-O Command Reference
umts-iub backhaul-timer
umts-iub backhaul-timer
To determine how often backhaul packets are sent for UMTS, use the
umts-iub backhaul-timer
Interface configuration command. This option is commonly used for High Speed Downlink Data Packet
Access (HSDPA) offload environments. HSDPA traffic requires much more bandwidth than
voice/signaling traffic on UMTS. Customers can offload the HSDPA traffic to an alternate backhaul
media, such as metro-Ethernet while still maintaining low latency traffic (voice/signaling) on the
existing T1/E1s. By configuring a separate UMTS peer for the HSPDA interface(s) and a timer value in
the 3 ms to 8 ms range, customers can reduce CPU utilization on the Cisco 3825 router and save backhaul
costs by sending HSDPA across the lower cost metro-Ethernet.
Note
The value should be carefully selected. Typically, it should not exceed 2 ms when the backhaul is T1/E1
MLPPP. However for alternate backhaul Frame Forwarding (FF) or Gigabit Ethernet (GE), this value can
be selected at a greater value to reduce the CPU load on the platform. Depending on the load the UMTS
interface and timer selected, the UMTS payload could exceed the Maximum Transmission Unit (MTU).
In this case, the backhaul packets will be sent when they reach the backhaul MTU (for non-MLPPP
backhauls). A maximum MTU of 450 bytes is used for MLPPP backhauls.
umts-iub backhaul-timer ? [
1-8
]
timer value(in ms)
Syntax Description
This command has no arguments or keywords.
Defaults
Timer value of 1 ms.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to determine how often the backhaul packets are sent for UMTS:
Router(config)#
interface a0/3/0
Router(config-if)
umts-iub backhaul-timer ?
<1-8> timer value(in msec)
Router(config-if)#
Release
Modification
12.4(4)MR
This command was introduced.