The single point of failure service has detected that all of device sdddd CHPIDs share an I/O component internally in the host machine that has a possibility of failing.
Byte Bit
(1-12) (1-8) Component identified
------ ----- ---------------------------------------
1 1-2 Comparison Status. These bits being on
indicates the comparison is invalid
and can be ignored.
3 Book. If you have a multi-book system,
you might consider finding alternate
paths to the device from a different
book.
4 Cage. If you have multiple I/O cages
in your configuration, you might
consider finding paths from
different I/O cages to your device.
5 Failover Domain. If there is a failure
of the IFB-MP card, some paths to
the device will be lost. Some
priority should be given to finding
paths from different redundant
domains to the device.
6 Fanout. Although redundant I/O
interconnect will prevent any loss
of connectivity, some thought
should be given to spreading paths
across different fanout cards.
7 Domain. If there is a failure of the
IFB-MP card, all paths to the device
will be lost. Priority should be
given to finding paths from multiple
domains to the device.
8 Secondary STI/STI. Indicates all paths
to the device are from the same
channel card. Priority should be given
to spreading the paths across
this single point of failure.
2 1 Internal BUS. This is for internal
use only and can be ignored.
2 IBU. This is for internal use only
and can be ignored.
3 Channel. Indicates a single path
exists to the device.
4-8 Reserved
3-12 Reserved
The system continues processing.
None.
The single point of failure might be expected because of hardware limitations within your machine configuration. If the single point of failure is not expected, consult configuration experts to analyze the condition.
IOS
IOSVSPOF