A diskless node's partner node provides the system software and disk services for the diskless node. It does not necessarily store any of the diskless node user's files. Each partner node must run the diskless node server, netman. Partners can be user nodes with display monitors, or DSPs, the server nodes.
A partner node must have the correct system software for the diskless node type. For example, if the diskless node is a DN570 and the partner node is a DSP90, the partner node must have both a Isau2 directory and a IsauS directory. Similarly, the partner's Isys directory must have any microcode files required by the diskless node. Tables 3-1 through 3-3 list many of the node-type dependent system software files.
Each diskless node has its own Isyslnode_data.diskless_node_id directory on the partner node, and 'node_data on each diskless node resolves to Isyslnode_data.diskless_node_id. If you change diskless node partner assignments, delete the Isyslnode_data.diskless_node_id directory from the original
c
partner's Isys directory.
0
The home directories of diskless node users can be located on any node in the network, and do not
o
log-in start-up scripts, user_data/startup _dm [.type], should be in their home directories.Specifying Partners
Figure 3-8. A Isyslnetldlskless_list File
If you put a diskless node on more th&n one diskless list, you cannot predict which node will become the partner when the diskless node boots. As a result, the diskless node's 'node_data directory, and therefore its contents, could change whenever the node reboots. Therefore, you must configure the diskless node correctly on each possible partner node. (See the following section "The /sys/node_data.node_id Directory on New Partners" for more details.) If you use names for diskless nodes, do not change the name of the
/sys/node_data.diskless_node_id directory to /sys/node_data.diskless_node_name.
Remember, a diskless node name is not valid in a pathname. You must specify the diskless node ID to accurately access this object.
When you boot a diskless node you can request a specific partner node. See
"Requesting a Specific Partner," later in this chapter.
The Isys/node_data.node_id Directory on New Partners
If a diskless node's partner does not have a /sys/node_data.node_id directory when the diskless node boots using the partner, netman automatically creates one. If this directory does not contain the minimal set of files required by the diskless node to operate, netman creates them. Netman also copies the startup[.type] file from the partner's /sys/dm/startup_templates or
/sys /spm/startup _templates directory.
Providing a New Partner for a Diskless Node
Use Procedure 3-1 to configure a partner for a new node, change a partner for an existing node, or to provide an additional partner for an existing node. Note that if a service representative installs a diskless node, he or she creates a partner for the node; however, you might want to use a different partner.
PROCEDURE 3-1: Providing a Permanent Partner for a Diskless Node
1. Determine the diskless node's ID number. If the node is new, the node identification slip lists the node ID. If the diskless node currently has a partner, you can determine the ID by entering the following command at the diskless node:
$ netstat
The node 10 of this node is eff21.
c
2. Log in to the partner node. shell on the partner by using the following command: If the partner does not have a display you can create a remote
c\
_/$ crp -on Ilpartner -me
3. Add the diskless node's node ID to the partner node's Isyslnetldiskless_list file.
4. If you are changing partner nodes, delete the diskless node from the old partner node's Isyslnetldiskless_list. Also delete the Isyslnode_data.diskless_node_id directory from the original partner's Isys directory.
5. If the partner node is not running netman, do the following:
a. Remove the comment character (#) from the following line in the partner's Isyslnode_data[.node_id]/startup[.type] file:
# cps /sys/net/netman -n netman
The netman server will now start automatically whenever you reboot the partner.
b. Start the partner node's netman server. (By doing this, you do not have to reboot the part- f~
ner.) If you are at the partner node, enter the following command in its DM input window:
~/
Command: cps Isys/net/netman
To start netman from a remote node, enter the following command. (You must use this com-mand even if yoU used the crp comcom-mand in Step 2.)
$ crp -on node -cps Isys/net/netman -n netman
6. You can limit the size of the partner's memory pool that is available to the diskless node for paging requests. Enter
$ netsvc -p [poo,-size]
where poo'-size is the maximum number of memory pages that will be available for diskless node paging.
7. If you are installing a new diskless node, you can give it a name as follows. Skip this step if
o
o o o
o
Procedure 3-1 (Cont.)
• If you do not use ns_helper on your network enter the following command. After you finish this procedure, catalog the node on the network as described in Chapter 2.
$ ctnode node_name nOdeJd
• If you use ns_helper at your site, enter the following:
$ ctnode node_name nOdeJd -root
8. Create the diskless node's node start-up and configuration files. While there are many different ways you can do this, the following steps will work in all cases:
a. Create the diskless node's Isyslnode_data.node_id directory by entering the following com-mand at the partner node:
$ crd Isys/node_data.nodeJd where nodeJd is the diskless node's ID.
NOTE: If you are changing the partner of an existing diskless node, you can skip Steps 8b and 8c.
Instead, copy these configuration files from the old partner to the new partner.
b. Copy thelsyslnode_data.node_idlstartup[.type] file (where type indicates the type of display on the diskless node, not the partner) from the partner. You can copy the file from the part-ner's Isyslnode_data directory, or from the Isysldmlstartup_templates directory (for diskless nodes with displays) or Isyslspmlstartup _templates directory (for diskless DSPs).
c. Edit the following files to meet the diskless node's needs:
Isyslnode_data.node _idlstartup [.type]
9. Log off the partner node.
10. You can now start or restart the diskless node. If you are changing an existing diskless node's partner, do the following:
a. Enter the following DM command to log off and shut down the operating system.
Command: shut
b. The Bootstrap PROM prompt (» appears on the screen; enter the following reset command:
> re
c. Press <RETURN> twice.
d. The PROM identifier appears, followed by the PROM prompt. Restart the operating system by entering the following command:
MD REV n, yy/dd/mm
> ex aegis
The node now restarts, using the new partner node; you can now log in.
END OF PROCEDURE 3-1