Table of Contents
Advertisement
DR operations work normally on M4000/M5000/M8000/M9000 server domains
running in SPARC64 VI Compatible Mode. You can use DR to add, delete or move
boards with any of the processor types, which are all treated as if they are SPARC64
VI processors. The M3000 servers do not support DR operations.
DR also operates normally on domains running in SPARC64 VII Enhanced Mode,
with one exception: You cannot use DR to add or move into the domain a system
board that contains any SPARC64 VI processors. To add a SPARC64 VI processor you
must power off the domain, change it to SPARC64 VI Compatible Mode, then reboot
the domain.
In an exception to the above rule, you can use the DR addboard(8) command with
its -c reserve or -c assign option to reserve or register a board with one or
more SPARC64 VI processors in a domain running in SPARC64 VII Enhanced Mode.
The next time the domain is powered off then rebooted, it comes up running in
SPARC64 VI Compatible Mode and can accept the reserved or registered board.
Note – Change the cpumode from auto to compatible for any domain that has or
is expected to have SPARC64 VI processors. If you leave the domain in auto mode
and all the SPARC64 VI processors later fail, the Oracle Solaris OS will see only the
SPARC64 VII+ and SPARC64 VII processors – because the failed SPARC64 VI
processors will have been degraded –and it will reboot the domain in SPARC64 VII
Enhanced Mode. You will be able to use DR to delete the bad SPARC64 VI boards so
you can remove them. But you will not be able to use DR to add replacement or
repaired SPARC64 VI boards until you change the domain from SPARC64 VII
Enhanced Mode to SPARC64 VI Compatible mode, which requires a reboot.
Setting cpumode to compatible in advance enables you to avoid possible failure of
a later DR add operation and one or more reboots.
2-184
SPARC Enterprise Mx000 Servers XSCF User's Guide • January 2012
Advertisement
Table of Contents
