ALTUS Nexto NX3004 User Manual

6. Redundancy with NX3030 CPU
288
Parameters that must be configured in the Multiple IP method:
 IP Address PLC A Active: PLCA communication address, when in Active state.
 IP Address PLC A Non Active: PLCA communication address, when in Non-Active state.
 IP Address PLC B Active: PLCB communication address, when in Active state.
 IP Address PLC B Non Active: PLCB communication address, when in Non-Active state.
 Subnetwork Mask.
 Gateway Address.
NIC Teaming and Active IP Combined Use
In case a determined port pair form a NIC Teaming in a redundant CPU, these ports can implement,
at the same time, the strategies NIC Teaming and Active IP.
E.g. if the NX3030 CPU NET 1 and NET 2 ports form a NIC Teaming pair, then:
 IP Address PLC A: IP address of the NET 1 + NET 2 ports in the PLCA NX3030 CPU
 IP Address PLC B: IP address of the NET 1 + NET 2 ports in the PLCB NX3030 CPU
 IP Address Active: IP address of the NET 1 + NET 2 ports in the NX3030 CPU in the Active
CPU
This way, the excellent availability from the NIC Teaming strategy is associated with the practicality
of the Active IP strategy, which doesn’t need scripts in SCADA systems or in other clients connected
to the Active CPU server.
Ethernet Interfaces Use with Vital Fault Indication
The Ethernet ports of NX3030 and NX5000 modules can be configured to generate vital failures.
This option is important for applications in which the modules of inputs and outputs are distributed
over Ethernet network. In this case, if a failure occurs on the Ethernet port, this will generate a
switchover. This behavior is applicable only to Ethernet ports where there is at least a communication
driver that manages fault.
The communication drivers that generate vital failure are MODBUS client and MODBUS Symbol
Client (all references to MODBUS Client in the following sections apply to both cases). The
MODBUS Server drivers, MODBUS Symbol Server and EtherCAT Master do not generate vital
failure. Thus, if an Ethernet port has a MODBUS Client driver configured and a failure occurs in the
Ethernet port, a switchover will be generated if vital fault option is enabled. If the driver configured
on the Ethernet port is a MODBUS Server, even if there is failure in the door, it will not generate a
vital failure that causes a switchover.
To a fault be considered a vital failure in an Ethernet port on a MODBUS Client, all servers
configured in the driver must be faulty. That is, if there is more of a MODBUS Client driver
configured in the same Ethernet port, is considered vital fails when all servers of both Clients are
faulty.
When the Ethernet port is configured to operate with NIC Teaming, the vital failure will be
considered only when the two pair of doors fails.
Failure in Ethernet Interface
A switchover can be generated due to failure in the Ethernet interface, such as a loss of link. The link
loss may be caused, for example, by a cable breakage or failure of a switch on the Ethernet network.
Accordingly, it is necessary that, in addition to being configured to generate vital failure, there is a
MODBUS Client instance configured on the Ethernet interface.
When the interval of MainTask is greater than or equal to 100 ms after the fault is detected the
switchover will occur in up to two cycles of MainTask. When the interval of MainTask is less than
100 ms switchover will occur within 100 ms plus the time of MainTask after detection of failure.

ALTUS Nexto NX3004 Specifications

General

Brand	ALTUS
Model	Nexto NX3004
Category	Processor
Language	English