Expilicit IP Addressing ABB Controllers & Networking
Dear All, I have a special requirement from Customer not to use default ABB IP addressing for the Plant, We have two Control Networks - CN1 and CN2 both are redundant (CN1 primary & Secondary ) & (CN 2 primary & Secondary )
IP Ranges of Primary CN1 - 10.109.114.0/24
IP Ranges of Secondary CN1 - 10.109.115.0/24
IP Ranges of Primary CN2 - 10.109.116.0/24
IP Ranges of Secondary CN1 - 10.109.117.0/24
IP Ranges of Primary Client Server - 10.109.112.0/24
IP Ranges of Secondary Client Server - 10.109.113.0/24
Also we will use NE870 ( Redundant ) for each Control Network
Switch Admin Network will be 10.109.10.0/23
While allocating the IP address for the Controllers in the Control Network, the node numbers are getting changed for the primary and secondary.
Example for the Controller IP : 10.109.114.110 /24( Ethernet #1 ) - Node number is 622 as per ABB Calculation ( Network configuration document 6.1)
for Ethernet # 2 IP address: 10.109.115.110 /24 - Node number is 878 ( Used Stephan.Hissbach's RNRP address Calculator for this calculation)
also the path number is 1 for both this IP. the Network area also same for both the IP's - As the third octet is getting modified for primary and secondary IP's.
my request is to know if these allocated IP ranges are valid for our RNRP configuration , if it is valid how to provide the Node numbers, Path and Area for the Controller ethernet addressing.
What base address has to be provided in Controller Settings and also in NE870s
As this is Explicit addressing can I just use the last part of IP address as the Node number , primary path as “0”, Secondary path as “1” and Area as 22 for CN1 and 24 for CN2 , without worrying much about the calculations.Thanks in advance,
Voted best answer
I suggest to study IP addressing and subnet mask theory on Wikipedia. Using /24, the highest possible node number is 254.
The 172.x.y.z (implicit scheme) is recommended to minimize efforts to configure networking. Explicit configuration is more time consuming and error prone.
Customer should not have anything to complain over by you opting for the easier and less effort implicit scheme.
With other words, all seem OK except for the tools you are using to calculate and the added effort of having to calculate explict parameters for every node and interface.
defining std/implicit rule is easier to trouble shoot and maintain.
If you want to configure IP address explicitly still possible, you have to do the manual configuration of RNRP parameters in each node and each path that includes controller as well.
keep in mind needs restart of RNRP and controller warm download.
It works i did it one project.