6. HX3040 Redundancy
272
NIC Teaming and Active IP Combined Use
If a given pair of ports form a NIC Teaming pair in a redundant CPU, they can implement, at the
same time, the Active NIC Teaming and IP strategies.
For example, if the NET 1 and NET 2 ports of the CPU form a NIC Teaming pair, then:
CPU A IP Address: IP address of the ports NET 1 + NET 2 of CPU, which is in position 2 of the
bus.
CPU B IP Address: IP address of the ports NET 1 + NET 2 of CPU, which is in position 3 of the
bus.
Active IP Address: IP address of the ports NET 1 + NET 2 of that CPU which is in Active state.
Thus, the Hadron Xtorm Series combines the excellent availability of NIC Teaming strategy with the
practicality of Active IP strategy, releasing scripts in SCADA systems or other clients connected to
servers in the Active CPU.
Redundant CPU States
In a redundant system, the CPU (CPUA or CPUB) may present the following states:
Active
Stand-by
Inactive
Non-Configured
Starting
ATTENTION:
Frequently this manual uses the designation “Non-Active” for any state other than Active (Stand-by,
Inactive, Non-Configured and Starting).
In the following sections, these five states are briefly described. For further details regarding the
redundant CPU see Transition between Redundancy States, which also describes the states machine
and the transition causes among them.
Non-Configured State
This is the initial redundancy state. The CPU is in this state when:
The CPU is OFF (convention)
Before starting the MainTask
Before there is a switch into the Starting state
In case there is a restart through commands like Reset warm, Reset cold or Reset origin
In case the MainTask runs in Non-Configured states, the CPU performs the following tasks:
The bus modules are not controlled by the CPU
The cyclic synchronization services are executed as long as the requirements for that are fulfilled
(see Cyclic Synchronization Services through Redundancy Synchronism Channels)
The sporadic synchronization services can also be executed (see Sporadic Synchronization
Services through Redundancy Synchronism Channels )
The CPU will be blocked in the Non-Configured state if the other CPU is in Active state, and this
CPU project is different from the Active CPU project. In a situation other than that, the CPU goes
from the Non-Configured state for the Starting one, as soon as the configuration request arrives.
Sometimes, the CPU goes into the Non-Configured state when it has already received an automatic
configuration request. In this case, the user does not need to make a new request for changing the
state. This happens at the CPU energizing, for instance.