|
Home > Archive > Data Storage > February 2005 > Why Can't NetApp Keep Time
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Why Can't NetApp Keep Time
|
|
| danorton@gmail.com 2005-02-04, 5:46 pm |
| The company I work for has NetApp file servers and according to our IT
people, they can't keep proper time using NTP.
Why not?
Consequently, builds across network drives are a nuisance. Apparently
the clock drifts fast and our ops set the time slow to compensate. We
don't have to have the correct time, but we do need for all systems to
have the *same* time. As the NetApp server can't do NTP service, we
can't it to be the common time.
Thanks.
--
Daniel Norton
| |
| David Magda 2005-02-04, 5:46 pm |
| danorton@gmail.com writes:
> The company I work for has NetApp file servers and according to our
> IT people, they can't keep proper time using NTP.
>
> Why not?
If you're having trouble with NTP why are you asking in a storage
newsgroup? Try asking in the NTP group:
comp.protocols.time.ntp
--
David Magda <dmagda at ee.ryerson.ca>, http://www.magda.ca/
Because the innovator has for enemies all those who have done well under
the old conditions, and lukewarm defenders in those who may do well
under the new. -- Niccolo Machiavelli, _The Prince_, Chapter VI
| |
| Andrei Ivanov 2005-02-04, 8:45 pm |
| danorton@gmail.com wrote:
> The company I work for has NetApp file servers and according to our IT
> people, they can't keep proper time using NTP.
On my NetApp filer (ONTAP 6.1.2R3) there are these three lines
in the /etc/rc file:
timezone US/Pacific
options timed.servers 1.2.3.4
options timed.enable on
The 'date' command shows exactly the same time as on all other servers
synchronized from the same source.
--
andrei
| |
| Faeandar 2005-02-05, 2:45 am |
| On 4 Feb 2005 12:32:57 -0800, danorton@gmail.com wrote:
>The company I work for has NetApp file servers and according to our IT
>people, they can't keep proper time using NTP.
>
>Why not?
>
>Consequently, builds across network drives are a nuisance. Apparently
>the clock drifts fast and our ops set the time slow to compensate. We
>don't have to have the correct time, but we do need for all systems to
>have the *same* time. As the NetApp server can't do NTP service, we
>can't it to be the common time.
>
>Thanks.
I can empathize with your problem, in fact I have the same one.
Unlike Andrei I don't keep the info in the rc file anymore but rather
the options. The process should still be the same but I wonder where
you have set the info? Maybe it's a problem with their registry.
And David, the reason he would post it here is because it's not a
problem with the protocol, but rather the storage that is implementing
it.
~F
| |
| Yura Pismerov 2005-02-06, 2:45 am |
|
danorton@gmail.com wrote:
> The company I work for has NetApp file servers and according to our IT
> people, they can't keep proper time using NTP.
>
> Why not?
As somebody already pointed out, NetApp uses timed protocol instead, so it won't talk to an NTP server.
So ask your "IT people" to setup a timed server somewhere on the network.
>
> Consequently, builds across network drives are a nuisance. Apparently
> the clock drifts fast and our ops set the time slow to compensate. We
> don't have to have the correct time, but we do need for all systems to
> have the *same* time. As the NetApp server can't do NTP service, we
> can't it to be the common time.
>
> Thanks.
>
> --
> Daniel Norton
>
| |
|
|
Netapp like web pages. 
Filer->Set Date/Time
Set Timezone
Set Misc.
Or as mentioned above (and how we did it) edit the file by hand.
Our time is always on the money. If it were not our users would complain.
--
Wolf
----------------------------------------------------------------
Please post all responses to UseNet. All email cheerfully and automagically
routed to Dave Null
| |
|
| "Yura Pismerov" <ypismerov@tucows.com> wrote in message
news:cu3vej$1l5$1@yura.org...
>
>
> danorton@gmail.com wrote:
>
> As somebody already pointed out, NetApp uses timed protocol instead, so it
won't talk to an NTP server.
> So ask your "IT people" to setup a timed server somewhere on the network.
You can configure it to use ntp. See my previous post.
--
Wolf
----------------------------------------------------------------
Please post all responses to UseNet. All email cheerfully and automagically
routed to Dave Null
| |
| Faeandar 2005-02-07, 5:45 pm |
| On Sun, 06 Feb 2005 15:25:33 GMT, "Wolf" <wolfdotcom@hotmail.com>
wrote:
>
>Netapp like web pages.
>
>Filer->Set Date/Time
> Set Timezone
> Set Misc.
>
>Or as mentioned above (and how we did it) edit the file by hand.
>Our time is always on the money. If it were not our users would complain.
FilerView?! Bah, I forget it even exists. Besides, all that does is
edit the options directive which in turn edits the registry. Any more
I think the entry in the rc file does the same thing as well.
I see entries in the log file all the time about time being off by X
seconds. It keeps correcting them but they keep happening. And
usually it's by 3.x seconds. Odd, now that I write that every one
that I can recall was 3.x seconds. Need to look into that one...
~F
| |
|
| "Faeandar" <mr_castalot@yahoo.com> wrote in message
news:g0qf0158rr3pmk6t03na2abkd707kmd1d3@
4ax.com...
> On Sun, 06 Feb 2005 15:25:33 GMT, "Wolf" <wolfdotcom@hotmail.com>
> wrote:
>
>
> FilerView?! Bah, I forget it even exists. Besides, all that does is
> edit the options directive which in turn edits the registry. Any more
> I think the entry in the rc file does the same thing as well.
>
> I see entries in the log file all the time about time being off by X
> seconds. It keeps correcting them but they keep happening. And
> usually it's by 3.x seconds. Odd, now that I write that every one
> that I can recall was 3.x seconds. Need to look into that one...
I set it up that way as part of the installation process and have had zero
problems. I have not bothered looking at how many seconds it may go
off since it uses our ntp servers to keep time and it's always on the money.
Another avenue to find out more is to call Netapp support for help-they
are usually very helpful.
--
Wolf
----------------------------------------------------------------
Please post all responses to UseNet. All email cheerfully and automagically
routed to Dave Null
|
|
|
|
|