Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NEAX2400 IPX clock

Status
Not open for further replies.

PREPAPBX

Programmer
Jul 10, 2009
17
PR
Hello. We used to have a NEC Server (MA4000)to synchronize the clocks on all of our NEAX2400 IPX's. This server is no longer working after a 13KV electric cable fell on a cooper cable going into the PBX room.

Now, without the MA4000, there is a NEAX2400 IPX switch that resets its clock around 4:00 a.m. every day. How do I resolve this? Thanks.
 
The MA-4000 actually reset CMD ATIM, it is not like a network clock where the PBX gets it's time from a server. Like Ozzie suggested, you must go into each individual system and set the time with CMD ATIM, unless you have a fusion network. With fusion you can synch all of the systems to the main or central node in the system.
 
That's the problem, every morning we have to go into CMD ATIM to set the clock because it resets itself every day around 4:00 a.m. We don't have a fusion network. Thanks.
 
If that has been happening since installation or since an upgrade, then it might be a software bug fixed in subsequent software levels. I have not seen this issue.
 
Everything worked fine before the MA4000 server was installed. After this server was installed by NEC, the clock in all PBX's were synched and everything was perfect.

The problem started happening, in only one of the PBX's, after the server stopped working. No software upgrade has been done for many years. Thanks.
 
Can you provide the software level of the PBX? CMD DISS, main memory. I can do some research on it.
 
Hello. Here's the output for CMD DISS:

Type Version Issue Date
Main Memory 17 03.46.001 2005/01/05
Boot ROM H 2004/04/20
MAT 17 02.25 2004/11/05
TCP/IP 7 02.18 2004/11/15
PHDP 4 01.00 2004/3/14

Thanks.
 
I would try busying out the IO card overnight to see if the time stays correct. Something else may be logging in and resetting the time. It would be interesting to disconnect all comms and see if that stops the clock from changing, it could be something as silly as a script on another machine that has the timezone set wrong. If there is an Ethernet connection to the machine, try running a wireshark trace on it overnight. I can't think of any command that will set the conditions you are experiencing (not conclusive).
 
Command ANTPL will synch the system to an outside clock source. Maybe there is something programmed incorrectly in that cmd.
 
I found the command and deleted the outside source IP. I'll let you know tomorrow if this did the trick. Thanks.
 
EXC300, you the MAN! Problem solved. Thank you very much.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top