mds9222i leap second

[piotr.szczerba]

Hello,

leap second is coming. According to https://bst.cloudapps.cisco.com/bugsearch/bug/CSCut22182 on mds9222i switches there will be a need to nondisruptively update the MDS system clock by manually resyncing to the NTP peer with the ntp sync-retry CLI command after the leap second event.

When it is need to be done? Can it wait 1 day after event, or should be done just after it happens?

Thanks

[Walter Dey]

Please have a look at

http://www.cisco.com/c/en/us/about/supplier-sustainability/leap-second.html#~ProductInformation

[piotr.szczerba]

Hello Walter,

thanks for replay.

I know that page, it pointed me to a bug on mds9222i CSCut22182

but wanted to know one thing because I am not sure.

There is said that there is a need to manually resync to the NTP peer, but how it will affect when it will be done some time later that instead right away after leap time event.

[Walter Dey]

Hi Piotr

The procedure is the following

1)The MDS system clock is not updated after receiving an NTP leap second update.

2)Nondisruptively update the MDS system clock by manually resyncing to the NTP peer with the ntp sync-retry CLI command after the leap second event.

Walter.