We have a setup where 2 DC's receive their clock from a GPS clock. Then our 2 core switches (C3650 running on 15.0.(2) ) receive their clock from these DC's. It all seems to work fine. However, when I turn of the ntp service on both DC's our two core routers still remain synchronized. That is, when a look at the ntp association both peers keep their original state (i.e. sys.peer and candidate). Furthermore the ntp status also indicates that the clock is synchronized with the same stratum as before (referencing to on of the DC's). When I turn on debugging i do receive a ntp_receive message indicating that:
NTP Core(DEBUG): ntp_receive: peer is 0x00000000, next action is 3
I assume that this means that there's a problem with the peer seeing that normally the address is filled in and the next action is.
My question here. How come the two core switches still think they are synchronized? Does it take more time for the update (although i waited until they missed several poll intervals).
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...