ntp:time reset & ntp:frequency error - Post NX-OS upgrade

[Zubair.Sayed_2]

Hi All.

I recently upgraded 2 of my MDS 9222i SAN switches from OS to NX-OS.

All working fine on both switches, except that switch 2 comes up with NTP issues in the log.

Removed the NTP config and reapplied and it seemed to have stopped for a brief period.

They back now. Can anybody assist?

2011 Jan  4 04:36:26 SAN2 ntpd[2852]: ntp:frequency error 512 PPM exceeds tolerance 500 PPM

2011 Jan  4 04:51:41 SAN2 ntpd[2852]: ntp:time reset +3.090399 s

2011 Jan  4 04:51:41 SAN2 ntpd[2852]: ntp:frequency error 512 PPM exceeds tolerance 500 PPM

2011 Jan  4 05:07:09 SAN2 ntpd[2852]: ntp:time reset +3.186555 s

2011 Jan  4 05:07:09 SAN2 ntpd[2852]: ntp:frequency error 512 PPM exceeds tolerance 500 PPM

2011 Jan  4 05:22:22 SAN2 ntpd[2852]: ntp:time reset +3.131617 s

2011 Jan  4 05:22:22 SAN2 ntpd[2852]: ntp:frequency error 512 PPM exceeds tolerance 500 PPM

2011 Jan  4 05:37:36 SAN2 ntpd[2852]: ntp:time reset +3.145349 s

2011 Jan  4 05:37:36 SAN2 ntpd[2852]: ntp:frequency error 512 PPM exceeds tolerance 500 PPM

2011 Jan  4 05:52:52 SAN2 ntpd[2852]: ntp:time reset +3.110993 s

2011 Jan  4 05:52:52 SAN2 ntpd[2852]: ntp:frequency error 512 PPM exceeds tolerance 500 PPM

2011 Jan  4 06:08:07 SAN2 ntpd[2852]: ntp:time reset +3.107459 s

2011 Jan  4 06:08:07 SAN2 ntpd[2852]: ntp:frequency error 512 PPM exceeds tolerance 500 PPM

Thanks

ZS

[Michael Brown]

I see 2 options..

The message is advising that the NTP time recieved is > 500 parts per million, or about over 43 seconds apart from the local clock time.

Best would be to manually sync the clock once (Clock set), and then it should synchronies smoothly, as long as NTP server connectivity is
maintained.

You coulalso try the command ntp sync-retry which should stop and restart the NTP daemon on the MDS.

HTH,

  Mike

[Zubair.Sayed_2]

Once again thanks Mike.

I have issued the 'ntp sync-retry', cleared the logfile and will monitor.

I have however also tried to issue the 'clock set' command and receive the below error. Must I remove ntp server information and then issue command?

Error:

FSSAN2(config)# clock set 08:35:00 07 January 2011

Clock set:: NTP server/peer configured. Can't set the clock.

To set the clock, please remove the ntp server/peer config.

Thanks

ZS

[Zubair.Sayed_2]

Hi Mike,

It seems the 'ntp sync-retry' worked on 2 of my other switches.

However on the one switch it does not see to work or re-sync. I have removed the ntp server information, ran 'clock set' manually and reapplied ntp server info.

So now only on 1 switch I still keep seeing this:

2011 Jan  7 09:42:37 FSSAN2 ntpd[24241]: ntp:time reset +3.097231 s

2011 Jan  7 09:42:37 FSSAN2 ntpd[24241]: ntp:frequency error 512 PPM exceeds tolerance 500 PPM

2011 Jan  7 09:43:25 FSSAN2 ntpd[24241]: ntp:frequency error 512 PPM exceeds tolerance 500 PPM

Regards

ZS

[Michael Brown]

What software leve is this MDS on?  Is it the same as the MDS that the re-sync command worked on?

Makes sense that the system would not let you manually set the clock while it was configured to use NTP.

Are all 3 pointed to the same NTP server?

-Mike

[Zubair.Sayed_2]

Mike.

Do you mean what software logging level the switch is on?

Yes, all 4 switches are the same. 2 switches are hosted at one Data Center and 2 switches at the other.

1. at DC 1 the primary switch works fine post upgrade, no ntp issues or messages, switch 2 however does not.
2. at DC 2 both switches have the same ntp messages post upgrade to NX-OS.
3. They are all pointed to the same NTP servers.

I dont find much information on the web about this and these messages are clogging our syslog messages.

Cheers

Z