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

Network Bindings, Video Drivers in the CE, Redirected Devices

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

HP NetServer AA screws until they are snug but do not over-tighten. Over-tightening may cause the retaining pins to break. There should be no gaps between the Cable head and the MIC. Common Problems In the experiences obtained to date working with the HP AA solution, a few potential problems have shown themselves to occur more frequently than others. These occurrences can generally be attributed to user inexperience. As a user becomes familiar with the system and its architecture, these problems tend not to be created. Network Bindings - Because of the added services and protocols from the Marathon software in addition to the presence of virtual adapters, it is easy for an inexperienced person to confuse the protocols and bindings with the adapters. Remembering there are three distinct networks with different roles is the first step towards understanding that the protocol/service bindings have a unique combination for each network. Configuring the bindings one at a time is also recommended. For details on the network setup, see the Marathon Installation Guide, the Marathon Users Guide, or Module Six of this course. Video Drivers in the CE - With the addition of NT Service Packs or the desire on a customers behalf to have a higher resolution screen, the video drivers can be changed form the Marathon supplied VGA.sys equivalent. This will prevent the CE's from being in sync and only one can participate in the array. Reloading the Marathon software without any changes to the configuration will alleviate this problem. Redirected Devices - Another new concept to first time users is the concept of the physical devices in the IOP being redirected for use to the NT copy for the CE. The concept itself is relatively easy to grasp, the problem sometimes surfaces during the implementation particularly when SCSI IDs for redirected disks must match. The installation guide for Marathon has worksheets and detailed steps on acquiring the correct IDs for redirected devices. 7-24 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
7-24
screws until they are snug but do not over-tighten.
Over-tightening
may cause the retaining pins to break.
There should be no gaps
between the Cable head and the MIC.
Common Problems
In the experiences obtained to date working with the HP AA
solution, a few potential problems have shown themselves to occur
more frequently than others.
These occurrences can generally be
attributed to user inexperience.
As a user becomes familiar with the
system and its architecture, these problems tend not to be created.
Network Bindings
– Because of the added services and protocols
from the Marathon software in addition to the presence of virtual
adapters, it is easy for an inexperienced person to confuse the
protocols and bindings with the adapters.
Remembering there are
three distinct networks with different roles is the first step towards
understanding that the protocol/service bindings have a unique
combination for each network.
Configuring the bindings one at a
time is also recommended.
For details on the network setup, see the
Marathon Installation Guide, the Marathon Users Guide, or Module
Six of this course.
Video Drivers in the CE –
With the addition of NT Service Packs
or the desire on a customers behalf to have a higher resolution
screen, the video drivers can be changed form the Marathon supplied
VGA.sys equivalent.
This will prevent the CE’s from being in sync
and only one can participate in the array.
Reloading the Marathon
software without any changes to the configuration will alleviate this
problem.
Redirected Devices –
Another new concept to first time users is the
concept of the physical devices in the IOP being redirected for use to
the NT copy for the CE.
The concept itself is relatively easy to
grasp, the problem sometimes surfaces during the implementation
particularly when SCSI IDs for redirected disks must match.
The
installation guide for Marathon has worksheets and detailed steps on
acquiring the correct IDs for redirected devices.