IO faults proxying in LDOM environment
(Doc ID 1942045.1)
Last updated on APRIL 26, 2021
Applies to:SPARC T5-8 - Version All Versions to All Versions [Release All Releases]
SPARC M7-16 - Version All Versions to All Versions [Release All Releases]
SPARC T5-2 - Version All Versions to All Versions [Release All Releases]
SPARC M6-32 - Version All Versions to All Versions [Release All Releases]
SPARC M5-32 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
On SPARC M5-32 and M6-32 or T5 Servers, when an error is reported on the SP/SPP running ILOM or on the Host (primary domain) running Solaris, the fault is diagnosed by the respective side that reported the error, i.e.. the SP/SPP running ILOM or the host (primary domain) running Solaris.
In order to keep the FMA information in sync between the SP/SPP and the Host, the diagnosed faults are proxyed to the counterpart.
FMA Fault Proxying occurs between the primary domain any of the Hosts (up to 4 Hosts/Pdoms on Mx-32 servers) and the SP/SPP over the interconnect channel.
See SPARC M5-32 and M6-32 Servers: Interconnect, FMA Fault Proxying and LDOM configuration (Doc ID 1683087.1)
In an LDOM configuration, it's possible to assign IO resources (rootcomplexes/bus, PCIE card) to special guest domains named IO or root domain.
See the Oracle VM Server for SPARC 3.1 Administration Guide.
When an error relative to an IO resource is detected, it is reported and diagnosed by the domain owning the IO resource.
Which means that the IO fault is diagnosed on the IO or root domain.
In order to make sure that the primary domain is aware of any IO fault diagnosed on an IO or root domain, the faults are proxied between the control domain and the IO/root domain. This is done using ETM over LDC channel.
The faults are then proxied to the SP/SPP via the interconnect.
Note : when a guest domain is using services (vnet, vdisk) from a control/IO/root domain, it does not own the IO resource. Any error reported for the IO resources is still diagnosed by the respective control/IO/root domain owning the resource.
As a result, the FMA faults are in sync between the SP/SPP, control and IO/root domains.
Basic example of a configuration where the following domains are configured on the Host :
- control domain : primary
- root domain : ldg1
- IO domain : ldg2
- guest domain : ldg3
Note : no channel exists between ldg3 and primary as ldg3 is a guest domain, not owning any IO resource.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document