You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[NTP Server BD SVI][d25] | CSCwp92030 | :white_check_mark: | :no_entry_sign:
197
+
196
198
197
199
[d1]: #ep-announce-compatibility
198
200
[d2]: #eventmgr-db-size-defect-susceptibility
@@ -222,6 +224,7 @@ Items | Defect | This Script
222
224
[d26]: #stale-pconsra-object
223
225
[d27]: #isis-dteps-byte-size
224
226
[d28]: #policydist-configpushshardcont-crash
227
+
[d29]: #ntp-server-bd-svi
225
228
226
229
227
230
## General Check Details
@@ -2648,6 +2651,15 @@ Due to [CSCwp95515][59], upgrading to an affected version while having any `conf
2648
2651
If any instances of `configpushShardCont` are flagged by this script, Cisco TAC must be contacted to identify and resolve the underlying issue before performing the upgrade.
2649
2652
2650
2653
2654
+
#### NTP Server BD SVI
2655
+
2656
+
In ACI, Leaf Switches can be configured as NTP servers, allowing Endpoints in ACI to act as NTP clients and sync their datetime with the Fabric. The Leaf switch uses it's BD SVI IP address to send NTP traffic.
2657
+
2658
+
Due to [CSCwp92030][62], after a policy upgrade NTP can stop working between Endpoint clients and NTP Server (ACI Leaf), Client reach the NTP server by it's BD SVI IP address, but the server replies on a Loopback address.
2659
+
2660
+
If you see the check alerting about Datetime Policies, apply the workaround to prevent NTP issues post-upgrade.
0 commit comments