linuxptp-users

[Linuxptp-users] PTP not Sync with TDD base stations

[<gan...@la...>]

Dear Richard,

 

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.

 

* PTP server and the base station in the same L2 broadcast domain

* Neo 6M gps module connected to the server via serial interface 

* interface card is Intel 82580 Gigabit Network Connection

 

My ptp4l configurations as follows,

 

[root@info ~]# cat /etc/ptp4l.conf 

[global]

verbose               1

time_stamping  hardware         

#priority1 127

#tx_timestamp_timeout 100

#[eno2]

#

# Default Data Set

#

twoStepFlag                      1

gmCapable                         1

slaveOnly                            0

priority1                               128

priority2                              128

domainNumber                 24

#utc_offset                        37

clockClass                            7

#clockAccuracy                 0xFE

clockAccuracy                   0x20

#offsetScaledLogVariance        0xFFFF

offsetScaledLogVariance 0xD2AF

free_running                      0

freq_est_interval              1

dscp_event                        0

dscp_general                     0

dataset_comparison      ieee1588

G.8275.defaultDS.localPriority  128

#

# Port Data Set

#

logAnnounceInterval       1

logSyncInterval                 0

logMinDelayReqInterval  0

logMinPdelayReqInterval 0

announceReceiptTimeout  3

syncReceiptTimeout      0

delayAsymmetry                0

fault_reset_interval    4

neighborPropDelayThresh 20000000

masterOnly              1

G.8275.portDS.localPriority     128

#

# Run time options

#

assume_two_step         0

logging_level                      6

path_trace_enabled      0

follow_up_info                  0

hybrid_e2e                         0

inhibit_multicast_service       0

net_sync_monitor            0

tc_spanning_tree              0

tx_timestamp_timeout    1

unicast_listen          0

unicast_master_table    0

unicast_req_duration    3600

use_syslog              1

verbose                 0

summary_interval        0

kernel_leap             1

check_fup_sync          0

#

# Servo Options

#

pi_proportional_const   0.0

pi_integral_const       0.0

pi_proportional_scale   0.0

pi_proportional_exponent        -0.3

pi_proportional_norm_max        0.7

pi_integral_scale       0.0

pi_integral_exponent    0.4

pi_integral_norm_max    0.3

step_threshold          0.0

first_step_threshold    0.00002

max_frequency           0

clock_servo             pi

sanity_freq_limit       200000000

ntpshm_segment          24

#

# Transport options

#

transportSpecific       0x0

ptp_dst_mac             01:1B:19:00:00:00

p2p_dst_mac             01:80:C2:00:00:0E

udp_ttl                 1

udp6_scope              0x0E

uds_address             /var/run/ptp4l

#

# Default interface options

#

clock_type              OC

network_transport       L2

delay_mechanism         E2E

time_stamping           hardware

tsproc_mode             filter

delay_filter            moving_median

delay_filter_length     10

egressLatency           1500

ingressLatency          0

boundary_clock_jbod     0

#

# Clock description

#

productDescription      ;;

revisionData            ;;

manufacturerIdentity    00:00:00

userDescription         ;

timeSource              0xA0

 

[enp3s0f3]

transportSpecific       1

 

[root@info ~]#

 

==============================================================

 

[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

Oct 31 15:46:12 info phc2sys: [621628.853] enp3s0f3 sys offset       -11 s2
freq      -2 delay   1533

Oct 31 15:46:13 info phc2sys: [621629.853] enp3s0f3 sys offset        -8 s2
freq      -2 delay   1537

Oct 31 15:46:14 info phc2sys: [621630.853] enp3s0f3 sys offset         0 s2
freq      +4 delay   1530

Oct 31 15:46:15 info phc2sys: [621631.854] enp3s0f3 sys offset        -4 s2
freq      -0 delay   1530

Oct 31 15:46:16 info phc2sys: [621632.854] enp3s0f3 sys offset        -3 s2
freq      -1 delay   1530

 

 

==========================================================

 

 

At the same time I tried to capture the interface traffic that associated
with the server. Screen shot as below.

 



 

 

Do you have any suggestion for that ?

 

Best Regards,

Ganganath

 

 

 

 

Re: [Linuxptp-users] PTP not Sync with TDD base stations

[Richard C. <ric...@gm...>]

On Thu, Oct 31, 2019 at 04:18:57PM +0530, gan...@la... 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

Re: [Linuxptp-users] PTP not Sync with TDD base stations

[<gan...@la...>]

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 <ric...@gm...> 
Sent: Thursday, October 31, 2019 07:35 PM
To: gan...@la...
Cc: lin...@li...
Subject: Re: PTP not Sync with TDD base stations

On Thu, Oct 31, 2019 at 04:18:57PM +0530, gan...@la... 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