IAC communication between different subnet 800xA Systems
We have a case where we have 800xA systems (V5.1) with different IP series ( Area 4 and Area 20 for system 1 and system 2 respectively) and controller series also in different series ( area 21 and area 20)
as per RNRP routing its possible to have an IAC-Communication variable interface between two controllers of the different system if the Client-server network is connected,
We are planning to have one additional network card with network area 4 in system 2 and communicate with System 1, this way now AS and CS servers are connected between Syst 1 and Syst 2, will the RNRP route IAC communication between controllers? or is there any better workaround?
as per RNRP routing its possible to have an IAC-Communication variable interface between two controllers of the different system if the Client-server network is connected,
We are planning to have one additional network card with network area 4 in system 2 and communicate with System 1, this way now AS and CS servers are connected between Syst 1 and Syst 2, will the RNRP route IAC communication between controllers? or is there any better workaround?
Asked 26 days ago
Answers
2
IAC, MMS, SNTP, etc. exchange is possible if there is a routable path between the control networks.
Using default settings, RNRP would configure this interconnectivity fully automatically, however, both systems would then also "see each others nodes" in RNRP Network status tools. This might not be desirable.
To declutter the RNRP status tools, I suggest connecting via a RNRP "Backbone" setting (read about backbone in the Network Configuration manual).
In layman terms, an RNRP backbone acts a default gateway - where telegrams for "unknown destinations" are routed.
E.g. one or two connectivity servers of System A and B are equipped with an extra network card.
The RNRP Router To Ext Netw setting can be used in several "layers", also in RNRP in nodes running Microsoft Windows, each layer forwards telegrams with unknown destination "upwards" until reaching a common backbone where it takes "step to the side" (to another backbone router) and begin its travel downwards again.
Technically, it is also possible to make backbones on the "bottom level" below the controllers, then it is usually called a "controller backbone".
The "RNRP Ext Netw ID & Mask" settings cuts off the reachability, e.g. 172.16.0.0/15 will limit use of the backbone for 172.16.x.y. addresses with redundant path only. This opens up for using the traditional Default Gateway setting in AC 800M and Microsoft Windows for connectivity with even more distant destinations.
Using default settings, RNRP would configure this interconnectivity fully automatically, however, both systems would then also "see each others nodes" in RNRP Network status tools. This might not be desirable.
To declutter the RNRP status tools, I suggest connecting via a RNRP "Backbone" setting (read about backbone in the Network Configuration manual).
In layman terms, an RNRP backbone acts a default gateway - where telegrams for "unknown destinations" are routed.
E.g. one or two connectivity servers of System A and B are equipped with an extra network card.
- This extra NIC is set as RNRP backbone (requires explicit declaration, Local Area Flag = 2).
It is common to select Area 0 (172.16.0.0/22) as backbone area number, but there is no requirement for doing so. Any unique number between 0 and 63 is OK to use. - The AC 800M controllers of system A and B need to be downloaded with "RNRP Router To Ext Netw" setting pointing to the regular connectivity servers (two can be defined, for redundancy)
The RNRP Router To Ext Netw setting can be used in several "layers", also in RNRP in nodes running Microsoft Windows, each layer forwards telegrams with unknown destination "upwards" until reaching a common backbone where it takes "step to the side" (to another backbone router) and begin its travel downwards again.
Technically, it is also possible to make backbones on the "bottom level" below the controllers, then it is usually called a "controller backbone".
The "RNRP Ext Netw ID & Mask" settings cuts off the reachability, e.g. 172.16.0.0/15 will limit use of the backbone for 172.16.x.y. addresses with redundant path only. This opens up for using the traditional Default Gateway setting in AC 800M and Microsoft Windows for connectivity with even more distant destinations.
Add new comment