Home

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version

Contents

1. The XSCF for one of the PSBs making Problems that might occur with XCP 2250 and workarounds continued Workaround To add a PSB to a PPAR that fulfills the conditions shown on the left use one of the following methods Turn off the power to the PPAR and then execute the addboard 8 command to add a PSB After executing the addboard 8 command to add a PSB turn off the power to the PPAR turn it on again and then rebuild the PPAR Using the DR function execute the addboard 8 command to add a PSB How to restore If the error message No analytical target is not displayed Execute the poweroff 8 command to turn off the power to the PPAR and then execute the poweron 8 command to turn on the power to the PPAR If the error message No analytical target is displayed Execute the poweroff f command to forcibly turn off the power to the PPAR and then execute the poweron 8 command to turn on the power to the PPAR If there is a standby XSCF that fulfills the condition shown on the left execute the addboard 8 or deleteboard 8 command after the standby XSCF has restarted Check whether the XSCF has restarted by executing the showhardconf 8 command to confirm that the Status of the SPARC M10 45 chassis BB xx that includes the XSCF is Normal Example The XSCF at BB 02 is running XSCF gt showhardconf SPARC M10 4S Omitted BB 02 Status Normal Role Slave Ver 2220h Serial 123
2. usr sbin zpool status Notes on support for disks with an EFI GPT label The default disk label that is effective when Oracle Solaris is installed has changed from VTOC SMI to EFI GPT If you need a disk with a VTOC SMI label execute the format e command of Oracle Solaris to apply the VTOC SMI label and then install Oracle Solaris For details on the format 1M command see the Oracle Solaris Reference Manual In addition be sure to select Use a slice on the disk for the Solaris slice screen on the Oracle Solaris installation menu to ensure that the disk is VTOC SMI labeled Solaris Slices 6 0GB unknown Boot Oracle Solaris can be installed on the whole disk or a slice on the disk The following slices were found on the disk Unused Unused Unused Unused Unused rpool Unused backup Use the whole disk Use a slice on the disk Esc 2 Continue Esc 3 Back Esc 6 Help Esc 9 Quit If an EFI GPT labeled disk is used Oracle Solaris booting from a disk more than 2 TiB that is treated as a virtual disk is not supported If an EFI GPT labeled disk is used any second GPT header is not supported on a virtual disk Chapter 3 Information on Software 41 Notes on Oracle VM Server for SPARC If logical domains are reconfigured by Oracle VM Server for SPARC or if the guest domain is reset with the XSCF firmware s reset 8 command after executing the Idm unbind domain Idm bind domain command and before e
3. 03 04 Initialization Phase 05 06 Initialization Complete 07 08 09 10 11 Initialization Complete 12 13 14 15 XSCF gt RTIF2 x x x Ifyouspecify pop as the authentication 140623 002 method by executing the setsmtp 8 command e mail sending may fail even after you execute the setemailreport 8 command to enable e mail notification Workaround Do not use the poweron a command to turn on the power to multiple PPARs at the same time Use the poweron p command to turn on the power to PPARs one at a time How to restore Turn off the power to PPARs by using the following procedure and then turn it on again 1 Execute the poweroff f command to forcibly turn off the power to the PPARs that have failed to start XSCF gt poweroff y f p ppar_id 2 Confirm that the status of each PPAR specified in step 1 is Powered OFF XSCF gt showpparstatus p ppar_id Omitted 04 Powered Off Omitted 3 Turn on the power to the PPAR again XSCF gt poweron y p ppar_id When executing the setsmtp 8 command to specify an authentication method specify either smtp auth or none instead of pop Chapter 3 Information on Software 103 Table 3 13 Problems resolved in XCP 2230 continued SPARC M10 RTINo 1 4 4S Description RTIF2 x x Xx Suppose that the XSCF STANDBY LED 140623 003 on the operation panel blinks immediately after turning on the input power AC ON If the pow
4. ERROR devices or resources are busy end PSB 00 0 could not be unconfigured from PPAR ID 0 due to operating system or Logical Domains Manager error When a logical domain with a 10 Gigabit Ethernet card SP1X7HF1F for which the value of OpenBoot PROM environment variable diag switch is set to true the console displays the following warning message and the error log records Msg Device error FCode informed error WARNING pci X XXXXXX FCODE mapin doesn t match decoded register type Also executing the showstatus 8 command may show Degraded for the FRU on which the relevant PCI card is mounted If dynamic reconfiguration is performed on a physical partition which has a dual channel 10G FCoE card SP1X7FBR2F SP1X7FBS2F 7101683 7101684 7101687 7101688 mounted on it system panic may occur due to the processing of the emlxs driver If dynamic reconfiguration is performed on a physical partition which has a Dual 10Gbps FCoE card SEOX7EC12F SEOX7EF12F SG PCIEFCOE2 Q TA SG XPCIEFCOE2 Q TA 7105382 SG PCIEFCOE2 Q SR SG XPCIEFCOE2 Q SR 7105381 mounted on it system panic may occur due to the processing of the qlge driver If dynamic reconfiguration is performed on a physical partition which has a dual channel 10Gbps FCoE card SP1X7FAR2F SP1X7FAS2F 7101673 7101674 7101677 7101678 mounted on it system panic may occur due to the suspend processing of the inactivated qlcnic driver Workaroun
5. RTIF2 121113 018 RTIF2 121113 019 RTIF2 121113 021 RTIF2 121113 022 RTIF2 121113 023 RTIF2 121113 028 Problems resolved in versions prior to XCP 2050 continued SPARC M10 1 4 4 x x x x x x x x x x xX x x x x x x x x x x x x x Description While XSCF is running process down panic or watchdog timeout occurs which may cause XSCF not to be restarted after XSCF reset If you execute the showsnmp 8 command the following message may appear which means that the snmp daemon has been terminated Agent Status Disabled The error message etc redhat release not found appears while XSCF is starting When you replace an FRU with the replacefru 8 command the message configuration changed showing the configuration change may be registered more than once in the event log When the power supply of the physical partition PPAR is disconnected according to the power supply schedule may be displayed as the cause Cause in the power log If time cannot be read accurately due to a failed clock in the XSCF board an error showing a clock failure may not be recorded in the error log If the operation panel has failed or is not connected XSCF cannot be started If a CPU failure occurs while Hypervisor is running the physical partition PPAR is reset more than once and restarting of the PPAR may take time Workaround Confirm that XSCF is successfully started If it is no
6. SPARC M10 1 4 4S x x x x Description If the system board is deleted by dynamic reconfiguration of the physical partition any of the following phenomena may occur The following message is output from the logical domain and Oracle Solaris enters the panic state Fatal error has occurred in PCle fabric Oxxx Oxxx There is a hangup during the device resume processing of a logical domain and deleteboard 8 ends with an error due to a timeout If the logical domain has degraded memory because of a memory failure when dynamic reconfiguration of the physical partition is executed with the deleteboard 8 command Oracle Solaris on the domain with the degraded memory may enter the panic state When adding a PCI Expansion Unit by PCI hot plugging PHP Oracle Solaris may panic by producing the following message panic cpuX thread XXXXXXXXXxX Fatal error has occured in PCIe fabric 0xX OxXX Workaround This has been modified with SRU11 1 15 4 0 This has been modified with SRU11 1 17 5 and the patch 150817 02 for Oracle Solaris 10 Before executing dynamic reconfiguration of the physical partition check whether memory degradation has occurred from the control domain If memory degradation has occurred delete the associated memory area in advance How to check Execute ldm list devices a S memory If the resulting STATUS column displays fail the memory area has been degraded by SIZE fro
7. This phenomenon may occur when the following procedure is performed 1 While the PPAR is being reactivated due to a component failure the poweroff 8 command is executed Workaround There is no effective workaround If the current master XSCF differs from what you intended re execute the switchscf 8 command There is no effective workaround How to restore Turn off the input power to all SPARC M10 4S chassis that make up the system and then turn it on again There is no effective workaround If no message appears there are no faulty components You can continue system operation Do not execute the poweroff 8 command while the PPAR is being reactivated due to a component failure How to restore Execute the shutdown command from Oracle Solaris to power off the PPAR Example shutdown y g0 i5 Chapter 3 Information on Software 81 Table 3 8 RTI No RTIF2 140929 002 RTIF2 141008 001 RTIF2 141031 002 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 4 4S x xXx x x xX x x x x Description without the f option 2 After the PPAR is powered off upon a PPAR reactivation failure due to a component failure the poweron 8 command is executed to power on the PPAR 3 The poweroff 8 command is executed without the f option The setting of the power supply interlocking function RCIL disappears if a microSD card which is mounted on a mother
8. When a guest domain is reset by the reset 8 command a guest domain other than the specified one may be reset If you reset the guest domain execute from the guest domain and not from XSCF If SNMP is set the name of the guest domain in trap notification may be incorrect The migration with the Idm migrate domain command is not supported if the logical domain at the migration source is in the OpenBoot PROM state Perform migration with the Idm migrate domain command after changing the logical domain at the migration source to either of the following states CR 15858731 Stopped state bound state State where Oracle Solaris is running Be sure to start the ldmd service sve ldoms ldmd default of the control domain A boot disk with an EFI GPT disk label is supported by the following systems SPARC M10 systems to which XCP 2230 or later is applied and SPARC T series or M series systems to which SysFW 8 4 or SysFW 9 1 or later is applied However SPARC M10 systems to which XCP 2221 or earlier is applied do not support a boot disk with an EFI GPT disk label Therefore do not migrate to a SPARC M10 42 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 system to which XCP 2221 or earlier is applied from a SPARC M10 system to which XCP 2230 or later is applied or a SPARC T series or M series to which SysFW 8 4 or SysFW 9 1 or later is applied You can determine whether the boot disk is EFI GPT labele
9. There is no effective workaround Check for power errors if the error log of XB XB interface link up error was registered Ignore the error log for XB XB interface link up error if a power error has occurred There is no effective workaround There is no effective workaround Power off the input power supply and then power it on again There is no effective workaround Execute the showboards 8 command to check that the Pwr field of the relevant PSB is set to n If the field is set to y execute the showboards 8 command every few minutes to check that the field changes to n Do not switch an XSCF by using the switchscf 8 command while a PPAR is being powered on When power supply interlocking is not necessary Disable power supply interlocking with setremotepwrmgmt c disable and then delete the power supply interlocking setting with the clearremotepwrmgmt 8 command When power supply interlocking is necessary If the system has multiple PPARs create a management file for power supply interlocking by specifying a PPAR ID as a SubNodelID and then register the power supply interlocking setting with setremotepwrmgmt c config Chapter 3 Information on Software 51 Table 3 8 RTI No RTIF2 130516 002 RTIF2 130516 004 RTIF2 130516 006 RTIF2 130702 001 RTIF2 130710 001 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 4 4S X D
10. There is no effective workaround if any hardware failure occurs while executing DR How to restore Check the status of the system board PSB using the showboards 8 command Execute the addboard 8 or deleteboard 8 command after that 54 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 RTI No RTIF2 131213 003 RTIF2 131213 010 RTIF2 131213 011 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 xX Description While executing the poweroff 8 poweron 8 reset 8 command on a physical partition if the addboard 8 or the deleteboard 8 command of the DR feature is executed on another physical partition to add or remove a system board PSB the addboard 8 or deleteboard 8 command may detect timeout and terminate abnormally When the firmware of the PCI Expansion Unit is updated with the ioxadm c update command process down may occur at the XSCF firmware When a SPARC M10 4S or a crossbar box is added using the addfru 8 command the following message is output and the addition may fail Warning 036 Failed to find BB x The BB ID setting and or the cable connections of the BB x will be wrong Please confirm the BB ID setting and the cable connections Do you want to try to add BB x again a add c cancel Workaround Do not execute the addboard 8 or deleteboard 8 command while the poweroff 8 poweron 8
11. domain is Oracle Solaris 10 As a result of executing ldm list domain o memory primary the RA real address is greater than 0x200000000000 32 TB Workaround This has been modified with the patch 148888 03 for Solaris 10 Perform the following procedure 1 Execute ldm list domain o memory primary to display the value of SIZE 2 Execute Idm start reconf primary to enter the delayed reconfiguration mode 3 Execute Idm remove memory 256M primary to reduce the assigned memory 4 Execute ldm set memory primary to return the assigned memory back to the original size 5 Restart the Oracle Solaris of the control domain 6 Execute Idm list domains o memory primary to confirm that the RA is smaller than 0x200000000000 7 Execute Idm add spconfig to save the configuration information to the XSCF Problems resolved in Oracle Solaris 11 2 The following table lists the problems resolved in Oracle Solaris 11 2 You might encounter them in supported releases earlier than Oracle Solaris 11 2 Problems resolved in Oracle Solaris 11 2 SPARC M10 1 4 4S x Description If you try to access via telnet or ssh a domain where 8000 GB about 7 8 TB or greater memory is mounted the following message appears on the destination control domain console and the access fails For ssh error dev ptmx Not enough space error session_pty_req session 0 alloc failed For telnet telnetd open dev ptmx Not enough
12. screen of XSCF Web you need to note the following A PSB cannot be specified if it has already been assigned to another physical partition PPAR Workaround If the reason for the high load is the L2 loop eliminate the root cause by reviewing the network connection etc How to restore To clear the failure mark on PSU turn off the input power and then turn it back on There is no effective workaround Please ignore this message There is no effective workaround There is no effective workaround For the setting use the setpcl 8 command of the XSCF shell Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 13 Problems resolved in XCP 2230 continued SPARC M10 RTINo 1 4 4S Description RTIF2 x Suppose that the system is made up of 140606 007 multiple physical partitions PPARs consisting of multiple SPARC M10 45 chassis If you turn on the power to multiple PPARs at the same time for the first time after turning on the input power or resetting the XSCF the following event may occur A PPAR ID error is registered the self diagnosis test POST on some PPARs is not completed and these PPARs fail to start You can confirm this event by executing the showpparstatus command Example Only PPAR 4 is indicated with Initialization Phase and fails to complete POST processing XSCF gt poweron a XSCF gt showpparstatus a PPAR ID PPAR Status 00 Initialization Complete 01 02
13. temporary warning message If event 4 occurs Turn off the input power supply of the system and then back on AC OFF ON to recover The execution results can be displayed if the showcodactivation 8 command is executed after the execution of the restoreconfig 8 or restorecodactivation 8 command is completed Chapter 3 Information on Software 169 Description If the XCP firmware version is XCP 2041 XCP 2042 or XCP 2043 SPARC M10 4S cannot be replaced by using the replacefru 8 command in a system with more than one SPARC M10 4S Problems resolved in versions prior to XCP 2050 continued Workaround Perform cold replacement replacement performed with the input power off or update the XCP firmware version to XCP 2044 or later before performing replacement Problems with Oracle Solaris and Workarounds This section describes problems with Oracle Solaris and workarounds for each version Problems that might occur in any versions of Oracle Solaris and workarounds The following table lists the problems that might occur in any versions of Oracle Solaris being supported and workarounds for them Table 3 25 SPARC M10 RTI No 1 4 4S RTIF2 x 130612 001 aS Table 3 26 SPARC M10 Bug 1 4 4S 15813959 x xX X 15813960 7196117 170 Description When a PCI expansion unit is added by hotplug 1M in a SPARC M10 system devices on the PCI expansion unit are not recognized Problems that might
14. 121204 004 Description When you replace the CPU memory unit lower CMUL or motherboard unit MBU the XSCF user account information may be deleted To recover the XSCF user account information you need to use the restoreconfig 8 command to restore the information saved by the dumpconfig 8 command The restoredefaults 8 cannot initialize the following information The setting information remains as it is Timezone for XSCF Server certificate for HTTPS When you enable and disable the power supply interlocking of RCIL and then enable it again the power supply interlocking of ETERNUS DX80 DX90 DX410 DX440 DX8100 DX8700 S2 may not work The dynamic resource management software ServerView Resource Orchestrator sometimes fails to register a server to be monitored If a node of PRIMECLUSTER stops node switching does not occur automatically When you set or change environment variables of OpenBoot PROM by setenv or nvramrc of OpenBoot PROM or by the eeprom 1M or ldm set var commands of Oracle Solaris the setting or changes may not be retained after recycling the power supply to the system When you enable the auto boot function of the guest domain by the setpparmode 8 command of XSCF and then start the control domain and the guest domain simultaneously you may encounter the situation where the following error message is recorded and Oracle Solaris cannot be started in the guest domain Code 200000
15. BB xx was stopped by power failure Power failure date is yyyy mm dd hh mm ss When the flashupdate 8 command is executed only occasionally XSCF may not start up If a failure occurs in the PCI Expansion Unit all the domains that are situated in the physical partition PPAR that is connected to the PCI Expansion Unit are shut down Workaround There is no effective workaround Do not execute the poweron 8 or the reset 8 command while the XSCF BB control cable is disconnected How to restore If hardware failure had occurred execute power off and on on the physical partition If XSCF is performing retrial operations execute the poweroff f p ppar id command to forcibly power off the physical partition After that power it on There is no effective workaround There is no effective workaround Contact a field engineer if this problem occurs There is no effective workaround Problems resolved in XCP 2091 The following table lists the problems resolved in XCP 2091 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 18 RTI No RTIF2 140117 001 Table 3 19 RTI No RTIF2 130219 003 RTIF2 130219 007 Problems resolved in XCP 2091 SPARC M10 1 4 4S x x x Description When the setsnmp 8 setsnmpusm 8 setsnmpvacm 8 commands or XSCF Settings Service SNMP XSCF Settings Service SNMP Security on XSCF Web is execute
16. Chapter2 XCP 2250 Related Information 17 Should this occur turn off the input power to the replaced installed SPARC M10 4S Subsequently using the maintenance menu replace the CPU memory unit lower CMUL or install the SPARC M10 45 again SPARC M10 4S From XCP 2090 onwards automatic synchronization of firmware versions between chassis when replacement of CPU Memory Unit lower CMUL or XSCF unit expansion of SPARC M10 4S or crossbar box is performed in off state of the input power supply without using the maintenance menu has been enabled After replacement or expansion of components if the XSCF firmware update now in progress BB xx please wait for XSCF firmware update complete message is output after logging in to the master XSCF the XCP firmware is in the process of being updated automatically Automatic synchronization of XCP firmware versions can be confirmed by the XCP firmware version synchronization completed message which is output by the showlogs monitor showlogs event or showmonitorlog command Do not execute the following until the firmware update is complete Turn off the input power supply Execute the poweron 8 command Execute the testsb 8 command Execute the diagxbu 8 command Execute the getflashimage 8 or the flashupdate 8 command Notes on CPU Activation If the XSCF setting information is initialized by executing the restoredefaults 8 command in XCP 2032 or earlier t
17. Chapter2 XCP 2250 Related Information 31 perform the setting again Restrictions At this point no mem to be set with the s option of the setpcl 8 command is not supported Alive monitoring between the XSCF and a Hypervisor is not supported Alive monitoring between the XSCF and a Hypervisor cannot be enabled disabled even by using the setpparmode 8 command SPARC M10 4S Suppose that the XSCF was switched while connecting to the control domain console in the SPARC M10 4S5 that is composed of more than two chassis In that case connection to the control domain console may not be established until all the SPARC M10 4S chassis have been restarted if an attempt has been made to reconnect the control domain console to the switched master XSCF If all XSCFs have not been restarted due to an error in the XSCF establish a connection to the control domain console again Replace a failed XSCF or CPU memory unit lower CMUL if a connection cannot be established to the control domain console SPARC M10 4S The poweroff 8 and reset 8 commands may not be executed normally if all XSCF have not been restarted due to an error in a XSCF in the SPARC M10 4S that is composed of more than two chassis To disconnect the power of a physical partition PPAR login to the control domain of the PPAR and execute the shutdown 1M command on Oracle Solaris Then disconnect the power of the PPAR using the poweroff f command on the XSCF firmware
18. Even if two default gateways are set up using the setroute 8 command connection from other networks is possible only on either XSCF LAN 0 or XSCF LAN 1 Workaround There is no effective workaround How to restore Replace the MBU Among XSCF LAN 0 and XSCF LAN 1 use the IP address of the gateway that can be connected to 94 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 10 Problems resolved in XCP 2240 continued SPARC M10 RTINo 1 4 4S Description Workaround RTIF2 x In order to configure the XSCF startup There is no effective workaround 140515 001 mode function after changing the startup mode with the xscfstartupmode 8 command or setting the operation panel mode switch to Locked or Service if the rebootxscf 8 command is executed to reset XSCF the new startup mode gets enabled However under normal circumstances the configuration of the startup mode is not enabled when XSCF is reset using the rebootxscf 8 command It is enabled only when the input power of the system is turned off on AC OFF ON This state can be confirmed by the xscfstartupmode d command as follows Example When startup mode is set to fast after setting the operation panel mode switch to Locked XSCF gt xscfstartupmode d Setting Mode normal Current Mode normal XSCF gt xscfstartupmode m fast XSCF gt rebootxscf a XSCF gt xscfstartupmode d Setting Mode fast need AC OFF ON Curren
19. For any previously set time zone that the system cannot use anymore the XSCF switches from this unusable time zone to Coordinated Universal Time UTC and operates in UTC When the set time zone operates in UTC execute the settimezone c settz a command and check the settable time zones If the time zone list does not have a set time zone set a time zone again Notes on power supply interlock function RCIL Do not register the same node with multiple power supply interlocking groups If power supply interlocking is performed by registering a single node with multiple power supply interlocking groups the operation may not be as intended With the setremotepwrmgmt 8 command you cannot confirm whether a single node is registered with multiple power supply interlocking groups When creating or modifying a power supply interlocking group management information file take care not to cause overlaps Do not register an I O node with multiple power control groups If the same I O node is set with multiple power supply interlocking groups and both of the conditions below are met the I O node is turned on and off alternately setremotepwrmgmt c enable is executed and the power supply interlocking function is enabled There is a power control group in which one or more host nodes are on and there is a power control group in which all the host nodes are off If you accidentally register an I O node with multiple power control group
20. I O domain is started a PCI Express correctable error may occur and cause degradation of the PCI expansion unit at the next reboot of Oracle Solaris Chapter 7 Information on PCI Expansion Unit Hardware Workaround The display of this error message does not affect the operation If the error message is output restart the PPARs or I O domain or reinstall the PCI expansion unit by PCI hot plug PHP 209 Problems resolved in version 1100 of the PCI expansion unit firmware The following table lists the problems resolved in version 1100 of the PCI expansion unit firmware Table 7 9 SPARC M10 RTI No 1 4 4S RTIF2 x x x 130703 005 RTIF2 x x x 130703 006 Description When physical partitions PPARs or the I O domain is started the PCIe card or link board mounted in the PCI expansion unit may be erroneously detected as having an error Example of PCIe card message FRU BB 0 PCI 3 PCIBOX 1234 PCI 3 Msg PCICARD failed Example of link board message FRU BB 0 PCI 0 PCIBOX 1234 LINKBD Msg TWI access error If the serial number of the PCI expansion unit that is displayed upon execution of the ioxadm v list command consists entirely of 0 s 0000000000 the following occurs Hardware errors detected after the input power to the PCI expansion unit is turned on but before the power to the first physical partition PPAR is turned on are not registered as errors Problems resolved in version 1100 of
21. If the setting specifying the XSCF as an NTP client is enabled 1 Disconnect the LAN cable from the XSCF LAN port and then perform replacement N After the XSCF starts connect the serial cable to the serial port Do not connect the LAN cable at this time e gt Execute the setdate 8 command to set the XSCF time After this the XSCF is reset 4 Connect the LAN cable to the XSCF LAN port 5 Execute the version command to confirm the firmware version information If the XCP firmware version does not match that used before the replacement update the firmware For details see 16 1 3 Updating firmware in the Fujitsu M10 SPARC M10 Systems System Operation and Administration Guide If you replace the microSD card the CMU firmware versions do not match However you do not need to perform an update The following example shows 02 01 0001 1 in the execution example as the CMU firmware version of the current XCP and 02 00 0006 2 in the execution example as the CMU 16 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 firmware version of the reserve XCP Thus you can see that the CMU firmware versions do not match XSCF gt version c xcp v BB 00 XSCF O Master XCPO Current 2011 CMU 02 01 0001 1 POST 1 2040 OpenBoot PROM 4 34 0 1 2 0 Hypervisor z 0 20 17 XSCF 02 01 0002 XCP1 Reserve 2011 CMU 02 00 0006 2 POST z dy 3s 0 OpenBoot PROM 4 34 0 1 0 5 Hyper
22. a PCI Express correctable error may occur and cause degradation of the PCI expansion unit at the next reboot When you install a PCI expansion unit with PCI hot plug PHP the PCI expansion unit may not be recognized Workaround This is just a display problem and does not affect operation When using PHP execute cfgadm c configure instead of cfgadm c connect If there a fault error message is output after installing a PCI expansion unit with PHP reinstalled the PCI expansion unit If the PCI expansion unit is not recognized after installing it with PHP reinstall the PCI expansion unit Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 7 1 SPARC M10 RTI No 1 4 4s RTIF2 x x x 130724 002 RTIF2 x x x 130724 003 Description If you install a 6Gbps SAS card in the PCI expansion unit with the PCI hot plug PHP linkup with PCI Express 8lane may not be successful and Speed may be displayed as 5 0GTx4 or 5 0GTx2 in response to executing the prtdiag 1M command prtdiag output example SYS PCIO PCIE LSLsas pciex1000 72 LSI 2008 5 0GTx2 pci 8000 pci 4 pci 0 pci 8 pci 0 pci 0 pci 0 pci 1 pci 0 pci 8 LSI_sas 0 The following error may be registered for the PCI cards mounted in slots 6 7 10 and 11 of the PCI expansion unit when the physical partitions PPARs are started Error message example FRU MBU PCI 0 PCIBOX 0000 PCI 7 Msg PCICARD failed Probl
23. ne vous conf re aucun droit et aucune licence expr s ou tacites concernant le produit ou la technologie auxquels il se rapporte Par ailleurs il ne contient ni ne repr sente aucun engagement de quelque type que ce soit de la part d Oracle ou de Fujitsu Limited ou des soci t s affili es de l une ou l autre entit Ce document ainsi que les produits et technologies qu il d crit peuvent inclure des droits de propri t intellectuelle de parties tierces prot g s par le droit d auteur et ou c d s sous licence par des fournisseurs a Oracle et ou ses soci t s affili es et Fujitsu Limited y compris des logiciels et des technologies relatives aux polices de caract res Conform ment aux conditions de la licence GPL ou LGPL une copie du code source r gi par la licence GPL ou LGPL selon le cas est disponible sur demande par I Utilisateur Final Veuillez contacter Oracle et ou ses affili s ou Fujitsu Limited Cette distribution peut comprendre des composants d velopp s par des parties tierces Des parties de ce produit pourront tre d riv es des syst mes Berkeley BSD licenci s par l Universit de Californie UNIX est une marque d pos e de The OpenGroup Oracle et Java sont des marques d pos es d Oracle Corporation et ou de ses affili s Fujitsu et le logo Fujitsu sont des marques d pos es de Fujitsu Limited SPARC Enterprise SPARC64 le logo SPARC64 et toutes les marques SPARC sont utilis es sous licence et sont des marqu
24. not exist devices virtual devices 100 channel devices 200 virtual channel 0 hvctl Workaround This has been improved with SRU11 1 16 4 0 and patch 150011 03 for Oracle Solaris 10 We recommend that you do not configure the system with a single PPAR but divide it into multiple PPARs and then configure guest domains in each PPAR Using the recommended configuration described above not only mitigates the described phenomenon but also helps improve fault tolerance If a virtual network switch vsw is configured you can reduce the time for binding by half by setting inter vnet link to off For notes when inter vnet link is set to off see Oracle VM Server for SPARC Administration Guide or Oracle VM Server for SPARC Release Notes It has been modified with SRU11 1 14 5 0 and the Oracle Solaris 10 patch 150400 07 It has been modified with SRU11 1 19 6 0 and the Oracle Solaris 10 patch 150840 04 How to restore After confirming that the device file in question exists restore the Idoms ldmd service using the svcadm 1M command Is I devices virtual devices 100 channel devices 200 virtual channel 0 hvctl 1 root sys 148 2048 Jan 21 20 08 devices virtual devices 100 channel devices 200 virtual channel 0 hvctl svcadm clear Idmd Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 29 Bug 17709858 17777004 18055846 Problems resolved in Oracle Solaris 11 2 continued
25. perform binding for the guest domains It takes approximately the number of guest domains for which binding has already been performed 1 x 6 10 seconds to perform binding Therefore if there are no domains for which binding has been performed and binding is performed for the guest domains one by one through the Idm bind domain command the required time is obtained by summing the times taken to perform binding for all of them If the guest domain is Oracle Solaris 11 1 and SRU11 1 9 or later is applied to it or if the guest domain is Oracle Solaris 10 and 150400 01 or newer is applied to it system panic may occur when conducting live migration or dynamic reconfiguration of physical partitions Messages like the following are output to the console at the time of starting Oracle Solaris and the lIdoms ldmd service is put to maintenance mode Example of the messages Jan 20 16 01 37 sve startd 11 svc Idoms Idmd default Method opt SUNWIdm bin ldmd_start failed with exit status 96 Jan 20 16 01 38 sve startd 11 ldoms Idmd default misconfigured transitioned to maintenance see svcs xv for details At this time messages like the following will be registered to the log file var svc log Idoms ldmd default log of the ldoms ldmd service Example of the messages Jan 21 20 08 55 Executing start method opt SUNWldm bin Idmd_start Idmd cannot communicate with the hypervisor as the required device does
26. reset 8 command is being executed elsewhere There is no effective workaround if DR is executed while also executing power supply operations on another physical partition How to restore Execute the following 1 Execute the showboards 8 command 2 Check the status of Pwr Conn Conf Test of the system board PSB to confirm the end of power operations End of power on reset The status of Pwr Conn Conf Test is y y y passed respectively End of power off The status of Pwr Conn Conf is nn n respectively 3 Re execute the addboard 8 or the deleteboard 8 command There is not effective workaround Re execute the ioxadm c update command to update the PCI Expansion Unit firmware again When the following maintenance menu is output after executing the addfru 8 command input power on the SPARC M10 4S or the crossbar box to be added and execute the next operation step 2 after 20 minutes Please execute the following steps 1 After the added device is connected with the system please turn on the breaker of the BB x 2 Please select f finish How to restore Input a in response to the a add c cancel message and re execute the addfru 8 command Chapter 3 Information on Software 55 Table 3 8 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 RTI No 1 4 4S Description Workaround RTIF2 x After replacing SPARC M10 with the There is no effective workaround 13
27. x 130903 002 142 Problems resolved in XCP 2070 continued Description When Oracle Solaris is operating if you change the SNMP setting with the setsnmp 8 command the following phenomena may occur 1 A part of the data such as the XCP version number is not output as a result of the prtpicl v and prtdiag v commands 2 For var adm messages of Oracle Solaris the following warning message is output PICL snmpplugin cannot fetch object value If you log in to the XSCF Web from the master XSCF when the standby XSCF is in either the maintenance or input power off state a dialog starting with Cannot communicate with BB xxx that indicates a non breaking communication error is output If the firmware is updated while a logical domain is operating in a system consisting of multiple SPARC M10 4S units the master XSCF may not switch to a standby XSCF causing the firmware update to fail In a system consisting of multiple SPARC M10 4S units it may take longer than usual from the time a physical partition PPAR is turned on until the Power On Self test POST starts For example for a 2BB configuration POST usually starts after about 10 minutes but it may take 20 minutes or longer Workaround There is no effective workaround If 1 occurs Perform recovery by using the following procedure 1 End the prtdiag command with Ctrl C 2 Wait for about 30 minutes and let an SNMP timeout occu
28. 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 0000 666c6173 68757064 6174652e Xxxxxxxx 00000000 00000000 0000 where xxxxxxxx is indefinite The showlogs event command displays the XCP update has been completed event log How to restore Re execute the flashupdate 8 command In case of SNMPv3 do not register a trap host name with the setsnmp 8 command that contains a colon If such a trap host name has already been registered use the following command to remove the trap host name setsnmp remv3traphost u username p port_nunber trap_host_name In such a case be sure to specify a port number If the port number is not specified when removing a trap host name that includes a colon the Entry does not exist message is displayed and the trap host name is not removed The port number specified at the time of removal should be the one which is not wrongly displayed by the showsnmp 8 command but the one specified at the time of registration 62 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 SPARC M10 RTI No 1 4 4S RTIF2 x 140304 004 RTIF2 x 140304 005 Description In case of a SPARC M10 4S that is attached to cross bar box if XSCF failure occurs on a portion of chassis when the physical partition PPAR is in the powered on state the follow symptom may occur Symptom 1 When the poweroff 8 command is executed the
29. 003 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 4 4S X Description If an error occurs in the DC DC converter of a crossbar unit XB XB interface link up error is erroneously registered instead of the correct error log of LSI detected errors with power subsystem failure If the poweroff 8 command is executed in the system that has more than one physical partition PPAR it takes time for the processing because the power of the PPARs is disconnected one by one Depending on the system configuration it may take about one hour When you turn on the input power supply in SPARC M10 1 READY LED of XSCF remains blinking and the system may not start The diagnosis of the system board may fail during the power off of the system board PSB by executing the diagxbu 8 or testsb 8 command displaying the following message Warning 010 An internal error has occurred The switching of an XSCF may fail if the XSCF is switched by executing the switchscf 8 command while a physical partition PPAR is being powered on If a physical partition PPAR is powered on in the system that satisfies all the following conditions other PPAR may also be powered on The power supply interlocking is enabled with the setremotepwrmgmt 8 command Anode is created whose SubNodelD is not set in a power supply interlocking management item Multiple PPARs are configured Workaround
30. 0224 For details see see the Oracle website relating to the following Critical Patch Updates In SPARC M10 4 M10 4S power supply interlocking by RCIL does not work Moreover if the following RCIL related commands are executed the Controller response timeout error message is output and the command ends abnormally setremotepwrmgmt 8 showremotepwrmgmt 8 getremotepwrmgmt 8 clearremotepwrmgmt 8 Workaround Update the XCP firmware to XCP 2221 or later There is no effective workaround Operate power supply of the target SPARC M10 systems and I O devices manually Problems resolved in XCP 2220 The following table lists the problems resolved in XCP 2220 Chapter 3 Information on Software 107 Table 3 15 SPARC M10 RTI No 1 4 4S RTIF2 x x 130806 001 RTIF2 X 140212 002 108 Problems resolved in XCP 2220 Description Suppose that the XSCF is configured as an NTP client and is synchronized with the upper level NTP server in time If you replace one of FRUs listed below for each model and then power on the physical partition PPAR the Oracle Solaris time may become January 1 2001 SPARC M10 1 Motherboard unit MBU PSU backplane PSUBP SPARC M10 4S crossbar backplane unit XBBPU XSCF unit XSCFU You can determine the occurrence of this problem by executing the showdateoffset 8 command If an extremely large value 400 million seconds or more is displayed in Domain Date O
31. 05 0002 XCP1 Current 2052 XSCF 02 05 0002 XBBOX 81 XSCF 0 Standby XCPO Current 2052 XSCF 02 05 0002 XCP1 Reserve 2052 XSCE 02 05 0002 BB 00 XSCF 0 XCPO Reserve 2042 CMU 02 05 0002 POST 1 43 0 OpenBoot PROM 4 34 0 1 22 0 Hypervisor 0 27 8 XSCE 02 04 0000 XCP1 Current 2052 CMU 02 05 0002 POST 1 43 0 OpenBoot PROM 4 34 0 1 22 0 Hypervisor 0 27 8 XSCF 02 05 0002 If the input power is turned off AC OFF while the XSCF is processing large amounts of data only occasionally XSCF may not start up when the input power in turned on AC ON again The OID information of scfPsbInfo in the definition file of XSCF extension MIB is not updated even if the information of the system board PSB is updated Workaround There is no effective workaround How to restore Specify the BB ID of the crossbar box XBBOX or of the SPARC M10 4S BB which was not updated to the rebootxscf b BB ID command and execute it to reset the XSCF of the specified chassis There is no effective workaround Contact a field engineer if this problem occurs Restart the snmp daemon using any of the setsnmp 8 setsnmpusm 8 or the setsnmpvacm 8 commands or reset XSCF 58 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 RTI No RTIF2 140212 005 RTIF2 140212 007 RTIF2 140212 008 RTIF2 140212 011 RTIF2 140212 012
32. 1 Includes cases in which a link card link cable management cable or link board is replaced Notes on dual power feed setting The power supply unit of the SPARC M10 system is redundantly configured Enabling or disabling the dual power feed function with the setdualpowerfeed 8 command does not affect the behavior of a redundantly configured system Therefore when the display results of the showdualpowerfeed 8 and showhardconf 8 commands which are dependent on the setting of the setdualpowerfeed 8 command also fall under any of the following conditions the behavior of the redundantly configured system is not affected The showhardconf 8 command displays Power_Supply_System Dual when the showdualpowerfeed 8 command displays Dual power feed is enabled The showhardconf 8 command displays Power_Supply_System Single when the showdualpowerfeed 8 command displays Dual power feed is disabled The system administrator can use this setting function as a memo for determining whether the power supply unit has a dual power feed configuration Notes on Active Directory If Active Directory is enabled and you try login via telnet inquiry to the second and subsequent alternative servers may time out causing the login to fail Ifthe value set by the timeout operand of the setad 8 command is small and you log in to the XSCF the user privilege may not be assigned to you In this case increase the timeout setting value a
33. 3openss Notes on remote maintenance service Note Enhanced Support Facility ESF and Remote Customer Support System REMCS are supported only for SPARC M10 systems sold within Japan by Fujitsu This section describes notes when using the remote maintenance service See Enhanced Support Facility User s Guide for REMCS for how to set and use REMCS Before setting the remote maintenance service To use the remote maintenance service with SPARC M10 Systems you must perform settings for the REMCS agent function by using XSCF Web In addition the REMCS agent uses timezone information of XSCF Perform the following settings in advance with the XSCF shell Setting necessary for using the XSCF Web such as enabling the HTTPS setting Setting the timezone for XSCF After completing the above settings perform settings for the REMCS agent function by using the XSCF Web See Fujitsu M10 SPARC M10 Systems System Operation and Administration Guide for details of the XSCF Web settings and timezone settings Timezone for the REMCS agent function The REMCS agent uses the timezone currently set for the system For this reason when you change the system timezone with XSCF set the periodical connection schedule again to update the information of REMCS center Chapter 3 Information on Software 47 Notes on SNMP When using the SNMPv3 agent after setting up the authentication protocol and the encryption protocol using the setsnmp 8 c
34. Abnormalities may occur such as an XSCF firmware error or reset depending on your USB memories In such a case immediately stop using the USB memory The saved data contains information on the system If you use the USB memory consideration should be made for the management of the USB memory in which the data is saved for security reasons 193 Restrictions on replacing crossbar box Replacement of a crossbar box using the replacefru 8 command is not supported at present To replace a crossbar box perform the following procedure 1 Execute the showhardconf command to confirm that the crossbar box to be replaced is not the master chassis The crossbar box indicated as Role Master is the master chassis XSCF gt showhardconf XBBOX 80 Status Normal Role Master Ver 2038h Serial 2111206001 2 If the crossbar box to be replaced is the master chassis execute the switchscf command to switch it to standby XSCF gt switchscf y t Standby The master XSCF is switched Log in to the XSCF again 4 Power off the physical partition PPAR that uses the crossbar box and then power off the crossbar box to be replaced Confirm that the Power LED on the operation panel of the crossbar box is turned off 5 Disconnect the input power supply to the crossbar box to be replaced and replace it Note Although error logs for the crossbar box to be replaced are registered when the input power supply is disconnected ignore all of th
35. Case of symptom 2 Forcibly power off the PPAR using the poweroff f command Change the configuration of the direct 1 O feature with the setpciboxdio 8 command only after removing the degraded system board from the physical partition with the deleteboard 8 command Example XSCF gt deleteboard c unassign 01 0 After changing the configuration of the direct I O feature assign the system board to the PPAR with the addboard 8 command and then mount the system board onto the PPAR following the maintenance procedure Example XSCF gt addboard c assign p 0 01 0 Meanwhile from XCP 2210 onwards this problem can be solved by performing maintenance on the degraded chassis by the replacefru 8 command In such a case the above procedure is unnecessary Chapter 3 Information on Software 63 Table 3 8 RTI No RTIF2 140304 006 RTIF2 140304 007 RTIF2 140402 001 RTIF2 140402 003 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 X X X Description No error log is registered when any of the following occurs the power supply PSU fails due to PSU shortage power off started PSU shortage and the wrong PSU is installed if the errors re occur on the PSU of the same chassis after active replacement or hot replacement of the PSU by the replacefru 8 command When the power supply unit PSU fails due to any of the following errors and after a
36. Oracle Solaris 10 1 13 Oracle Solaris 11 2 Oracle Solaris 11 1 Oracle Solaris 10 1 13 Oracle Solaris 11 2 Oracle Solaris 11 1 Oracle Solaris 10 1 13 SPARC M10 4S Direct inter chassis connection SPARC64 X 3 7 GHz SPARC64 X 3 0 GHz 2210 or later 2031 or later Oracle Solaris 11 2 Oracle Solaris 11 1 Oracle Solaris 10 1 13 6 Oracle Solaris 11 2 Oracle Solaris 11 1 Oracle Solaris 10 1 13 6 SPARC M10 45S Connection through crossbar box Required packages 4 Required products 5 system Idoms 1 system ldoms ldomsmanager 2 system Idoms 1 system ldoms ldomsmanager 2 Oracle VM Server for SPARC 3 0 or later 3 system Idoms 1 system ldoms ldomsmanager 2 system Idoms 1 system ldoms ldomsmanager 2 Oracle VM Server for SPARC 3 0 or later 3 system Idoms 1 system ldoms ldomsmanager 2 system Idoms 1 system ldoms ldomsmanager 2 Oracle VM Server for SPARC 3 0 or later 3 system Idoms 1 system ldoms ldomsmanager 2 system Idoms 1 system ldoms ldomsmanager 2 Oracle VM Server for SPARC 3 0 or later 3 system Idoms 1 system ldoms ldomsmanager 2 system Idoms 1 system ldoms ldomsmanager 2 Oracle VM Server for SPARC 3 0 or later 3 7 8 system Idoms 1 system ldoms ldomsmanager 2 system Idoms 1 system ldoms ldomsmanager 2 Oracle VM Server for SPARC 3 0 or later 3 7 8 2 Fujitsu M10 SPARC M10 Systems Prod
37. PCIe card are registered upon executing the showlogs event command The number of event logs is calculated as follows depending on the event type Event of PCle card insertion 2 Event other than PCle card insertion 1 For example if a PCle card is repeatedly inserted and removed four times eight message lines are displayed However the number of registered event logs is 12 which is calculated by multiplying three events by four This applies to this case Example of PCle card insertion removal XSCF gt showlogs event Dec 20 10 49 59 JST 2013 Attach operation BB 0 PCI 1 PCIBOX 3001 PCI 1 Dec 20 10 49 59 JST 2013 Detach operation BB 0 PCI 1 PCIBOX 3001 PCI 1 Omitted Six or more logs are registered by the PCI expansion unit firmware the first byte in the third field of Code is 11 upon executing the showlogs error command Chapter 7 Information on PCI Expansion Unit Hardware 205 Example of log registration by PCI expansion unit firmware XSCF gt showlogs error Date Jun 06 10 55 28 JST 2014 Code 80000400 00d4000000f 0000f 1100002a0000000000000000 AA Status Alarm Occurred Jun 06 10 55 28 028 JST 2014 FRU BB 0 PCI 1 PCIBOX 3001 PSU 0 Msg AC FAIL Date Jun 06 10 55 34 JST 2014 Code 10000400 00d4000000f 0000fFF 1100002b0000000000000000 Status Information Occurred Jun 06 10 55 34 479 JST 2014 FRU BB 0 PCLI 1 PCIBOX 3001 PSU 0 Msg PSU RECOVERY Omitted Problems re
38. PPARs are being powered on There is no workaround for errors that are detected at power on after the addition Making the following setting prevents the error detection that occurs every time the PPAR is powered on or the control domain is rebooted 1 After starting Oracle Solaris execute the Idm rm io command to delete the PCIe root complex of the added CMUU from the configuration of the control domain 2 Execute the Idm add spconfig command to save the constructed logical domain configuration to the XSCF There is no effective workaround How to restore Turn off and then turn on the input power supply AC OFF ON to every SPARC M10 4S or execute the replacefru 8 command to perform pseudo replacement replacement work without replacing any parts of the SPARC M10 4S that does not start 52 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 RTI No RTIF2 130711 003 RTIF2 130802 003 RTIF2 130919 001 RTIF2 131001 002 RTIF2 131112 001 RTIF2 131112 013 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 4 4S X Description Before active replacement of the XSCF unit of the crossbar box is completed the replacefru 8 command is completed normally When you replace the XSCF unit of the crossbar box by using the replacefru 8 command the command is completed normally but the following error log may be reg
39. Problems resolved in XCP 2210 continued SPARC M10 RTI No 1 4 4S Description RTIF2 x x x If either of the following events occurs 140605 005 the ttydm process may fail causing the XSCF to be reset The console 8 command is executed to connect to the control domain console after one of the following events occurs A large amount of data is output to the screen of the domain console and the console 8 command terminates when the XSCFs for multiple SPARC M10 4S chassis are reset The console 8 command is executed to forcibly connect to the control domain console If the ttydm process fails the following error log is registered Example XSCF gt showlogs error v Date Dec 01 22 08 13 JST 2013 Code 20000000 00fcff00b0000000Ff 010400010000000000000000 Status Notice Occurred Dec 01 22 08 04 886 JST 2013 FRU FIRMWARE XBBOX 80 XSCFU Msg SCF process down detected Diagnostic Code 00000000 00000000 0000 50000000 00000000 0000 00000000 00000000 0000 74747964 6d2e3239 37302e62 7a320000 00000000 00000000 0000 If the first five bytes on the fourth line in Diagnostic Code are 747479646d the ttydm process has failed Workaround There is no effective workaround How to restore In the case of a system that consists of multiple SPARC M10 4S chassis By executing the console 8 command after XSCF resetting which causes master standby XSCF switching you can connect to the control dom
40. QUALITE MARCHANDE AL APTITUDE A UNE UTILISATION PARTICULIERE OU A L ABSENCE DE CONTREFACON Contents Preface ix Chapter1 Software Requirements 1 XCP Oracle Solaris and Required SRU Patch 1 Notes on using Oracle Solaris 10 4 Notes when using a version older than Oracle VM Server for SPARC 3 1 0 1 4 Required XCP Oracle Solaris and required SRU patch to enable dynamic reconfiguration of physical partition 5 Required XCP Oracle Solaris and required SRU patch to enable dynamic reconfiguration of PCIe endpoint device 5 Software supporting Software on Chip 6 How to Obtain XCP and Oracle Solaris SRU Patch Oracle VM Server for SPARC 7 Web Browser 7 Existing XCP Firmware Versions and Support Information 7 Chapter 2 XCP 2250 Related Information 11 Latest Information on XCP 2250 11 Notes and Restrictions 11 Notes on Secure Socket Layer SSL 3 0 12 Restrictions on audit 12 Notes on dynamic reconfiguration of physical partitions 12 Notes on mixing SPARC64 X processors with SPARC64 X processors 13 Notes and restrictions on the SR IOV functions 13 Notes on OpenBoot PROM 14 Notes on maintenance for CPU memory units motherboard unit XSCF unit PSU backplane or crossbar backplane unit 16 Notes on CPU Activation 18 Notes and restrictions on XSCF Web 19 Notes on firmware update 20 Notes on configurations with a PCI expansion unit connected 22 Notes on dual power feed setting 24 Notes on Active Directory 24 Notes on LDAP over SSL 24 Note
41. RTIF2 140212 014 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 4 48 x x x x x x x x x x x x xX x Description In the OID information of scfComponentStatusEvent in the definition file of XSCF extended MIB the path information of the suspected components may be denoted as unspecified in the trap notification This symptom occurs when the OID FaultEventCode information is any of the following 05018113 05018123 05018133 05018211 05018221 05018231 When an attempt is made to register a password containing 256 or more characters in the password input prompt of either the setsnmp 8 or the setsnmpusm 8 command only 255 characters are registered When powering on or rebooting a physical partition PPAR even if the process is stopped due to the failure of a component the POWER LED of the operation panel keeps blinking If the XSCF master standby switchover occurs when the physical partition PPAR is running in some very rare cases XSCF process down may occur and the XSCF may be reset In a system configuration with 3 or more BBs or with a crossbar box if the XSCF master standby switchover occurs for 60 or more times a process down may occur on the slave XSCF and the slave XSCF is reset Even if the CPU cache degraded CPU xx error is detected the CHECK LED of the operation panel may not light up Workaround There is no effective workaround
42. Restore In case of SPARC M10 45 M10 4 replace the CMUL on which the I O has failed In case of SPARC M10 1 replace the MBU on which the I O has failed There is no effective workaround Reset XSCF with the rebootxscf a command After that execute the svcs command on the control domain to restart the picl fmd and the Idmd services There are no effective workaround Contact the maintenance staff if this symptom occurs Chapter 3 Information on Software 123 Table 3 16 Problems resolved in XCP 2210 continued SPARC M10 RTI No 1 4 4S Description RTIF2 x After a degraded system board is 140407 007 replaced using the replacefru 8 command the replacement system board is diagnosed using the replacefru 8 command menu or the testsb 8 command The diagnosis fails if all of the following conditions are met Physical partition PPAR consists of multiple system boards and the PPAR power is on Some system boards in the PPAR are stopped through degradation RTIF2 x x x AnXSCF NTP server function may be 140410 001 used as the platform for a DDoS attack CVE 2013 5211 RTIF2 x When setting the takeover IP address 140410 007 virtual IP address for the XSCF network the XSCF LAN IP address physical IP address needs to be set for both master and standby XSCFs Otherwise the takeover IP address setting may not be reflected after the setting is applied and XSCF is reset RTIF2 x x x If Firefox
43. SPARC M10 chassis using the b option of the diagxbu 8 command 2 Select the SPARC M10 chassis by the b option of the replacefru 8 command 3 When the message for the replacement of SPARC M10 chassis is output in the maintenance menu turn on the input power AC ON of the SPARC M10 chassis without replacing it There is no effective workaround How to Restore Perform the following procedures 1 Power off the physical partition PPAR by the poweroff 8 command 2 Check the physical state of the crossbar cable loose connection disconnection etc who component information is depicted by a number of s 3 Execute the poweron 8 command to power on the PPAR 4 Check the component information of the target crossbar cable with the showhardconf 8 command Example When the crossbar cable is properly connected Chapter 3 Information on Software 75 Table 3 8 SPARC M10 RTI No 1 4 4S Description RTIF2 x x x 140602 001 When the input power of a PCI expansion unit is turned off AC OFF an error log is registered but notification through SNMP trap or REMCS is not performed Confirmation that the input power of a PCI expansion unit had been turned off can be seen in the output of the showlogs error command like the following Date May 29 20 03 05 JST 2014 Code 10000400 00d4000000ff0000ff 1100002a0000000000000000 Status Information Occurred May 29 20 03 00 905 JST 2014 FRU BB 0 PCI 8 P
44. SPARC version that is older than 3 1 0 1 the ldoms ldmd service fails to start and thus Oracle VM Server for SPARC does not function If using an Oracle VM Server for SPARC version that is older than 3 1 0 1 disable the PPAR DR feature before setting up logical domains Configuration of the PPAR DR feature is performed with the setpparmode 8 command of XSCF firmware For details on the setpparmode 8 command refer to Fujitsu M10 SPARC M10 Systems XSCF Reference Manual Meanwhile in case of Oracle Solaris 11 Oracle VM Server for SPARC 3 1 0 1 is included in SRU11 1 14 Required XCP Oracle Solaris and required SRU patch to enable dynamic reconfiguration of physical partition The following lists XCP Oracle Solaris and required SRU patch to enable dynamic reconfiguration of physical partition Table 1 2 List of XCP Oracle Solaris and required SRU patches needed for physical partition dynamic reconfiguration Server XCP Oracle Solaris Required packages Required SRU Required products Required patch SPARC M10 45 2220 or Oracle Solaris 11 2 system Idoms 1 None later system ldoms ldomsmanager 2 Oracle Solaris 11 1 system Idoms 1 SRU11 1 14 or system Idoms ldomsmanager 2 later 3 Oracle Solaris 10 1 13 Oracle VM Server for SPARC 3 1 4 150817 02 or later 4 5 1 Required for the control domain and the guest domain Included in group system solaris large server and group system solaris small server 2 Required only for the
45. Systems Product Notes for XCP Version 2250 May 2015 Table 3 21 RTI No RTIF2 130930 001 RTIF2 131004 001 Problems resolved in XCP 2070 continued SPARC M10 1 4 4S Description x x x If in an environment for which a time zone is set for the XSCF and daylight saving time is introduced a physical partition PPAR is restarted or a PPAR is turned off and then on again the start time of the logical domain may be advanced or delayed for 3600 seconds or longer This can be confirmed by executing the showdateoffset 8 command In the following execution example the time difference between PPAR and XSCF is 3600 seconds or greater indicating that this defect has occurred Example XSCF gt showdateoffset a PPAR ID Domain Date Offset 00 7205 sec 01 7205 sec 02 7205 sec 03 7205 sec 04 7205 sec 05 7205 sec 06 7205 sec 07 7205 sec 08 7205 sec 09 7205 sec 10 7205 sec 11 7205 sec 12 7205 sec 13 7205 sec 14 7205 sec 15 7205 sec x If firmware update is executed when the physical partition PPAR is powered on the CPU MBC interface fatal error error which is related to the motherboard unit MBU is mistakenly detected and may be registered in the error log This mistaken detection may lead to stopping of the logical domains Workaround There is no effective workaround For every logical domain in the system make the settings so that they can be synchronized with the NTP server in t
46. The reset 8 command cannot be used in this state The c wait option which is used to set the wait time before the system is started for the setpowerupdelay 8 command is not supported at present Replacement of a crossbar box using the replacefru 8 command is not supported at present For how to replace a crossbar box see Restrictions on replacing crossbar box in Chapter 6 Information on SPARC M10 4S Hardware Addition of a crossbar box using the addfru 8 command is not supported at present For how to add a crossbar box see Restrictions on adding expansion rack 2 in Chapter 6 Information on SPARC M10 4S Hardware SPARC M10 4S If you power on all physical partitions PPAR in a system that has more than one PPARs with the poweron 8 command the startup time taken when specifying power on of PPAR is longer than the time taken for batch power on by specifying a SPARC M10 4 M10 4S As for the ioreconfigure that can be specified by m function of the setpparmode 8 command leave it as the default false and disable the I O bus reconfiguration function If you enable the I O bus reconfiguration function by specifying true to the ioreconfigure it may be necessary to reinstall Oracle Solaris SPARC M10 4S 32 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 If showhardconf M is executed it may not be possible to display one screen at a time if both of the conditions below are met Do not
47. again RTIF2 If you turn on the AC when the system The error log is registered because no 130130 001 configuration has no CPU memory unit CMUU is mounted So ignore it upper CMUU a Hardware access error error log is generated for CMUU The same phenomenon occurs when you add or replace SPARC M10 4S RTIF2 If the power save operation whichis set Set the power save operation to 130212 001 by the setpparmode 8 command is disabled by using the setpparmode 8 enabled the following problems may occur A hang up heartbeat function in a logical domain may be unable to be detected Ifthe CPU core resources are reduced during system startup while a physical partition PPAR is operating the PPAR may be powered off command Chapter 3 Information on Software 163 Table 3 25 RTI No RTIF2 130212 002 RTIF2 130212 003 RTIF2 130215 001 RTIF2 130215 002 RTIF2 130219 001 RTIF2 130219 005 164 Problems resolved in versions prior to XCP 2050 continued SPARC M10 1 4 4s x x x Description When you check the domain status by using the showdomainstatus 8 command from the XSCF after executing the Idm add spconfig command from Oracle Solaris Host stopped is displayed for all domains including the control domain If you execute the testsb 8 command to a system board PSB that is being diagnosed by the testsb 8 or diagxbu 8 command in a different session the PSB that i
48. board unit MBU or a CPU memory unit lower CMUL is replaced in the system with a single unit configuration of SPARC M10 1 SPARC M10 4 or SPARC M10 4S The setsnmp 8 setsnmpusm 8 or setsnmpvacm 8 command may fail to reflect settings properly if the settings are changed to valid immediately after being changed to invalid Example The command fails and some of the settings Enabled MIB Modules are not reflected properly XSCF gt setsnmp disable XSCF gt setsnmp enable setsnmp Agent enable failed XSCF gt showsnmp Agent Status Enabled Agent Port 161 System Location System Location System Contact System Contact Status Enabled Community String public Enabled MIB Modules None lt not reflected XSCF gt SP MIB is displayed in Enabled MIB Modules when the settings are reflected properly Expiration date for the self authenticated certificate used by the HTTPS service will arrive in 1 year not in 10 years Workaround There is no effective workaround How to restore See the Fujitsu M10 SPARC M10 Systems RCIL User Guide and reconfigure RCIL Be sure to wait 30 seconds or more if the settings are changed to valid after being changed to invalid How to restore Execute the command again after a lapse of 30 seconds or more After executing the command again confirm the settings are reflected as expected executing the showsnmp 8 showsnmpusm 8 or showsnmpvacm 8 command You
49. command to forcibly power off the PPAR If the PPAR power off process or system board diagnosis is interrupted Turn off the input power to all SPARC M10 system chassis or crossbar box chassis and then turn it on again AC OFF ON There is no effective workaround Ignore this error log There is no effective workaround How to restore If the PPAR power supply remains in the power on state 30 minutes after executing the showpparprogress 8 command turn off the input power to all chassis and then turn it on again AC OFF ON Chapter 3 Information on Software 71 Table 3 8 RTI No RTIF2 140410 008 RTIF2 140410 009 RTIF2 140507 003 RTIF2 140507 004 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 4 48 x x x x xXx x Description minute has passed this phenomenon has occurred Example of unsuccessful power off XSCF gt showpparprogress p 0 This PPAR is powered on Normally when the PPAR power off completes the power off sequence and PPAR state are as follows Example of successful power off XSCF gt showpparprogress p 0 PPAR Power Off PPAR O 1 3 CPU Stop PPAR O 2 3 PSU Off PPAR O0 3 3 The sequence of power control is completed Even if the XSCF DUAL control cable is reconnected after the system input power has been turned on with this cable disconnected data synchronization between the master chassis and standby chassis cannot be se
50. control domain Included in group system solaris large server and group system solaris small server 3 Required for the control domain and the guest domain Though SRU11 1 14 includes Oracle VM Server for SPARC 3 1 0 1 the modification for Solaris 11 1 to fix BugID 17709858 is required to ensure stable DR functionality This issue has been resolved in SRU11 1 15 and later 4 Required only for the control domain 5 Do not apply patch 150400 01 to 150400 06 Required XCP Oracle Solaris and required SRU patch to enable dynamic reconfiguration of PCle endpoint device The following lists XCP Oracle Solaris and required SRU patch to enable dynamic reconfiguration of PCle endpoint device Chapter 1 Software Requirements 5 Table 1 3 List of XCP Oracle Solaris and SRU patches needed for dynamic reconfiguration of PCIe endpoint device Server XCP Oracle Solaris Required packages Required SRU Required products Required patch SPARC M10 1 2230 or Oracle Solaris 11 2 system Idoms 1 SRU11 2 2 or SPARC M10 4 later system ldoms ldomsmanager 2 later PARC M10 4 S CMIS Oracle Solaris 11 1 4 system ldoms 1 SRU11 1 17 or later 3 Oracle Solaris 10 1 13 Oracle VM for SPARC 3 1 5 6 150817 03 or later 5 1 Required for the control domain and other domains Included in group system solaris large server and group system solaris small server 2 Required only for the control domain Included in group system solaris large server and group syst
51. disabled format Searching for disks done AVAILABLE DISK SELECTIONS 0 c2t50000394281B5312d0 lt TOSHIBA MBF2600RC 3706 cyl 64986 alt 2 hd 27 sec 668 gt Logical device path name Vendor name Product name pci 8800 pcit4 pcit0 pcil0 scsi 0 iport disk w50000394281b5312 0 Physical device path name Procedure for enabling MPxlO 1 Add the information the vendor name and the product name of the internal SAS disk or the SSD with the MPxIO setting disabled to the kernel drv scsi_ vhci conf file Setting example of the scsi_vhci conf file For Oracle Solaris 11 and later scsi vhci failover override TOSHIBA MBF2600RC f sym Vendor name Product name For Oracle Solaris 10 device type scsi options list TOSHIBA MBF2600RC sym opt Vendor name Product Name sym opt 0x1000000 2 Enable MPxIO with the stmsboot 1M command For details of the stmsboot 1M command see the online manual stmsboot D mpt_sas e If a message as shown below is output as the execution result of the command continue by executing the stmsboot u command stmsboot D mpt_sas e STMS is already enabled No changes or reboots needed stmsboot u Executing the stmsboot 1M command restarts the system of the domain and enables MPxIO of the internal SAS disk or the SSD After the restart the target device path name is changed Chapter 3 Information on Software 37 You need to change the device path name i
52. error in BB 00 use the replacefru 8 command To remove a SPARC M10 4S chassis perform the cold removal the chassis is removed by turning off the input power Chapter 3 Information on Software 161 Table 3 25 SPARC M10 RTI No 1 4 4S RTIF2 x x x 121219 016 RTIF2 x 121219 017 RTIF2 x 121219 018 RTIF2 x x x 121219 019 RTIF2 x 130109 002 RTIF2 x x x 130109 005 162 Description An internal error may occur if the prtfru 8 command is executed while powering on off or resetting the physical partition PPAR If a SPARC M10 4S chassis is powered off after an error log is registered because a memory error occurred in BB 00 or BB 01 the same error log may be registered again In a system in which two or more SPARC M10 4S chassis units constitute multiple physical partitions PPARs if you power on the PPAR after switching the master XSCF as a result of any of the following error logs of STICK does not start CPU STICK does not start MBC or STICK count up error may be registered causing degradation of the CPU memory units CMUU CMUL Performing firmware update Detecting an XSCF failure Executing the switchscf 8 command When a PCI card is inserted to or removed from a PCI expansion unit a number that is different from the relevant PCI card number PCI is displayed in the log In addition when error log PCICARD failed is registered due to an error with the PCIe slot on t
53. execute showhardconf M System configured with 2BB or more One or more SPARC M10 4S units are subject to an XSCF reset by the rebootxscf 8 command so they cannot communicate SPARC M10 1 If firmware update to the version of XCP 2070 or earlier is executed when the physical partition PPAR is powered on the logical domains may stop Be sure to execute firmware update when the physical partition PPAR is powered off See RTIF2 131004 001 of Problems resolved in XCP 2070 for this issue The XSCF user account s user privilege managed by the LDAP server which is specified by either by the setldap 8 command or by specifying XSCF Setting User Manager LDAP on the XSCF Web cannot be set up with XSCF Setting User Manager Account on the XSCF Web Set up user privilege with the setprivileges 8 command on XSCF shell prompt XCP 2250 Problems and Workarounds See Problems that might occur with XCP 2250 and workarounds for information on problems that can occur with XCP 2250 See Problems resolved in XCP 2250 for information on problems resolved in XCP 2250 Chapter2 XCP 2250 Related Information 33 34 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Chapter 3 Information on Software This chapter describes special instructions and problems concerning the SPARC M10 Systems software Notes and Restrictions Problems with XCP and Workarounds Problem
54. for a long time powering off and then powering on a physical partition PPAR may cause the Oracle Solaris time to deviate This phenomenon occurs in one of the following cases The setting specifying the XSCF as an NTP client is enabled and the Oracle Solaris does not use the NTP server The setting specifying the XSCF as an NTP client is enabled and Oracle Solaris uses the NTP server At the time of Oracle Solaris booting the ntpdate command is not executed or the ntpdate command fails to correct the time Workaround There is no effective workaround Note To update the firmware from XCP 2232 or earlier to XCP 2040 or later for which this problem has been resolved see the RTIF2 140711 001 additional information How to restore Execute the following procedure to boot Oracle Solaris in single user mode and set the time 1 Execute the poweroff 8 command to power off the PPAR 2 Execute the showpparstatus 8 command to confirm that the status is Powered off meaning that the PPAR is disconnected 3 Set the environment variable auto boot of OpenBoot PROM to false XSCF gt setpparparam p PPAR ID s bootscript setenv auto boot false 4 Execute the poweron 8 command to power on the PPAR 5 Execute the console 8 command to connect to the control domain console and display the ok prompt 6 Boot Oracle Solaris in single user mode 0 ok boot s 7 Execute the date command to set the Or
55. host name Workaround If a host name with more than 16 characters has already been registered execute the setsnmp 8 command with either the remtraphost or the remv3traphost operands to remove the trap host and register the trap host again with the IP address When the trap host is registered with the setsnmp 8 command the following message may be output iptables v1 4 7 host network example com not found Try iptables h or iptables help for more information This message indicates that the name resolution has not been executed for the host name of the registered host Although the trap host has been properly registered traps are not reported to the trap host as name of the trap host could not be resolved Set up the name server by executing the setnameserver 8 command and conduct name resolution for the target host 48 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 RTI No RTIF2 130109 003 RTIF2 130219 004 RTIF2 130219 006 RTIF2 130305 001 Problems with XCP and Workarounds This section describes problems with XCP and workarounds for each version Problems that might occur with XCP 2250 and workarounds The following table lists the problems that might occur with XCP 2250 and workarounds for them Problems that might occur with XCP 2250 and workarounds SPARC M10 1 4 48 x x x x x x x x x x Description If you use the se
56. log of PSUs detect 100V and 200V at AC inputs indicating that an error in the configuration of the input power supply may be registered XCP 2041 or later Wrong PSU is installed XCP 2032 or earlier PSUs detect 100V and 200V at AC inputs RTIF2 x 140227 001 When the cross bar boxes are powered on AC ON for the first time the SCF panic detected or the XSCF hang up is detected error log may be registered when XSCF is started Workaround There is no effective workaround Ignore this error log There is no effective workaround How to restore 1 Confirm that all crossbar boxes and SPARC M10 4S are displayed with the showhardconf 8 command 2 Perform AC OFF ON on all crossbar boxes and SPARC M10 4S 3 Check the master XSCF with the showbbstatus 8 command If XBBOX 81 had been switched to master XSCF use the switchscf 8 command to make XBBOX 80 the master XSCF Chapter 3 Information on Software 93 Table 3 10 RTINo RTIF2 140314 001 RTIF2 140507 013 Problems resolved in XCP 2240 continued SPARC M10 1 4 4s x x x x Description In case of a SPARC M10 1 to which XCP 2210 is applied if an internal component failure occurs in Type B motherboard unit MBU it may not be detected and the following error may be registered in numbers Voltage problem within MBU FRU MBU Msg Critical low voltage error Or Fan speed problem FRU FAN x MBU Msg FAN speed too low
57. message may be registered to the event log and maintenance or addition fails Two or more CMUL or SPARC M10 chassis is cold replaced or cold added at one time The XCP versions of replacement components do not match the version of the master XCP If XSCF login is performed with a XSCF user account whose privileges are managed by a LDAP server specified by the setldap 8 command execution of commands in the XSCF shell or operations on the XSCF Web may take a while The following improper error message is displayed when the addboard c configure command is executed specifying a non existent system board PSB PPAR is currently unavailable for DR because XBU status has failed Or The current configuration does not support this operation When performing AC OFF ON in some very rare cases the SCF process down detected error message is registered and XSCF fails to start Workaround When cold replacing or cold adding two or more CMUL or SPARC M10 chassis use the replacefru 8 or addfru 8 command to perform the operations one by one How to restore Execute any of the following procedures Procedure 1 1 Perform AC OFF ON 2 Execute the flashupdate 8 command specifying the XCP version XSCF gt flashupdate c update m xcp s xxxx f xxxx is the XCP version of the master XSCF Procedure 2 Execute the replacefru 8 command to perform a pseudo replacement of the CMUL or SPARC M10 chassis that failed
58. occur in any versions of Oracle Solaris and workarounds Workaround Before you add a PCI expansion unit by hotplug 1M add the following line in the etc system file in advance and restart Oracle Solaris set pcicfg pcicfg_slot_busnums 4 Note that the system does not recognize a device of a PCI expansion unit if you add the PCI expansion unit by PHP to a root complex that has been added by either of the following the dynamic reconfiguration of the physical partition or the Dynamic PCIe bus assignment If this problem occurs restart the logical domain to which the PCI expansion unit is assigned to make the system recognize the device of the PCI expansion unit Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 26 Bug 17561541 18502702 18595023 18665751 SPARC M10 1 4 48 x x x x xX x x xX x x xXx x Description In an environment with XCP 2230 or later is applied if the Idm add io command is executed after executing the Idm remove io command during delayed reconfiguration the Idmd daemon may dump core and restart If the SunVTS 7 0 ps17 1 test is started on a SPARC M10 system with SPARC64 X processors it may end with an error If the Idm list io command is executed after PCI cards which support the SR IOV function are mounted on PCI Expansion Unit s SLOT4 or higher the pseudonym of the physical function of the PCI cards mounted on SLOT4 or higher is mistak
59. of the switchscf 8 command when the power to the PPAR is on or if the error occurs due to an XSCF failure process down etc when the power to the PPAR is on Perform recovery of the SPARC M10 4S chassis for which the XSCF hang up is detected error log has been registered by using either of the following methods Execute the replacefru 8 command to replace the CPU memory unit lower CMUL or XSCF unit XSCFU Power off and on the CPU memory unit lower CMUL or the XSCF unit XSCFU Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 21 SPARC M10 RTI No 1 4 4S RTIF2 x 130711 001 RTIF2 x x x 130716 001 RTIF2 x 130801 001 RTIF2 x x x 130802 001 Problems resolved in XCP 2070 continued Description When you perform maintenance of the SPARC M10 4S by executing the replacefru 8 or addfru 8 command the FMEM serious error error log may be registered and the replacefru 8 or addfru 8 command may fail Also when you turn on the power to the physical partition PPAR during the execution of the flashupdate 8 command similarly the FMEM serious error error log may be registered and the flashupdate 8 command may fail When you update the PCI expansion unit firmware by executing the ioxadm 8 command a LINKCARD I2C error error may occur Even if you execute the switchscf 8 command the XSCF may not be switched At this time the master XSCF and standby X
60. of the internal SAS disk and SSD stmsboot D mpt_sas d Procedure for confirming the device path You can confirm the following items by using the procedure below the device path name the vendor name the product name and the enabling disabling state of MPXxIO of an internal disk or SSD on SPARC M10 system If MPxIO is already enabled the character string scsi_vhci appears in the physical device path name of the internal SAS disk or SSD Display example when MPXxIO for an internal disk is enabled The physical device path name includes the character string scsi_vhci So MPxIO is enabled The format command omits a part of the logical device path name to display The actual name of the logical device path is the path name with dev rdsk added Chapter 3 Information on Software 39 format Searching for disks done AVAILABLE DISK SELECTIONS 0 c0t50000394281b5310d0 lt TOSHIBA MBF2600RC 3706 cyl 64986 alt 2 hd 27 sec 668 gt Logical device path name Vendor name Product name scsi_vhci disk g50000394281b5310 Physical device path name dev chassis FUJITSU BBEXP 500000e0e06d31bf 03N0 HDDOO disk Display example when MPXxIO for an internal disk is not enabled The physical device path name does not include the character string scsi_vhci So MPxIO is disabled The format command omits a part of the logical device path name to display The actual name of the logical device path is the path name with dev rdsk
61. on another chassis execute the restoreconfig 8 command on that chassis to confirm the following settings before restoring the XSCF setting information LDAP client setting Example To display all LDAP setting information except the CA certificate and password XSCF gt showldap Bind Name Not set Base Distinguished Name Not set LDAP Search Timeout 60 Bind Password Not set LDAP Servers Not set CERTS None LDAP over SSL client setting Example To display enabled disabled status of LDAP over SSL XSCF gt showldapssl usermapmode disabled state disabled strictcertmode disabled timeout 4 logdetail none Configuration setting of the Active Directory Example To display enabled disabled status of the Active Directory XSCF gt showad dnslocatormode disabled expsearchmode disabled state disabled strictcertmode disabled timeout 4 logdetail none 66 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 RTI No 1 4 4S Description Workaround SNMP agent setting Example To display the SNMP agent setting information XSCF gt showsnmp Agent Status Disabled Agent Port 161 System Location Unknown System Contact Unknown System Description Unknown Trap Hosts None SNMP V1 V2c None Example To display the setting information for the SNMPv3 agent USM XSCF gt showsnmpusm U
62. or keys during the physical partition power off due to the trouble in 1 the following error log may be detected and the mother board unit MBU may need to be replaced MBC CPU interface fatal error Check all the following five conditions are satisfied to see if the trouble in 1 occurs Any of the following error logs is registered MBU SCF failed to read write interrupt mask register MBU SCF failed to read write active status register Voltage out of range error Oracle Solaris is not accessible via the network No power failure notification is issued 1 Workaround eef ynny 3 Execute setremotepwrmgmt c config file name to apply the management file 4 Execute setremotepwrmgmt c enable to enable the power supply interlocking 2 Disable the power supply interlocking function 1 Execute setremotepwrmgmt c disable to disable the power supply interlocking 2 If the external I O device is ETERNUS set the ETERNUS to LOCAL mode for operation There is no effective workaround If MBC CPU interface fatal error is detected replace the MBU If MBC CPU interface fatal error is not detected turn off the input power supply and then turn it on again Chapter 3 Information on Software 85 Table 3 8 SPARC M10 RTI No 1 4 4S Description The physical partition status display that you can check by the showpparstatus 8 command is not updated and indicates the physical par
63. or later XSCF gt flashupdate c sync Problems with Hardware and Workarounds There is no problem that has been confirmed as of this moment Chapter6 Information on SPARC M10 4S Hardware 195 196 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Chapter 7 Information on PCI Expansion Unit Hardware This chapter describes special instructions and problems concerning the PCI expansion unit hardware Direct I O Function for the PCI Expansion Unit Problems with PCI Expansion Units and Workarounds Direct I O Function for the PCI Expansion Unit For XCP 2044 or later of SPARC M10 1 M10 4 and for XCP 2050 or later of SPARC M10 4S the direct I O function of Oracle VM Server for SPARC is supported for the PCI expansion unit This makes it possible to assign an I O domain for each slot of the PCI expansion unit For details on the direct I O function of Oracle VM Server for SPARC see Oracle VM Server for SPARC Administration Guide for the version used If the PCI expansion unit is connected to SPARC M10 4 make the setting below before using the direct I O function For SPARC M10 1 the setting below need not be made The direct I O function can be used simply by connecting the PCI expansion unit to SPARC M10 1 Setting displaying the direct I O function To set the direct I O function for the PCI expansion unit use the setpciboxdio 8 command of the XSCF firmware To confirm the present settings use t
64. resolved in version 1170 of the PCI expansion unit firmware 202 Problems resolved in version 1150 of the PCI expansion unit firmware 206 Problems resolved in version 1130 of the PCI expansion unit firmware 207 Problems resolved in version 1120 of the PCI expansion unit firmware 209 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Problems resolved in version 1110 of the PCI expansion unit firmware 209 Problems resolved in version 1100 of the PCI expansion unit firmware 210 Chapter 8 Contents of Revision of Documentation 213 Contents vii viii Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Preface This document describes the latest information about XSCF Control Package XCP and the important and latest information regarding hardware firmware software and documents of SPARC M10 Systems Note If a newer version of XCP than the version supported in this document is released only the document supporting the latest version of XCP is updated In addition to reading this document visit the following websites to see the document supporting the latest version of XCP Check the contents and usage to confirm whether there are any corrections in the documents related to XCP version that you use Japanese site http jp fujitsu com platform server sparc manual Global site http www fujitsu com global services computing server sparc downloads manual Fujitsu M10 is
65. setsmtp 8 command you execute the setemailreport 8 command to send a test mail Then the reply address shows that the mail has been successfully sent x x x Ifyou execute the setaudit delete command and use the viewaudit 8 to display the audit log some audit logs may not be deleted x x x Ifyou display the XSCF Web screen in another window or in another tab without using the XSCF Web menu contents may not be normally displayed x x x While XSCF is starting process down panic or watchdog timeout occurs which may cause XSCF to be reset Workaround There is no effective workaround Even if it is displayed that the test mail has been successfully sent it is not sent There is no effective workaround For operation to display the XSCF Web screen use the menu tree Confirm that XSCF is successfully started If it is not started turn off the power of the physical partition PPAR and then disconnect the input power supply to the system and back on again AC OFF ON When recycling the power supply to the system wait for 30 seconds or more to turn on the input power supply after disconnecting In case XSCF is not started even if recycling the input power supply to the system replace the CPU memory unit lower CMUL or the motherboard unit MBU 156 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 25 RTI No RTIF2 121113 009 RTIF2 121113 011 RTIF2 121113 014
66. setsnmpvacm 8 command of the XSCF shell 64 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 SPARC M10 RTI No 1 4 4S RTIF2 x x x 140407 001 Description Suppose you attempt to execute the dumpconfig 8 command to save XSCF setting information and then execute the restoreconfig 8 command to restore the XSCF setting information in the same chassis or other chassis In this case some settings may not be saved restored or may be excessively restored on other chassis The following settings are not saved restored in the same chassis or other chassis Setting values for power operation at power recovery set with the setpowerschedule c recover command Setting values for enabling disabling ASR function set with the setservicetag 8 command PPAR DR feature setting values set with the setpparmode p ppar_id m ppar_dr command for XCP 2210 or later of the SPARC M10 4S Setting values for configuring a power supply interlocking group changing its settings and enabling disabling the power supply interlocking function for the group set with the setremotepwrmgmt 8 command The following settings are excessively restored on the same or other chassis Information on the time difference between XSCF and the hypervisor of each physical partition PPAR The following settings are excessively restored on other chassis Setting values for the LDAP client set with t
67. space Workaround This has been modified with Oracle Solaris 11 1 SRU3 5 1 and the patch 148888 04 for Oracle Solaris 10 Execute the following command to change ptmx_ptymax Example echo ptms_ptymax Z 0x400000 mdb kw ptms_ptymax 0 0x400000 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 29 Problems resolved in Oracle Solaris 11 2 continued SPARC M10 Bug 1 4 4S Description 15822113 x x x Ifldm add vcpu and ldm remove vcpu are repeatedly executed in a shell script the process that is being run may cause a core dump and abnormally terminate 15823255 x An Oracle Solaris panic may occur if the CPU allocation is changed using the psradm 1M or psrset 1M command or the configuration of a virtual CPU is dynamically changed using the Idm 1M command under the environment that meets the following two conditions The environment where the physical partition PPAR is composed of two or more SPARC M10 4S chassis The environment where the following lgroup exists when the lgrpinfo command is executed on the control domain or logical domain Among the lgroups that are displayed as Igroup XX intermediate only one number is displayed before CPU of the Lgroup resources field This number is not displayed before memory Example lusr bin Igrpinfo lgroup 12 intermediate Children 10 Parent 0 CPUs 0 1 Memory installed 520M allocated 494M
68. specified by m function of the setpparmode 8 command leave it as the default false and disable the I O bus reconfiguration function If you enable the I O bus reconfiguration function by specifying true to the ioreconfigure it may be necessary to reinstall Oracle Solaris With a logical domain running Oracle Solaris 11 updating to XCP 2050 or later allows you to have an increased maximum number of PCle cards on one root complex RC To install a PCle card after updating to XCP 2050 or later perform the steps below in the control domain This example assumes that two sets of configuration information currently in use Idm set1 and factory default are stored 1 Check the configuration information of the logical domain stored in XSCF primary ldm list spconfig ldm setl current factory default 2 Execute the following commands on all of the logical domains including the control domain Specify the name of the logical domain for Idom primary ldm set variable fix_atu true ldom primary ldm remove variable fix_atu ldom 3 Store the updated configuration information for the logical domain again Delete the stored 1dm set1 and then store the information again primary ldm rm spconfig ldm set1 primary ldm add spconfig ldm setl 4 Restart all logical domains An XSCF user account name cannot be the same as an LDAP user name In addition an XSCF user account UID cannot be the same as an LDAP UID When st
69. supply and then power it on again AC OFF ON Problems resolved in XCP 2050 The following table lists the problems resolved in XCP 2050 Workaround After switching between the master XSCF and the standby XSCF by using the switchscf 8 command execute the testsb 8 command to the target slave XSCF The incorrect connection with the XSCF connection cable is detected and an error log is issued Execute the flashupdate 8 command by specifying the f option to reupdate the XCP firmware for all SPARC M10 4S or crossbar boxes If you power off the PPAR before powering off the input power supply of SPARC M10 4S or crossbar box check that power off the target PPAR and SPARC M10 4S is complete by using the showboards 8 and showlogs power commands Then power off the input power supply of SPARC M10 4S or crossbar box Chapter 3 Information on Software 151 Table 3 24 SPARC M10 RTI No 1 4 4S RTIF2 x x x 130319 003 RTIF2 x 130329 004 RTIF2 x 130329 006 RTIF2 x xX x 130516 003 152 Problems resolved in XCP 2050 continued Description If the shutdown i5 command and power off command compete for power off of the PPAR when the former is executed in the control domain or the latter is executed from the ok prompt while power off of the physical partition PPAR is performed with the poweroff 8 command SCF PPAR issued power off request PPARID X may be registered many times In a system with buildin
70. the intrd 1M service before removing the PCIe end point device from the I O domain svcadm disable intrd Enable the intrd 1M service after the process of the Idm remove io command is completed svcadm enable intrd Chapter 3 Information on Software 177 Table 3 27 Bug 18747641 19358400 178 Problems that might occur with Oracle Solaris 11 and workarounds continued SPARC M10 1 4 48 x xXx x x x x Description Core dumps may be produced or wrong calculation results may be obtained or a panic may occur when a program which performs double precision floating point instructions after enabling SPARC64 X SPARC64 X processor specific options and 4 byte boundary alignment 1 and compiled with Oracle Solaris Studio compiler version 12 3 2013 06 17 or newer is executed on a SPARC M10 system with Oracle Solaris 11 1 or newer 1 The 4 byte boundary alignment is enabled by default when creating 64 bit programs In case of 32 bit programs it is enabled if xmemalign Ns N 1 2 4 8 16 or fast is not specified Procedure of checking compiler version The V option shows version information The date is output at the end of version notation The compiler version that corresponds to this bug is 2013 06 17 or newer cc V cc Sun C 5 12 SunOS_sparc Patch 148917 06 2013 06 17 95 V 90 and 77 are also same 95 Sun Fortran 95 8 6 SunOS_sparc Patch 148517 05 2013 06 17 CC V CC Sun
71. to reboot XSCF Chapter 3 Information on Software 133 Table 3 19 Problems resolved in XCP 2090 continued SPARC M10 RTI No 1 4 4S Description Workaround RTIF2 x x x Any of the following may occur while There is no effective workaround 131213 017 XSCF is running How to restore Symptom1 For symptoms 1 2 and 4 Process down occurs and XSCF resets The system can be recovered by Symptom2 resetting XSCF The system can be Response of commands which deals used after that with acquiring MIB information get For symptom 3 and 5 command etc becomes slow Reset XSCF with the rebootxscf 8 Symptom3 command Execution of commands like showhardconf 8 takes time Moreover when the showhardconf 8 command is executed the following message may be output and the command is terminated abnormally Cannot communicate with the other XSCF Check the other XSCF stat Symptom 4 The SCF panic detected error is produced and the XSCF is reset Symptom 5 Login to XSCF Web fails However login to the XSCF shell is possible RTIF2 x If XSCF has disabled the setup of NTP Enable the NTP client setup of XSCF by 131213 018 client the time difference between XSCF executing the setntp s client c enable and the hypervisor of each physical command and synchronize XSCF with partition PPAR is mistakenly updated the upper level NTP server Otherwise and the time of the logical domain may execute the following be misaligned aft
72. using the showaudit 8 command In the following example Policy on full trail is suspend indicating that writing to the audit record has been set to stop temporarily Also Audit space free is 0 indicating that the audit trail has reached its full capacity Example XSCF gt showaudit all Auditing enabled Audit space used 4194304 bytes Audit space free 0 bytes Records dropped 0 Policy on full trail suspend Omitted Problems that might occur with XCP 2250 and workarounds continued Workaround Immediately before powering off a physical partition or resetting it execute the Idm add spconfig from Oracle VM Server for SPARC and store the latest guest domain configuration information in XSCF How to restore If the guest domain time deviates boot Oracle Solaris in single user mode and then synchronize the time Example Setting of 18 30 00 on June 27 2014 date 0627183014 00 Execute the setaudit p count command to configure the audit system to delete new audit records when the audit trail has reached its full capacity Default How to restore Perform the following procedure 1 Perform login authentication using the default user account 2 Execute the restoredefaults xscf command The audit log is erased You can execute the setaudit command 3 Execute the setaudit p count command to configure the audit system to delete new audit records when the audit trail has re
73. using the XSCF Web APCS or the power supply interlocking Not powering on An internal error has occurred Please contact your system administrator Problems that might occur with XCP 2250 and workarounds continued Workaround There is no effective workaround Maintain according to the FRU displayed by the showlogs error command There is no effective workaround Maintain the applicable PSB of SPARC M10 system chassis Confirm that XSCF is successfully started If it is not started turn off the power of the physical partition PPAR and then disconnect the input power supply to the system and back on again AC OFF ON When recycling the power supply to the system wait for 30 seconds or more to turn on the input power supply after disconnecting In case XSCF is not started even if recycling the input power supply to the system replace the CPU memory unit lower CMUL or the motherboard unit MBU There is no effective workaround Ignore the logs with the same contents that were notified at the same period of time considering that they are caused by the same reason There is no effective workaround Use the showboards 8 command to replace the XSCF of the PSB which is shown as unknown 50 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 RTI No RTIF2 130305 023 RTIF2 130305 025 RTIF2 130329 005 RTIF2 130410 001 RTIF2 130410 002 RTIF2 130410
74. versions However the Oracle Solaris time may deviate if a physical partition is started up immediately after updating the firmware from XCP 2232 or earlier to XCP 2240 or later To synchronize the time see Notes on the logical domain time Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Problems resolved in XCP 2232 The following table lists the problems resolved in XCP 2232 Table 3 11 Problems resolved in XCP 2232 SPARC M10 RTINo 1 4 4S Description Workaround RTIF2 x x x Security fixes CVE 2013 4784 Update the XCP firmware to XCP 2232 or 141031 001 For detail see the Oracle website relating later to the following Critical Patch Updates Problems resolved in XCP 2231 The following table lists the problems resolved in XCP 2231 Table 3 12 Problems resolved in XCP 2231 SPARC M10 RTINo 1 4 4S Description Workaround RTIF2 x x x Security fixes see MOS Doc Id 1934739 1 Update the XCP firmware to XCP 2231 or 140930 001 later RTIF2 x x x After executing live migration on a There is no effective workaround 141003 001 system with XCP 2230 adding CPU s to How to restore a logical domain or creating anew logical After the live migration is conducted domain on the source machine may power off the physical partition PPAR cause the logical domain to hang up which is the source machine and then power it on again Problems resolved in XCP 2230 The following table lists the pr
75. with cross boxes if the master standby switchover if executed for more than 256 times the SCF process down detected error is detected on the slave XSCF and XSCF coremgrd may cause process down If cold replacement of CPU memory unit lower CMUL or a motherboard unit MBU is done in the following procedure the physical partitions PPAR may not start 1 Execute the restoredefaults c factory command 2 After XSCF has stopped turn off the input power of the system AC OFF 3 Replace the CMUL or MBU without replacing the microSD card 4 Turn on the input power of the system In a system with several SPARC M10 4S if a crossbar box or the XSCF unit of a crossbar box is replaced after powering off all chassis and then the input power is turned on the following error log may be registered Indispensable parts are not installed OPNL Workaround The showenvironment fan command shows that the number of rotation has been decreased Visual judgment reveals that the number of rotation has been stopped Do not perform consecutive XSCF master standby switchover How to Restore Reset the XSCF The system will become usable Replace CMUL or MBU in the following procedure 1 Execute the restoredefaults c factory command 2 To stop XSCF as in procedure 1 turn off on the input power of the system AC OFF ON and then confirm that XSCF has started 3 Replace the targeted CMUL or MBU
76. 0 0000 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 00000000 00000000 00000000 00000000 0000 Example 2 Date Jan 01 09 05 51 JST 1970 Code 10000000 000e010000ff0000Ff 010240020000000000000000 Status Information Occurred Jan 01 09 05 35 008 JST 1970 FRU MBU Msg TWI access error Diagnostic Code 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 00000000 00000000 00000000 00000000 0000 RTIF2 x x x The message WARNING Time of Day 150119 001 clock error reason Reversed by YYYY or WARNING Time of Day clock error reason Jumped by YYYY may appear on the OS console Workaround There is no effective workaround Do not press the RESET switch unless it is urgent and required How to restore After turning off the power of the physical partition PPAR turn off and then turn on AC OFF ON the input power of the system By turning on the power again the XSCF time is restored automatically There is no effective workaround How to restore If you need an accurate time while the NTP client is not set reboot Oracle Solaris so that it references the hardware time Confirm the time after this reboot Chapter 3 Information on Software 91 Table 3 9 Problems resolved in XCP 2250 continued SPARC M10 RTINo 1 4 4S Description RTIF2 x x x Ifan XSCF LAN network is configured 150218 002 while an XSCF LAN cable is not connected to an XSCF LAN por
77. 0 45 SPARC M10 4 SPARC M10 4S Service Manual XSCF unit XSCFU crossbar unit XBU XSCF interface unit XSCFIFU crossbar backplane unit XBBP fan backplane unit FANBP operation panel OPNL power supply unit PSU fan FAN Perform the following procedure when replacing SPARC M10 4S or CPU memory unit lower CMUL Execute the replacefru 8 command and follow the maintenance menu to perform the replacement SPARC M10 4S When maintenance is performed by either the replacefru 8 or the addfru 8 command terminate the command using the c option If the flashupdate 8 command is executed before terminating the above commands in case of systems comprising of a number of SPARC M10 4S automatic switchover to master XSCF may not be executed after firmware update is complete How to Restore After maintenance is completed using either the replacefru 8 or the addfru 8 command use the c option to terminate the command If switchover to the master XSCF is not performed after the completion of firmware update execute the switchscf 8 command on the master XSCF command to switchover to the master XSCF If XSCF reset or switchover is performed while you are performing an operation on the setting by using an XSCF shell or the XSCF Web the setting may not be saved in XSCF Use the XSCF shell or the XSCF Web to confirm that the setting is saved after the XSCF reset or switchover has completed If the setting is not saved
78. 00 00ffff0000ff0000ff 030000020000000000000000 Status Notice Occurred Nov 16 16 55 25 518 JST 2012 FRU UNSPECIFIED Msg Boot process failed Problems resolved in versions prior to XCP 2050 continued Workaround After you have conducted the replacement use the restoreconfig 8 command to restore the information saved by the dumpconfig 8 command or set the XSCF user account information again There is no effective workaround Reset by the settimezone 8 sethttps 8 and setssh 8 commands When you enable and disable the power supply interlocking of RCIL restart XSCF There is no effective workaround Register the server to be monitored again by the dynamic resource management software There is no effective workaround Switch nodes manually in PRIMECLUSTER After you update an environment variable of OpenBoot PROM execute the Idm add config command to save the domain configuration information to XSCF Use the XSCF setpparmode 8 to disable the auto boot function of the guest domain and then start Oracle Solaris of the control domain Then use the Idm start command of Oracle VM Server for SPARC to start the guest domain How to restore Use the Idm stop command of Oracle VM Server for SPARC to stop the guest domain and then use the ldm start command to start the guest domain Chapter 3 Information on Software 159 Table 3 25 RTI No RTIF2 121206 001 RTIF2 121219 002 RTIF2 121219 0
79. 01 0 fails with the following error message After replacing the system board assign Warning 028 the system board to the physical partition BB XX cannot be replaced because the using the addboard 8 command and PSB in the BB that you indicated is follow the maintenance procedures to running add it in the physical partition Similarly an attempt to initialize the Example degraded system board with the initbb 8 XSCF gt addboard c assign p 0 01 0 command fails with the following error message Hardware error occurred by initial diagnosis This symptom occurs if the system board is in the following state when the showhardconf 8 or the showboards 8 command is executed Example In case PSB 01 0 BB 01 has been degraded XSCF gt showhardconf BB 01 Status Deconfigured XSCF gt showboards a PSB PPAR ID LSB Assignment Pwr Conn Conf Test Fault 01 0 00 01 Assigned n n n Passed Faulted RTIF2 x If Ctrl C is executed in the middle of There is no effective workaround 140212 010 executing the setsnmp 8 setsnmpusm 8 or the setsnmpvacm 8 commands SNMP cannot be set up using the above commands after that In such a case the error message configuration being changed by another user may be displayed 120 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 16 Problems resolved in XCP 2210 continued SPARC M10 Workaround RTI No 1 4 4S Description RTIF2 140212 015 RTIF2 1
80. 04 RTIF2 121219 005 RTIF2 121219 006 RTIF2 121219 009 RTIF2 121219 010 160 Problems resolved in versions prior to XCP 2050 continued SPARC M10 1 4 48 x x x x x xX x X xX x x xXx x x xX x x Description When starting the domain the following error message may appear Msg PCI Express link not active Some chassis may not be recognized if all power cables are not connected within four minutes when connecting the power cables of the system that is composed of multiple SPARC M10 4S chassis While powering on off the power supply interlocking group the showremotepwrmgmt 8 command may be abnormally terminated with the following message Controller response timeout When a component with high temperature or low temperature at an air inlet is registered the information on the second faulty component the second suspect component displayed in the FRU may not be correct Replacement of the power supply unit PSU using the replacefru 8 command may fail with Warning 005 If an error log indicating a fan failure Power on failure or Power off failure is registered other than the correct component may be displayed as the faulty FRU Error log XSCF hang up is detected may be registered when the switchscf 8 command is executed Workaround Ignore this message if the showhardconf 8 command recognizes the PCI Express PCIe card Make sure not to exceed four minutes to finish c
81. 05 002 RTIF2 140605 006 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 x Description POST Diag complete from PPAR PPAR ID 0 Omitted PPAR ID 0 Console path is switched Omitted PPARID 0 GID 00000000 state change OpenBoot Running Suppose that all but one of the system boards PSBs that make up a physical partition PPAR are faulty If you attempt to use the DR function to disconnect the normal PSB by executing the deleteboard 8 command this command times out and terminates abnormally In addition if you execute the deleteboard 8 command using the DR function after then in an attempt to disconnect another PSB in the same PPAR the command always times out Furthermore you can no longer connect to the control domain console by executing the console 8 command Example deleteboard 8 command timeout XSCF gt deleteboard c disconnect 00 0 PSB 00 0 will be unconfigured from PPAR immediately Continue y In y All domains are temporarily suspended proceed y n y Start unconfigure preparation of PSB 1200sec Osi B0 ie 60 5 90 41205 150 1802 3 210 240 270 300 330 360 390 420 450 ee 480 510 540 570 600 630 660 690 720 pm 750 780 810 840 870 900 930 960 990 sates 1020 1050 1080 1110 1140 1170 end Timeout dete
82. 1 2 AL13SEB600 Disabled Enabled AL13SEB900 Disabled Disabled 38 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 2 Default MPxIO setting on an internal SAS disk and an SSD continued Product name Default MPxIO setting Oracle Solaris 11 1 Oracle Solaris 11 2 MBF2600RC Disabled Enabled MK1001CRZB Disabled Enabled MK2001CRZB Disabled Enabled Table 3 3 Example of the device path change before and after MPxIO enabling Device path name before MPxIO is enabled Device path name after MPxIO is enabled Physical device path pci 8800 pci 4 pci 0 pci 0 scsi 0 scsi_vhci disk g50000394281b5310 name iport f disk w50000394281b5312 0 Logical device path dev rdsk c2t50000394281B5312d0 dev rdsk c0t50000394281b5310d0 name Note that a device path name is not changed if MPxIO of an internal SAS disk or an SSD of the SPARC M10 system is enabled manually before updating to Oracle Solaris 11 2 Corrective action Take the following actions after updating to Oracle Solaris 11 2 When the physical device path name can be changed Confirm the physical device path name by using the procedure shown in Procedure for confirming the device path Change the device path of the internal SAS disk or SSD directly specified in backup software or application programs to the confirmed device path name When the physical device path name cannot be changed Execute the following command and forcibly disable the MPxIO setting
83. 1 400000100 sec 15 400000100 sec Phenomenon 3 If you reset the PPAR or power off and on the PPAR the Oracle Solaris time may return to January 1 2001 RTIF2 x x x Ifyou execute the XSCF commands in the 131112 010 following order the setting information for the setntp 8 or settelnet 8 command is not applied and may return to the original state 1 Execute any of the sethostname 8 setnameserver 8 setnetwork 8 setroute 8 or setsscp 8 command 2 Execute either the setntp 8 or settelnet 8 command 3 Execute the applynetwork 8 command Workaround There is no effective workaround Update to firmware version XCP 2221 or later How to restore For details see Restoration after the SCF Diagnosis initialize RTC error RTIF2 131108 001 After executing any of the sethostname 8 setnameserver 8 setnetwork 8 setroute 8 or setsscp 8 command is executed do not execute the setntp 8 or settelnet 8 command until the applynetwork 8 command is executed and the settings are applied Chapter 3 Information on Software 147 Table 3 21 RTI No RTIF2 131112 016 RTIF2 140623 001 Problems resolved in XCP 2070 continued SPARC M10 1 4 4S x xX x x x x Description If you use the deleteuser 8 command to delete a user account for which an SSH user public key is registered it is deleted but the user public key is not deleted User public keys will continue to increase in number s
84. 10 4S chassis and crossbar box the power of the crossbar unit of a crossbar box is not stopped and the crossbar box is also powered on Hypervisor Abort or OS PANIC may occur if all the PPARs are powered on using the poweron a command in a system that has four or more SPARC M10 4S chassis units with multiple physical partitions PPARs Immediately after starting the XSCF the system board PSB may be recognized as Unmount and the addboard 8 command or the poweron 8 command may fail Workaround Power on the input power supply to all the crossbar boxes and SPARC M10 45 chassis that compose the system before powering on a PPAR If you collect a snapshot of the entire system collect snapshots one by one by specifying a BB ID of SPARC M10 4S using b option and not a option Perform this operation on all SPARC M10 4S There is no effective workaround Make sure that the XSCF of each SPARC M10 4S is restarted Power on the PPAR again if they are restarted There is no effective workaround Do not power on all the PPARs at the same time using the poweron a command Power on each PPAR using the p option Wait for about 30 seconds after starting up the XSCF and check that the target PSB is mounted using the showboards 8 command Then execute the addboard 8 or poweron 8 command Chapter 3 Information on Software 165 Table 3 25 RTI No RTIF2 130305 024 RTIF2 130319 001 RTIF2 130329 001 RT
85. 1213 012 replacefru 8 command diagnosis How to restore processing may not terminate properly Re execute the replacefru 8 command Example The replacement of BB 2 Diagnostic tests for BB 2 have started Initial diagnosis is about to start Continue y In y PSB 02 0 power on sequence started 810 840 870 900 end Initial diagnosis has completed PSB power off sequence started 1200sec 0 30 60 90 120 150 180 540 570 600 630 660 690 720 810 840 870 900 930 960 990 1080 1110 1140 1170 1200end Failed to power off Please check the FRU An internal error has occurred Please contact your system administrator done Warning 030 testsb failed c cancel RTIF2 x x x _ Ifthe time zone of XSCF is changed using There is no effective workaround 131213 014 the settimezone 8 command the time Boot the Oracle Solaris after executing zone of Oracle Solaris on that physical the resetdateoffset 8 command and set partition which is booted after the to the right time on the Oracle Solaris change gets misaligned to the tune of the time difference before and after changing the time zone of the XSCF Example If the time zone before setup was UTC and after setup is JST the time misalignment of Oracle Solaris will be 9 hours 56 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 Probl
86. 156 Problems with Oracle Solaris and Workarounds 170 Problems that might occur in any versions of Oracle Solaris and workarounds 170 Problems that might occur with Oracle Solaris 11 and workarounds 177 Problems that might occur with Oracle Solaris 10 and workarounds 179 Problems resolved in Oracle Solaris 11 2 180 Chapter4 Information on SPARC M10 1 Hardware 189 Notes and Restrictions 189 Notes on using external DVD drive 189 Notes on using USB memory 189 Problems with Hardware and Workarounds 190 Contents V vi Chapter5 Information on SPARC M10 4 Hardware 191 Notes and Restrictions 191 Notes on using external DVD drive 191 Notes on using USB memory 191 Problems with Hardware and Workarounds 192 Chapter6 Information on SPARC M10 4S Hardware 193 Notes and Restrictions 193 Notes on using external DVD drive 193 Notes on using USB memory 193 Restrictions on replacing crossbar box 194 Restrictions on adding expansion rack 2 195 Problems with Hardware and Workarounds 195 Chapter 7 Information on PCI Expansion Unit Hardware 197 Direct I O Function for the PCI Expansion Unit 197 Setting displaying the direct I O function 197 Problems with PCI Expansion Units and Workarounds 198 Problems and their workarounds for all versions of the PCI expansion unit firmware 198 Problems resolved in version 1200 of the PCI expansion unit firmware 199 Problems resolved in version 1180 of the PCI expansion unit firmware 200 Problems
87. 1M command on the guest domain that has the physical device after you delete the system board dynamically with the deleteboard 8 command the guest domain may output the following message causing Oracle Solaris to panic panic cpuXX thread XXXXXXXXXXXX assertion failed obj gt afo_corep NULL file common os numaio c line 724 Problems that might occur with Oracle Solaris 11 and workarounds continued Workaround Add the following line to etc system and restart Oracle Solaris set lgrp_topo_levels 1 Before adding the root complex to the logical domain dynamically add the following setting to etc system and then reboot Oracle Solaris set default_stksize 0xa000 If you delete the system board dynamically with the deleteboard 8 command execute the following command before you execute the ipadm 1M command or the ifconfig 1M command on the guest domain modunload i 0 Problems that might occur with Oracle Solaris 10 and workarounds The following table lists the problems that might occur with Oracle Solaris 10 and workarounds for them Chapter 3 Information on Software 179 Table 3 28 Bug 15738030 Table 3 29 Bug 15812880 180 Problems that might occur with Oracle Solaris 10 and workarounds SPARC M10 1 4 4s x x x Description If both of the following conditions are satisfied a control domain panic may occur with BAD TRAP type 31 The operating system of the control
88. 26 is used in an environment 140507 with XSCF firmware older than XCP 019 2210 the frame of the pop up window appears in thick black line RTIF2 x Ifthe master XSCF is switched to standby 140507 020 state just after executing the poweroff f p n n is partition number command the following message is registered in the error log displayed by the showlogs error command Msg SCF process down detected Workaround Use either of the following procedures to replace a system board and execute diagnosis 1 Before replacing the system board execute the deleteboard 8 command to change the system board state to system board pool SP 2 After completing system board replacement and diagnosis execute the addboard 8 command to assign the system board to PPAR again Or 1 After powering off the PPAR execute system board replacement and diagnosis How to restore After executing the deleteboard 8 command to change the system board state to system board pool SP or after powering off the PPAR redo the system board diagnosis Update the XCP firmware version to XCP 2210 or later Set the XSCF LAN IP address physical IP address of both master and standby XSCFs and then set the takeover IP address Ignore the thick black frame There is no effective workaround This symptom has no effect on the system operation 124 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 16
89. 40212 017 RTIF2 140212 018 RTIF2 140212 019 x x x If the version 8 command is executed after replacing the CPU memory unit lower CMUL XSCF unit XSCFU or the motherboard unit MBU the state of Current Bank and Reserve Bank is wrongly displayed Example Before replacing CMUL XSCF gt version c xcp BB 00 XSCF 0 Master XCPO Reserve 2210 XCP1 Current 2210 Wrong After replacing CMUL XSCF gt version c xcp BB 00 XSCF 0 Master XCPO Reserve 2210 XCP1 Current 2210 Right After replacing CMUL XSCF gt version c xcp BB 00 XSCF 0 Master XCPO Current 2210 XCP1 Reserve 2210 After removing SPARC M10 4S or crossbar boxes XBBOX with the initbb 8 or the replacefru 8 commands if the XSCF network host and domain names SSCP IP address routing name server is setup and the applynetwork 8 command is executed the An internal error has occurred Please contact your system administrator error message is output and the XSCF network parameters are not enabled In the REMCS customer information input screen if any of the following two byte characters are input in the two byte input field input error message may be output The leading character corresponds to A1xx of the EUC code The trailing character corresponds to xxA1 of the EUC code When turning on the input power the voltage reading of the power supply unit PSU fails and the PSU error Hardwar
90. 4567890 The XSCF at BB 02 is restarting XSCF gt showhardconf SPARC M10 4S Omitted BB 02 Status Cannot communicate Chapter 3 Information on Software 79 Table 3 8 SPARC M10 RTI No 1 4 4S Description up the PPAR to which the PSB is to be added is restarting In the case of deleteboard The XSCF for one of the PSBs making up the PPAR from which the PSB is to be deleted is restarting RTIF2 x 140616 001 The showhardconf 8 command executed on a SPARC M10 1 does not display Type for the power supply unit PSU Either Type A or Type B should be displayed as the PSU type The meaning of each value of Type is as follows Type A PSU for SPARC64 X Type B PSU for SPARC64 X RTIF2 x x x 140616 002 When the procedure below is executed the error message An internal error has occurred Please contact your system administrator is displayed at execution of the prtfru 8 command and the command abnormally terminates 1 Turn on the input power and then execute the rebootxscf 8 or switchscf 8 Problems that might occur with XCP 2250 and workarounds continued Workaround How to restore Even if switching between master and standby XSCFs occurs you can continue using the system because the addboard 8 or deleteboard 8 command has been executed correctly If the previous master XSCF has stopped execute the following procedure 1 Execute the poweroff a command to t
91. 8 command of the DR feature In such a case the showboards 8 command shows that the status of all the Pwr Conn Conf of the system board PSB is y Workaround Execute the XSCF setpparmode 8 command to enable disable the PPAR DR feature There is no effective workaround How to restore Execute the deleteboard 8 command when the number of master XSCFs automatically returns to one after a few minutes If the number of master XSCFs does not return to one even after 15 minutes press the RESET switch at the rear panel of all existing SPARC M10 system and crossbar boxes Execute the deleteboard 8 command after that Re execute the addboard 8 or deleteboard 8 command If it fails again either reboot the control domain or reboot the XSCF with the rebootxscf a command After that re execute the addboard 8 or deleteboard 8 command of the DR feature There is no effective workaround How to restore Reboot all the XSCFs by executing the rebootxscf a command Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 16 RTI No RTIF2 131218 001 RTIF2 140122 001 SPARC M10 1 4 4S x x x x Problems resolved in XCP 2210 continued Description While Solaris OS is running if physical partition is reset due to the output of the Hypervisor Abort message on the OS console the state of Oracle VM Server for SPARC may change to maintenance mode at the next
92. ARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 RTI No RTIF2 140507 005 RTIF2 140507 006 RTIF2 140507 007 RTIF2 140507 008 RTIF2 140507 009 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 4 48 x x x x x x x x x x x x Description If the ending of daylight saving time be October 31 AM 2 00 and the local time being attempted to set to October 31 AM 1 40 JDT the time is set to the standard local time of October 31 AM 1 47 JST XSCF gt showdate Wed Apr 30 10 16 57 JDT 2014 XSCF gt setdate y s 103101402014 00 Fri Oct 31 01 40 00 JST 2014 The XSCF will be reset Continue y n y Thu Oct 30 16 40 00 UTC 2014 XSCF gt showdate Fri Oct 31 01 47 16 JST 2014 If a failure is detected in DC DC converter DDC the Power subsystem failure error log may be registered twice When error logs Critical ultrahigh temperature at XXX at the time of abnormality of components due to high temperature ultrahigh temperature level are registered and the system is forcibly stopped if the showlogs power command is executed the Cause column of power log may show After a DC DC converter DDC fault has been detected if the system is run continuously without replacing the FRU that appears in the error logs the following error is mistakenly detected at every turning off of input power Msg Power off failure The testsb 8 co
93. C 5 12 SunOS_sparc Patch 148506 11 2013 06 17 The PCIe end point device under an added deleted root complex is not reflected to the PCIe end point device configuration information shown by the showpparinfo 8 command under either of the following conditions The root complex is dynamically added deleted by using Dynamic PCIe Bus Assignment or The root complex is dynamically added deleted by dynamic reconfiguration of the physical partition Workaround This has been modified with SRU11 2 4 Recompile the program with the following xarch flag xarch sparcima There is no effective workaround How to restore By restarting the logical domain that added deleted the root complex dynamically the showpparinfo 8 command displays the correct configuration information Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 27 SPARC M10 Bug 1 4 4S 19680186 X 19913088 x xX x 20061005 x Description If Oracle Solaris 11 2 and later is running and the system board is deleted by dynamic reconfiguration of physical partitions PPAR DR Oracle Solaris may panic If a root complex with PCI expansion unit connected is added dynamically to the logical domain with the Idm add io command the logical domain may output the following message causing Oracle Solaris to panic panic cpuX thread XXXXXXXXXXXX bad stack overflow at TL 1 If you use the ipadm 1M command or the ifconfig
94. CF LAN hardware settings RTIF2 x If XSCF master standby switchover takes There is no effective workaround 130903 004 place when either the XSCF BB control Please make sure that the XSCF BB cable or the XSCF DUAL control cable is control cable and the XSCF DUAL not connected properly the settings at control cable is properly connected the master XSCF side may not be If this symptom occurs confirm whether properly carried on to the standby XSCF each setting by master XSCF had been and thus it may not operate properly stored after confirming that the cables are properly connected Set up XSCF again when the setting has not been saved RTIF2 x Ifthe standby XSCF is restarted while the There is no effective workaround 131004 004 XSCF BB control cable is either faulty or Do not reset an XSCF when the XSCF BB not connected it is started as the master control cable between the master and XSCF so that there are two master XSCF standby is either faulty or not connected units in the system How to restore When there are two master XSCF units If there are two master XSCF units in the system operation cannot be guaranteed system turn off all the chassis and then This state can be confirmed from the fact turn them on again that there are two chassis for which the MASTER LED is lit on their rear panels Problems resolved in XCP 2051 The following table lists the problems resolved in XCP 2051 150 Fujitsu M10 SPARC M10 Systems Product Notes for XCP V
95. CIBOX 2003 PSU 0 Msg AC FAIL Diagnostic Code 00083230 30330000 0000 00080000 00000000 0000 00080000 00000000 0000 00000000 00000000 00000000 00000000 00000000 00000000 0000 RTIF2 x 140605 001 Suppose the following scenario You turn on the power to a physical partition PPAR that consists of multiple SPARC M10 4S chassis The status of the PPAR domain is between self diagnosis test POST completion Initialization Complete and OpenBoot PROM start completion OpenBoot Running If the XSCF in a SPARC M10 4S in the PPAR resets in this status you may be unable to switch to the control domain console You can confirm that this event has occurred by executing the showlogs event command and confirming that an event log for console path switching was registered during the time between POST diagnosis completion and OpenBoot PROM start completion Example Event log message issued when PPAR_ID is 0 Problems that might occur with XCP 2250 and workarounds continued Workaround FRU Part Number 2123628 2 Ver 3920h Type Optic Length 2 There is no effective workaround There is no effective workaround How to restore Perform one of the following operations Execute the rebootxscf a command From XSCF Web reset all XSCFs Turn off the power to the PPAR and then turn it on again 76 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 RTI No RTIF2 1406
96. EVENT ID 5cf4edb8 0613 cbe0 acb1 a9a28a2facl10 DESC A service failed a start stop or refresh method failed AUTO RESPONSE The service has been placed into the maintenance state IMPACT sve ldoms ldmd default is unavailable REC ACTION Run svcs xv sve Idoms Idmd default to determine the generic reason why the service failed the location of any logfiles and a list of other services impacted Please refer to the associated reference document at http support oracle com msg SMF 8000 YX for the latest service procedures and policies regarding this diagnosis Chapter1 Software Requirements 3 Note When Oracle Solaris 11 1 is installed in SPARC M10 Systems the following message appears at the start of Oracle Solaris Example of message WARNING failed to instantiate provider ldmd for process 753 WARNING failed to instantiate provider ldmd for process 753 Sep 24 06 15 59 svc startd 11 svc Idoms Idmd default Method opt SUNW1 dm bin Idmd_ start failed with exit status 95 Sep 24 06 15 59 svc startd 11 ldoms Idmd default failed fatally transitioned to maintenance see svcs xv for details After Oracle Solaris 11 1 is installed apply SRU1 4 or later Then the Oracle VM Server for SPARC package is updated to the version supporting SPARC M10 Systems and such message will no longer be output For other information about Oracle Solaris see Problems with Oracle Solaris and Workarounds Notes on using Oracle Sol
97. Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 fo FUJITSU Manual Code C120 0015 02EN ORACLE Haai Copyright 2007 2015 Fujitsu Limited All rights reserved Oracle and or its affiliates provided technical input and review on portions of this material Oracle and or its affiliates and Fujitsu Limited each own or control intellectual property rights relating to products and technology described in this document and such products technology and this document are protected by copyright laws patents and other intellectual property laws and international treaties This document and the product and technology to which it pertains are distributed under licenses restricting their use copying distribution and decompilation No part of such product or technology or of this document may be reproduced in any form by any means without prior written authorization of Oracle and or its affiliates and Fujitsu Limited and their applicable licensors if any The furnishings of this document to you does not give you any rights or licenses express or implied with respect to the product or technology to which it pertains and this document does not contain or represent any commitment of any kind on the part of Oracle or Fujitsu Limited or any affiliate of either of them This document and the product and technology described in this document may incorporate third party intellectual property copyrighted by and or licensed from the supplier
98. How to Restore Restore with the following procedure 1 Turn off the input power of the system AC OFF 2 Temporarily mount the microSD card that was mounted on the CMUL or MBU when the restoredefaults c factory command was executed to the new unit 3 Confirm that XSCF has started after turning on the input power AC ON 4 Turn off the input power of the system AC OFF 5 Extract the microSD card that was temporarily mounted and mount the original microSD card 6 Turn on the input power of the system AC ON When replacing a crossbar box do so after turning off the input power AC OFF of the target crossbar box only When replacing the XSCF unit of a crossbar box execute the replacefru 8 command to do so Refer to Fujitsu M10 4 Fujitsu M10 4S SPARC M10 4 SPARC M10 4S Service 74 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 RTI No RTIF2 140507 014 RTIF2 140507 016 RTIF2 140507 021 RTIF2 140507 022 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 4 4S Description Indispensable parts are not installed FAN Indispensable parts are not installed PSU When replacefru 8 addfru 8 or rebootxscf 8 command is executed the XSCF hang up is detected error message may be detected at the slave XSCF After configuring the XSCF network with the setnetwork 8 command and applying the configura
99. Hypervisor dump collection Enabled Automatic reboot during hypervisor dump collection Disabled The ldmd 1M daemon may repeat core dump if a suspend process of the appropriate domain fails during live migration Workaround This has been modified with SRU11 2 8 and Oracle VM Server for SPARC 3 2 for Oracle Solaris 10 How to restore Replace the faulty CPU or memory If you want to boot Oracle Solaris while leaving the faulty CPU or memory installed perform the following procedure on the XSCF 1 Execute the poweroff 8 command to power off the physical partition PPAR 2 Execute the setdomainconfig 8 command to place the PPAR in the factory default state XSCF gt setdomainconfig p ppar_id c default 3 Execute the poweron 8 command to activate the PPAR Oracle Solaris reboots in a configuration that includes only the control domain factorydefault This has been modified with SRU11 2 8 and Oracle VM Server for SPARC 3 2 for Oracle Solaris 10 How to restore After executing the l1dm 1M command to change the hypervisor dump setting save the domain configuration information Idm set hvdump hvdump X XXX hvdump reboot YYYY Idm add spconfig ZZZZ After replacing the faulty component execute the setdomainconfig 8 command to initiate a reboot with the original domain configuration This has been modified with SRU11 2 8 and Oracle VM Server for SPARC 3 2 for Oracle Solaris 10 How to res
100. I Expansion Unit for Fujitsu M10 SPARC M10 Systems Service Manual If you need to save restore information related to the PCI expansion unit configuration see the information in the following table Table 2 2 Required work regarding the PCI expansion unit configuration Mounting of PCI Domain configuration Reconstructing Oracle Setting OpenBoot PROM expansion unit VM Server for SPARC environment variables config again No factory default Unnecessary Unnecessary No Guest domain exists Unnecessary Unnecessary Yes factory default Unnecessary Unnecessary Yes Guest domain exists Necessary XML Necessary SPARC M10 4 M10 45 If either of the tasks is performed with the setpciboxdio 8 command using firmware of version XCP 2044 or later for the SPARC M10 4 or version XCP 2050 or later for the SPARC M10 4S the logical domain configuration of the physical partitions PPARs is restored to the factory default at the next startup Moreover when the domain configuration includes a guest domain the OpenBoot PROM environment variable is initialized The enable disable setting for the direct I O function of the PCI expansion unit is 22 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 changed A PCI expansion unit is added removed or replaced for a PCI slot of SPARC M10 chassis for which the direct I O function of a PCI expansion unit is enabled Save the logical domain configuration information to an
101. I hot plugging PHP using the cfgadm 1M command on the logical domain on which it is mounted and thus power supply to it is stopped the LINK CARD 12C error log may be mistakenly registered RTIF2 x x x 140403 001 If you connect to the control domain console by executing the console 8 command on the XSCF serial terminal and then execute any of the following while the control domain console outputs a message the SCF process down detected error may occur and the XSCF may be reset Entering to disconnect the control domain console Executing the console 8 command by specifying the f option from another terminal to forcibly connect to the control domain console of the physical partition PPAR Executing the switchscf 8 command to switch the master XSCF Executing the rebootxscf 8 command to reset the XSCF Workaround There is no effective workaround If after replacing the MBU CMUL or CMUU in question the same error is registered again replace all the DIMMs that are mounted on the MBU CMUL and the CMUU There is no effective workaround Ignore this error log Power supply to the link card has been stopped for sure and the system can be operated continuously Execute the console 8 command after connecting to the XSCF via telnet or ssh or terminate the console 8 command after powering off the PPAR 88 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Tabl
102. IF2 130329 002 166 Problems resolved in versions prior to XCP 2050 continued SPARC M10 1 4 48 x x x x x Description If the input power supply of a crossbar box is disconnected and then powered on again in the state where a physical partition PPAR is powered on in the system that has the crossbar boxes the following message may be output in the control domain console and the power on process of the PPAR may not be completed WARNING Unable to connect to Domain Service providers Immediately after the input power supply of SPARC M10 4 M10 4S is powered on DMA timeout error Hard detected may be detected The CPU memory unit lower CMUL will be degraded if you start the logical domain with DMA timeout error Hard detected detected During firmware updating in SPARC M10 4S ALARM LED of the master chassis suddenly turns on and remains stopped and the firmware updating may not complete If the configuration has two or more crossbar boxes and the physical partition PPAR is configured not to use any crossbar box you cannot disconnect the power supply from the operating panel Workaround There is no effective workaround How to restore If the power on process of the PPAR is canceled disconnect the power of the PPAR forcefully using the poweroff f command After that reset all the XSCFs using the rebootxscf a command or disconnect the input power supply of all the SPARC M10 4S chassis an
103. If the PCI expansion unit cannot be powered on it indicates that a PSU has failed Replace the PSU Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 7 7 RTI No RTIF2 130703 009 Table 7 8 RTI No RTIF2 130703 007 RTIF2 130703 008 Problems resolved in version 1120 of the PCI expansion unit firmware The following table lists the problems resolved in version 1120 of the PCI expansion unit firmware Problems resolved in version 1120 of the PCI expansion unit firmware SPARC M10 1 4 4S x x x Description When physical partitions PPARs or the 1 O domain is started the 6Gbps SAS card mounted in the PCI expansion unit may not be successfully linked up with the PCI Express 8lane Workaround If the 6Gbps SAS card is not successfully linked up with the PCI Express 8lane restart the PPARs or I O domain or reinstall the 6Gbps SAS card by PCI hot plug PHP Problems resolved in version 1110 of the PCI expansion unit firmware The following table lists the problems resolved in version 1110 of the PCI expansion unit firmware Problems resolved in version 1110 of the PCI expansion unit firmware SPARC M10 1 4 4S x x x Description When physical partitions PPARs or the T O domain is started a link card may be erroneously detected as having an error Example of message FRU BB 0 PCI 1 LINK Msg TWI access error When physical partitions PPARs or the
104. Nov 06 17 10 10 509 JST 2014 FRU BB 0 PCI 9 PCIBOX 2005 PSU 1 Msg PSU failed Diagnostic Code 00093131 31310100 0000 00090000 00000000 0000 00090000 00000000 0000 01492800 00000038 00000000 00000000 00000000 00000000 0000 Problems resolved in version 1170 of the PCI expansion unit firmware The following table lists the problems resolved in version 1170 of the PCI expansion unit firmware 202 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 7 4 SPARC M10 RTI No 1 4 4S RTIF2 x x x 131224 003 Description The following error messages related to the link board may be displayed if the link board with Part Number CA20365 B60X007AD 7061035 is connected to the PCI expansion unit Error message example 1 FRU BB 0 PCI 3 PCIBOX 1234 IOB BB 0 PCI 3 PCIBOX 1234 LINKBD Msg PCI access error Error message example 2 FRU BB 0 PCI 3 PCIBOX 1234 IOB Msg PCI access error Error message example 3 BB 0 PCI 3 LINK BB 0 PCI 3 LINK LINKCBL BB 0 PCI 3 PCIBOX 1234 LINKBD Msg PCI Express lane is degraded The Part Number can be checked in the Part Num line upon executing the ioxadm v list command Example XSCF gt ioxadm v list Location Type FW Ver Serial Num Part Num State Omitted PCIBOX 9011 LINKBD BOARD PP134701CJ CA20365 B60X 007AD 7061035 On Chapter 7 Problems resolved in version 1170 of the PCI expansion unit firmware Workaround There is no e
105. OX 2006 BOX 2006 1 XSCF gt ioxadm fvAM serial target serial num For target specify the identifier of the target PCI expansion unit In this case PCIBOX 0000 is specified For serial_num specify the serial number of the PCI expansion unit before the change in the format of nnnnnnnnnn The serial number is found on the label on the chassis of the PCI expansion unit This command replaces the serial number and identifier of the PCI expansion unit By executing the ioxadm v list command you can confirm that the serial number and identifier have been replaced In the following example the serial number of the PCI expansion unit is 2121212006 serial PCIBOX 0000 2121212006 v list Type FW Ve Serial Num Part Num PCIBOX 2121212006 PSU 0 PSU FEJD1201000170 CA01022 0750 D PSU 1 PSU FEJD1245001342 CA01022 0750 D 7060988 BOX 2006 IOB IOBOARD 1110 PP1210010M CA20365 B66X OO7AF LINKBD BOARD PP123300TR CA20365 B60X OO1AA BOX 2006 BB 00 PCL 00 XSC F gt FANBP FANBP PP120904SY CA20365 B68X 004AC CARD 1110 Chapter 7 Information on PCI Expansion Unit Hardware 211 212 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Chapter 8 Contents of Revision of Documentation There are currently no revisions 213 214 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015
106. Obtain XCP and Oracle Solaris SRU Patch Oracle VM Server for SPARC The customers who subscribed SupportDesk can obtain the latest XCP firmware and Oracle Solaris SRU patch Oracle VM Server for SPARC from the SupportDesk Web Web Browser Table 1 6 lists the web browsers on which the XSCF Web operation is confirmed For other information about XSCF Web see Notes and restrictions on XSCF Web Table 1 6 Version of web browser of which operation has been confirmed Web browser Version Microsoft Internet Explorer 8 0 9 0 10 0 and 11 0 Firefox 10 0 or later Existing XCP Firmware Versions and Support Information The following lists the XCP firmware versions that have been released for the SPARC Chapter 1 Software Requirements 7 8 M10 System as well as the main support and update information for each version Table 1 7 XCP version XCP 2250 XCP 2240 XCP 2232 XCP 2231 XCP 2230 XCP 2221 XCP 2220 XCP 2210 XCP 2092 XCP 2091 XCP 2090 XCP 2080 Existing XCP firmware versions and support information Main support information CMU version Support for SPARC64 X processor 3 7 GHz in SPARC 02 25 0000 M10 1 M10 4 Support for the verified boot Support for the DNS round robin for the host name of the 02 24 0000 NTP server Support for 1984 LDC endpoints per guest domain Support for Dynamic PCle bus assignment provided with Oracle VM Server for SPARC 3 2 Security fixes 02 23 0000 Security fix
107. P 2050 continued SPARC M10 RTI No 1 4 RTIF2 x x 131107 002 Description If the input power to the system is turned on the XSCF is reset or the XCP firmware is updated the SCF Diagnosis initialize RTC error is erroneously detected causing the following phenomena to occur Phenomenon 1 The XSCF time may return to January 1 1970 Phenomenon 2 The time difference between the XSCF and all physical partitions PPARs may become a value of 1 3 billion seconds or more You can check this phenomenon by executing the showdateoffset 8 command since the time difference between the XSCF and all the PPARs is displayed as a value of 1300000000 sec or more XSCF gt showdateoffset a PPAR ID Domain Date Offset 00 1300000100 sec 01 1300000100 sec 15 1300000100 sec Phenomenon 3 If you reset the PPAR or power off and on the PPAR the Oracle Solaris time may return to January 1 1970 Workaround There is no effective workaround Update to firmware version XCP 2050 or later How to restore For details see Restoration after erroneous detection of the SCF Diagnosis initialize RTC error RTIF2 131107 002 Reconstructing the logical domain RTIF2 130528 001 To resolve this problem when you have saved the configuration information of the logical domain and are operating the system with a configuration other than factory default you must reconstruct the logical domain configuration after update of
108. P addresses of the trap hosts are registered by the setsnmp addtraphost or setsnmp addv3traphost command Then executing the showsnmp 8 command displays each of the SNMPv1 SNMPv2 SNMPv2 inform and SNMPv3 trap hosts up to a maximum of 128 entries Similarly suppose that 129 or more entries are registered by the setsnmpusm create setsnmpvacm creategroup setsnmpvacm createview or setsnmpvacm createaccess command Then executing the showsnmpusm or showsnmpvacm command displays no more than 128 entries for a user view group and access OID of scfDomainInfoGroup is duplicated and defined in the MIB definition file for XSCF expansion Therefore any attempt to install the MIB definition file for XSCF expansion in the server management software e g JP1 Integrated Management manufactured by Hitachi may fail If the XSCF BB control cable is faulty or loose or if an XSCF failure occurs it may take several hours to disconnect or reset the power supply of the physical partition PPAR consisting of multiple SPARC M10 4S units Workaround There is no effective workaround When 129 or more data entries are registered by the setsnmp 8 setsnmpusm 8 or setsnmpvacm 8 command without an abnormal end the data entries have been registered successfully Delete the line of text of the duplicated OID from the MIB definition file for XSCF expansion Then install the MIB definition file for XSCF expansion again The line o
109. PARC64 X Chapter 3 Information on Software 43 Table 3 5 List of cpu arch properties that support live migration On Oracle VM Server for SPARC 3 1 or 3 1 0 1 Migrate to Run on SPARC64 X Run on SPARC64 X compatible Run on SPARC64 X Migrate from Run on SPARC64 X generic native generic Run on SPARC64 X compatible generic generic native Run on SPARC64 X Table 3 6 List of cpu arch properties that support live migration For Oracle VM Server for SPARC 3 0 Migrate to Run on SPARC64 X Run on SPARC64 X compatible Run on SPARC64 X Migrate from Run on SPARC64 X native none Run on SPARC64 X compatible none generic native Run on SPARC64 X When executing live migration of the domain with the kernel zone operating from a SPARC M10 system with XCP 2230 or newer the following output is displayed and live migration fails ldm migrate domain ldgl root target name Target Password Failure occurred while preparing domain ldgl for suspend operation Live migration failed because Kernel Zones are active Stop Kernel Zones and retry Timeout waiting for domain ldgl to suspend Domain Migration of domain ldgl failed domain suspend failure Domain Migration of LDom ldgl failed To execute live migration of a domain with kernel zone operating stop the kernel zone beforehand Live migration from a SPARC M10 system with XCP 2210 or newer to another SPARC M10 system with XCP 2092 or older fails and produces the following e
110. PU cores or threads which were not added using the Idm add core command or the Idm add vcpu command This has been modified with SRU11 2 8 and Oracle VM Server for SPARC 3 2 for Oracle Solaris 10 How to restore Use the following process to change the timeout value of starting the ldoms ldmd service to 600 svccfg s Idmd listprop start timeout_seconds count 180 svccfg s Idmd setprop start timeout_ seconds 600 svccfg s Idmd listprop start timeout_seconds count 600 svcadm refresh Idmd svcadm restart Idmd Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 26 Bug 19424242 19424359 19513561 Problems that might occur in any versions of Oracle Solaris and workarounds continued SPARC M10 1 4 4S x xX x x xX x x x x Description On a system to which Oracle VM Server for SPARC 3 1 0 1 or later is applied the following event may occur If all CPUs or memory in an I O domain are degraded due to a CPU or memory failure the Idmd service abnormally terminates and as a result the ldm 1M command terminates with an error If the domain configuration is restored in the degraded configuration both of the following settings are reset to their default values the setting specifying whether to enable disable hypervisor dump collection and the setting specifying whether to enable disable automatic reboot during hypervisor dump collection Default values
111. R is powered on again after the PPAR is forcefully powered off with the poweroff f command while starting up Oracle Solaris Unable to connect to Domain Service providers is output to the OS console and Oracle Solaris may not be started In a system configuration for which power supply interlocking with ETERNUS is set ETERNUS is not powered on even if the power is turned on from the power switch located on the operation panel of the SRARC M10 system In the state where the physical partition PPAR is powered on when switching of the master XSCF occurs it may take time before the standby XSCF switches to the master XSCF As a result the following error may occur Master switch synchronization timeout Workaround Power on the PPAR again with the poweron 8 command after disconnecting the power of the PPAR with the poweroff 8 command If Oracle Solaris does not start up even after that reset the XSCF after disconnecting the power of the PPAR and then power on the PPAR again Turn on the power in one of the following ways XSCF command poweron 8 command Menu on the XSCF Webpage Automatic power turning on with schedule settings There is no effective workaround How to restore If the error occurs during execution of the flashupdate 8 command when the power to the PPAR is on Turn off the power to the PPAR and then execute the flashupdate 8 command again If the error occurs during execution
112. Required only for the control domain Included in group system solaris large server and group system solaris small server 3 Required only for the control domain 4 For Oracle Solaris 11 5 For Oracle Solaris 10 6 If Oracle Solaris 10 1 13 is to be run in the control domain the CPUs that can be assigned to the control domain are those CPUs that are mounted on logical system boards with LSB numbers 0 to 7 There are no LSB number limitations on the CPUs that can be assigned to the guest domain If the Oracle Solaris 10 1 13 is run in the guest domain however up to 1024 CPUs vepus can be assigned to a single guest domain 7 Refer to Notes when using a version older than Oracle VM Server for SPARC 3 1 0 1 8 Refer to Notes on using Oracle Solaris 10 Note When Oracle Solaris 11 1 Oracle Solaris 11 2 is installed or booted from DVD media in a SPARC M10 system the following two messages are displayed Ignore these messages because they have no impact on installation work Message example 1 Dec 21 02 18 22 solaris genunix NOTICE core_log ldmd 1978 core dumped tmp core Dec 21 02 18 22 solaris svc startd 9 ldoms ldmd default failed fatally transitioned to maintenance see svcs xv for details Message example 2 SUNW MSG ID SMF 8000 YX TYPE defect VER 1 SEVERITY major EVENT TIME Fri Dec 21 02 18 50 UTC 2012 PLATFORM ORCL SPARC64 X CSN 2081210008 HOSTNAME solaris SOURCE software diagnosis REV 0 1
113. SCF cannot communicate with each other and the redundancy of the XSCF is not maintained When you specify USB memory for the getflashimage 8 command the following message may be output and the execution of the command may fail Error Unable to mount USB device Workaround For details see Response to FMEM serious error of SPARC M10 4S RTIF2 130711 001 There is no effective workaround However if both of the conditions below can be confirmed the update of the PCI expansion unit firmware has been completed normally In this case ignore the LINKCARD I2C error error message and continue the operation The update of the PCI expansion unit firmware by using the ioxadm 8 command has been completed normally Executing the ioxadm v list command displays the version number of the PCI expansion unit firmware that has been specified for the update There is no effective workaround If the XSCF is not switched even by executing the switchscf 8 command execute the replacefru 8 command to perform active replacement of the XSCF unit that is in the standby chassis Also when you disconnect the XSCF unit disconnect and then connect the XSCF BB control cable After disconnecting and then connecting the USB memory execute the getflashimage 8 command again Chapter 3 Information on Software 141 Table 3 21 SPARC M10 RTI No 1 4 4S RTIF2 x x x 130802 002 RTIF2 x 130826 001 RTIF2 x 130902 001 RTIF2
114. Settings for entire system etc ssh ssh_config Settings per user HOME ssh ssh_config Setting contents Ciphers aesl28 cbc aes192 cbhc aes256 cbhc 3des bc arcfourl28 arcfour256 arcfour blowfish cbc If you use it with the server function sshd 1M etc 1 Add the content of the setting to the target file as one line Target file etc ssh ssh_config Setting contents recommended Ciphers 3des cbc arcfourl28 arcfour256 arcfour blowfish cbc 2 Restart the service with the following command sveadm restart svc network ssh default Ifthe problem cannot be resolved with any of the client function and server function 1 Add the following in place of the above content of the setting UseOpenSSLEngine no Chapter 3 Information on Software 187 If Oracle Solaris is activated during memory degradation a panic may occur CR 15851441 Workaround If a panic occurs due to a memory failure replace the failed memory If a panic occurs due to the memory mirror mode setting start the system from the XSCF by using the following procedure Also if a panic occurs due to a memory failure starting the system from the XSCF by using the procedure shown below may prevent the problem but this method is not always reliable If a panic recurs even after the system is started by using the following procedure replace the failed memory 1 Execute the poweroff 8 command to power off the physical partition PPAR 2 Execut
115. TIF2 131023 005 Problems resolved in XCP 2050 continued SPARC M10 1 4 48 x x x x x x x x x Description You cannot use the PCI hot plug PHP function to add a Quad Gigabit Ethernet card SE1X7GQ2F to a PCI Express slot of a PCI expansion unit In the XSCF e mail notification function the following characters cannot be included in the local part or the domain part of the reply mail address which is sent by the setsmtp 8 command E EB oh Se I ME Ne na onon An ononon me 2 py won If Physical bar is selected on the XSCF Web menu PCI excluding the link card may appear to be abnormal 4 Workaround This has been modified with XCP 2050 and SRU11 1 6 4 0 If XCP and SRU are not applied you must stop the logical domain to which you want to add the PCI card before adding it Precautions To resolve this problem when you have saved the configuration information of the logical domain and are operating the system with a configuration other than factory default you must reconstruct the logical domain configuration after update of the XCP firmware For details see Reconstructing the logical domain RTIF2 130528 001 Use reply mail addresses which do not include the characters shown by the Description There is no effective workaround Even if PCI excluding the link card is indicated as being abnormal ignore it Chapter 3 Information on Software 153 Table 3 24 Problems resolved in XC
116. This problem does not affect system operation Response to FMEM serious error of SPARC M10 4S RTIF2 130711 001 turn on When adding the SPARC M10 45 by following the maintenance menu displayed by executing the addfru 8 command perform Step 1 and then turn on the input power to the target SPARC M10 4S BB x Then after waiting for 50 minutes manually enter f in Step 2 to perform the work Please execute the following steps 1 After the added device is connected with the system the breaker of the BB x 148 please turn on Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 2 Please select f finish Executing the flashupdate 8 command Do not power on the physical partition PPAR during the execution of the flashupdate 8 command If you power on the PPAR during the execution of the flashupdate 8 command power it on again after the completion of the command Upon the completion of the flashupdate 8 command execute the showlogs event command to confirm the following message XCP update has been completed XCP version xxxx last version yyyy Restoration after the SCF Diagnosis initialize RTC error RTIF2 131108 001 How to restore If phenomenon 1 occurs a If the Oracle Solaris time has returned to January 1 2001 execute the setdate 8 command to set the XSCF time again In this case the XSCF is reset After that power off and on the PPAR b If the Oracle Solari
117. When setting up a password equal to or longer than 256 letters use the password option of either the setsnmp 8 or the setsnmpusm 8 command instead of using the password input prompt How to restore If a password equal to or longer than 256 characters has been registered using the password input prompt remove the target user data with either the setsnmp remv3traphost or the setsnmpusm delete command and then register the user again There is no effective workaround There is no effective workaround The system can be operated continuously as it will be restored after being reset There is no effective workaround The slave XSCF will be restored by the reset and the system can be used continuously after that There is no effective workaround Chapter 3 Information on Software 59 Table 3 8 SPARC M10 RTI No 1 4 4S RTIF2 x x x 140212 016 RTIF2 x 140212 021 Description When resetting XSCF the snmpd XXXXX svrSP error doAction ACTION_CONTROL_LED error message regarding SNMP may be displayed on the XSCF serial terminal If any of the physical partitions is reset due to some hardware failure in the middle of the execution of the testsb 8 command the testsb 8 command may terminate abnormally The following is an example of such an error Example XSCF gt testsb PSB_NO Initial diagnosis is about to start Continue y In y SB power on sequence started Initial diagnosis started 7200
118. XML file from Oracle Solaris in advance Execute the Idm list constraints x command to save the logical domain configuration information to an XML file Execute the Idm init system i command to restore the logical domain configuration information from an XML file Also write down in advance the setting information of the OpenBoot PROM environment variable for the control domain and set it again To display the information execute the printenv command in the ok prompt For details of these procedures see 1 7 2 How to save the configuration information and the OpenBoot PROM environment variable in the logical domain and subsequently restore them in the PCI Expansion Unit for Fujitsu M10 SPARC M10 Systems Service Manual If you need to save restore various information when you change the enable disable setting of the direct I O function of PCI expansion units by executing the setpciboxdio 8 command the information in the following table applies Table 2 3 Work for switching the enable disable setting by executing the setpciboxdio command Configuration of PCI Domain configuration Reconstructing Oracle Setting OpenBoot PROM expansion unit VM Server for SPARC environment variables config again Yes No factory default Unnecessary Necessary Yes No Guest domain exists Necessary XML Necessary If you add remove or replace a PCI expansion unit for a PCI slot of SPARC M10 chassis for which the direct I O function of a PCI expansion unit is en
119. a power failure occurring while Oracle Solaris is inactive or the physical partition PPAR is powered off PPAR may erroneously reboot even though the PPAR should remain powered off Note When a power failure occurs while Oracle Solaris is active and a UPS is connected Oracle Solaris will automatically reboot upon power recovery This phenomenon may occur when the operation below is followed by a power failure recurrence and then a recovery therefrom A power failure occurs while Oracle Solaris is active After Oracle Solaris boots automatically upon power recovery the shutdown command is executed on Oracle Solaris to stop Oracle Solaris display the ok prompt Example shutdown y g0 i0 A power failure occurs while Oracle Solaris is active After Oracle Solaris boots automatically upon power recovery the shutdown command is executed on Oracle Solaris to power off the PPAR Example shutdown y g0 i5 x x A PCI Express correctable error may occur if you connect a PCI Express expansion unit connected by PCI Express Gen1 which is an IHV product to aSPARC M10 1 Workaround If you want to stop Oracle Solaris there is no effective workaround To power off the PPAR execute the poweroff 8 command on the XSCF How to restore Execute the poweroff 8 command on the XSCF to power off the PPAR There is no effective workaround Chapter 3 Information on Software 105 Table 3 13 Problems r
120. abled by executing the setpciboxdio 8 command the cases in which you need to save restore information are listed in the following table Note In maintenance on a PCI expansion unit with the PCI hot plug PHP function the direct I O function is disabled Therefore no information needs to be saved restored Table 2 4 Work to be performed after you add remove or replace a PCI expansion unit for a PCI slot of SPARC M10 chassis for which the direct I O function is enabled Maintenance environment Domain configuration Reconstructing Setting OpenBoot Oracle VM Server PROM environment for SPARC config variables again When addition removal is factory default Unnecessary Unnecessary performed by stopping the Guest domain exists Necessary XML Necessary PPAR When a faulty PCI expansion factory default Unnecessary Unnecessary unit 1 is replaced by Guest domain exists Necessary XML Necessary stopping the PPAR Chapter2 XCP 2250 Related Information 23 Table 2 4 Work to be performed after you add remove or replace a PCI expansion unit for a PCI slot of SPARC M10 chassis for which the direct I O function is enabled continued Maintenance environment Domain configuration Reconstructing Setting OpenBoot Oracle VM Server PROM environment for SPARC config variables again When anormal PCI expansion _factory default Unnecessary Unnecessary unit 1 is replaced by Guest domain exists Unnecessary Unnecessary stopping the PPAR
121. ached its full capacity Default Chapter 3 Information on Software 83 Table 3 8 SPARC M10 RTI No 1 4 4S RTIF2 X 141226 001 RTIF2 x x x 150126 001 Description If time synchronization of the master XSCF and the NTP server fails during master standby XSCF switching the XSCF time may deviate and the ntpd may not start If ntpd is not active a message NTP is unavailable is output by executing the showntp 1 command Note that this problem does not occur if the NTP client setting of XSCF and the NTP server setting are disabled If XSCF is reset while the system is operating with the power supply interlocking function enabled the power of an external I O device may be turned off incorrectly Problems that might occur with XCP 2250 and workarounds continued Workaround There is no effective workaround How to restore If ntpd is not active when the NTP client setting of XSCF or the NTP server setting is enabled execute the rebootxscf 8 command to reset XSCF Disable the power supply interlocking function by RCIL and enable it again every time after the power of the physical partition PPAR is turned on This also applies when the power of the PPAR is automatically turned on due to power failure power recovery auto power control system APCS RCIL etc Example XSCF gt setremotepwrmgmt c disable XSCF gt setremotepwrmgmt c enable Perform the following procedure when you cannot perfor
122. acle Solaris time Example Setting of 18 30 00 on June 27 2014 date 0627183014 00 Chapter 3 Information on Software 97 Table 3 10 Problems resolved in XCP 2240 continued SPARC M10 RTINo 1 4 4S Description RTIF2 x In SPARC M10 1 if the power supply 140715 001 unit PSU has a redundant configuration and the power cable connected to one of the power supply units is pulled out a PSU error may be erroneously detected and the SPARC M10 1 chassis Check LED amber may go on At this time executing the showlogs error command outputs the Msg PSU failed log RTIF2 x x x AC input power may be incorrectly 141016 001 determined to have a mix of 100 V and 200 V if any of the power supply units PSU in redundant configuration triggers an AC input error and then power loss recovery repeats in a short time Consequently though system operation may continue when power is recovered two PSUs are degraded with the PSU shortage power off started message displayed and the system stops Workaround There is no effective workaround How to restore Use either of the following procedures How to restore 1 Turn off the power to the SPARC M10 chassis connected to the PCI expansion unit Then disconnect both PCI expansion unit power cables AC OFF Then wait for 30 seconds to reconnect the cables AC ON How to restore 2 Perform pseudo active replacement of the PSU in which the error has been detected tem
123. added format Searching for disks done AVAILABLE DISK SELECTIONS 0 c2t50000394281B5312d0 lt TOSHIBA MBF2600RC 3706 cyl 64986 alt 2 hd 27 sec 668 gt Logical device path name Vendor name Product name pci 8800 pcit4 pcit0 pcit0 scsil 0 iport disk w50000394281b5312 0 Physical device path name dev chassis FUJITSU BBEXP 500000e0e06d31bf 03NO_HDDO0 disk Notes on boot switching by beadm Boot environment switching with the beadm command or with the pkg command may fail with the output of an error message where Oracle Solaris 11 1 or later is installed in the internal SAS disk or the SSD Message example 1 beadm activate S11U1SRU20B04 z_ stress 2 10 1 Error while accessing dev rdsk c2t500003942823F352d0s0 No such file or directory Unable to activate S11U1SRU20B04 z_stress 2 10 1 Error installing boot files Message example 2 beadm activate S11U1SRU20B04 z_ stress 2 10 1 Error while accessing dev rdsk c2t500003942823F352d0s0 No such file or directory Unable to activate S11U1SRU20B04 z_stress 2 10 1 Error installing boot files 40 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Cause This occurred because the MPxIO device path is not properly inherited by beadm or pkg when the internal SAS disk or SSD is made into a multipath type MPxIO Corrective action Execute the following command and then execute the boot environment switching command again
124. address virtual IP address This symptom occurs when a takeover IP address is set up If the addboard 8 or deleteboard 8 command is executed using the DR feature addition or removal of system boards using the DR feature may fail with displaying the following message Failed to evacuate board resources After the detection of a degradation of SPARC M10 chassis if reboot or AC OFF ON is executed on the physical partitions the PSU shortage error message may be mistakenly registered Moreover when the error is detected a Failure mark is attached to the PSU Workaround There is no effective workaround Either specify a trap host name which does not contain the XSCF host name or specify the IP address of the trap host There is no effective workaround Re execute the addboard 8 or deleteboard 8 command If it fails again either reboot the control domain only or reset XSCF using the rebootxscf a command After that re execute the addboard 8 or deleteboard 8 command using the DR feature There is no effective workaround How to restore Execute the following procedures If the Status of the power supply unit PSU has not become Faulted 1 Eliminate the cause of the degradation of SPARC M10 chassis 2 If a Failure mark is attached to the PSU perform AC OFF ON to remove it If the Status of the power supply unit PSU has become Faulted 1 Replace the PSU 2 Perform AC OFF ON
125. ailable available available available 1 It is a system like SPARC M5 M6 which supports Oracle VM Server for SPARC 2 Live migration is possible only for cpu arch generic Notes on a case when recovery mode of Oracle VM Server for SPARC is enabled Suppose that a system disk in a physical partition PPAR PPAR A in which recovery mode is enabled is switched to a system disk that has been used for another PPAR PPAR B The PPAR A domain configuration information held in the XSCF may be overwritten on the PPAR B domain configuration information If you want to use recovery mode to switch the system disk to the system disk that has been used for another PPAR and boot from the new system disk perform the following Uninstall Oracle VM Server for SPARC from the system disk prior to switching After the switch is completed reinstall Oracle VM Server for SPARC on the system disk Suppose that you add a system board using dynamic reconfiguration of physical partitions in the condition where the domain configuration has been recovered in the degraded configuration The added resource is not allocated automatically to any logical domain Allocate the added resource manually Alternatively execute the Idm set spconfig command to select the original domain configuration and then reboot the physical partition using the poweron 8 and poweroff 8 commands Chapter 3 Information on Software 45 46 Suppose that you delete a system board PSB us
126. ain console In the case of SPARC M10 1 SPARC M10 4 or SPARC M10 4S in a single chassis configuration By executing the console 8 command after XSCF resetting you can connect to the control domain console Problems resolved in XCP 2092 The following table lists the problems resolved in XCP 2092 Chapter 3 Information on Software 125 Table 3 17 RTI No RTIF2 131213 015 RTIF2 140110 001 RTIF2 140110 002 RTIF2 140115 001 126 Problems resolved in XCP 2092 SPARC M10 1 4 48 x x x x x x x x Description In case all of the three conditions below are met on a physical partition the crossbar unit XBU error Msg XB XB interface fatal error is detected Condition 1 The physical partition is configured by several SPARC M10 4S Condition 2 The XSCF BB control cables that are connected to the SPARC M10 4S chassis are either defective or have been disconnected In such a case the Msg BB control cable detected unexpected error log is registered Condition 3 The physical partition was rebooted due to a hardware failure the poweron 8 or reset 8 command was executed Moreover XSCF had either rebooted the physical partition due to a hardware failure or had performed retrial of the poweron 8 or the reset 8 command when this symptom occurred previously In a SPARC M10 4S with crossbar box configuration the following event log which notifies power off is not registered
127. al partitions where the version of Oracle VM Server for SPARC is earlier than 3 2 as there is a chance of the logical domain to hang or the deleteboard 8 command to fail Due to this problem memory module DIMM of different capacities cannot be mounted on a chassis which is the target of the dynamic reconfiguration of physical partitions Make sure that the mounted memory modules DIMMs on chassis whose physical partition is the target of dynamic reconfiguration are all of the same capacity Meanwhile there is no problem if the number of DIMMs differs from chassis to chassis Do not apply patches 150400 01 to 150400 06 on Oracle Solaris 10 In such a case dynamic reconfiguration of physical partitions may cause system panic CR 17510986 Notes on mixing SPARC64 X processors with SPARC64 X processors To mix SPARC64 X processors with SPARC64 X processors configure each type in a unit of the SPARC M10 system chassis which is the system board configuration unit SPARC64 X processors cannot be mixed with SPARC64 X processors and mounted together inside each chassis in the SPARC M10 system In the SPARC M10 4 M10 4S there are systems configured with the CPU memory unit lower CMUL and CPU memory unit upper CMUU These units must have the same processor Notes and restrictions on the SR IOV functions Notes Ifthe maintenance of PCI Express PCIe cards that use the SR IOV function is performed either with dynamic reconfigur
128. an obtain the firmware from the SupportDesk Web Global site Please contact your local support provider to obtain the files required for XCP update The following files are provided Firmware program file XSCF Control Package XCP file XSCF extended MIB XSCF SP MIB definition file Note XSCF Control Package XCP XCP is a packaged control program of the hardware that configures SPARC M10 Systems An XCP file includes the XSCF firmware OpenBoot PROM firmware Power On Self Test firmware and Hypervisor firmware Disposal and recycling Note This information is applicable to SPARC M10 systems sold within Japan by Fujitsu For product disposal and recycling paid service contact your sales representatives xii Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Documentation Feedback If you have any comments or requests regarding this document please take a moment to share it with us by indicating the manual code manual title and page and stating your points specifically through the following websites Japanese site http jp fujitsu com platform server sparc manual m Global site http www fujitsu com global services computing server sparc downloads manual Preface xiii xiv Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Chapter 1 Software Requirements This chapter describes the software requirements for using SPARC M10 Systems XCP Oracle S
129. ance is done in off state of the input power supply Support of the Auto Service Request ASR function 02 08 0000 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 1 7 XCP version XCP 2070 XCP 2052 XCP 2051 XCP 2050 XCP 2044 XCP 2042 XCP 2041 XCP 2032 XCP 2031 XCP 2013 XCP 2012 Existing XCP firmware versions and support information continued Main support information Improvement of XCP firmware defects Support of the AES algorithm encryption function for the SNMP agent function Support of different memories in the chassis Improvement of XCP firmware defects Support of the direct I O function for the PCI expansion unit SPARC M10 4S Support of the direct I O function for the PCI expansion unit SPARC M10 1 M10 4 Support of the crossbar box configuration of up to 16 BB Support of the PCI expansion unit Improvements related to the Oracle VM Server for SPARC software Support of SPARC M10 4S configuration of up to 4 BB Improvement of XCP firmware defects Support of SPARC M10 1 M10 4 CMU version 02 07 0000 02 05 0002 02 05 0001 02 05 0000 02 04 0004 02 04 0001 02 04 0001 02 03 0001 02 03 0001 02 01 0003 02 01 0002 Note When the CMU firmware version is updated turn off the power of the physical partition and then turn it on again to complete the CMU firmware update For details on firmware update see 16 1 Updating the XCP Firmware in the F
130. ards 8 command If this phenomenon has occurred the command outputs y for Pwr and Failed for Test Example If the power to the SPARC M10 4S chassis is on and the system board diagnosis indicates an error XSCF gt showboards a PSB PPAR ID LSB Assignment Pwr Conn Conf Test Fault 00 0 00 00 Assigned y n n Failed Faulted When the fan speed is switched due to a change in the intake air temperature an error log indicating an abnormal fan speed may be erroneously registered for a fan that is not faulty Workaround There is no effective workaround Check the error log and perform maintenance on the component There is no effective workaround How to restore Execute the replacefru 8 command and select the fan for which the error log has been registered Follow the replacement instructions on the maintenance menu without replacing the fan 116 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 15 Problems resolved in XCP 2220 continued SPARC M10 RTI No 1 4 4S Description RTIF2 x x x For XCP 2210 or earlier the error log 141106 002 PCI Express link up failed may be erroneously registered and an on board 1 O device or a PCI slot may be degraded if a physical partition PPAR is powered on off after any of the following error logs related to abnormal temperature is registered Temperature out of range error High temperature at SW Hardware access error the
131. aris 10 SPARC M10 45S When the control domain is running on Oracle Solaris 10 with Oracle VM Server for SPARC version 3 1 0 1 or older if the physical partition dynamic reconfiguration PPAR DR feature is enabled the Idoms ldmd service fails to start and Oracle VM for SPARC does not work The PPAR DR feature is enabled at the time of shipment Therefore either disable the PPAR DR feature before setting up logical domains or update Oracle VM Server for SPARC to version 3 1 0 1 or later Configuration of the PPAR DR feature is performed with the setpparmode 8 command of XSCF firmware For details on the setpparmode 8 command refer to Fujitsu M10 SPARC M10 Systems XSCF Reference Manual To update Oracle VM Server for SPARC version to 3 1 0 1 apply patch no 150817 01 after installing Oracle VM Server for SPARC 3 1 SPARC M10 45 When Oracle Solaris 10 is running on the control domain in order to perform dynamic reconfiguration of physical partitions PPAR DR with the deleteboard 8 addboard 8 commands update to Oracle VM Server for SPARC 3 1 1 or newer When updating to 3 1 1 apply patch 150817 02 after installing Oracle VM Server for SPARC 3 1 Notes when using a version older than Oracle VM Server for SPARC 3 1 0 1 SPARC M10 4S When the physical partition dynamic reconfiguration PPAR DR feature is enabled 4 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 on an Oracle VM Server for
132. arting OpenBoot PROM even if an error is detected with the GFX 550e graphics card TechSource PCIExpress Graphics Board nothing may be output to the console The problem can be confirmed from the following error log output with the showlogs error command which registers the faulty component suspect component as UNSPECIFIED 30 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 XSCF gt showlogs error Date MMM DD hh mm ss JST 2014 Code 80000000 00ffffO0000ff0000ff 030000010000000000000000 Status Alarm Occurred MMM DD hh mm ss sss JST 2014 FRU UNSPECIFIED Msg I O device error detected SPARC M10 45 If cold replacement is performed on a system with several SPARC M10 4S and crossbar boxes the XSCF may not start Perform the following procedure depending on the target components for cold replacement Perform the following procedure when replacing crossbar boxes XBBOX 1 Turn off the input power AC OFF of the target XBBOX 2 Replace the XSCF unit XSCFU When performing this procedure swap the microSD card in the old XSCF unit to the new XSCF unit before replacing the XSCF unit itself 3 Turn on the input power AC ON of the XBBOX Perform the following procedure when replacing the following components that are mounted on the crossbar box XBBOX In the following cases replacement of microSD card is unnecessary For details on maintenance refer to Fujijtsu M10 4 Fujitsu M1
133. ation DR of physical partitions or with PCI hot plugging PHP execute the following procedure beforehand 1 Remove all virtual functions VF from the I O domains by executing the Idm remove io command 2 Destroy all virtual functions VF by executing the Idm destroy vf command Regarding maintenance using DR or PHP refer to either Fujitsu M10 4 Fujitsu M10 4S SPARC M10 4 SPARC M10 4S Service Manual or PCI Expansion Unit for Fujitsu M10 SPARC M10 Systems Service Manual Chapter2 XCP 2250 Related Information 13 Regarding details on the Idm command refer to Oracle VM Server for SPARC Administration Guide of the version you are using After performing maintenance with DR or PHP execute the following procedure if necessary 3 Create virtual functions VF by executing the Idm create vf command 4 Assign the virtual functions VF to the I O domains using the Idm add io command The on board LAN interfaces of SPARC M10 systems support the SR IOV feature The static SR IOV feature is supported from Oracle VM Server for SPARC 3 0 onwards The dynamic SR IOV feature is supported from Oracle VM Server for SPARC 3 0 onwards For details on the SR IOV feature refer to Oracle VM Server for SPARC Administration Guide of the version you are using For the necessary fixes when using the SR IOV feature refer to Oracle VM Server for SPARC Release Notes of the version you are using Fora list of PCI cards that s
134. can access to XSCF Web even though the certificate has expired Use the same certificate or create a certificate or import a certificate with the sethttps 8 command 82 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 SPARC M10 RTI No 1 4 4S RTIF2 x x x 141204 001 RTIF2 x xX x 141208 001 Description If the guest domain has been kept active for a long time powering off and then powering on a physical partition PPAR may cause the guest domain time to deviate This phenomenon occurs under the following conditions A guest domain is configured 1 and along period of time passes after the ldm add spconfig command is executed from Oracle VM Server for SPARC 2 and a physical partition power is turned on or reset 1 Time deviation does not occur on the control domain 2 Time deviation comes to about 20 seconds per month Suppose that the audit system is configured so that writing to audit records stops temporarily when the audit trail reaches its full capacity An XSCF shell or XSCF Web operation at this time may lead to an XSCF reset due to the mistaken detection of one of the following errors Hardware access error or SCF panic detected This problem occurs even when the XSCF shell is automatically run regularly to monitor the logical domain status by using PRIMECLUSTER software You can check the contents of the currently set audit system by
135. ce the CPU memory unit lower CMUL on the faulty SPARC M10 4S chassis There is no effective workaround Execute the following procedure to synchronize power control schedule settings for automatic power on off between the master and standby XSCFs 1 Execute the showpowerschedule m list command to confirm that the power control schedule has been registered If no power control schedule has been registered re register it by using the addpowerschedule 8 and setpowerschedule 8 commands 2 Execute the setpowerschedule c control command to enable or disable the power control schedule There is no effective workaround To confirm information on PCI cards installed on the PCI expansion unit execute the showhardconf 8 command with no options installed Problems resolved in XCP 2080 The following table lists the problems resolved in XCP 2080 136 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 20 SPARC M10 RTI No 1 4 4s RTIF2 x 121219 011 RTIF2 x 130305 018 RTIF2 x x x 130305 019 RTIF2 x 130307 001 RTIF2 x 131001 001 Problems resolved in XCP 2080 Description The power of a physical partition PPAR may not be disconnected if deleteboard c unassign is executed to the system board that belongs to the PPAR while the power of the PPAR is being disconnected using the poweroff 8 command An internal error may occur when performing Diagnostic tests when select
136. ckup memory is registered which is related to the PSU backplane PSUBP or XSCF interface unit XSCFIFU The FRU of the error log registered immediately after that error log may not be correct In this case any one of the following messages is displayed to indicate that the FRU PSUBP or XSCFIFU is not correct Msg SCF Diagnosis initialize RTC FRU PSUBP or XSCFIFU or Msg SCF Diagnosis error on XXXX FRU PSUBP or XSCFIFU XXXX indicates any of the following FRUs CPU L2 cache SDRAM RTC SPI FMEM NAND Workaround There is no effective workaround The failed parts are degraded Power on the PPAR again Do not execute the testsb 8 diagxbu 8 or flashupdate c sync command while the flashupdate 8 command is being executed To confirm the completion of the flashupdate 8 command execute the showlogs event command and then check for the following message XCP update has been completed XCP version xxxx last version yyyy There is no effective workaround Replace the FRU as follows For SPARC M10 1 FRU MBU For SPARC M10 4 FRU BB 00 CMUL For SPARC M10 4S FRU BB xx CMUL or FRU XBBOX xx XSCFU Chapter 3 Information on Software 129 Table 3 19 RTI No RTIF2 131112 011 RTIF2 131112 012 130 Problems resolved in XCP 2090 continued SPARC M10 1 4 48 x x x x x x Description If the physical partition PPAR is powered on and then the ioxadm 8 command is executed before the p
137. cle Solaris is activated during memory degradation a panic may occur CR 15851441 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 29 Problems resolved in Oracle Solaris 11 2 continued SPARC M10 Bug 1 4 4S Description 15858713 x x x Ifamemory error occurs and all the 16769782 memories assigned to the guest domain are degraded ldmd 1M causes a core dump to abnormally terminate and the Idm 1M command ends with an error 15887244 x x x When you start the SunVTS 7 0 ps14 and ps15 tests in a SPARC M10 system they may terminate with an error 16238762 x Ifa system board is added to the PPAR by dynamic reconfiguration of physical partitions after booting the Oracle Solaris in the control domain with the factory default configuration or if CPUs on the system board are added to a domain by the Idm add vcpu command after the system board is added by dynamic reconfiguration of physical partitions the system will panic with the following message panic cpuX thread XXXXXXXXXXX mpo_cpu_add Cannot read MD Workaround This has been modified with SRU11 1 10 5 0 On Oracle Solaris 10 it has been modified with Oracle VM Server for SPARC 3 1 If this defect occurs because SRU is not applied replace the memory having an error If you want to start Oracle Solaris while the memory having an error remains to be mounted start it using the following procedure from XSCF 1 Execute t
138. common to all models are described in all chapters describing hardware Therefore when you check the hardware information about multiple models you will find that some contents are duplicated in some chapters Check the information on the PCI expansion unit Chapter 7 when the PCI expansion unit is introduced Contents of revision of documents Chapter 8 are provided in each document Check whether the contents of your document have been revised x Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Related Documentation All documents for your server are available online at the following locations Sun Oracle software related manuals Oracle Solaris and so on http www oracle com documentation Fujitsu documents Japanese site http jp fujitsu com platform server sparc manual Global site http www fujitsu com global services computing server sparc downloads manual The following table lists documents related to SPARC M10 Systems SPARC M10 Systems related documentation 1 Fujitsu M10 SPARC M10 Systems Getting Started Guide 2 Fujitsu M10 SPARC M10 Systems Quick Guide Fujitsu M10 SPARC M10 Systems Important Legal and Safety Information 2 Software License Conditions for Fujitsu M10 SPARC M10 Systems Fujitsu M10 SPARC M10 Systems Safety and Compliance Guide Fujitsu M10 SPARC M10 Systems Security Guide Fujitsu M10 SPARC M10 Systems SPARC Enterprise PRIMEQUEST Common Installation Pla
139. cted during unconfiguration of PSB 00 0 XSCF gt When the OS panics a large volume of panic messages may be sent to the XSCF In this case the XSCF cannot handle the large volume of panic messages As a Workaround If all but one of the PSBs are faulty first turn off the power to the PPAR and then execute the deleteboard 8 command to disconnect the normal PSB How to restore Execute the following procedure 1 Execute the rebootxscf a command to reset the XSCF 2 Check the error logs and messages to identify the cause of the error 3 Eliminate the cause of the error 4 Perform the operation described in 6 3 1 Example operation for unassigning a system board or 6 3 3 Example operation for reserving the unassignment of a system board in the Fujitsu M10 SPARC M10 Systems Domain Configuration Guide There is no effective workaround How to restore The system is restored when the XSCF is reset by codd process failure Chapter 3 Information on Software 77 Table 3 8 RTI No RTIF2 140606 001 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 X 4 4S Description result the codd process fails and OS panic error logs are registered in large quantities as shown below Example OS panic and process failure error logs XSCF gt showlogs error v Date Dec 20 14 44 26 JST 2013 Code 40000000 00ffff0000ff0000ff 01b900060000000000000000 Status Warni
140. ction and then configure it again while the standby XSCF is in failure or using the following procedure starting the changed setting information 1 Execute the setremotepwrmgmt c may not be reflected in the standby XSCF disable command to disable the power even after the start of the standby XSCF supply interlocking function is completed 2 Save the management file and then If XSCF switching occurs in this state the use the clearremotepwrmgmt 8 master XSCF after the switching may not command to initialize the setting be able to achieve power supply information interlocking based on the changed setting If the standby XSCF is starting execute information the clearremotepwrmgmt 8 command after the start is completed If the standby XSCF is in failure use the replacefru 8 command to replace the target FRU and then execute the clearremotepwrmgmt 8 command 3 After the start of the standby XSCF is completed execute the setremotepwrmgmt c config command to restore the setting information based on the saved management file 4 Execute the setremotepwrmgmt c enable command to enable the power supply interlocking function RTIF2 x If all physical partitions PPARs are There is no effective workaround 130109 007 stopped and you try to power ona Tun off the input power supply and turn PPAR the PPAR may not be powered on it back on to all SPARC M10 system with no error log registered chassis and then try to power on the PPAR
141. ctive replacement or hot replacement of the PSU by the replacefru 8 command if any of the following errors re occur on the PSU of the same chassis no error log is registered PSU shortage power off started PSU shortage Wrong PSU is installed When replacing power supply units PSUs with the replacefru 8 command if the f key in the menu of the replacefru 8 command is pressed within 30 seconds after mounting the new PSU any problem in the new PSU cannot be detected The following special characters cannot be included in the mail address input field for the Settings Service SMTP Settings Email Reporting Settings Audit and Settings CoDActivation menus on the XSCF We b ES a o a lt a a a mon i nym nyy mow When using XSCF Web in Internet Explorer if you attempt to delete the second and subsequent User Group settings of Groups and View Access of VACM in the XSCF Settings Service SNMP Security menu an error message is output and the deletion cannot be executed Workaround Execute the replacefru 8 command to perform cold replacement if a PSU is replaced for the first time after any of the error logs shown in Description is registered In such a case do not perform active replacement or hot replacement See Workaround for RTIF2 140304 007 Use the setemailreport 8 command of the XSCF shell Execute the deletion by using XSCF Web in Firefox or the
142. cured Continuous system operation is possible However after switching the master and standby XSCFs normal system operation is not guaranteed This is because information in the old master XSCF is not reflected in the new XSCF If the input power to the standby or slave chassis is turned off a Board control error MBC link error error log may be registered After adding or removing a system board with the dynamic reconfiguration of physical partitions PPAR if the PPAR is powered off the output of the showpparprogress 8 command mistakenly shows the status of the procedure of powering on the system In a system which implements daylight saving time if the current time is changed with the setdate s command to a time that is within one hour of the ending of daylight saving time the time is changed to a time beyond daylight saving time Example Workaround Before turning on the input power confirm that the XSCF DUAL control cable is correctly inserted How to restore Execute the rebootxscf a command to reset all XSCFs There is no effective workaround Ignore this error log There is no effective workaround How to Restore After the PPAR ID x Reset message is output to the event log re execute the showpparprogress 8 command for the right display To set up the local time to something around the daylight saving time use the setdate u command and set the time in UTC 72 Fujitsu M10 SP
143. d Ignore all these outputs To prevent these outputs execute the following command on the ok prompt to change the value of OpenBoot PROM environment variable diag switch to false setenv diag switch false There is no effective workaround If this specific card is mounted on a system conduct any reconfiguration in deactivated state instead of dynamic reconfiguration This has been modified with SRU11 1 8 4 0 and the patch 145648 04 for Oracle Solaris 10 There is no workaround other than applying the modification If this specific card is mounted on a system conduct any reconfiguration in deactivated state instead of dynamic reconfiguration This has been modified with SRU11 1 19 6 0 and the patch 149167 03 for Oracle Solaris 10 Before dynamically reconfiguring a physical partition on which this specific card is mounted activate any unplumbed qlcnic interface with the ifconfig interface_name plumb command Chapter 3 Information on Software 175 Table 3 26 SPARC M10 Bug 1 4 4S x X X x x x x x X x 176 Description If dynamic reconfiguration is performed ona physical partition which has a Dual Port Gigabit Ethernet card MMF SP1X7GD1F 7100482 7100481 connection is terminated When using XCP 2210 the Dynamic Resource Management DRM feature of Oracle VM Server for SPARC does not work When Oracle VM Server for SPARC 3 1 1 1 is installed on the control domain messages li
144. d the exclusive control file open error error message is output and all setups regarding SNMP fail This problem occurs only on XCP 2090 Workaround Update firmware either to XCP 2080 or older or to 2091 or later Problems resolved in XCP 2090 The following table lists the problems resolved in XCP 2090 Problems resolved in XCP 2090 SPARC M10 1 4 4S x x Description The following error log is registered if you remove a XSCF BB control cable when removing a SPARC M10 4S with the initbb 8 command or replace a SPARC M10 4S or an XSCF unit with the replacefru 8 command Msg Board control error MBC link error Msg BB control cable detected unexpected Msg XSCF hang up is detected When you turn on the input power to a crossbar box or SPARC M10 4S after disconnecting it in a system having a building block configuration Board control error MBC link error may be registered in the error log In addition an non existing crossbar box or SPARC M10 4S may be displayed as a faulty unit Workaround There is no effective workaround Ignore the error log This error log is registered when you disconnect the input power supply Ignore this error log Chapter 3 Information on Software 127 Table 3 19 RTI No RTIEF2 130305 009 RTIF2 131023 003 RTIF2 131107 001 128 Problems resolved in XCP 2090 continued SPARC M10 1 4 48 x x x x x x x Description Suppose that 129 or more I
145. d by executing the devinfo 1M command of Oracle Solaris on the raw device of the boot disk In case the EFI GPT disk label is not attached devinfo i dev rdsk c2d0s0 dev rdsk c2d0s0 0 0 73728 512 2 Incase the EFI GPT disk label is attached devinfo i dev rdsk cl1d0s0 devinfo dev rdsk cld0s0 This operation is not supported on EFI labeled devices Notes on live migration of Oracle VM Server for SPARC The sparc64 class1 value of the cpu arch property is being supported from Oracle VM Server for SPARC 3 1 1 onwards For details on the cpu arch property and its configuration options refer to the Reference Manual of your Oracle VM Server for SPARC The values of the cpu arch property which supports live migration differs according to the category of the operation mode of the CPUs on the physical partition and the version of Oracle VM Server for SPARC Please refer to the following table For details on CPU operational modes of physical partitions refer to section 7 2 1 of Fujitsu M10 SPARC M10 Systems System Operation and Administration Guide Table 3 4 List of cpu arch properties that support live migration On Oracle VM Server for SPARC 3 1 1 or later Migrate to Run on SPARC64 X Run on SPARC64 X compatible Run on SPARC64 X Migrate from Run on SPARC64 X generic native sparc64 class1 generic sparc64 class1 Run on SPARC64 X compatible generic sparc64 class1 generic native sparc64 class1 Run on S
146. d detected At this time the logical domain is continuously operated but the functions that access hardware e g power on off monitoring function no longer operate An error log due to hardware is erroneously registered in the following cases A watchdog timeout occurs due to a software factor XSCF RESET switch is pressed XSCF panic occurs due to firmware Example a Complete replacefru 8 command execution by following the maintenance menu b Execute the initbb 8 command to disconnect the chassis from the system If the READY LED of the XSCF or XSCF unit is not lit Remove the chassis and replace the XSCF unit or CPU memory unit lower CMUL where a failure is suspected There is no effective workaround If this phenomenon occurs turn off the input power to all chassis and then turn it on again There is no effective workaround How to restore Turn off the input power to the system and then turn it on again AC OFF ON Do not connect and then disconnect the USB memory while information is being collected into the memory by the snapshot 8 command How to restore Turn off the input power to the system and then turn it on again AC OFF ON There is no effective workaround Read the Alarm status as Notice 70 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 RTI No RTIF2 140410 002 RTIF2 140410 003 RTIF2 140410 005 Proble
147. d then power on again There is no effective workaround Before starting the logical domain disconnect the input power supply and then power it on again There is no effective workaround Disconnect the power by using the poweroff 8 command Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 25 RTI No RTIF2 130329 003 RTIF2 130410 004 RTIF2 130410 005 SPARC M10 1 X X Description If you power off the input power supply while the status of the physical partition PPAR is PowerOn from the startup of Oracle Solaris to the completion of PowerOff an SRAM serious error occurs in any of the SPARC M10 4S units in the PPAR when you next power on the input power supply preventing you from powering on the input power supply The power may not be turned on off from the operation panel Executing the poweron a command leads to the failure of power on if more than one PPAR is powered on or more than one PPAR has failed in the system that has multiple physical partitions PPARs Problems resolved in versions prior to XCP 2050 continued Workaround When you power off the input power supply do so after disconnecting the PPAR power supply in advance and making sure that disconnection is complete How to restore If any problem occurs restore the configuration with the following procedure 1 Save settings with the dumpconfig 8 command 2 Init
148. e access error may be mistakenly detected and the PSU is degraded There is no effective workaround It will not affect the system as it is only a problem of the command output How to restore Re execute the flashupdate 8 command There is no effective workaround How to restore After re connecting or replacing the removed SPARC M10 4S or XBBOX set up the XSCF network again Do not input the two byte characters at the beginning and end of the character strings which produce errors There is no effective workaround How to restore Ignore this error log To dissolve the degraded state of the PSU turn off the input power and turn it on again Chapter 3 Information on Software 121 Table 3 16 SPARC M10 RTI No 1 4 4s RTIF2 x x x 140212 020 RTIF2 x x 140212 023 RTIF2 x x x 140212 024 122 Problems resolved in XCP 2210 continued Description When hot swapping a fan if the fan is installed right after removing it hot swapping may fail If CPU failures like the following occur on a SPARC M10 4 M10 4S to which a CPU memory unit lower CMUL and a CPU memory unit upper CMUU is mounted when starting a physical partition PPAR the Hypervisor Abort error is produced and the PPAR may not be used anymore Incase of SPARC M10 4 if all the CPUs mounted on the CMUL are degraded In case of SPARC M10 4S if all the CPUs mounted on the CMUL on all the chassis that configures the PPAR are d
149. e effective How to restore After replacing the FRU listed in Description perform the following When you power on the physical partition the Oracle Solaris time becomes January 1 2001 Start Oracle Solaris in single user mode and then set the time There is no effective workaround Please adjust the reading to the right sequence Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 15 SPARC M10 RTI No 1 4 4S RTIF2 x x x 140212 004 RTIF2 x x x 140212 006 RTIF2 x x x 140212 022 RTIF2 x 140221 003 RTIF2 xX x x 140227 003 Problems resolved in XCP 2220 continued Description The OID information of scfPPAROsMachine in the definition file of XSCF extension MIB should have a value of sun4v but instead it contains the CMU firmware version information like 02090000 In case of SNMPv1 or SNMPvz if the trap host name which contains the XSCF host name is registered by the setsnmp 8 command the trap host is not displayed by the showsnmp 8 command Example of non displaying with the showsnmp 8 command XSCF host name example com Trap host name test example com If the trap host is registered by specifying the trap type with the t option as inform to the setsnmp addtraphost command the UDP address of the trap that is reported to the trap host becomes the IP address that is assigned to the XSCF LAN physical IP address instead of the takeover IP
150. e of a CPU core activation violation If the PPAR power is off PPAR power on fails because there is an insufficient number of CPU core activations RTIF2 x x x When the firmware update of the PCI 131126 004 expansion unit and link card is complete the firmware version of the PCI expansion unit is erroneously displayed Specifically PCIBOX version of the event log displays the pre update version while last version displays the post update version Example Version displayed after an update from 1120 to 1130 Incorrect LINKCARD 1 bank 1 PCIBOX version 1120 last version 1130 Correct LINKCARD 1 bank 1 PCIBOX version 1130 last version 1120 Workaround After installation replacement the synchronous processing of the CPU core activation keys is performed when the following is executed If the master standby XSCF is not switched Execute the rebootxscf a or addcodactivation 8 command from the master XSCF that requested installation replacement If the master standby XSCF has been switched Execute the switchscf 8 command to return the master XSCF to the pre installation replacement state After that execute the rebootxscf a or addcodactivation 8 command Note Do not perform the following operations before restoring the master XSCF to its original state by executing the switchscf 8 command If these operations are performed it may be necessary to register the CPU core activation key again reb
151. e the left most x80 bit is 0 and the second x40 bit from the left is 0 any of 0 1 2 and 3 Date Jan 13 15 19 40 JST 2015 Code 80000408 00cb000000ff0000Ff 110000256001000000000000 Status Alarm Occurred Jan 13 15 19 40 742 JST 2015 FRU MBU PCI 1 PCIBOX 1111 PSU 0 Msg PSU failed Diagnostic Code 00013131 31310000 0000 00010000 00000000 0000 00010000 00000000 0000 01410800 00000000 00000000 00000000 00000000 00000000 0000 Problems resolved in version 1200 of the PCI expansion unit firmware Workaround There is no effective workaround How to restore Use either of the following procedures How to restore 1 Turn off the power to the SPARC M10 chassis connected to the PCI expansion unit Then disconnect both PCI expansion unit power cables AC OFF Then wait for 30 seconds to reconnect the cables AC ON How to restore 2 Perform pseudo active replacement of the PSU in which the error has been detected temporarily remove the PSU and then reinstall it When performing pseudo replacement of the PSU use the ioxadm 8 command Note that the fieldeng privilege is required to execute the ioxadm 8 command Problems resolved in version 1180 of the PCI expansion unit firmware The following table lists the problems resolved in version 1180 of the PCI expansion unit firmware Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 7 3 Problems resolved in version 1180 of
152. e the poweroff 8 command continues being processed after the XSCF has panicked and reset 78 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 SPARC M10 RTI No 1 4 4S RTIF2 X 140606 004 RTIF2 x 140606 008 Description on one PPAR to forcibly turn off the power to that PPAR the XSCF may slow down panic and then reset Suppose that you execute the addboard 8 and reset por commands to add a system board PSB to a physical partition PPAR that fulfills both of the conditions below You may see an error message No analytical target repeatedly Also Oracle Solaris running on this PPAR may hang up The SPARC M10 4S including a crossbar box has a building block configuration Power is supplied only to a PPAR made up of one PSB Suppose that you are attempting the following Adding a system board PSB with the addboard c configure command using dynamic reconfiguration of physical partitions PPARs or disconnecting a PSB using the deleteboard c unassign or deleteboard c disconnect command If any of the conditions below is fulfilled switching between master and standby XSCFs occurs If the restarting XSCF mentioned in the condition description is the standby XSCF it becomes the master XSCF after the switching However the previous master XSCF is reset and deactivated Condition In the case of addboard The XSCF for the PSB to be added is restarting
153. e 3 9 Problems resolved in XCP 2250 continued SPARC M10 RTINo 1 4 4S Description RTIF2 x x x __ If Ctrl t is pressed in response to the 140407 003 ok prompt that appears after starting OpenBoot PROM the following trap related error message is output on the domain console of the logical domain 10 ok ERROR Last Trap Fast Instruction Access MMU Miss TL 1 TL 1 TT 64 TPC 1056e6f20 TnPC 1056e6 24 TSTATE 4420001600 CWP 0 PSTATE 16 AG 0 IE 1 PRIV 1 AM 0 PEF 1 RED 0 MM 0 TLE 0 CLE 0 MG 0 IG 0 ASI 20 CCR 44 XCC nZvc ICC nZve TL 2 TT 183 TPC f0248e68 TnPC 0200c80 TSTATE 14420001400 CWP 0 PSTATE 14 AG 0 IE 0 PRIV 1 AM 0 PEF 1 RED 0 MM 0 TLE 0 CLE 0 MG 0 IG 0 ASI 20 CCR 44 XCC nZve ICC nZve Omitted Called from f0227228 at 0227240 0 emit Called from lf at f020c3c8 lf Called from If at 020c404 If Called from crlf at f020c424 pop base Called from f0225fe0 at 0226024 pop base Called from f0225fe0 at 0226024 f0225fe0 Called from f0248350 at 024838c 7fffffffffffff9S 80000000fecdaff8 f02081dc Called from f0248350 at 024837c 0 ok RTIF2 x When the showhardconf 8 command is 140808 002 executed after the input power is turned off and then on information on the configuration of components installed on the system may not be recognized RTIF2 x x x NOTICE Unable to get TX queue state 140929 001 is displayed mistakenly if Oracle Solaris is started in the syste
154. e abnormality on the master XSCF the master XSCF may fail to switch over to the standby XSCF and start up as another master XSCF Due to this the system seems to contain two master XSCFs Normal behavior of a system is not guaranteed when there are two master XSCFs in the system This state can be confirmed by a lighted MASTER LED at the rear panel of two chassis While in the process of adding or removing a system board PSB using the addboard 8 or deleteboard 8 command of the DR feature if another physical partition is rebooted due to hardware failure or the poweroff 8 poweron 8 reset 8 command is executed on it the executed addboard 8 or deleteboard 8 command may detect timeout and terminate abnormally Problems that might occur with XCP 2250 and workarounds continued Workaround There is no effective workaround Execute the ioxadm c update command to update the PCI expansion unit firmware again There is no effective workaround How to restore The system can be operated normally when the number of master XSCFs automatically returns to one after a few minutes If the number of master XSCFs does not return to one even after 15 minutes press the RESET switch at the rear panel of all existing SPARC M10 systems and crossbar boxes The system can be operated normally after that Do not execute the poweroff 8 poweron 8 reset 8 command while the addboard 8 or deleteboard 8 command is being executed
155. e confirmed with the following procedure 1 Execute the showsscp a command 2 Check that in the output results obtained in Step 1 Cannot communicate is not displayed for the Address for which the SSCP link network ID network_id is 2 or 4 Example If there is no crossbar box confirm the Address with an SSCP link network ID network_id of 2 XSCF gt showsscp a N 2 Location Address bb 00 if 2 169 254 1 17 bb 01 if 2 169 254 1 18 Similarly if there is a crossbar box confirm the Address with an SSCP link network ID network_id of 4 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 21 Problems resolved in XCP 2070 continued SPARC M10 RTI No 1 4 4S Description RTIF2 x xX x If the SCF Diagnosis initialize RTC 131108 001 error occurs or if the motherboard unit MBU is replaced with the SPARC M10 1 and the CPU memory unit lower CMUL is replaced with the SPARC M10 4 M10 4S the following phenomena may occur Phenomenon 1 The XSCF time may return to January 1 2001 Phenomenon 2 The time difference between the XSCF and all physical partitions PPARs may become a value of 400 million seconds or more You can check this phenomenon by executing the showdateoffset 8 command since the time difference between the XSCF and all PPARs is displayed as a value of 400000000 sec or more XSCF gt showdateoffset a PPAR ID Domain Date Offset 00 400000100 sec 0
156. e may be output and the panic may persist recursive rw_enter lp XXXXXXXX wwwh XXXXXXXX thread XXXXXXXX When the memory fails and is degraded the following message may be output at startup of Oracle Solaris and the panic may persist tilelet_assign_fini_cb tile 0xX in memgrp X was unused This may also occur when you set the mirror mode for the memory after saving the logical domain setting with Idm add spconfig Workaround This has been modified with XCP 2050 and SRU11 1 6 4 0 For XCP 2050 see the description of RTIF2 130528 001 If XCP and SRU are not applied stop the logical domain to which you want add the PCI card before adding it This has been modified with SRU11 1 6 4 0 and the patch 148888 03 for Oracle Solaris 10 Ignoring this message does not have an impact on the system This has been modified with SRU 11 1 12 5 0 and patch 150840 01 for Oracle Solaris 10 Add the following to etc system of the I O domain and restart Oracle Solaris forceload drv vpci Note that if starting of the I O domain is disabled you must change to inactive state the guest domain to which the virtual disk vdisk which is a target of the virtual disk service vds of the I O domain is assigned with the Idm stop domain and ldm unbind domain commands This will enable starting of the I O domain After starting the I O domain set the above This has been modified with SRU11 1 11 4 0 For details see If Ora
157. e showlogs error v command is Msg SP InternalError Occurred and the first 4 bytes of the 5th line of the Diagnostic Code is 01920212 it corresponds to this symptom Example XSCF gt showlogs error v Date Nov 11 18 29 04 JST 2013 Code 40000000 00fcff0000ff0000ff 0186ffff0000000000000000 Status Warning Occurred Nov 11 18 29 04 871 JST 2013 FRU FIRMWARE Msg SP Internal Error Occurred Diagnostic Code 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 0000 0007000b 02040002 00000000 00000000 01920212 00620000 0000 If you execute the reset xir command immediately after starting Oracle Solaris or the ldmd service LDC Protocol info fromPPAR PPAR ID 0 Domain Service Data Send Failed may be registered in the event log and the XSCF process down and reset may occur Workaround There is no effective workaround Please ignore this message There is no effective workaround There is no effective workaround How to restore Execute the showstatus 8 command to check whether a part has failed A CPU whose Status is Deconfigured has failed Follow the maintenance procedure to replace the FRU mounted on the CPU Example When a Deconfigured CPU exists XSCF gt showstatus BB 11 Status Normal CMUU Status Normal CPU O Status Deconfigured There is no effective workaround After XSCF is reset execute the showlogs event command to confirm the event logs Or execute th
158. e showpparstaus 8 command to confirm that the physical partition PPAR was reset If the physical partition has not been reset execute the reset xir command again Chapter 3 Information on Software 135 Table 3 19 Problems resolved in XCP 2090 continued SPARC M10 RTI No 1 4 4S Description Workaround There is no effective workaround RTIF2 x Suppose that an XSCF failure occurs on 140605 003 one SPARC M10 4S chassis in a physical partition PPAR and the CHECK LED is on and the READY LED is off on the XSCF If you attempt to power on this PPAR the system erroneously judges that an error has occurred on every SPARC M10 4S chassis in this PPAR and you cannot power on the PPAR RTIF2 x When you add or replace one SPARC 140605 004 M10 4S chassis BB 00 or BB 01 or crossbar box chassis XBBOX 80 or XBBOX 81 power control schedule settings for automatic power on off are not synchronized between the existing and additional replacement chassis If master standby XSCF switching is performed in this state automatic power on off is not performed because the power control schedule settings remain unavailable RTIF2 x x x When the showhardconf u command is 140617 001 executed on a system connected to a PCI expansion unit the number of PCI cards installed on the PCI expansion unit is erroneously displayed as 11 the maximum number of cards that can be Follow the maintenance procedure for XSCF failures to repla
159. e the setdomainconfig 8 command to place the PPAR in the factory default state XSCF gt setdomainconfig p ppar_id c default 3 Execute the poweron 8 command to activate the PPAR Oracle Solaris is started in the factory default configuration which consists of only control domains If you set the mirror mode for the memory configure a logical domain after setting the mirror mode in the factory default condition Then save the settings with Idm add spconfig In addition you must not specify with Idm set config or the setdomainconfig 8 command of XSCF the settings that were saved with no mirror mode set to the environment where the mirror mode is used 188 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Chapter 4 Information on SPARC M10 1 Hardware This chapter describes special instructions and problems concerning the SPARC M10 1 hardware Notes and Restrictions Problems with Hardware and Workarounds Notes and Restrictions Notes on using external DVD drive USB bus power drive is not supported for external DVD drives connected via USB Notes on using USB memory Prepare a USB memory as a medium in advance if you execute the command specifying the USB memory as a destination of saving data among XSCF commands When connecting a USB memory to the USB port for XSCF directly connect it to the USB port If you connect the USB memory via the USB hub or USB extension cable it may cause a
160. eboard 8 command Disconnect the PSB where an error is detected from the PPAR configuration by using the deleteboard 8 command Specify the IP addresses of XSCF LAN 0 and XSCF LAN 1 of the master XSCF and the standby XSCF for IPAddress and SlaveAddress respectively There is no effective workaround Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 25 RTI No RTIF2 130219 008 RTIF2 130227 001 RTIF2 130305 005 RTIF2 130305 008 RTIF2 130305 010 RTIF2 130305 021 Problems resolved in versions prior to XCP 2050 continued SPARC M10 1 4 4S X Description If you turn on the input power supply to a SPARC M10 4S chassis while a physical partition PPAR is being powered on in a system that has multiple PPARs the SPARC M10 4S chassis for which the input power supply is turned on may not be recognized by the master XSCF If you collect a snapshot by specifying the a option XSCF Kernel Panic may occur due to the increased load on the master XSCF If XSCF panic occurs in a SPARC M10 4S while processing the diagnose by the POST after a physical partition PPAR is powered on in the system that has more than one SPARC M10 4S chassis then the power may be disconnected without continuing the process of powering on the PPAR If each physical partition PPAR is configured with one system board PSB in the system that has more than one SPARC M
161. egraded After executing the Idm add spconfig or the Idm set spconfig command on Oracle Solaris if the auto boot environment variable of OpenBoot PROM is changed the set value does not show up when the XSCF showpparpara m 8 command is executed The value that existed before executing the Idm add spconfig or Idm set spconfig command is displayed This symptom occurs when the following procedures are conducted in the following sequence 1 Start the physical partition PPAR 2 Execute the Idm add spconfig command from the control domain of the started PPAR to save the configuration information of the logical domain Or execute the Idm set spconfig command from the control domain of the started PPAR to specify the name config name of the configuration information of the logical domain that is to be used at the time of the next starting of the PPAR 3 From Oracle Solaris on the control domain execute eeprom auto boot xxxx to change the environment variable of the OpenBoot PROM or change the OpenBoot PROM environment variable from the OpenBoot PROM itself Workaround When replacing a fan after removing it wait for at least 10 seconds before reinstalling it There is no effective workaround Replace the CMUL on which the failed CPUs are mounted There is no effective workaround However the value itself has been enabled Check the value of the OpenBoot PROM environment variable auto boot
162. elete I O devices without stopping the logical domains and without delayed reconfiguration on Oracle Solaris 11 2 SRU11 2 8 or later After dynamic reconfiguration of a physical partition the execution results of prtdiag 1M command executed from the control domain may differ from the actual physical configuration Executing svcadm restart picl can update to the latest information While adding or removing system boards with the addboard 8 or deleteboard 8 command of the DR feature do not reboot all the XSCFs with either the rebootxscf a command or from the XSCF Web interface If such an operation is performed not only the DR processing will terminate abnormally Oracle Solaris on a running physical partition may hang hardware failure may occur physical partitions may stop abnormally and replacement of parts may become necessary If even one logical domain in the OpenBoot PROM state is situated in the physical partition dynamically reconfiguring the physical partition causes it to end with an 12 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 error Execute dynamic reconfiguration of the physical partition after changing the logical domain to any of the following states state where Oracle Solaris is running bound state or inactive state Do not specify either unbind resource or unbind shutdown at the m option of the deleteboard 8 command when executing dynamic reconfiguration of physic
163. em 6 Connect the power cord of the crossbar box to the input power supply For details see 5 4 Connecting Cable to Crossbar Box in the Fujitsu M10 SPARC M10 Systems Installation Guide Wait until STANDBY LED on the operation panel of the crossbar box turns on 7 Execute the diagxbu command to perform diagnosis of the newly installed crossbar box XSCF gt diagxbu y b XX t YY t ZZ Specify the BB_IDs 00 to 15 of SPARC M10 4S that is powered off in XX YY and ZZ 8 Execute the showlogs command to confirm that no error occurred during the diagnosis 194 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 XSCF gt showlogs error 9 Confirm that there are no faulty components XSCF gt showstatus Restrictions on adding expansion rack 2 Addition of a crossbar box using the addfru 8 command is not supported at present To add a crossbar box see the 9 4 Installing Expansion Rack 2 in the Fujitsu M10 SPARC M10 Systems Installation Guide and read Steps 17 and 18 as follows 17 Connect all power cords of the crossbar box and SPARC M10 4S to the input power supply For details see 5 2 Connecting Cable to SPARC M10 4 SPARC M10 4S and 5 4 Connecting Cable to Crossbar Box 18 Update the firmware to the same version as the master XSCF XCP 2040 or earlier XSCF gt getflashimage file media usb_msd images XCPxxxx tar gz XSCF gt flashupdate c update m xcp s version XCP 2041
164. em solaris small server 3 Required for the control domain and other domains 4 Can be used only in domains other than the control domain 5 Required only for the control domain 6 There are patches required other than the Oracle VM Server for SPARC patch For details see Required Oracle Solaris OS Versions for Oracle VM Server for SPARC 3 1 1 1 in the Oracle VM Server for SPARC 3 1 1 1 3 1 1 and 3 1 Release Notes Software supporting Software on Chip The Software on Chip SoC on the SPARC64 X SPARC64 X processor can be used with the software below When used with Oracle Database Table 1 4 Software supporting Software on Chip when used with Oracle Database Function Operating environment The decimal floating point Oracle Database 12c or later arithmetic processing Oracle Solaris 11 1 or later Oracle Number SIMD In memory processing Oracle Database 12c Enterprise Edition Oracle Database In Memory Oracle Solaris 11 1 or later Cryptographic processing Oracle Database 12c Enterprise Edition Oracle Advanced Security Oracle Solaris 11 1 or later 6 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 When used with user application Table 1 5 Software supporting Software on Chip when used with user application Function Operating environment The decimal floating point Oracle Solaris Studio 12 4 or later arithmetic processing Oracle Solaris 11 2 SRU12 2 4 or later IEEE754 SIMD How to
165. emporarily suspended proceed y In y Start unconfigure preparation of PSB 1200sec Oend Unconfigure preparation of PSB has completed Start unconfiguring PSB from PPAR 7200sec ON Workaround This has been modified with SRU11 2 8 and Oracle VM Server for SPARC 3 2 for Oracle Solaris 10 How to restore Hypervisor abort may be caused from the operation of adding removing memory to from PPAR DR or a logical domain after the Idoms ldmd services are recovered Therefore execute the poweroff 8 command for XSCF firmware to power off the physical partition PPAR then execute the poweron 8 command to power on the PPAR There is no effective workaround How to restore If this problem occurs when dynamically deleting a system board take the following action 1 Use delayed reconfiguration to delete resources related to the system volume you want to delete from the system volume in use that has the problem 2 Reboot the domain in 1 3 Dynamically delete the system board from XSCF Note that this operation does not need to be carried out on other domains Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 26 Bug Problems that might occur in any versions of Oracle Solaris and workarounds continued SPARC M10 1 4 4S x x x x x x Description The removal of PCIEO from the domain primary failed Error message from svc ldoms agents in domain primary
166. ems and their workarounds for all versions of the PCI expansion unit firmware continued Workaround Restart the physical partitions PPARs or I O domain or reinstall the 6Gbps SAS card by PHP When the device can be recognized from Oracle Solaris ignore this error message Problems resolved in version 1200 of the PCI expansion unit firmware The following table lists the problems resolved in version 1200 of the PCI expansion unit firmware Chapter 7 Information on PCI Expansion Unit Hardware 199 Table 7 2 SPARC M10 RTI No 1 4 RTIF2 x x 150225 001 200 4S Description x _ Ifthe input voltage drops instantaneously on the system with the PCI expansion unit connected a failure of the power supply unit PSU of the PCI expansion unit may be detected by mistake and the Check LED amber of the PCI expansion unit may go on You can confirm this symptom with the showlogs error v command If the execution result of the showlogs error v command is Msg PSU failed or PSU failed PSU shortage and the fourth line of the Diagnostic Code has the following values the symptom corresponds to this problem 1 Fourth byte the left most x80 bit is 0 any of 0 1 2 3 4 5 6 and 7 and 2 Fourth byte the seventh x02 bit from the left is 0 any of 0 1 4 5 8 9 c and d and 3 Fifth byte the left most x80 bit is 0 any of 0 1 2 3 4 5 6 and 7 and 4 Seventh byt
167. ems that might occur with XCP 2250 and workarounds continued SPARC M10 RTI No 1 4 4S RTIF2 x x x 131213 019 Description While XSCF is starting after being powered on watchdog timeout may occur and XSCF is reset After this reset is completed the configuration information of the components mounted on the system cannot be checked by the showhardconf 8 command Moreover error logs regarding the following configurations may be registered Msg Indispensable parts are not installed PSU Msg Indispensable parts are not installed FAN Msg Indispensable parts are not installed OPNL Msg PSU shortage Msg FAN shortage Workaround There is no effective workaround How to restore Re execute power off and on Chapter 3 Information on Software 57 Table 3 8 RTI No RTIF2 131213 022 RTIF2 140121 001 RTIF2 140212 003 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 X X Description After firmware update if the XCP version is checked by the version 8 command or the XSCF Web interface versions of each crossbar box XBBOX or the XCP of SPARC M10 4S BB may not be the same as the updated XCP version In the following example although the firmware has been updated to XCP2052 from XCP 2042 the XCP of XCPO Reserve of BB 00 has not been updated XSCF gt version c xcp v XBBOX 80 XSCF 0 Master XCPO0 Reserve 2052 XSCF 02
168. enly shown as SLOT2 Moreover the virtual functions created from the physical functions of the PCI cards that are mounted on SLOT4 or higher cannot be assigned to logical domains Example of command output Idm Is io I NAME TYPE BUS DOMAIN STATUS SYS PCI1 SLOT5 PCIE PCIE1 primary OCC pci 8100 pci 4 pci 0 pci 1 pci 0 pci 0 pci 0 pci 1 pci 0 pci 10 pci 0 pci 1 network 0 network 0 1 SYS PCI1 SLOT2 IOVNET PFO PF PCIE1 primary pci 8100 pci 4 pci 0 pci 1 pci 0 pci 0 pci 0 pci 1 pci 0 pci 10 pci 0 pci 1 network 0 maxvfs 7 When using XCP 2210 the Dynamic Resource Management DRM feature of Oracle VM Server for SPARC does not work Problems that might occur in any versions of Oracle Solaris and workarounds continued Workaround This has been modified with SRU11 2 8 and Oracle VM Server for SPARC 3 2 for Oracle Solaris 10 During delayed reconfiguration execute the Idm remove io command after executing the Idm add io command This has been modified with SRU11 2 1 5 0 and the patch 151265 03 for Oracle Solaris 10 This has been modified with SRU11 2 2 and the patch 150817 03 for Oracle Solaris 10 This has been modified with SRU11 2 8 and Oracle VM Server for SPARC 3 2 for Oracle Solaris 10 Update the XCP firmware to XCP 2220 or later Chapter 3 Information on Software 171 Table 3 26 Bug 19074260 19310540 19310550 172 Problems that might occur in any versions of Oracle Sola
169. er PPAR is rebooted 1 Execute the showdateoffset 8 command before powering on or rebooting the PPAR and confirm the time difference between XSCF and the hypervisor 2 If the time difference is too large execute the resetdateoffset 8 command with the PPAR at stopped state in order to reset the time difference 3 After powering on the PPAR reset the time of Solaris OS RTIF2 x Due to the retry functionality of XSCF if There is no effective workaround 131213 020 any abnormality occurs in the recoverable How to restore backup memory inside the PSU backplane PSUBP for more than three times XSCF regards it wrongly as a fixed error and the starting of XSCF may be deterred In such a case the REBOOT COUNTER ERROR message is displayed Re execute power off and on 134 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 19 RTI No RTIF2 131216 001 RTIF2 140303 001 RTIF2 140410 004 RTIF2 140410 006 SPARC M10 1 4 48 x x x x x x x x x x x x Problems resolved in XCP 2090 continued Description The XCP update is started message is mistakenly displayed when the flashupdate c check command is executed Response may become slow when using XSCF Web If a CPU error occurs while powering on a physical partition PPAR an erroneous error log may be registered This symptom can be confirmed by using the showlogs error v command If the result of th
170. er switch on the operation panel is pressed powering on off the physical partition PPAR becomes disabled The power to the PPAR is turned on off when The power switch on the operation panel is manipulated The poweron 8 or poweroff 8 command is executed PPAR power on off operation is performed on XSCF Web Power supply interlocking by RCIL takes place The auto power control system APCS issues a power on off instruction RTIF2 x x x An Event Log Host stopped is not 140731 001 displayed by a showlogs 8 event and showmonitorlog 8 when the primary domain is shutdown RTIF2 x If the system board is deleted by the 140805 001 dynamic reconfiguration of physical partitions a process on the logical domains may produce a core dump by SIGILL Illegal Instruction Workaround To operate the power switch on the operation panel immediately after turning on the input power wait at least 30 seconds after the STANDBY LED switches from blinking to being constantly on There is no effective workaround There is no effective workaround 104 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 13 RTINo RTIF2 140808 001 RTIF2 140808 004 Problems resolved in XCP 2230 continued SPARC M10 1 x x 4 4S Description On a SPARC M10 system to which an uninterruptible power supply UPS is connected the following problem may occur After recovery from
171. ersion 2250 May 2015 Table 3 23 RTI No RTIF2 130717 001 Table 3 24 RTI No RTIF2 130219 002 RTIF2 130305 016 RTIF2 130319 002 Problems resolved in XCP 2051 SPARC M10 1 4 4S x x x Description If an error occurs in the USB SSD in the XSCF interface unit XSCFIFU of the PSU backplane PSUBP or crossbar box the System backup memory access error error log may be registered In this case a problem such as the inability to execute the poweron 8 command or the inability to collect data with the snapshot 8 command may occur Problems resolved in XCP 2050 SPARC M10 1 4 48 x x x x x Description When maintaining SPARC M10 4S with a slave XSCF if you incorrectly connect the standby XSCF and the slave XSCF with an XSCF connection cable the maintenance is considered to have finished normally without detecting the error Timeout may occur if the XCP firmware version of a SPARC M10 4S or crossbar box is updated using the flashupdate c sync command Before power off of the physical partition PPAR completes in SPARC M10 4S if you power off and then power on the input power supply of a SPARC M10 45 or a crossbar box again and power on the PPAR again the PPAR in operation may be powered off if the master XSCF is switched with the switchscf 8 command firmware update or failure Workaround There is no effective workaround When this problem occurs power off the input power
172. es 02 23 0000 Support for Internet Explorer 10 and 11 in XSCF Web 02 23 0000 Support for Extensible Firmware Interface GUID Partition Table EFI GPT labels Support for recovery mode provided by Oracle VM Server for SPARC 3 1 Support for the function for dynamically reconfiguring PCIe endpoint devices through combination with Oracle VM Server for SPARC Support for Oracle Solaris kernel zones Improvement of XCP firmware defects 02 22 0000 Support of the dynamic reconfiguration DR function of 02 22 0000 the system board in a physical partition PPAR Support for XSCF startup mode function SPARC M10 1 Support for SPARC64 X processors 02 21 0000 Support for CPU operational mode which specifies how a CPU should operate Enable the factory default configuration for the dynamic reconfiguration of physical partitions feature The LDAP Active Directory LDAP over SSL features have been supported for the XSCF user account The SR IOV feature in combination with Oracle VM Server for SPARC has been supported The no io feature when configuring physical partition has been supported Improvement of XCP firmware defects 02 09 0000 Improvement of XCP firmware defects 02 09 0000 Support of 64 GB memory 02 09 0000 Support of multiple specifications of the port and community string for the Trap host of the SNMP agent function Support for automatic XCP firmware version synchronization between chassis when mainten
173. es d pos es de SPARC International Inc aux Etats Unis et dans d autres pays Tout autre nom mentionn peut correspondre a des marques appartenant a leurs propri taires respectifs Si ce logiciel ou la documentation qui l accompagne est conc d sous licence au Gouvernement des Etats Unis ou toute entit qui d livre la licence de ce logiciel ou l utilise pour le compte du Gouvernement des Etats Unis la notice suivante s applique U S GOVERNMENT END USERS Oracle programs including any operating system integrated software any programs installed on the hardware and or documentation delivered to U S Government end users are commercial computer software pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplication disclosure modification and adaptation of the programs including any operating system integrated software any programs installed on the hardware and or documentation shall be subject to license terms and license restrictions applicable to the programs No other rights are granted to the U S Government Avis de non responsabilit les seules garanties octroy es par Oracle et Fujitsu Limited et ou toute soci t affili e de l une ou l autre entit en rapport avec ce document ou tout produit ou toute technologie d crits dans les pr sentes correspondent aux garanties express ment stipul es dans le contrat de licence r gissant le produit ou la techn
174. escription If XSCF switching or an XSCF reset occurs while the physical partition PPAR is being powered off it may be impossible to turn off the power If a hardware failure occurs in a 4BB or greater configuration automatic cluster switching may fail If 16 or more guest nodes are incorporated into a single cluster the following warning message may be output to the console of the control domain If XSCF switching occurs while multiple physical partitions PPARs are being powered on at the same time it may take more than usual to power them on If the following applies I O devices error detected is detected at the time of PPAR power on and control domain reboot In SPARC M10 4 M10 4S the CPU memory unit upper CMUU is added to a configuration that has been operated with only the CPU memory unit lower CMUL and false has been set as the IOreconfigure setting of the physical partition PPAR If XSCF switching is performed using the switchscf 8 command in rare cases the standby XSCF may not start Workaround There is no effective workaround While powering off PPAR do not use the switchscf 8 command to perform XSCF switching or the rebootxscf 8 command to perform an XSCF reset If automatic cluster switching fails follow the procedure in the manual of the cluster software to perform switching manually There is no effective workaround Do not switch an XSCF by using the switchscf 8 command while
175. esolved in XCP 2230 continued SPARC M10 RTINo 1 4 4S Description RTIF2 x x x When an attempt is made to install 140813 001 Oracle Solaris via vnet installation menu activation may take one hour or more in the following case the network speed between the SPARC M10 system chassis and the installation server is exceeding 1 Gbps or the system consists of multiple SPARC M10 45s Example Network installation on a SPARC M10 4S via vnet 0 ok boot net dhcp install Boot device virtual devices 100 channel devices 200 network 0 dhcp File and args install lt time unavailable gt wanboot info WAN boot messages gt console lt time unavailable gt wanboot info configuring virtual devices 100 channel devices 200 network 0 dhcp lt time unavailable gt wanboot info Starting DHCP configuration lt time unavailable gt wanboot info DHCP configuration succeeded lt time unavailable gt wanboot progress wanbootfs Read 368 of 368 kB 100 lt time unavailable gt wanboot info wanbootfs Download complete Wed Aug 13 06 24 51 wanboot progress miniroot Read 4864 of 243471 kB 1 1 1 This step takes time RTIF2 x If the system board is deleted by the 140815 001 dynamic reconfiguration of physical partitions DR the monitoring of Host Watchdog for logical domains may stop RTIF2 x x x When the XSCF is restarted or the input 140819 001 power is turned on again the following problem may in rare cases occur ntpd is
176. execute the 1 Remove PSU n 2 Execute either the following 2 1 After installing the exchanged device please select finish 2 2 If you want to suspend the maintenance without exchanging device please select cancel f finish c cancel if want to continue r replace c cancel r following steps How to restore If both PSUs become Deconfigured without performing workarounds active replacement of the PSUs cannot be done with the replacefru 8 command Maintenance Replacement Menu Please select a FRU to be replaced Status PSU 0 PSU 1 Deconfigured Deconfigured Select 1 2 b back Warning 307 PSU 1 cannot be replaced Select 1 2 b back 2 Warning 307 PSU 1 cannot be replaced Please verify the configuration Chapter 3 Information on Software 87 To restore after removing the replaced PSUs without the replacefru 8 command use the replacefru 8 command to replace the PSUs Problems resolved in XCP 2250 The following table lists the problems resolved in XCP 2250 Table 3 9 Problems resolved in XCP 2250 SPARC M10 RTINo 1 4 4S Description Due to the failure of a DIMM the CPU internal fatal error which suspects the motherboard unit MBU CPU memory unit lower CMUL or the CPU memory unit upper CMUU may be registered when powering on the physical partition PPAR RTIF2 x xX x 140212 013 RTIF2 x x x 140227 004 If a link card is removed from the system by PC
177. f text to be deleted is that in which scfDomainInfoGroup containing scf MIBObjectGroups 14 is defined Example For the MIB definition file for XSCF expansion XSCF SP MIB_2050 mib delete the following lines 3558 to 3566 3558 scf DomainInfoGroup OBJECT GROUP 3559 OBJECTS 3560 scfDomainNumber scfPPARId scfDomainName 3561 scfDomainStatus 3562 3563 STATUS current 3564 DESCRIPTION 3565 A collection of objects providing PPAR information 3566 scf MIBObjectGroups 14 There is no effective workaround Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 19 SPARC M10 RTI No 1 4 4S RTIF2 x 131112 002 RTIF2 x x x 131112 003 RTIF2 x x x 131112 008 Problems resolved in XCP 2090 continued Description Suppose that the system uses a crossbar box and contains two or more physical partitions PPARs each consisting of 2BB or more In this system if a hardware failure that affects all the PPARs occurs the failed part is degraded such that the PPAR reactivation processing may fail causing all the PPAR power supplies to remain turned off If the testsb 8 diagxbu 8 or flashupdate c sync command is executed during the execution of the flashupdate 8 command the error log FMEM serious error is registered and the testsb 8 diagxbu 8 or flashupdate c sync command may fail Suppose that the error log SCF Diagnosis error on System ba
178. f the system ignore it There is no effective workaround Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 26 Bug Table 3 27 Bug 18615814 Problems that might occur in any versions of Oracle Solaris and workarounds continued SPARC M10 1 4 4S Description RA PA SIZE 0x10000000 0x7b0fc0000000 1G minimum RA 0x400800000 0x7f01a0800000 11G a b The maximum RA is the sum of a b which will be 0x6c0800000 0x400800000 0x2c0000000 11G 0x6c0800000 The difference between the maximum RA and the minimum RA is 27400 MB 0x6c0800000 0x10000000 0x6b0800000 27400 MB Therefore the remainder is 8 MB in this example 27400 MB 64 MB 428 and the remainder is 8 MB Workaround Problems that might occur with Oracle Solaris 11 and workarounds The following table lists the problems that might occur with Oracle Solaris 11 and workarounds for them Problems that might occur with Oracle Solaris 11 and workarounds SPARC M10 1 x 4 x 4S Description x An I O domain may output the following message and Oracle Solaris panic may occur if a PCIe end point device is dynamically removed from the I O domain executing the Idm remove io command panic cpuX thread XXXXXXXXXXXX mutex_exit not owner lp XXXXXXXX owner X thread XXXXXXXXXXXX Workaround This has been modified with SRU11 2 8 Execute the svcadm 1M command on the I O domain to disable
179. ffective workaround Information on PCI Expansion Unit Hardware 203 Table 7 4 RTI No RTIF2 140902 001 RTIF2 140902 002 Problems resolved in version 1170 of the PCI expansion unit firmware continued SPARC M10 1 X x Description If input power for the PCI expansion unit is disconnected AC OFF or power failure occurs a PSU Information level error log is supposed to be registered However a failure level error log Alarm is incorrectly registered At this point CHECK LED on the front of the PCI expansion unit lights up Faulted is displayed on the PSU status and the error message AC Fail is displayed You can check the error message of this phenomenon by executing the showlogs error command and check the status by executing the showhardconf command Error message example XSCF gt showlogs error Date Jul 10 16 25 02 JST 2014 Code 80000400 00d4000000ff0000F 1100002a0000000000000000 Status Alarm Occurred Jul 10 16 24 57 269 JST 2014 FRU BB 0 PCI 8 PCIBOX 2003 PSU 1 Msg AC FAIL PSU status example XSCF gt showhardconf Omitted PCIBOX 2003 Status Normal Ver 1150h Serial 2121152003 Omitted PSU 1 Status Faulted Serial FEJD1201000170 Link card fault may be incorrectly registered if logs related to one PCI expansion unit are registered more than once in a short time 5 to 10 minutes when one or more physical partitions PPAR are operating in t
180. ffset this problem has occurred Example XSCF gt showdateoffset a PPAR ID Domain Date Offset 00 424915200 sec 01 424915200 sec 02 424915200 sec 03 424915200 sec Omitted 15 424915200 sec If the crossbar cable in the crossbar unit XBU of SPARC M10 4S fails the name of the failed component is wrongly displayed with the showstatus 8 command The numerical and alphabetical part of the component name is displayed in the reverse order Example In case of crossbar cable number OL Wrong display CBL L0 Status Deconfigured Right display CBL 0L Status Deconfigured Workaround Use the following procedure to replace an FRU listed in Description If the setting specifying the XSCF as an NTP client is disabled This problem will not occur Perform the ordinary replacement procedure If the setting specifying the XSCF as an NTP client is enabled 1 Disconnect the LAN cable from the XSCF LAN port and then perform replacement 2 After the XSCF starts connect the serial cable to the serial port Do not connect the LAN cable at this time 3 Disable the setting specifying the XSCF as an NTP client You need to reset the XSCF to make your change effective 4 Execute the setdate 8 command to set the XSCF time After this the XSCF is reset 5 Connect the LAN cable to the XSCF LAN port 6 Enable the setting specifying the XSCF as an NTP client You need to reset the XSCF to make your chang
181. free 26M Lgroup resources 1 CPU 10 11 memory Latency 21 15825208 x x x InSPARC M10 Systems the scp 1 sftp 1 and ssh 1 commands of Oracle Solaris may generate an error or installation of Oracle RAC may fail Workaround This has been modified with SRU11 1 7 5 0 If this defect occurs because SRU is not applied execute the command again In addition when executing Idm remove vcpu execute it in such a condition that the process load is low This has been modified with Oracle Solaris 11 1 SRU5 5 and the patch 150400 01 for Oracle Solaris 10 Add the following line to etc system and restart Oracle Solaris set lgrp_topo_levels 2 This has been modified with Solaris 11 1 SRU1 4 For details see An error occurs in executing the scp 1 sftp 1 or ssh 1 command of Oracle Solaris or the installation of Oracle RAC fails CR 15825208 Chapter 3 Information on Software 181 Table 3 29 SPARC M10 Bug 1 4 4S 15826052 x x x 15840018 x X x 15851224 x x x 15851441 x x x 182 Problems resolved in Oracle Solaris 11 2 continued Description You cannot use the PCI hot plug PHP function to add a Quad Gigabit Ethernet card SE1X7GQ2F to a PCI Express slot of a PCI expansion unit When the firmware is updated to XCP2031 or later the following message is displayed when starting Oracle Solaris NOTICE skipping unsupported token fjorclnum When starting the I O domain the following messag
182. g block configuration if the following operations are performed during power on of the physical partition PPAR connection to the control domain console may not be possible 1 XSCF for any of the SPARC M10 4S units constituting PPAR is reset 2 Switching of the master XSCF and standby XSCF occurs 3 XSCF of the SPARC M10 4S that was reset in 1 is reset again If XSCF of SPARC M10 4S belonging to the physical partition PPAR in operation is reset due to a panic or watchdog timeout while the master XSCF and the standby XSCF are restarting simultaneously connection to the control domain console may not be possible If the XSCF load is high the following warning message may be output indicating the power supply unit PSU as a suspected location Insufficient FAN rotation speed PSU voltage out of range error PSU output current too high PSU over temperature warning Workaround Ignore the registered event log because the PPAR has been normally powered off There is no effective workaround Reset the master XSCF using the switchscf 8 command There is no effective workaround Power off the PPAR by using the poweroff f command and then power it on again There is no workaround This is a warning message so you can operate it as it is Ignore the message Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 24 RTI No RTIF2 130528 001 RTIF2 130903 005 R
183. he showpciboxdio 8 command For details on the setpciboxdio 8 and showpciboxdio 8 commands see Fujitsu M10 SPARC M10 Systems XSCF Reference Manual or the manual page for each command 197 Table 7 1 RTI No RTIF2 130703 001 RTIF2 130703 002 RTIF2 130703 003 RTIF2 130703 004 198 Problems with PCI Expansion Units and Workarounds This section describes problems regarding the PCI expansion unit as well as the workarounds for them for each version of the PCI expansion unit firmware Problems and their workarounds for all versions of the PCI expansion unit firmware The following table shows problems that might occur in any versions of Oracle Solaris being supported and workarounds for them Problems and their workarounds for all versions of the PCI expansion unit firmware SPARC M10 1 4 4S x x x x x x x x Description When installing a PCI expansion unit by PCI hot plug PHP among PCI expansion unit slots 6 7 10 and 11 those without HBA will have command execution result disconnected instead of empty for the Oracle Solaris cfgadm 1M command Although the display is not appropriate the slots work normally if you mount HBA This phenomenon does not occur if you restart the logical domain after connecting the PCI expansion unit When you install a PCI expansion unit with PCI hot plug PHP there may be lane degrade When you install a PCI expansion unit by PCI hot plug PHP
184. he PCI expansion unit or the PCI card a number other than that of the relevant PCI card number PCI is displayed in the error log If Console path is switched is registered in the event log of a system in which the physical partition PPAR consists of multiple system boards PSBs the PPAR ID may have an invalid value If you use the replacefru 8 command to replace a power supply unit PSU Indispensable parts are not installed PSU may be registered in the event log Problems resolved in versions prior to XCP 2050 continued Workaround Wait for the power on off or reset of the PPAR to complete and then execute the prtfru 8 command again There is no effective workaround There is no effective workaround After switching of the master XSCF is performed power off the input power supply of all SPARC M10 4Ss and power them on again without powering on the PPAR Read it as the number obtained by subtracting one from the PCI number PCI displayed in the log There is no effective workaround This is an error log that is registered because a PSU is removed Ignore it Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 25 Problems resolved in versions prior to XCP 2050 continued SPARC M10 RTI No 1 4 4S Description Workaround RTIF2 x Ifyou change the setting information of Disable the power supply interlocking 130109 006 the power supply interlocking function fun
185. he configuration with PCI expansion units connected For details see Confirmation method of RTIF2 140902 002 Workaround Update the PCI expansion unit firmware to 1170 or later and the XCP firmware to XCP 2220 or later There is no impact on system operation from this phenomenon Ignore this error message because there is no impact on system operation 204 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Confirmation method of RTIF2 140902 002 The phenomenon of RTIF2 140902 002 can be checked in the following ways 1 The phenomenon of RTIF2 140902 002 can be checked in the following ways FRU displays LINK or LINKBD Msg displays TWI access error The first byte in the fourth line of the Diagnostic Code is 07 Example of incorrect registration XSCF gt showlogs error v Date Dec 20 10 50 05 JST 2013 Code 80000480 001 010021 f 00cc01 11000057d000000000000000 Status Alarm Occurred Dec 20 10 49 59 136 JST 2013 FRU MBU PCI 1 LINK MBU PCI 1 LINK MGCBL MBU PCI 1 PCIBOX 3001 LINKBD Msg TWI access error Diagnostic Code 00010000 00000000 0000 00010000 00000000 0000 00013330 30310000 0000 07100000 00000000 00000000 00000000 AA 00000000 00000000 0000 2 When the showlogs event command or showlogs error command are executed on the same PCI expansion unit within 10 minutes multiple logs shown below are registered 12 or more event logs related to the
186. he information of the CPU Activation key is also initialized When executing the restoredefaults 8 command save the CPU Activation key in advance before restoring it or register the key again In addition when you replace a CPU memory unit or motherboard the CPU Activation key may be erased For details see Notes on maintenance for CPU memory units motherboard unit XSCF unit PSU backplane or crossbar backplane unit If you execute the restoredefaults c xscf command on XCP 2041 or later the information of the CPU Activation key is deleted not only from the XSCF unit but also from the backup information in the XSCF On the other hand even if you execute the restoredefaults c factory command the information of the CPU Activation key is not deleted To initialize all settings to factory defaults including the information of the CPU Activation key use the c factory r activation option XSCF setting information saved by the dumpconfig 8 command contains CPU Activation information and CPU Activation keys You can use the restoreconfig 8 command to restore the CPU Activation information and CPU Activation keys that were saved with the dumpconfig 8 18 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 command Therefore if you configure CPU Activation or install a CPU Activation key when configuring settings for the XSCF such as when configuring an XSCF network or physical partition PPAR we reco
187. he poweroff 8 command to turn off the power of the physical partitions PPARs 2 Execute the setdomainconfig 8 command to restore PPARs to their factory default state XSCF gt setdomainconfig p ppar_id c default 3 Execute the poweron 8 command to start the PPARs Oracle Solaris is started in the factory default configuration which consists of only control domains This has been modified with Oracle Solaris 11 1 SRU4 6 and the patch 149395 02 for Oracle Solaris 10 There is no workaround other than applying the modification This has been modified with SRU11 1 7 5 and Oracle Solaris 10 patch 150400 12 Meanwhile when this fix has been applied to the system if a system board is added to the system by means of the dynamic reconfiguration of physical partitions the following message may be output but as it has no effect on the system ignore it WARNING mpo_cpu_add defaulting to lgroup x for CPU x For the control domain or the domain whose CPU is added by the Idm add vcpu command add the following line to the domain s etc system file and reboot the Oracle Solaris set suspend_count 1 Chapter 3 Information on Software 183 Table 3 29 Bug 16292272 17510986 17627526 184 Problems resolved in Oracle Solaris 11 2 continued SPARC M10 1 4 48 x x xXx x x x x Description If you configure many guest domains in a system where 16 BBs compose one physical partition PPAR it takes time to
188. he setlIdap 8 command Setting values for the LDAP over SSL client set with the setldapssl 8 command Configuration setting values for the Active Directory set with the setad 8 command Setting values for the SNMP agent set with the setsnmp 8 setsnmpusm 8 setsnmpvacm 8 command Setting values for the SMTP service set with the setsmtp 8 command Problems that might occur with XCP 2250 and workarounds continued Workaround There is no effective workaround How to restore Execute the following procedure 1 Before saving the XSCF setting information with the dumpconfig 8 command confirm the following settings Setting for power operation at power recovery recover mode Example Not powering on at power recovery XSCF gt showpowerschedule a m state PPAR ID schedule member recover mode 0 enable 4 off ASR function Service Tag enable disable setting XSCF gt showservicetag Enabled PPAR DR feature enable disable setting Example Disabled XSCF gt showpparmode p 0 Omitted PPAR DR Current PPAR DR Next _ off Power supply interlocking group setting Saving configuration and setting changes Example Saving management file to ftp server when registering one power supply interlocking group XSCF gt getremotepwrmgmt G 1 ftp server port path file Power supply interlocking function enable disable setting Example Enabled XSCF gt showremotepwrmgmt Remo
189. ialize the system to the factory default with the restoredefaults c factory command 3 Confirm that the READY LED of XSCF or XSCF unit is lighted up after performing AC OFF ON 4 Replace the CPU memory unit lower CMUL or the motherboard unit MBU 5 Restore the configuration with the restoreconfig 8 command If you power on from the XSCF shell execute the poweron 8 command If you power off from the XSCF shell execute the poweroff 8 command How to restore If this event occurs power off the physical partition PPAR by using the poweroff f command Specify the p option to execute the poweron 8 command and turn on the power of each PPAR How to restore If this event occurs execute the poweroff f command to forcefully power off the PPAR whose power has stopped being supplied during the middle of the power supply process Then execute the poweron p command to power on the PPAR Chapter 3 Information on Software 167 Table 3 25 SPARC M10 RTI No 1 4 4S RTIF2 X 130410 006 RTIF2 x 130410 007 RTIF2 x x 130415 001 RTIF2 X X x 130416 001 RTIF2 X 130417 001 168 Description If a crossbar box has failed in the system that satisfies all the following conditions a crossbar box may be degraded and the operation may not be continued Two or more crossbar boxes are configured Multiple PPARs are configured Each physical partition PPAR is configured with multiple CPU memory
190. ibes notes and restrictions that are known as of this release 11 Notes on Secure Socket Layer SSL 3 0 For security reasons you cannot use SSL 3 0 with XCP 2240 or later Use Transport Layer Security TLS 1 0 Restrictions on audit The log file transfer function of the audit log set with the setaudit archive command and the setaudit disable command is not supported at present Ifthe policy for writing to an audit record is set to stop temporarily suspend degradation due to an error may occur or the XSCF may be reset In the setaudit 8 command specify overwriting count by default for the write policy for the audit trail For details of this problem see RTIF2 141208 001 From XCP 2250 onwards specifying suspend invokes the same behavior as specifying count Notes on dynamic reconfiguration of physical partitions Incase of dynamic reconfiguration of physical partitions when adding an I O device it is necessary to either stop the domain or use the delayed reconfiguration feature to integrate the I O device into the logical domain after executing the addboard 8 command Moreover when removing an I O device after removing the I O device by stopping the domain or using the delayed reconfiguration feature execute the deleteboard 8 command in order to disconnect the system board For details on each procedure refer to the Fujitsu M10 SPARC M10 Systems Domain Configuration Guide Note that you can add and d
191. ime and if the start time of a logical domain shifts correct the time on the NTP Execute firmware update when the physical partition PPAR is powered off Chapter 3 Information on Software 145 Table 3 21 RTI No RTIF2 131004 002 RTIF2 131004 003 146 Problems resolved in XCP 2070 continued SPARC M10 1 4 4s x x Description If in a system configured with 3 BB or greater the chassis of the master XSCF and the standby XSCF are turned off and then on again the system enters a state in which there is no master XSCF If the master XSCF is stopped while the XSCF DUAL control cable is either faulty or not connected master standby XSCF switching is suppressed so that the standby XSCF is not switched to the master XSCF If master standby XSCF switching occurs while the XSCF DUAL control cable is either faulty or not connected switching may be performed even though communication between the master and standby is not guaranteed If an XSCF is configured and master standby XSCF switching is performed while the XSCF DUAL control cable is either faulty or not connected the information set in the XSCF will be erased Workaround There is no effective workaround Update to firmware version XCP 2070 or later There is no effective workaround Perform master standby XSCF switching while the XSCF DUAL control cable is connected normally Whether the XSCF DUAL control cable is connected normally can b
192. incidental or consequential damages even if advised of the possibility of such damages DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS REPRESENTATIONS AND WARRANTIES INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE OR NON INFRINGEMENT ARE DISCLAIMED EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID Copyright 2007 2015 Fujitsu Limited Tous droits r serv s Oracle et ou ses affili s ont fourni et v rifi des donn es techniques de certaines parties de ce composant Oracle et ou ses affili s et Fujitsu Limited d tiennent et contr lent chacun des droits de propri t intellectuelle relatifs aux produits et technologies d crits dans ce document De m me ces produits technologies et ce document sont prot g s par des lois sur le droit d auteur des brevets et d autres lois sur la propri t intellectuelle et des trait s internationaux Ce document le produit et les technologies aff rents sont exclusivement distribu s avec des licences qui en restreignent l utilisation la copie la distribution et la d compilation Aucune partie de ce produit de ces technologies ou de ce document ne peut tre reproduite sous quelque forme que ce soit par quelque moyen que ce soit sans l autorisation crite pr alable d Oracle et ou ses affili s et de Fujitsu Limited et de leurs ventuels conc dants de licence Ce document bien qu il vous ait t fourni
193. ing BB with the replacefru 8 command or executing the testsb 8 command If you check the error log at this time you can see that no PSB available in PPAR was registered in PPAR 30 when the internal error occurred Diagnosis continues even when an error occurred on the testsb 8 command and timeout occurs after a two hour wait If any SPARC M10 4S that is specified with the diagxbu 8 command is not implemented the message PSB xx 0 is not installed showing the PSB No that represents the unimplemented SPARC M10 4S should appear However the PSB No of the SPARC M10 45 which actually has been implemented may be erroneously output If the SPARC M10 4S or the crossbar box is disconnected with the initbb 8 command and then all chassis are turned off and then on again with the XSCF BB control cable left connected the chassis disconnected with the initbb 8 command will become the master chassis and the XSCF settings will be initialized to the factory defaults Workaround After executing the poweroff 8 command confirm that the status field of the relevant PPAR shows Powered Off by using the showpcl 8 command Then execute the deleteboard 8 command An error occurred in the applicable SPARC M10 4S and the system board PSB is in an unavailable state Check the error log and replace the SPARC M10 4S Execute the showboards 8 command in another session while executing the testsb 8 command to check the statu
194. ing the deleteboard 8 command where the version of Oracle VM Server for SPARC is earlier than 3 2 while the physical partition PPAR is powered on after the domain configuration is recovered in the degraded configuration This deleteboard 8 command may fail After a domain configuration is recovered in the degraded configuration do not delete a system board using dynamic reconfiguration of physical partitions Suppose the firmware is updated to XCP 2230 or later and the recovery mode supported in Oracle VM Server for SPARC 3 1 1 1 or later is enabled If the physical partition is started with the logical domain configuration information created with XCP 2221 or earlier after those operations the following message may be output to the console of the physical partition warning Configuration xxxx could not be imported from the system controller This is because the recovery mode of the logical domain configuration information created with XCP 2221 or earlier is not enabled Execute the Idm add spconfig command of Oracle VM for SPARC on the control domain and save the logical domain configuration information Notes on a case where openssl is used Oracle Solaris provides accelerated cryptographic libraries for SPARC M10 systems These libraries can be used by using the PKCS11 engine of OpenSSL See man pages openssl 5 engine 3openssl and evp 3openssl or the following OpenSSL documents http www openssl org docs crypto engine htm
195. isplay the tree There is no effective workaround Chapter 3 Information on Software 117 Table 3 16 SPARC M10 RTI No 1 4 4S RTIF2 x x x 131213 004 RTIF2 x 131213 008 RTIF2 x 131213 009 RTIF2 x 131213 021 118 Problems resolved in XCP 2210 continued Description If the PPAR DR feature is enabled disabled on XSCF Web selecting the PPAR Operation PPAR Mode Configuration menu selecting PPAR DR Current or PPR DR Next and clicking Configure a wrong dialogue box appears and the PPAR DR feature is not enabled disabled In a configuration with 3 or more BBs or with crossbar boxes after XSCF switchover occurs due to some problems on the master XSCF while the addboard c configure command is running the deleteboard 8 command executed on the new master XSCF may not get any response This symptom occurs if two master XSCFs exist on a system after a master standby switchover of XSCFs Reference RTIF2 131213 001 This state can be confirmed by a lighted MASTER LED at the rear panel of two chassis The Failed to evacuate board resources message may be output when the addboard 8 or deleteboard 8 command of the DR feature is executed and the addition or removal of system boards with DR feature fails The timeout error log Timeout detected during unconfiguration of PSB xx x may be registered and an abnormal termination may occur when a system board PSB is removed by the deleteboard
196. istered The suspected location indicated by this error log is incorrect SCF Board control error link failed In case of a system comprising of several SPARC M10 45 if input power is turned off and on AC OFF ON on a number of SPARC M10 4S chassis while some other slave chassis are running the physical partitions may not start While a physical partition PPAR is operating or when a PPAR is turned off master standby XSCF switching may occur If master standby switching occurs the following message is displayed on the console of the master XSCF Kernel panic not syncing MBC Dual ifcut interrupt If data is transmitted via SSH by the snapshot 8 t command this transmission may be delayed by about 10 to 30 minutes in comparison with transfer using USB devices and XSCF Web Suppose that multiple physical partitions PPARs are simultaneously started by the poweron a command The error message Error storing configuration variable LDC is not up Configuration variable setting will not persist after a reset or power cycle may be output to the OS console after the message Unable to connect to Domain Service providers Oracle Solaris may be started without applying the OpenBoot PROM environment variable specified with the setpparparam 8 command Workaround When you use the replacefru 8 command to replace the XSCF unit the following message may appear after you replace the XSCF unit If it does wait for 10
197. ith the f option only for a power supply unit Configuring a memory mirror setting by using the setupfru 8 command should be done when the physical partition PPAR to which the target system board PSB belongs is powered off To display a man page set TERM vt100 for the terminal software When configuring a physical partition PPAR do not set a BB ID that does not exist in the system as the PPAR ID For example if BB IDs 00 and 01 exist in the system you can set 00 or 01 as the PPAR ID If you set 02 as the PPAR ID the PPAR with PPAR ID 02 becomes unable to start Among the information displayed by executing the showhardconf 8 command the PCI Express PCIe card information of the guest domain will be reflected after Oracle Solaris of the corresponding guest domain has started As of XCP 2032 the default value for the power save operation set by the setpparmode 8 command is changed from enabled to disabled When you execute the testsb 8 or diagxbu 8 command a PPAR ID of PPAR 30 that does not exist may appear in an error log suspected area This indicates that an error was detected on the system board PSB while diagnosing The output PPAR ID does not have any meaning We recommend to connect the control domain console via the XSCF LAN port When a large amount of data is output by connecting to the control domain console via a serial port the data may not be displayed properly SPARC M10 4S The time taken fo
198. ke the following will be registered to the log file var svc log Idoms ldmd default log of the ldoms Idmd service Example of the messages Get Device ID command failed Unknown 0x7E ERROR Cannot connect to BMC No response time from the migration source domain may become long because a different process from the original live migration is performed during live migration Network services and the like operating on the migration source domain may time out because of no response This case occurs if the migration source domain meets both of the following conditions The difference between the maximum RA of the migration source domain actual address and its minimum RA cannot be divided by 64 MB The remainder is 32 MB or less when the difference between the maximum RA of the migration source domain and its minimum RA is divided by 64 MB The maximum RA and the minimum RA of the domain can be checked with the following command Example Idm list domain o memory domain name NAME domain name MEMORY Problems that might occur in any versions of Oracle Solaris and workarounds continued Workaround There is no effective workaround If this specific card is mounted on a system conduct any reconfiguration in deactivated state instead of dynamic reconfiguration Update the XCP firmware to XCP 2220 or newer There is no effective workaround As this error message has no effect on the functioning o
199. l http www openssl org docs crypto evp html Please note The PKCS11 engine is the only way in OpenSSL to obtain the acceleration of cryptographic functions from the encryption arithmetic unit of the SPARC64 X processor The implementation of PKCS11 engine for OpenSSL in Oracle Solaris requires the enabling of EVP model for digest and encryption methods supported by engine The following digest methods have been optimized for the SPARC64 X processor SHA1 SHA224 SHA256 SHA384 SHA512 The following encryption methods have been optimized for the SPARC64 X processor DES CBC DES EDE3 CBC DES ECB DES EDE3 AES 128 CBC AES 192 CBC AES 256 CBC AES 128 ECB AES 192 ECB AES 256 ECB AES 128 CTR AES 192 CTR AES 256 CTR Here is an example on calling the accelerated version of AES method on SPARC64 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 x openssl speed engine pkcs11 evp AES 256 CBC The following public key encryption methods have been optimized for the SPARC64 X processor from Oracle Solaris 11 2 RSA512 RSA1024 RSA2048 DSA512 DSA1024 DSA2048 The following is an example of the command to invoke the RSA2048 method optimized for the SPARC64 X processor openssl speed engine pkcs11 rsa2048 To use the optimized digest method or encryption method in the PKCS11 engine with an application using the OpenSSL library libssl libcrypto enable the EVP interface explained in evp
200. le in such a case is changed from XCP 2250 as follows Message prior to XCP 2250 0 ok boot Boot device disk File and args Can t open boot device ERROR boot read fail 0 ok 0 ok boot Boot device disk File and args Can t locate boot device ERROR boot read fail 0 ok Message XCP 2250 or later Chapter2 XCP 2250 Related Information 15 0 ok boot No viable default device found in boot device variable 0 ok Notes on maintenance for CPU memory units motherboard unit XSCF unit PSU backplane or crossbar backplane unit SPARC M10 1 SPARC M10 4S When replacing a motherboard unit or a PSU backplane mounted on SPARC M10 1 or when replacing an XSCF unit or a crossbar backplane unit mounted on a crossbar box if any of the following conditions are true execute the following procedures to solve the problems reported in RTIF2 130806 001 which has been fixed in XCP 2220 lt Condition 1 gt XCP firmware version is XCP 2210 or older lt Condition 2 gt The microSD card of the old motherboard unit or the old XSCF unit is not used As XSCF firmware writes onto the microSD card mounted on the FRUs if the XSCF firmware is XCP 2210 or older the following procedure is necessary because failing to do so will result in the occurrence of the problem reported in RTIF2 130806 001 If the setting specifying the XSCF as an NTP client is disabled Perform the ordinary replacement procedure
201. left inactive and as a result synchronization of the XSCF time with the NTP server time fails To confirm whether ntpd is inactive execute the showntp 1 command If the message NTP is unavailable appears ntpd is inactive This problem does not occur if the setting specifying the XSCF as an NTP client or NTP server is disabled Workaround Install Oracle Solaris from a vdisk or DVD ROM created using an ISO image After the system board is deleted to restart the monitoring of Host Watchdog reboot one of logical domains in the physical partition PPAR There is no effective workaround How to restore If the setting specifying the XSCF as an NTP client or NTP server is enabled and ntpd is inactive execute the rebootxscf 8 command to restart the XSCF 106 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 13 RTINo RTIF2 140910 001 Table 3 14 RTI No RTIF2 140611 001 RTIF2 140617 002 Problems resolved in XCP 2230 continued SPARC M10 1 4 4S x Description Workaround If Oracle Solaris 11 2 and later is running There is no effective workaround and the system board is deleted by dynamic reconfiguration of physical partitions Hypervisor may abort Problems resolved in XCP 2221 The following table lists the problems resolved in XCP 2221 Problems resolved in XCP 2221 SPARC M10 1 4 48 x x x x x Description Security fixes CVE 2014
202. lems resolved in XCP 2220 continued SPARC M10 RTI No 1 4 4S Description Workaround RTIF2 x Suppose you execute the setaudit a If user account default is not displayed 140407 004 command to set the user audit policy for User Policy in the output result of and then reset the XSCF In this case the the showaudit all command execute the audit policy of the registered user may be _ setaudit a command to set the audit used as the audit policy of the user policy of the user account default account default and the audit policy of Example User account the registered user may be erased This Set the audit policy for default occurs when the user account default XSCF gt setaudit a default enable has no set audit policy How to restore Example Setting an audit policy for Execute the following procedure yyyyy user 1 Execute the setaudit a command to XSCF gt setaudit a yyyyy disable reset the user audit policy that had XSCF gt showaudit all been used as the audit policy of the Omitted user account default User policy 2 Execute the rebootxscf 8 command to yyyyy disabled reset XSCF Events 3 Execute the showaudit all command to AEV_AUDIT_START enabled confirm that the set user audit policy is XSCF gt rebootxscf a displayed for User Policy XSCF gt showaudit all Omitted User policy default disabled Events AEV_AUDIT_START enabled RTIF2 x The Dynamic Resource Management There is no effective
203. lization and may not work the dynamic resource management DRM on large domain system where 150 domains or more exist Security fixes CVE 2014 3566 For detail see the Oracle website relating to the following Critical Patch Updates In some rare cases CPU Internal Serious error might occur After a CPU fatal error occurs the time required for a physical partition PPAR restart may be 6 to 30 minutes longer than usual The required restart time varies depending on the number of mounted PCIe cards If many PCIe cards are mounted the following error may be mistakenly detected In the case of a SPARC M10 4S system consisting of 2BB or more SRAM data error In the case of a SPARC M10 1 M10 4 systemv gt Timeout of Reset Watch PPARID 0 Workaround There is no effective workaround Ignore this message because there is no impact on system operation There is no effective workaround Update the XCP firmware to XCP 2240 or later There is no effective workaround There is no effective workaround How to restore If SRAM data error has been detected Replace the component at the suspected location indicated by the error log After that update the XCP firmware to XCP 2240 or later If Timeout of Reset Watch PPARID 0 has been detected Update the XCP firmware to XCP 2240 or later RTIF2 140711 001 additional information This problem RTIF2 140711 001 has been resolved for XCP 2240 and later
204. logs error v Date Dec 17 15 50 11 JST 2013 Code 10000400 009eff0000ff0000ff 110000440000000000000000 Status Information Occurred Dec 17 15 50 06 930 JST 2013 FRU BB 0 PCI 3 LINK LINKCBL 1 Msg LINKCBL failed Diagnostic Code 00030001 00000000 0000 00030000 00000000 0000 00030000 00000000 0000 00001000 00000000 00000000 00000000 00000000 00000000 0000 Problems resolved in version 1130 of the PCI expansion unit firmware The following table lists the problems resolved in version 1130 of the PCI expansio unit firmware Chapter 7 Information on PCI Expansion Unit Hardware n 207 Table 7 6 SPARC M10 RTI No 1 4 4S RTIF2 x x x 131120 001 208 Description If an external factor causes an instantaneous voltage drop or the like an error in the power supply unit PSU of the PCI expansion unit is erroneously detected and the error log Msg PSU failed may be registered Moreover if the erroneous detection of this PSU error occurs simultaneously in two PSUs of the PCI expansion unit the physical partition PPAR is shut down You can use the showlogs error v command to check whether this problem is due to an instantaneous voltage drop caused by an external factor Suppose that the execution result for this command is Msg PSU failed and that the first second and third bytes on the fourth line of Diagnostic Code have the following values The problem may be due to for example an instantaneous v
205. m PA physical address displayed on the same line How to delete a memory area Execute Idm remove memory lt total value of above SIZEs gt lt domain name gt It has been modified with Oracle Solaris 11 2 and the Oracle Solaris 10 patch 150400 18 Chapter 3 Information on Software 185 Table 3 29 Bug 18112775 186 Problems resolved in Oracle Solaris 11 2 continued SPARC M10 1 4 4S x x x x x x Description When Oracle VM Server for SPARC 3 1 0 1 SRU11 1 14 is installed on the control domain if dynamically assigned memory is reduced from a guest domain which is running Oracle Solaris 10 with the Idm set memory or the Idm remove memory command the Idmd 1M command on the control domain may produce a core dump and it may be restarted If Java VM is started on aSPARC M10 system with SPARC64 X processors the following message may be output along with the production of a core dump Example of message Internal Error output cpp 1576 pid 1310 tid 91 guarantee int blk_starts i 1 blk_starts i gt current_offset blk_offset failed shouldn t increase block size lt gt Abort core dumped Moreover due to the production of the core dump by Java VM the following events may occur 1 On a SPARC M10 system with SPARC64 X processors the Add Asset operation on Solaris fails 2 On a SPARC M10 system with SPARC64 X processors installation of Solaris
206. m configured with Oracle Solaris kernel zones Workaround There is no effective workaround How to restore From the ok prompt execute the reset all command to restart OpenBoot PROM 0 ok reset all There is no effective workaround How to restore Execute the rebootxscf a command to reset all XSCFs There is no effective workaround Ignore this message Chapter 3 Information on Software 89 Table 3 9 SPARC M10 RTINo 1 4 4s RTIF2 x x x 141111 001 Problems resolved in XCP 2250 continued Description On SPARC M10 1 M10 4 or SPARC M10 4S in a single chassis configuration the content of the scheduled operation setting for automatic power on power off is lost and automatic power on power off becomes disabled It occurs even when the PSU backplane PSUBP and the microSD card or the PSU backplane unit PSUBPU and the microSD card are not replaced at the same time as shown in the following procedure 1 Turn off the input power AC OFF and replace PSUBP or PSUBPU 2 Turn on the input power AC ON and start XSCF 3 Turn off the input power AC OFF and replace the microSD card on the mother board unit MBU or CPU memory unit lower CMUL Note that this problem occurs even if the microSD card is replaced first Workaround After the first FRU is replaced disable the scheduled operation and then enable it again to transfer the contents of the scheduled operation to the replacing FRU E
207. m this workaround due to a system operation issue When two or more SPARC M10 systems are registered to the power supply interlocking group Do no reset XSCF at the same time as XSCF resetting of other SPARC M10 system When only a single SPARC M10 system is registered to the power supply interlocking group Perform either 1 or 2 below 1 Disable only the power off of the power supply interlocking function 1 Execute setremotepwrmgmt c disable to disable the power supply interlocking 2 Specify 0x01 for the Linkage value in the management file of the power supply interlocking Example 1 1 0x01 00000000000000000000000000000011 0x01 0x00 10 20 300 40 0x20 aa bb ce dd e0 f0 5525001 1 2 0x10 00000000000000000000000000000022 0x01 0x00 10 20 300 41 0x20 aa bb cc dd 84 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 RTI No RTIF2 150129 001 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 X 4 4S Description 1 If the input voltage drops usually a power failure notification is issued and the power of the physical partition is turned off However if the input voltage of SPARC M10 1 drops instantaneously no power failure notification is issued and the power of the physical partition is turned off 2 If you execute the console 8 command to switch to the control domain console and input texts
208. minutes and then enter f The replacement of XBBOX xx XSCFU has completed normally f finish Replace the XSCF unit of the same crossbar box by using the replacefru 8 command again If you have turned off the input power AC OFF during the replacement work disconnect and then connect all the XSCF BB control cables When performing AC OFF ON do so on all the chassis comprising a system How to Restore Turn off input power of all the chassis comprising the system and then turn on the input power There is no effective workaround As a result of this defect master standby switching occurs but this does not affect the system and the system can be operated continuously There is no effective workaround Even if transfer is delayed there is no problem with the collected data There is no effective workaround Restart the control domain for the physical partition PPAR for which the error message was output Chapter 3 Information on Software 53 Table 3 8 SPARC M10 RTI No 1 4 4S RTIF2 x x x 131126 003 RTIF2 x 131213 001 RTIF2 x 131213 002 Description Update of the PCI expansion unit firmware may fail If it fails LINKCARD update is failed appears in the event log Example SCF LINKCARD update is failed LINKCARD 1 bank 0 PCIBOX version 1130 last version 1120 In a configuration with 3 or more BBs or with crossbar boxes when the XSCF master standby switchover is executed due to som
209. mmand detects the STICK Stop Register error does not stop or the STICK does not stop CPU error message and may fail Even when rotation abnormality is found on both fans at the same time in the same fan unit error log for only one fan is registered and thus the system is not shutdown As a result temperature of components like CPU may rise Workaround There is no effective workaround Ignore the 2nd error log Moreover replace the faulty FRU as soon as possible There is no effective workaround Replace the faulty FRU Moreover as this error message has no effect on the functioning of the system ignore it There is no effective workaround How to Restore Collect diagnosis information by executing the snapshot 8 command After the collection is complete turn off on the input power AC OFF ON of all the chassis and then contact the maintenance staff There is no effective workaround How to Restore If the system is not shut down when fan rotation abnormality is detected if any of the following symptom is confirmed in the two fans which comprises the faulty fan unit change the following fan unit as soon as possible Chapter 3 Information on Software 73 Table 3 8 RTI No RTIF2 140507 010 RTIF2 140507 011 RTIF2 140507 012 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 4 48 x x xXx x x Description In a system with three or more BBs or
210. mmend that you first save the CPU Activation information and CPU Activation key by using the dumpconfig 8 command To save and restore only CPU Activation keys execute the dumpcodactivation 8 and restorecodactivation 8 commands respectively Note however that CPU Activation information cannot be saved and restored Use the showcod 8 and setcod 8 commands to reconfigure CPU Activation Notes and restrictions on XSCF Web Notes 1 Common to browsers When you import XCP or update the firmware by using XSCF Web Session is invalid may appear on the web browser If the timeout of the XSCF shell is short when you import XCP by using XSCF Web XCP importing fails Set the timeout of the XSCF shell to 30 minutes or longer Select the menu tab and select XSCF Settings Autologout menu Then enter a value of 30 minutes or greater in Time out value Suppose you select XSCF Setting CoD Reservation menus on the XSCF Web and change the setting value by pressing the Reserve CoD Resources button on the PPAR Usage and Reservation table If you specify a value smaller than the current setting value the following warning message dialog appears to confirm that you have entered the correct value PROC Permits assigned is less than current setting Continue Click the OK button to continue the setting and click the Cancel button to cancel the setting 2 Internet Explorer If you use XSCF Web of a versio
211. ms that might occur with XCP 2250 and workarounds continued SPARC M10 1 4 48 x x x x x x x Description Incorrect Status Alarm FRU FIRMWARE MBU Msg SCF panic detected Correct Status Notice FRU FIRMWARE MBU Msg SCF panic detected If during execution of the restoreconfig 8 command you power on or off the physical partition PPAR or execute diagnosis of the system board the operations in progress are interrupted With the system input power off if the CPU memory unit lower CMUL is replaced or if the SPARC M10 4S is added without using the maintenance menu the following error log may be registered as a result of automatic synchronization of XCP firmware versions Alarm SCF Gaps between XBBOX ID Or Alarm SCF Gaps between BB ID If a hardware error is detected immediately after powering off or restarting the physical partition PPAR the PPAR power off or restart process may be stopped and may not be completed To check whether this phenomenon has occurred power off or restart the PPAR and then execute the showpparprogress 8 command If the PPAR remains in the power on state and the power off process has not completed after at least one Workaround During execution of the restoreconfig 8 command do not power on or off the physical partition PPAR or execute diagnosis of the system board How to restore If the PPAR power on process is interrupted Execute the poweron f
212. mware and then upload XCP with XSCF Web without restarting XSCF uploading of XCP will fail and the XSCF Web session will time out After creating an I O domain to which the PCI card is assigned with Oracle VM Server for SPARC turn on the power of the I O domain If you then stop it in ok prompt the configuration information of the PCI card may not be displayed with the showhardconf 8 command of XSCF During operation of the XSCF firmware a system backup memory access error which is an error in the PSU backplane PSUBP may be erroneously detected and registered in the error log If this erroneous detection occurs during the start process of the physical partition PPAR the start of the PPAR may fail Also if it occurs during the collection of log information the log information collection fails In addition a failure mark may be displayed on the PSUBP when the error is detected If the failure mark is displayed on the PSUBP the resources necessary for starting the PPAR are insufficient Therefore when start of the PPAR is requested a log indicating that the start of the PPAR failed is registered in the power log You can display the power log with the showlogs power command Problems resolved in versions prior to XCP 2050 continued Workaround Use the showlogs 8 command to check a failure state on XSCF If you update the firmware and then continue to upload XCP with XSCF Web restart XSCF Start Oracle S
213. n disclosure modification and adaptation of the programs including any operating system integrated software any programs installed on the hardware and or documentation shall be subject to license terms and license restrictions applicable to the programs No other rights are granted to the U S Government Disclaimer The only warranties granted by Oracle and Fujitsu Limited and or any affiliate in connection with this document or any product or technology described herein are those expressly set forth in the license agreement pursuant to which the product or technology is provided EXCEPT AS EXPRESSLY SET FORTH IN SUCH AGREEMENT ORACLE OR FUJITSU LIMITED AND OR THEIR AFFILIATES MAKE NO REPRESENTATIONS OR WARRANTIE S OF ANY KIND EXPRESS OR IMPLIED REGARDING SUCH PRODUCT OR TECHNOLOGY OR THIS DOCUMENT WHICH ARE ALL PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS REPRESENTATIONS AND WARRANTIES INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT ARE DISCLAIMED EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID Unless otherwise expressly set forth in such agreement to the extent allowed by applicable law in no event shall Oracle or Fujitsu Limited and or any of their affiliates have any liability to any third party under any legal theory for any loss of revenues or profits loss of use or data or business interruptions or for any indirect special
214. n XCP 2221 or earlier while you are in Internet Explorer 10 or 11 you may see distorted screen layouts such as disordered tables or superposed characters If you see a distorted XSCF Web screen layout in the above environment use Internet Explorer 9 or earlier or Firefox However this problem does not affect system operation 3 Firefox If you use XSCF Web in a Firefox environment the browser may prompt you to save the login ID and password when you log in to the XSCF In this case do not save the login ID and password If you save the login ID and password the saved data may be displayed on LDAP SMTP and REMCS web pages Chapter2 XCP 2250 Related Information 19 Note Remote Customer Support System REMCS is supported only for SPARC M10 systems sold within Japan by Fujitsu Configure either of the following settings to disable the login ID password save function of the browser Disable the login ID password save function throughout the browser Select Tools Options Security tab and uncheck Remember passwords for sites in Passwords Specify the site as an exception to login ID and password saving Select Tools Options Security tab and check Remember passwords for sites in Passwords Then click the Never Remember Password for This Site button in the dialog box that appears for ID and password saving when you log in to the XSCE This registers the address of the XSCF in the Exceptions list f
215. n application programs etc if they specify the name directly 3 Confirm that MPxIO is enabled If MPxIO is enabled the character string scsi_vhci appears in the device path name format Searching for disks done AVAILABLE DISK SELECTIONS 0 c0t50000394281b5310d0 lt TOSHIBA MBF2600RC gt Logical device path name Vendor name Product name scesi_vhei disk g50000394281b5310 Physical device path name If the ZFS system volume is installed in an HDD of a multipath type MPxIO confirm that the volume status is normal usr sbin zpool status Notes on updating SPARC M10 system to Oracle Solaris 11 2 Notes on enabling MPxIO The device path name of an internal SAS disk or an SSD may be changed when Oracle Solaris 11 1 is updated to Oracle Solaris 11 2 or later You can boot Oracle Solaris even when the device path name is changed However if any application or backup software specifies the device path name of the internal SAS disk or the SSD directly the device path may not be available for reference Cause The cause of this is that updating from Oracle Solaris 11 1 to Oracle Solaris 11 2 changes the default MPxIO setting of the internal SAS disk or the SSD from disabled to enabled For the target disks see Table 3 2 For an example of a device path change see Table 3 3 Table 3 2 Default MPxIO setting on an internal SAS disk and an SSD Product name Default MPxIO setting Oracle Solaris 11 1 Oracle Solaris 1
216. n error Not all the commercially available USB memories of any manufacturer are guaranteed for their connectivity and operability with XSCF Abnormalities may occur such as an XSCF firmware error or reset depending on your USB memories In such a case immediately stop using the USB memory The saved data contains information on the system If you use the USB memory consideration should be made for the management of the USB memory in which the data is saved for security reasons 189 Problems with Hardware and Workarounds There is no problem that has been confirmed as of this moment 190 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Chapter 5 Information on SPARC M10 4 Hardware This chapter describes special instructions and problems concerning the SPARC M10 4 hardware Notes and Restrictions a Problems with Hardware and Workarounds Notes and Restrictions Notes on using external DVD drive USB bus power drive is not supported for external DVD drives connected via USB Notes on using USB memory Prepare a USB memory as a medium in advance if you execute the command specifying the USB memory as a destination of saving data among XSCF commands When connecting a USB memory to the USB port for XSCF directly connect it to the USB port If you connect the USB memory via the USB hub or USB extension cable it may cause an error Not all the commercially available USB memories of any manufact
217. n the crossbar box Execute the reset por command or power off the PPAR by using the poweroff f command and then power it on again There is no effective workaround Ignore this event log Chapter 3 Information on Software 49 Table 3 8 SPARC M10 RTI No 1 4 4S RTIF2 x x x 130305 002 RTIF2 x x x 130305 007 RTIF2 x x x 130305 013 RTIF2 x 130305 020 RTIF2 x 130305 022 Description If an error in the CPU or memory is detected and if the XSCF is switched while the XSCF is notifying the error information to the control domain the error information may not be notified again to the control domain Because of this the error information displayed with the showlogs error command is not displayed in the Fault Report output by the fmdump command FRU registered in the error log is displayed as PPAR 30 if the configuration error of the system board PSB is detected when executing the testsb 8 command or diagxbu 8 command While XSCF is starting process down panic or watchdog timeout occurs which may cause XSCF to be reset If an XSCF panic or hang up occurs an error log showing that XSCF hang up is detected may be posted many times The poweron 8 command may fail with the output of the following message if an error log showing that XSCF hang up is detected was detected and an unknown system board PSB was found by the showboards 8 command The same can be said for the instruction of power on
218. nd try again Notes on LDAP over SSL If the value set by the timeout operand of the setldapssl 8 command is small and you log in to the XSCF the user privilege may not be assigned to you In this case increase the timeout setting value and try again 24 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Notes on the logical domain time Suppose the physical partition PPAR has been kept active for a long time on the system with the XCP version earlier than XCP 2232 Then restarting the physical partition may cause the Oracle Solaris time to deviate This problem RTIF2 140711 001 is solved in XCP 2240 and later XCP versions However restarting a physical partition right after firmware update from XCP 2232 or earlier to XCP 2240 or later may cause the Oracle Solaris time to deviate Also after the physical partition PPAR has been kept active for a long time restarting the physical partition may cause the time of logical domains other than the control domain to deviate RTIF2 141204 001 To solve these problems restart the physical partition boot Oracle Solaris in single user mode execute the date 1M command and then set the correct time The following shows the workaround procedure 1 Execute the poweroff p command to power off the target physical partition Also stop the logical domains within the physical partition XSCF gt poweroff p xx PPAR IDs to power off xx Continue yln y xx Powe
219. ng Occurred Dec 20 14 44 26 513 JST 2013 FRU UNSPECIFIED Msg XSCF command System status change OS panic PPARID 00 path 00 Diagnostic Code 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 00000000 00000000 00000000 00000000 0000 Date Dec 20 15 00 01 JST 2013 Code 20000000 00fcff00b0000000ff 010400010000000000000000 Status Notice Occurred Dec 20 14 59 56 838 JST 2013 FRU FIRMWARE XBBOX 81 XSCFU Msg SCF process down detected Diagnostic Code 00000000 00000000 0000 51000000 00000000 0000 00000000 00000000 0000 636f6464 2e323537 382e627a 32000000 00000000 00000000 0000 You can check codd by confirming that the first four bytes on the fourth line of the Diagnostic Code have the value 636f6464 Suppose that a cluster system is built to fulfill the following condition It is composed of multiple SPARC M10 Systems chassis each of which includes 10 or more guest domains 10 or more cluster nodes running in one physical partition PPAR Moreover PRIMECLUSTER software is installed on each of these guest domains Alternatively the cluster system is composed of multiple PPARs within the SPARC M10 Systems chassis If you execute the poweroff f command Workaround Confirm that less than 10 cluster nodes are included in one PPAR that exists on an instance of SPARC M10 1 SPARC M10 4 or SPARC M10 4S How to restore The system will be available as is becaus
220. ng information for the XSCF is deleted When a SPARC M10 4S chassis is removed with the initbb 8 command the information on the removed chassis remains without being completely deleted Problems resolved in versions prior to XCP 2050 continued Workaround Use the following procedure to replace a SPARC M10 4S chassis by using the replacefru 8 command 1 Enter r to replace the chassis in response to the message Do you want to continue r replace c cancel which is displayed after the replacefru 8 command is executed 2 Replace the SPARC M10 4S chassis and wait for about 15 minutes after the input power of the chassis is turned on 3 Execute the showlogs event command to display an event log 4 Continue the replacement using either of the following methods If the event log displays XSCF update is started Wait until the XCP update has been completed log is registered When XCP update has been completed is displayed enter f in response to Please select f finish and then continue the replacement by following the instructions displayed on the screen If the event log does not display XSCF update is started Enter f in response to Please select f finish and then continue the replacement according to the instructions on the screen Ignore the error log regarding a cable connection error registered for a SPARC M10 4S chassis that does not exist To replace a SPARC M10 4S chassis due to an
221. ng states depending on the setting of OpenBoot PROM environment variable auto boot If auto boot is true Oracle Solaris is started from the device that is set as the boot device If however the device specified with the select command above is the same as the device that has been set as the boot device this device is degraded so that Oracle Solaris will fail to start and the ok prompt appears If auto boot is false The ok prompt appears in the same way as in normal operation Workaround After specifying a device and executing the select command be sure to execute the unselect dev command before executing the boot command Example 0 ok select pci 8000 pci 4 pci 0 pci 1 network 0 0 ok unselect dev 0 ok boot net How to restore If after the defect occurs the logical domain is in the ok prompt state Execute the following command to reset the logical domain 0 ok reset all If after the defect occurs Oracle Solaris has been started in the logical domain Use the shutdown command to first enter the ok prompt state and then set environment variable auto boot to false Then use the reset all command to restart OpenBoot PROM Example shutdown y g0 i0 0 ok setenv auto boot false 0 ok reset all After recovery any device that was degraded as a result of this defect will be recognized normally Ignore the message registered in the error log when the defect occurred Fujitsu M10 SPARC M10
222. nk in Chapter 3 Examples of Power Supply Interlocking Configuration in the Fujitsu M10 SPARC M10 Systems RCIL User Guide Other notes and restrictions Notes When the mode switch on the operation panel is set to Service mode the power cannot be turned on by using the power switch on the operation panel To turn on the power using the power switch on the operation panel set the mode switch on the operation panel to the Locked mode position To add the 64 GB memory apply XCP 2090 or later SPARC M10 1 M10 4 M10 4S The maximum number of users who can concurrently connect to the XSCF via Telnet and SSH is as follows M10 1 20 users M10 4 40 users M10 45 without crossbar box 40 users M10 45 with crossbar box 70 users If the maximum allowable number of users is exceeded access is denied XSCF LAN is compliant with auto negotiation If you connect XSCF LAN to a network device that is fixed to full duplex mode the XSCF LAN communicates in half duplex mode according to the IEEE 802 3 protocol This may slow down the speed of network communication or cause communication error Be sure to set auto negotiation for network devices to which you connect XSCF LAN 28 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Settings made by the setdualpowerfeed 8 command are immediately applied Therefore the XSCF does not need to be reset The ioxadm poweroff 8 command can be specified w
223. nning Manual Fujitsu M10 SPARC M10 Systems Installation Guide Fujitsu M10 1 SPARC M10 1 Service Manual Fujitsu M10 4 Fujitsu M10 4S SPARC M10 4 SPARC M10 4S Service Manual Crossbar Box for Fujitsu M10 SPARC M10 Systems Service Manual PCI Expansion Unit for Fujitsu M10 SPARC M10 Systems Service Manual Fujitsu M10 SPARC M10 Systems PCI Card Installation Guide Fujitsu M10 SPARC M10 Systems System Operation and Administration Guide Fujitsu M10 SPARC M10 Systems Domain Configuration Guide Fujitsu M10 SPARC M10 Systems XSCF Reference Manual Fujitsu M10 SPARC M10 Systems RCIL User Guide 3 Fujitsu M10 SPARC M10 Systems XSCF MIB and Trap Lists Fujitsu M10 SPARC M10 Systems Product Notes Fujitsu M10 SPARC M10 Systems Glossary 1 The listed manuals are subject to change without notice 2 The printed manual comes with the product 3 This document applies specifically to the FUJITSU M10 and FUJITSU ETERNUS storage system Preface xi Documents provided on DVD ROM SPARC M10 SPARC Enterprise Software DVD Note Enhanced Support Facility ESF and Remote Customer Support System REMCS are supported only for SPARC M10 systems sold within Japan by Fujitsu Remote maintenance service Enhanced Support Facility User s Guide for REMCS J2X1 7753 EN Information on firmware This is information for customers of Fujitsu Obtain the firmware for your server from the following sources Japanese site Customers who subscribed to SupportDesk c
224. oblems resolved in XCP 2230 Chapter 3 Information on Software 101 Table 3 13 RTINo RTIF2 140212 009 RTIF2 140527 001 RTIF2 140606 002 RTIF2 140606 003 RTIF2 140606 006 102 Problems resolved in XCP 2230 SPARC M10 1 4 4S x x x x x x x x x xX x Description When the XSCF is under high load due to high volume of packets sent to the XSCF network by the L2 loop etc the false error Hardware access error regarding the power unit PSU is detected Moreover the PSU is marked as failed due to this error On a system that is configured with several SPARC M10 4S if XSCF rebooting is not performed with the rebootxscf 8 command or if the input power is not turned off for about 10 days in respect to the XSCFs of the following status the XSCF self diagnosis warning detection error message is logged Astandby XSCF which did not perform master standby switchover for about 10 days Slave XSCF Even though the AEV_ AUTHENTICATE audit event is enabled XSCF Web login failure events are not registered in the audit log When an attempt is made to look at an audit log concerning XSCF Web operation using the viewaudit 8 command the command displays incorrect values The displayed values of the port number and IP address at the time of XSCF Web access are 0 and 0000 When specifying a system board PSB for a logical system board LSB on the PPAR Operation PPAR Configuration
225. occurs when you perform the setting on the XSCF Web RTIF2 X xX x 140710 001 After you replace a motherboard or CPU memory unit lower CMUL the XCP firmware version should differ from the pre replacement version Nevertheless the message XCP version of XSCF and Back Panel mismatched that should appear at the time of login to XSCF is not displayed Workaround There is no effective workaround How to restore Replace the following part SPARC M10 1 PSU backplane PSUBP SPARC M10 4 M10 45 PSU backplane unit PSUBP SPARC M10 45 with crossbar box XSCF interface unit XSCFIFU There is no effective workaround How to restore When replacing a component execute the following procedure 1 Before replacement execute the version 8 command to check the XCP version Example XSCF gt version c xcp BB 00 XSCF 0 Master XCPO0 Current 2051 XCP1 Reserve 2051 2 After replacement execute the version 8 command to check the XCP version again 3 If the XCP versions before and after replacement do not match execute the flashupdate 8 command to update the firmware Example Updating to XCP 2052 XSCF gt flashupdate c update m xcp s 2052 96 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 10 SPARC M10 RTINo 1 4 4S RTIF2 x x x 140711 001 Problems resolved in XCP 2240 continued Description After Oracle Solaris has been kept active
226. ocking group and enable disable setting of power supply interlocking function Example Restoring setting information based on management file saved to FTP server XSCF gt setremotepwrmgmt c config ftp server port path file Example Enabled when saving XSCF gt setremotepwrmgmt c enable Initializing time difference between XSCF and hypervisor of each PPAR After clearing the time difference information to 0 power on the physical partition synchronize the Oracle Solaris time with the NTP server or adjust the time with the date 1 command Example Time difference existing at saving XSCF gt resetdateoffset y a 6 When restoring to another chassis execute the command in step 3 again and reconfirm the settings If the settings after restore differ from the settings before restore execute the command below to implement a reset using the values confirmed in step 3 Restoring LDAP client setting Example Setting LDAP search timeout value to 60 seconds 68 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 RTI No RTIF2 140407 005 RTIF2 140407 006 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 4 4S x x x Description Suppose that the system is operated continuously without replacing a CPU memory unit lower CMUL or CPU memory unit upper CMUU having a faulty DC DC converter DDC In such case even if an error occ
227. olaris and Required SRU Patch How to Obtain XCP and Oracle Solaris SRU Patch Oracle VM Server for SPARC Web Browser Existing XCP Firmware Versions and Support Information XCP Oracle Solaris and Required SRU Patch The following lists XCP Oracle Solaris and required SRU patch supported on SPARC M10 Systems Table 1 1 XCP Oracle Solaris and required SRU patches supported by the SPARC M10 system Server XCP Oracle Solaris Required packages 4 Required SRU 4 Required products 5 Required patch 5 SPARC M10 1 SPARC64 2250 or Oracle Solaris 11 2 system Idoms 1 None X 3 7GHz later system Idoms ldomsmanager 2 Oracle Solaris 11 1 system Idoms 1 SRU1 4 or system ldoms ldomsmanager 2 later 3 Oracle Solaris 10 1 13 Oracle VM Server for SPARC 3 0 or later 3 SPARC64 2210 or X 3 2 GHz later Oracle Solaris 11 2 system Idoms 1 system ldoms ldomsmanager 2 Oracle Solaris 11 1 system Idoms 1 system ldoms ldomsmanager 2 Oracle Solaris 10 1 13 Oracle VM Server for SPARC 3 0 or later 3 150310 03 or later None SRU1 4 or later 3 150310 03 or later Table 1 1 Server SPARC64 X 2 8 GHz SPARC M10 4 SPARC64 X 3 7 GHz SPARC64 X 3 4 GHz SPARC64 X 2 8 GHz XCP 2012 or later 2250 or later 2210 or later 2012 or later Oracle Solaris Oracle Solaris 11 2 Oracle Solaris 11 1 Oracle Solaris 10 1 13 Oracle Solaris 11 2 Oracle Solaris 11 1
228. olaris of the logical domain to which the PCI card is assigned with Oracle VM Server for SPARC If you find a log described in Description execute the showstatus 8 or showhardconf 8 command to check whether the failure mark is displayed on the PSUBP When the failure mark is not displayed on the PSUBP No problem has occurred in the hardware So ignore the error log and continue the operation When the failure mark is displayed on the PSUBP Clear the failure mark by using the following procedure 1 Switch the mode switch on the operation panel to the Service mode position 2 Turn the power to the target SPARC M10 system chassis off and then on again and then restart the XSCF For the M10 4S turn the power to every SPARC M10 4S chassis off and then on again 3 After the XSCF has been restarted return the mode switch on the operation panel to its original position If the same error recurs even after restarting the XSCF there is a possibility that the error has not been erroneously detected but that a PSUBP hardware failure has occurred Ask your Fujitsu field engineer service provider to replace the PSUBP 158 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 25 SPARC M10 RTI No 1 4 4S RTIF2 x x x 121129 002 RTIF2 x x x 121129 004 RTIF2 x x x 121130 001 RTIF2 x xX x 121204 001 RTIF2 x x x 121204 002 RTIF2 xX x x 121204 003 RTIF2 x x x
229. ologie fournis SAUF MENTION CONTRAIRE EXPRESSEMENT STIPULEE AU DIT CONTRAT ORACLE OU FUJITSU LIMITED ET OU LES SOCIETES AFFILIEES A L UNE OU L AUTRE ENTITE DECLINENT TOUT ENGAGEMENT OU GARANTIE QUELLE QU EN SOIT LA NATURE EXPRESSE OU IMPLICITE CONCERNANT CE PRODUIT CETTE TECHNOLOGIE OU CE DOCUMENT LESQUELS SONT FOURNIS EN L ETAT EN OUTRE TOUTES LES CONDITIONS DECLARATIONS ET GARANTIES EXPRESSES OU TACITES Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE A L APTITUDE A UNE UTILISATION PARTICULIERE OU A L ABSENCE DE CONTREFACON SONT EXCLUES DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE Sauf mention contraire express ment stipul e dans ce contrat dans la mesure autoris e par la loi applicable en aucun cas Oracle ou Fujitsu Limited et ou l une ou l autre de leurs soci t s affili es ne sauraient tre tenues responsables envers une quelconque partie tierce sous quelque th orie juridique que ce soit de tout manque a gagner ou de perte de profit de probl mes d utilisation ou de perte de donn es ou d interruptions d activit s ou de tout dommage indirect sp cial secondaire ou cons cutif m me si ces entit s ont t pr alablement inform es d une telle ventualit LA DOCUMENTATION EST FOURNIE EN L ETAT ET TOUTE AUTRE CONDITION DECLARATION ET GARANTIE EXPRESSE OU TACITE EST FORMELLEMENT EXCLUE DANS LA MESURE AUTORISEE PAR LA LOI EN VIGUEUR Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA
230. oltage drop caused by an external factor First byte 00 Second byte The sixth x04 bit from the left is 0 any of 0 1 2 3 8 9 a or b Third byte The third x20 bit from the left is 1 any of 2 3 6 7 a b e or f for the second and third bytes indicates any value The first to third bytes on the fourth line of Diagnostic Code are 000120 XSCF gt showlogs error v Date Oct 30 10 27 17 JST 2013 Code 80000408 00cb000000ff0000Ff 110000246101000000000000 Status Alarm Occurred Oct 30 10 27 17 597 JST 2013 FRU MBU PCI 1 PCIBOX 7010 PSU 1 Msg PSU failed Diagnostic Code 00013730 31300100 0000 00010000 00000000 0000 00010000 00000000 0000 00012000 00000000 00000000 00000000 00000000 00000000 0000 Problems resolved in version 1130 of the PCI expansion unit firmware Workaround There is no effective workaround If the value of the first to third bytes on the fourth line of Diagnostic Code does not match the value in the Description column assume that a PSU failure occurred How to restore For this event occurring in a single PSU If the error log Msg PSU RECOVERY is registered the system has already been restored from the instantaneous voltage drop The system can be operated continuously If the error log Msg PSU RECOVERY is not registered a PSU failure occurred Replace the PSU For this event occurring in two PSUs The PPAR is shut down Reactivate the PPAR
231. ommand be sure to set up User based Security Model USM management information using the setsnmpus m 8 command and View based Access Control Model VACM management information using the setsnmpvacm 8 command Specification of the authentication protocol and the encryption protocol is required in the SNMPv3 agent setup process Moreover the password set up when executing the setsnmp 8 and setsnmpusm 8 commands will also be necessary Jfa server on which the SNMP manager is not running is registered as the inform trap host of SNMPv3 execution of setsnmp 8 setsnmpusm 8 or setsnmpvacm 8 commands may output the Agent restart failed message This message is output when there is an abnormality in the restarting of the SNMP agent but as the SNMP agent works properly even if this messages is output it has no effect on the system Register the trap host after the SNMP manager had been started Ifthe setsnmp 8 command is executed with the addtraphost or the addv3traphost operands and a trap host is registered with the host name consisting of 16 or more characters the UDP address of the trap that is reported to the trap host becomes the IP address that is assigned to the XSCF LAN physical IP address instead of the takeover IP address virtual IP address This symptom occurs when a takeover IP address is set up If the host name of the trap host consists more than 16 characters register the trap host with its IP address not its
232. onnecting all the power cables when the system is composed of multiple SPARC M10 4S chassis Remove and connect the power cables of all the chassis again when there is a SPARC M10 4S chassis that is not recognized Execute the showremotepwrmgmt 8 command again Ignore the information on the displayed second faulty component the second suspect component Execute the replacefru 8 command again and replace the PSU If the failure is Power on failure or Power off failure and the faulty component is a fan replace the following component For the SPARC M10 1 Motherboard unit MBU For the SPARC M10 4 M10 4S PSU backplane unit Ignore this error log Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 25 SPARC M10 RTI No 1 4 4S RTIF2 X 121219 012 RTIF2 X 121219 013 RTIF2 x 121219 014 RTIF2 x 121219 015 Description When a SPARC M10 4S chassis is replaced using the replacefru 8 command replacement of the SPARC M10 4S chassis may fail with internal error displayed When a SPARC M10 4S chassis finds an error indicating that the XSCF cannot be started not only an error log for the SPARC M10 4S chassis where the error occurred but also an error log regarding a cable connection error in a chassis that does not exist may be registered When cold replacement is performed replacement performed while the input power is off due to an error with BB 00 the setti
233. ontinue ylin ty xx Powering on Note This command only issues the instruction to power on The result of the instruction can be checked by the showlogs power XSCF gt 6 Execute the console 8 command to switch to the console of the control domain XSCF gt console p 0 omitted 0 ok 7 Execute the boot s command to start Oracle Solaris in single user mode 0 ok boot s 8 Execute the date 1M command of Oracle Solaris to display the control domain time 9 Set the control domain time by executing the date 1M command 10 Enter the escape command such as from the control domain console of the physical partition and return to XSCF shell 11 Execute the showdate 8 command to display the XSCF time to confirm that the control domain time of the target physical partition is the same as the clock time of XSCF 12 If necessary specify true for OpenBoot PROM environment variable auto boot Execute the setpparparam 8 command and enable the autoboot 26 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 function of the control domain XSCF gt setpparparam p XX s bootscript setenv auto boot false XSCF gt 13 Similarly execute the Idm add spconfig command for the guest domain after adjusting the time of Oracle Solaris Notes on Timezones The time zones regions place names supported by the XSCF can be changed to support the latest time zone information
234. oofast_pcibox This problem occurs when the fourth byte from the beginning of the third field of Code at execution of the showlogs error command is as shown below 1100002E 1100002F After the system board is deleted by dynamic reconfiguration of physical partitions PPAR DR I O devices on I O domain may not work or root domain or T O domain may cause a panic Hypervisor Abort may occur if all of cores are degraded on primary domain Workaround There is no effective workaround When the fourth byte from the beginning of the third field of Code as shown in the Example in Description at execution of the showlogs error command take action by interpreting the message to be correct There is no effective workaround How to restore If I O devices does not cause a panic after physical partitions PPAR DR reboot the I O domain There is no effective workaround Chapter 3 Information on Software 99 Table 3 10 RTINo RTIF2 141106 001 RTIF2 141110 001 RTIF2 141113 001 RTIF2 141203 001 RTIF2 141208 002 100 1 X Problems resolved in XCP 2240 continued SPARC M10 4 4S Description Any of the following errors related to abnormal temperature may be erroneously registered Temperature out of range error High temperature at SW In these error logs the first two bytes of the second field in Code has the value of 0013 ldm 1M may not display correct CPU uti
235. ootxscf a addcodactivation 8 deletecodactivation 8 Input power off on There is no effective workaround Replace the version number Moreover update the XCP firmware to XCP 2090 or later 132 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 19 Problems resolved in XCP 2090 continued SPARC M10 RTI No 1 4 4S Description RTIF2 x x x Ifthere isa mounted memory the last 131129 001 eight digits of whose Code start with 00 as displayed by the showhardconf 8 command in execution of any of the following actions may result in incorrect display showing a value of 0 for both the Code and the Size of that memory as shown Execute the restoredefaults factory command Execute the initbb 8 command Change the mounting point of memory Example XSCF gt showhardconf MEM 10B Status Normal Code ce8001M393B2G70QH0 YKO 0000 00511571 Type 07 Size 16 GB XSCF gt showhardconf MEM 10B Status Deconfigured Code 000000 0000 00000000 Type Size 0 GB RTIF2 x x x The LDC Protocol info from PPAR 131213 006 PPAR ID X Domain Service Data Send Failed event log is registered on a running logical domain and shutdown of that logical domain may not be properly executed Workaround Apply the latest version of the XCP and then execute power off and on There is no effective workaround Either reboot the control domain or execute the rebootxscf a command
236. or ID and password saving and the dialog box for ID and password saving does not appear at subsequent logins to the XSCF Restrictions 1 Common to browsers There are no restrictions known at present 2 Internet Explorer If you use Internet Explorer 8 in a Windows 7 environment built in Administrator accounts cannot be used 3 Firefox There are no restrictions known at present Notes on firmware update SPARC M10 4S If you update the firmware by executing the flashupdate 8 command or using XSCF Web the time for the processing depends on the number of SPARC M10 45 chassis or crossbar boxes that configure the system The relationship of the master XSCF and the standby XSCF after the update of the XSCF firmware depends on the version of the updated XCP The following table shows the relationship between the master XSCF and the standby XSCF as well as the operation of firmware update for each XCP version 20 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 2 1 Difference between firmware update in XCP 2050 or later and in XCP 2044 or earlier XCP version Relationship between master XSCF and standby Operation during firmware update XSCF XCP 2050 or later The master XSCF and the standby XSCF 1 that have been switched over during update will return to the status before the gt switchover gt gt XCP 2044 or earlier The master XSCF and the standby XSCF 1 that have been
237. ound How to restore Use either of the following procedures How to restore 1 Turn off the power to the SPARC M10 chassis connected to the PCI expansion unit Then disconnect both PCI expansion unit power cables AC OFF Then wait for 30 seconds to reconnect the cables AC ON How to restore 2 Perform pseudo active replacement of the PSU in which the error has been detected temporarily remove the PSU and then reinstall it When performing pseudo replacement of the PSU use the ioxadm 8 command Note that the fieldeng privilege is required to execute the ioxadm 8 command There is no effective workaround How to restore How to restore 1 Power off the SPARC M10 chassis to which the PCI expansion unit is connected then pull out both power cables AC OFF of the PCI expansion unit Wait for 30 seconds then connect both power cables AC ON How to restore 2 Perform pseudo active replacement of the PSU in which the error is erroneously detected temporarily remove the PSU and then reinstall it When performing pseudo active replacement of the PSU use the ioxadm 8 command Note that the fieldeng privilege is required to execute the ioxadm 8 command Information on PCI Expansion Unit Hardware 201 Table 7 3 Problems resolved in version 1180 of the PCI expansion unit firmware continued SPARC M10 RTI No 1 4 4S Description Workaround 00d4000000ff0000Ff 110000256100000000000000 Status Alarm Occurred
238. ower on processing is complete the error log SCF process down detected is registered and the ioxadm 8 command may fail Suppose that the error log FAN speed too high is registered because of an excessive fan rotation count Subsequently if an event that changes the fan rotation speed occurs the fan rotation speed may not be switched to the correct value and instead may be switched to level 5 full speed If an event that changes the fan rotation speed occurs the following event logs are registered However the displayed fan rotation speed will not be correct The actual fan rotation speed level is 5 which is full speed Low temperature was detected at air inlet FANs are changed to speed level 1 mode Low temperature was detected at air inlet FANs are changed to speed level 2 mode Middle temperature was detected at air inlet FANs are changed to speed level 3 mode High temperature was detected at air inlet FANs are changed to speed level 4 mode Air outlet temperature recovered from warning state Workaround Do not execute the ioxadm 8 command until the PPAR power on processing is complete You can check the progress of the PPAR power on processing by executing the showpparstatus 8 command If the Running message appears as a result of executing the showpparstatus 8 command it indicates that the PPAR power on processing has been completed Once the PPAR power on processing has been com
239. pleted execute the ioxadm 8 command again There is no effective workaround How to restore Replace the fan of the detected excessive rotation speed error Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 19 SPARC M10 RTI No 1 4 4S RTIF2 x x x 131112 014 RTIF2 x 131112 015 RTIF2 x X x 131126 001 Problems resolved in XCP 2090 continued Description If the following mail server is being used and REMCS registration or REMCS environment setting is performed a communication timeout with the mail server is detected causing processing to fail Windows ExchangeServer E PORT qmail If the initbb 8 or replacefru 8 command is executed an event log stating Change Master Failed may be registered Suppose that a system satisfying one of the conditions described in Conditions sets the power supply interlocking function If Oracle Solaris is running and one of the events mentioned in Event occurs an external I O device may be erroneously powered off Conditions Asingle SPARC M10 system is registered in the power supply interlocking group Multiple SPARC M10 systems are registered in the power supply interlocking group and the physical partitions other than those of the SPARC M10 system that resets the XSCF are powered off Event Firmware update was executed from the flashupdate 8 command and XSCF Web and the XSCF was reset The XSCF
240. porarily remove the PSU and then reinstall it When performing pseudo replacement of the PSU use the replacefru 8 command Note that the fieldeng privilege is required to execute the replacefru 8 command There is no effective workaround Replace the faulty PSU 98 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 10 RTINo RTIF2 141020 001 RTIF2 141031 003 RTIF2 141031 004 1 x x Problems resolved in XCP 2240 continued SPARC M10 Description When using the ASR function and an abnormality occurs with the fan unit in the PCI expansion unit or the SPARC M10 system chassis the following incorrect fault telemetry is sent to ASR Manager An error in the fan unit of a PCI expansion unit is sent as an error in the fan unit of a SPARC M10 system chassis An error in the fan unit of a SPARC M10 system chassis is sent as an error in the fan unit of a PCI expansion unit Example Error in fan unit of SPARC M10 system chassis Incorrect message ID device fan toofast_pcibox Correct message ID device fan tooslow This problem occurs when the fourth byte from the beginning of the third field of Code at execution of the showlogs error command is as shown below 01911026 01911027 01911028 01911029 0191102a 0191102b Example Error in fan unit of PCI expansion unit Incorrect message ID device fan tooslow Correct message ID device fan t
241. power on the PPAR is turned off but the command prompt does not respond for about 20 minutes Symptom 2 When the PPAR is powered on the XB XB interface fatal error error is produced the power on process is repeated and it does not end properly On a physical partition PPAR that is composed of several SPARC M10 4S system board after a system board has been degraded due to failure if the setpciboxdio 8 command is executed to disable enable the direct I O feature of the PCI card mounted on the PCI expansion unit which is attached to the degraded chassis without powering off the PPAR first the following message is output and the command fails This operation cannot be done because the PPAR including a PSB of the target BB is powered on This symptom occurs when the state of system board is like the following which can be derive from either the showhardconf 8 or the showboards 8 command Example When PSB 01 0 BB 01 has been degraded XSCF gt showhardconf BB 01 Status Deconfigured XSCF gt showboards a PSB PPAR ID LSB Assignment Pwr Conn Conf Test Fault 01 0 00 01 Assigned n n n Passed Faulted Problems that might occur with XCP 2250 and workarounds continued Workaround If XSCF failure has occurred replace the CPU memory unit lower CMUL or the XSCF unit How to restore Case of symptom 1 After about 20 minutes the poweroff 8 command ends properly and the prompt comes back
242. r In such a case take the actions described in workarounds then update again Chapter2 XCP 2250 Related Information 21 Notes on configurations with a PCI expansion unit connected SPARC M10 1 If one of the following cases the logical domain configuration of physical partitions PPARs is restored to the factory default state at the next startup Moreover when there is a guest domain in the logical domain configuration the OpenBoot PROM environment variable is initialized Firmware of version XCP 2043 or earlier is updated to that of XCP 2044 or later in a configuration with a PCI expansion unit connected A PCI expansion unit is added to or removed from a system with firmware of XCP 2044 or later Save the logical domain configuration information to an XML file from Oracle Solaris in advance Execute the Idm list constraints x command to save the logical domain configuration information to an XML file Execute the Idm init system i command to restore the logical domain configuration information from an XML file Make a note of the OpenBoot PROM environment variable setting information for the control domain beforehand so that you can subsequently reconfigure it To display the information execute the printenv command in the ok prompt For details of these procedures see 1 7 2 How to save the configuration information and the OpenBoot PROM environment variable in the logical domain and subsequently restore them in the PC
243. r in the XSCF 3 On the logical domain execute the svcadm command to restart the picl service If 2 occurs The system can be operated continuously because this is a temporary warning message There is no effective workaround The message in the dialog indicates a display defect so you can operate the system as is Ignore the dialog related to this communication error There is no effective workaround Recover the system by following the procedure described below 1 Log in to either standby XSCF and then execute the following command XSCF gt rebootxscf s 2 After 10 seconds log in to the other standby XSCF and then execute the following command XSCF gt rebootxscf a 3 Wait for 20 minutes log in to the master XSCF and then execute the flashupdate 8 command again There is no effective workaround If this defect occurs execute the rebootxscf a command to reset all the XSCFs and restore the system Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 21 SPARC M10 RTI No 1 4 4S RTIF2 x 130903 006 RTIF2 xX x x 130903 007 Problems resolved in XCP 2070 continued Description If multiple physical partitions PPARs exist in a system consisting of multiple SPARC M10 4S units and some SPARC M10 4S units are turned off and then on again an SRAM Serious Error may occur requiring the replacement of the CPU memory unit lower CMUL When the state is displa
244. r processing a command that displays the system configuration or status such as showhardconf 8 command showboards 8 command and showpparstatus 8 command depends on the number of SPARC M10 45 chassis or crossbar boxes that configure the system SPARC M10 45 For a system configured with multiple chassis chassis BB 01 or XBBOX 81 may become the master XSCF first SPARC M10 45 Depending on the system configuration it may take time to reboot If you add a SPARC M10 4S to the SPARC M10 4S on which XCP 2032 is installed update to the latest firmware in advance When you execute the setsnmpvacm 8 command specifying createview as the operand you cannot set an access restriction using the OID mask of MIB When you execute the setsnmpvacm 8 command specifying createview as the operand do not use the OID mask of MIB If a takeover IP address has been set the UDP packet sender IP address and Agent Address for the SNMP Trap of SNMPv1 are different The IP address assigned to each XSCF LAN physical IP address is stored as the UDP packet sender IP address while the takeover IP address virtual IP address is stored as the Agent Chapter2 XCP 2250 Related Information 29 Address The device path of the I O device that has been used changes if a CPU memory unit upper CMUU is added to add two CPUs when the I O bus reconfiguration is enabled in SPARC M10 4 or SPARC M10 4S with two CPUs installed As for the ioreconfigure that can be
245. r the SNMP Security menu of XSCF Web Workaround There is no effective workaround How to restore Perform AC OFF ON There is no effective workaround Disable the lockout feature of user accounts There is no effective workaround when the setldap 8 command is used Use the encryption feature of LDAP LDAP over SSL with the setldapssl 8 command Do not configure SNMP from XSCF Web Use the following XSCF shell commands to configure SNMP setsnmp 8 setsnmpusm 8 setsnmpvacm 8 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 15 Problems resolved in XCP 2220 continued SPARC M10 RTI No 1 4 4S Description RTIF2 x Incase XCP 2210 is applied to a SPARC 140314 002 M10 4S that is attached to a crossbar box XBBOX if the crossbar cable is degraded due to some problems the following symptom may occur while the system is running If a failure occurs in the crossbar unit XBU of the crossbar box XBBOX it may not be detected and the physical partition may hang up Failure of crossbar cable can be confirmed by any of the following error logs FRU BB n XBU x CBL y BB n XBU x XBBOX m XBU x Msg XB XB interface fatal bus protocol error Or FRU BB n XBU x CBL y BB n XBU x XBBOX m XBU x Msg XB XB interface timeout error Or FRU BB n XBU x CBL y BB n XBU x XBBOX m XBU x Msg XB XB interface link up error RTIF2 x x x _ Inthe sea
246. ration can be continued If the showcodactivation 8 command is executed while data is being restored with the restoreconfig 8 or restorecodactivation 8 command it may be impossible to display the execution results If this occurs the showcodactivation 8 command ends with a codd internal error Problems resolved in versions prior to XCP 2050 continued Workaround Please run the activate volume command at ok prompt to activate a hardware RAID volume For the detailed procedure see 12 2 8 Re enabling hardware RAID volume in the Fujitsu M10 SPARC M10 Systems System Operation and Administration Guide There is no effective workaround How to restore If event 1 occurs Recover with the following procedure 1 End the prtdiag 1M command with Ctrl C 2 Wait for about 30 minutes and allow an SNMP timeout to occur in the XSCF 3 In the control domain execute the svcadm 1M command to restart the picl service If event 2 occurs Execute the command again If results are displayed the system can be operated continuously If the state where results are not displayed as expected continues check whether the XSCF is operating If the XSCF is operating use the rebootxscf 8 command to reset the XSCF If the XSCF is not operating turn the input power supply of the system off and then back on AC OFF ON to recover If event 3 occurs The system can be operated continuously because this is a
247. rch function for each log in the 140402 002 XSCF Logs menu on the XSCF Web if you click the Search button with both Start and End times set to execute a search a message indicating an error in the specified period may be output and it may not be possible to execute the search RTIF2 x x x Inasystem configuration with a 140407 002 connected PCI expansion unit you may update XCP firmware or reset XSCF with the physical partition PPAR powered on In this case the PCI expansion unit information is not output to the result of executing the ioxadm 8 command or showhardconf 8 command Or the PCI expansion unit can no longer be controlled with the ioxadm 8 command Workaround If a problem of any crossbar cable has occurred stop all PPARs immediately and replace the crossbar cable How to restore 1 Stop all PPARs If any of them cannot be stopped normally stop it forcibly 2 Replace the degraded crossbar cable 3 Diagnose the hardware with the testsb a command and confirm whether there is any failure of the XBU of XBBOX 4 If there is any failure in the XBU replace it Use the showlogs 8 command of the XSCF shell There is no effective workaround How to restore Execute either of the following Power off the PPAR and then power it on again Use PCI hot plug PHP to remove the link card from the system and reinstall it Chapter 3 Information on Software 111 Table 3 15 Prob
248. reboot of the physical partition When a PCI Expansion Unit is connected to a logical system board whose LSB number is equal to or more than 01 LSB 01 if direct I O feature is enabled in respect to the PCI Expansion Unit the PCI Expansion Unit may not be recognized by the logical domain Workaround There is no effective workaround How to restore Reboot the control domain only If the state of Oracle VM Server for SPARC does not become online execute the rebootxscf a command to reset all the XSCFs and then check the state of Oracle VM Server for SPARC once again If the state has not yet become online once more reboot the control domain only If the PCI Expansion Unit is not recognized reboot the logical domain Chapter 3 Information on Software 119 Table 3 16 Problems resolved in XCP 2210 continued SPARC M10 RTI No 1 4 4S Description Workaround RTIF2 In a system configuration with several After removing the degraded system 140212 001 SPARC M10 4S system boards after a board from the physical partition with system board in a physical partition has the deleteboard 8 command execute been degraded due to failure when the either the replacefru 8 or the initbb 8 system board is attempted to be replaced command to replace or remove the with the replacefru 8 command the system board system board is recognized as being Example running and the attempt of replacement XSCF gt deleteboard c unassign
249. red off remount the removed disk while the PPAR is in the powered off state How to Restore Perform the following procedure if this symptom occurs 1 Remove the newly created RAID volume 2 Set up the target disk as hot spare When the hot spare feature is enabled the disk will be automatically placed in the original RAID volume Meanwhile refer to F 4 Creating Hot Spare of Hardware RAID Volume or F 5 Deleting Hot Spare of Hardware RAID Volume of Fujitsu M10 SPARC M10 Systems System Operation and Administration Guide for the procedures of removing a volume or setting up a hot spare There is no effective workaround Chapter 3 Information on Software 113 Table 3 15 SPARC M10 RTI No 1 4 4S RTIF2 x X 140507 015 RTIF2 x x x 140507 017 RTIF2 x x x 140507 018 114 Problems resolved in XCP 2220 continued Description If the showhardconf 8 command is executed on a system configuration with 3 or more BBs or crossbar boxes wrong information may be output at the FRU Part Number of the crossbar cable Example In case of crossbar cable no RO Error CBL RO Status Normal FRU Part Number D00Q Ver 0020h Type Optic Length 2 Correct CBL RO Status Normal FRU Part Number ALLTO3FQPE Ver 0020h Type Optic Length 2 If XSCF is reset using the rebootxscf 8 command the XSCF may stop due to XSCF failure When the system is in the initialized state XSCF may not s
250. ring off Note This command only issues the instruction to power off The result of the instruction can be checked by the showlogs power XSCF gt 2 Execute the showpparstatus 8 command to confirm the physical partition is powered off Confirm the PPAR Status displays Powered off XSCF gt showpparstatus p xx PPAR ID PPAR Status 00 Powered off 3 Execute the showdate 8 command to display the clock time of XSCF XSCF gt showdate Mon Jan 23 14 53 00 JST 2012 Note Set the clock to the right time if it is incorrect Power off all physical partitions if you set the time by executing the setdate command Starting the physical partition may cause the logical domain time to deviate Use the NTP server to set the logical domain time or if it is the control domain perform steps 4 to 9 in the following procedure execute the date 1M command in single user mode and set the control domain time Chapter2 XCP 2250 Related Information 25 4 Specify false for the OpenBoot PROM environment variable auto boot execute the setpparparam 8 command and disable the autoboot function of the control domain XSCF gt setpparparam p xx s bootscript setenv auto boot false PPAR ID of PPARs that will be affected xx OpenBoot PROM variable bootscript will be changed Continue yln y 5 Execute the poweron 8 command to power on the target physical partitions XSCF gt poweron p xx DomainIDs to power on xx C
251. ris and workarounds continued SPARC M10 1 4 4s x x x Description The following messages may be output in the log of Idoms ldmd services var svc log Idoms ldmd default log and the communication between Idmd daemon and XSCF may be disconnected during or after physical partition dynamic reconfiguration PPAR DR Message example Sep 18 13 31 37 warning Device busy open_Idc_channel Open of devices virtual devices 100 channel devices 200 virtual channel 3 spds failed After that time processes which need to communicate with XSCF such as PPAR DR or Idm list spconfig command fail If the addboard 8 command is executed in the factory default configuration CPU cores may not be assigned to the control domain On a physical partition to which 8 or more system boards have been assigned when collecting dump files of the hypervisor which is executed as the ldoms ldmd service is started the following console messages is output by the Idoms ldmd service and it may fall back to maintenance mode Example of message Feb 28 16 19 39 svc startd 11 ldoms Idmd default failed transitioned to maintenance see svcs xv for details Workaround There is no effective workaround How to restore Execute the svcadm 1M command to restart the ldoms Idmd services svcadm restart Idmd This has been modified with SRU11 2 8 and Oracle VM Server for SPARC 3 2 for Oracle Solaris 10 How to restore Add the C
252. rkaround There is no effective workaround How to restore Execute the rebootxscf 8 command to reset the standby XSCF 92 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 9 Problems resolved in XCP 2250 continued SPARC M10 RTINo 1 4 4S Description RTIF2 x x x 150227 001 If you connect an input power cable of one of the power supply units PSUs in a redundant configuration right after disconnecting it the event logs for power failure and power recovery may not be registered In addition if you repeat the operation of connecting the input power cable of a PSU right after disconnecting it Input fail AC may appear in Power Status of PSU shown with the showhardconf 8 command even when the input power cable is connected Workaround Wait for at least 10 seconds after you disconnect an input power cable before connecting it again How to restore If Input fail AC appears in Power Status of the PSU shown with the showhardconf 8 command even when the input power cable is connected wait for at least 10 seconds after you disconnect the input power cable and then connect it again Problems resolved in XCP 2240 The following table lists the problems resolved in XCP 2240 Table 3 10 Problems resolved in XCP 2240 SPARC M10 RTINo 1 4 4S Description RTIF2 x x x 130305 003 If you reconnect the input power cable soon after it is unplugged the error
253. rmal sensor In these error logs the first two bytes of the second field in Code has the value of 0013 Workaround There is no effective workaround How to restore Turn off the system input power then restore the power AC OFF ON Problems resolved in XCP 2210 The following table lists the problems resolved in XCP 2210 Table 3 16 Problems resolved in XCP 2210 SPARC M10 RTI No 1 4 4S Description RTIF2 x x If a DIMM failure occurs a configuration 130801 002 error is erroneously detected and the following event log is registered SCF DIMM configuration error on PSB xx 0 RTIF2 x x x The Physical or Logical tree displayed 131126 005 in the menu frame is not updated even if you click the Refresh button of the masthead frame on XSCF Web RTIF2 x If there is a physical partition PPAR 131212 001 whose LSB number is 01 or larger the showlogs error command either does not show the I O device error detected log even if I O errors occur or the FRU in the I O device error detected message is displayed mistakenly Workaround There is no effective workaround Ignore this event log Using the maintenance procedure for DIMM failures turn off the input power to the SPARC M10 system chassis in which the failed DIMM is mounted replace the DIMM and then turn on the power These steps will remove the configuration error and failure Click the Physical or Logical tab of the menu frame to red
254. round If an I O failure is detected in the logical domain locate the failed portion from the display in Fault Report by executing the fmdump 1M command and perform maintenance on the failed part If a CPU or memory failure is detected in the XSCF perform maintenance according to the FRU displayed by executing the showlogs error command Ignore this message There is no effective workaround How to restore Execute the rebootxscf a command to reset all the XSCFs and then reactivate the control domain If restoration fails execute the poweroff 8 and poweron 8 commands on the XSCF to power off and then power on the physical partitions PPARs Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 20 RTI No RTIF2 131126 006 Problems resolved in XCP 2080 continued SPARC M10 1 4 4S x x x Description Suppose that the input power is turned off and on or that the XSCF is reset If an operation related to CPU core activation is performed for the first time using XSCF Web rather than the XSCF shell it may fail The procedure that fails is any of the following 1 Perform any of the following on XSCF Web From the Settings CoD Activation menu add the CPU core activation key From the Maintenance Configuration Management menu save the XSCF setting information From the Maintenance Configuration Management menu save restore the CPU core activa
255. rror message primary ldm migrate ldg1 root target name Target Password Domain ldgl is using features of the system firmware that are not supported in the version of the firmware running on the target machine Domain Migration of LDom ldgl failed When performing live migration from a SPARC M10 system with XCP 2210 or newer to another SPARC M10 system make sure to update the XCP firmware of the target system to XCP 2210 or newer Refer to the following table for the feasibility of performing live migration based 44 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 7 Migrate to Migrate from SPARC M10 Systems XCP 2230 or later SPARC M10 Systems XCP 2210 or later SPARC M10 Systems XCP 2092 or earlier SPARC T series SPARC M series 1 SysFW 8 4 or later SPARC T series SPARC M series 1 SysFW 8 3 or earlier on the version of the firmware Version of the firmware that support live migration SPARC M10 SPARC M10 SPARC M10 SPARC T series SPARC T series Systems Systems Systems SPARC M series SPARC M series 1 XCP 2230 or later XCP 2210 or later XCP 2092 or 1 SysFW 8 3 or earlier earlier SysFW 8 4 or later available available 2 not available available not available available available not available available available available available available available available available available not available available not available available av
256. s use setremotepwrmegmt c disable to disable power supply interlocking first and then use clearremotepwrmegmt to delete the power control group setting After deletion create a power supply interlocking group management information file so that the I O node is not registered with multiple groups and then use setremotepwrmgmt c config to register it again If XCP 2080 or earlier is used together with a single SPARC M10 system that is connected to an external I O device do not use the power supply interlocking Chapter2 XCP 2250 Related Information 27 function The external I O device may be erroneously powered off when the XSCF is reset For a management file to set the power supply interlocking function use CR and LF or LF as linefeed code For a management file to set the power supply interlocking function you need to specify the MAC address regardless of the node type Otherwise the following error occurs when you execute the setremotepwrmgmt 8 command Example XSCF gt setremotepwrmgmt c config u guest ftp xx xx xx xx rpmgroup csv Password Download successful 213Byte at 2103 000KB s Checking file The definition of MACAddress in ftp xx xx xx xx rpmgroup csv is invalid XSCF gt You need to set the MAC address regardless of the node type of the I O node master host node host node or remote power supply control unit This is required though the MAC addresses of some nodes are not set and left bla
257. s being diagnosed may enter an abnormal state and become unavailable After the hardware initial diagnosis detects a system board PSB error as described in the following error log the PSB may not be degraded but the physical partition PPAR may be reset repeatedly Code 40002000 003cff0000ff0000Ff 02000e000000000000000000 FRU BB x Msg SB deconfigured SB SB access error Code 40002000 003cff0000ff0000Ff 02000e010000000000000000 FRU BB x Msg SB deconfigured not running Even when policy is set to psb by the setpcl 8 command a unit of resource to be degraded when an error occurs may not be a system board but Field Replaceable Unit FRU The takeover IP address of an XSCF cannot be specified as a value for IPAddress or SlaveAddress which can be set in the management file for a power supply interlocking group If a failure occurs in a component in a physical partition PPAR the status of the PPAR in the SNMP MIB is not updated Workaround There is no effective workaround Execute the ldm list domain command from Oracle Solaris to check the domain status Confirm that the PWR of the PSB to be diagnosed is n and that Test is not Testing by using the showboards 8 command before executing the testsb 8 command If a PSB becomes unavailable power off the entire system and then power it on again Disconnect the PSB where an error is detected from the PPAR configuration by using the delet
258. s of PSB to be diagnosed An operation will fail if Test is set to other than Testing and Pwr is set to n In this case cancel the testsb 8 command by pressing Ctrl C There is no effective workaround Execute the showhardconf 8 command to check the status of the SPARC M10 4S to which the corresponding PSB No is assigned The SPARC M10 4S which has not been implemented is not displayed with the showhardconf 8 command When the corresponding SPARC M10 4S is displayed read the PSB No in the message PSB xx 0 is not installed as that of the unimplemented SPARC M10 4S that was specified when this command was executed Be sure to follow the procedure below when disconnecting the SPARC M10 4S and the crossbar box 1 Execute the initbb 8 command to stop the target chassis 2 Turn off the stopped chassis first and then disconnect the XSCF BB control cable Chapter 3 Information on Software 137 Table 3 20 RTI No RTIF2 131023 001 RTIF2 131023 004 RTIF2 131108 002 RTIF2 131112 009 138 Problems resolved in XCP 2080 continued SPARC M10 1 4 48 x x x x x x x xX x x x x Description If the XSCF is reset by the rebootxscf 8 or switchscf 8 command executed while the logical domain is either starting or stopped the following problems may occur If the showdomainstatus 8 command is executed the logical domain state is not displayed properly If the showlogs even
259. s on the logical domain time 25 Notes on Timezones 27 Notes on power supply interlock function RCIL 27 Other notes and restrictions 28 XCP 2250 Problems and Workarounds 33 Chapter3 Information on Software 35 Notes and Restrictions 35 Notes on internal disk drives of SPARC M10 systems 35 Notes on updating SPARC M10 system to Oracle Solaris 11 2 38 Notes on support for disks with an EFI GPT label 41 Notes on Oracle VM Server for SPARC 42 Notes on live migration of Oracle VM Server for SPARC 43 Notes on a case when recovery mode of Oracle VM Server for SPARC is enabled 45 Notes on a case where openssl is used 46 Notes on remote maintenance service 47 Notes on SNMP 48 Problems with XCP and Workarounds 49 iv Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Problems that might occur with XCP 2250 and workarounds 49 Problems resolved in XCP 2250 88 Problems resolved in XCP 2240 93 Problems resolved in XCP 2232 101 Problems resolved in XCP 2231 101 Problems resolved in XCP 2230 101 Problems resolved in XCP 2221 107 Problems resolved in XCP 2220 107 Problems resolved in XCP 2210 117 Problems resolved in XCP 2092 125 Problems resolved in XCP 2091 126 Problems resolved in XCP 2090 127 Problems resolved in XCP 2080 136 Problems resolved in XCP 2070 139 Problems resolved in XCP 2052 150 Problems resolved in XCP 2051 150 Problems resolved in XCP 2050 151 Problems resolved in versions prior to XCP 2050
260. s output to the domain console before the OpenBoot PROM banner is displayed 14 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 NOTICE Entering OpenBoot NOTICE Fetching Guest MD from HV NOTICE Starting additional cpus NOTICE Initializing LDC services NOTICE Probing PCI devices NOTICE Finished PCI probing Suppose the following The environment variable multipath boot of OpenBoot PROM is true the boot L command is executed to display boot environments BEs that existing in the root pool allow booting and the number of a boot environment is selected from the displayed interactive menu The system does not return to the ok prompt but restarts OpenBoot PROM The number of restarts depends on the environment variable boot device of OpenBoot PROM OpenBoot PROM restarts as many times as the number of configured devices and then the message ERROR All device paths in boot device have failed is displayed and the ok prompt reappears To avoid this problem set the environment variable multipath boot of OpenBoot PROM to false before executing the boot L command or execute the boot device_path L command Suppose you execute the boot command with arguments omitted while multipath boot of the OpenBoot PROM environment variable is set to false and all the booting from devices specified in boot device of the OpenBoot PROM environment variable fails The message output to the domain conso
261. s time is other than January 1 2001 contact a field engineer In this case do not execute the resetdateoffset 8 of setdate 8 command on the XSCF c If the PPAR power is off power on the PPAR After that check the Oracle Solaris time and perform the above steps a or b If phenomenon 2 occurs a If the Oracle Solaris time has returned to January 1 2001 it is necessary to initialize the time difference between the XSCF time and Hypervisor on all of the PPARs Stop all the PPARs and execute the resetdateoffset a command to clear the time difference b If the Oracle Solaris time is other than January 1 2001 contact a field engineer In this case do not execute the resetdateoffset 8 of setdate 8 command on the XSCF c If the PPAR power is off power on the PPAR After that check the Oracle Solaris time and perform the above steps a or b If phenomenon 3 occurs If phenomenon 1 or 2 also occurs perform its How to restore action first Set the Oracle Solaris time again Chapter 3 Information on Software 149 Problems resolved in XCP 2052 The following table lists the problems resolved in XCP 2052 Table 3 22 Problems resolved in XCP 2052 SPARC M10 RTI No 1 4 4S Description Workaround RTIF2 x x x A timeout or connection failure may be There is no effective workaround 130827 001 detected for the communication party because XSCF packet reception is delayed delaying the response due toa defect in the XS
262. s to Oracle and or its affiliates and Fujitsu Limited including software and font technology Per the terms of the GPL or LGPL a copy of the source code governed by the GPL or LGPL as applicable is available upon request by the End User Please contact Oracle and or its affiliates or Fujitsu Limited This distribution may include materials developed by third parties Parts of the product may be derived from Berkeley BSD systems licensed from the University of California UNIX is a registered trademark of The Open Group Oracle and Java are registered trademarks of Oracle and or its affiliates Fujitsu and the Fujitsu logo are registered trademarks of Fujitsu Limited SPARC Enterprise SPARC64 SPARC64 logo and all SPARC trademarks are trademarks or registered trademarks of SPARC International Inc in the United States and other countries and used under license Other names may be trademarks of their respective owners If this is software or related documentation that is delivered to the U S Government or anyone licensing it on behalf of the U S Government the following notice is applicable U S GOVERNMENT END USERS Oracle programs including any operating system integrated software any programs installed on the hardware and or documentation delivered to U S Government end users are commercial computer software pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplicatio
263. s with Oracle Solaris and Workarounds Notes and Restrictions Notes on internal disk drives of SPARC M10 systems We recommend using an internal SAS disk of SPARC M10 systems with the Oracle Solaris MPxIO setting enabled Cause It enhances redundancy because disk access continues even when the communication paths of an internal SAS controller are degraded due to a failure etc Note that you can set MPxIO to enable by using the bundled tool from Enhanced Support Facility 5 0 or later Note Only SPARC M10 systems sold by Fujitsu in Japan support Enhanced Support Facility ESF 35 Target disks Whether you need to perform the Oracle Solaris MPxIO setting depends on the product name of the internal SAS disk or the SSD mounted in the SPARC M10 system and the Oracle Solaris version as shown in Table 3 1 Table 3 1 Necessity of MPxIO setting for an internal SAS disk or an SSD Product name Necessity of MPxIO setting Oracle Solaris 10 1 13 Oracle Solaris 11 1 Oracle Solaris 11 2 AL13SEB600 Required 1 Required 1 Not required 3 AL13SEB900 Required 1 Required 1 Required 1 MBF2600RC Required 1 Required 1 Not required 3 MK1001CRZB Required 1 Required 1 Not required 3 MK2001CRZB Required 1 Required 1 Not required 3 Other HDD and SSD Required 2 Required 2 Required 2 When the internal hardware Not required 4 Not required 4 Not required 4 RAID is specified 1 MPxIO is disabled b
264. sec O 30 60 90 120 150 180 2 210 240 270 300 330 Hardware error occurred by initial diagnosis SB power off sequence started 1200sec Osse BD 5200605 9025120 150 180 210 240 270 300 330 360 390 420 450 hts 480 510 540 570 600 630 660 690 720 sats 790 0 80 810 840 870 900 930 960 990 sess 1020 1050 1080 1110 1140 1170 1200end Failed to power off Please check the FRU An internal error has occurred Please contact your system administrator done Problems that might occur with XCP 2250 and workarounds continued Workaround There is no effective workaround Ignore this message There is no effective workaround How to restore Execute maintenance on the failed hardware after confirming it with the showlogs 8 command After that execute the testsb 8 command again 60 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 RTI No RTIF2 140227 005 RTIF2 140227 009 RTIF2 140227 010 RTIF2 140304 001 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 X Description At the time of cold replacement or cold addition of CPU memory unit lower CMUL or SPARC M10 chassis if the following conditions are met the XCP firmware version synchronization failed
265. sername Auth Encrypt user_name SHA DES Example To display the setting information for the SNMPv3 agent VACM XSCF gt showsnmpvacm Groups Groupname Username test_group user_name Views None Access None SMTP service setting Example To display the SMTP setting information XSCF gt showsmtp Mail Server Port 25 Authentication Mechanism none Reply Address E mail notification function setting Example To display the e mail report setting information XSCF gt showemailreport E Mail Reporting disabled 4 Execute the restoreconfig 8 command to restore the XSCF setting information 5 After restoring the XSCF setting information with the restoreconfig 8 command execute the command below to implement a reset using the setting values confirmed in step 1 Or initialize Chapter 3 Information on Software 67 Table 3 8 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 RTI No 1 4 4S Description Workaround the time difference Restoring setting for power operation at power recovery Example Not powering on at power recovery XSCF gt setpowerschedule a c recover off Restoring ASR function Service Tag enable disable setting Example Setting to enable XSCF gt setservicetag c enable Restoring PPAR DR feature enable disable setting Example Setting to disable XSCF gt setpparmode p 0 m ppar_dr off Restoring configuration and setting changes of power supply interl
266. sold as SPARC M10 Systems by Fujitsu in Japan Fujitsu M10 and SPARC M10 Systems are identical products This preface includes the following sections m Audience How to Use This Document Related Documentation Disposal and recycling Documentation Feedback Audience This document is designed for system administrators with advanced knowledge of a computer network and Oracle Solaris How to Use This Document This document supports all models of SPARC M10 Systems Depending on the server you use read the related items listed in the following table Chapter titles in this document SPARC M10 1 SPARC M10 4 SPARC M10 4S Chapter 1 Software Requirements x x x Chapter 2 XCP 2250 Related Information x x X Chapter 3 Information on Software x x x Chapter 4 Information on SPARC M10 1 Hardware x Chapter 5 Information on SPARC M10 4 Hardware x Chapter 6 Information on SPARC M10 4S Hardware x Chapter 7 Information on PCI Expansion Unit Hardware x when x when x when introduced introduced introduced Chapter 8 Contents of Revision of Documentation x x X The information about firmware and software which are described in Chapter 1 Chapter 2 and Chapter 3 is common to all models Some of the information are only related to a specific model In such case the applicable model name is indicated The information about hardware devices is provided in Chapter 4 Chapter 5 and Chapter 6 separately for each model The contents
267. solved in version 1150 of the PCI expansion unit firmware The following table lists the problems resolved in version 1150 of the PCI expansion unit firmware Table 7 5 Problems resolved in version 1150 of the PCI expansion unit firmware SPARC M10 RTI No 1 4 4S Description Workaround RTIF2 x x x Oracle Solaris may hang while There is no effective workaround 131224 001 starting up if using the direct I O feature in respect to the PCI Expansion Unit The probability of the occurrence of this symptom increases with the number of PCI cards that are mounted on the PCI Expansion Unit 206 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 7 5 Problems resolved in version 1150 of the PCI expansion unit firmware continued SPARC M10 RTI No 1 4 4S Description Workaround RTIF2 x x x When the PCI Expansion Unit and Ignore this error message as it has no effect on 131224 002 the chassis of SPARC M10 system the system are connected by optical cables in a low temperature environment optical cable error logs may be registered This symptom can be confirmed by the showlogs error v command If the result of the showlogs error v command is Msg LINKCBL failed and the 3rd byte of the 4th line of the Diagnostic Code is either 10 50 or 60 it corresponds to this symptom Example of the error message In case the 3rd byte of the 4th line of the Diagnostic Code is 10 XSCF gt show
268. store Perform the following on the disconnected SPARC M10 4S chassis Chapter 3 Information on Software 69 Table 3 8 RTI No RTIF2 140407 008 RTIF2 140409 001 RTIF2 140409 002 RTIF2 140409 003 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 4 48 x x x x x xX x x xX x Description the chassis from the system the chassis remains assigned to the physical partition PPAR To check this phenomenon execute the showboards 8 command to confirm Workaround 1 Execute the replacefru 8 command to replace the chassis 2 Power on AC ON the replacement chassis If the READY LED of the XSCF or whether Assignment of the target SPARC XSCF unit is lit M10 4S chassis PSB remains Assigned XSCF gt showboards av PSB RPPAR ID LSB Assignment Pwr Conn Conf Test Fault 00 0 00 00 Assigned y y y Passed Normal 01 0 00 01 Assigned n n n Unmount Normal If the poweroff 8 command is executed and the master chassis XSCF is reset during the time that it takes for a prompt to be returned the following power on power off operation cannot be executed An error may be detected in the Realtime Clock RTC built into the SPARC M10 system and XSCF may not start If you disconnect and then connect the USB memory while the executed snapshot 8 command is collecting information into the memory the hardware error below may be detected Msg DMA timeout error Har
269. switched over during update will stay switched over gt gt Execute the flashupdate 8 command from the master XSCF of BB 00 The XSCF of BB 00 that has executed the flashupdate 8 command is in the standby status immediately after XSCF reset XSCF automatic switchover is performed after the update has been completed When XSCF automatic switchover is completed the XSCF of BB 00 that has executed the flashupdate 8 command is restored to the status of the original master Confirm that the update has been completed by referring to the log message XCP update has been completed from the master XSCF of BB 00 Execute the flashupdate 8 command from the master XSCF of BB 00 The XSCF of BB 00 that has executed the flashupdate 8 command is in the standby status immediately after XSCF reset XSCF automatic switchover is not performed after the update has been completed For this reason the XSCF of BB 00 that has executed the flashupdate 8 command will stay in the standby status Confirm that the update has been completed by referring to the log message XCP update has been completed from the master XSCF of BB 01 To restore the status of the master and standby XSCFs to the status before the update execute the switchscf 8 command from the master XSCF of BB 01 to restore the XSCF of BB 00 to the master When updating firmware errors described in Problems with XCP and Workarounds may occu
270. t XSCF LAN may seem to be in the active state of RUNNING Example If no cable is connected to XSCF LAN 1 XSCF gt shownetwork a bb 00 lan 0 Link encap Ethernet HWaddr 00 00 00 12 34 56 inet addr 192 168 11 10 Beast 192 168 11 255 Mask 255 255 255 0 UP BROADCAST RUNNING MULTICAST MTU 1500 Metric 1 Omitted bb 00 lan 1 Link encap Ethernet HWaddr 00 00 00 12 34 57 inet addr 192 168 10 10 Beast 192 168 10 255 Mask 255 255 255 0 UP BROADCAST RUNNING MULTICAST MTU 1500 Metric 1 Omitted RTIF2 x x x _ IFXSCF is reset due to any of the 150220 001 following while the physical partition PPAR is active a break signal may be sent to the control domain of PPAR rebootxscf 8 command execution watchdog timeout occurrence due to a firmware factor Panic occurrence due to a firmware factor Pressing of RESET switch of XSCF This problem may occur even when you execute the setppartmode 8 command to set the break signal suppression RTIF2 x Suppose you set the power supply 150226 001 interlocking group with the setremotepwrmgmt 8 command when the power supply interlock function RCIL is used on a system configured with two or more SPARC M10 4S If you execute the switchscf command on the master XSCF to switch between master and standby power supply interlocking may fail in the subsequent power supply operation Workaround This state does not affect the system operation Use it as is There is no effective wo
271. t Mode fast However the correct result will be that the Current Mode be normal like the following XSCF gt xscfstartupmode d Setting Mode fast need AC OFF ON Current Mode normal RTIF2 x In the event of an instantaneous power There is no effective workaround 140523 001 failure lasting 11 ms or more the CHECK How to restore LED on the operation panel will remain After turning off the input power wait on after recovery and the XSCF may not for at least 10 seconds before turning it start on again Therefore even if the system is set to automatically start after recovery it may not actually start automatically Chapter 3 Information on Software 95 Table 3 10 Problems resolved in XCP 2240 continued SPARC M10 RTINo 1 4 4S Description RTIF2 x x x 140616 003 If a problem occurs with the microSD card on the XSCF or the XSCF unit you may not be able to access data in the restored XSCF This may cause the output of the error message An internal error has occurred Please contact your system administrator at the execution of the following command After this the command terminates abnormally initbb 8 resetdateoffset 8 setpciboxdio 8 setpowercapping 8 setpparmode 8 setpparparam 8 setservicetag 8 In addition the following command execution terminates normally but the setting information is not reflected in the system addboard 8 deleteboard 8 setpcl 8 setupfru 8 This problem also
272. t command is executed the log used for notification of the logical domain state is not displayed An SNMP Trap for notification of the state of the logical domain is not sent Even when an I O failure is detected in the logical domain the XSCF may not be notified of an error For this reason the T O failure information in Fault Report to be displayed from the execution of the fmdump 1M command is not displayed even if the showlogs error command is executed Moreover even if a CPU or memory error is detected in the XSCF no notification may be sent to the logical domain For this reason Fault Report does not display the CPU or memory failure information to be displayed from the execution of the showlogs error command even if the fmdump 1M command is executed The warning message WARNING invalid vector intr number 0x10001 pil 0x11000 may be output to var adm messages If the physical partition PPAR is powered on the event log of LDC Protocol info from PPAR PPAR ID 0 Domain Service Data Send Failed is output Moreover after Oracle Solaris activation ldoms ldmd default failed transitioned to maintenance is output to the OS console This may cause Oracle VM Server for SPARC to enter maintenance mode Workaround There is no effective workaround How to restore To display the state of the logical domain properly update it such as by reactivating the logical domain There is no effective worka
273. t occur with XCP 2250 and workarounds continued Workaround There is no effective workaround This incorrect SNMP Trap sending does not affect the behavior of the PCI expansion unit or the PCle card May 2015 Table 3 8 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 RTI No 1 4 4S Description Workaround RTIF2 x CHECK LED of the old master XSCF There is no effective workaround 150226 002 blinks during the master standby Ignore the blinking CHECK LED of the switchover of XSCFs old master XSCF during the master standby switchover of XSCFs RTIF2 x After updating the firmware with the When updating the firmware with the 150313 001 flashupdate 8 command while the flashupdate 8 command while the physical partition is powered on if dynamic reconfiguration of PPARs is performed without first rebooting the PPAR in order to update the CMU firmware the following error log may be registered Warning BB x CMUL SCF POST OBP HV data write error physical partition is powered on reboot the PPAR before performing dynamic reconfiguration of PPARs Moreover the error message when the problem occurs may be ignored as it has no effect on the proper functioning of the system Workaround for RTIF2 140304 007 If PSU is replaced by the replacefru 8 command after mounting the new PSU wait for at least 30 seconds before pressing the f key of the menu of replacefru 8 command Do you Please
274. t started turn off the power of the physical partition PPAR and then disconnect the input power supply to the system and back on again AC OFF ON When recycling the power supply to the system wait for 30 seconds or more to turn on the input power supply after disconnecting In case XSCF is not started even if recycling the input power supply to the system replace the CPU memory unit lower CMUL or the motherboard unit MBU Execute the showsnmp 8 command again to confirm that the snmp daemon is restarted If Agent Status Disabled remains displayed execute the setsnmp enable command to restart the snmp daemon Ignore this message Ignore the message that appears second time and later There is no effective workaround There is no effective workaround If the following message appears when you execute the poweron 8 command the clock in the XSCF board has failed Replace the XSCF board Poweron canceled due to invalid system date and time Connect the operation panel If the operation panel has failed replace it There is no effective workaround Chapter 3 Information on Software 157 Table 3 25 RTI No RTIF2 121113 025 RTIF2 121113 027 RTIF2 121113 031 RTIF2 121129 001 SPARC M10 1 4 4S x x x x xX x x x x x x x Description When a CPU failure occurs an error message showing degradation or offline on Oracle Solaris may not be output to Syslog If you update the fir
275. tart even after turning on the input power Workaround There is no effective workaround There is no effect of this wrong display on the system There is no effective workaround How to Restore Turn off on the input power AC OFF ON of the system There is no effective workaround How to Restore Replace the CPU memory unit lower CMUL the XSCF unit XSCFU or the motherboard unit MBU Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 15 RTI No RTIF2 140605 007 Problems resolved in XCP 2220 continued SPARC M10 1 4 4S Description x x x _ For XCP 2041 or later when an error log for a configuration error in a power supply unit PSU is registered inappropriate message text is registered for this log Although the message text should indicate the mixing of different AC input voltages 100 V and 200 V it indicates the existence of an incorrect combination of PSU types Example Message text to the right of Msg inappropriately registered when different AC input voltages of 100 V and 200 V are mixed Code 80000000 0001020000 f0000ff 018af 0220000000000000000 Status Alarm Occurred May 27 11 22 00 0000 JST 2014 FRU MBU Msg Wrong PSU is installed The correct message indicating the mixing of different AC input voltages is as follows Msg PSUs detected 100V and 200V at AC inputs Workaround There is no effective workaround Execute the sho
276. te Power Management Group 01 Information Remote Power Management Status Enable Omitted Time difference between XSCF and the hypervisor of each PPAR Example If there is a time difference between XSCF and the Chapter 3 Information on Software 65 Table 3 8 RTI No Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 4 4S Description Setting values for the e mail notification function set with the setemailreport 8 command Furthermore since the PPAR DR feature setting values cannot be saved restored powering on the PPAR after executing the following procedure switches the logical domain configuration information to the factory default state 1 Execute the setpparmode p ppar_id m ppar_dr command to enable disable the PPAR DR feature 2 Execute the dumpconfig 8 command to save XSCF setting information 3 Initialize the chassis to factory defaults by executing the initbb 8 or the restoredefaults 8 command 4 Restore the XSCF configuration information of the chassis in procedure 3 with executing the restoreconfig 8 command 5 Power on the PPAR by executing the poweron 8 command Workaround hypervisor of each PPAR XSCF gt showdateoffset a PPAR ID Domain Date Offset 00 12 sec 01 12 sec Omitted 15 12 sec 2 Execute the dumpconfig 8 command to save the XSCF setting information 3 If the XSCF setting information is to be restored
277. the Install Server feature fails 3 On a SPARC M10 system with SPARC64 X processors installation of Enterprise Controller and Proxy Controller Ops Center management server on the domains fail Workaround This has been modified with SRU11 1 17 5 and the patch 150817 02 for Oracle Solaris 10 Check the memory size that has been assigned to a logical domain with the Idm list domain command and reduce it to the required size in several steps using the Idm remove memory command It is recommended to reduce memory size by less than 256 MB at one time but memory may also be reduced by a larger amount at one time Meanwhile the reduction may fail due to the occurrence of the same symptom while performing this action In such a case reduce the memory in smaller units This has been modified with SRU11 1 17 5 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 An error occurs in executing the scp 1 sftp 1 or ssh 1 command of Oracle Solaris or the installation of Oracle RAC fails CR 15825208 Workaround Using the following procedure change the setting so that the AES_CTR AES_CBC_ MAC and AES_CFB128 algorithms are not used with the assist function of the encryption unit If you use it with the client function scp 1 sftp 1 ssh 1 etc 1 Add the content of the setting to the target file as one line A space is necessary only between Cipher and aes128 cbc Target file
278. the Oracle Solaris time is other than January 1 1970 contact a field engineer In this case do not execute the resetdateoffset 8 of setdate 8 command on the XSCF c If the PPAR power is off power on the PPAR After that check the Oracle Solaris time and perform the above steps a or b If phenomenon 2 occurs a If the Oracle Solaris time has returned to January 1 1970 it is necessary to initialize the time difference between the XSCF time and Hypervisor on all of Chapter 3 Information on Software 155 Table 3 25 RTI No RTIF2 121113 001 RTIF2 121113 002 RTIF2 121113 006 RTIF2 121113 007 the PPARs Stop all the PPARs and execute the resetdateoffset a command to clear the time difference b If the Oracle Solaris time is other than January 1 1970 contact a field engineer In this case do not execute the resetdateoffset 8 of setdate 8 command on the XSCF c If the PPAR power is off power on the PPAR After that check the Oracle Solaris time and perform the above steps a or b If phenomenon 3 occurs If phenomenon 1 or 2 also occurs perform its How to restore action first Set the Oracle Solaris time again Problems resolved in versions prior to XCP 2050 The following table lists the problems resolved in versions prior to XCP 2050 Problems resolved in versions prior to XCP 2050 SPARC M10 1 4 4S Description x x x After setting an invalid value for the user name with the
279. the PCI expansion unit firmware SPARC M10 RTI No 1 4 4S RTIF2 x x x 140715 001 RTIF2 x xX x 141111 003 Description In a PCI expansion unit if the power supply unit PSU has a redundant configuration and the power cable connected to one of the power supply units is pulled out a PSU error may be erroneously detected and the PCI expansion unit chassis Check LED amber may go on At this time executing the showlogs error command outputs the Msg PSU failed log In a PCI expansion unit a power supply unit PSU failure is erroneously detected if you perform the following operations in the condition that a power cable connected to either of PSUs in a redundant configuration is pulled out Power on of a physical partition PPAR Mount a PCI expansion unit in PCI hot plug PHP Also Check LED amber of the PCI expansion unit chassis may go on You can confirm this phenomenon with the showlogs error v command If the result of the showlogs error v command shows Msg PSU failed and the fifth x08 bit from left of the second byte of the forth line of Diagnostic Code shows 1 any of 8 9 a b c d e f it corresponds to this failure Error message example If the left of the second byte of the forth line of Diagnostic Code shows 49 XSCF gt showlogs error v Date Nov 06 17 10 14 JST 2014 Code 80000408 Chapter 7 Workaround There is no effective workar
280. the PCI expansion unit firmware and their workarounds Workaround The display of this error message does not affect the operation When this problem occurs in the link board the CHECK LED on the PCI expansion unit turns on However if this problem does not occur at the next start of the PPAR the CHECK LED turns off Do not replace an I O board together with a fan backplane Also do not mount in the PCI expansion unit an I O board or fan backplane that has been used previously in another PCI expansion unit If the serial number of the PCI expansion unit that is displayed in response to execution of the ioxadm v list command consists entirely of 0 s 0000000000 execute the ioxadm 8 command of the XSCF firmware to restore the serial number In this case you need the fieldeng privilege For details see Restoring the serial number of the PCI expansion unit RTIF2 130703 006 Restoring the serial number of the PCI expansion unit RTIF2 130703 006 If the serial number of the PCI expansion unit that is displayed in response to execution of the ioxadm v list command consists entirely of 0 s 0000000000 execute the ioxadm 8 command of the XSCF firmware to restore the serial number In this case you need the fieldeng privilege 210 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 XSC XSC F gt ioxadm F gt ioxadm Location PGI PCI PCI PCI PCI PCI BOX 2006 BOX 2006 B
281. the XCP firmware through the following procedure 1 Check the current configuration information of the logical domain stored in XSCF This example assumes that the name of the saved logical domain configuration information is config1 XSCF gt showdomainconfig p 0 20xx yy zz hh mm ss PPAR ID O Booting config 154 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Current configl Next configl Index al config name factory default domains ale date _created Index eZ config name configl domains i2 date_created 20xx yy zz hh mm ss 2 Set a dummy variable and then clear it for all logical domains Execute the following commands for all logical domains primary ldm set variable fix php true ldom primary ldm remove variable fix php ldom w Save the changed configuration in XSCF to replace the current configuration information In this example the name of the current configuration information is replaced with config1 primary ldm remove spconfig configl primary ldm add spconfig configl 4 Restart all logical domains Restoration after erroneous detection of the SCF Diagnosis initialize RTC error RTIF2 131107 002 How to restore If phenomenon 1 occurs a If the Oracle Solaris time has returned to January 1 1970 execute the setdate 8 command to set the XSCF time again In this case the XSCF is reset After that power off and on the PPAR b If
282. tion by the applynetwork 8 command if the shownetwork 8 command is executed without executing the rebootxscf 8 command the displayed IP address may not match the IP address that is being used on the present system In the middle of performing diagnosis by the p and b options of the diagxbu 8 command if a failure occurs in the physical partition specified by the p option the diagxbu 8 command may terminate abnormally and powering off the SPARC M10 chassis specified by the b option may fail When the crossbar cable of the crossbar unit XBU in SPARC M10 4S is in bad electrical contact the crossbar cable components are depicted with a number of s as the result of the showhardconf 8 command Example When the crossbar cable is loose FRU Part Number 4H 48 HH Ver h Type Length Workaround Manual for replacing the crossbar box or the XSCF unit in the crossbar box How to Restore Turn off on the input power AC OFF ON of the replaced crossbar box There is no effective workaround Ignore this error log as the command in question is terminated properly and thus it has no effect on the system After executing the applynetwork 8 command to apply network configurations of the XSCF execute the rebootxscf 8 command to reset the XSCF There is no effective workaround How to Restore Perform the following procedure 1 Turn off the input power AC OFF of
283. tion key 2 Execute the deletecodactivation 8 or setcod 8 command on the XSCF shell Alternatively delete the CPU core activation key on XSCF Web Alternatively change the assignment of the CPU core activation on XSCF Web Alternatively 1 Perform any of the following on XSCF Web From the Settings CoD Activation menu delete the CPU core activation key From the Settings CoD Reservation menu release the assignment of the CPU core activation 2 Log in to the XSCF shell or XSCF Web with another user account 3 Execute the deletecodactivation 8 or setcod 8 command on the XSCF shell Alternatively delete the CPU core activation key on XSCF Web Alternatively change the assignment of the CPU core activation on XSCF Web Workaround To perform an operation related to the CPU core activation for the first time after the input power is turned off and on or after the XSCF is reset execute it on the XSCF shell How to restore Execute the rebootxscf 8 command to reset the XSCF Then execute the deletecodactivation 8 or setcod 8 command on the XSCF shell Problems resolved in XCP 2070 The following table lists the problems resolved in XCP 2070 Chapter 3 Information on Software 139 Table 3 21 RTI No RTIF2 130228 001 RTIF2 130516 001 RTIF2 130709 001 140 Problems resolved in XCP 2070 SPARC M10 1 4 48 x x x x x x x Description If a physical partition PPA
284. tition is active the status is other than Powered Off You can access XSCF but the execution result of the showlogspower command does not include SCF Reset indicating that XSCF is reset 1 If a power failure notification is issued usually the following log is registered by the showlogsevent command PSU input power failure PSU 0 PSU input power failure PSU 1 In addition the following error log is detected in many cases when the trouble in 1 occurs failed to read write extended active status register RTIF2 150218 001 x Suppose you execute any of the following on a system with a PCI expansion unit connected when the power to the physical partition is on In such case an SNMP Trap related to the addition of the PCI expansion unit or the link card is sent by mistake Reset XSCF Switch master standby XSCF Change the SNMP agent from the disabled state to the enabled state Set the SNMP agent management information when the SNMP agent is enabled In such case the following SNMP Traps are sent PCI expansion unit addition scfPciBoxEvent scfTrapEventType add 10 Link card addition scfComponentEvent scfTrapEventType add 10 Similarly the following SNMP Trap on the PCIe card addition is sent by mistake in a system with a PCIe card connected scfComponentEvent scfTrapEventType add 10 86 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 Problems that migh
285. to be cold replace In case of a LDAP server specified by the setldap 8 command there is no effective workaround Specify the LDAP server with the setldapssl 8 command There is no effective workaround Execute the addboard c configure command specifying existent PSBs There is no effective workaround If this symptom has occurred contact the maintenance staff Chapter 3 Information on Software 61 Table 3 8 RTI No RTIF2 140304 002 RTIF2 140304 003 Problems that might occur with XCP 2250 and workarounds continued SPARC M10 1 X X Description The SCF process down detected error log may be registered when the flashupdate 8 command is running In case of SNMPv3 if the trap host name registered by the setsnmp 8 command contains a colon it does not show up properly by the showsnmp 8 command Example In case the trap host name is test example com the host name is shown as test and port number is shown as 0 Workaround There is no effective workaround When restoration is not required If both of the following conditions are met there is no need for restoration It may be assumed that firmware update has completed properly The showlogs error rv command reveals that the following diagnostic message along with the Msg SCF process down detected error message had been registered when the flashupdate 8 command was running Example Diagnostic Code
286. to remove the Failure mark from the PSU Chapter 3 Information on Software 109 Table 3 15 SPARC M10 RTI No 1 4 4S RTIF2 x x x 140227 006 RTIF2 x 140227 007 RTIF2 x x x 140227 008 RTIF2 x xX x 140310 001 RTIF2 x X x 140312 001 110 Problems resolved in XCP 2220 continued Description If Ctrl C is pressed when any of the following command is running in some very rare cases the command may not terminate moreover other running commands executed by other logged in users may not terminate as well ping 8 setservicetag 8 shownetwork 8 showntp 8 showpacketfilters 8 showservicetag 8 traceroute 8 When the SSCP IP address of an unmounted SPARC M10 4S chassis is set up using the setsscp 8 command the showsscp 8 command displays the Not installed message and thus the set IP address cannot be confirmed Therefore before adding SPARC M10 4S chassis or cross bar boxes with the addfru 8 command SSCP IP address of the added chassis cannot be confirmed with the showsscp 8 command When the lockout feature of user accounts is enabled with the setloginlockout 8 command if three logins to the XSCF Web are performed with the same user account further logins are disabled for the duration of the configured lockout time If server certificate is imported with the setldap c command an error is produced and importing fails Configuration of SNMP fails when it is done from the SNMP o
287. tore Restart the physical partition according to the following steps 1 Execute the poweroff 8 command to power off the physical partition PPAR 2 Execute the poweron 8 command to restart PPAR Chapter 3 Information on Software 173 Table 3 26 Bug 19728345 20646928 174 Problems that might occur in any versions of Oracle Solaris and workarounds continued SPARC M10 1 4 4s x x Description The physical partition dynamic reconfiguration PPAR DR fails if the ldoms ldmd services are restarted because of Oracle Solaris panic and the like during PPAR DR If you perform dynamic deletion with the dynamic reconfiguration function of the physical partition for a system board with the system volume located in the following environment system board deletion processing may fail Problem occurrence conditions 1 A ZFS mirror volume is created by using an internal SAS disk of the SPARC M10 system or a disk on an external storage connected with the 6Gbps SAS card and 2 the mirroring disk and mirrored disk are located in different system boards and 3 you dynamically delete a system board to which a system volume is assigned This trouble does not occur if the system volume is located on external fiber channel storage Example of output message XSCF gt deleteboard c disconnect m unbind resource 00 0 PSB 00 0 will be unconfigured from PPAR immediately Continue y n y All domains are t
288. tpcl 8 command to change the LSB number of a SPARC M10 system chassis to which a PCI expansion unit is connected and start Oracle Solaris in the logical domain configuration you cannot display the configuration information of the PCI expansion unit by executing the showhardconf 8 command If an error occurs with a crossbar unit mounted on a crossbar box many instances of failed to read write interrupt mask register may be registered in the error log If you restart an XSCF by using the flashupdate 8 or rebootxscf 8 command while a physical partition PPAR is being powered on the POST may stop in a state where the diagnosis is completed Initialization Complete The limit of power has been exceeded is registered in the event log if you perform the following Execute the setpowercapping 8 command to set the power consumption limiting function to Enable the power consumption maximum allowable value to Specify 100 percent default and the time extension when exceeding the maximum allowable power consumption to none Then turn on the input power supply or turn off the power to the physical partition PPAR Workaround Use the setdomainconfig 8 command to set the logical domain configuration to the factory default and power on the physical partition PPAR Then configure the logical domain again There is no effective workaround Power off the physical partition PPAR and replace the crossbar unit i
289. uch that it may not be possible to register one for a new user account Moreover if a user account with the same name is registered again the SSH user public key registered previously is set Even when the snapshot 8 command is executed it does not collect log data concerning NTP related statistics Replacing SPARC M10 45 When replacing the SPARC M10 4S by following the maintenance menu displayed by executing the replacefru 8 command perform Step 3 and then turn on the input power to the target SPARC M10 45 BB x Then after waiting for 50 minutes manually enter f in Step 4 to perform the work Please execute the following steps 1 Remove Delete the BB x from a system 2 Turn off the breaker of the BB x After the exchanged device is connected with the system the breaker of the BB x Please select f finish Adding SPARC M10 4S Workaround Before deleting a user account with the deleteuser 8 command execute setssh c delpubkey a u to delete the SSH user public key registered for the user account How to restore Perform the following procedure 1 Execute the adduser 8 command to register the deleted user account again 2 Execute the rebootxscf a command to reset the XSCF or turn off and on the input power 3 Execute setssh c delpubkey a u to delete the SSH user public key 4 Execute the deleteuser 8 command to delete the user account There is no effective workaround
290. uct Notes for XCP Version 2250 May 2015 XCP Oracle Solaris and required SRU patches supported by the SPARC M10 system continued Required SRU 4 Required patch 5 None SRU1 4 or later 3 150310 03 or later None SRU1 4 or later 3 150310 03 or later None SRU1 4 or later 3 150310 03 or later None SRU1 4 or later 3 150310 03 or later None SRU1 4 or later 3 7 150310 03 or later 8 None SRU1 4 or later 3 7 150310 03 or later 8 Table 1 1 XCP Oracle Solaris and required SRU patches supported by the SPARC M10 system continued Server XCP Oracle Solaris Required packages 4 Required SRU 4 Required products 5 Required patch 5 SPARC64 2210 or Oracle Solaris 11 2 system Idoms 1 None X 3 7GHz later system ldoms ldomsmanager 2 Oracle Solaris 11 1 system Idoms 1 SRU1 4 or system Idoms ldomsmanager 2 later 3 7 Oracle Solaris 10 Oracle VM Server for SPARC 3 0 or 1 13 6 later 3 7 8 150310 03 or later 8 SPARC64X 2043 or Oracle Solaris 11 2 system Idoms 1 None 3 0 GHz later system ldoms ldomsmanager 2 Oracle Solaris 11 1 system Idoms 1 SRU1 4 or system ldoms ldomsmanager 2 later 3 7 Oracle Solaris 10 Oracle VM Server for SPARC 3 0 or 150310 03 or 1 13 6 later 3 7 8 later 8 1 Required for the control domain and the guest domain Included in group system solaris large server and group system solaris small server 2
291. ujitsu M10 SPARC M10 Systems System Operation and Administration Guide Note The CMU firmware version may differ with the XCP version For example in XCP 2042 the XSCF version is 02 04 0002 whereas the CMU version is 02 04 0001 Chapter1 Software Requirements 9 10 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Chapter 2 XCP 2250 Related Information This chapter provides XCP 2250 related information Latest Information on XCP 2250 Notes and Restrictions XCP 2250 Problems and Workarounds Latest Information on XCP 2250 This section describes major changes in XCP 2250 This XCP version modifies XSCF firmware and CMU firmware Note After the firmware update completes power off power on of the physical partition may be required For details on firmware update see 16 1 Updating the XCP Firmware in the Fujitsu M10 SPARC M10 Systems System Operation and Administration Guide For SPARC M10 1 M10 4 SPARC64 X processor 3 7 GHz is supported m Oracle Solaris Verified Boot function 1 which can be used from Oracle Solaris 11 2 onwards can be configured in XCP For details see the Fujitsu M10 SPARC M10 Systems System Operation and Administration Guide 1 Verified boot function provides security protection for SPARC M10 systems against threats that could exist in programs such as drivers and modules loaded at Oracle Solaris boot Notes and Restrictions This section descr
292. units CMUU CMUL If you forcefully turn off the power of the physical partition using the poweroff f command immediately after you powered on the physical partition you may not be able to power on off the physical partition after that In SPARC M10 4 M10 4S if the firmware version is XCP 2031 or XCP 2032 the initial value of the following OpenBoot PROM environment variable differs from the default Even if the setting is changed by using the setpparparam 8 command of the XSCF shell or the setenv command from the OpenBoot PROM prompt it will return to the original value auto boot false diag switch true fcode debug true local mac address false If the PCI device in the I O domain is deleted Idm rm io or a PCI device is added Idm add io hypervisor abort may occur when the I O domain starts If the XSCF mounted in the crossbar box panics it may be impossible to perform communication between the master XSCF and non master XSCF Problems resolved in versions prior to XCP 2050 continued Workaround There is no effective workaround How to restore Execute the poweron p command to power on the PPAR again whose power has been turned off due to an error in the crossbar box After powering on a PPAR do not execute the poweroff f command until the ok prompt is displayed How to restore If you fail to forcefully turn off the power of a PPAR power off the input power supply and then turn on the po
293. upport the SR IOV feature refer to Fujitsu M10 SPARC M10 Systems PCI Card Installation Guide Notes on OpenBoot PROM If you execute the sendbreak 8 command after the OpenBoot PROM banner appears on the domain console but before OpenBoot PROM startup is completed the following error message is output In this case the boot command becomes unable to be executed FATAL OpenBoot initialization sequence prematurely terminated In this case set the OpenBoot PROM environment variable auto boot to false at the ok prompt and execute the reset all command When OpenBoot PROM is restarted set auto boot to true and execute the boot command When you use the XSCF firmware setpparparam 8 command to set an OpenBoot PROM environment variable such as nvramrc the maximum number of characters that can be set is 254 If you want to set a string of 255 or more characters in an OpenBoot PROM environment variable such as nvramrc do so in the OpenBoot PROM or Oracle Solaris environment Note that however the maximum number of characters is 1024 The OpenBoot PROM device aliases disk and net are not created for Oracle VM Server for SPARC disks and logical domains to which no network is assigned To execute disk boot or network boot by specifying the device alias disk or net set the device aliases disk and net by using the OpenBoot PROM nvalias command From XCP 2210 onwards at the time of starting up OpenBoot PROM the following message i
294. urer are guaranteed for their connectivity and operability with XSCF Abnormalities may occur such as an XSCF firmware error or reset depending on your USB memories In such a case immediately stop using the USB memory The saved data contains information on the system If you use the USB memory consideration should be made for the management of the USB memory in which the data is saved for security reasons 191 Problems with Hardware and Workarounds There is no problem that has been confirmed as of this moment 192 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Chapter 6 Information on SPARC M10 4S Hardware This chapter describes special instructions and problems concerning the SPARC M10 4S hardware Notes and Restrictions Problems with Hardware and Workarounds Notes and Restrictions Notes on using external DVD drive USB bus power drive is not supported for external DVD drives connected via USB Notes on using USB memory Prepare a USB memory as a medium in advance if you execute the command specifying the USB memory as a destination of saving data among XSCF commands When connecting a USB memory to the USB port for XSCF directly connect it to the USB port If you connect the USB memory via the USB hub or USB extension cable it may cause an error Not all the commercially available USB memories of any manufacturer are guaranteed for their connectivity and operability with XSCF
295. urn off the power to all PPARs 2 Turn off the input power to the SPARC M10 4S chassis set on the master and standby XSCFs and then turn it on again 3 Log in to the master XSCF and execute the showhardconf 8 command to confirm that the Status of the SPARC M10 4S chassis for the standby XSCF is Normal When you execute the showhardconf 8 command it displays FRU Part Number CAXXXXX XXXX X XXXXXXx as part of the PSU information You can determine the PSU type by checking the value of CAXXXXX XXXX X in this information If the value of CAXXXXX XXXX X is CA01022 0750 M Type A PSU for SPARC64 X If the value of CAXXXXX XXXX X is CA01022 0751 M Type B PSU for SPARC64 X If multiple PSU types are mounted mixed you can determine the PSU type by checking the value of XXXXXX in the error log Code 80000000 XXXXXX0000ff0000ffxxxxxxxxxx000000 00000000 output by the showlogs error command If the value of XXXXXX is 002400 Type A PSU for SPARC64 X If the value of XXXXXX is 002401 Type B PSU for SPARC64 X After starting or resetting the XSCF execute the prtfru 8 command before executing the snapshot 8 command How to restore Execute the rebootxscf a command to reset all XSCFs 80 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 8 RTI No RTIF2 140616 004 RTIF2 140616 005 RTIF2 140804 002 RTIF2 140808 003 Problems that might occur
296. urs with the CPU mounted on the CMUL or CMUU having the faulty DDC CPU related failures may not be detected and the physical partition PPAR may hang up For a DDC failure confirm whether any of the following error logs is registered Msg Critical low voltage error Or Msg Critical high voltage error Or Msg Power subsystem failure For a SPARC M10 4S chassis with the XSCF stopped or with the input power off AC OFF even if you execute the initbb f command to forcibly disconnect Workaround XSCF gt setidap T 60 Restoring LDAP over SSL client setting Example Setting LDAP over SSL to disable XSCF gt setidapssl disable Restoring Active Directory configuration settings Example Setting Active Directory to disable XSCF gt setad disable Restoring SNMP agent settings Example Stopping SNMP agent XSCF gt setsnmp disable setsnmp Agent disabled Example Registering SNMPv3 agent user XSCF gt setsnmpusm create a SHA p XXXXXXXX e yyyyyyyy user_name Example Registering SNMPv3 agent group XSCF gt setsnmpvacm creategroup u user_name test_group Restoring SMTP service settings Example Setting port number 25 for e mail server XSCF gt setsmtp s port 25 Restoring e mail notification settings Example Disabling e mail report function XSCF gt setemailreport s enable no Immediately replace the CMUU or CMUL where the DDC failure has occurred There is no effective workaround How to re
297. visor 2 OF21 3 XSCF gt 02 01 0001 CMU BACKUP 0 02 01 0001 1 XSCF gt 6 Execute the testsb command to confirm that the FRU requiring maintenance is recognized normally XSCF gt testsb a 7 Execute the showstatus command to confirm that the FRU is operating normally after the completion of maintenance Nothing is displayed in the normal state xscf gt showstatus 8 Power on the physical partition After the logical domain starts up the logical domain time have a time lag If there is a time lag set the correct time The setting information of the CPU Activation and the CPU Activation key may be deleted when the CPU memory unit lower CMUL or the motherboard unit MBU is replaced To restore the setting information of CPU Activation and the CPU Activation key it is necessary to save the setting information of the CPU Activation and CPU Activation key beforehand using the dumpconfig 8 command and restore them with the restoreconfig 8 command To replace the CPU memory unit lower CMUL or to install the SPARC M10 4S execute the replacefru 8 or addfru 8 command and follow the maintenance menu Suppose that the system contains a crossbar box or consists of multiple SPARC M10 4S units and that the firmware is XCP 2044 or later If the CPU memory unit lower CMUL is replaced or if the SPARC M10 4S is installed without using the maintenance menu the XSCF of the replaced installed device may not start
298. was reactivated from the rebootxscf 8 command and XSCF Web and the XSCF was reset The XSCF was reset because of a failure Workaround After changing the mail server to be used to sendmail or postfix perform REMCS registration or REMCS environment setting If it is difficult to change the mail server update its firmware to XCP 2090 or later There is no effective workaround Ignore the event log Apply either of the following countermeasures Before firmware update or XSCF reactivation execute the setremotepwrmgmt c disable command to disable the power supply interlocking function Subsequently update the firmware or reactivate the XSCF After the XSCF has been activated execute the setremotepwrmgmt c enable command to enable the power supply interlocking function Disable the power supply interlocking function with the setremotepwrmgmt c disable command and then manually power on the external I O device Chapter 3 Information on Software 131 Table 3 19 Problems resolved in XCP 2090 continued SPARC M10 RTI No 1 4 4S Description RTIF2 x If one of BB 0 BB 01 XBBOX 80 131126 002 XBBOX 81 is installed or replaced the synchronous processing of the CPU core activation key in the master standby XSCF will fail Subsequently if the master and standby are switched the CPU core activation key may be lost This generates the following phenomena If the PPAR power is on The PPAR power is powered off becaus
299. wer again AC OFF ON There is no effective workaround Make a firmware update to XCP 2041 or a later version and then set the value of the OpenBoot PROM environment variable again To delete the PCI device in the I O domain delete all devices under the same route complex as that of the PCI device to be deleted which have the same xxxx of pci xxxx and then add the necessary devices again Alternatively do not assign multiple devices under the same route complex to a single I O domain There is no effective workaround How to restore If the event occurs wait for 15 minutes or longer and then use rebootxscf s to reset the master XSCF Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 25 RTI No RTIF2 130507 001 RTIF2 130515 001 RTIF2 130516 005 SPARC M10 1 4 48 x x x x x x x x x Description There is a case where a RAID volume cannot be recognized after a power failure occurred while using the hardware RAID function While the system is operating the following events may occur 1 The prtpicl command no longer responds 2 Display data such as the XCP version of prtpicl v and prtdiag v is not output as expected 3 For var adm messages the warning message PICL snmpplugin cannot fetch object value is output 4 XSCF CMDD process shutdown occurs and an XSCF is reset repeatedly such that it becomes unusable At this time system ope
300. which will be used at the next starting of the PPAR not from the XSCEF but from Oracle Solaris on the control domain or from the OpenBoot PROM Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 16 RTI No RTIF2 140212 025 RTIF2 140221 002 RTIF2 140303 002 Problems resolved in XCP 2210 continued SPARC M10 1 4 48 x x x x x x x x x Description In case of SPARC M10 4 M10 4S if all T O cease to be used on the CPU memory unit lower CMUL of the chassis which construct the physical partition PPAR or in case of SPARC M10 1 if all I O cease to be used on the motherboard unit MBU if the PPAR is powered on without replacing the failed components the starting of hypervisor is aborted Or after Oracle Solaris is started the state of Oracle VM Server for SPARC becomes suspended If all I O cease to be used any of the following must have occurred I O power supply has failed All PCI Express root complex have failed All PCI switches have failed The LDC Protocol info from PPAR PPAR ID X Domain Service Data Send Failed message is registered while logical domains are running and the WARNING ds x ds_handle_recv invalid message length received xxx bytes expected xxx message is displayed on the control domain console In some very rare cases XSCF does not start after performing AC OFF ON Workaround There is no effective workaround How to
301. with XCP 2250 and workarounds continued SPARC M10 1 4 48 x x x x x x x x Description command to start or reset the XSCF 2 Execute the snapshot 8 command 3 Execute the prtfru 8 command When you execute the switchscf 8 command XSCF master standby switching may take time As a result the following error may occur Master switch synchronization timeout If you turn off the input power of the master XSCF AC OFF and then turn it on again AC ON when the power to the physical partition PPAR is off error handling may fail due to the temporary absence of the master XSCF In addition the PPAR may remain abnormal so that you may be unable to power on the PPAR again You can determine the occurrence of this phenomenon by executing the showboards 8 command If the value of Pwr Conn Conf displayed as the master XSCF PSB status is n y n this phenomenon has occurred Example If the master XSCF is BB 00 XSCF gt showboards a PSB PPAR ID Assignment Pwr Conn Conf Test Fault 00 0 00 00 Assigned n y n Passed Normal 01 0 01 00 Assigned y y n Passed Normal Although the showstatus 8 command is executed when there are no faulty components the message No failures found in System Initialization indicating that there is no faulty component does not appear Example XSCF gt showstatus XSCF gt After the occurrence of a component failure you may fail to power off the physical partition PPAR
302. wlogs error command and check the value of the third and fourth bytes in the third field in Code Depending on this value take appropriate action by following the correct message indicated below instead of the output message If the value of the bytes is 022 Different AC input voltages of 100 V and 200 V are mixed on the PSU Check the PSU for AC input connection status If the value of the bytes is not f022 The combination of PSU types is incorrect Contact a field engineer Chapter 3 Information on Software 115 Table 3 15 RTI No RTIF2 140606 005 RTIF2 140804 001 1 x Problems resolved in XCP 2220 continued SPARC M10 Description Suppose that the testsb 8 command running for system board PSB diagnosis detects one of the errors listed below during the period between power off and power on of the SPARC M10 Systems chassis or crossbar box chassis In this case the command terminates leaving the power to the chassis on The DC DC converter DDC in the chassis is faulty Error log Msg Power on failure The circuit that monitors cooling components within the chassis is abnormal Error log Msg LLC protection circuit test error Acrossbar cable is connected to the crossbar unit XBU within the chassis in an invalid combination Error log Msg XB CABLE configuration error You can determine the occurrence of this phenomenon from the above error log and the output of the showbo
303. workaround 140418 001 DRM of Oracle VM Server for SPARC does not work 112 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 15 SPARC M10 RTI No 1 4 4S RTIF2 x xX x 140507 001 RTIF2 x 140507 002 Problems resolved in XCP 2220 continued Description In a SPARC M10 system with XCP 2043 or newer when a disk failure occurs due to its removal from a hardware RAID RAID1 or RAID1E if the state of the Open Boot PROM is transitioned due to the execution of input power off on rebooting of Oracle Solaris or the execution of the shutdown i0 command even after the restoration of the disk it is not placed in the original RAID volume but in another RAID volume Moreover the original RAID volume stays in the degraded state If the system board is deleted by dynamic reconfiguration of physical partitions Oracle Solaris on the domain may panic or Hypervisor may abort Workaround Execute any of the following procedures according to the encountered circumstances If the disk which is a part of the RAID volume fails while the system is running do not restart Oracle Solaris and replace the disk while the system is running If the disk which is a part of the RAID volume is removed while the system is running do not restart Oracle Solaris and remount the removed disk while the system is running If the disk which is a part of the RAID volume is removed while the PPAR is powe
304. xecute the following procedure 1 Replace the first FRU step 1 in the Description 2 Disable the scheduled operation XSCF gt setpowerschedule a c control disable 3 Enable the scheduled operation again XSCF gt setpowerschedule a c control enable 4 Execute step 2 and the subsequent steps in the Description How to restore If the dumpconfig 8 command is used to save the XSCF setting information execute the restoreconfig 8 command and restore the XSCF setting information If the XSCF setting information is not saved execute the setpowerschedule 8 command and reset the scheduled operation 90 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 Table 3 9 Problems resolved in XCP 2250 continued SPARC M10 RTINo 1 4 4S Description RTIF2 x x x Ifany of the following events occur and 141111 002 the XSCF is reset an incorrect error log may be registered In addition the XSCF time after the error occurrence time may be initialized to January 1 1970 XSCF panic watchdog timeout The RESET switch on the rear panel pressed The following two examples show the cases when incorrect error logs are registered and the error occurrence times are also initialized Example 1 Date Jan 01 09 05 40 JST 1970 Code 80002008 000e010000ff0000ff 018b00010000000000000000 Status Alarm Occurred Jan 01 09 04 56 276 JST 1970 FRU MBU Msg Hardware access error Diagnostic Code 00000000 0000000
305. xecuting the Idm add spconfig command a guest domain other than what had been specified may be reset Or the specified guest domain is not reset Save a configuration of the logical domain with the Idm add spconfig command If you reset the guest domain before saving it execute the Idm stop command from the control domain not from XSCF If you specify a logical domain configuration for next time you start use the Idm set config command in place of Idm add spconfig r If you use the Idm add spconfig r command to specify a logical domain configuration for next time you start and operate a guest domain with the reset 8 command of the XSCF firmware another guest domain may be reset If you execute the Idm migrate domain command with Oracle VM Server for SPARC for live migration the following problems occur with the XSCF If you execute the showdomainstatus 8 command Unknown is the status displayed for the migrated guest domain If you execute the Idm add spconfig command from the migrated control domain to save configuration information the status will be displayed normally by the showdomainstatus 8 command After live migration is executed if showdomainstatus 8 is then executed at the migration source Host stopped is the status displayed for the migrated and non existent guest domain When a physical partition PPAR is powered off by the poweroff 8 command not all of the guest domains may be shut down correctly
306. y default of Oracle Solaris Enable MPxIO manually 2 Check whether MPxIO is enabled or disabled If it is disabled enable MPxIO manually 3 MPxIO is enabled by default of Oracle Solaris So you need not to perform the setting 4 Since the internal hardware RAID is not subject to the MPxIO setting it does not require the setting Confirming the product name the vendor name and MPxlO state of the internal SAS disk or the SSD Confirm the product name the vendor name and the device path name of the internal disk or the SSD of the SPARC M10 system and see Table 3 1 to determine whether you need to perform the MPxIO setting If MPxIO is already enabled the character string scsi_vhci appears in the device path name of the internal SAS disk or the SSD When the MPxIO setting is enabled In the following example scsi_vhci appears in the device path name So the MPxIO setting is enabled format Searching for disks done AVAILABLE DISK SELECTIONS 0 c0t50000394281b5310d0 lt TOSHIBA MBF2600RC 3706 cyl 64986 alt 2 hd 27 sec 668 gt Logical device path name Vendor name Product name scesi_vhci disk g50000394281b5310 Physical device path name dev chassis FUJITSU BBEXP 500000e0e06d31bf 03N0 HDDOO disk 36 Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2250 May 2015 When the MPxIO setting is disabled In the following example scsi_vhci does not appear in the device path name So the MPxIO setting is
307. yed with the showpparstatus 8 command or the showdomainstatus 8 command the PPAR state may not be displayed correctly If the setcod 8 command is executed repeatedly on the physical partition PPAR in the PowerOn state the resources available within the process may be exhausted and codd may cause a process down Workaround There is no effective workaround While a PPAR is operating do not turn off the SPARC M10 4S Use the poweroff 8 command for example to stop a PPAR before turning it off You can avoid this by executing setcod 8 when PPAR is in the PowerOff state How to restore Restart codd Chapter 3 Information on Software 143 Table 3 21 SPARC M10 RTI No 1 4 4S RTIF2 x x x 130903 008 144 Problems resolved in XCP 2070 continued Description If any device is specified with the select command of OpenBoot PROM first but then the unselect dev command is not executed and subsequently the boot command is used to start Oracle Solaris from a network device the following defect will occur On the console of the logical domain the seek failed and Can t mount root messages are displayed and the starting of Oracle Solaris fails Then the I O device error detected message is registered in the error log and the logical domain is reset After the logical domain is reset the device specified with the select command is degraded After reset the logical domain enters either of the followi

Download Pdf Manuals

Related Search

Related Contents

The Warranty Certificate for this product can be found by locating it  取扱説明書 (4.33 MB/PDF)  documentation AJL  Blanco 440172 Use and Care Manual  Système chirurgical MERLIN™ Ré-inverseur ROLS®  Samsung RS22HDHPNSR/AA Energy Guide  White Outdoor ROTO BOSS 510 215-310-190 User's Manual  Operating Instructions - u      

Copyright © All rights reserved. Failed to retrieve file