ClearPath IX Systems Installation and Configuration Guide

Verifying the Interconnects and Achieving Hardware RFU
The "1" option instructs CMS 1100 to retrieve the system configuration from CMS1100$*-
CONFIG$.CONFIG and save an internal representation of it. This option must be used
whenever the system configuration changes and CMS 1100 is reconfigured. At other times,
it is unnecessary but harmless.
Using CMS 1100 in Verifying Hardware Communications (If Not Yet Done)
At this point, if the PING test for hardware communications has not been done, continue
with 14.6. Otherwise continue with Section 15.
14.6. Running the PING Test to Verify Hardware
Communications
Once CMS 1100 is up and running (14.5.1 or 14.5.2), take the steps below to test
interconnect communications and achieve hardware RFU.
Notes:
• For Model IX5000 Series or IX4800 servers below Plateau 2.0 that are configured for
resilient partitions, a minimum CC3000 tape level of 1R2 is required to execute the
PING test for the second 2200 node. At Plateau 2.0, the CC6000 tape supersedes the
CC3000 for all configurations. The minimum required level of CC6000 is 2R1.
• If the second 2200 node in a resilient partition is up and running, perform the
PING test for both nodes.
• During a PING test, CMS 1100 warning messages may appear stating “*FDDIVn
NODE(S) NOT CONFIGURED IN THE EXEC.” You can ignore those messages if the
connections were not configured because the extra interconnect hardware
components were not purchased as part of the system. But, if you receive four of
those messages where n is equal to I, J, K, and L then the ODB either does not have
the interconnect configured, or it is configured with the wrong device names.
1. At each Intel node, log on as follows:
• If running UnixWare, log on as superuser at a console session, if you are not
already logged on (8.12.1).
• If running Windows NT, log on as administrator, if you are not already logged on
(3.5), and launch a Command Prompt session.
2. For each active 2200 node, type the following command, then press Enter:
ping fddiname
where fddiname is the FDDI host name of the 2200 node being tested (see Appendix B
for assigned FDDI host names).
The response depends on which software is being run as follows:
• For UnixWare, the following message appears:
fddiname is alive
The connection is not operational if the following message appears:
no answer from fddiname
7850 5104–009 Version 009B (Web Only) 14–15