Sun Fire V240 Server
 
Sun Fire V210 Server
 

GCS>Sun Microsystems>Servers>Entry-Level Servers
 

./scadm date
Fri 30 May 2003 05:12:22 PM EST
However, when trying to actually set the date, you will get a usage
statement as listed below.
# ./scadm date -s 05301311
USAGE: scadm date [-s] | [[mmdd]HHMM | mmddHHMM[cc]yy][.SS]
1  <=  mm  <= 12
1  <=  dd  <= 31
1  <=  HH  <= 23
0  <=  MM  <= 59
1970 <= ccyy <= 2038
0  <=  SS  <= 59
bash-2.05# ./scadm date -s
scadm: command/option not supported
bash-2.05# ./scadm date 1230
scadm: command/option not supported
The above syntax is in fact a usage error. If the correct syntax
"scadm date 05301311" was used there would have been a message saying the
command is not supported.
Also setting the date to the current system date with the "scadm date -s"
command would also give a command not supported message.
These two unsupported options were left in place by engineering because
there are other platforms on which they are supported. There is
no way the set the ALOM date and time from Solaris with the Sun Fire
V210/V240.
Use the setdate command from the lom prompt to set the current ALOM date
and time.
When the server boots, it sets the current ALOM date and time. The server
also periodically sets the ALOM date and time while running. If you use the
setdate command while the server is starting or running, ALOM returns an
error message. The setdate command only works when the server is in
OpenBoot PROM (OBP) or powered off.
Note: Your server uses local time, but ALOM uses Universal Time (UTC). ALOM
does not accept time zone conversions or daylight time changes.
This example sets the time to September 16, 2002, at 9:45 PM (Universal
Time).
sc> setdate 091621452002
MON SEP 16 21:45:00 2002 UTC

This solution has no attachment