ClearPath IX Systems Installation and Configuration Guide
ClearPath IX Systems Installation and Configuration Guide ClearPath IX Systems Installation and Configuration Guide
Verifying the Interconnects and Achieving Hardware RFU WARNING TEMPORARY CMS-SETUP RESTRICTION AND WORKAROUND If you plan to use Integration Expert (15.3), you must first correct the output from CMS-SETUP. The configuration that CMS-SETUP produces supports PING testing and basic communications, but it does not allow Integration Expert to function. Example 14–1 contains two ClearPath sentinels that Integration Expert requires but that CMS-SETUP omits. Each sentinel consists of the following line: . CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH To permit Integration Expert to execute correctly, you must 1. Update the element CMS1100$*CONFIG$.CONFIG to contain the two ClearPath sentinel lines exactly as shown in Example 14–1. Each line is exactly 81 characters long, begins with a period and a space, and contains eight repetitions of the word CLEARPATH separated by asterisks. You can use a Telnet session on any Windows workstation attached to the LAN to do the editing. 2. Terminate the CMS 1100 run (if you have started it—see "Starting CMS") by entering the following keyin: II CMS TERM 3. Start CMS 1100 again with the following keyin: ST STARTCMS,1 The need for this workaround will be eliminated with the next ClearPath release. Follow the steps below to configure CMS 1100 with a minimum, or basic, configuration, using the CMS-SETUP run. This configuration lets you use CMS 1100 to install other products and customize your site (Sections 15 and 16). Later, if you wish, you can enhance the CMS 1100 configuration to meet the site's full requirements. 1. Start the run using the ST keyin on the 2200 node. ST CMS-SETUP The following messages from CMS-SETUP appear: CMS-SETUP START n-ENTER HOST1 FDDI LAN INPUT DEVICE NAME n 2. Press Enter to accept the default, or type a different device name. You are asked for an FDDI LAN output device name for the same host (Host1): n-ENTER HOST1 FDDI LAN OUTPUT DEVICE NAME n 14–12 Version 009B (Web Only) 7850 5104–009
Verifying the Interconnects and Achieving Hardware RFU 3. Press Enter to accept the default, or type a different device name. You are asked for an input device name for the FDDI LAN on the next host, Host2: n-ENTER HOST2 FDDI LAN INPUT DEVICE NAME n 4. Press Enter to accept the default, or type a different device name. You are asked for an output device name for the FDDI LAN on Host2: n-ENTER HOST2 FDDI LAN OUTPUT DEVICE NAME n 5. Press Enter to accept the default, or type a different device name. You are asked for an input device name for the FDDI LAN on the next host, Host3: n-ENTER HOST3 FDDI LAN INPUT DEVICE NAME n 6. Press Enter to accept the default, or type a different device name. You are asked for an output device name for the FDDI LAN on Host3: n-ENTER HOST3 FDDI LAN OUTPUT DEVICE NAME n 7. Press Enter to accept the default, or type a different device name. You are asked for an input device name for the FDDI LAN on the last host, Host4: n-ENTER HOST4 FDDI LAN INPUT DEVICE NAME n 8. Press Enter to accept the default, or type a different device name. You are asked for an output device name for the FDDI LAN on Host4: n-ENTER HOST4 FDDI LAN OUTPUT DEVICE NAME n 9. Press Enter to accept the default, or type a different device name. You are asked to enter the name of the Ethernet LAN input device: n-ENTER ETHERNET LAN INPUT DEVICE NAME < > n devnam 10. Type the name of the input device and press Enter. You are asked to enter the name of the corresponding output device: n-ENTER ETHERNET LAN OUTPUT DEVICE NAME < > n devnam 11. Type the name of the output device and press Enter. The following query appears: *****MESSAGE,I THE EXTERNAL LAN MAY OPTIONALLY HAVE A GATEWAY n-DO YOU HAVE A GATEWAY ON YOUR LAN? Y/N n 7850 5104–009 Version 009B (Web Only) 14–13
- Page 291 and 292: Installing and Configuring SPO Work
- Page 293 and 294: Installing and Configuring SPO Work
- Page 295 and 296: Installing and Configuring SPO Work
- Page 297 and 298: Installing and Configuring SPO Work
- Page 299 and 300: Installing and Configuring SPO Work
- Page 301 and 302: Installing and Configuring SPO Work
- Page 303 and 304: Installing and Configuring SPO Work
- Page 305 and 306: Installing and Configuring SPO Work
- Page 307 and 308: Section 12 Configuring Intel Nodes
- Page 309 and 310: Configuring Intel Nodes for Monitor
- Page 311 and 312: Configuring Intel Nodes for Monitor
- 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: 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 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
Verifying the Interconnects <strong>and</strong> Achieving Hardware RFU<br />
WARNING<br />
TEMPORARY CMS-SETUP RESTRICTION AND WORKAROUND<br />
If you plan to use Integration Expert (15.3), you must first correct the<br />
output from CMS-SETUP. The configuration that CMS-SETUP produces<br />
supports PING testing <strong>and</strong> basic communications, but it does not allow<br />
Integration Expert to function.<br />
Example 14–1 contains two <strong>ClearPath</strong> sentinels that Integration Expert<br />
requires but that CMS-SETUP omits. Each sentinel consists of the<br />
following line:<br />
. CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH<br />
To permit Integration Expert to execute correctly, you must<br />
1. Update the element CMS1100$*CONFIG$.CONFIG to contain the two<br />
<strong>ClearPath</strong> sentinel lines exactly as shown in Example 14–1. Each line<br />
is exactly 81 characters long, begins with a period <strong>and</strong> a space, <strong>and</strong><br />
contains eight repetitions of the word CLEARPATH separated by<br />
asterisks. You can use a Telnet session on any Windows workstation<br />
attached to the LAN to do the editing.<br />
2. Terminate the CMS 1100 run (if you have started it—see "Starting<br />
CMS") by entering the following keyin:<br />
II CMS TERM<br />
3. Start CMS 1100 again with the following keyin:<br />
ST STARTCMS,1<br />
The need for this workaround will be eliminated with the next <strong>ClearPath</strong><br />
release.<br />
Follow the steps below to configure CMS 1100 with a minimum, or basic, configuration,<br />
using the CMS-SETUP run. This configuration lets you use CMS 1100 to install other<br />
products <strong>and</strong> customize your site (Sections 15 <strong>and</strong> 16). Later, if you wish, you can enhance<br />
the CMS 1100 configuration to meet the site's full requirements.<br />
1. Start the run using the ST keyin on the 2200 node.<br />
ST CMS-SETUP<br />
The following messages from CMS-SETUP appear:<br />
CMS-SETUP START<br />
n-ENTER HOST1 FDDI LAN INPUT DEVICE NAME <br />
n<br />
2. Press Enter to accept the default, or type a different device name.<br />
You are asked for an FDDI LAN output device name for the same host (Host1):<br />
n-ENTER HOST1 FDDI LAN OUTPUT DEVICE NAME <br />
n<br />
14–12 Version 009B (Web Only) 7850 5104–009