Notes on Maintenance of a CPU Memory Unit, Motherboard Unit, XSCF Unit, PSU Backplane, or Crossbar Backplane Unit
Notes on Maintenance of a CPU Memory Unit, Motherboard Unit, XSCF Unit, PSU Backplane, or Crossbar Backplane Unit
- Note on correcting the time (1)
After replacement of the XSCF unit and SD card, and after the system has been running for a long time, an XSCF reboot followed by PPAR startup may cause the Oracle Solaris time to shift.
This problem occurs when all of the following conditions are true:- Replacement of both the XSCF unit and SD card- System: SPARC M12-2 (single-chassis configuration) or SPARC M12-2S (single-chassis configuration).
To avoid this problem, be sure to perform the following procedure after replacing the XSCF unit and SD card.
[Workaround]- If the NTP client setting for the XSCF is disabled (default)
Execute the setdate command to set the XSCF time to the current time.
In the following example, the XSCF time is set to 2017/3/25 12:00:00.
| XSCF> setdate -s 032512002017.00 |
- The XSCF automatically reboots when the time is set.
- - If the NTP client setting for the XSCF is enabled
- 1. Execute the showlogs event command to check whether the XSCF time and NTP server time are successfully synchronized.
If multiple event logs are registered, see the latest event log.
| XSCF> showlogs event -rM Date Message Mar 25 11:45:31 JST 2017 NTP service found NTP server to synchronize. |
- When "NTP service found NTP server to synchronize." appears, the time is correctly synchronized. Then, the following steps are not necessary.
- 2. Execute the setntp command to temporarily disable the XSCF NTP client function.
| XSCF> setntp -s client -c disable |
- 3. Reboot the XSCF.
| XSCF> rebootxscf -a |
- 4. Execute the setdate command to set the XSCF time to the current time.
In the following example, the XSCF time is set to 2017/3/25 12:00:00.
| XSCF> setdate -s 032512002017.00 |
- The XSCF automatically reboots when the time is set.
- 5. Execute the setntp command to re-enable the XSCF NTP client function.
| XSCF> setntp -s client -c enable |
- 6. Reboot the XSCF.
| XSCF> rebootxscf -a |
| Note - Even if the XSCF time and NTP server time fail to synchronize and the following message appears, this workaround has been completed. XSCF> showlogs event -rM Date Message Mar 25 12:15:31 JST 2017 NTP service failed to reach appropriate NTP server. |
- Note on correcting the time (2)
Due to the problem reported in RTIF2-170224-036, the Oracle Solaris time may shift at PPAR startup.
To avoid this problem, be sure to perform the following procedure after maintenance.
| Note - Before performing the procedure in "Note on correcting the time (2)," check whether the conditions in "Note on correcting the time (1)" are met. If they are met, first perform the procedure in "Note on correcting the time (1)." |
- [Workaround]1. Execute the showdateinfo(8) command to check the times of the control domain and guest domain.
- For XCP 3050 or later
Check the times of the control domain and guest domain.
If the times are correct, the subsequent steps are unnecessary.
If the times are not correct, go to step 2.
- For XCP 3040 or earlier
Go to step 2 because it is not possible to check the times with the showdateinfo(8) command.
Example: Physical partition is PPAR#0
| XSCF> showdateinfo -p 0 PPAR-ID : 0 config_name : 10guest_config XSCF information: ----------------- XSCF Date : Aug 03 19:56:16 JST 2017 Logical domains information: ---------------------------- primary Date : Aug 03 19:56:16 JST 2017 guest 0 Date : Aug 03 19:56:16 JST 2017 guest 1 Date : Aug 03 19:56:16 JST 2017 guest 2 Date : Aug 03 19:56:16 JST 2017 XSCF> |
| Note - The times of the control domain and the guest domain are displayed by using the XSCF time zone. |
- 2. Specify false for the OpenBoot PROM environment variable auto-boot?, and execute the setpparparam(8) command to disable the autoboot function of the control domain. Also execute the setpparmode(8) command to disable startup of guest domains.
Example: Physical partition is PPAR#0
| XSCF> setpparparam -p 0 -s bootscript "setenv auto-boot? false" -y XSCF> setpparmode -p 0 -m guestboot=off |
- 3. Execute the poweron(8) command to power on the target physical partition.
| XSCF> poweron -p 0 -y |
- 4. Execute showdomainstatus -p 0 -g primary, and confirm that "OpenBoot Running" appears under Status.
- 5. Execute the console(8) command to switch to the control domain console.
| XSCF> console -p 0 -y : Omitted {0} ok |
- 6. Execute the boot -s command to start Oracle Solaris in single user mode.
| {0} ok boot -s |
- 7. Execute the date command of Oracle Solaris to set the control domain time.
Example: Setting for 12:20:00 on March 25, 2017
| primary# date 0325122017.00 |
| Note - Execute the showdate(8) command to display the XSCF time, and confirm that the control domain time of the target physical partition is the same as the XSCF time. |
- 8. Switch to multi-user mode.
| primary# exit |
- 9. For a logical domain configuration, set the correct time for guest domains.
For details on how to check for a logical domain configuration, see [How to check whether logical domain configuration/factory-default configuration].
Perform the following procedure on every guest domain to set the time.
a. Check the CONS value of the guest domain.
| primary# ldm list-domain NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME primary active -n-cv- SP 8 3968M 0.2% 0.1% 18h 37m guest bound ------ 5000 8 2G |
b. Disable the autoboot function of the guest domain.
| primary# ldm set-variable auto-boot?=false guest |
c. Start the guest domain.
| primary# ldm start-domain guest |
d. Open the guest domain console.
| primary# telnet localhost 5000 : {0} ok |
e. Execute the boot -s command to start Oracle Solaris in single user mode.
| {0} ok boot -s |
f. Execute the date command of Oracle Solaris to set the guest domain time.
Example: Setting for 12:30:00 on March 25, 2017
Example: Setting for 12:30:00 on March 25, 2017
| guest# date 0325123017.00 |
g. Switch to multi-user mode.
| guest# exit |
h. If the guest domain is an NTP client, execute the ntpq -np command, and confirm synchronization with the NTP server.
The asterisk ("*") at the beginning of a line indicates that the NTP server in the "remote" column is synchronized with the guest domain.
The asterisk ("*") at the beginning of a line indicates that the NTP server in the "remote" column is synchronized with the guest domain.
| guest# while [ 1 ]; do ntpq -np; sleep 60; done remote refid st t when poll reach delay offset jitter ============================================================================== *203.0.113.156 203.0.113.70 4 u 46 64 3 0.458 0.754 7.243 remote refid st t when poll reach delay offset jitter ============================================================================== *203.0.113.156 203.0.113.70 4 u 39 64 7 0.478 1.487 5.664 remote refid st t when poll reach delay offset jitter ============================================================================== *203.0.113.156 203.0.113.70 4 u 35 64 17 0.450 2.164 5.077 ^C guest# |
i. If necessary, re-enable the autoboot function of the guest domain.
| primary# ldm set-variable auto-boot?=true guest |
- 10. If necessary, re-enable the functions that were disabled in step 1.
For the autoboot function of the control domain, specify true for the OpenBoot PROM environment variable auto-boot?, and execute the setpparparam(8) command to re-enable the function. For startup of guest domains, execute the setpparmode(8) command to re-enable it.
Example: Physical partition is PPAR#0
| XSCF> setpparparam -p 0 -s bootscript "setenv auto-boot? true" -y XSCF> setpparmode -p 0 -m guestboot=on |
- 11. For a logical domain configuration, save logical domain configuration information.
For details on how to check for a logical domain configuration, see [How to check whether logical domain configuration/factory-default configuration].
Example: Saving logical domain configuration information under the name of "config_A"
| primary# ldm list-domain -l Omitted primary# ldm list-spconfig Omitted primary# ldm remove-spconfig config_A primary# ldm add-spconfig config_A |
[How to check whether logical domain configuration/factory-default configuration]
You can check whether the configuration is a logical domain configuration by using the showdomainconfig command.
- Logical domain configuration
If a value other than factory-default is set below, as indicated by underline, it is a logical domain configuration.
| XSCF> showdomainconfig -p 0 PPAR-ID :0 Booting config (Current) :config_A (Next) :config_A ----------------------------------------------------------------------------- Index :1 config_name :factory-default domains :1 date_created:- ----------------------------------------------------------------------------- Index :2 config_name :config_A domains :1 date_created:'2014-03-05 17:33:17' |
- factory-default configuration
If factory-default is set below, as indicated by underline, it is not a logical domain configuration but in the factory-default configuration.
| XSCF> showdomainconfig -p 0 PPAR-ID :0 Booting config (Current) :factory-default (Next) :factory-default ----------------------------------------------------------------------------- Index :1 config_name :factory-default domains :1 date_created:- |
- [SPARC M12-2S]
Suppose that the XSCF unit is replaced, or the SPARC M12-2S or crossbar box is added, with the input power turned off, without using the maintenance menu. Then, automatic synchronization of firmware versions between chassis is enabled.
After replacement or addition of components, if the "XSCF firmware update now in progress. BB#xx, please wait for XSCF firmware update complete." message is output after login to the master XSCF, the XCP firmware is in the process of being updated automatically.
Automatic synchronization of the XCP firmware versions can be confirmed by referring to 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. The same also applies to the XSCF Web operations corresponding to XSCF commands.- Turning off the input power- Executing the poweron, testsb, diagxbu, or reset command, or operating the POWER switch on the operation panel- Executing the setdate, switchscf, rebootxscf, initbb, restoreconfig, or restoredefaults command, or operating the RESET switch on the rear panel- Executing the getflashimage -d command- Executing the flashupdate -c update command
- When a component has been replaced in the following procedure, the physical partition (PPAR) cannot start.1. Execute the restoredefaults -c factory command.2. After the XSCF stops, turn off (AC OFF) the input power of the system.3. Replace the XSCF unit (XSCFU) without replacing the SD card.4. Turn on the input power (AC ON).
[Workaround]
Replace the component in the following procedure.1. Execute the restoredefaults -c factory command.2. After the XSCF stops, turn off/on (AC OFF/ON) the input power, and confirm that the XSCF has started.3. Replace the XSCF unit (XSCFU).
[How to restore]
Restore with the following procedure:1. Turn off the input power (AC OFF).2. Remount the original SD card that was mounted in the XSCF unit (XSCFU) when the restoredefaults -c factory command was executed.3. Turn on the input power (AC ON), and confirm that the XSCF has started.4. Turn off the input power (AC OFF).5. Replace the SD card.6. Turn on the input power (AC ON).
< Previous Page | Next Page >