User`s manual

CBI-1010
On systems where the BI is the system I/O bus (i.e. 58xx, 85xx, 8700, 8800 and
aIl6000's), the system node ID does not match the BI node ID. For example, a
VAX 6000 machine has 240 system node ID's. The XMI bus has 15 nodes each
logically capable of containing a bus
adapter with 16 node ID of its own.
Physically this arrangement is not permissible, however, this is
how VMS
looks at the system.
Table 3-4 shows a
map of system node ID's for a VAX 6000 type machine.
Table 3-4
Map
of System Node 10 for VAX 6000
XMI node
System nodes
1
0-15
2
16 -
31
3 32 - 47
4
48 - 63
5
64 -
79
6
80 - 95
7
96 - 111
8
112 - 127
9 128 -
143
10
144 - 159
11
160 - 175
12
176 -
191
13 192 - 207
14
208 - 223
15
224 - 239
It is desirable to install the CBI-I0I0 at a system node ID that will not change
the physical device names of the currently installed devices. This is
accomplished by installing the CBI-l0l0 at a higher system node ID than
any other currently installed device of the same type.
The
CBI-I0I0/T is device type PT /MU and should be installed at a higher
system node ID
than other TMSCP tape controllers. The CBI-I010 /M and CBI-
1010/MB is a device type PU/DU and should be installed at a higher system
node ID than other MSCP disk controllers. The CBI-I0I0/TM is a device type
of
PU /DU and PT /MU and should be installed at a higher system node ID
than other MSCP disk and TMSCP tape controllers.
Installation 3-5