01-01-2017 01:18 AM - edited 03-03-2019 08:25 AM
Hi,
I have a pair of Nexus C9372PX configured as vPC peers running version 7.0(3)I1(3).
NTP master is configured on both of them. they are configured with 3 NTP servers and can get time updated from them.
I am running the NTP master feature and it is working alternately. internal servers that these N9Ks are their default gateway are configured to use the SVI address as NTP server but not always succeeding to get the NTP updated.
here is the N9Ks config:
ntp server 192.118.33.64 prefer use-vrf CP
ntp server 200.189.40.8 use-vrf CP
ntp server 201.49.148.135 use-vrf CP
ntp source-interface Vlan122
ntp logging
ntp master 8
NX9K-B# sh run int vlan 122
interface Vlan122
no shutdown
vrf member CP
ip address 10.127.215.253/27
ip router eigrp 100
hsrp version 2
hsrp 122
authentication md5 key-chain HSRP
preempt
ip 10.127.215.254
NX9K-A# sh run int vlan 122
interface Vlan122
description Client-TenantA-VLAN122
no shutdown
vrf member CP
ip address 10.127.215.252/27
ip router eigrp 100
hsrp version 2
hsrp 122
authentication md5 key-chain HSRP
preempt
priority 110
ip 10.127.215.254
NX9K-A# sh ntp peer-status
Total peers : 4
* - selected for sync, + - peer mode(active),
- - peer mode(passive), = - polled in client mode
remote local st poll reach delay vrf
-------------------------------------------------------------------------------
=127.127.1.0 10.127.215.252 8 16 0 0.00000
=201.49.148.135 10.127.215.252 1 32 377 0.02028 CP
=200.189.40.8 10.127.215.252 2 32 377 0.00832 CP
*192.118.33.64 10.127.215.252 3 32 377 0.28699 CP
NX9K-B# sh ntp peer-status
Total peers : 4
* - selected for sync, + - peer mode(active),
- - peer mode(passive), = - polled in client mode
remote local st poll reach delay vrf
-------------------------------------------------------------------------------
=127.127.1.0 10.127.215.253 8 64 0 0.00000
=201.49.148.135 10.127.215.253 1 64 377 0.02107 CP
=200.189.40.8 10.127.215.253 2 64 377 0.00752 CP
*192.118.33.64 10.127.215.253 3 64 377 0.28848 CP
here is the output from the server when it success to N9K-B but fails to N9K-A:
[root@dltemp ~]# ntpdate -q 10.127.215.253
server 10.127.215.253, stratum 4, offset -0.000886, delay 0.02591
1 Jan 09:00:25 ntpdate[12683]: adjust time server 10.127.215.253 offset -0.000886 sec
[root@dltemp ~]# ntpdate -q 10.127.215.252
server 10.127.215.252, stratum 0, offset 0.000000, delay 0.00000
1 Jan 09:00:32 ntpdate[12684]: no server suitable for synchronization found
Also, after a while, the 'reach' value on the 'show ntp peer-status' command output shows '0' value:
NX9K-A# sh ntp peer-status
Total peers : 4
* - selected for sync, + - peer mode(active),
- - peer mode(passive), = - polled in client mode
remote local st poll reach delay vrf
-------------------------------------------------------------------------------
*127.127.1.0 10.127.215.252 3 64 17 0.00000
=201.49.148.135 10.127.215.252 1 64 0 2.85214 CP
=200.189.40.8 10.127.215.252 2 64 0 0.25294 CP
=192.118.33.64 10.127.215.252 3 64 0 13.9852 CP
02-13-2017 06:10 AM
if anyone has this issue as well please note that software upgrade resolved the issue.
old version - 7.0(3)I1(3)
new version - 7.0(3)I2(4)
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: