Emerson Exchange 365

• Not Answered

Single CSLS causing SZ controller failure

Hi.

We have a project in the development phase which has a SIS element consisting of a single redundant SZ controller and 9 CSLS.

We have been developing with this kit for a couple of weeks when all of a sudden, the SZ controller has started resetting. Communications are not lost but after a successful download completes and after restart the SZ has lost its config again.

After initial fault finding I have identified one of the CSLS that seems to be causing the issue by disconnecting the ethernet to all CSLS and re-introducing one by one.

Can anyone suggest what could be causing this and how to get around it?

The SZ does not stay operational long enough to perform a decommission of the effected CSLS.

 

Any help gratefully received.

• CSLS
• fail
• SZ controller
• restart
• fallover
• communications

Ed OBrien

• 17 Jul 2019 6:43 PM
• Cancel

1 Reply

• Andre Dicaire

  

  • 17 Jul 2019 7:30 PM

  this is really for the GSC to investigate with you. You can try moving CSLS processors one at a time in simplex to a different carrier and see if you can confirm the Software/Hardware versions. If you are unable to communication with one or more CSLS or if problem only occurs on a given Carrier, Isolate to the hardware that does not work and look to have it replaced, if the GSC is not able to offer you a solution you can implement locally.

  Andre Dicaire

  • Cancel