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.

3GPP Gy

  • When services are modified through DSA, SRC’s Gy sends CCR-I message instead of CCR-U message to the OCS. For a workaround, see the PR record. PR1097134
  • If SRC’s Gy is enabled after the SAE, SRC’s plug-ins are not initialized for certain subscribers. For a workaround, see the PR record. PR1097126

CLI

  • 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

Gx Router Driver (Services Control Gateway)

  • When the SRC software receives an incremented origin state ID in the first CCR-I message sent from the Services Control Gateway after the SAE restarts, the subscriber sessions with lesser origin state ID are not cleared from the session store. PR1098493
  • The output of the show sae subscribers command displays IPv4 address instead of IPv6 address even though activate-on-login provision is provided for IPv6 subscribers. PR1098520
  • For interface policies, the SAE does not send the Charging-Rule-Remove AVP to the Services Control Gateway during the SRC software triggered subscriber session detach scenario. PR1096826
  • When you modify the default policy configuration in the SRC software for active subscribers, the SRC software does not trigger the RAR messages. PR1098513
  • The SAE does not deactivate the services for the associated charging rules which are partially failed during provisioning of policies to the Services Control Gateway. For a workaround, see the PR record. PR1098515
  • The output of the show sae drivers command displays erroneous RAR attempt count in the Gx router driver statistics. PR1098496
  • When the SRC software receives CCR messages with two different origin state IDs from the Services Control Gateway during SAE startup or failover, the subscriber sessions with lesser origin state ID are not cleared from the session store. PR1098492
  • The SRC software sends the UNABLE_TO_DELIVER error to the Services Control Gateway instead of the UNABLE_TO_COMPLY error, when the origin state ID received in the CCR-I message is lesser than the value received in the previous message. PR1098499
  • CLI displays the application-accounting attribute in the policies group name list name rule name command for Gx router driver until the Gx specific rule type is selected. For a workaround, see the PR record. PR1097580
  • Subscriber classification based on interface name is not supported for IPv6 subscribers of Services Control Gateway. PR1098522

PTSP

  • 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

SAE

  • The show sae drivers device-name command displays the number of junos-ise and junos-ptsp devices that are not currently connected. PR904065
  • 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

Virtualized SRC Software

  • The create_vm.py script fails to create a virtualized SRC instance by using the qcow2 image if an invalid memory value is provided as input. For a workaround, see the PR record. PR1097104
  • The create_vm.py script fails to create a virtualized SRC instance by using the qcow2 image if the qcow2 image path provided as input contains a leading or trailing space. For a workaround, see the PR record. PR1095166

Modified: 2015-11-30