I've tried everything I can think of to get the time and date set on my 6248. I've tried using public, stratum 2 NTP servers; I've setup my own unicast NTP server that is a DC in a domain; I've tried turning on broadcasting with UDP relay; I've tried saving run to start and rebooting the system; I've got the latest firmware installed. Nothing works. Can anyone help? Here's my "show sntp configuration"
Polling interval: 128 seconds MD5 Authentication keys: Authentication is not required for synchronization. Trusted keys: No trusted keys. Unicast clients: Enable
Here's an update: I connected to Dell chat support and they found the source of the problem--Management ACL's block SNTP traffic. You have to have a explicit permit rule in the priority list. Also, the DOS attack suppression still has to be disabled; this was not addressed in 2.2.0.3. Hopefully they'll get to that because I'd like to use it. I may try to zero in on which part of DOS suppression is causing the problem.
Found the cause of the problem. SNTP will not sync up if you have DOS attack protection on. This is apparently a bug with the latest version of the firmware. Hopefully Dell will address it in the next patch.
Unfortunately, I am still stuck. I updated to FW 2.2.0.3 last night, and now SNTP is hopelessly broken. DOS attack protection is entirely disabled, so that is not a factor. I actually started from scratch with the firmware, manually resetting all of the various switch configuration parameters, so I know it's not a matter of bringing in wonky config information from the old firmware revision (1.0.0.27). Dell definitely broke something. I'm going to take it up with support and see what sort of walls I run into.
Huh. I just performed the 2.2.0.3 myself and now SNTP has stopped working again. I suppose I'll do another packet sniff and look at the NTP frame coming from our Internet gateway. If it shows success (like it did when it was working) I'll know that it's the switch. Keep me posted if you hear anything from Dell.
Excellent! Thanks for the update! I haven't had a chance to contact them myself... Exchange 2007 migration ate my week. I'll dig into that later today, though. Can't push syslog data with bad time on the switches... throws off my reporting mojo.
Worked great! Don't think I'd have thought to check that, frankly. I appreciate your posting the results. I was able to get things all smooth and shiny over the weekend. Now if I could only warm up the -25 wind chills outside...
And here's what I discovered this morning regarding Denial of Service: I've narrowed it down to "Denial of Service L4 port". When this is enabled the switch will not allow a successful time update to occur.
BrandonSchultz
13 Posts
10908
1
Posted December 13th, 2008 10:00
Here's an update: I connected to Dell chat support and they found the source of the problem--Management ACL's block SNTP traffic. You have to have a explicit permit rule in the priority list. Also, the DOS attack suppression still has to be disabled; this was not addressed in 2.2.0.3. Hopefully they'll get to that because I'd like to use it. I may try to zero in on which part of DOS suppression is causing the problem.
B. Schultz