CM filesync failed for all LSP servers

Doc ID		SOLN268530
Version:		2.0
Status:		Published
Published date:		16 Aug 2016
Created Date:		14 May 2015

Author:

Hai Huang

Details

CM Release version 5.2.1 SP5

Problem Clarification

Customer is reporting below filesync alarms, and all the LSP servers are not being updated during daily maintenance or manual save trans. Can't reach out (ping/traceroute/ssh) to these LSP servers from main CM active server, and also they can't login the SMI webpage of the main active server, but main standby server is all ok.

ID Source EvtID Lvl Ack Date Description

2 FSY 1 MIN Y Wed May 13 04:13:49 SGT 2015 file sync failed for LSP/ESS

1 FSY 1 MIN Y Wed May 13 04:08:25 SGT 2015 file sync failed for LSP/ESS

0 FSY 1 MIN Y Wed May 13 04:03:23 SGT 2015 file sync failed for LSP/ESS

Name            Type      IP Address     Reg Act
Translations     Net

                                                          Updated          Rgn

LM-JP-PE        ESS D     172.28.72.17    y   n          4:00 5/13/2015    1

LM-TPE-LSP      LSP       172.28.47.5     y   n          4:00 5/12/2015    9

LM_HK_LSP       LSP       172.28.51.5     y   n          4:00 5/12/2015    8

LM_MEL_LSP      LSP       172.28.56.5     y   n          4:00 5/12/2015    7

Cause

The Corp LAN/PE (eth4) IP address of the main CM server was configured on these LSP servers for synchronization, and they registered to main CM server via a CLAN.

Captured sniffer trace and found IP conflict on Main active server IP 172.28.52.15, there is another device on their network with below mac address is using the same IP address.

Source: Cisco_a4:e2:67 (f0:9e:63:a4:e2:67)

Attached the sniffer trace.

Solution

Customer need to resolve the IP conflict issue on their network.

Attachment File

pingtest.pcap
0Bytes • < 1 minute @ 56k, < 1 minute @ broadband

Additional Relevant Phrases

CM6.0.1 patch 15928

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy