Network redundancy not working in AC 800M controllers
I am commissioning a redundant PM866 controller on a platform and I am facing some issues with regards to the network redundancy.
The Enable Ethernet Channel parameter was previously set to false, I enabled this parameter, made a download to the controller and performed a controller reset (INIT > 3s) by resetting the backup first and then the primary after the backup had synchronized. But the CN2 Ethernet interface is reporting the error No Communication BackupCPU.
I have checked the controller log, both ethernet interfaces are enabled on both primary and backup. I have tried pinging both controllers, which works except for CN2 on the primary. Pinging CN2 on backup works.
In the controller log for the primary CPU there is reported the following error:
NetIntersup Failed to bind IP address to secondary interface, CHECK IP ADDRESS !!!!
NIS:Sup Error init send socket
I suspect there is some issues with enabling CN2 on primary. I have attached controller logs.
Looking forward to your replies.
I'm no expert on the controller but I agree with your suspicion - hardware...
IP settings looks good, valid address and backup controller is using default (0.0.2.0) rule
Network Interface 172.16.80.157 (255.255.252.0 ) : 00-00-23-18-90-3e
Network Interface 172.17.80.157 (255.255.252.0 ) : 00-00-23-18-90-3f
Backup Interface 172.16.82.157 (255.255.252.0 ) (default rule)
Backup Interface 172.17.82.157 (255.255.252.0 ) (default rule)
By not being able to ping 172.17.80.157 you have ruled out that something else is holding that IP address.
Do you have any spare units?
Can you swap primary/backup and see if the problem follows the hardware (thus increasing the probability of a defective CN2 port)?
I suggest filing a support case with your regional ABB support team.
please ensure that standby controller should be off while setting the IP address else change over may occur & always we should set the primary Ip address only through the tool cable by connecting CN1 cable to the network & then reset the controller to set the IP address & then secondary IP address to be set through the CBM in ethernet2 "enable ethernet connection" to be true so while downloading hardware configuration ensure CN2 cable is connected to secondary switch & Standby controller should be remains turned off then download the controller & reset the controller through the INIT button
then ping the CN2 IP address.
As per log Ip address set are 172.16.80.157/172.17.80.157 for primary controller
for backup controller its 172.16.82.157/172.17.82.157 as per default rule.
it looks Ok.
So here make the secondary controller as primary by switching over & then try to ping the CN2 IP address as 172.17.80.157 if it works & then ping 172.17.82.157 if this not works then CN2 is not working for this controller then replace the total hardware (baseplate+controller) since GUID is unique for each controllers.