02-26-2019 10:51 PM
Hi All,
I have deployed N9k with multiple VRFs and NTP source SVI located at MGT vrf.
How could I configure NTP in this environment. I have mentioned configs done
SLDC1-CORE-SW02(config)#clock timezone IST 5 30
SLDC1-CORE-SW02(config)# feature ntp
NTP feature is already enabled
SLDC1-CORE-SW02(config)# ntp logging
SLDC1-CORE-SW02(config)# sh ntp status
Distribution : Disabled
Last operational state: No session
SLDC1-CORE-SW02(config)#
SLDC1-CORE-SW02(config)# ntp server 10.200.233.101 prefer
SLDC1-CORE-SW02(config)# ntp server 10.200.233.101 use-vrf mgmt prefer
SLDC1-CORE-SW02(config)# ntp server 10.200.233.102 use-vrf mgmt
SLDC1-CORE-SW02(config)# sh ntp status
Distribution : Disabled
Last operational state: No session
SLDC1-CORE-SW02(config)#
SLDC1-CORE-SW02(config)# sh ntp status
Distribution : Disabled
Last operational state: No session
How ever i can see that devices are not synchronized with NTP
Please assist us to configure NTP if have done something wrong
Regards,
Dilk
02-27-2019 12:51 AM
what is your vrf mgmt IP addres ? do you have reachability for these IP address 10.200.233.101 and 10.200.233.102
can you post ping 10.200.233.101 and 10.200.233.101 using src vrf mgmt
here is example guide for ntp for nexus:
02-28-2019 12:05 AM - last edited on 03-09-2022 11:24 PM by smallbusiness
Hi BB,
I have connectivity to NTP servers form Mgmt IP address. There is connectivity to server from mgmt VRF too.
Meantime I got some debug logs related to NTP and please find the attachment, it shows that device is synchronized with NTP peers.
executed "clock protocol ntp vdc 1 " too.
and please find the following outputs , but I cannot see NTP status in "show ntp status" output.
What is ntp distribution : Disabled ? and Last operation says No session
SLDC1-CORE-SW02# sh ntp status
Distribution : Disabled
Last operational state: No session
SLDC1-CORE-SW02# sh ntp peers
--------------------------------------------------
Peer IP Address Serv/Peer
--------------------------------------------------
10.200.233.101 Server (configured)
10.200.233.102 Server (configured)
SLDC1-CORE-SW02#
SLDC1-CORE-SW02# sh ntp peer-status
Total peers : 2
* - selected for sync, + - peer mode(active),
- - peer mode(passive), = - polled in client mode
remote local st poll reach delay vrf
-----------------------------------------------------------------------------------------------------------------------
*10.200.233.101 10.200.233.252 6 64 377 0.00063Mgmt
=10.200.233.102 10.200.233.252 6 64 377 0.00052Mgmt
SLDC1-CORE-SW02#
SLDC1-CORE-SW02# sh ntp session status
Last Action Time Stamp : None
Last Action : None
Last Action Result : None
Last Action Failure Reason : none
SLDC1-CORE-SW02#
SLDC1-CORE-SW02# sh ntp statistics peer ipaddr 10.200.233.101
remote host: 10.200.233.101
local interface: 10.200.233.252
time last received: 34s
time until next send: 27s
reachability change: 4073s
packets sent: 244
packets received: 244
bad authentication: 0
bogus origin: 0
duplicate: 0
bad dispersion: 0
bad reference time: 0
candidate order: 6
SLDC1-CORE-SW02#
SLDC1-CORE-SW02#
SLDC1-CORE-SW02# sh ntp statistics peer ipaddr 10.200.233.102
remote host: 10.200.233.102
local interface: 10.200.233.252
time last received: 57s
time until next send: 5s
reachability change: 4077s
packets sent: 242
packets received: 242
bad authentication: 0
bogus origin: 0
duplicate: 0
bad dispersion: 0
bad reference time: 0
candidate order: 4
SLDC1-CORE-SW02#
Regards,
Dilk
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide