Installation guide

Physical Hardware Configuration
HP-UX version 11.00.03 Administering Fault Tolerant Hardware 5-7
CPU, Memory, and Console Controller Paths
The CPU and memory constitute one physical nexus (PMERC) while the console
controllers constitute a separate physical nexus (RECCBUS), but the resources for
both (such as processors or tty devices) are treated as part of the same logical nexus
(see “Logical CPU/Memory Configuration”). The CPU, memory, and console
controllers are housed in a single suitcase. The physical addressing scheme is as
follows:
■ The first-level address identifies either the main system bus nexus (GBUS) or
the console controller bus nexus (RECCBUS). For the CPU/memory, the
address is 0. For the console controller, the address is 1.
■ The second-level address identifies either the CPU/memory nexus (PMERC) or
the console controller (RECC). In either case, the values for duplexed boards
are 0 and 1.
■ The third-level address identifies the PMERC resource as either CPU (0) or
memory (1). (Console controllers do not have a third-level physical address.)
The following sample ftsmaint ls output shows physical CPU, memory, and
console controller hardware paths:
Modelx H/W Path Description State Serial# PRev Status FCode Fct
===========================================================================
- CLAIM - - Online - 0
- 0 GBUS Nexus CLAIM - - Online - 0
g32100 0/0 PMERC Nexus CLAIM 10426 9.0 Online - 1
- 0/0/0 CPU Adapter CLAIM - - Online - 0
m70700 0/0/1 MEM Adapter CLAIM - - Online - 0
g32100 0/1 PMERC Nexus CLAIM 10426 9.0 Online - 1
- 0/1/0 CPU Adapter CLAIM - - Online - 0
m70700 0/1/1 MEM Adapter CLAIM - - Online - 0
...
- 1 RECCBUS Nexus CLAIM - - Online - 0
e59300 1/0 RECC Adapter CLAIM 12379 17.0 Online - 0
e59300 1/1 RECC Adapter CLAIM 12386 17.0 Online - 0
NOTE
The sample ftsmaint ls output in this and the following sections
shows the selected devices only. Actual ftsmaint ls output lists all
devices.