Filter
Top Products
There are two console level Memory Channel diagnostics, mc_diag and
mc_cable:
• The mc_diag diagnostic:
– Tests the Memory Channel adapter(s) on the system running the
diagnostic.
– Runs as part of the initialization sequence when the system is
powered up.
– Runs on a standalone system or while connected to another system or
a hub with the link cable.
• The mc_cable diagnostic:
– Must be run on all systems in the cluster simultaneously (therefore,
all systems must be at the console prompt).
__________________ Caution __________________
If you attempt to run mc_cable on one cluster member
while other members of the cluster are up, you may crash
the cluster.
– Is designed to isolate problems to the Memory Channel adapter,
BC12N or BN39B link cables, hub linecards, fiber optics converters,
BN34R fiber optics cable, and, to some extent, to the hub.
– Indicates data flow through the Memory Channel by response
messages.
– Runs continuously until terminated with Ctrl/C.
– Reports differences in connection state, not errors.
– Can be run in standard or virtual hub mode.
When the console indicates a successful response from all other systems
being tested, the data flow through the Memory Channel hardware has
been completed and the test may be terminated by pressing Ctrl/C on each
system being tested.
Example 5–1 shows a sample output from node 1 of a standard hub
configuration. In this example, the test is started on node 1, then on node
0. The test must be terminated on each system.
5–12 Setting Up the Memory Channel Cluster Interconnect