Symptom
PTP went down and below error logs are seen on standby RSP.
RP/0/RSP1/CPU0:Feb 25 16:22:18.876 IST: wdsysmon[485]: %HA-HA_WD-6-TOP_PULSEQ_USER : Top PulseQ User 0 PROCESS PID-913776 NAME = ptp_ctrlr COUNT=16025
RP/0/RSP1/CPU0:Feb 25 16:22:18.876 IST: wdsysmon[485]: %HA-HA_WD-6-TOP_PULSEQ_USER : Top PulseQ User 1 PROCESS PID-692368 NAME = syncctrl COUNT=12770
RP/0/RSP1/CPU0:Feb 25 16:22:18.876 IST: wdsysmon[485]: %HA-HA_WD-6-TOP_PULSEQ_USER : Top PulseQ User 2 PROCESS PID-708813 NAME = fsyncmgr COUNT=2124
RP/0/RSP1/CPU0:Feb 25 16:22:18.876 IST: wdsysmon[485]: %HA-HA_WD-6-TOP_PULSEQ_USER : Top PulseQ User 3 PROCESS PID-913740 NAME = isis COUNT=5
RP/0/RSP1/CPU0:Feb 25 16:22:18.876 IST: wdsysmon[485]: %HA-HA_WD-6-TOP_PULSEQ_USER : Top PulseQ User 4 PROCESS PID-213096 NAME = licmgr COUNT=1
RP/0/RSP1/CPU0:Feb 25 16:23:18.979 IST: wdsysmon[485]: %HA-HA_WD-4-PULSEQ_ALARM : PULSEQ STATE ALARM:IN STATE:SEVERE STATE
Conditions
ASR9k with PTP configuration and RSP440.
Further Problem Description
This fix allows timing on active RSP to work properly even if the standby RSP is faulty.
