cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2629
Views
5
Helpful
3
Replies

Timezone name issue

Revolve17x
Level 1
Level 1

Hello!

I have a cisco 2921 router with 15.4(3)M7 ios software.

I made an update from ios 15.3 few days ago, and today I find out that timezone was reset.

I try to name timezone GMT+5 and router returns the error:

router(config)#clock timezone GMT+5 5 0
Apr 25 19:11:33.818: %SYS-3-TIMEZONE_INVALID: Invalid timezone name

In routers with 15.3 this problem does not exist. I do not find any bugs and release notes about timezone naming changes. Maybe someone encountered this problem too.

It's critical to set timezone name to GMT+5 because I use CDR parse software and do not have source code for change it variables.

3 Replies 3

Mark Elsen
Hall of Fame
Hall of Fame

 - Recursively check the helper  output of the 'clock ?' and 'clock timezone ?' commands , perhaps the syntax was changed.

M.



-- Let everything happen to you  
       Beauty and terror
      Just keep going    
       No feeling is final
Reiner Maria Rilke (1899)

Julio E. Moisa
VIP Alumni
VIP Alumni

Hi

As Marce mentioned  previosly, try to use clock timezone, for example:

Router(config)#clock timezone CST -5  and press enter.

Also check the space between GMT and +5

http://www.cisco.com/c/en/us/td/docs/ios/12_2/configfun/command/reference/ffun_r/frf012.html

Also use the following command to align the logs with your time:

service timestamps log datetime localtime msec

Please dont forget to rate the comment if it is useful

:-)




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Hi Julio

I mean than in ios 15.3 devices I can set Router(config)#clock timezone GMT+5 5 0 at example, where GMT+5 it's zone name nor offset. But in 15.4, when I try to set same name I'm get a syntax error.

It's not critical for network functionality, but this parameter used in third-party software we use to get a call statistics, and it was unexpected syntax change.