Communication Channel Between The Primary Domain And The Service Processor (Sp) Might Hang (Cr 6583567) - Fujitsu SPARC Enterprise T5120 Product Notes

Sparc enterprise servers
Hide thumbs Also See for SPARC Enterprise T5120:
Table of Contents

Advertisement

2. Run power-on-self-test (POST) to identify whether this is a persistent failure
or not.
To enable POST, use the setsc (an ALOM CMT compatibility CLI command)
and configure POST to run at max level.
For example:
sc> setsc diag_mode normal
sc> setsc diag_level max
3. Power on the system.
POST tests the CPU, memory, and I/O subsystems. If the problem is persistent,
POST will fail the PCIe root complex test and disable the /SYS/MB/PCIE
component.
4. If POST detects the problem, replace the motherboard.
Communication Channel Between the Primary
Domain and the Service Processor (SP) Might
Hang (CR 6583567)
Rarely, a communication channel between the primary domain and the SP might
hang and disable communication over the channel.
Workarounds:
If the channel is used by a primary domain service or application other than the
fault management daemon (fmd), for example the LDoms Manager ldmd, you
might see warning or error messages concerning communication failures. In this
case, the channel can be brought back up by restarting the affected service or
application.
If the channel is the one used by fmd, there are no warning or error messages. fmd
will not receive ereports, and diagnosis of the errors does not occur.
If the channel is the one used by the Solaris OS to communicate with the SP, you
could see warning or error messages regarding failure to obtain the PRI, failure to
access ASR data, or failure to set LDoms variables or failure in SNMP
communication. In this case, the channel can be brought back up by resetting the
SP. If the SP is reset, restart the fmd on the primary domain. If resetting the SP
fails to bring the channel back up, then it might also be necessary to reboot the
primary domain.
If a domain crashes or a service spontaneously restarts without any associated
fault messages, you must recover as follows to minimize potential loss of error
telemetry.
Chapter 3
Known Issues
39

Advertisement

Table of Contents
loading

This manual is also suitable for:

Sparc enterprise t5220

Table of Contents