ClearPath IX Systems Installation and Configuration Guide
ClearPath IX Systems Installation and Configuration Guide ClearPath IX Systems Installation and Configuration Guide
Customizing the Site 9. Select each new UnixWare node name and the new SPO server name. A dialogue box appears for each new UnixWare node name, informing you that the UNIX agent for the new UnixWare node name has been placed into directory /var/opt/spo/manual/new-Intelnode-name on the SPO server. 10. Click OK for each dialogue box. A dialogue box appears informing you that the UNIX agent for the new SPO server name has been installed successfully. 11. Click OK. 12. Check to see that the URM agent is running on the SPO server as follows: a. Enter the following command on the SPO server: ps -ef | grep urm.loop b. Check the response output for sh ./urm.loop. If the URM agent is not running, su to the root user (enter the su command to become superuser) and enter the following command: /opt/SPO-agent start 13. Sign on to each UnixWare node as the root user (user-id root) and enter the following commands: rcp -pr spo-server-name:/var/opt/spo/data/manual/new-Intelnode-name /tmp where spo-server-name is the network name of the SPO server. cd /tmp/new-Intelnode-name ./install 14. Again, check to see that the URM agent is running on the UnixWare node by entering the following command: ps -ef | grep urm.loop a. Check the response output for sh ./urm.loop. b. If the URM agent is not running, enter the following command: /opt/SPO-agent start 15. At the SPO workstation, in the Maintain UNIX Agents window's menu bar, click File, then select Exit. 16. Exit the Single Point Configuration routine as follows: a. From the Configure SPO Basic Edition main menu window click File, then select the Exit Configuration Routine option. A window appears to verify that you wish to quit. b. Click OK. 16–16 Version 009B (Web Only) 7850 5104–009
16.6. Testing TCP/IP Communications Customizing the Site Once sites customize their CMS 1100 configuration(16.2), they can test TCP/IP communications as follows: 1. Access an OS 2200 console session at either the SPO workstation or at the monitor concentrator. 2. Start the customized CMS 1100 configuration. CMS 1100 should indicate that the Ethernet interface has been initialized, and is up and active. 3. At the Intel node, log on as follows: • At a UnixWare node, log on as superuser at a console session, if you are not already logged on (10.13.2). • At a Windows NT node, log on as administrator, if you are not already logged on (11.8), and open the Command Prompt window (MS-DOS prompt). 4. Type the following command, then press Enter: ping xxx.xxx.xxx.xxx where xxx.xxx.xxx.xxx is the IP address of the 2200 node. Alternatively, you could enter hostname instead of the IP address, where hostname is the Internet system name assigned to the 2200 node. The following message should appear in response: xxx.xxx.xxx.xxx is alive where xxx.xxx.xxx.xxx is the IP address of the 2200 node. The connection is not operational if the following message appears: no answer from xxx.xxx.xxx.xxx 16.7. Installing Optional UnixWare Products After running the tuning script to complete installation of UnixWare, sites can install optional application packages. In general, optional packages are installed using the following procedure: 1. If you are not already logged on, log on as the root user (user-id root). 2. Load the application package release medium (CD-ROM, tape, or diskette) in the appropriate drive unit. 3. At the shell prompt enter a pkgadd command appropriate to the media. For example: # pkgadd -d /dev/rdsk/device where device is the name of the device from which software is being installed (for example, c0s0 or f03ht). Answer any prompts that appear on the screen. Refer to the individual product documentation for specific instructions. 4. After the last package has been installed, reboot. 7850 5104–009 Version 009B (Web Only) 16–17
- 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 and 364: Customizing the Site lan-address la
- Page 365 and 366: 14. Select the Changes menu bar ite
- Page 367 and 368: Customizing the Site b. Select CP_U
- Page 369: Customizing the Site l. Repeat thes
- 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
- Page 415 and 416: Glossary master configuration table
- Page 417 and 418: N NAS NetBIOS See network access se
- Page 419 and 420: Glossary Open/OLTP Pathway An Open/
Customizing the Site<br />
9. Select each new UnixWare node name <strong>and</strong> the new SPO server name.<br />
A dialogue box appears for each new UnixWare node name, informing you that the<br />
UN<strong>IX</strong> agent for the new UnixWare node name has been placed into directory<br />
/var/opt/spo/manual/new-Intelnode-name on the SPO server.<br />
10. Click OK for each dialogue box.<br />
A dialogue box appears informing you that the UN<strong>IX</strong> agent for the new SPO server<br />
name has been installed successfully.<br />
11. Click OK.<br />
12. Check to see that the URM agent is running on the SPO server as follows:<br />
a. Enter the following comm<strong>and</strong> on the SPO server:<br />
ps -ef | grep urm.loop<br />
b. Check the response output for sh ./urm.loop.<br />
If the URM agent is not running, su to the root user (enter the su comm<strong>and</strong> to<br />
become superuser) <strong>and</strong> enter the following comm<strong>and</strong>:<br />
/opt/SPO-agent start<br />
13. Sign on to each UnixWare node as the root user (user-id root) <strong>and</strong> enter the following<br />
comm<strong>and</strong>s:<br />
rcp -pr spo-server-name:/var/opt/spo/data/manual/new-Intelnode-name /tmp<br />
where spo-server-name is the network name of the SPO server.<br />
cd /tmp/new-Intelnode-name<br />
./install<br />
14. Again, check to see that the URM agent is running on the UnixWare node by entering<br />
the following comm<strong>and</strong>:<br />
ps -ef | grep urm.loop<br />
a. Check the response output for sh ./urm.loop.<br />
b. If the URM agent is not running, enter the following comm<strong>and</strong>:<br />
/opt/SPO-agent start<br />
15. At the SPO workstation, in the Maintain UN<strong>IX</strong> Agents window's menu bar, click File,<br />
then select Exit.<br />
16. Exit the Single Point <strong>Configuration</strong> routine as follows:<br />
a. From the Configure SPO Basic Edition main menu window click File, then select<br />
the Exit <strong>Configuration</strong> Routine option. A window appears to verify that you wish<br />
to quit.<br />
b. Click OK.<br />
16–16 Version 009B (Web Only) 7850 5104–009