HP NetServer AA 6200 HP AA HP Netserver 4000 Reference Guide - Page 80

Adding a Public Rail, Working with a fully con d system

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

Page 80 highlights

HP NetServer AA Adding a Public Rail After the HPAA system is operational, it may be decided that another public rail is needed for whatever reason. It could be to offload traffic from one public rail and have more aggregate bandwidth, or it could be to service clients from a specific LAN segment. There are two choices of methods to add a public rail. One choice places the emphasis on uptime and will only have one single system reboot. At least one reboot is unavoidable due to Windows NT's requirements when adding network properties. The systems can be prepared one at a time offline while the other systems remain online until it is time to do one quick reboot. This method provides the most availability, but it also involves what could be very lengthy disk re-mirror operations. The other choice is to schedule downtime and bring down the entire system for the purposes of adding network cards and properties at once. This avoids the lengthy re-mirroring process, but also means the downtime could be upwards of one hour. CAUTION Do not mix versions of vendor LAN drivers for the NICs in the IOP. The results may be unpredictable. Working with a fully configured system As mentioned earlier, a new system should arrive with all of the networking preconfigured. In most environments, all that is left to do is add the necessary networking protocols and settings that go with the networking environment the HPAA system is installed. Changing the networking properties is simple, unfortunately, so is changing the wrong network properties. The most important consideration to be made when working with a preconfigured system is knowing what network properties to change. The following guidelines will help in ensuring that the correct network properties are changed and the HPAA system stays operational. • Using Windows NT on the HPAA system is no different than a single server implementation. If the network properties are changed to the point that a "re-binding" occurs, Windows NT must be rebooted for the changes to take effect. • Server reboots of the CE operating system results in the HPAA system being unavailable; plan accordingly. • When trying to place the HPAA system on the network for clients to access, it is the CE network properties that must be changed, not the IOPs. 4-14 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-14
Adding a Public Rail
After the HPAA system is operational, it may be decided that
another public rail is needed for whatever reason.
It could be to
offload traffic from one public rail and have more aggregate
bandwidth, or it could be to service clients from a specific LAN
segment.
There are two choices of methods to add a public rail.
One choice
places the emphasis on uptime and will only have one single system
reboot.
At least one reboot is unavoidable due to Windows NT’s
requirements when adding network properties.
The systems can be
prepared one at a time offline while the other systems remain online
until it is time to do one quick reboot.
This method provides the
most availability, but it also involves what could be very lengthy
disk re-mirror operations.
The other choice is to schedule downtime and bring down the entire
system for the purposes of adding network cards and properties at
once. This avoids the lengthy re-mirroring process, but also means
the downtime could be upwards of one hour.
CAUTION
Do not mix versions of vendor LAN drivers for the NICs in
the IOP.
The results may be unpredictable.
Working with a fully configured system
As mentioned earlier, a new system should arrive with all of the
networking preconfigured.
In most environments, all that is left to
do is add the necessary networking protocols and settings that go
with the networking environment the HPAA system is installed.
Changing the networking properties is simple, unfortunately, so is
changing the wrong network properties.
The most important
consideration to be made when working with a preconfigured system
is knowing what network properties to change.
The following
guidelines will help in ensuring that the correct network properties
are changed and the HPAA system stays operational.
•
Using Windows NT on the HPAA system is no different than a
single server implementation.
If the network properties are
changed to the point that a “re-binding” occurs, Windows NT
must be rebooted for the changes to take effect.
•
Server reboots of the CE operating system results in the HPAA
system being unavailable; plan accordingly.
•
When trying to place the HPAA system on the network for
clients to access, it is the CE network properties that must be
changed, not the IOPs.