Instruction Manual

Look for any missing entry. In our example, the definition of the route to Network3
is missing. We will add the definition using the command:
smitty nim_mkroute
Select the Originating and Destination Network Object Names; in our example,
network1 and network3 , respectively.
à ð
Define a Network Install Route
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
 Originating Network Object Name network1
 Gateway Used by Originating Network [gw1_tok]
 Destination Network Object Name network3
 Gateway Used by Destination Network [gw1_eth]
Force no +
F1=Help F2=Refresh F3=Cancel F4=List
F5=Reset F6=Command F7=Edit F8=Image
F9=Shell F1=Exit Enter=Do
á ñ
Figure 48. Defining the Route Between First and Second Networks
The gateway's IP Addresses and IP Names must be defined in the name server
database or in the NIM Master's /etc/hosts file.
9.2.5 NIM Client Machine Definition
In our example, we are using an RS/6000 Model 40P as the NIM Client. The 40P
is also a PCI-based RS/6000, and thus its platform type is rspc . The rspc systems
can be installed over the network as stand-alone , diskless or dataless systems. In
this example, we are going to install the 40P as a stand-alone machine.
Before you can enter the NIM Client's definition, you must obtain the hardware
address of the network adapter on the Client. Obtaining this address is different on
PCI-based RS/6000 systems than on the microchannel-based RS/6000 systems.
Using PCI-based RS/6000 systems you can look up the network adapter hardware
address by using System Management Services and selecting the Adapter
Parameters option.
PCI-based RS/6000 systems do not require an IPL ROM emulation device. Some
microchannel-based RS/6000 systems, however, do require IPL ROM emulation
media and you will have to create this on the NIM Master. As you are using a
PCI-based RS/6000 system as a NIM Master, you will have to explicitly state the
166 Introduction to PCI-Based RS/6000 Servers