A forum for topics related to the scope of Modicon PAC offers and ecosystem along the whole lifecycle: Modicon M580 and 340, EcoStruxure Control Expert, EcoStruxure Process Expert (Unity Pro) and more.
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2023-02-1606:49 PM
M580 NUA100 OPC-UA Module
When using the NUA0100 OPC-UA module in CA mode, the CSR generated by the module has three ip addresses in the Subject Alternative Name field.
1. Backplane IP
2. Control Port IP
3. Default IP based on Mac Address.
We've recently discovered by accident that if any of the IP addresses within the Subject Alternative Name field are incorrect, the module will drop the certificate on restart and revert to a self signed and provide you absolutely no indication of why it's done this (whilst politely refusing to go into run mode).
I expect that the "Security Export" of this module contains all the modules certificates and private key and is intended to allow someone to restore the configuration onto another card in the event of failure given that a password must be entered to secure the information in the export.
If the OPC-UA module is being used in critical infrastructure, such as a water treatment plant and it fails out of hours, then i would expect an on-call maintenance technician to be able to arrive on site and replace it - especially if the module is being used as Schneider promote as the future planned link between GeoSCADA and M580 PACs.
The problem is that the technician can't get the module going again. The replacement module has a different default IP address (because it has a different MAC address) and after he restores the configuration and restarts the module the certificate is dropped and the unit will refuse to go into run.
This is pointless and means that a failed OPC module in CA mode can't be replaced out of hours without someone from ICT being woken up to generate a new certificate that matches the default IP address of the replacement unit.
It seems like an oversight and is a big enough operational risk that i would not recommend using the modules in CA mode anywhere where it forms part of a critical communication link.
The module needs to be updated to remove the default IP address from the Subject Alternative Name - it doesn't need to be there, and nothing remotely is talking to it using this IP anyway.