RNRP Binding Issue
800XA 6.0.3
windows 2016/Windows10
DNS setting done to listen only only for Client Server Primary/Secondary.
We have total 3 network in a Node : Client Server Primary / Client Server Secondary / Management
Below issue we are facing :
windows 2016/Windows10
DNS setting done to listen only only for Client Server Primary/Secondary.
We have total 3 network in a Node : Client Server Primary / Client Server Secondary / Management
Below issue we are facing :
- Network Adaptor sometime is not showing the Domain Name ( Shows as public network )
- Primary Client server get always get Metic-1 after any restart - but secondary and management network goes to automatic and management network get the lower metric number than secondly
- Below error are shown in RNRP route add , error =5010 ( As soon as management adaptor is disabled issue get resolved )
- SPDC Shown below error adaptors Media Disconnected
Asked 10 months ago
Answers
0
Which system version of 6.0.3?
6.0.3.0 (initial release several years ago)
6.0.3.1
6.0.3.2
6.0.3.3 (released some months ago)
I'm guessing 6.0.3.2 or 6.0.3.3 since support for Server 2016 was added in 6.0.3.2.
There is actually a 6.0.3.3B revision out (the first attempt to release 6.0.3.3 had a flaw with ProfiBus and a revision had to be made).
RNRP will set the Interface Metric of the primary path of the primary RNRP network area to 1. This is expected and will make sure DNS resolution start with this interface. The domain controllers should be on this primary area. The primary area is defined as the lowest RNRP area number except area 0. So, make sure your domain controllers are on the RNRP area having the lowest, non-zero area number.
The rest of the network adapters will be set to Automatic and gain an automated Interface Metric based on the Ethernet Link capabilities, e.g. a faster link speed will drive a lower metric shown in "route print". What makes the Management Network second in Metric is hard to tell. It's not a big deal as long as the primary area's primary path has best (lowest) Interface Metric.
Route add, error=5010 indicates RNRP is not able to manage the computer's routing table properly (something is out of sync). If you know how, stop RNRP service and purge the routing table from any non-default routes, then start RNRP service again. Another option is to restart the computer. Remember some routes can be made persistent (-p) and will survive a reboot. Make sure no such manual manipulations have been done that conflicts with RNRP. Let RNRP govern the routing table and Interface Metric.
I don't think SPDC can contribute with so much in these circumstances... try adhere to the System Health Check Manual, attached.
If not at 6.0.3.3, please consider upgrading since I know RNRP was updated in that revision of System 800xA.
If you can't work this out, please file a support case with your regional ABB support center.
6.0.3.0 (initial release several years ago)
6.0.3.1
6.0.3.2
6.0.3.3 (released some months ago)
I'm guessing 6.0.3.2 or 6.0.3.3 since support for Server 2016 was added in 6.0.3.2.
There is actually a 6.0.3.3B revision out (the first attempt to release 6.0.3.3 had a flaw with ProfiBus and a revision had to be made).
RNRP will set the Interface Metric of the primary path of the primary RNRP network area to 1. This is expected and will make sure DNS resolution start with this interface. The domain controllers should be on this primary area. The primary area is defined as the lowest RNRP area number except area 0. So, make sure your domain controllers are on the RNRP area having the lowest, non-zero area number.
The rest of the network adapters will be set to Automatic and gain an automated Interface Metric based on the Ethernet Link capabilities, e.g. a faster link speed will drive a lower metric shown in "route print". What makes the Management Network second in Metric is hard to tell. It's not a big deal as long as the primary area's primary path has best (lowest) Interface Metric.
Route add, error=5010 indicates RNRP is not able to manage the computer's routing table properly (something is out of sync). If you know how, stop RNRP service and purge the routing table from any non-default routes, then start RNRP service again. Another option is to restart the computer. Remember some routes can be made persistent (-p) and will survive a reboot. Make sure no such manual manipulations have been done that conflicts with RNRP. Let RNRP govern the routing table and Interface Metric.
I don't think SPDC can contribute with so much in these circumstances... try adhere to the System Health Check Manual, attached.
If not at 6.0.3.3, please consider upgrading since I know RNRP was updated in that revision of System 800xA.
If you can't work this out, please file a support case with your regional ABB support center.
Add new comment