SDX 6.4.0 Release Notes > Known Problems and Limitations

Known Problems and Limitations

This section identifies known problems and limitations in this release.

eTrust Directory

• When you first configure an action with Policy Editor, make sure that you fill in a value for the Description field. If the Description field is not filled in when you first create the action, some of the attributes might not be saved to eTrust Directory. Subsequent configuration changes to this type of action do not require you to fill in the Description field.

Reference: TIC 12056

JPS

• If you change the JPS configuration for the RKS interface on a running JPS, some RADIUS messages might be lost.

Reference: TIC 11917

• The JPS might fail to close the TCP connection to the application manager when it closes COPS connections.

Reference: TIC 11902

SAE

• When you have installed and are using SDX Release 6.3.0 in a PCMM I02 environment, you cannot migrate active SSP services to SDX Release 6.4.0 in a PCMM I03 environment.

Reference: TIC 11967

• When the passive SAE is unreachable from the active SAE, there are two active SAEs.

Reference: TIC 11890

SAE Web Admin

• When you check the JUNOS configuration with SAE Web Admin, the Check configuration button does not work properly.

Reference: TIC 11834