8968 NRT network overlapping detected

Description

The host ranges of the network at the standard Ethernet port of the controller and the Sercos III NRT channel overlap. This overlap is caused by changing the NetID or the setting on the standard Ethernet port.

Changing the NetID

Cause	Solution
oBefore allocating any IP addresses, it is verified whether the networks and the currently set NetID overlap. If so, a message logger entry is triggered. oAt the same time, the system tries to fix the issue automatically by first accessing the default value of the parameter NetID (172.20.0.0). If the overlap continues to exist, the NetID 172.21.0.0 is used instead. oIf the issue could be solved this way, the message corrected is entered in the field Ext. Diagnosis of the message logger. oIf the overlap could not be removed, then the set NetID is used to allocate the IP address parameters. In the field Ext. Diagnosis of the message logger, the ip com.deact. is entered and the IP communication between the controller and the NRT channel is deactivated. oIf the IP address settings are set valid again, then the IP communication is active again. No message logger entry is triggered.	Verify the current set NetID or the communication setting on the standard Ethernet port (see below) and adjust them if necessary so that no network overlap can occur anymore.

Cause

Solution

oBefore allocating any IP addresses, it is verified whether the networks and the currently set NetID overlap. If so, a message logger entry is triggered.

oAt the same time, the system tries to fix the issue automatically by first accessing the default value of the parameter NetID (172.20.0.0). If the overlap continues to exist, the NetID 172.21.0.0 is used instead.

oIf the issue could be solved this way, the message corrected is entered in the field Ext. Diagnosis of the message logger.

oIf the overlap could not be removed, then the set NetID is used to allocate the IP address parameters. In the field Ext. Diagnosis of the message logger, the ip com.deact. is entered and the IP communication between the controller and the NRT channel is deactivated.

oIf the IP address settings are set valid again, then the IP communication is active again. No message logger entry is triggered.

Verify the current set NetID or the communication setting on the standard Ethernet port (see below) and adjust them if necessary so that no network overlap can occur anymore.

Changing the standard Ethernet Port

Cause	Solution
oIf the communication settings on the standard Ethernet port of the controller are changed and no network overlap with the existing Sercos III settings is detected, then the IP communication to the NRT channel is deactivated. The message 8968 appears with the Ext. Diagnosis ip com.deact. in the message logger. oIf these communication settings are set valid again, then the IP communication is active again. No message logger entry is triggered.	Verify the current set NetID (see above) or the communication settings on the standard Ethernet port and adjust them if necessary so that no network overlap can occur anymore.

Cause

Solution

oIf the communication settings on the standard Ethernet port of the controller are changed and no network overlap with the existing Sercos III settings is detected, then the IP communication to the NRT channel is deactivated. The message 8968 appears with the Ext. Diagnosis ip com.deact. in the message logger.

oIf these communication settings are set valid again, then the IP communication is active again. No message logger entry is triggered.

Verify the current set NetID (see above) or the communication settings on the standard Ethernet port and adjust them if necessary so that no network overlap can occur anymore.

NOTE: The check-ups for the network overlapping are performed at different times. This is why it can happen that the message is displayed in the message logger several times.