Why PM867 first net card warnning
Asked 10 days ago
Answers
1
A redundant controller will signal "No communication BackupCPU" if the Primary (running) CPU is unable to communicate with the Backup (standby) CPU over Ethernet.
The Backup CPU must be given an IP address via the serial IP configuration tool. Default is Disabled.
We recommend using the so called Default Rule which simply adds 0.0.2.0 to the Primary CPU's address and assign it to the Backup CPU. 172.16.1.2 + 0.0.2.0 = 172.16.3.2 which should fit a /20 subnet (but will not work with a /24 subnet).
The secondary Ethernet interface seem "parameterized" but:
a) left at default, disabled.
b) lacks RNRP explicit parameters (which is required since not using the /22 subnet size which is required for implicit addressing scheme)
If you want to run redundant network, be sure to enable the secondary Ethernet interface AND assign appropriate RNRP explicit parameters, then download, then perform a controller reset to make the changes take effect. Study the RNRP Monitor to see the result.
Please notice that the Backup CPU will not be listed by RNRP. If using routers (as in my case in the image above) the Backup CPU will not be pingable from any other network than its own (a Backup CPU does not need to communicate with anything else but the Primary CPU). As soon as failover takes place, the Backup CPU will become the running CPU and become routable from other networks.
If you can choose addresses, I recommend returning to a /22 subnetwork (255.255.252.0) - it will make the RNRP redundancy much simpler to setup. No explicit parameters required, leave them empty as they are right now.
The Backup CPU must be given an IP address via the serial IP configuration tool. Default is Disabled.
We recommend using the so called Default Rule which simply adds 0.0.2.0 to the Primary CPU's address and assign it to the Backup CPU. 172.16.1.2 + 0.0.2.0 = 172.16.3.2 which should fit a /20 subnet (but will not work with a /24 subnet).
The secondary Ethernet interface seem "parameterized" but:
a) left at default, disabled.
b) lacks RNRP explicit parameters (which is required since not using the /22 subnet size which is required for implicit addressing scheme)
If you want to run redundant network, be sure to enable the secondary Ethernet interface AND assign appropriate RNRP explicit parameters, then download, then perform a controller reset to make the changes take effect. Study the RNRP Monitor to see the result.
Please notice that the Backup CPU will not be listed by RNRP. If using routers (as in my case in the image above) the Backup CPU will not be pingable from any other network than its own (a Backup CPU does not need to communicate with anything else but the Primary CPU). As soon as failover takes place, the Backup CPU will become the running CPU and become routable from other networks.
If you can choose addresses, I recommend returning to a /22 subnetwork (255.255.252.0) - it will make the RNRP redundancy much simpler to setup. No explicit parameters required, leave them empty as they are right now.
0
RNRP Parameter calculator
Answered 8 days ago
0
Hello,
To configure IP address in AC800M controller, firstly need to configure primary/CN1 IP address for primary CPU keeping backup CPU off via toolport COM4 and always do the default formula to set the IP address for backup CPU which is 0.0.2.0 will be used in you case it will be 172.16.3.x/172.17.3.x (/22 subnet)
To enable the CN2, first stop the Backup CPU and configure the CN2 IP address from hardware editor of CBM and enable "enable Ethernet channel=true" its missed in your snap and download the configuration followed by reset the primary controller.
Now power on your backup controller and ensure the following for redundancy:
To configure IP address in AC800M controller, firstly need to configure primary/CN1 IP address for primary CPU keeping backup CPU off via toolport COM4 and always do the default formula to set the IP address for backup CPU which is 0.0.2.0 will be used in you case it will be 172.16.3.x/172.17.3.x (/22 subnet)
To enable the CN2, first stop the Backup CPU and configure the CN2 IP address from hardware editor of CBM and enable "enable Ethernet channel=true" its missed in your snap and download the configuration followed by reset the primary controller.
Now power on your backup controller and ensure the following for redundancy:
- CN1 and CN2 of both CPU connected to respective switches.
- Both controllers should have same firmware
- TK851 cable should be used if BC810 is used for segmentation.
- TK850 cable should be used, if BC810 not used generally for optical module bus communication where no CI used.
Add new comment