Start a Conversation

Unsolved

This post is more than 5 years old

G

4292

March 14th, 2018 19:00

Set local date in 6224 clock detail

I have sntp configured on my 6224 with EDT time zone (UTC -4). It seems like the date in clock detail is UTC date while time is EDT time. How do I set date to correspond with time zone?

5 Practitioner

 • 

274.2K Posts

March 15th, 2018 06:00

There have been some improvements to SNTP throughout the firmware rereleases. If the switch is on older firmware, you may want to consider scheduling an upgrade window.

http://dell.to/2tQQabW

 

During configuration did you set the zone to EDT? Can you share with us your configuration? The output from the command # show clock details? 

6224 timezone.png

18 Posts

March 15th, 2018 17:00

The date in output of show clock detail seems to be correct but not so in web Openmanage Switch Administrator.

console#show clock detail 

20:38:50 EDT(UTC-4:00) Mar 15 2018 
Time source is SNTP

 Time zone:
 Acronym is EDT
 Offset is UTC-4:00

 Summertime:
 Summer-time is disabled

console#show switch

    Management Standby   Preconfig     Plugged-in    Switch        Code  
SW  Status     Status    Model ID      Model ID      Status        Version
--- ---------- --------- ------------- ------------- ------------- -----------
1   Mgmt Sw              PCT6224       PCT6224       OK            3.3.16.1   

Capture.PNG

5 Practitioner

 • 

274.2K Posts

March 16th, 2018 07:00

That is an interesting discrepancy. Could you please try updating the firmware on the switch, then check and see if the GUI has been corrected. 

http://dell.to/2FFxmln

Keep us posted

18 Posts

March 16th, 2018 15:00

I considered upgrading to Version 3.3.17.1, A42 but the risk seems to be greater than any potential benefits. Only one fix documented. The upgrade is on my to-do list but remains a low priority.

Fixes:
CS2987546/FIELD-2366 - 3.3.16.1/WebUI Error-Default VLAN cannot be made static.

Enhancements:
None
 

5 Practitioner

 • 

274.2K Posts

March 22nd, 2018 10:00

Updating the firmware is just part of the process of troubleshooting. The firmware affects both the CLI and the GUI, and could correct this discrepancy between the CLI and GUI. another approach would be to boot to the secondary image, to see if the behavior is the same in that version. Keep us posted on your findings. 

No Events found!

Top