RTA Node disconnection from AC50 Controller Master table view
After RTA board power restarts, the RTA board Node gets disconnected from the Controller "Master Table View". And, the particular controller Alarms & Events are stopped to appear in the 800xA System.
After the RTA node is manually added in the Controller Master Table View by "OMVT" command, Alarms & Events are started to appear in the 800xA and it is working okay.
There are total 4 Controller nodes in the site, the above problem is observed only in a particular controller node.
System details are,
Controller - AC 450, PM510
RTA Unit - PU410
800xA System - 800xA 5.1 Rev-E, FP4.
attached the screenshots.
1. What cause the RTA node gets disconnected from the Controller Master view table ?
2. Why the problem is observed only in a particular node in the system ? Should i check any hardware settings in that controller node ?
Appreciate your quick reply.
Answers
Sounds like the RTA event filtering configuration may be wrong.
Check the NODE_DESCR settings on the RTA board. Save and reboot the RTA again.
Answer to question 1: A node (Here: The RTA node) gets removed from MVTAB when the node that table resides in (The AC450) detects that the (RTA) node is no longer on the MB300 network. This is part of the low level function from the days of MasterPiece and MasterView.
2. Don't know. When a new node starts up (here: The RTA node) and it wants to subscribe to events it sends out a broadcast asking if anyone wants to supply this. If the (here: problem) node does not reply, the RTA node will not send a new message asking to be added to the its MVTAB. Is there anything particular with the problem node, such as not being on both redundant networks, having high load etc,?
AFAIK only a warm start (or CLEAR INIT) of an AC400 controller purges its MVT.
The typical problem is the inverse... too many nodes in MVT leading to ”DCBAG03 24 16” messages for each alarm that cannot be delivered.
If a node has left MVT, a restart is very likely (detected or not).
Add new comment