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

CE Bindings

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 76 highlights

HP NetServer AA CE Bindings The adapter that works in conjunction with the public rail is the MTCETHR Virtual adapter. This adapter is an Ethernet Redirector and is "matched up" with the pair of adapters in the IOP, which are bound to Ethernet Providers. To logically follow the path, the IOP, being the system with a NIC directly on the LAN "provides" network capabilities. The CE accesses this capability by "redirecting" networking requests to the IOP. Still, there is no direct communication from the CE to the IOP. The CE (ETHR) redirects the request to the MIC, then through the SSDL, to the other MICs that go to ETHP, and finally to the NIC in the IOPs. There will be one MTCETHR virtual adapter for each public rail. The list of the virtual adapters listed by Windows NT must match the same order as the public rails on the IOP from top-to-bottom. They do not have to occupy the same numerical position. For the purposes of protocol settings, remember the first MTCETHR on the list in the CE corresponds to the first public rail provider on each IOP. The second instance of the MTCETHR on the CE corresponds with the second rail on the IOP, and so on. Each MTCETHR needs to have bound to it a traditional protocol that logically makes sense when considering where its associated pair of NICs in the IOP are cabled. If one pair of NICs is cabled to LAN segment A via a switch, and another pair of NICs is cabled to LAN 4-10 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-10
The adapter that works in conjunction with the public rail is the
MTCETHR Virtual adapter.
This adapter is an Ethernet Redirector
and is “matched up” with the pair of adapters in the IOP, which are
bound to Ethernet Providers.
To logically follow the path, the IOP,
being the system with a NIC directly on the LAN “provides”
network capabilities.
The CE accesses this capability by
“redirecting” networking requests to the IOP.
Still, there is no direct
communication from the CE to the IOP.
The CE (ETHR) redirects
the request to the MIC, then through the SSDL, to the other MICs
that go to ETHP, and finally to the NIC in the IOPs.
CE Bindings
There will be one MTCETHR virtual adapter for each public rail.
The list of the virtual adapters listed by Windows NT must match the
same order as the public rails on the IOP from top-to-bottom.
They
do not have to occupy the same numerical position.
For the purposes
of protocol settings, remember the first MTCETHR on the list in the
CE corresponds to the first public rail provider on each IOP. The
second instance of the MTCETHR on the CE corresponds with the
second rail on the IOP, and so on.
Each MTCETHR needs to have bound to it a traditional protocol that
logically makes sense when considering where its associated pair of
NICs in the IOP are cabled.
If one pair of NICs is cabled to LAN
segment A via a switch, and another pair of NICs is cabled to LAN