Dear Richard,
Thank you very much for the reply,
The Base station's time reference can be configured to get the time directly
via GPS or manually using IEEE 1588 telecom profile and that is I wanted to
say "ip clock"
Clock status massages, generated by base station as follows,
=============================================
--- ENDDSP CLKSTAT:SN=7;
Kolpitty_LB_10070
+++ Kolpitty_LB_10070 2019-11-01 09:01:58
O&M #48248
%%/*19620355*/DSP CLKSTAT:SN=7;%%
RETCODE = 0 Operation succeeded.
Display System Clock Status
---------------------------
Cabinet No. = 0
Subrack No. = 0
Slot No. = 7
Current Clock Source = IP Clock
Current Clock Source State = Normal
Clock Working Mode = Manual
PLL Status = Locked
Clock Synchronization Mode = TIME
GSM Frame Bit Offset(1/8bit) = 0
GSM Frame Sync Switch = ON
(Number of results = 1)
======================================================
Blow is the Phase Difference Between 1588 And GPS,
--- ENDDSP PHASEDIFF:;
Kolpitty_LB_10070
+++ Kolpitty_LB_10070 2019-11-01 09:02:21
O&M #48250
%%/*19620405*/DSP PHASEDIFF:;%%
RETCODE = 0 Operation succeeded.
Display Phase Difference Between 1588 And GPS
---------------------------------------------
Phase Discrimination(ns)
8
(Number of results = 1)
=================================================
But after around 20 seconds " Current Clock Source State " become
unavailable
--- ENDDSP CLKSTAT:SN=7;
Kolpitty_LB_10070
+++ Kolpitty_LB_10070 2019-11-01 09:02:24
O&M #48251
%%/*19620415*/DSP CLKSTAT:SN=7;%%
RETCODE = 0 Operation succeeded.
Display System Clock Status
---------------------------
Cabinet No. = 0
Subrack No. = 0
Slot No. = 7
Current Clock Source = IP Clock
Current Clock Source State = Unavailable
Clock Working Mode = Manual
PLL Status = Holdover
Clock Synchronization Mode = TIME
GSM Frame Bit Offset(1/8bit) = 0
GSM Frame Sync Switch = ON
(Number of results = 1)
Below is the alarm generated by base station
----------------------------------------------------------------------------
----------------------------------------------------------------------------
--.
----------------------------------------------------------------------------
----------------------------------------------------------------------------
--
Name: External Clock Reference Problem
NE Type: BTS3900 LTE
Alarm Source: Kolpitty_LB_10070
MO Name: Kolpitty_LB_10070
BBU Name: Kolpitty_LB_10070
RRU Name:
eNodeB ID: 10070
User Label:
Location Information: Specific Problem=IPCLK Reference Unavailable due to
Unacceptable Quality
Additional Information: RAT_INFO=L, AFFECTED_RAT=L, DID=NULL,
Cumulative Duration(s)=200, eNodeBId=10070
Severity: Minor
Type: Hardware system
Occurrence Times: 8
Cleared By:
Cleared On (NT):
Clearance Status:
Auto Clear: Yes
Clearance Type:
Acknowledged By:
Acknowledged On (ST):
Acknowledgment Status:
First Occurred (NT): 2019/10/29 11:02:04 +05:30
Last Occurred (NT): 2019/11/01 09:02:16 +05:30
==================================================================
Do you have any suggestion for above situation ?
In the previous email I wanted to pay your attention to malformed packet
section in the packet capture
What is the meaning of malformed packet ? is that mean any hardware level
error ?
Frame 184: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on
interface 0
Ethernet II, Src: IntelCor_38:86:37 (90:e2:ba:38:86:37), Dst:
IeeeI&MS_00:00:00 (01:1b:19:00:00:00)
Precision Time Protocol (IEEE1588)
0001 .... = transportSpecific: 0x1
.... 1000 = messageId: Follow_Up Message (0x8)
.... 0010 = versionPTP: 2
messageLength: 44
subdomainNumber: 24
flags: 0x0000
correction: 0.000000 nanoseconds
ClockIdentity: 0x90e2bafffe388637
SourcePortID: 1
sequenceId: 5
control: Follow_Up Message (2)
logMessagePeriod: 0
preciseOriginTimestamp (seconds): 1572514019
preciseOriginTimestamp (nanoseconds): 998847150
[Malformed Packet: PTP]
[Expert Info (Error/Malformed): Malformed Packet (Exception occurred)]
[Malformed Packet (Exception occurred)]
[Severity level: Error]
[Group: Malformed]
Best Regards,
Ganganath
-----Original Message-----
From: Richard Cochran <richardcoch...@gmail.com>
Sent: Thursday, October 31, 2019 07:35 PM
To: gangana...@lankabell.net
Cc: linuxptp-users@lists.sourceforge.net
Subject: Re: PTP not Sync with TDD base stations
On Thu, Oct 31, 2019 at 04:18:57PM +0530, gangana...@lankabell.net wrote:
> I have successfully implement the setup with ptp4l to sync TDD base
> station and base station receives the ptp sync massages but after 2
> second it lost the ip clock which is sent by the server.
What do you mean by "ip clock"?
> [root@info ~]# tail -f /var/log/messages
>
> Oct 31 15:46:11 info phc2sys: [621627.853] enp3s0f3 sys offset -12
s2 freq +1 delay 1530
Show us the ptp4l log.
> At the same time I tried to capture the interface traffic that
> associated with the server. Screen shot as below.
Here the port with the Intel MAC address has become the MASTER. Is that
what you intended?
Thanks,
Richard
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
