cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1845
Views
0
Helpful
2
Replies

ASR1001-x clock timezone command doesn't seem to work

mmccallebaut
Level 1
Level 1

Our client has 2 ASR1001-x routers with IOS-XE sr1001x-universalk9.03.13.02.S.154-3.S2-ext.SPA.bin.

I can configure the clock summer-time:

clock summer-time BE recurring last Sun Mar 2:00 last Sun Oct 3:00

However I can't configure the clock timezone. When I enter the configuration rule "clock timezone BE 1 0" the router doesn't complain but afterwards this configuration rule doesn't appear in the configuration and the clock isn't adapted:

RT00BDCE1EX1#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
RT00BDCE1EX1(config)#clock timezone BE 1 0
RT00BDCE1EX1(config)#exit
RT00BDCE1EX1#sho run | inc clock
clock summer-time BE recurring last Sun Mar 2:00 last Sun Oct 3:00
RT00BDCE1EX1#sho clo
11:58:32.032 BE Thu Apr 23 2015
RT00BDCE1EX1#

 

NTP is configured and is working properly:

RT00BDCE1EX1#sho ntp asso

  address         ref clock       st   when   poll reach  delay  offset   disp
*~10.136.13.217   10.136.2.83      3     39   1024   377  3.991 2753.49  1.116
+~10.136.13.125   10.136.2.83      3    337   1024   377  3.990 2748.64  1.093
 * sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
RT00BDCE1EX1#

 

Is this a bug ? Is there a new way to configure the right timezone? Thanks in advance.

Best regards

Mike

 

 

2 Replies 2

mmccallebaut
Level 1
Level 1

After a long search I found a configuration that worked:

clock timezone UTC 1 0
clock summer-time UTC+2 recurring last Sun Mar 2:00 last Sun Oct 3:00

RT00BDCE1EX1#sho clo
09:13:47.967 UTC+2 Wed Apr 29 2015


The only issue is that we can't show the timezone in the loggings or the debuggings because in winter time it will be UTC which is not correct (must be UTC+1).

mmccallebaut
Level 1
Level 1

After a long search I found a configuration that worked:

clock timezone UTC 1 0
clock summer-time UTC+2 recurring last Sun Mar 2:00 last Sun Oct 3:00

RT00BDCE1EX1#sho clo
09:13:47.967 UTC+2 Wed Apr 29 2015


The only issue is that we can't show the timezone in the loggings or the debuggings because in winter time it will be UTC which is not correct (must be UTC+1).

Review Cisco Networking for a $25 gift card