01-16-2018 07:07 AM - edited 03-08-2019 01:26 PM
Hi,
I have N7k with NX-OS 6.2 (16), and divided with one admin vdc and a Prod vdc.
I have 3 external NTP server (10.92.5.58, 10.92.5.59 and 10.7.11.6).
The vdc admin is configured like this (3 ntp server; source interface: management) :
interface mgmt0
description Mgmt0-N7K-1
vrf member management
ip address 10.197.99.100/24
N7K-Admin# show ntp peers
--------------------------------------------------
Peer IP Address Serv/Peer
--------------------------------------------------
10.92.5.58 Server (configured)
10.92.5.59 Server (configured)
10.7.11.6 Server (configured)
N7K-Admin# show ntp peer-status
Total peers : 3
* - selected for sync, + - peer mode(active),
- - peer mode(passive), = - polled in client mode
remote local st poll reach delay vrf
-------------------------------------------------------------------------------
*10.92.5.58 10.197.99.100 3 64 377 0.01596 management
=10.92.5.59 10.197.99.100 3 64 377 0.01591 management
=10.7.11.6 10.197.99.100 3 64 377 0.00061 management
In this configuration, the 3 ntp servers, replace an old ntp server (10.92.1.4). So, I want that only the IP of management interface of the Admin vdc (10.197.99.100) sends ntp requests to ntp servers (10.92.5.58, 10.92.5.59 and 10.7.11.6).
The problem is that the old ntp server (10.92.1.4) receive again the ntp requests from the Loopback interface0 (10.103.17.253) of the vdc Prod.
Loopback0 interface configuration of the vdc Prod :
interface loopback0
ip address 10.103.17.253/32
ip router ospf LAN area 0.0.0.0
Show command on the vdc Prod:
N7k-Prod# show ntp peers
INFO: System clock is not controlled by NTP in this VDC
You can use "clock protocol <protocol> vdc <vdc_id>"
to change the current setting.
N7k-Prod# show ntp peer-status
INFO: System clock is not controlled by NTP in this VDC
You can use "clock protocol <protocol> vdc <vdc_id>"
to change the current setting.
N7k-Prod# show ntp source
No Source IP address configured.
N7k-Prod# show ntp status
Distribution : Disabled
Last operational state: No session
Thank you.
Solved! Go to Solution.
02-05-2018 12:07 AM
Hi Mark,
the Nexus stopped to send ntp requests from the Loopback interface0 (10.103.17.253) to the ntp server (10.92.1.4).
The IP address of the ntp server (10.92.1.4) was configured on another switch (a C6509), neighbor of the Admin VDC of the Nexus. When I passed the command
no ntp peer 10.92.1.4
on the C6509, the Nexus stopped to send ntp requests.
Regards
01-16-2018 07:26 AM
01-16-2018 09:14 AM
Already done :
N7K-Admin# show ntp source-interface
Source interface mgmt0
Thanks
01-16-2018 09:59 AM
Some output from "debug ntp info" debug on vdc Admin :
2018 Jan 16 18:23:43.200378 ntp: ntp_process_mts_msg: Opcode received: MTS_OPC_NTP_SHOW_REQ
2018 Jan 16 18:23:43.210598 ntp: ntp_doquery: sendrequest, num attempts = 30
2018 Jan 16 18:23:43.211061 ntp: fsrv_is_shared_intf_vdc(2225): srv_type: 2 vdc_id: 1
2018 Jan 16 18:23:43.211143 ntp: Sending cmi response with return_code = 0x0
2018 Jan 16 18:23:43.211181 ntp: setting global CMI msg req to NULL
2018 Jan 16 18:26:30.512358 ntp: Sending Time of day upd to standby
2018 Jan 16 18:26:30.512496 ntp: setting global CMI msg req to NULL
2018 Jan 16 18:26:30.512570 ntp: setting global CMI msg req to NULL
2018 Jan 16 18:26:30.512648 ntp: setting global CMI msg req to NULL
2018 Jan 16 18:26:30.512702 ntp: setting global CMI msg req to NULL
2018 Jan 16 18:26:30.520498 ntp: setting global CMI msg req to NULL
2018 Jan 16 18:26:30.565192 ntp: setting global CMI msg req to NULL
2018 Jan 16 18:29:30.778764 ntp: ntp_sigchld_wait_and_fetch_status: waitpid() returns with status of 28627
2018 Jan 16 18:29:30.778832 ntp: ntp_sigchld_wait_and_fetch_status: Non-ntp child exited ! Dont care !
Some output from "debug ntp info" debug on vdc Prod :
2018 Jan 16 18:37:33.263229 ntp: Processed a sdwrap msg (MTS_OPC_SYSLOG_FACILITY_OPR)
2018 Jan 16 18:37:37.070364 ntp: Sending Time of day upd to standby
2018 Jan 16 18:38:47.981899 ntp: Processed a sdwrap msg (MTS_OPC_SYSLOG_FACILITY_OPR)
2018 Jan 16 18:39:07.080467 ntp: Sending Time of day upd to standby
2018 Jan 16 18:40:37.080392 ntp: Sending Time of day upd to standby
2018 Jan 16 18:42:07.083508 ntp: Sending Time of day upd to standby
2018 Jan 16 18:42:07.083508 ntp: Sending Time of day upd to standby
2018 Jan 16 18:43:37.093499 ntp: Sending Time of day upd to standby
2018 Jan 16 18:44:22.378147 ntp: ntp_sigchld_wait_and_fetch_status: waitpid() returns with status of 30773
2018 Jan 16 18:44:22.378218 ntp: ntp_sigchld_wait_and_fetch_status: Non-ntp child exited ! Dont care !
01-17-2018 05:24 AM
01-18-2018 06:31 AM
I Mark,
I changed from
ntp source-interface mgmt0
to
ntp source ip-address
on the vdc Admin, and I passed the command
no feature ntp
on the vdc Prod, but the ntp server received again the requests from the 10.103.17.253.
Perhaps it is a bug.
I pass the incident to the network architects team, maybe they will find the problem. In this case, I will post the solution.
Thank you
01-18-2018 07:02 AM
01-18-2018 07:31 AM
The ntp is configured only on the default VDC (the vdc Admin) :
ntp server 10.7.11.6 use-vrf management
ntp server 10.92.5.58 prefer use-vrf management
ntp server 10.92.5.59 use-vrf management
ntp source 10.197.99.100
vlan1
vrf context management
ip route 0.0.0.0/0 10.197.99.254
interface mgmt0
description Mgmt0-N7K-1
vrf member management
ip address 10.197.99.100/24
02-05-2018 12:07 AM
Hi Mark,
the Nexus stopped to send ntp requests from the Loopback interface0 (10.103.17.253) to the ntp server (10.92.1.4).
The IP address of the ntp server (10.92.1.4) was configured on another switch (a C6509), neighbor of the Admin VDC of the Nexus. When I passed the command
no ntp peer 10.92.1.4
on the C6509, the Nexus stopped to send ntp requests.
Regards
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