F Resolution Of Known Customer Issues

Issue: startNode Command gets stuck in ACTIVE -> TO-ACTIVE state

Description: It has been observed in LSMS that during startNode on active server, sometimes even after Node is started, the server gets stuck in ACTIVE -> TO_ACTIVE state as shown below:

$hastatus
ACTIVE "lsmspri->TO_ACTIVE"

Solution:

Remove the file /usr/TKLC/plat/etc/HA/state.d/.haTransitionInProgress_lsmspri if issue is observed on primary server or /usr/TKLC/plat/etc/HA/state.d/.haTransitionInProgress_lsmssec if issue is observed on secondary server using command as mentioned below:

$ rm /usr/TKLC/plat/etc/HA/state.d/.haTransitionInProgress_lsmspri

Issue: The following alarm is observed:

FALARM LOG << 20240923090347 >> [4008:LSMS] DB Proc Mon Err - HA STATE IS UNINITIALIZED!

Description: Alarm gets cleared automatically. The issue is observed as hastatus command sometimes reports status as UNINITIALIZED, which is not the correct status. However, during the next run, the status is reported correctly and the alarm is cleared.

Solution: If hastatus is observed as UNITIALIZED on running server, re-run the command if this is observed.