1. Service model’s status in TrueSight Presentation Server (TSPS) is not in sync with TrueSight Infrastructure Management (TSIM)
2. CI removed from Service model in TSIM is still appearing in TSPS service model
3. Newly added service model in TSIM is not seen in TSPS

Enable following debug logs on TSPS and TSIM, collect thread dump for the TSIM’s jserver process and raise a ticket with BMC Support for further analysis of the issue:

1. Enable debug on TSPS using commands
tssh logger debug on -n TsimAudit
tssh logger debug on -n AppContextApplication
tssh logger debug on -n com.bmc.sas.ngp.service.message.impl
tssh logger debug on -n com.bmc.truesight.platform.etl.CI.TSIMSyncCICRUDTask

2. Enable debug on TSIM using commands
pw debug on -p pronet_cntl -s MessageServiceAC
pw debug on -p jserver -s  MessageServiceJS

3. Reproduce issue, Collect few snapshots of problem if possible.

4. Collect thread-dump of TSIM’s jserver process. This can be done by running following commands from command prompt
pw threaddump <pid/pname> (Windows)
kill -QUIT <pid> (UNIX)

5. Disable debug on TSPS using commands
tssh logger debug off -n TsimAudit
tssh logger debug off -n AppContextApplication
tssh logger debug off -n com.bmc.sas.ngp.service.message.impl
tssh logger debug off -n com.bmc.truesight.platform.etl.CI.TSIMSyncCICRUDTask

6. Disable  debug on TSIM using commands 
pw debug off -p pronet_cntl -s MessageServiceAC
pw debug off -p jserver -s  MessageServiceJS

7. Then Immediately collect following logs, Raise support case and attach to BMC case
         a.     pw/pronto/logs directory from TSIM
         b.     TrueSightPServer/truesightpserver/logs from TSPS server

Please note: - if you restart TSPS and TSIM application this issue will get resolved but this is only workaround. Since BMC need to find root cause of issue to provide permanent fix ,We would recommend you to go through above steps and collect requested data to help us to resolve issue on permanently