RNRP Router redundancy on Cross Control network failure
We have two RNRP Router we checked a cross failure scenario for control network and client/server network.
1. We have removed Control network A from first RNRP router and Control Network B from second RNRP router.
2. We have seen in the RNRP one router is fully disconnected from RNRP monitor and one RNRP router is showing both network is (up,up) - in reality we have removed one network from both RNRP router.
Control network B is reported failure for all nodes.
What is the reason for RNRP reporting with one RNRP router showing (up,up) ?
When one RNRP router has A Side and anothe RNRP has B control network why we have control network B is fully down ?
1. We have removed Control network A from first RNRP router and Control Network B from second RNRP router.
2. We have seen in the RNRP one router is fully disconnected from RNRP monitor and one RNRP router is showing both network is (up,up) - in reality we have removed one network from both RNRP router.
Control network B is reported failure for all nodes.
What is the reason for RNRP reporting with one RNRP router showing (up,up) ?
When one RNRP router has A Side and anothe RNRP has B control network why we have control network B is fully down ?
Asked 10 months ago
Answers
1
This is, since a couple of week's time a known issue with the RNRP status reporting in 6.0.3-2.
The actual IP routing is not affected; verify with ping. You can also type "route print" to display facts about which node the client/server node will use as router to reach the control network area(s) and path(s).
The problem is still under investigation; please stay tuned to ABB Library for upcoming new product bulletins and/or release notes where this issue will be given a Product Issue Number (PIN) and current status of problem vs correction.
The actual IP routing is not affected; verify with ping. You can also type "route print" to display facts about which node the client/server node will use as router to reach the control network area(s) and path(s).
The problem is still under investigation; please stay tuned to ABB Library for upcoming new product bulletins and/or release notes where this issue will be given a Product Issue Number (PIN) and current status of problem vs correction.
Add new comment