Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

Known Problems and Limitations

This section identifies known problems and limitations in this release.

For the most complete and latest information about known defects, use the Juniper Networks online Problem Report Search application.


  • The SRC software supports VSA definitions only in the format Vendor-Specific.4874.<vsa#>.<type>, even though the SRC software accepts other formats too. PR939170
  • When you load backup configuration from XML or text file by using the load replace command, the CLI displays a null pointer exception because of the new logrotate files added in the SRC Release 4.8.0. The load merge and load override commands load the backup configuration without any error. For a workaround, see the PR record. PR1039688
  • Remote authentication (TACACS or RADIUS) is not working after migrating to the SRC Release 4.8.0, because the remote user is not getting mapped to the TACACS or RADIUS user. For a workaround, see the PR record. PR1049786
  • File operational commands (for example, the file list command) are not working when used with usb:// url. For a workaround, see the PR record. PR1050706


  • When upgrading the DSA RPM, a ZIP warning message Local Entry CRC does not match CD: WEB-INF/ is displayed but the RPM is installed successfully. The DSA functionalities are not impacted so you can ignore this warning message. PR1048403


  • SRC Release 4.8.0 has been updated to run on Centos 6.5. However, this operating system does not support older C series controllers (C2000 and C4000) because of hardware incompatibility. PR1049794


  • When deleting the JDB community in secondary node, the SRC software sometimes displays a service unavailable exception but sets the mode to standalone and retains the replication agreement. If the community is configured again, the erroneous attributes in the agreement sometimes affect the replication feature. For a workaround, see the PR record. PR1042609


  • Subscribers get some services activated without subscription, if services refer to the same policy group. For example, if a subscriber is only subscribed to Internet-Bronze, Internet-Gold may get activated if both the services refer to the same policy group. PR906540


  • The show sae drivers device-name command displays the number of junos-ise and junos-ptsp devices that are not currently connected. PR904065
  • After you change IP address and then restart the components such as SAE and NIC, the newly changed addresses are not displayed in the sminfo.log file. PR904184
  • The service associated with the incorrect ESSMD policy exists in SAE but not in the MX series router if the Diameter component in the SRC software or Diameter service in the router is restarted before the router sends a session-sync-AAR message with failed policy information to SAE. PR1049102
  • SAE RADIUS local address and SAE real portal address are not getting updated properly after installing the SRC Release 4.8.0. As a workaround, you must manually configure these attributes. For more information on the workaround, see the PR record. PR1039725

Modified: 2015-07-22