Problem with NTS-200 (TrueTime)

[news]

I was wondering if anyone using same might be experiencing problems.
The nature of my problem is that the IP stack apparently craps out at
random times for no apparent reason. It doesn't respond to pings, ntp
types of packets, nothing. The only fix is to power cycle the unit.

The switch to which it is a attached (a Cisco Catalyst 6500) knows
about the MAC address in it's arp tables, but even it can't ping the
NTS. Initially, I had been running the interface at 100, but it would
crap out almost weekly. Now I run at 10, and it craps out about every
other week or so. There are about 500 NTP clients using this box
presently; they are a mix of NT servers/workstations, and a bunch of
Solaris boxen.

I called TrueTime, and they said there is a firmware upgrade, but that
we would need to send the unit back to them. Unfortunately, that will
not work for us. I was told there was an NT application I might be
able to use to upgrade the firmware ourselves, but that it wasn't
ready to go yet.

Short story long, I just mainly wanted to know if any other NTS-200
users are experiencing similar problems?

thanks.

[Terje Mathisen]

news wrote:
[snipped sad story]

> Short story long, I just mainly wanted to know if any other NTS-200
> users are experiencing similar problems?

No, I have had an NTS-200 for as long as they have been around, and I
have told the unix group that all systems can use this server directly.

I can't get 'ntpdc -c monlist' to work against it currently, so I can't
tell you exactly how many clients it has, but it should be quite a few.

It is probably sitting on a 10 Mhz port.

Terje
--
- <Terje.M...@hda.hydro.com>
Using self-discipline, see http://www.eiffel.com/discipline
"almost all programming can be viewed as an exercise in caching"

[Jerome Limozin]

> Short story long, I just mainly wanted to know if any other NTS-200
> users are experiencing similar problems?
>

I had same problem with a NTS-100 once. I had to power cycle it to
restore ntp service.
the difference is that I only have 3 unix boxes connecting to the NTS
unit (these unix boxes distribute time to many other servers). Maybe
that makes a difference??

Jerome

[Gerik]

I have one of my NTS100i face the same problem last month.
It doesn't response to ping. I get my network guys to verify our switch
etc,
all other than our NTS100i ntp port were working fine.
Finally reboot solved the problem.
This thing happened once in it's about one year life with me.
I can't afford to have this happen again since my voip billing system
really
depend on this.
Nice to hear any update from you and others on this matter.

tq,
--fg