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

IOP Public Rail Bindings, Virtual Adapters

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

Ch 4: Networking Explaineds IOP Public Rail Bindings Each pair of network cards on the IOP will have the same bindings. Each physical network card will NOT be bound to a traditional protocol. Instead, each network card will only have the Marathon Datagram Service and the Marathon Ethernet Provider as its only enabled bindings. Along with the traditional protocol, the MtcEtx protocol will be disabled. Public Rail Configuration (CE) The bindings on the CE will be a little different than the IOPs. First, consider that the bindings have significance in that they represent a "connection" to the bindings on the network cards in the IOP. Remember, there are not any physical network cads in the CE, and the CE is represented by two NetServers, but only one copy of Windows NT. Virtual Adapters On the CE, there are two types of adapters present in the networking properties. Since there are not any physical cards in the system, these adapter types are virtual. The first virtual adapter is the MtcVnR. This represents the virtual adapter that communicates with a virtual adapter on IOP1. There are two IOPs, so there needs to be two instances of the MtcVnR, and only two. Network Server Division 4-9

  • 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-9
IOP Public Rail Bindings
Each pair of network cards on the IOP will have the same bindings.
Each physical network card will NOT be bound to a traditional
protocol.
Instead, each network card will only have the Marathon
Datagram Service and the Marathon Ethernet Provider as its only
enabled bindings.
Along with the traditional protocol, the MtcEtx
protocol will be disabled.
Public Rail Configuration (CE)
The bindings on the CE will be a little different than the IOPs.
First,
consider that the bindings have significance in that they represent a
“connection” to the bindings on the network cards in the IOP.
Remember, there are not any physical network cads in the CE, and
the CE is represented by two NetServers, but only one copy of
Windows NT.
Virtual Adapters
On the CE, there are two types of adapters present in the networking
properties.
Since there are not any physical cards in the system,
these adapter types are virtual.
The first virtual adapter is the
MtcVnR.
This represents the virtual adapter that communicates with
a virtual adapter on IOP1.
There are two IOPs, so there needs to be
two instances of the MtcVnR, and only two.