MB300 primary network lost resulted in Node to Node communication failure and Data set signal loss
Did any one come across MB300 primary control network issue in the past which could result in data set lost between AC450 Nodes?
As a part of MB300 redundancy check we disconnect primary network connection from CS513 which in turn resulted in data set signal loss between nodes, but secondary CN network works fine. From functional stand point of MB300 network the secondary network should automatically take over in case of fault in the primary network and it should be bumbles. HMI data remains normal but node to node communication fails and Data set Not valid Alarms appears on the OS500.
We tried by replacing the Alled telisis switces with new hirschmann network switches , new AUI Transceiver ,new FO and Ethernet cables but no luck
I am just wondering whether this could be AC450 Firmware issue? we have AC450 with QC07-BAS41*1.0/1 and QC07-BAS41*4.0/1 two versions in our site
Voted best answer
Login to RTA and provide the output of LNET xx for your primary and secondary control network, eg 11 and 12
# SLLEV SYST
* LOCPSET CMDS:TP02.CT
* LNET 11
* LNET 12
To spot a partly broken fiber or Ethernet hardware (fault exists in one direction only) compare what the LNET command output in the subject node and a reference node (e.g. RTA or another controller).
From RTA Board Configuration, load an troubleshooting command processor and remove the lock that prevents you from connecting a remote node:
* LOCPSET CMDS:TP02.CT
* DFTARG -1,-1
Then press <CTRL-B>
Now SLTARG to the suspect and reference nodes and call LNET for primary and secondary MB300 network, e.g. 11 and 12 or 21 and 22.
The result is a table of the selected network with a matrix containing all remote nodes (read decade on X-axis, 0, 20, 40, .., then add 0-20 from the Y-axis)
- A direct reachable node is represented with 00xxxxxx (x = positive integer)
- An indirectly (via another network) reachable node is represented with F9xxxxxx (x = positive integer)
- A no longer reachable node is represented with 04000000.
- ........ = never seen node
A broken fiber will give an asymmetric result, different depending on what node you probe from.
Be on the lookout for F9 entries (reachable via another network than the queried)