How to set the clock date on Sun Blade[TM] 8000 Chassis Monitoring Modules (CMM)

Asset ID:	1-71-1005364.1
Update Date:	2011-02-22
Keywords:

Solution Type Technical Instruction Sure

Solution 1005364.1 : How to set the clock date on Sun Blade[TM] 8000 Chassis Monitoring Modules (CMM)

Applies to:

Sun Blade 8000 P System - Version: Not Applicable and later [Release: N/A and later ]
Sun Blade 8000 System - Version: Not Applicable and later [Release: N/A and later]
All Platforms

Goal

Description

Document to check and adjust date/time on Sun Blade 8000 Chassis Management Modules (CMMs)

Symptoms

Incorrect date/time

Purpose/Scope

This document gives details on how to adjust the CMM date and time. This is highly recommended to ensure log files of chassis events processes are kept in sync between Chassis CMM and blade Service Processors, to ensure easy monitoring of faults, events etc

Solution

Steps to Follow

How to set date on CMM in Sun Blade[TM] 8000.

1. Confirm Active CMM time and date

-> show /CMM/clock

2a. Set CMM NTP server

-> set /CMM/clock usentpserver=enabled

-> show /CMM/clock

-> show /CMM/clients/ntp/server/1

-> set /CMM/clients/ntp/server/1 address=

-> show /CMM/clients/ntp/server/1

-> set /CMM/clients/ntp/server/2 address=

-> show /CMM/clients/ntp/server/2

2b. Set CMM local time

-> set /CMM/clock datetime=MMddHHmmYYYY

-> show /CMM/clock

MM=month ; dd=day ; HH=hour (in 24H format) ; mm=minute ; YYYY=year

NOTE: NTP is the preferred method of clock management.

3. Confirm Active CMM time and date

-> show /CMM/clock

4a. If running 1 CMM, then skip to step 5. Since the clock setting is local to the CMM, if running 2 CMM's, check which is current Active, then force a failover.

-> show /CMM/redundancy fru_name
-> set /CMM/redundancy initiate_failover_action=true

This will forcibly log out the user. Login as 'root' or an account with Administrator privilege.

4b. If using NTP method via step 2a, then this should synchronize to the NTP server upon becoming Active, with the setting already made on the Active.
Confirm the new Active CMM time and date

-> show /CMM/clock

4c. If using CMM local time method via step 2b, then the new Active CMM time and date needs to be set again:

-> set /CMM/clock datetime=MMddHHmmYYYY
-> show /CMM/clock

MM=month ; dd=day ; HH=hour (in 24H format) ; mm=minute ; YYYY=year

5. Login to 'sunservice' on each CMM directly to commit the hardware clock changes. Note, you should not use the CMM HA address since each CMM maintains its own local hardware clock, and both need to be set independently.

5a. Set CMM0 Linux time and date:

# ssh -l sunservice
[(flash)root@SUNCMMXXXXXXXXXXXX:~]# /usr/local/bin/hwclock --systohc
[(flash)root@SUNCMMXXXXXXXXXXXX:~]# date
[(flash)root@SUNCMMXXXXXXXXXXXX:~]# exit

5b. Set CMM1 Linux time and date (using the same procedure as in 5a)

# ssh -l sunservice

etc

6. Verify the changes survive across CMM resets:

6a. Login as 'root' or an account with Administrator privilege to Active CMM.

# ssh -l root 

-> show /CMM/clock
-> reset /CMM

NOTE: If running 2 CMM's, this will force a failover.

6b. Wait 2 minutes for this CMM to reset and boot.

6c. If running 1 CMM, then login to the CMM and verify the clock is current time:

-> show /CMM/clock

This should complete the process for a 1 CMM system.

6d. If running 2 CMM's, then login to the current Active CMM after the failover from step 6a. Reset the current Active CMM:

-> show /CMM/clock
-> reset /CMM

This will again force a failover. Now login to the new Active CMM that was originally reset in step 6a. and verify the time is still set current:

-> show /CMM/clock

Wait 2 minutes for the redundant CMM to reset and boot. Verify the redundant CMM is online:

-> show /CMM/redundancy status

Properties:
       status = Active
Commands:
       show

Wait until this status shows as "Active" and not "Stand-alone".

Force a failover to verify the local clock of the 2nd CMM.

-> set /CMM/redundancy initiate_failover_action=true

This will force a failover and logout the Active CMM. Now login to the new Active CMM that was reset at the beginning of this step 6d. and verify the time is still set current:

-> show /CMM/clock

This completes the process for 2 CMM systems.

Internal Comments
If the CMM is running ILOM 2.0.1.1 or later, then step 5 is not necessary.
Step 5 is only necessary if the CMM is running ILOM 1.1.5 or earlier, due to CR 6530888. Step 6 may not be necessary in either case, but is good practice.

This document contains normalized content and is managed by the the Domain Lead
(s) of the respective domains. To notify content owners of a knowledge gap
contained in this document, and/or prior to updating this document, please
contact the domain engineers that are managing this document via the “Document
Feedback” alias(es) listed below:

Domain Lead: [email protected]
Feedback Alias: [email protected]
normalized, CMM, date, NTP, clock, sb8000, 8000, blade
Previously Published As
89613

Change History
Date: 2008-09-29
User Name: 79977
Action: Updated
Comment: Bought document under normalization project

Attachments

This solution has no attachment