HP NetServer AA 4000 HP AA HP Netserver 4000 Reference Guide - Page 72

Marathon Datagram Service.

Get HP NetServer AA 4000 PDF manuals and user guides View all HP NetServer AA 4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 72 highlights

HP NetServer AA Before any Marathon software implementation is performed, two pieces of data need to be collected: (1) the MAC addresses of the network cards to be used, and (2) the verification of the PCI slot use. Armed with the above information, the protocols and services can be set up on known, good equipment. The bindings to be deployed as part of the Network card configuration are a traditional networking protocol of choice (NetBEUI, TCP/IP), the MtcEtx Driver, and the Marathon Datagram Service. These bindings go on the card chosen as the private IOP link as represented by the correct bus and slot number according to Windows NT. There is only one network card in each IOP with these bindings, the cards do not support Adapter Fault Tolerance, and they are NOT "redirected" devices to be configured in the Marathon Configuration Utility. 4-6 Hewlett-Packard Company

  • 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
HP NetServer AA
Hewlett-Packard Company
4-6
Before any Marathon software implementation is performed, two
pieces of data need to be collected: (1) the MAC addresses of the
network cards to be used, and (2) the verification of the PCI slot use.
Armed with the above information, the protocols and services can be
set up on known, good equipment.
The bindings to be deployed as
part of the Network card configuration are a traditional networking
protocol of choice (NetBEUI, TCP/IP), the MtcEtx Driver, and the
Marathon Datagram Service.
These bindings go on the card chosen
as the private IOP link as represented by the correct bus and slot
number according to Windows NT.
There is only one network card in each IOP with these bindings, the
cards do not support Adapter Fault Tolerance, and they are NOT
“redirected” devices to be configured in the Marathon Configuration
Utility.