Hello @Muhammad-ly ,
they are two different type of errors that are not likely related to each other.
The first error complains of a parity error in a clock and it might be hardware related.
The second error is caused by the fact that a specific IP prefix 192.168.120.1/32 ( this is my guess) is advertised in LDP with an MPLS label binding by two different LDP peers of the local node 10.1.1.14 ( the :0 means node level MPLS label space ) but an MPLS LDP binding for the prefix already exist anf it is addvertised by LDP peer 10.6.1.210 ( again the final :0 just indicates node level label space).
So this second error is the result of an error in configuration . Connect to the two other PE nodes and verify that there is a duplicated address configured on both of them.
This can be fixed with a config change in one of the two other nodes.
Hope to help
Giuseppe
