6. REDUNDANCY WITH NX3030 CPU
A cluster of two Ethernet ports forming a NIC Teaming pair has a single IP address, related to the port pair. This way, a
client as SCADA or MasterTool, connected to a CPU server, doesn’t need to worry in IP address changing in case there’s a
failure in any NIC Teaming pair port.
Each of the Ethernet interfaces that form the NIC Teaming pair have an unique diagnostics structure to point to failures
which eventually might appear in any port of a NIC Teaming pair.
For further details regarding NIC Teaming configuration and diagnostics, see the following sections:
Ethernet Ports Configuration in the CPU NX3030 (NET 1 and NET 2)
NX5000 Modules Configuration
6.3.11. IP Change Methods
A redundant cluster from Nexto Series has four methods for IP change in the Ethernet ports of the NX5000 modules in each
half-cluster and one method for IP change in the NET 1 and NET 2 ports of the NX3030 CPU. These methods define the ports’
behavior, regarding its IP, according to the current state of the half-cluster (Active or Non-Active) and with the half-cluster
(PLCA or PLCB).
The methods are: Fixed IP, Exchange IP, Active IP and Multiple IP.
Overall, it can be listed up to four IPs, according to the IP change method.
6.3.11.1. Fixed IP
It’s the simplest method for IP addressing and can be configured in the Ethernet interfaces in the NX5000 Ethernet modules.
In this method, it’s only listed the IP addresses from the PLCA and from PLCB. Apart from the redundancy state, PLC Active
or Non-Active, the PLCA will always answer by the configured IP, as also will PLCB.
Figure 172: Fixed IP method
Parameters that must be configured in the Fixed IP method:
IP Address PLC A: PLCA communication address
IP Address PLC B: PLCB communication address
Subnetwork Mask
Gateway Address
6.3.11.2. Exchange IP
The Exchange IP can be configured in the Ethernet interfaces in the NX5000 Ethernet module. In this method, the half-
cluster IP depends on the PLC state (Active or Non-Active). On every switchover the IP change occurs between the half-clusters
allowing them to assume the IP address from the new redundancy state.
PS: for this addressing method, the Ethernet ports from both PLCs (PLCA and PLCB) assume the same IP address while
they both are in the Non-Active state, generating a network address conflict. Considering this situation uncommon, where no
PLC is controlling the system, this turns out to be a big problem and has to be considered.
289
To Next Page
Loading...
Need help?
General
