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

Knowing which MTCETHR

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

Ch 4: Networking Explaineds • The IOPs have the actual HP 10/100 TX driver installed and it is listed in the network properties in Winodws NT on the IOP even if the network cards are being redirected. Through the protocol "Marathon Ethernet Provider" it establishes a relationship with a MTCETHR virtual adapter on the CE. • The CEs only have virtual adapters, one MTCETHR virtual adapter exists for each public rail. Knowing which MTCETHR adapter network protocols to modify is very important. For example, if there are two public rails, one for subnet A and one for subnet B, then there will be two MTCETHR virtual adapters appearing in the network properties in Windows NT on the CE. Which one of the MTCETHRs is for subnet B? • The AA 4000 software does not know which network public rail is cabled to subnet A and which one is cabled to subnet B, and so on. It is up to the administrator to sort out. • To match the physical cabling of the NICs representing the public rail going to a subnet, to the actual protocol settings on the CEs MTCETHR virtual adapter, look at the list of network adapters in the Windows NT network properties on both the CE and the IOP. • Each Network adapter will have a number next to it, for example [3]. Match the lowest adapter number for the HP 10/100 TX driver on the IOP, NOT counting the IOP Private Link, to the lowest number of the MTCETHR virtual adapter on the CE. Be aware that the numbers will not match most of the time; [1] HPTX on the IOP may match with [3] MTCETH on the CE if those are the two lowest numbers. The MTCETHR network protocols and settings will be carried out by its matching public rail. Network Server Division 4-15

  • 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
Ch 4: Networking Explaineds
Network Server Division
4-15
•
The IOPs have the actual HP 10/100 TX driver installed and it is
listed in the network properties in Winodws NT on the IOP even
if the network cards are being redirected.
Through the protocol
“Marathon Ethernet Provider” it establishes a relationship with a
MTCETHR virtual adapter on the CE.
•
The CEs only have virtual adapters, one MTCETHR virtual
adapter exists for each public rail.
Knowing which MTCETHR
adapter network protocols to modify is very important.
For
example, if there are two public rails, one for subnet A and one
for subnet B, then there will be two MTCETHR virtual adapters
appearing in the network properties in Windows NT on the CE.
Which one of the MTCETHRs is for subnet B?
•
The AA 4000 software does not know which network public
rail is cabled to subnet A and which one is cabled to subnet
B, and so on.
It is up to the administrator to sort out.
•
To match the physical cabling of the NICs representing the
public rail going to a subnet, to the actual protocol settings
on the CEs MTCETHR virtual adapter, look at the list of
network adapters in the Windows NT network properties on
both the CE and the IOP.
•
Each Network adapter will have a number next to it, for
example [3].
Match the lowest adapter number for the HP
10/100 TX driver on the IOP, NOT counting the IOP Private
Link, to the lowest number of the MTCETHR virtual adapter
on the CE.
Be aware that the numbers will not match most
of the time; [1] HPTX on the IOP may match with [3]
MTCETH on the CE if those are the two lowest numbers.
The MTCETHR network protocols and settings will be
carried out by its matching public rail.