Recently, I have set up a SP2023R2SP1P01 environment, as shown below.
- Machine 1 – Windows Server 2025 with 16 GB and 8 CPUs. PCS SMS server, GR service repository, Historian, AEL and IDE are installed on this machine.
- Machine 2 – Windows Server 2025 with 16 GB and 8 CPUs with dual NICs. One of NICs is configured as private IP and not registered on DNS. This channel will be used for RMC and PLC communications. PCS runtime, App Server and OMI, Historian client are installed on this machine. The machine hosts AOS1
- OFSOPC server is configured talking to remote PLCs via the private IP.
- OI Server gateway is configured to talk to the local OFSOPC
- SuiteLink instance is configured to talk to the local OI Gateway.
- Machine 3 – Windows Server 2022 with 16 GB and 8 CPUs with dual NICs. The installation is the same as machine 2. This machine hosts AOS2
- Machine 4 – Windows 11 with 8 GB and 4 CPUs where PCS runtime, App Server and OMI, System Monitor, and historian client are installed.
The configured galaxy is deployed without any issue. However, the following messages are flooded in Logger on the primary engine node as shown below after set Redundancy.ForceFailoverCmd = true. I rebooted this primary node but it didn’t resolve the issue until I used the failover command again to make this primary node on scan.
Has anyone seen that the message of “Rejecting mx message.AppEngine_001 1.3.3 GetRequest MxSubscribe3 (version ) from 1.3.1” floods aaLogger on the primary node when its backup is on scan before? How could I suppress this message? Thanks.