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

SCSI Bus Numbers, SCSI IDs, Boot Disks

Page 18 highlights

HP NetServer AA Here is an example of the SCSI information needed from the Windows NT Registry: When filling out the SCSI configuration chart included in the Installation Guide, the following notes are some reminders about the configurations of SCSI devices: • SCSI Bus Numbers - Be sure to have all of the drivers installed for the SCSI adapters to be used. The check the NT registry for the bus numbers. • SCSI IDs - Verify what SCSI ID is being used by the adapter. This may be seen in the setup utility of the SCSI adapter as the "Initiator ID", or in the NT Registry as the "Target ID." Typically the adpater ID is '7,' but it may be changed or different. The same SCSI ID for the adapter must be used on both IOPs. • Boot Disks - For the IOP, this should be the disk that is SCSI ID 0 on each IOP. For the CE, this should be the first disk redirected in the AA 4000 software; typically this is SCSI ID 1. SCSI Port Number Changes Windows NT assigns port numbers to SCSI adapters based on the load order of the adapters' device drivers at boot time. This is important because it is possible that the addition of another SCSI adapter may impact the NT port assignments. For example, the addition of an Adaptec Controller may result in its port assignment being 0 and the other SCSI adapters that previously existed would have their port numbers increased by 1. The result of this scenario is the AA 4000 software will not be able to identify the devices correctly based upon its configuration file. 1-12 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
1-12
Here is an example of the SCSI information needed from the
Windows NT Registry:
When filling out the SCSI configuration chart included in the
Installation Guide
, the following notes are some reminders about the
configurations of SCSI devices:
SCSI Bus Numbers
– Be sure to have all of the drivers installed
for the SCSI adapters to be used.
The check the NT registry for
the bus numbers.
SCSI IDs
– Verify what SCSI ID is being used by the adapter.
This may be seen in the setup utility of the SCSI adapter as the
“Initiator ID”, or in the NT Registry as the “Target ID.”
Typically the adpater ID is ‘7,’ but it may be changed or
different.
The same SCSI ID for the adapter must be used on
both IOPs.
Boot Disks
– For the IOP, this should be the disk that is SCSI ID
0 on each IOP.
For the CE, this should be the first disk
redirected in the AA 4000 software; typically this is SCSI ID 1.
SCSI Port Number Changes
Windows NT assigns port numbers to SCSI adapters based on the
load order of the adapters’ device drivers at boot time. This is
important because it is possible that the addition of another SCSI
adapter may impact the NT port assignments.
For example, the
addition of an Adaptec Controller may result in its port assignment
being 0 and the other SCSI adapters that previously existed would
have their port numbers increased by 1.
The result of this scenario is
the AA 4000 software will not be able to identify the devices
correctly based upon its configuration file.