Skip to main content

B.3 Other Considerations


B.3 Other Considerations
  1. When a CPU memory unit (upper stage) (CMUU) is mounted on all the system boards constituting the physical partition (PPAR), if the PSB is temporarily removed from the PPAR configuration to remove the CMUU by using the dynamic reconfiguration function (PPAR DR), some of the I/O for the CMUL will not be visible when PSB is returned. If necessary, set the configuration information for the logical domains again.
  2. If an abnormal end occurs when executing the deleteboard command, do not execute the addboard command. Otherwise, the addboard command will detect an error called "internal error," resulting in an abnormal end. This command may also affect any subsequent operations.
  3. If an abnormal end occurs while the dynamic reconfiguration function is being used and while the PSB (BB) is removed with the deleteboard command, perform the following procedure:
    1. Identify the cause of the error according to the error message.

    2. Remove the cause of the error.

    3. Use the dynamic reconfiguration function and execute the deleteboard command again to delete the PSB from the PPAR configuration.

    If you fail to delete the PSB again, stop the physical partition (PPAR) and then perform the operation described either in "6.3.1 Example of Operations for Deleting a System Board Assignment" or in "6.3.3 Example of Operations for Reserving a System Board Unassignment."
  4. If an abnormal end occurs while using the dynamic reconfiguration function and executing the addboard command to add the PSB (BB), perform the following procedure or operations:
    1. Identify the cause of the error according to the error message.

    2. Remove the cause of the error.

    3. Use the dynamic reconfiguration function and execute the addboard command again to add the PSB to the PPAR configuration.

    Or, use the dynamic reconfiguration function and execute the deleteboard command to delete the PSB from the PPAR configuration, and then execute the addboard command again to add the PSB to the PPAR configuration.
    If you fail to add a PSB again with both of the above operations, stop the physical partition (PPAR) and then perform the operation described either in "6.2.1 Example of System Board Assignment" or in "6.2.3 Example of Operations for Reserving the Incorporation of a System Board."
  5. When you use the dynamic reconfiguration function to add the PSB (BB) with the addboard command or to delete the PSB with the deleteboard command, do not stop or restart Oracle VM Server for SPARC. Otherwise, the addboard command or the deleteboard command will abnormally end.
    If you restart Oracle VM Server for SPARC and then rerun the addboard command or the deleteboard command, an abnormal end may occur again.
    In this case, when the system board is added, stop the physical partition (PPAR) and then perform the operation described in "6.2.1 Example of System Board Assignment" or in "6.2.3 Example of Operations for Reserving the Incorporation of a System Board."
    When the system board is removed, stop the physical partition and then perform the operation described either in "6.3.1 Example of Operations for Deleting a System Board Assignment" or in "6.3.3 Example of Operations for Reserving a System Board Unassignment."
  6. When you use the dynamic reconfiguration function to add the PSB (BB) with the addboard command, or to delete the PSB with the deleteboard command, do not restart all the XSCFs using the rebootxscf -a command or XSCF Web. This operation may cause not only abnormal termination of the DR processing, but also abnormal stop of the physical partition due to an Oracle Solaris hangup or hardware failure with the operating physical partition, and parts replacement may therefore be required.
  7. If the assignment to the internal hard disk is deleted by using the dynamic reconfiguration function, the following message may appear and the deletion processing may fail.
# ldm remove-io /BB0/CMUL/SASHBA primary
The removal of /BB0/CMUL/SASHBA from the domain primary failed.
Error message from svc:/ldoms/agents in domain primary:
ERROR: devices or resources are busy.
  1. The above error may occur when the fmd service uses the device to be deleted. Issue the stop command to the fmd service on the domain to which the target device is assigned, check that the service has stopped and then execute the deletion processing again. In addition, restart the fmd service after the assignment of the target device is deleted.
    Use the following commands to stop/restart the fmd service.
  1. - Stopping the fmd service
# svcadm disable svc:/system/fmd:default
  1. - Checking the fmd service has stopped
  1. It may take a few minutes for the fmd service to stop.
    After issuing the stop command, check that the STATE is disabled and the service has stopped.
# svcs fmd
STATE STIME FMRI
disabled 00:00:00 svc:/system/fmd:default
  1. - Restarting the fmd service
# svcadm enable svc:/system/fmd:default
  1. If Oracle Solaris suspends or resumes with the dynamic reconfiguration function in the logical domain to which the SPARC M12-2S on-board LAN or Dual 10Gigabit Ethernet card (SP1X7HF1F, SE1X7HE3G) is assigned, an "NIC-8000-1C" error may be detected. Ignore this error because it does not affect the operation.
  1. When deleting a PSB using deleteboard, either release the LAN or I/O devices of the PSB to be deleted from the redundant configuration or change to the unused status in advance.
  1. When adding a PSB using the addboard command, either incorporate the LAN or I/O device of the PSB to be added or change the settings to enable reuse.