Resolution Of Known Customer Issues

F Resolution Of Known Customer Issues

Issue: TKSPLATMA20|tpdDeviceError is observed in alarmMgr --alarmStatus output and LSMS-NAS-MIB::volumeNearlyFull is observed in syscheck even if disk if free on NAS

Description: It has been observed that once NAS volume is full, an alarm is raised on LSMS stating that NAS volume is full, but it does not get cleared automatically from syscheck or alarmMgr --alarmStatus

Solution:

Run the following commands from NAS:

From LSMS do ssh backupserver and run the below commands

/usr/bin/snmptrap -v 2c -c public server1A '' LSMS-NAS-MIB::volumeRepaired enterprises s
      'volume_repaired
/usr/bin/snmptrap -v 2c -c public server1B '' LSMS-NAS-MIB::volumeRepaired
      enterprises s 'volume_repaired'

Then run the below command on both LSMS A and B:

alarmMgr --clear TKSPLATMA20

Issue: Initial Configuration Menu Not Visible After Initial Configuration Is Successful

Description: On LSMS, once initial configuration is done by running all options, the menu option is not visible to customers. This happens when the initial configuration is re-run by mistake, impacting the functioning of the server and requiring re-installation. In some cases, it might be required to reconfigure NAS even after initial configuration is done. This option is available only in the initial configuration menu.

Solution: The below mentioned command can be used to show/hide initial configuration menu:

platcfgadm --show "InitialConfig" --user=lsmsmgr

platcfgadm --hide "InitialConfig" --user=lsmsmgr

Issue: 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.