We have a problem:Every 10m time set on SM.
We test with ntp-server and we test to set the time.
No Chance.
THX for help
11:25:36 UT : 12/01/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
11:39:23 UT : 12/01/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
11:49:23 UT : 12/01/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
12:03:09 UT : 12/01/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
THX
as i understand it, “time set” is referring to the timing pulse being reset on the radio as it has “drifted” - it’s not related to the NTP or date and time. Check for localized interference?
Localized interference?
What do you mean?
The Problem is in 5 of our 10 networks.
Only on SM not on AP or BH.
THX for help
how are you syncing your units? gps sync? passing sync from an SM to an AP?
jay wrote: how are you syncing your units? gps sync? passing sync from an SM to an AP?
We sync our sm with cmm micro.And i test to sync the sm with an AP.
The same problem!!
System Event Log
15:46:52 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 522 System Log Cleared
15:57:38 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
16:11:25 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
16:21:25 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
16:35:12 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
16:48:58 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
16:58:58 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
17:12:44 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
17:26:31 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
17:36:31 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
17:50:18 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
18:04:05 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
18:14:05 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
18:27:51 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
18:41:38 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
18:51:38 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
19:05:25 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
19:19:12 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
19:29:12 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
19:42:59 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
19:56:44 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
20:06:44 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
20:20:31 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
20:34:18 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
20:44:18 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
20:58:05 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
21:11:52 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
21:21:52 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
21:35:38 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
21:49:25 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
21:59:25 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
22:13:12 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
22:26:59 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
22:36:59 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
22:50:45 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
23:04:32 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
23:14:32 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
23:28:18 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
23:42:05 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
23:52:05 UT : 12/02/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
00:05:52 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
00:19:39 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
00:29:39 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
00:43:26 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
00:57:12 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
01:07:12 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
01:20:59 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
01:34:45 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
01:44:45 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
01:58:32 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
02:12:19 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
02:22:19 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
02:36:05 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
02:49:52 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
02:59:52 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
03:13:39 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
03:27:26 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
03:37:26 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
03:51:12 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
04:04:58 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
04:14:58 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
04:28:44 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
04:42:31 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
04:52:31 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
05:06:18 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
05:20:05 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
05:30:05 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
05:43:51 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
05:57:38 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
06:07:38 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
06:21:25 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
06:35:12 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
06:45:12 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
06:58:59 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
07:12:44 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
07:22:44 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
07:36:31 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
07:50:18 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
08:00:18 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
08:14:05 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
08:24:05 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
08:37:52 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
08:51:38 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
09:01:38 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
09:15:25 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
09:29:12 UT : 12/03/06 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
yes, this problem appears after changing sws to hws.
we have mix hws and sws in our cluster.
I’d noticed the same a few days ago on two sectors of two different clusters. The sectors are in one frequency. The customers SM’s logs were full of ‘Time set’ errors. Some with 10 minutes interval, some with 3 minutes. It had stopped by itself.
We also had switched to hws a week ago.
This is normally a sign of GPS sync issues. Are you using CMM2’s or CMM Micro’s?
How many sat’s are seen & tracked? How long is the cable run from the CMM to the GPS antenna? What type of cable are you using?
Main cluster - ‘Time set’ events had stopped a few days ago:
6 sat’s are tracked,
CMM2,
sync cables - stp ~25 m.
Remote point (SM+AP) - ‘Time set’ events continue to come:
SM get sync from main cluster,
AP sync cable - utp 13 m.
No Out of sync events has been registered anywere.
what tech support is asking for is cable type and length between the CMM and the GPS antenna. with tracking 6 sat’s its possable you have a cable or antenna issue. If you drop a couple sat’s you could drop sync causing you’re issue. Out of the 10 CMMmicro’s i just checked none of them are tracking less then 8.
Also I have had a cluster with a CMMmicro providing sync on power port. A bad AP was degrading the sync pulse causing other AP’s and BHM’s to drop sync.
What is the link quality from the remote SM to the Main Cluster?
If you have some new interference or link issue, your sync will not pass correctly
The link efficiency is 100%.
Motorola support said it may be caused by self interference – the SM and the AP at the remote point are operating in one band (different channels). They said this problem appeared because traffic could increase and because we had switched to HWS.
But with all that no ‘Out of sync’ events is registering anywhere.
We’ve got one connectorized AP with an omni, running V8.1.4 software, with one backhaul hooked to a cmm micro. All our other sites are running V7.3.6.
We’re seeing time sets every 10 minutes in the log that didn’t exist before changing the software over (I’m assuming now it’s also now running on hws).
If the problem didn’t exist before the software upgrade and there are at least 8 sats visable and tracking no less than 4. Cable length between the CMM and GPS antenna is 10 ft.
It seems to me the problem is a software issue or a problem with hws in V8.1.4. Anyone have any insights as to how to stop this? The new software doesn’t have the hws sws radio buttons anymore to see if that’s the problem.
Any help would be appreciated as our Prizm is getting bombarded with traps from this IP.
I downgraded the software on the AP and all SM’s to 7.3.6. After 12 hours, the problem still continued. Changed the everything to software scheduling and bingo…the problem stopped. Apparently this is a glitch in hardware scheduling that is not isolated to version 8.1 alone.
Is there something else that I’m missing or is this simply the way hardware scheduling is supposed to work (I suspect not).
Finally I’ve found the cause of the problem.
The ‘Time set’ messages had been appearing on the SMs of our Remote point (SM->AP). It had stopped after we had installed a Mini-GPS2 for providing GPS syncing and timing for the modules. In normal way the SM of a remote point provides only sync signal to the AP.
The second analogous event was when something had happened with a sync cable of one AP in our main cluster. The AP was still getting the sync but it showed a wrong GPS information (time, coordinates and so on). The ‘Time set’ messages disappeared after we had replaced the sync cable connectors.
Thus the ‘Time set’ messages appear on SMs when the AP has no issue to set current time and only in HWS mode. If there is no GPS syncing try to use NTP server to provide time to an AP.