Sun Microsystems Sun HPC 3.0, Руководство пользователя

Страница: 37 / 67

ID 1 to the adapter in the next higher-numbered slot, and so forth. ID value
assignments are always consecutive, even if the adapters are not installed in adjacent
slots. Consequently, if adapter cards are not installed in adjacent slots, adapter ID
values do not necessarily correspond to SBus slot numbers.
Once an ID value is assigned, it will not be reassigned, even if the adapter to which
it was originally assigned is removed.
Because a ID values do not necessarily correspond to SBus slot numbers, the adp n
values that you assign in the sci_config.hpc file may not match the actual ID
assignments made by the device driver. For this reason, you may need to revise this
adapter connection description (that is, the contents of Section 7) to match the actual
adapter connections.
This is why you were advised to make the temporary map of the physical network
layout. Instructions for ensuring that the sci_config.hpc file matches the actual
adapter ID values are provided in “Compare
sm_config
Output With Contents of
sci_config.hpc
” on page 28
Section 7 – Network IP Addresses
Specify the first three octets of the IP address of each link or switch. For example, for
a two-node, striped configuration,
Network IP address for Link 0 = 204.71.29
Network IP address for Link 1 = 204.71.15
An example of a four-node, nonstriped configuration might be
Network IP address for Switch 0 = 204.101.30
Section 8 – Netmask Value
Specify the netmask to be used for the private SCI subnet. For example,
Netmask = e0
This netmask value will support up to eight subnets with up to 30 hosts per subnet.
Configuring the SCI Network Interface
27