ClearPath IX Systems Installation and Configuration Guide
ClearPath IX Systems Installation and Configuration Guide ClearPath IX Systems Installation and Configuration Guide
Customizing the Site 5. Select the Hosts File menu bar item, then press Enter. A list of options appears as follows: Load Save Exit 6. Select Load, then press Enter. 7. Press the up or down arrow keys to get the following drop down list: DOS-HD DOS-DD UNIX 8. Use the arrow keys to select the UNIX option, then press Enter. 9. Tab to the Host Name field, enter the site-defined name of the console you are loading. The Execute box appears. 10. Again press Enter. You are prompted to insert the diskette. 11. Insert the diskette with the hosts file on it, then press Enter. A window appears indicating that the system is working and that you should wait. When the system completes loading the hosts file, it returns to the Single Point Interface Utility window. 12. If you do not have a router, skip this step. If you have a router, add router information as follows: a. Select the Routers menu bar item. A list of options appears as follows: Add Router Delete Router Display Routers b. Select Add Router, then press Enter. An Add Router window appears. c. Enter information in that window as follows: • In the top portion enter the IP address and host name that defines the destination of messages to be routed through the router. That destination can be either a network or a host. • In the bottom portion, enter the IP address and host name of the router. 13. When done, press Enter. The Single Point Interface Utility window reappears. 16–10 Version 009B (Web Only) 7850 5104–009
14. Select the Changes menu bar item. A list of options appears as follows: Initialize Work Execute Changes Report Changes 15. Select Execute Changes to enable the changes to the hosts file. 16. Select Exit to exit from the Single Point Interface utility. Repeat this procedure for each system console. Customizing the Site 16.5.4. Changing a Windows 2000 or Windows NT Representation Using the Rename Script When the SPO server operating system is installed, a tuning script is run. The tuning script prompts for Windows 2000 and Windows NT node system names. It assigns those system names as labels for the Windows node representations in SPO cluster diagrams. To later change the names of those node representations, you must first edit the SPO server and UnixWare hosts files to reflect the desired Windows 2000 or Windows NT node names (see 16.5.2). The format of those changes in the hosts files must be as follows: where: xxx.xxx.xxx.xxx newname oldname cp_ntx xxx.xxx.xxx.xxx The IP address of the node newname The new name oldname The name currently being used, if not cp_ntx cp_ntx The CP_NT alias designation Once the hosts files have been edited, you can use the Single Point Configuration routine as described in 16.5.5 to replace existing node representations with new ones one at a time. Or you can run a rename script to replace them all at once. The rename script searches all SPO configurations whose names contain NT (for example, 2_2UNIX_2NT_6.3CP) for lines with the cp_nt aliases and substitutes all occurrences of the third field in the hosts file with the second field. To run the rename script, take the following steps at the SPO server: 1. If you are not already logged on, log on as the root user (user-id root). 2. Enter the following command to change to the directory containing the script: cd /var/sadm/pkg/cptune/install 7850 5104–009 Version 009B (Web Only) 16–11
- Page 313 and 314: Configuring Intel Nodes for Monitor
- Page 315 and 316: Configuring Intel Nodes for Monitor
- Page 317 and 318: Configuring Intel Nodes for Monitor
- Page 319 and 320: Configuring Intel Nodes for Monitor
- Page 321 and 322: Section 13 Installing the Basic OS
- Page 323 and 324: Installing the Basic OS 2200 IOE Yo
- Page 325 and 326: Installing the Basic OS 2200 IOE 5.
- Page 327 and 328: Installing the Basic OS 2200 IOE 2.
- Page 329 and 330: Installing the Basic OS 2200 IOE Yo
- Page 331 and 332: Section 14 Verifying the Interconne
- Page 333 and 334: 14.2.1. Installing HLC-2 Microcode
- Page 335 and 336: Verifying the Interconnects and Ach
- Page 337 and 338: Verifying the Interconnects and Ach
- Page 339 and 340: Verifying the Interconnects and Ach
- Page 341 and 342: Verifying the Interconnects and Ach
- Page 343 and 344: Verifying the Interconnects and Ach
- Page 345 and 346: Verifying the Interconnects and Ach
- Page 347 and 348: Section 15 Installing the Remaining
- Page 349 and 350: 15.2.2. Setting Up the TIP Environm
- Page 351 and 352: APP 3 ROLLBACK INITIALIZATION START
- Page 353 and 354: INAP3 MAX PAGES Installing the Rema
- Page 355 and 356: Section 16 Customizing the Site Cus
- Page 357 and 358: Customizing the Site 1. Copy the ne
- Page 359 and 360: Customizing the Site 5. Verify your
- Page 361 and 362: Customizing the Site A dialogue box
- Page 363: Customizing the Site lan-address la
- Page 367 and 368: Customizing the Site b. Select CP_U
- Page 369 and 370: Customizing the Site l. Repeat thes
- Page 371 and 372: 16.6. Testing TCP/IP Communications
- Page 373 and 374: Customizing the Site ClearPath IX50
- Page 375 and 376: Section 17 Installing Optional OS 2
- Page 377 and 378: Appendix A Tables of Documentation,
- Page 379 and 380: Major Hardware or Software Changes
- Page 381 and 382: Major Hardware or Software Changes
- Page 383 and 384: Intel Platform Tables of Documentat
- Page 385 and 386: Tables of Documentation, Support, a
- Page 387 and 388: Appendix B Communication Settings S
- Page 389 and 390: Communication Settings Specific to
- Page 391 and 392: Appendix C SPO/HMP IX Interface Lic
- Page 393 and 394: SPO/HMP IX Interface License Key Re
- Page 395 and 396: Appendix D Configuring the FDDI Int
- Page 397 and 398: INVENTORY_INCLUDE: Limited Comprehe
- Page 399 and 400: The HLC-2 Subsystem Connections FDD
- Page 401 and 402: Appendix E Installing OPE and SysAd
- Page 403 and 404: Glossary A ACID properties The esse
- Page 405 and 406: Glossary central electronics comple
- Page 407 and 408: CSIOP D DAC daemon datagram See cha
- Page 409 and 410: DSA DSPER DTP DUA See directory ser
- Page 411 and 412: H HBA Abbreviation for host bus ada
- Page 413 and 414: Glossary Integration Expert The onl
14. Select the Changes menu bar item.<br />
A list of options appears as follows:<br />
Initialize Work<br />
Execute Changes<br />
Report Changes<br />
15. Select Execute Changes to enable the changes to the hosts file.<br />
16. Select Exit to exit from the Single Point Interface utility.<br />
Repeat this procedure for each system console.<br />
Customizing the Site<br />
16.5.4. Changing a Windows 2000 or Windows NT Representation<br />
Using the Rename Script<br />
When the SPO server operating system is installed, a tuning script is run. The tuning script<br />
prompts for Windows 2000 <strong>and</strong> Windows NT node system names. It assigns those system<br />
names as labels for the Windows node representations in SPO cluster diagrams.<br />
To later change the names of those node representations, you must first edit the SPO<br />
server <strong>and</strong> UnixWare hosts files to reflect the desired Windows 2000 or Windows NT node<br />
names (see 16.5.2). The format of those changes in the hosts files must be as follows:<br />
where:<br />
xxx.xxx.xxx.xxx newname oldname cp_ntx<br />
xxx.xxx.xxx.xxx The IP address of the node<br />
newname The new name<br />
oldname The name currently being used, if not cp_ntx<br />
cp_ntx The CP_NT alias designation<br />
Once the hosts files have been edited, you can use the Single Point <strong>Configuration</strong> routine<br />
as described in 16.5.5 to replace existing node representations with new ones one at a time.<br />
Or you can run a rename script to replace them all at once.<br />
The rename script searches all SPO configurations whose names contain NT (for example,<br />
2_2UN<strong>IX</strong>_2NT_6.3CP) for lines with the cp_nt aliases <strong>and</strong> substitutes all occurrences of<br />
the third field in the hosts file with the second field.<br />
To run the rename script, take the following steps at the SPO server:<br />
1. If you are not already logged on, log on as the root user (user-id root).<br />
2. Enter the following comm<strong>and</strong> to change to the directory containing the script:<br />
cd /var/sadm/pkg/cptune/install<br />
7850 5104–009 Version 009B (Web Only) 16–11