System driver data point "Active standby" rest sometimes empty after reconnect.
The defect appears only when the formally standby after the reconnect continue to be the active server. In that situation cut happens that the formally server, which is when connecting the new active server still be server, from the server will be accepted as client. The formally server don't report to the new server that he is the standby then at this time he is still server but not the active one. As result the system driver data point which hold the active standby is not filled. The role change of the formally server to standby was correctly processed and the redundancy was not influenced.
Now when the new active server detects that a computer which has actually a server role try to connect, it refuse this computer until his role change to standby.
This refusing creates for module net a warning log message: "SysMod Server tried to connect server"
System driver data point "Active standby" rest sometimes empty after reconnect.
The defect appears only when the formally standby after the reconnect continue to be the active server. In that situation cut happens that the formally server, which is when connecting the new active server still be server, from the server will be accepted as client. The formally server don't report to the new server that he is the standby then at this time he is still server but not the active one. As result the system driver data point which hold the active standby is not filled. The role change of the formally server to standby was correctly processed and the redundancy was not influenced.
Now when the new active server detects that a computer which has actually a server role try to connect, it refuse this computer until his role change to standby.
This refusing creates for module net a warning log message: "SysMod Server tried to connect server"
none