ALTUS Nexto NX3004 User Manual

6. Redundancy with NX3030 CPU
284
 PO5065: PROFIBUS slave DP-V1 with Hart, for Ponto Series remotes;
 AL-3416: PROFIBUS slave DP-V0 for AL-2004 CPU.
 NX5210: PROFIBUS slave DP-V0 for Nexto Series remotes.
Figure 6-1 also shows the possibility to connect non-redundant remotes to this type of redundant
PROFIBUS network, through the AL-2433 module (ProfiSwitch). Such non-redundant PROFIBUS
remotes can be from any brand or model.
PROFIBUS Failure Modes Vital and Not-Vital
Each one of the PROFIBUS networks can be configured in two different modes:
 Vital failure: in case this network fails completely, this failure can determine a redundancy state
transition in the redundant CPU (switchover). In case a redundant PROFIBUS network, a
complete failure implies in the failure of both composing networks.
 Not-Vital failure: even if this network fails completely, this failure won’t determine a
redundancy state transition in the redundant CPU (switchover).
Redundant Ethernet Networks with NIC Teaming
Figure 6-1 shows two redundant Ethernet networks examples, with NIC Teaming.
In the first case, the NX3030 CPU connects to the supervision network (SCADA), also used for
configuration through MasterTool. Both NX3030 CPU Ethernet ports (NET 1 and NET 2) form a
NIC Teaming redundant pair, interconnected in two different switches (Ethernet A and Ethernet B).
In some point, these two switches must be interconnected, for the two NIC Teaming ports connection
and for an even higher availability (against double failures).
In the second case, two NX5000 modules also form a NIC Teaming redundant pair, interconnected in
two different switches (Ethernet HSDN A and Ethernet HSDN B). In some point, these two switches
must be interconnected, for the two NIC Teaming ports connection and for an even higher
availability (against double failures).
Such Ethernet architectures turn possible an excellent availability, against Ethernet port failures, in
cables and switches.
ATTENTION:
If two modules, or Ethernet interfaces, form a NIC Teaming redundant pair, the configuration and
device inclusion will be only possible in the first interface. The second interface will have his
configuration parameters blocked for edition.
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 a 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
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 NET1 and NET2 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.

ALTUS Nexto NX3004 Specifications

General

Brand	ALTUS
Model	Nexto NX3004
Category	Processor
Language	English