Known anomalies in this release

The list identifies the known anomalies in
FactoryTalk Policy Manager
 version
6.60.00
.
Use the identification information provided in the brackets
[]
 to track anomalies in future releases or to request assistance from Customer Support.

Automatic Policy Deployment fails to process some devices [1487250]

The Automatic Policy Deployment feature may fail to process
CIP Security
 devices with two or more EtherNet/IP interfaces enabled.
This anomaly first identified in version 6.30.

Automatic Policy Deployment adds devices with empty fields [1664017]

The Automatic Policy Deployment feature may add devices with empty Catalog Number, Vendor, and Firmware Revision fields to the Onboarding Area.
TIP: Devices with empty device type fields cannot be configured. To make such a device configurable, remove the device from the Onboarding Area and wait until the device is onboarded again.
This anomaly first identified in version 6.30.

FactoryTalk Policy Manager does not support empty passwords [3329276]

In
FactoryTalk Administration Console
, if you add a user with an empty user password, the user will not be able to log on to
FactoryTalk Policy Manager
.
To resolve this issue, add passwords to users with empty passwords.
TIP: To prevent this issue from happening again, in
FactoryTalk Administration Console
, in
Security Policy Properties
, set
Minimum password length
 to a value higher than
0
.
Rockwell Automation
 recommends using at least six character passwords.
This anomaly first identified in version 6.40.

Redundant 1756-EN4TR modules may freeze when you deploy a security policy model [3778439]

If you deploy a security policy to v5 1756-EN4TR modules that are in a redundant pair, one of the modules may freeze.
TIP: To prevent one of the modules from freezing, update the modules firmware to the latest revision, add the associated controllers to the model again, and then deploy the security policy.
This anomaly first identified in version 6.50.

Connections may not reset for deleted devices that communicate with each other securely [3281094]

After deleting and deploying two devices that communicate with each other using class 3 TLS, the connections are not reset even if you select
Reset existing connections
.
TIP: To reset secure communication between impacted devices, reset existing connections. For example, power cycle the impacted devices.
This anomaly first identified in version 6.50.

Redundant 1756-EN4TR modules cannot establish class 0/1 communication with I/O modules [4048807]

1756-EN4TR modules configured for redundancy do not support secure class 0/1 communication with I/O modules.
TIP: To establish secure class 0/1 communication between 1756-EN4TR modules and I/O modules:
  1. Add another 1756-EN4TR module to the chassis for secure class 0/1 communication with I/O modules.
  2. In
    FactoryTalk Policy Manager
    , do
    not
     add the 1756-EN4TR module to the security policy model and do
    not
     deploy the security policy to the module.
This anomaly first identified in version 6.51.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal