Thanks Lennart, I change to invalid now since the ticket is written in a view
of defect. We will create an enhancement one in a view of improvement.
---
** [tickets:#2688] NTF: Cold sync misses to sync logged alarm (cached)
notification**
**Status:** accepted
**Milestone:** 5.18.01
- **status**: accepted --> invalid
- **assigned_to**: Minh Hon Chau --> nobody
---
** [tickets:#2688] NTF: Cold sync misses to sync logged alarm (cached)
notification**
**Status:** invalid
**Milestone:** 5.18.01
**Created:** Tue Nov 21, 2017 04:29 AM UTC by Minh Hon Chau
**Last Updated:**
This is not a defect. NTF is working according to NTF PR document where it is
clearly documented that among other things cold sync of stored alarm
notifications is not implemented, also this store is not persistent and only
alarm notifications are stored
This means that this ticket must be
Please note that the solution of #2688 will not help in the scenario of
upgrade. At the time that reboots the standby SC (new software), the NTFD in
active SC is still old software so that it can not sync the cached alarm to
standby NTFD.
---
** [tickets:#2688] NTF: Cold sync misses to sync
- Description has changed:
Diff:
--- old
+++ new
@@ -6,4 +6,4 @@
- swap 2N Opensaf SI
- ntfread, no alarm is printed
-After reboot the standby SC, the alarm that was logged in active SC are not
synced to standby SC, thus after switchover, ntfread shows no alarm
+After reboot the
- **summary**: NTF: Cold sync misses to sync alarm logged notification --> NTF:
Cold sync misses to sync logged alarm (cached) notification
---
** [tickets:#2688] NTF: Cold sync misses to sync logged alarm (cached)
notification**
**Status:** accepted
**Milestone:** 5.18.01
**Created:** Tue
