One specific CPU goes into fault; when connected to module bus clusters.
HI Everyone,
Facing one strange issue:-
Software:- CHMI-6.0.0-1
CPU:- Redundant PM-862 with 5 nos. of module bus cluster nodes (TB-840A)
Observation:-
Both CPU when powered on without connecting any nodes; found ok. As nodes are switched on; secondary controller goes in to fault. In order to troubleshoot, following excercise has been done:-
1. Checked with replacing, OFC patch cords.
2. Upgraded firmware and re-configure IP addresses of both CPU.
3. Checked by configuring new project and with one single node also.
Let's say we have CPU-A and CPU-B:-
Case:-1
1. CPU-A is primary and CPU-B is secondary:- On switching on nodes; nodes are getting communicated with CPU-A and CPU-B goes into fault.
2. CPU-A is ON and CPU-B is OFF:- On switching on nodes; nodes are getting communicated with CPU-A.
3. CPU-A is OFF and CPU-B is ON:- Nodes does not communicated.
Case:2
1. CPU-B is primary and CPU-A is secondary:- On switching on nodes; nodes are getting communicated with CPU-A and CPU-B goes into fault.
2. CPU-A is ON and CPU-B is OFF:- On switching on nodes; nodes are getting communicated with CPU-A.
3. CPU-A is OFF and CPU-B is ON:- Nodes does not communicated.
Not sure, if there is some issue with specifically CPU-B; because in every case CPU-B goes into fault.
Log files attached for reference.
Best Regards,
Rachit
Facing one strange issue:-
Software:- CHMI-6.0.0-1
CPU:- Redundant PM-862 with 5 nos. of module bus cluster nodes (TB-840A)
Observation:-
Both CPU when powered on without connecting any nodes; found ok. As nodes are switched on; secondary controller goes in to fault. In order to troubleshoot, following excercise has been done:-
1. Checked with replacing, OFC patch cords.
2. Upgraded firmware and re-configure IP addresses of both CPU.
3. Checked by configuring new project and with one single node also.
Let's say we have CPU-A and CPU-B:-
Case:-1
1. CPU-A is primary and CPU-B is secondary:- On switching on nodes; nodes are getting communicated with CPU-A and CPU-B goes into fault.
2. CPU-A is ON and CPU-B is OFF:- On switching on nodes; nodes are getting communicated with CPU-A.
3. CPU-A is OFF and CPU-B is ON:- Nodes does not communicated.
Case:2
1. CPU-B is primary and CPU-A is secondary:- On switching on nodes; nodes are getting communicated with CPU-A and CPU-B goes into fault.
2. CPU-A is ON and CPU-B is OFF:- On switching on nodes; nodes are getting communicated with CPU-A.
3. CPU-A is OFF and CPU-B is ON:- Nodes does not communicated.
Not sure, if there is some issue with specifically CPU-B; because in every case CPU-B goes into fault.
Log files attached for reference.
Best Regards,
Rachit
Asked 1 year ago
Answers
0
Check the healthiness of cluster modems/bases. Probably one of them in B side is not working. You can confirm by swapping the fiber optic cables in controller and re-doing the above said steps.
Answered 1 year ago
Add new comment