Duplicate Profinet Io-Controller Ip Address - GE PACSystems RXi User Manual

10.2.2 Duplicate PROFINET IO-Controller IP Address

The PNC detects that a network device has the same IP address as its own:
a) during power-up,
b) when a new hardware configuration is downloaded from the programmer and
c) during operation when a device with a conflicting IP address announces its presence
When a duplicate is detected during power-up, PNC reset, or new hardware configuration
store, the PNC:



When a duplicate IP address is detected after the PNC has established connection to
configured IO Devices, the PNC:



When the IP conflict is resolved, the PNC:



Note:
Resolving Duplicate IP Addresses
When an IP address conflict exists, IP-based network communication with the device(s) may
be disrupted. The IP address conflict should be resolved by disconnecting one of the
offending devices from the network or assigning each a unique address. The Duplicate IP
Address Detected fault lists the MAC address of the offending devices in bytes 8 – 13 and
14 – 19 of the Fault Extra Data. The Discovery and Configuration Protocol (DCP) tool in
Proficy Machine Edition may be useful to identify PROFINET devices on the network with
conflicting IP addresses.
GFK-2816F
on the network.
logs a Duplicate IP Address Detected fault for itself,
does not connect to any configured PROFINET IO Devices,
periodically queries the network for resolution of the IP address conflict.
logs a Duplicate IP Address Detected fault for itself,
disconnects from all currently-connected PROFINET IO Devices,
logs a Loss of Device fault for each PROFINET IO Device that was disconnected,
logs a Duplicate IP Address Resolved fault for itself,
attempts to re-connect all configured PROFINET IO Devices,
logs an Addition of Device fault for each connected PROFINET IO Device to indicate
that device is back online.
Power cycling an RXi Controller with the same IP address as another node on the
network will result in two Duplicate IP Address Detected faults in the I/O Fault table.
This is normal behavior that occurs because the PNC retains IP parameters through
a power cycle and attempts to exist on the network before receiving a new
configuration from the CPU. The first fault occurs before the PNC receives the new
configuration and the second fault occurs after the PNC receives its new
configuration. Both faults result in the PNC not attempting to connect to the network.
Chapter 10. PROFINET IO-Controller Operation
August 2015
8
207