Administration HiPath 3000/5000 V7 IP systems

More documents

Recommendations

Info

3000sb4.fm HiPath 3000/5000 in the LAN Network For internal use only HG 1500 V3.0 4.5.20.1 Multi-Gateway Administration (MGA) The configuration of a large number of gateways, in particular, can cost administrators considerable time and effort, and so can – even only minor – modifications to a configuration. HG 1500 V3.0 therefore supports the distribution of configurations from a master gateway to any number of slave gateways. Prerequisites In order to use Multi-Gateway Administration (MGA), no special hardware or software prerequisites are required on the gateways involved. However, the following conditions for configuration must be met: ● All slave gateways must be able to be accessed by the master gateway via IP. ● The port used for WBM must have the same number on each gateway (usually 8085) and must be accessible from the master gateway. Therefore, access must not be blocked by a firewall, for example. ● All slave gateways must have a user access for MGA. All accesses must have the same name and password. This access must have root access privileges. ● The slave gateways must be entered on the master gateway. (The list of slave gateways can also be imported by another master gateway, if necessary) Using MGA The administrator first configures the master gateway as required. He then uses a command to transfer this configuration data to slave gateways. The administrator can specify individually to which slave gateways the data will be transferred and also select which configuration tables will be transferred. 4.5.21 Quality of Service in HG 1500 Quality of Service encompasses various methods for guaranteeing certain transmission properties in packet-oriented networks (IP). It is thus important, for example, to ensure a minimum bandwidth for Voice over IP for the entire duration of the transfer operation. If multiple applications with equal rights are operating via IP, then the available bandwidth for the transmission path (for example an ISDN B channel, 64 Kbps) is split. In this case, a voice connection may experience packet losses which can reduce voice quality. P31003-H3570-Y100-4-7618, 2007-10-31 4-58 HiPath 3000/5000 V7, System Description
3000sb4.fm For internal use only HiPath 3000/5000 in the LAN Network HG 1500 V3.0 HG 1500 V3.0 uses various different procedures to implement Quality of Service. On layer 2 (in accordance with OSI, Ethernet), you can activate an extension (IEEE 802.1p) to the standard Ethernet format (DIX V2). This adds more information to the Ethernet header including a 3-bit data field. This field carries priority information on the data packet. For all packets that reach the board from the LAN, both Ethernet formats (IEEE 802.1p and DIX V2) are understood; for all packets that are sent from the board to the LAN, the format can be selected via "Basic Settings > IEEE 802.1p". You should check whether all components in the network support this format before this parameter is activated. Otherwise, it may not be possible to access HG 1500 V3.0 from the LAN anymore. The Ethernet header is not transported when switching to another transport medium (for example ISDN). An IP router (like the HG 1500 V3.0’s router) can, however, use the information contained in the IP header for prioritization. Straightforward IP routers that connect two network segments, for example, can use the IP level prioritization. In the "Type of Service" field, either three bit (IP precedence based on RFC 791, older standard) or six bit (Differentiated Services or DiffServ, based on RFC 2474) are evaluated for the creation of various classes. HG 1500 V3.0’s IP router provides various bandwidths for these classes, so that voice packets can be processed first. The procedure adopted by HG 1500 V3.0 can be set under "Basic settings > QoS procedures" (Autodetect is set by default). For the DiffServ parameter, various so-called codepoints ("Basic Settings > AF/EF Codepoints") are defined, and based on these codepoints two different procedures are used for processing the payload of different marked data flows: The "Expedited Forwarded (EF)" procedure (based on RFC 2598) guarantees a constant bandwidth for data in this class. If this defined value is reached, all packets that exceed this bandwidth are rejected. A separate class is defined for EF on HG 1500 V3.0. For this class, the bandwidth can be defined as a percentage for every ISDN peer (QoS bandwidth for EF). The "Assured Forwarding (AF)" procedure (based on RFC 2597) guarantees a minimum bandwidth for the data of one (of many) classes. Lower priority classes share the bandwidth not used by EF or the classes with higher priority. In addition, the speed at which packets are rejected if the system is unable to forward them fast enough can be defined for every class by means of the Dropping Level setting. Nothing is thus to be gained by buffering voice packages for an extended period of time (this only increases the delay). In the case of secure data transfer (for example file transfer), on the other hand, a large buffer is advantageous as packets are otherwise sent repeatedly between the two terminals. Four classes are reserved for AF on the HG 1500 V3.0: AF1x (high priority), AF2x, AF3x and AF4x (low priority), where "x" stands for one of three dropping levels: low (1), medium (2) and high (3). In the case of "low", packets are buffered over an extended period, in the case of "high", packets are promptly rejected if they cannot be forwarded. Unmarked IP packets (ToS field=00) are handled in the same way as the lowest priority. P31003-H3570-Y100-4-7618, 2007-10-31 HiPath 3000/5000 V7, System Description 4-59
Page 1 and 2:
Administration HiPath 3000/5000 V7
Page 3 and 4:
3000sbTOC.fm For internal use only
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
3000sb1.fm For internal use only In
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
3000sb2.fm For internal use only Hi
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180: 3000sb4.fm For internal use only Hi
Page 229: 3000sb4.fm For internal use only Hi
Page 273 and 274: 3000sb5.fm For internal use only Se
Page 281 and 282:
3000sb5.fm For internal use only Se
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
3000sb6.fm For internal use only Mi
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
3000sb55.fm For internal use only A
Page 331 and 332:
3000sb7.fm For internal use only Wo
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Page 433 and 434:
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
3000sb8.fm For internal use only Ap
Page 451 and 452:
Page 453 and 454:
Page 455 and 456:
Page 457 and 458:
Page 459 and 460:
Page 461 and 462:
Page 463 and 464:
Page 465 and 466:
Page 467 and 468:
Page 469 and 470:
Page 471 and 472:
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Page 479 and 480:
Page 481 and 482:
3000sb9.fm For internal use only Ca
Page 483 and 484:
Page 485 and 486:
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
Page 495 and 496:
Page 497 and 498:
Page 499 and 500:
3000sb10.fm For internal use only O
Page 501 and 502:
3000sb11.fm For internal use only I
Page 503 and 504:
Page 505 and 506:
Page 507 and 508:
Page 509 and 510:
Page 511 and 512:
Page 513 and 514:
Page 515 and 516:
Page 517 and 518:
Page 519 and 520:
3000sbIX.fm For internal use only I
Page 521 and 522:
Page 523 and 524:
Page 525 and 526:
show all

Administration HiPath 3000/5000 V7 IP systems

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?