On removing Primary OR secondary cable from Pri AS1(6.0.2) all system alarms become RTN
In one of our system 6.0.2 on removing Pri AS1 (primary Or secondary) cable all other unconnected servers will show RTN in alarm list.
1. checked RNRP found Ok (primary and secondary) and disabled RSS and Ping Ok
2.Disconnected primary/secondary for each servers found alarm in HMI.
3.restarted the Pri AS1 and sec AS1 but problem remains.
4.On swich off Primary/secondary switch connected to Redundant servers then all system alarms related to servers including Sec-AS showing connection down then again made it normal
5.On switch off secondary/Primary switch of primary servers then it's generating only Primary aspect alarm
a)Primary switches (2 No) extended as bus network to connect each other from different cabinet such that all primary servers connected to one switch and other redundant servers connected to another primary switch.
b)Secondary switches (2 No) extended as bus network to connect each other from different cabinet such that all primary servers connected to one secondary switch and other redundant servers connected to another secondary switch.
The RNRP Connection down alarms in the System Alarm list are delivered by the System Status service, this service is redundant and usually the first aspect server is in "Service" state while the secondaries are kept in "Standby".
If the primary aspect server becomes disconnected from the secondaries, the "primary among the secondaries" will promote its System Alarm service into "Service".
Because of this, network disturbances may create two or more "islands" with independently operating System Alarm services. "Team AS1" will point out the others as "down" while "Team AS2" will point out "Team AS1" as down; both are in principle correct.
After the network disturbance has settled down and connections are restored, the System Alarm list will now reflect "Team AS1" (other alarms are removed) and the System Event List may or may not list a summary of all teams.
The order of the primary and secondaries are decided by the Service Group configuration. If servers have been removed and readded, the order in effect might not be what you expect, e.g. AS1 last.
I try to convey the message that removing and readding a server is often a futile exercise (with no effect on the real problem) - but it may (will?) toss around service provider order and mess up Affinity. IMHO: never remove+readd a server or client during troubleshooting.
I recommend using System Alarm and System Event Lists as indicators only - to really know what took place and when, in each affected server or client, check the locally running RNRP event log (the RNRP Config Wizard has a button to launch the log in notepad.exe).
These files reflect what took place, from a local perspective, which in my view is more true information than a global summary.
If this does not explain or match up with your situation, please forward a support case via your regional ABB support center.